Hi all,
I'm in the middle of putting together a changelog for the upcoming 3.1
release.
Just in case anyone needs to do this in the future, I've put together a
quick script that interacts with the bitbucket REST API to generate a
summary of all merged pull requests since the release of yt 3.0 on August
4th.
The script is here: https://bpaste.net/show/f86b1b4c0326
My plan now is to use the output of this script to manually create a
changelog for the docs and release announcement.
Hope that's helpful,
-Nathan
New issue 969: Metallicity values reported by LightRay in 3.0 significantly differ from metallicity values in 2.x
https://bitbucket.org/yt_analysis/yt/issue/969/metallicity-values-reporte...
Cameron Hummels:
I've run into an insidious bug in the LightRay analysis module, wherein metallicity values reported along the light ray in yt 3.0 differ by an OOM with metallicity values reported along the light ray in 2.x. Strangely enough, temperature values between the two versions don't change at all, and density values only change at the <1e-4 level.
I have investigated this to some degree and it appears that the bug is confined to the LightRay analysis module, as I'm seeing the same metallicity values for raw ``Ray`` and other data objects between the two versions of yt.
The following scripts demonstrate this problem with the enzo_cosmology_plus dataset. Because of the way in which the LightRay object operates, you'll need to run these scripts *inside* the enzo_cosmology_plus directory.
For yt-2.x, run this script in the enzo_cosmology_plus directory:
http://paste.yt-project.org/show/5323/
With the resulting output:
```
#!python
Density: [ 9.97279296e-32 9.20237619e-31]
Temperature: [ 1706.254685 75236.83753987]
Metallicity: [ 4.96203366e-09 4.62205944e-09]
```
For yt-3.0, run this script in the enzo_cosmology_plus directory:
http://paste.yt-project.org/show/5324/
With the resulting output:
```
#!python
Density: [ 9.97278399e-32 9.20236791e-31]
Temperature: [ 1706.254685 75236.83753987]
Metallicity: [ 1.01225503e-10 9.42900276e-11]
```
Hey everyone,
I've seen a lot of PRs get merged in the last few days. So I guess we're
gearing up for a 3.1 release? What is the plan for its release?
I advocate for having a wait time where no PRs get merged for a while
before we release to sort out bugs. I'm personally somewhat hesitant about
using yt tip right now for production level analysis after all of those
merges, many of which didn't appear to have much review. It was my
understanding that we were going to wait to let the dust settle on some
things when everyone was back at their desks next week.
Either way, I wanted to see what the status of things were with all of the
recent activity, since I hadn't heard anything on the list.
Cameron
--
Cameron Hummels
Postdoctoral Researcher
Steward Observatory
University of Arizona
http://chummels.org
