<div dir="ltr">In my work with the secretive enzo-BW (~1.5) data, I've always just defined my own derived field using creation time when I needed to check if a particle is a star. I don't recall using it in the ellipsoid parameter find. Not sure if Stephen used it in his halo finder, but I thought he made his own as well.<div>
<br></div><div>a quick grep in the source show it being used only in:</div><div><div>frontends/enzo/fields.py:def _IsStarParticle(field, data):</div><div>frontends/enzo/fields.py:add_field('IsStarParticle', function=_IsStarParticle,</div>
<div><br></div><div>But I don't know if others use this or not, and I don't know if I want to use it in the future if I implement dm or dm+star in ellipsoid halo calculations. So I'm with Nathan that it's probably better to fix if it's an easy fix.</div>
<div><br></div><div>From</div><div>G.S.</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 10, 2013 at 2:17 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 style="word-wrap:break-word"><div>Hey Britton,</div><div><br></div><div>I'd say -1</div><div><br></div><div>In principle we should be able to define boolean fields. If there's something about the way that handle fields that prevents that, we should fix it.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>-Nathan</div></font></span><div><div class="h5"><br><div><div>On May 10, 2013, at 2:13 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Ok, so we should probably remove that field from the code base since it is not really doing the right thing. It doesn't seem to be in use anywhere. Does anyone have any thoughts on removing this? +-1?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 10, 2013 at 4:49 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@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><div>On Fri, May 10, 2013 at 4:44 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I am seeing something odd with a field called "IsStarParticle". This is an<br>
> Enzo field defined in the following way:<br>
><br>
> def _IsStarParticle(field, data):<br>
> is_star = (data['creation_time'] > 0).astype('float64')<br>
> return is_star<br>
><br>
> When I do the following:<br>
> print pf.h.grids[0]['IsStarParticle']<br>
><br>
> I get the expected field of 1s and 0s.<br>
><br>
> When I do this:<br>
> all_data = pf.h.all_data()<br>
> print all_data['IsStarParticle']<br>
><br>
> I get the values that correspond to the creation_time field. It does not<br>
> matter in what order I do this. Whenever I try to access the field from a<br>
> geometric object, I get the actual creation time and not the field I expect.<br>
> Whenever I access it from a grid object, I get the right thing.<br>
><br>
> Does anyone know what's going on here?<br>
<br>
</div></div>No, not really. But there is one thing that I should note, which is<br>
that it may be getting caused by using "IsStarParticle" as a boolean<br>
index. Which would not work correctly, and would just return the 0th<br>
and 1st values of whatever array it's being used as an index into. I<br>
think.<br>
<br>
-Matt<br>
<br>
><br>
> Britton<br>
><br>
> _______________________________________________<br>
> yt-users mailing list<br>
> <a href="mailto:yt-users@lists.spacepope.org" target="_blank">yt-users@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-users mailing list<br>
<a href="mailto:yt-users@lists.spacepope.org" target="_blank">yt-users@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br>
</blockquote></div><br></div>
_______________________________________________<br>yt-users mailing list<br><a href="mailto:yt-users@lists.spacepope.org" target="_blank">yt-users@lists.spacepope.org</a><br><a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
yt-users mailing list<br>
<a href="mailto:yt-users@lists.spacepope.org">yt-users@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br>
<br></blockquote></div><br></div>