yt-dev

yt-dev@python.org

2527 discussions

[ANN] yt 4.1.2
by Clément Robert 19 Nov '22

19 Nov '22

Announcing yt 4.1.2 ! This is a bugfix release with no new features, all users are encouraged to upgrade. See the release notes for details https://github.com/yt-project/yt/releases/tag/yt-4.1.2 Clément, for the yt dev team

1 0

What's new in Python 3.8 (digest)
by Clément Robert 21 Oct '22

21 Oct '22

Hi all, yt 4.2 (current main branch) has officially dropped support for Python 3.7 While this is mainly done to reduce technical debt, it also means we can now start using Python 3.8+ syntax, so I wanted to highlight a couple things from the “What’s new in Python 3.8” page, to get everyone on the same page. FTR this isn’t me campaigning to modernise all the things, but it’s always nice to have access to a larger subset of what Python can do :) - Assignment expressions, aka “walrus operator” https://docs.python.org/3/whatsnew/3.8.html#assignment-expressions In some places, using `:=` makes for shorter code without sacrificing readability. I find it really shines when binding a variable that’s immediately going to be tested in an `if/else` block, for instance. - Positional-only parameters: https://docs.python.org/3/whatsnew/3.8.html#positional-only-parameters Though rarely useful, making arguments positional-only means we don’t have to commit to non-meaningful names forever (looking at you, `yt.load(fn=…)`) - “debug fstrings” https://docs.python.org/3/whatsnew/3.8.html#f-strings-support-for-self-docu… Python 3.8 makes fstrings even nicer and more useful ! - new features for the `typing` module https://docs.python.org/3/whatsnew/3.8.html#typing We now have easy access to `typing.Final` (declare that a variable should be considered constant and not be assigned to), and `typing.TypedDict`, which allows to mark dictionaries as having an exact set of keys with known types. These have no effect at runtime but are very useful in making sure the code is correct at type-check time with mypy (e.g, am I rebinding a varname that was suppposed to be constant ? Did I forget a key in my return dict, or does it have an unexpected type ?) Cheers ! Clément

1 0

Expiring deprecations and dropping 3.7
by Matthew Turk 20 Oct '22

20 Oct '22

Hi all, I'd like to merge https://github.com/yt-project/yt/pull/4101 https://github.com/yt-project/yt/pull/4106 The first should be relatively non-problematic, as it is dropping a fairly old version of Python (3.7). The second is an expiration of some deprecations. I've marked them as approved, but I'd like someone else to also review and considering pushing the button. The second one in particular is more likely to cause disruption, although all the deprecations have been in place for some time. -Matt

1 0

ANN: yt 4.1.1 is available
by Clément Robert 18 Oct '22

18 Oct '22

yt 4.1.1 is out ! It fixes a couple important bugs that were discovered after the 4.1.0 release, including the octree memory leak recently discussed on the user mailing list. See the release notes on github for details : https://github.com/yt-project/yt/releases/tag/yt-4.1.1 Happy analysis! Clément, on behalf of the yt team

1 0

ANN: yt 4.1.0 is available
by Clément Robert 07 Oct '22

07 Oct '22

yt 4.1.0 is out ! This release represents more than a year worth of work form 30 contributors, and contains many improvements as well as new features. See the release notes on github for details : https://github.com/yt-project/yt/releases/tag/yt-4.1.0 Happy analysis! Clément, on behalf of the yt team

1 0

Proposal for a roadmap to yt 4.1
by Clément Robert 28 Sep '22

28 Sep '22

Hi team 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 Best Clément

2 6

REQ: Help yt cite your papers
by Matthew Turk 13 Sep '22

13 Sep '22

Hi everyone, tl;dr: tell us how to cite your yt-using papers at https://forms.gle/Vkvab2RXLf8oTp3z6 For the last few years, we've been working on a paper about yt-4.0, and the updates since the last paper was published over a decade ago. I've dragged my feet on it a little bit, but I'm hoping that over the next few months the last bits can be written up, polished, and the paper submitted. (See the end of this email for authorship information on the paper!) The current "build" of the paper is here: https://yt-project.github.io/yt-4.0-paper/ with a repository at github.com/yt-project/yt-4.0-paper/ . The paper isn't *yet* complete... which is where this email comes in! I've been trying to collect a somewhat representative set of references to the papers that describe or utilize yt for different simulation platforms. There are two types of citations that we're trying to track down -- citations that describe the simulation platform (i.e., the "method paper" that talks about the code) and those that use yt to analyze data output by the simulation platform (i.e., maybe you wrote a paper and used yt). To make this easy, I've made up a google form: https://forms.gle/Vkvab2RXLf8oTp3z6 If you are able to take a minute and submit a couple references to your work or work you know about that used yt, it would be very, very helpful! And as for the paper itself, we're preparing an email inviting authorship to anyone who has had changes committed into the yt repository, but the authorship policy for the paper is by design very inclusive and described here: https://github.com/yt-project/yt-4.0-paper#authorship-policy . If you have contributed, you are likely going to receive this email, but if you are certain you would like to be included, please follow the instructions in that link to see how to be added to the manuscript. Thanks very much, Matt

