Sorry to chime in so late. I have run hop on ranger on a 1024^3 unigrid about a week or so ago. I had to give it a relatively large amount of ram to make it go, but it did eventually work. However, when it failed, I was not getting that error. I believe it was something that specifically mentioned being out of ram. Unfortunately, I have to leave for the airport now, so I don't have time to add anything more useful at the moment. I will come back later and try to take a closer look. Britton On Thu, Apr 30, 2009 at 12:07 PM, Matthew Turk <matthewturk@gmail.com>wrote:
Hi Stephen,
Is this what you had in mind?
Sure is.
This ran just fine using 32 threads on 16 nodes on Ranger. The two threads I watched with top maxed out at about 20% of the node each, with roughly 1/2 of the system memory shown as 'used.'
Okay, so that's roughly what we saw before. So it's probably not a memory issue.
dir() on which object? The hoplist? Or self.data_source in HaloFinding?
Sorry -- dir() on the so-called 'list' object that is throwing the error. I'd say dig in there, see if it's a Python error. If 'append' is in the dir but it throws an attribute error, then there's a bug in the interpreter or somehow yt is propagating a bug upwards.
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org