I have a small handful of use cases where it would be nice to save a serialized projection.  The primary case I'm thinking of is making projections on a supercomputer and downloading the serialized files locally to make images.  However, if we're totally rethinking what yt should be doing on its own with writing files, I am totally in favor of making it an explicit, opt-in thing.  Is it simple enough to set the serialization keyword default to False?

In general, performing analysis on supercomputers and then downloading reduced data to my laptop to make figures is how I do almost everything.


On Fri, Apr 19, 2013 at 11:18 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Dave, out of curiosity, how long does a projection of one of your datasets take?

On Fri, Apr 19, 2013 at 11:17 AM, david collins <antpuncher@gmail.com> wrote:
>
> I use serialized projections quite frequently.  As long as the current
> behavior, or some reasonable facsimile, is still available I'm for doing it
> now.
>
>
> On Fri, Apr 19, 2013 at 9:05 AM, Matthew Turk <matthewturk@gmail.com> wrote:
>>
>> On Fri, Apr 19, 2013 at 11:02 AM, Stephen Skory <s@skory.us> wrote:
>> > Just to play devil's advocate here, what would it take to "fix"
>> > serialization? Adding a checksum so that data changes can be detected?
>> > More than that?
>>
>> That would partly fix the issue of fields/hierarchy changes not being
>> detected (unless you manually mess with the data).  But it wouldn't
>> fix the deeper problem, which is that a) we scatter files willy nilly
>> about the directory, which I am coming to feel is a really gross
>> violation of expectations, and b) the process of auto-serialization
>> doesn't save a huge amount of time in most cases.  JohnW and I
>> spitballed last fall about some of the biggest hierarchies he's dealt
>> with in Enzo and I promised to write a Cython parser, which I never
>> succeeded at.
>>
>> -Matt
>>
>> >
>> >
>> >
>> > --
>> > Stephen Skory
>> > s@skory.us
>> > http://stephenskory.com/
>> > 510.621.3687 (google voice)
>> > _______________________________________________
>> > yt-dev mailing list
>> > yt-dev@lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev@lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
>
> --
> Sent from my computer.
>
> _______________________________________________
> yt-dev mailing list
> yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org