Hi Doug and Chris, Chris -- glad to see you're making good progress. I'm hopeful that this will become useful for you and your collaborators in the near term. Doug -- I'm very glad to hear you're interested in adding support for ART. My concern in the past has been that the ART file format seems to be somewhat in flux, but with you on board this should not be a problem. :) The RAMSES frontend has a couple different sections in it. My suggestion to Chris was to excise from it the patch coalescing mechanism and the broad python structure that works with it. The patch coalescing does not currently work in parallel, but because it works via domain decomposition naturally this should not be terribly difficult to implement. I have not yet implemented a serialization mechanism for the coalesced hierarchy, but that is from a lack of time, not a lack of will. So, yes, I think that the important sections of the RAMSES frontend will be general enough, and if they are not I will refactor them so that they are. Also, Doug -- thanks for your interest in yt! I am very excited to see interest in adding support for ART, and I'll do what I can to assist with that. Best, Matt On Wed, Sep 29, 2010 at 1:59 PM, Douglas Rudd <douglas.rudd@yale.edu> wrote:

Hi all,

I'm the developer of the distributed version of the ART code, newer than the one Daniel uses, but built on the same basic structure.

I have been interested in adding an ART yt reader for a while, but haven't had the time to get started.  Chris: if you want to give it a shot, feel free to send me questions, and I'll try to generalize your reader to the current version of ART.

Is the RAMSES frontend sufficiently feature-complete to be used for this purpose?

Douglas Rudd douglas.rudd@yale.edu

On 9/29/10 4:43 PM, Christopher Moody wrote:

...

Howdy folks,    I wanted to announce that I just committed to the hg repo a reader for Daniel Ceverino's particular version of the ART code. My research interest is to pipe his ART data to Sunrise via yt. As for the code, It's still a rudimentary reader, and I've included only a draft version of the frontend ('cevart'). I'll be using the RAMSES frontend as a starting point, fleshing it out to fit Daniel's data. Unfortunately, I believe Daniel's data is a bit post-processed, and so my work is not particularly generic.  So if anyone has any information on how ART typically generates it's outputs, please contact me!

Thanks, chris _______________________________________________ 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