<div dir="ltr">Hi Mike,<br><br>On Friday, March 28, 2014, Michael Zingale <<a href="mailto:michael.zingale@stonybrook.edu" target="_blank">michael.zingale@stonybrook.edu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">I made a bit more progress here, but I get an error in <div><br></div><div>amr_kdtree/amr_kdtree.py<br></div><div><br></div><div>in line 257, it does</div><div><br></div><div><div> dds = grid.dds.ndarray_view()</div>
</div></div></blockquote><div><br></div><div>That line indicates that it should be a YTArray, or at least it is for the other frontends.<span></span></div><div><br></div><div>I've issued a PR for an alternate fix here: <a href="https://bitbucket.org/yt_analysis/yt/pull-request/779/ensure-griddds-is-a-ytarray-for-the-boxlib/diff">https://bitbucket.org/yt_analysis/yt/pull-request/779/ensure-griddds-is-a-ytarray-for-the-boxlib/diff</a></div>
<div><br></div><div>Thanks for the testing, I don't think the boxlib frontend has seen much use since we ported it to use the new field and unit system.</div><div><br></div><div>You might also be interested in fields.py in the boxlib frontend. You should be able to edit the tuples that define "known" on-disk fields to include the ones in your dataset. The tuples look like this:</div>
<div><br></div><div>("eden", (eden_units, ["energy_density"], None))<br></div><div><br></div><div>The format is the boxlib field name in the first entry, and then a three-element tuple in the second entry, containing the units of the field, a list of aliases to 'universal' yt fields defined in the yt.fields namespace (you can take a look at the field definitions in the yt/fields/ folder), and a display name. If the display name is None, plot labels will be automatically generated based on the field name.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>
</div><div><br></div><div>but grid.dds is already an ndarray, so this should be</div><div><br></div><div><div> dds = grid.dds</div></div><div><br></div><div>still not through the cam.snapshot() part of my script, but I got everything up to there working.</div>
<div><br></div></div><div><br><br><div>On Fri, Mar 28, 2014 at 4:23 PM, Michael Zingale <span dir="ltr"><<a>michael.zingale@stonybrook.edu</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>On Fri, Mar 28, 2014 at 3:37 PM, Nathan Goldbaum <span dir="ltr"><<a>nathan12343@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Mike,<div><br></div><div>You've hit a bunch of big changes we've been making recently. If you want to get back to the version of yt before we merged these big changes in, you'll need to update to the 'development' bookmark. Right now you're on the 'experimental' bookmark.</div>
<div><br></div></div></blockquote><div><br></div></div><div>Oh... lucky me.</div><div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div></div><div>
<br><div><div>On Fri, Mar 28, 2014 at 12:10 PM, Michael Zingale <span dir="ltr"><<a>michael.zingale@stonybrook.edu</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Is there any updated examples for using the yt 3.0 volume rendering?<div>
<br></div><div>For instance, looking at this:</div><div><br></div><div><a href="http://yt-project.org/docs/dev/cookbook/simple_plots.html#simple-volume-rendering" target="_blank">http://yt-project.org/docs/dev/cookbook/simple_plots.html#simple-volume-rendering</a></div>
</div></blockquote><div><br></div></div><div>We haven't finished updating the docs yet. In-development docs (including some out-of-date information that we need to update) are available here: <a href="http://yt-project.org/docs/dev-3.0/" target="_blank">http://yt-project.org/docs/dev-3.0/</a></div>
<div>
<div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div><br></div><div>The field name is no longer simply "Density", but now, for my data, I need to use a tuple like: </div><div><br></div><div><div><div>field = ('boxlib', 'magvel')</div></div></div>
</div></blockquote><div><br></div></div><div>We no longer have a 'Density' field, since this introduces ambiguities for Enzo data and to create a consistent naming scheme for fields. The new name is 'density'. See: <a href="http://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0003.html" target="_blank">http://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0003.html</a></div>
</div></div></div></blockquote><div><br></div></div><div>thanks for the list. Maestro has it's own fun with variables (two definitions for temperature, several pressures, etc., magvel above is not simply the vector magnitude of x_vel, y_vel, z_vel, etc), so I'll pay attention to these definitions.</div>
<div>
<div><br></div><div><br></div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div>
<br></div><div>And then when I look at the extrema, I no longer take the [0] index, as that just gives the min, but instead if I look at:</div><div><br></div></div></div></blockquote><div><br></div></div><div>That true, we've simplified the derived quantity API somewhat. This fixes a long-standing issue at the cost of breaking some old user scripts. As you can see we are planning to break backward compatibility somewhat for the final yt 3.0 release.</div>
<div>
<div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div></div><div>dd.quantities["Extrema"](field)<br>
</div><div><div>
<br></div><div>I get:</div><div><br></div><div>(124.858613718 dimensionless, 18061918.0546 dimensionless)</div></div></div></div></blockquote><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"></div></blockquote></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote>
</div>