[yt-dev] gdf frontend and standards in tension?

j s oishi jsoishi at gmail.com
Thu Jan 30 13:08:30 PST 2014


Stuart,

Wow, a parallel gdf writer? I was planning to add that sometime next week
or so. I'd like to know how you approached it. I was simply thinking of
having a flag to only write a data-only "sidecar" file that would use HDF5
links in the master file for grids on other cores. Please let me know if I
can help integrate what you've done into this framework.

Jeff


On Thu, Jan 30, 2014 at 11:09 AM, Stuart Mumford <stuart at mumford.me.uk>wrote:

> Interesting!!
>
> I will have a look over this, I wrote a parallel compatible version of
> this code a while back I will try and get it working within your
> module.
>
> Stuart
>
> On 29 January 2014 22:22, j s oishi <jsoishi at gmail.com> wrote:
> > Hi all,
> >
> > I've adapted yt's gdf_writer.py into a standalone class called pygdf
> > (https://bitbucket.org/jsoishi/pygdf). I've done this so that any python
> > code can now save data in the gdf format.
> >
> > While doing this, I came across something in the yt gdf frontend that I'm
> > not quite sure I understand. In the grid metadata, yt expects
> > /grid_particle_count to be a 2-D array, but the gdf standard clearly
> states
> > this should be a 1-D (int64, N) array, where N is the number of grids.
> > Further complicating the issue is the fact that if I create a 1-D array
> for
> > /grid_particle_count, the failure point in the following script
> >
> > from yt.mods import *
> > pf = load("/tmp/blah.gdf")
> >
> > sp = SlicePlot(pf, 2, "Density")
> >
> > is actually in data_objects/grid_patch.py, not in the gdf frontend
> itself.
> > The file /tmp/blah.gdf can be generated by running the test.py script in
> > pygdf.
> >
> > The obvious workaround is to simply make /grid_particle_count a 2D array
> > (this is especially so since I'm not actually using particles at the
> > moment), but I'm not sure why this should be so. The total count of
> > particles in N grids seems to be better fit in a 1-D array to me.
> However,
> > I'd like to understand better what's going on. Any pointers or
> clarification
> > would be very helpful.
> >
> > Also, any feedback on pygdf would be most welcome!
> >
> > thanks,
> >
> > j
> >
> > _______________________________________________
> > yt-dev mailing list
> > yt-dev at lists.spacepope.org
> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20140130/32c95959/attachment.htm>


More information about the yt-dev mailing list