Mailman 3 June 2021 - yt-dev

YTEP-0040: a yt-baked colormap package
by Clément Robert 16 Jul '21

16 Jul '21

Hi yt-dev ! I wrote a small YTEP to propose that yt’s native colormaps be isolated into a lightweight independent package. See the motivation therein https://github.com/yt-project/ytep/pull/20 Although the priority for doing this is pretty low, I do think some form of change is required in this area, following the upstream change of behaviour introduced in matplotlib 3.4 Considering the task itself is also reasonably small and straightforward, I assume it is reasonable to submit it now so it may be considered for yt 4.0 (plus, I couldn’t resist submitting a 40th YTEP on Matt’s 40th birthday). A minimal goal here would be to improve our documentation to showcase the 7 (6 ?) original cmaps from the yt community. Namely: - algae - arbre - dusk - kamae - kelp - octarine - (spectral) -> this one seems to be currently broken actually, or was it just renamed ? See https://github.com/yt-project/yt/issues/3165#issuecomment-822241839 If we agree to bake a separate package out of them, I would also like to give credit to their respective creators. I know that Nathan came up with “arbre”, but I don’t know who created the other 6 (5). Please share your knowledge, I’m interested in knowing this whatever the fate of this YTEP :) Cheers Clément

3 4

draft yt-4.0 release PR log
by Matthew Turk 29 Jun '21

29 Jun '21

Hi folks, (Sending this here because we've been discussing it on Slack but I want to make sure nobody missed out.) In prep for an impending/very-very-soon release, I've drafted up a release list of PRs that I *think* went into yt-4.0. I generated this by running the gh command line and getting *everything* that targeted "main" (which was after yt-3.6 was released), everything that targeted "master" after April 13, 2020 (which was when yt 3.6 was released; this may include some 3.6.1 stuff) and everything that targeted yt-4.0 as a branch. I think this may have let some other PRs slip, because we used other repositories for a while, but it should be reasonably complete. This is not the "changelog" but it is the list of PRs. https://gist.github.com/matthewturk/7a1f21d98aa5188de7645eda082ce4e6 Feel free to engage here on the list or on the gist with any suggested changes. I'm working on now on the narrative changelog with high-level changes listed, which I'm basing on: https://github.com/yt-project/yt/blob/c4d693f099d450fe4d4cd22223c70f1368989… -Matt

1 0

IMPORTANT: DELAY of Managing Mischief Week!
by Stephanie Tonnesen 02 Jun '21

02 Jun '21

Dear all, I apologize, but after my email yesterday the steering committee discussed and decided that right now we are *this close* to the yt-4.0 release, and rather than give a Managing Mischief week half our attention and enthusiasm we should postpone. Therefore, *Managing Mischief week is NOT happening next week*. We really want this virtual yt MM week to be a success, and hopefully give us something to work off of for future yt-hack weeks, so it *will* happen this summer, just not in June. Please hang on to your excitement about this, and we will let you know well in advance of the rescheduled dates. And...get excited for the yt-4.0 release, coming soon! Thank you all for your understanding and patience, Stephanie (for the yt steering committee) -- Dr. Stephanie Tonnesen Associate Research Scientist CCA, Flatiron Institute New York, NY stonnes(a)gmail.com

1 0

Managing Mischief NEXT WEEK!
by Stephanie Tonnesen 01 Jun '21

01 Jun '21

Dear yt-ers! Next week is our first attempt at a completely virtual yt hack week, so we hope you can join in to make it a success! *The goal of this week is "Managing Mischief"--This is when we want dead code, code styling, and other PRs both submitted and merged. We can take a look at YTEPs that have been waiting for our attention as well!* This is a pretty open-ended week, with the goal being to push through these refactoring-type PRs. If you want to be involved, but aren't sure where to start, some of the steering committee will be "on-call" throughout the week on slack so you can ask them what people are working on, or who to ask to take a look at the PR you are working on. We are letting this be self-driven, so if you and someone else are hashing out something and want to zoom, go for it! If slack and github messaging are getting the job done, stick with that! If you want a third mind on a call/github discussion to help out, ask! *Let's try using the #development channel for most of this discussion on slack. *Post here the PRs you are working on so others can join in! Post here your questions about code style! Post here your frustration that you can't pass that last fido test! *So you know you are not alone, here is when we will definitely be online thinking yt thoughts. *These are NOT comprehensive (you may get a response very quickly outside of these times!), but you can expect a quick response during these days and times: Monday (June 7): 12 pm - 2pm UTC: Matt Turk and Britton Smith 6 pm - 8 pm UTC: John ZuHone and Cameron Hummels Tuesday (June 8): 1 pm - 3 pm UTC: Matt Turk and Britton Smith 6 pm - 8 pm UTC: Matt Turk and John ZuHone Wednesday (June 9): 2 pm - 4 pm UTC: Britton Smith and John ZuHone Thursday (June 10): 3 pm - 4 pm UTC: Matt Turk and Britton Smith 4 pm - 5pm UTC: Matt Turk and John ZuHone Friday (June 11): 2 pm - 3 pm UTC: Matt Turk and John ZuHone 7 pm - 8 pm UTC: Matt Turk and John ZuHone Can't wait to hack away next week! --Your friendly neighborhood yt steering committee -- Dr. Stephanie Tonnesen Associate Research Scientist CCA, Flatiron Institute New York, NY stonnes(a)gmail.com

1 0