Mailman 3 January 2016 - yt-dev

PR Triage Hangout (New Time!)
by Hilary Egan Jan. 19, 2016

Jan. 19, 2016

Hi everyone, This spring's PR Triage Hangouts will be at *12pm EST every Wednesday*. Here's the link to the next hangout, and let me know if there are any problems with this time. https://plus.google.com/b/107728486871834552760/events/cr17uqi688edbscsae41… -- Hilary Egan Astrophysical and Planetary Science Department University of Colorado Boulder _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

2 1

Issue #1160: Analysing GIZMO output by using yt (yt_analysis/yt)
by Ka Hou Leong Jan. 19, 2016

Jan. 19, 2016

New issue 1160: Analysing GIZMO output by using yt https://bitbucket.org/yt_analysis/yt/issues/1160/analysing-gizmo-output-by-… Ka Hou Leong: I have analysed some GIZMO test problems by using yt .I found a weird situation.In two particular test problems, yt can identify gas, but can't read the date of gas correctly. In the others test problems, yt can identify and read the date of gas correctly.The situation is strange as it may sound. It seem like a bug. The following is the problem list : … [View More]

1 0

Some updates from AAS
by Matthew Turk Jan. 17, 2016

Jan. 17, 2016

Hi folks, I wanted to write a quick email about some neat things that I heard about at AAS. The coolest one was that, on the heels of their announcement that software papers (of any length) would be welcome in AAS journals, the AAS is going to be making it possible for some articles to feature updating author lists. These author lists would be tied in to ADS as well. What this would mean is that future software and instrument papers can have authors added to their list, which will be … [View More]

2 1

Future of the install script
by Nathan Goldbaum Jan. 16, 2016

Jan. 16, 2016

I've changed the subject line to avoid derailing the other thread. On Friday, January 15, 2016, Matthew Turk <matthewturk(a)gmail.com> wrote: > Hi Nathan, > > (I'll reply to Andrew a bit later once I've thought it over.) > > I'd strongly campaign against unifying the two scripts right now, if > ever. I don't like that we have two either, but I don't think we > should make this part of the 3.3 release cycle, just because it's yet > another major potential … [View More]disruption. It would be nice to work out a > way to migrate nicely to conda, but maybe we should hold off until we > have infrastructure in place for our own conda package builds? What do we do about people who want to install on the latest versions of OSX? What about clusters that have older SSL installs? Right now our solution is to tell people about get_yt.sh when they complain on the mailing list, but I wouldn't be surprised if we're missing people who give up after getting errors. Why do we need our own package builds? What about simply linking to get_yt.sh on the website? > > On Thu, Jan 14, 2016 at 5:20 PM, Nathan Goldbaum <nathan12343(a)gmail.com > <javascript:;>> wrote: > > > > > > On Thu, Jan 14, 2016 at 1:45 PM, Andrew Myers <atmyers2(a)gmail.com > <javascript:;>> wrote: > >> > >> Dear yt developers, > >> > >> yt version 3.2 was released back in July of 2014. Since then, there > have a > >> been a number of cool new features added (good work, everyone!), and it > >> would be nice to get them into a stable release. However, there are a > few > >> major things that need to be done before that can happen. First, there > are a > >> number of outstanding issues related to the volume render refactor that > need > >> to be addressed before 3.3 can be released. Additionally, version 3.3 > will > >> include unstructured mesh visualization support, and there is some more > work > >> Matt and I need to do before that is ready. Other than those things, > though, > >> is there anything I'm leaving out that people want to get in before > version > >> 3.3 is released? > > > > > > I would like to see the install script situation resolved. In > particular, I > > think get_yt.sh and install_script.sh should be merged, and users > > should be able to choose at install time whether or not they want a > > source-based install or a miniconda-based install. > > > >> > >> > >> Thanks for your time, > >> Andrew > >> > >> _______________________________________________ > >> yt-dev mailing list > >> yt-dev(a)lists.spacepope.org <javascript:;> > >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > >> > > > > > > _______________________________________________ > > yt-dev mailing list > > yt-dev(a)lists.spacepope.org <javascript:;> > > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > > > _______________________________________________ > yt-dev mailing list > yt-dev(a)lists.spacepope.org <javascript:;> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org [View Less]

4 6

jetbrains licenses
by Matthew Turk Jan. 15, 2016

Jan. 15, 2016

Hi folks, we finally got the JetBrains licenses. Ping me off list to get one. We have 10. _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

1 0

What needs to be done for a 3.3 release?
by Andrew Myers Jan. 15, 2016

Jan. 15, 2016

Dear yt developers, yt version 3.2 was released back in July of 2014. Since then, there have a been a number of cool new features added (good work, everyone!), and it would be nice to get them into a stable release. However, there are a few major things that need to be done before that can happen. First, there are a number of outstanding issues <https://bitbucket.org/yt_analysis/yt/issues?q=%5Bexperimental%5D> related to the volume render refactor that need to be addressed before 3.3 can … [View More]

5 6

Testing infra update
by Kacper Kowalik Jan. 14, 2016

Jan. 14, 2016

Hi, I've revamped the way we handle PR testing. We no longer poll Bitbucket repository every 'n' minutes, instead we're utilizing webhooks [1]. It also means that testing and docs building should happen almost immediately. Whole thing is implemented as a simple web server [2] that runs on fido and listens for POST messages coming from Bitbucket. It allows for fine grained control over code executed upon different events i.e. pr creation, update, merge can be treated separately. As result we … [View More]

2 1

IPython dependency in the install script
by Nathan Goldbaum Jan. 14, 2016

Jan. 14, 2016

Hi all, With the release of Jupyter, the number of dependencies necessary for the IPython notebook has exploded somewhat. I just created a new virtualenv and did "pip install jupyter". The output of "pip freeze" for this virtualenv is pasted here: http://paste.yt-project.org/show/6141/ As you can see, jupyter brings in a large number of python packages, and it would be a real pain to manually install all of these in the install script. This is coming up because I'm in the middle of updating … [View More]

3 3

"Overdensity" in yt 2.x and 3 and the Enzo Dark_Matter_Density field
by Josh Moloney Jan. 13, 2016

Jan. 13, 2016

For the past couple of days I've been trying to figure out halo profiles and virial radius calculations in yt, which so far has mostly consisted of trying to understand the differences in the "Overdensity" field between yt versions. The biggest difference is due to yt-2.x using an incorrect redshift scaling for the overdensity calculation. The field is defined as Matter_Density / (rho_crit_now * data.pf.hubble_constant**2 * (1 + data.pf.current_redshift)**3) which scales the critical density … [View More]

3 3

Fwd: Imgur API v1 and v2 Deprecation Notice
by Matthew Turk Jan. 13, 2016

Jan. 13, 2016

Hi folks, What fortuitous timing! Kacper has recently deployed a cool new image pastebin, which we can switch "yt upload_image" to use. But, if anyone wants to update the code to work with v3 of the imgur API, that would also work to keep yt up to date. ---------- Forwarded message ---------- From: Imgur API <api+deprecate(a)imgur.com> Date: Mon, Jan 11, 2016 at 5:40 PM Subject: Imgur API v1 and v2 Deprecation Notice To: matthewturk(a)gmail.com Hi Imgur API user! It looks like you’… [View More]

2 1