-
Notifications
You must be signed in to change notification settings - Fork 283
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
Athena "temperature" issue #2486
Comments
It seems that the issue is that multiplication in
to
fixes the issue! Only the first unit gets checked for a registry. A hotfix here would be to change to the second definition -- not sure if that's the long-term solution. |
(Also, thanks to @Xarthisius for figuring this out) |
I believe this is the same as what was happening in PR #2454. |
I think this is resolved upstream since yt-project/unyt#164 (included in unyt 2.8.0, which is the latest release to date and the minimal required version as of yt 4.0) |
There is something strange going on with athena's temperature field for the case that pressure does not exist on-disk.
Unfortunately, surfacing the specific error requires changing a line of source code. In
yt/fields/field_info_container.py
change line 47 as follows:Now, this script, using the MHD Blast wave sample dataset:
produces this strange error:
I genuinely can't figure out how to address this. Especially because, from what I can see, the unit registry should have
code_pressure
-- and in fact, if I just let it go without raising the error, it actually shows up inds.unit_registry
. I'm reluctant to say this is aunyt
issue as I fear that there's some order of operations issue I'm not seeing. Is it possible that this is occuring because of a different unit registry during field detection, that doesn't havecode_pressure
defined?The text was updated successfully, but these errors were encountered: