<div dir="ltr">Sorry - not sure which issue you're talking about - this one maybe?<div><br></div><div><a href="https://bitbucket.org/yt_analysis/yt/issue/827/enzo-particle-fields-work-differently-than">https://bitbucket.org/yt_analysis/yt/issue/827/enzo-particle-fields-work-differently-than</a></div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 10:02 AM, 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">Related to that, do you have a reproducible script for the particle<br>
issue you reported? If so, could you add that to either an issue or a<br>
trello card so I can work on it?<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Jun 24, 2014 at 11:58 AM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
> I'd be +1 on this plan, although we should note that this is the plan in the<br>
> release announcement. We may also want to note that there are some issues<br>
> with volume rendering of oct and particle data at the moment (I believe<br>
> that's the case - let me know if I'm wrong there).<br>
><br>
> I think that leaves analysis modules and documentation as the main blockers<br>
> for a 3.0 release.<br>
><br>
> -Nathan<br>
><br>
><br>
><br>
> On Tue, Jun 24, 2014 at 9:53 AM, John ZuHone <<a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a>> wrote:<br>
>><br>
>> +1 on Matt's proposal. -1 on a beta.<br>
>><br>
>> My worry about a beta release is that it will slow adoption, whether<br>
>> rightly or wrongly. I think we agree that we're ready to encourage adoption<br>
>> of 3.0.<br>
>><br>
>> John ZuHone<br>
>> Laboratory for High-Energy Astrophysics<br>
>> NASA/Goddard Space Flight Center<br>
>> 8800 Greenbelt Rd., Mail Code 662<br>
>> Greenbelt, MD 20771<br>
>> (w) <a href="tel:301-286-2531" value="+13012862531">301-286-2531</a><br>
>> (m) <a href="tel:781-708-5004" value="+17817085004">781-708-5004</a><br>
>> <a href="mailto:john.zuhone@nasa.gov">john.zuhone@nasa.gov</a><br>
>> <a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a><br>
>><br>
>> > On Jun 24, 2014, at 12:38 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>> > wrote:<br>
>> ><br>
>> > I think Britton covered the halos, but the VR works as-is. As far as<br>
>> > 3.0beta, I'm a bit nervous about that as we want to avoid the<br>
>> > situation where we are in beta for 1+ years... I am worried about the<br>
>> > perception of a "beta" tag. Is that overblown? Would calling it<br>
>> > "yt-3.0-2014" work?<br>
>> ><br>
>> >> On Tue, Jun 24, 2014 at 10:32 AM, Nathan Goldbaum<br>
>> >> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>> >> Do the old VR and halo interfaces work? Not much effort has gone into<br>
>> >> porting them, I think.<br>
>> >><br>
>> >><br>
>> >>> On Tuesday, June 24, 2014, Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> I'm +1 on this, particularly since I'm at fault for not pushing on the<br>
>> >>> VR<br>
>> >>> as much as I'd like to.<br>
>> >>><br>
>> >>><br>
>> >>> On Tue, Jun 24, 2014 at 7:44 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>>><br>
>> >>>> Hi all,<br>
>> >>>><br>
>> >>>> One thing we really tried to do with 3.0 was break all the APIs we<br>
>> >>>> thought we'd need to before release. This included things like<br>
>> >>>> ds/pf,<br>
>> >>>> index/hierarchy, the way data selections were made, etc.<br>
>> >>>><br>
>> >>>> It's starting to become clear that we are approaching maturity at<br>
>> >>>> different rates in these initiatives. I am wondering if perhaps we<br>
>> >>>> should de-couple the release from all of the API breakages, and<br>
>> >>>> instead note which interfaces we know are going to change in the<br>
>> >>>> future.<br>
>> >>>><br>
>> >>>> Pragmatically, what this would mean is:<br>
>> >>>><br>
>> >>>> * Release a 3.0 with the old VR and halo finding interfaces<br>
>> >>>> * Release a 3.1 with either the new VR or the new halo finding (or<br>
>> >>>> both)<br>
>> >>>> * Do the same for 3.2<br>
>> >>>><br>
>> >>>> This doesn't fit with the usual "major numbers are where APIs break"<br>
>> >>>> philosophy that comes from semantic versioning, but I think from the<br>
>> >>>> perspective of pragmatism, if we identify those sections of the code<br>
>> >>>> that are *going* to change, and we pitch 3.0 as the first part of a<br>
>> >>>> staged release of totally rewritten infrastructure, we can likely<br>
>> >>>> come<br>
>> >>>> out okay.<br>
>> >>>><br>
>> >>>> I'd like to put this out there for discussion.<br>
>> >>>><br>
>> >>>> -Matt<br>
>> >>>> _______________________________________________<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" 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">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>
>> > 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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
><br>
> _______________________________________________<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" 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">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>