-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating Firefly-dependent areas to match API changes and PyPI packaging #4143
Conversation
Current version of Firefly is 3.2.0. These seem to be the only changes necessary to convert to the new python API. (API changes seem to mostly be a relabeling of parameter fields, plus velocities is elevated to a separate field. )
When installed from PyPI (e.g. using pip install firefly), the firefly module is brought in as lower-case.
Hi! Welcome, and thanks for opening this pull request. We have some guidelines for new pull requests, and soon you'll hear back about the results of our tests and continuous integration checks. Thank you for your contribution! |
Removed excess whitespace to make flake8 happy.
pre-commit.ci autofix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Clément Robert <cr52@protonmail.com>
Followed approach used in yt/data_objects/image_array, since as far as I can tell, datadir is just the new name of JSONdir (because data files are now generally .ffly instead of .json).
Fixes to the actual function call documentation that I missed earlier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
follow up comments on the deprecated API part
Co-authored-by: Clément Robert <cr52@protonmail.com>
Co-authored-by: Clément Robert <cr52@protonmail.com>
Additional kwargs passed to create_firefly_object are passed unchanged to the firefly.data_reader.Reader initialization.
Co-authored-by: Clément Robert <cr52@protonmail.com>
So, I am only just now tuning in. I am traveling until next Monday 10/3 and won't have a chance to formally review this until then. @mtryan83, first of all, thank you for putting all of this together! from your original PR summary this seems like exactly the sort of changes that I've had on a to-do list to do since we updated the API and submitted the Firefly paper so I am in your debt for handling it. It's been hard to follow the updates to the PR since then, has it all mostly been yt documentation stuff? Is there something in particular I should pay close attention to (it sounds like you covered all the bookkeeping stuff like switching JSONDIR and |
No rush on our side !
AFAICT there's nothing we'd want to clean up upstream. |
I think the main thing is just making sure I updated the API correctly. From what I could tell, it was just I don't see anything to clean up upstream either. Looks like I missed a JSONdir though, @neutrinoceros, sorry! |
For later reference, I previously triaged this for the 4.1 milestone, but I'm going to take it back, because that release is already far behind schedule. I would still be happy to include the patch in the release if we can get a second review in time, which seems likely, I just want to signal that the patch shouldn't be considered blocking. |
# Conflicts: # setup.cfg
(fast-cache and updated firefly dependencies were touching! Couldn't automerge anymore) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look great to me, thank you @mtryan83 for cleaning all this up with the new API. I'm hoping that I won't be compelled to change it again any time soon now that we have the .ffly format (which is what inspired most of the changes).
Hooray! Congratulations on your first merged pull request! We hope we keep seeing you around! 🎆 |
PR Summary
This PR aims to reconcile the changes to Firefly introduced since version 4.0.0 of yt was released. In summary, Firefly tweaked the
Reader
andParticleGroup
APIs and the installation of Firefly from PyPI installs asfirefly
(instead ofFirefly
orFirefly-vis
, the devs were able to get control of the package name). I've updated the documentation, including that (I believe) Firefly also now prefers their binary.ffly
format.I'm very new to Firefly and yt, so I would greatly appreciate it if e.g. @agurvich would double check.
I believe this counts as a fix/update for #3415
PR Checklist