+1 to Mike, but it also means someone has to agree to be the Dumses frontend keeper. Are you willing to be that person, Chris? On Tue, Oct 7, 2014 at 7:41 AM, John ZuHone wrote:

+1 to Mike

John ZuHone Kavli Center for Astrophysics and Space Research Massachusetts Institute of Technology 77 Massachusetts Ave., 37-582G Cambridge, MA 02139 (w) 617-253-2354 (m) 781-708-5004 jzuhone@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com

On Oct 7, 2014, at 10:40 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:

My vote would be that if someone is willing to maintain a new frontend, then it should go in, so it keeps sync with the rest of yt.

On Tue, Oct 7, 2014 at 10:37 AM, Chris Malone wrote:

...

All,

Are there any requirements/restrictions on what types of codes should be added as new frontends in the yt repository?

I ask because yesterday I wrote a frontend for a collaborator working with the Dumses code. As best I can tell, Dumses is a stripped-down version of Ramses, but without the AMR and with a completely different file format. Also, as best I can tell, only a handful of people (mainly at the CEA?) work on this code, and it is nigh-impossible to find any information on the interwebs about it.

Should I fold this new frontend into the main yt repo, or just give the users of Dumses the frontend code and let them do what they will? The former might pull in a couple more users/developers, but the latter would keep us from cluttering yt/frontends.

Chris

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

-- Michael Zingale Associate Professor

Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale

_______________________________________________ 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

-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org

Thanks for the feedback. I wouldn't mind helping keeping it maintained, but I couldn't be the sole maintainer, as I don't have the actual Dumses code and can't keep up with changes. My colleague says there is probably a person or two at CEA who would be willing to become co-keeper of the frontend. And I would get them to put a dataset up for testing. My current plan of attack was to finish making modifications in my repo, then let the Dumses users/devs know how to get it and test it out. If they're happy with it, and agree to (co-)maintain the frontend code, then we'll move forward with putting it into the main yt repo. Chris On Tue, Oct 7, 2014 at 8:45 AM, Britton Smith wrote:

I am in favor of including it. If it is kept aside in a separate branch, it may be difficult to maintain as yt infrastructure changes. I strongly recommend seeing if you can get a hold of a sample dataset that could be posted to yt-project.org/data and used for answer testing.

Britton

On Tue, Oct 7, 2014 at 10:41 AM, John ZuHone wrote:

...

+1 to Mike

John ZuHone Kavli Center for Astrophysics and Space Research Massachusetts Institute of Technology 77 Massachusetts Ave., 37-582G Cambridge, MA 02139 (w) 617-253-2354 (m) 781-708-5004 jzuhone@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com

On Oct 7, 2014, at 10:40 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:

My vote would be that if someone is willing to maintain a new frontend, then it should go in, so it keeps sync with the rest of yt.

On Tue, Oct 7, 2014 at 10:37 AM, Chris Malone wrote:

...

All,

Are there any requirements/restrictions on what types of codes should be added as new frontends in the yt repository?

I ask because yesterday I wrote a frontend for a collaborator working with the Dumses code. As best I can tell, Dumses is a stripped-down version of Ramses, but without the AMR and with a completely different file format. Also, as best I can tell, only a handful of people (mainly at the CEA?) work on this code, and it is nigh-impossible to find any information on the interwebs about it.

Should I fold this new frontend into the main yt repo, or just give the users of Dumses the frontend code and let them do what they will? The former might pull in a couple more users/developers, but the latter would keep us from cluttering yt/frontends.

Chris

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

-- Michael Zingale Associate Professor

Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale

_______________________________________________ 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

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

Sounds good - I'll add it to my list. Also, the _skeleton frontend is out of date. I'll fix that too. Chris On Tue, Oct 7, 2014 at 9:33 AM, Nathan Goldbaum wrote:

Hi Chris,

While you're at it, it might be worthwhile to update this page, which is still somewhat out of date:

http://yt-project.org/doc/developing/creating_frontend.html

Nathan

On Tuesday, October 7, 2014, Chris Malone wrote:

...

Thanks for the feedback.

I wouldn't mind helping keeping it maintained, but I couldn't be the sole maintainer, as I don't have the actual Dumses code and can't keep up with changes. My colleague says there is probably a person or two at CEA who would be willing to become co-keeper of the frontend. And I would get them to put a dataset up for testing.

My current plan of attack was to finish making modifications in my repo, then let the Dumses users/devs know how to get it and test it out. If they're happy with it, and agree to (co-)maintain the frontend code, then we'll move forward with putting it into the main yt repo.

Chris

On Tue, Oct 7, 2014 at 8:45 AM, Britton Smith wrote:

...

I am in favor of including it. If it is kept aside in a separate branch, it may be difficult to maintain as yt infrastructure changes. I strongly recommend seeing if you can get a hold of a sample dataset that could be posted to yt-project.org/data and used for answer testing.

Britton

On Tue, Oct 7, 2014 at 10:41 AM, John ZuHone wrote:

...

+1 to Mike

John ZuHone Kavli Center for Astrophysics and Space Research Massachusetts Institute of Technology 77 Massachusetts Ave., 37-582G Cambridge, MA 02139 (w) 617-253-2354 (m) 781-708-5004 jzuhone@space.mit.edu jzuhone@gmail.com http://www.jzuhone.com

On Oct 7, 2014, at 10:40 AM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:

My vote would be that if someone is willing to maintain a new frontend, then it should go in, so it keeps sync with the rest of yt.

On Tue, Oct 7, 2014 at 10:37 AM, Chris Malone

...

wrote:

...

All,

Are there any requirements/restrictions on what types of codes should be added as new frontends in the yt repository?

I ask because yesterday I wrote a frontend for a collaborator working with the Dumses code. As best I can tell, Dumses is a stripped-down version of Ramses, but without the AMR and with a completely different file format. Also, as best I can tell, only a handful of people (mainly at the CEA?) work on this code, and it is nigh-impossible to find any information on the interwebs about it.

Should I fold this new frontend into the main yt repo, or just give the users of Dumses the frontend code and let them do what they will? The former might pull in a couple more users/developers, but the latter would keep us from cluttering yt/frontends.

Chris

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

-- Michael Zingale Associate Professor

Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale

_______________________________________________ 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

_______________________________________________ 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