-
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
Commit a8b395e prevents dark matter-only Enzo simulations from being analyzed #3809
Comments
Hi, and welcome to yt! Thanks for opening your first issue. We have an issue template that helps us to gather relevant information to help diagnosing and fixing the issue. |
Thank you for reporting this regression with such care, pinning the exact commit the problem bisects to and providing a usable dataset for reproduction. I assume for now that this reveals a bug in the Enzo frontend, so I'm going to triage it as such. I'll take a deeper look soon. |
Awesome! Thanks! |
@anchwr thank you so much for reporting! I think a fix for this should go into 4.0.3. @brittonsmith I wanted to CC you on this just to make sure you saw it. |
@matthewturk Unless I'm mistaken this bug only appeared on the main branch so far (#3433) so there's no need to backport a fix to 4.0.x |
@neutrinoceros good catch |
Bug report
Bug summary
As of commit a8b395e, yt appears to fail with dark matter-only Enzo simulations as soon as frontends.enzo.fields.setup_energy_field() is called (e.g., via ds.all_data() or ds.add_particle_filter()). These simulations do not have an explicit energy field, so an error is triggered at line 278 of frontends/enzo/fields.py, since ('enzo', None) is not a valid field name.
Code for reproduction
Sample dataset that generates error at: http://use.yt/upload/35be3369
Actual outcome
Expected outcome
This shouldn't usually produce any output. As far as I can tell, it works on commits prior to a8b395e
Version Information
yt installed from source
The text was updated successfully, but these errors were encountered: