<div dir="ltr">This works for me (although I don't think there is a concept of H2_p1 when dealing with nuclei). Also it is interesting to see how different people view our field (astrophysics). I would have called the nuclear physics stuff "astrophysics" and the other stuff "chemistry" :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 7, 2014 at 10:52 AM, Britton Smith <span dir="ltr"><<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would rather not change the field names to denote the domain, but instead only optionally make fields available with varying naming convention based on loaded field plugins. For example, you might have in astrophysical_species:<div>("gas", "H_number_density")</div><div>("gas", "H_p1_number_density")</div><div><br></div><div>but in nuclear_physics_species:</div><div>("gas", "H1_number_density")</div><div>("gas", "H1_p1_number_density")</div><div>("gas", "H2_number_density")</div><div><div>("gas", "H2_p1_number_density")</div></div><div>to denote different isotopes.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 7, 2014 at 10:46 AM, Cameron Hummels <span dir="ltr"><<a href="mailto:chummels@gmail.com" target="_blank">chummels@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I like the idea of having context-specific field domains. It seems to me that is why the field system was generalized to have two parts in the first place. Perhaps we could move the nuclear fields to ('nuclear', 'Ytterbium_V') or something like that? Either way, I'm in favor of expanding YTEP-0003. Good suggestions everyone.<div><br></div><div>Cameron</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Oct 7, 2014 at 7:37 AM, Britton Smith <span dir="ltr"><<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Chris,<div><br></div><div>Thanks for starting this discussion. As you have stated, trying to encompass all domains with a single nomenclature probably won't work. Currently, the field system is set up to load all field plugins for every dataset, but I think we should be able to move to having different frontends declare which plugins they want and only load those. With that in place, for example, the current species field plugin can be renamed to be astrophysics-specific and another one can be created that is nuclear physics-specific. If people are in favor of something like this, then I would suggest that we try to expand YTEP-0003 to different domains and establish the naming conventions there.</div><div><br></div><div>Britton</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Oct 6, 2014 at 7:29 PM, Chris Malone <span dir="ltr"><<a href="mailto:chris.m.malone@gmail.com" target="_blank">chris.m.malone@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">At Britton's great suggestion, let's move the discussion of what to do with species fields from BitBucket comments to here. For reference, see the discussion in the comments here [1]. Note that the current situation is outlined in YTEP-003, specifically the section on species names [2].<div><br></div><div>The main issue is that yt supports a wide range of codes, which are applicable in various domains of science and sometimes the nomenclature clashes. What is meant by 'species' is a prime example. 'Species' can mean atomic elements, ions, or nuclei (perhaps others?), and the definition of each of these should - if it is possible - be made explicit.<br><div><br></div><div>Agreeing on the yt-internal nomenclature for this explicitness requires some discussion.</div><div><br></div><div>[1] <a href="https://bitbucket.org/yt_analysis/yt/pull-request/1240/bugfix-fixing-nuclei-density-fields/diff" target="_blank">https://bitbucket.org/yt_analysis/yt/pull-request/1240/bugfix-fixing-nuclei-density-fields/diff</a></div><div>[2] <a href="http://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0003.html#molecular-and-atomic-species-names" target="_blank">http://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0003.html#molecular-and-atomic-species-names</a></div></div><span><font color="#888888"><div><br></div><div>Chris</div></font></span></div>
<br></div></div>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</font></span></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Michael Zingale</div><div>Associate Professor</div><div><br></div><div>Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800</div><div><i>phone</i>: 631-632-8225</div><div><i>e-mail</i>: <a href="mailto:Michael.Zingale@stonybrook.edu" target="_blank">Michael.Zingale@stonybrook.edu</a></div><div><i>web</i>: <a href="http://www.astro.sunysb.edu/mzingale" target="_blank">http://www.astro.sunysb.edu/mzingale</a></div>
</div>