On Friday I'll be holding "yt office hours" at 9:30AM Central (10:30AM
Eastern, 3:30PM GMT). I'll announce the URL on Slack in #general just
beforehand, but the stream will *probably* be at
twitch.tv/powersoffour . If you have questions about yt, or want to
get your feet wet developing or see how code review and whatnot
happens, please stop on by!
I've started using org-level projects to collect and organize work.
The first one I started up was for stretched grids:
Please feel free to add items, play with this functionality, and so
on. One neat thing about it is that we can link issues across
The steering committee has discussed the current state of yt, where
things are and where they are going, and talked through various
strategies for moving forward effectively.
Where we're at right now is that many of the maintainers have been
timesliced quite a bit; this often results in bursts of activity,
which is then not followed up, and a long delay between (for instance)
pull requests being issued, being looked at, and issues being
responded to. Additionally, the thing that seems *really* lacking,
which needs to be addressed, is that the decision making process for
the community isn't entirely obvious -- not so much in terms of the
rules, but of what is being worked on, who's working on things, and
how to engage.
I've been somewhat less engaged with the project than I'd like lately,
and part of that has been situational (teaching, family, pandemic
overhead) and some of it has been that I've been trying to engage at
the project level without stepping on any toes *and* to try to
contribute code. The upshot was that neither was really happening!
So, after discussion with the steering committee, we've decided that
the best way forward for now is for me to step into a "project
manager" role. What this means is that I'll be taking on a much more
active daily role in yt. This will include being the first point of
contact for new issues and pull requests, being more assertive about
"assigning" issues to individuals (with the knowledge that they may
decline!), applying labels, editing issues for clarity and so on, and
also stewarding and managing the review process.
This also means that I'll be more engaged in public planning of
projects and utilizing the project management systems provided by
Github. We've long thought these were worth using, but where we ended
up was that in the absence of a consensus (or a lazy consensus) we
tended not to utilize new things for fear that they would go unused or
that others would not approve, or whatever. Additionally, we have in
place a structure for governance. But, this structure isn't
self-enforcing, and it will be in this role that I will work to ensure
we're following the guidelines, processes and structures we have
enumerated in our governance documents.
Finally, I'll be taking on the problem of holding and running
"meetings" and drop-in office hours. I have also been thinking about
ways of providing weekly updates on activity in the project for folks
who may have unsubscribed from the repo or who find the overall
communication volume to be not-quite-right.
But, all of this text aside, the proof will be in the actual *doing*
of things, and I look forward to *doing* things and being more vocal
The 4.0.2 milestone is currently complete !https://github.com/yt-project/yt/milestone/18
I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time.
I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history.
Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ?
Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ?
Hello yt folks !
We’re getting close to the next bugfix release, with 61 PRs merged to the yt-4.0.x branch since yt 4.0.1 was released.
There are a couple more that could use a review, most of which should be easy to review. You can get an overview of what’s left in the milestone
For this one bugfix in particular I would really appreciate a technical review, because it requires a change in the testing framework itself
This particular PR happens to be important to me because figures with height > width are extremely common when plotting data in spherical coordinates, something my group uses a lot.
Beyond these, I’ll defer to you guys, and our release manager in particular, to decide when the actual release should happen.
Have a good day!
Sorry I accidentally responded to Micheal only, here’s my response
> Begin forwarded message:
> From: Clément Robert <clement.robert(a)protonmail.com>
> Subject: Re: [yt-dev] Supporting arbitrary grid schemes ?
> Date: 20 October 2021 at 17:04:12 CEST
> To: Michael Zingale <michael.zingale(a)stonybrook.edu>
> Interesting. I think yt already has some support for these, though I admit I’ve never seen it used outside of (failed) image tests, so here’s one I was able to find on my computer.
> Does this fall into the “mapped grid” catagory ?
> Indeed what I want to support in the context of my current team is probably a subset of these “logically rectangular” grids. My teams uses rectilinear grids, but we stil have orthogonality everywhere.
>> On 20 Oct 2021, at 15:41, Michael Zingale <michael.zingale(a)stonybrook.edu> wrote:
>> here's an example of some simple mapped grids that are used in astro:
>> it sounds like what you are describing is a restricted version of a general mapped grid.
>> On Wed, Oct 20, 2021 at 9:31 AM Clément Robert via yt-dev <yt-dev(a)python.org> wrote:
>>> I don’t know ! Where can I find a definition for these ?
>>>> On 20 Oct 2021, at 13:52, Michael Zingale <michael.zingale(a)stonybrook.edu> wrote:
>>>> It's this similar to mapped grids?
>>>> On Wed, Oct 20, 2021, 5:33 AM Clément Robert via yt-dev <yt-dev(a)python.org> wrote:
>>>>> Hi folks
>>>>> As you may be aware, yt’s grid based index classes offer support for patched-based AMR as well octrees, but it’s currently lacking support for so called “stretched gridding scheme”. This is a known limitation in several existing frontends (AMRVAC, BoxLib, Chombo-Pluto are the ones I know of).
>>>>> For context, what I refer to as “stretched grids” are grids where cell sizes are not simple powers of 1/2 (with respect to a unitary reference) as in classic AMR and octrees, but may be specified by arbitrary rules (such as geometric series). Some hydro code support having parts of the grid following classic AMR scheme and other blocks to be “stretched” along one or several directions at once. This is the case of AMRVAC and Pluto, for instance. BoxLib also has support for complex refinement rules that are not covered by storing a single `refine_by` integer as we’re currently doing in Index classes (this is https://github.com/yt-project/yt/issues/3481).
>>>>> It seems to me that the “easy” way of supporting these data formats would be to generalise yt’s mechanisms for reconstructing cell position and size (currently it’s using cell index, domain edges, refinement level + a `refine_by` multiplier) so that cell edges can be stored as arrays that frontends would need to somehow retrieve from datafile or reconstruct from parameter files.
>>>>> There’s been some effort in the past to get over this limitation led by John and Matt, and we’ve been hitting this wall from time to time in discussions.
>>>>> Now, I understand that this would most likely not be a trivial change, especially because we don’t want to break existing frontends in the process (or performance !), and at the moment, I don’t have a very clear idea of what exact steps are needed to achieve this goal, and in particular I don’t have enough material to draft a YTEP on the topic.
>>>>> It seems clear we’d need *some* refactoring/generalisation of Index classes and friend classes and new pixelizer routines would likely be needed. Anything else ?
>>>>> I however have personal motivation to move forward here since my team is developing an hydro code and running simulations where grid streching is the rule rather than the exception.
>>>>> What I would like to do to get us rolling is simply collect the existing issues and PRs related to this goal. I know there are a couple, but it’s very easy to loose track of them, and it’s hard to see the big picture.
>>>>> Can I create a label (“arbitrary grids” ?) and apply it to existing material touching this topic ?
>>>>> Do you know of existing PRs and issues that are relevant to this topic ?
>>>>> Here are the ones I know:
>>>>> - https://github.com/yt-project/yt/issues/3481
>>>>> - https://github.com/yt-project/yt/pull/2998
>>>>> - https://github.com/yt-project/yt/issues/1880
>>>>> - https://github.com/yt-project/yt/issues/385 (from 2012 !!)
>>>>> yt-dev mailing list -- yt-dev(a)python.org
>>>>> To unsubscribe send an email to yt-dev-leave(a)python.org
>>>>> Member address: michael.zingale(a)stonybrook.edu
>>> yt-dev mailing list -- yt-dev(a)python.org
>>> To unsubscribe send an email to yt-dev-leave(a)python.org
>>> Member address: michael.zingale(a)stonybrook.edu
>> Michael Zingale
>> Professor of Physics and Astronomy
>> Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800
>> phone: 631-632-8225
>> e-mail: michael.zingale(a)stonybrook.edu
>> web: [https://zingale.github.io](https://zingale.github.io/)
>> github: [https://github.com/zingale](http://github.com/zingale)
Hi yt community!
I just heard about this meeting being held this upcoming May 2022 at the
CCA about open source development practices. I think many of us might be
interested! If so you can sign up to get updates about the meeting.
We are planning a workshop focused on topics in open source software
development practices for astronomy, held in person at the Center for
Computational Astrophysics in New York City, May 16–20, 2022. The program
and scope are still in development, but we expect it to be of interest to
astronomers with a wide range of open source experience, and across all
career stages. The schedule will include a large fraction of unstructured
time for participant-driven discussion, collaboration, and co-working.
For more information about this workshop and to sign up to hear more
details as they become available, please check out our website at
Please share this email with your department lists and/or anyone else who
you think might be interested in participating in this event.
(on behalf of the organizing committee)
Associate Research Scientist, Flatiron Institute
I am self-nominating myself to temporarily move to the fallow fields
for my development and community work in the yt-project. I would like to be
doing more in the project but I am not able to commit to the level I'd like
to, and I'd like to notify the community of my absence. In the interim, I
have asked Kacper (@Xarthisius) to be release manager for the project and
he has agreed.
Happy development everybody. I look forward to positively contributing in