On Tue, Feb 4, 2014 at 7:54 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi all,

Lately, a lot of the yt-3.0 dev has been going on in the unitrefactor
domain.  Britton, John, Nathan and I (in alphabetical order :) have
been pushing pretty hard on getting things in order.  I've been trying
to keep things organized a bit by using Trello, which Sam showed me
and was pretty cool -- I'm not sure I can give out access to writing
to the boards to anybody, but I think the yt boards are all "public"
readable, and you can request write privs:

https://trello.com/b/yv7o0dTp/unit-refactor

Anyway, as an update, here's where we stand on unit refactor.

Big blockers:

 * MOAB, GDF, Pluto, Chombo frontends
 * A few remaining (minor) cosmology issues that Britton's just about
got finished and for which I owe some unit tests
 * Some discussion about metallicity units:
https://bitbucket.org/MatthewTurk/yt/pull-request/38/fixing-cgs-unit-conversions-for-angle-and
 * Docs haven't been copied in yet, but John Z has updated the
bootcamp to 3.0 (units) style.

Not to sound like a broken record, but have the docs covering the unit refactor, SPH smoothing, and all of the other new things in unit refactor been written?  Or are you just talking here about moving the yt-docs repository (which only covers yt 2.x) into the yt-3.0 branch of the yt repository?  I'm excited to use the new yt, but I just want to make sure I know how and it is clear how it all works under the hood.
 

I think that's ... just about it.  At some point, maybe not
*immediately*, we also want to get non-CGS units much, much easier to
set as the default.

So, the other thing -- we *just* landed (in unit refactor) SPH support
with smoothing fields.  More on this is forthcoming, but I'm pretty
pleased with where it is now, and best of all there's room for
improvement and optimization.

I'm going to be traveling a good amount the next couple weeks, but I
hope to be able to address the remaining blockers, and then we can
land the unit refactor in mainline yt-3.0 at some point after the
documentation is included.

We'll let that sit for a while, and then at some point the
"rebranding" PR (which will be more invasive technically, but *less*
invasive API-wise) can be issued, tested, and landed.  I actually
think it might be reasonable to get 3.0 out ... kind of soon-ish.

Anyway, if you want to test it out, grab the unitrefactor bookmark
from MatthewTurk/yt ; I'll update the PR into the main yt repository
as soon as these next couple PRs pass into my repo.

-Matt
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org



--
Cameron Hummels
Postdoctoral Researcher
Steward Observatory
University of Arizona
http://chummels.org