On Mon, May 1, 2017 at 4:06 PM, Joseph Smidt <josephsmidt@gmail.com> wrote:
I just wanted to say, even though I never commit to the repository so probably shouldn't respond to a dev email :), that you guys are amazing.  YT has probably saved the average person who uses it *years* of analysis time, and the ease at which you have transitioned to a platform without drama is equally impressive. It also has made it so that every year I have summer students, they can produce results on day one which is worth its weight in gold. 

The only mistake I think you have made over the years is to have drinken the maplotlib koolaid and adopted a default colorscale that looks like a green version of greyscale. But I realize this koolaid involves the superiority you feel when reduce the eye to a linear algebra system (like any good nerdish koolaid should) and so I not going to debate the point other than to say: you guys are amazing.  You have saved the world countless hours and have made the barrier to entry such that nobody need waste any time. 

Just a comment: If you don't like the default yt colormap you can configure it in your yt configuration file:

http://yt-project.org/doc/reference/configuration.html#the-configuration-file

using the default_colormap configuration option. The name of the old default is "algae". We switched away from algae because it is not perceptually uniform.
 

So here's to a long and wonderful future via github.



On Mon, May 1, 2017 at 2:50 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi Britton,

Thanks for taking this on.  I think this is a great idea, and really happy to see you doing it!

-Matt

On Mon, May 1, 2017 at 4:48 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,

Now that yt development has moved to github, I want to bring up an opportunity for some smaller yt-related development projects.

As some of you may know, it was decided a couple months ago that most of the code in the analysis_modules directory will be moved to various external repositories to allow them to be developed separately from the main yt codebase.  The rough timeline for this is to have all analysis modules marked as deprecated by the release of yt-3.4 and fully removed (and in a separate, pip-installable repo) by yt-4.0.

The initial extraction of the analysis modules has now been done and can be found here:

To be clear, the analysis modules are still present in yt, but this repo contains only those modules.  The revision history has also been maintained.  Anyway, there are a number of small tasks that must be completed before this package becomes the replacement for yt's analysis modules.  I will begin adding issues on github for all these.  If anyone is interested in helping out with this, just come talk to me on the yt slack channel or feel free to just dig in and start issuing PRs.

Thanks!
Britton

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


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

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