I’d like to raise awareness on a small but recuring issue we’ve been having with how CI interacts with Github auto-merge.
As a reminder, auto-merge is a GH feature with allows us to set a PR to be merged automatically after configurable requirements are met.
The issue with our current configuration is that the “answer test” job is required, but does not always turn. In particular it doesn’t run on docs-only PRs.
This creates a situation where the PR is stuck on a “wait” status, and only repo owners can merge.
The latest example is https://github.com/yt-project/yt/pull/3963
I can see two solutions:
- update the requirements to exclude this particular job (or make it conditional ? I’m not sure that’s supported)
- change the rules and run normal CI even on docs-only PRs
Is there a preference ?
Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable.
2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17
I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
yt 4.0.4 is out !
This is a bugfix release. Most notably it fixes (future) compatibility with matplotlib 3.6, as well as a couple minor bugs.
It is available on PyPI and conda-forge. See the release notes for how to upgrade https://github.com/yt-project/yt/releases/tag/yt-4.0.4
Happy data crunching
I just got through reviewing @neutrinoceros's work on refactoring how norms
and colorbars are handled: https://github.com/yt-project/yt/pull/3849
A lot of effort went into it and it'd be great to get merged before it goes
stale. Anyone want to give it a look? Even if you don't have the bandwidth
to dig in too deeply, just checking out the branch and making some plots
using the new functionality would be useful and appreciated!
If I don't hear any responses (and if there are no objections), I'm
planning to go ahead and merge it next ~Tuesday -- if you **do** want to
review the PR but won't have time before then, send me a note and I'll hold
off and give more time for review.
Hi team !
Ronan Hix has successfully developed a new frontend for CHIMERA over the course of several months. A substantial amont of work went into it and it’s a very impressive first contribution.
It’s also a significant undertaking to review, but it’d be really nice to get eyes on it so we can get it in.
Here’s the pull request https://github.com/yt-project/yt/pull/3638
Any help would be appreciated, feel free to also submit partial reviews if you’d like to
Hi yt team !
Chris implemented a long requested API for swapping/flipping plot axis in https://github.com/yt-project/yt/pull/3640
I wanted to bring your attention to it because the patch, while moderately substantial, is likely intimidating to reviewers.
I just gave my own approval after months of back and forth with Chris, and I believe the implementation is now robust enough for inclusion.
I believe the API is mostly uncontroversial, _except_ for one aspect that we want to resolve before the next feature release, and for which a discussion is open, see
If we can’t find another reviewer, and if no one objects, I would like to merge this PR in a week or so, so we can move on to resolve the remaining question as a separate, second step.
Please let us know if you have any concerns with the PR, if you would like some more time to review it, or if you object having it merged with just my approval.
I'm writing to share with you a job posting to work at the University
of Illinois in the School of Information Sciences developing yt and
working on community-centric issues. In practice, this would mean
working on things related to getting yt and dask to play more nicely
together (which Chris Havlin is also working on), working on bridging
yt with other domains of study beyond astronomy, trying to make yt
easier (and more fun) to use, and helping to grow the yt community.
You would be welcomed to Champaign-Urbana, but this position can also be remote.
This posting is very similar in spirit to one I shared in 2020 -- the
position may be particularly interesting to individuals looking to
transition to industry, as well as those who are interested in
pursuing jobs in academia that are more focused on research software.
This job is posted as part of the School of Information Sciences, but
it's within a research group that spans the National Center for
Supercomputing Applications (NCSA), the Astronomy department, the
Institute for Genomic Biology, Materials Sciences, and other groups
and institutes on campus.
This position will also provide ample opportunities for
interdisciplinary work with academics, the open source scientific
software ecosystem (SciPy, PyData, etc) and for travel and
professional development. You'd get to work with folks involved in yt
and you'd get to have a hand in developing and designing some really
fun tools for data analysis and visualization.
Please do reach out to let me know if you have any questions about the
opportunity, and if you know anyone you think might be interested, it
would be very helpful if you could pass this information along to
Announcing yt 4.0.3 !
This is a bugfix release, all users are recommended to upgrade.
It includes a critical bugfix for particle data analysis, as well as a ~20 bug fixes, most notably for 2D plotting and loading RAMSES data.
It is available on PyPI as well as conda-forge.
See the Github release notes for more: https://github.com/yt-project/yt/releases/tag/yt-4.0.3
Clément for the yt dev team
Headsup: In order to facilitate downstream packaging, we’re dropping the unmaintained `toml` library as a dependency and switching to tomli + tomli_w instead
See https://github.com/yt-project/yt/pull/3830 for context and https://github.com/yt-project/yt/pull/3831 for the change.
This may break your dev env if you don’t have these packages installed already, so beware that you may need to fix that soon when you pull from yt’s main branch.
yt is working with NumFOCUS <http://numfocus.org> on a research project
funded by the Gordon & Betty Moore Foundation <https://www.moore.org/> to
understand the barriers to participation that contributors, particularly
those from historically underrepresented groups, face in the open-source
software community. The research team would like to talk to new
contributors, project developers and maintainers, and those who have
contributed in the past about their experiences joining and contributing to
Interested in sharing your experiences?
Please complete this brief “Participant Interest
<https://numfocus.typeform.com/to/WBWVJSqe>” form which contains additional
information on the research goals, privacy, and confidentiality
considerations. Your participation will be valuable to the growth and
sustainability of diverse and inclusive open-source software communities.
Accepted participants will participate in a 30-minute interview with a
research team member.
*Please do volunteer if you can--we would like yt to be as welcoming and
diverse as possible, and this is a really great way we can work on our
Dr. Stephanie Tonnesen
Associate Research Scientist
CCA, Flatiron Institute
New York, NY