<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 4:33 PM, 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">Wait, so we'd have both an 'all' ftype and an 'n-body' ftype and the 'n-body' ftype would just include non-gas particles (ie ones without the 'smoothing_length' field)? I'm assuming this won't add more computational load when reading in the dataset? </div></blockquote><div><br></div><div>I doubt it. There will just be some more fields in ds.derived_field_list (one 'n-body' field for each of the 'all' fields).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If that's the case, then I'm +0.5 on it. I haven't had a need for it up to this point, but maybe other people really need it?</div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 2:21 PM, John ZuHone <span dir="ltr"><<a href="mailto:jzuhone@gmail.com" target="_blank">jzuhone@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 style="word-wrap:break-word">+1.<div><br></div><div>"n_body"?</div><div><div class="m_3168107345220518545h5"><div><br></div><div><div><blockquote type="cite"><div>On Mar 29, 2017, at 5:19 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>> wrote:</div><br class="m_3168107345220518545m_-5319955312075545618Apple-interchange-newline"><div><div dir="ltr">+1, and I think updating YTEP-0031 is sufficient. Not sure that "n-body" specifically is my preference, since it's not tokenizable, but maybe it's fine.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 4:18 PM, Nathan Goldbaum <span dir="ltr"><<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@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 all,<div><br></div><div>I'd like to propose adding a new particle union that should be defined for all datasets that include particles. This came up in the context of the demeshening work (see <a href="https://bitbucket.org/yt_analysis/ytep/pull-requests/67" target="_blank">https://bitbucket.org/yt_<wbr>analysis/ytep/pull-requests/67</a> for more details).</div><div><br></div><div>Right now many of the derived quantities make a distinction between calculating results using just the gas or just the particles or both. Up until now they have calculated the results for particles using particle fields from the 'all' particle union. This makes perfect sense for AMR data but doesn't really make sense for SPH data, since it will double-count SPH particles. In fact, I think this is an issue even without the demeshening, but the demeshening makes it more starkly apparent.</div><div><br></div><div>I'd like to propose defining a new "n-body" particle union (suggestions for alternate names are very welcome) that will be defined for all yt datasets. This union will be identical to the 'all' particle union for AMR data and N-body particle data, but for SPH data will only include the particle types that aren't SPH particles (if any). That means the "n-body" particle type represents infinitesimal particles but not particles that have finite extents (e.g. an SPH particle's smoothing region).</div><div><br></div><div>I think this new particle type would probably be generically useful beyond just the derived quantities, maybe even more useful than "all". I also kind of prefer the name "n-body" to "all" since it more prominently indicates that it's associated with particle data.</div><div><br></div><div>Please let me know if you have thoughts or suggestions about this proposal. I'm happy to draft a YTEP or update YTEP-0031 with more details if people want to see that.</div><span class="m_3168107345220518545m_-5319955312075545618HOEnZb"><font color="#888888"><div><br></div><div>-Nathan</div></font></span></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/lis<wbr>tinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
______________________________<wbr>_________________<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/lis<wbr>tinfo.cgi/yt-dev-spacepope.org</a><br></div></blockquote></div><br></div></div></div></div><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/lis<wbr>tinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_3168107345220518545gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Cameron Hummels<div><span style="font-size:12.8000001907349px">NSF Postdoctoral Fellow</span></div><div><span style="font-size:12.8000001907349px">Department of Astronomy</span></div><div><span style="font-size:12.8000001907349px">California Institute of Technology</span><br></div><div><a href="http://chummels.org" style="font-size:12.8000001907349px" target="_blank">http://chummels.org</a><br></div></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/<wbr>listinfo.cgi/yt-dev-spacepope.<wbr>org</a><br>
<br></blockquote></div><br></div></div>