Oh man, that Sam Skillman from a couple of years ago really dropped the ball.  I did not end up giving it a go or report back!

That said, I think Matt's suggestion still holds up.  

One other option would be to use (or modify) the write_to_gdf functionality, though this would duplicate the data.  

So to reuse some bits...
If you give this a shot and test it, let us know how it goes, and feel free to pull request if it works out.

Sam


On Tue, Feb 5, 2013 at 12:50 PM, Andrew Myers <atmyers@berkeley.edu> wrote:
Hello YT users,

A couple of years ago, Sam Skillman (email chain attached) asked about support for saving derived fields to the disk, so we don't have to re-compute expensive fields over and over again. Did this functionality ever make it into yt? I'm working on something where this would be very useful, so if not I might have a go at implementing myself.

Thanks,
Andrew Myers

---------- Forwarded message ----------
From: Sam Skillman <samskillman@gmail.com>
Date: Tue, Jan 11, 2011 at 9:40 AM
Subject: [Yt-dev] saving derived fields
To: yt-dev@lists.spacepope.org


Hi all,

I've started dealing with a lot of time-consuming derived fields and am wondering if there is already support for writing derived fields back to the raw data files (e.g. .cpu files).  If not, any thoughts on doing so?   

Sam

_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org



_______________________________________________
yt-users mailing list
yt-users@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org