[Yt-dev] yt dataset database screencast

Cameron Hummels chummels at astro.columbia.edu
Thu Sep 8 21:00:18 PDT 2011


Stephen,

This is great!  What an excellent way of keeping track of your
datasets.  A couple of comments:

1) It might be nice to have a function which instantiates the datadumps
into the Amazon DB without having to actually load them in yt (to save
the time of actually loading them one-by-one). 

2) It might also be nice to have a keyword / description that one could
set in the PF or perhaps in the DB when loading the DDs, for
identification purposes (e.g. This is the run I did to look at metal
cooling with feedback, etc.).  Perhaps that is something that should be
built into enzo's PF though.  Hmm...

3) Is this functionality specific to enzo datafiles, or is it universal
to anything yt accesses?  I see the "ProblemType" header, which suggests
that it may be unique to enzo.  Or is it just pulling from a variety of
different headers which are defined in each datafile, regardless of
simulation-code origin?  It would be good for this to keep with yt's
goals of universal acceptance of other sim codes.

Also, the screencast is great for demonstrating this functionality (much
better than had you written a detailed email message explicating it). 
Anyway, good work!  I look forward to this sort of functionality being
included in yt, so that I can better track my different datasets instead
of just by filename (e.g. I just finished a job named L20S2D9H26SPMZF1 !!)

Cameron



On 09/08/2011 11:16 PM, Stephen Skory wrote:
> Hi all,
>
> this is not finished, but I wanted to show you all what I've been
> working on for the last couple days. I think it's interesting and
> promising. To remind you, the idea is that whenever you load() a
> dataset in yt, it will update a database on Amazon AWS with some
> information about that dataset. This will provide you with a central
> location where you can see all datasets you've ever touched with yt.
> I've written a cgi-bin python script that, given your AWS credentials,
> will display entires in your database and allow you to build queries
> to narrow things down. To give you an idea of what I've done, and to
> solicit ideas for improvements, and to play around with this whole
> screen casting thing, I've made a screen cast showing what I've got so
> far. This is linked below.
>
> So - let me know if you have any ideas or comments. Like I said, it's
> unfinished, but it works well enough to show off. Thanks!
>
> http://vimeo.com/28797703
>

-- 
Cameron Hummels
PhD Candidate, Astronomy Department of Columbia University
Public Outreach Director, Astronomy Department of Columbia University
NASA IYA New York State Student Ambassador
http://outreach.astro.columbia.edu 
PGP: 0x06F886E3




More information about the yt-dev mailing list