[Yt-dev] Packed AMR hierarchy problem
Stephen Skory
stephenskory at yahoo.com
Thu Nov 19 11:29:46 PST 2009
> > -> arr = myGroup.create_dataset(name,data=array)
> > (Pdb) name
> > 'DataFields'
> > (Pdb) array
> > []
>
> Interesting. Any ideas on how to fix it? :(
None now, sorry. I'm focusing on the hg version.
> As a sanity check, can you do this with the hierarchy-opt branch? To
> make sure I didn't screw anything up during the merge.
I get exactly the same issues. Which is a kind of good.
> self.max_level is being calculated wrong, and my suspicion is that
> it's getting the grid count, not the maximum level. Can you manually
> examine the .harrays file to make sure this is the case? Looking at
> the short output you have below, looks like it might actually be
> putting the ParentIDs into the level array.
The maximum value in .harrays["/Level"] (I used h5dump to check, to be sure) is the same as self.max_level, which is as it should be, right? I have self.max_level = 2867, max(["/Level"]) = 2867, the number of grids is 5403, MAXLEVEL is 48. Should self.level_stats have 2867 entries, 5403 or 48?
_______________________________________________________
sskory at physics.ucsd.edu o__ Stephen Skory
http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student
________________________________(_)_\(_)_______________
More information about the yt-dev
mailing list