1 0

Dropping support for Python 3.7
by Clément Robert 01 Sep '22

01 Sep '22

Hi team - With the recent addition of Python 3.11 to the set of versions we actively support, we now have five (3.7 to 3.11). - [NEP 29](https://numpy.org/neps/nep-0029-deprecation_policy.html) , to which yt complies, only requires supporting “at least two” different versions at any given point, and recommends dropping 3.7 after December 21 (2021 !). - Many important dependencies (including numpy and matplotlib) are already requiring Python 3.8 or newer. - [recent history](https://pypistats.org/packages/yt) indicates that Python 3.8 is by far the version yt is most downloaded with (via PyPI) With all this considered, I believe it is now reasonable to propose dropping Python 3.7. It’s probably okay that we keep providing binaries for it throughout the upcoming yt 4.1.x release series, but I would like to start requiring Python 3.8 starting with yt 4.2, assuming everyone’s okay with that. Let me know if you have any questions or arguments against it. If not, I’ll start working on a patch targeted to yt 4.2 Cheers, Clément

2 1

ANN: yt 4.0.5 is out
by Clément Robert 11 Aug '22

11 Aug '22

Fresh bugfix batch is out of the oven: announcing yt 4.0.5 ! We strongly recommend upgrading if you're using yt to analyse SPH data. See the release notes for details https://github.com/yt-project/yt/releases/tag/yt-4.0.5 Happy analysis ! Clément

1 0

Enzo-E v1.0 Announcement
by Matthew William Abruzzo 01 Jul '22

01 Jul '22

We are pleased to announce the v1.0 release of Enzo-E, a new parallel adaptive mesh refinement magnetohydrodynamics code. Enzo-E is based on Cello, a highly scalable, fully-distributed array-of-octree parallel adaptive mesh refinement (AMR) framework, and Enzo-E is a scalable branch of the original Enzo parallel astrophysics and cosmology application that has been ported to use Cello. Enzo-E’s parallel scalability is enabled by Charm++ (https://charmplusplus.org/), an advanced parallel runtime system developed at the University of Illinois. A short paper describing Enzo-E can be found here <https://ui.adsabs.harvard.edu/abs/2018arXiv181001319B/abstract>. Features include: - Three HD/MHD solvers: PPM, PPML, VL+CT - Self gravity with a multigrid Poisson solver - Collisionless particles - Cosmological evolution - A wide range of star formation and sink algorithms - Scalable HDF I/O - Radiative cooling and chemistry via connection to the Grackle package Source code repository: https://github.com/enzo-project/enzo-e Documentation: http://enzo-e.readthedocs.io/ Cello was written by James Bordner and Enzo-E includes contributions from: Matthew Abruzzo Stefan Arridge James Bordner Thomas Bolden Greg Bryan Vanesa Diaz Andrew Emerick Forrest Glines Ryan Golant Nathan Goldbaum Buket Benek Gursoy Philipp Grete William Hicks Michael Norman Claire Kopenhafer Brian O’Shea Molly Peeples John Regan Dan Reynolds Wolfram Schmidt Britton Smith Jason Tumlinson Matthew Turk Saoirse Ward Sophie Wenzel-Teuber John Wise Enzo-E / Cello has benefitted from the following funding sources in reverse chronological order. - NASA TCAN 80NSSC21K1053 (PI: Peeples; Co-PIs: Bryan, Norman, O’Shea, Wise) - Irish Research Council New Foundations Scheme (2019; PI: Regan) - NSF OAC-1835402 (PI: Norman; Institutional PIs: Bryan, O’Shea, Wise) - NSF SI2 SSE-1440709 (PI: Norman) - NSF PHY-1104819 (PI: Norman) - NSF AST-0808184 (PI: Norman)

1 0

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

yt-dev