You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may not be an actual issue, per se, but hopefully this will help center a conversation around some units and unit-handling for MIRGE-Com.
Currently, logging watches for built-in simulation quantities makes error messages like this:
/Users/mike/work/CEESD/MirgeCom/Drivers/CEESD-Shock1D/emirge/mirgecom/mirgecom/logging_quantities.py:289: UserWarning: Logging had to guess units for 'pressure': 'Pa'.It should not have to. Some other component should tell it.
warn(f"Logging had to guess units for '{quantity}': '{unit}'."
We need a way to indicate to the logger what the units are for this and also for user-defined quantities of interest.
This warning can be reproduced on mirgecom@logging by running the vortex-mpi.py example: python -m mpi4py examples/vortex-mpi.py
The text was updated successfully, but these errors were encountered:
This may not be an actual issue, per se, but hopefully this will help center a conversation around some units and unit-handling for MIRGE-Com.
Currently, logging watches for built-in simulation quantities makes error messages like this:
We need a way to indicate to the logger what the units are for this and also for user-defined quantities of interest.
This warning can be reproduced on
mirgecom@logging
by running thevortex-mpi.py
example:python -m mpi4py examples/vortex-mpi.py
The text was updated successfully, but these errors were encountered: