The second place should occur very early on in the instantiation of the hierarchy; you should be able to generate that error with just:
pf = load("my_data") pf.h
and it will die. Is that in fact the case?
There are a couple things we can do to reduce the memory overhead. A while back I was working on them, and the nascent efforts are in yt-hierarchy-opt on hg.enzotools.org.
The first problem you cite below is still odd to me.
On Wed, May 6, 2009 at 11:35 AM, Stephen Skory firstname.lastname@example.org wrote:
I'm still trying to run HOP on the 1024^3 dataset on Ranger. It's been dying in two places inconsistently, meaning two consecutive runs will die either place. Line 196 in BaseDataTypes.py:
where it's complaining that self.fields doesn't have append. In HierarchyType.py at line 92:
self.gridTree = [  for i in range(self.num_grids)]
Sometimes it gives a memory error. self.num_grids is 440,000+, but in my testing it doesn't matter how lists it's trying to make, it that's where it wants to die it dies.
I'm running on Kraken right now. We'll see how it goes.
_______________________________________________________ email@example.com o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_(_)_______________
Yt-dev mailing list Ytfirstname.lastname@example.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org