<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 3, 2017 at 4:10 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra">Ah, I see, this is covered in YTEP-0003:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><a href="http://ytep.readthedocs.io/en/latest/YTEPs/YTEP-0003.html#molecular-and-atomic-species-names" target="_blank">http://ytep.readthedocs.io/en/<wbr>latest/YTEPs/YTEP-0003.html#<wbr>molecular-and-atomic-species-<wbr>names</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">And what Lauren wants to use in yt-3 is the "H_nuclei_number_density" field. Except now that I check, we don't have that field at all, we only have 'H_nuclei_density'. I'll submit a pull request that adds the number density field automatically, but for now Lauren is going to need to define her own nuclei number density field.</div></div></div></blockquote><div><br></div><div>And it looks like ('gas', 'H_nuclei_density') *is* a number density after all:</div><div><br></div><div>In [3]: ds.fields.gas.H_nuclei_density</div><div>Out[3]: Derived Field (gas, H_nuclei_density): (units: cm**(-3))</div><div> </div><div>This is a tad annoying because the naming scheme here is inconsistent with the naming scheme of the other species fields.</div><div><br></div><div>So that's the field you want to use Lauren. Hope my flailing around here over the course of this thread wasn't too confusing :)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><br></div><div class="gmail_extra">Apologies for the noise about bugs!</div><span class="gmail-HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">-Nathan</div></font></span><div><div class="gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 3, 2017 at 4:06 PM, 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Nathan,<div><br></div><div>This is not a bug. I will dig up the reference when I can, but at some point it was decided that X_density should alias to X_p0_density, for whatever X is. Actually, I believe that this may go all the way back to when this naming convention was decided upon, and it was actually the other way around. X_density was originally designated to be the neutral density of element X, and sometime later X_p0 was added as an alias of this. I'll look to see if I can find the exact references for when this happened.</div><span class="gmail-m_2620557804805464206gmail-HOEnZb"><font color="#888888"><div><br></div><div>britton</div></font></span></div><div class="gmail-m_2620557804805464206gmail-HOEnZb"><div class="gmail-m_2620557804805464206gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 3, 2017 at 2:01 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Lauren,<div><br></div><div>Thanks for the detailed report. It was very straightforward to reproduce what you're seeing using one of the test cosmological datasets on <a href="http://yt-project.org/data" target="_blank">yt-project.org/data</a>.</div><div><br></div><div>I'm pretty sure you've stumbled across a bug in the way species fields are set up for Enzo.</div><div><br></div><div>Here's what's happening:</div><div><br></div><div>In yt-2, the field "H_NumberDensity" corresponds to the number density of all hydrogen ion species (i.e. HI + HII number density).</div><div><br></div><div>In yt-3, for some reason, ('gas', 'H_number_density') represents the number density of just HI ions. To get what you had before, you'd need to defined a new field which sums ('gas', 'H_number_density') and ('gas', 'H_p1_number_density').</div><div><br></div><div>The following IPython session illustrates the issue:</div><div><br></div><div><div>In [10]: ds.fields.gas.H_density</div><div>Out[10]: Alias Field for "('enzo', 'HI_Density')" (gas, H_density): (units: g/cm**3)</div><div><br></div><div>In [11]: ds.fields.gas.H_p0_density</div><div>Out[11]: Alias Field for "('gas', 'H_density')" (gas, H_p0_density): (units: g/cm**3)</div><div><br></div><div>In [12]: ds.fields.gas.H_p1_density</div><div>Out[12]: Alias Field for "('enzo', 'HII_Density')" (gas, H_p1_density): (units: g/cm**3)</div></div><div><br></div><div>Right now ('gas', 'H_density') is an alias to ('enzo', 'HI_Density'), and ('gas', 'H_p0_density') is an alias to ('gas', 'H_density'). I'm pretty sure that's wrong, ('gas', 'H_p0_density') should be an alias to ('enzo', 'HI_Density') and ('gas', 'H_density') should be a derived field formed by summing HI_density and HII_density.</div><div><br></div><div>Now, I'm pretty sure this is a bug, but I also don't normally with with Enzo multispecies data, so I'd like some confirmation about this from others who are more experienced with cosmological enzo data before I make a pull request.</div><span class="gmail-m_2620557804805464206gmail-m_6705963789870409785HOEnZb"><font color="#888888"><div><br></div><div>-Nathan</div></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-m_2620557804805464206gmail-m_6705963789870409785h5">On Fri, Mar 3, 2017 at 2:44 PM, Lauren Corlies <span dir="ltr"><<a href="mailto:laurennc009@gmail.com" target="_blank">laurennc009@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_2620557804805464206gmail-m_6705963789870409785h5"><div dir="ltr">Hello,<div><br></div><div>I've been a yt user for a while now but have recently noticed something concerning. A few months ago, I made the switch to yt3 and am currently using the new yt 3.3.4</div><div><br></div><div>I've been working with recently generated, cosmological zoom in simulations and I've generated a basic yt ray object. When I plot the hydrogen number density along the ray, the values that it's generating are un-physically low (<a href="http://i.imgur.com/1C1oAVr.png" target="_blank">seen here</a>). </div><div><br></div><div>It's especially concerning because when I use the old yt2 installation:</div><div><font face="verdana, sans-serif">Version = 2.7-dev</font></div><div><font face="verdana, sans-serif">Changeset = 1f9ca06815d0</font></div><div><br></div><div>and generate a yt ray object with the exact same trajectory, the hydrogen number density values are much more sensible (<a href="http://i.imgur.com/tcDcNd8.png" target="_blank">seen here</a>). The rays in both yt versions have mostly the same shape but there are some strong features in the yt2 version than in the yt3 one. </div><div><br></div><div>The discrepancy is specifically with this field and not other intrinsic fields like temperature or regular density (also attached). </div><div><br></div><div>Am I accessing the field incorrectly and there's a better way to get these values with the new version of yt? Or is there something deeper happening? The hydrogen number density is particularly important for the ion densities and emission that I've been interested in.</div><div><br></div><div>All of the plots and the <a href="http://paste.yt-project.org/show/7066/" target="_blank">script</a> to generate them are attached and posted online as described on the docs page, tagged with my last name with links included as an attachment.</div><div><br></div><div>Thanks for the help,<br>Lauren Corlies</div><div><br></div><div><br></div><div><br></div><div><br></div></div>
<br></div></div><span>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/lis<wbr>tinfo.cgi/yt-users-spacepope.o<wbr>rg</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/lis<wbr>tinfo.cgi/yt-users-spacepope.o<wbr>rg</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/lis<wbr>tinfo.cgi/yt-users-spacepope.<wbr>org</a><br>
<br></blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div></div>