<div dir="ltr">Hi Matt,<div><br></div><div>The change you suggested solved the problem of</div><div>ad['DarkMatter', 'particle_mass']</div><div>and</div><div>ad['CenOstriker', 'particle_mass']</div>
<div><br></div><div>However, when I do:</div><div>ad['all', 'particle_mass']</div><div>I get the following:</div><div><br></div><div><div>Traceback (most recent call last):</div><div> File "<stdin>", line 1, in <module></div>
<div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/data_objects/data_containers.py", line 189, in __getitem__</div><div> self.get_data(f)</div><div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/data_objects/data_containers.py", line 535, in get_data</div>
<div> particles, self, self._current_chunk)</div><div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/geometry/geometry_handler.py", line 507, in _read_particle_fields</div><div> fields_to_read)</div>
<div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/utilities/io_handler.py", line 176, in _read_particle_selection</div><div> rv[field_f][my_ind:my_ind + vals.shape[0],...] = vals</div><div>
ValueError: could not broadcast input array from shape (4851) into shape (4361)</div></div><div><br></div><div>Additionally, if I do:</div><div>ad['io', 'particle_mass']</div><div>I get this (which I got before this change as well):</div>
<div><div>Traceback (most recent call last):</div><div> File "<stdin>", line 1, in <module></div><div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/data_objects/data_containers.py", line 183, in __getitem__</div>
<div> f = self._determine_fields(key)[0]</div><div> File "/Users/britton/Documents/work/yt/yt-x86_64/src/yt-hg/yt/data_objects/data_containers.py", line 406, in _determine_fields</div><div> raise YTFieldTypeNotFound(ftype)</div>
<div>yt.utilities.exceptions.YTFieldTypeNotFound: Could not find field 'io'.</div></div><div><br></div><div>Britton</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 2, 2013 at 3:54 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks, Matt! I'll check this now and do so it if looks like it's working right.<span class="HOEnZb"><font color="#888888"><div>
<br></div><div>Britton</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 2, 2013 at 3:52 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">Hey Britton,<br>
<br>
I just dug into it briefly, and it looks like the particle types for<br>
active particles are not being "set up" the way they ought to be. I<br>
think the issue is that particle_types_raw was not being set<br>
correctly. Adding this line:<br>
<br>
self.particle_types_raw = self.particle_types<br>
<br>
on line 855 of enzo/data_structures.py fixed it for me. Can you<br>
double-check the values, compare "io" to "DarkMatter" (they should be<br>
identical) and if that looks good to you, submit a PR?<br>
<br>
-Matt<br>
<div><div><br>
On Mon, Dec 2, 2013 at 10:45 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> Since we've closed the final pull requests, I've now made the<br>
> repository yt_analysis/yt-3.0 read-only.<br>
><br>
> If you issue pull requests, please do make sure you issue them from a<br>
> named branch to the same named branch; bitbucket seems keen on merging<br>
> across branches lately. :)<br>
><br>
> -Matt<br>
><br>
> On Thu, Nov 28, 2013 at 9:57 AM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>> wrote:<br>
>> Hi all,<br>
>><br>
>> After some discussion on the dev mailing list, we've decided to unify<br>
>> the repositories for yt-3.0 and yt. It will still be located in a branch<br>
>> called<br>
>> yt-3.0 in that repository. At some point in the near future the separate<br>
>> yt-3.0 repository will become read-only.<br>
>><br>
>> This simply means that if you are using yt normally, from the repository<br>
>> here:<br>
>><br>
>> <a href="http://bitbucket.org/yt_analysis/yt" target="_blank">http://bitbucket.org/yt_analysis/yt</a><br>
>><br>
>> you will be able to switch to the yt-3.0 branch more easily. And, if<br>
>> you currently have a fork of the repository yt-3.0, you'll need to<br>
>> switch to using a fork of the main yt repository. This is easy, just<br>
>> fork the main yt repo (unless you already have!) and push your yt-3.0<br>
>> changes there.<br>
>><br>
>> Just as it has always been, installing the "stable" and "development"<br>
>> versions<br>
>> from the install script will still only put you on the latest stable and<br>
>> development<br>
>> versions of yt-2.x. Additionally, doing "yt update" will not accidentally<br>
>> switch<br>
>> you from one version to the other.<br>
>><br>
>> Happy Thanksgiving!<br>
>><br>
>> Britton and the yt development team<br>
>><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>
_______________________________________________<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>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>