Replies: 1 comment 1 reply
-
|
I hadn't thought about this. Presumably the same applies to converting between practical salinity and absolute salinity. I would think that map_from_native_model_vars and map_from_native_model_vars should take care of these as part of renaming variables. This would be clean because presumably the names on the Omega side (or at least the metadata) could also be made to reflect the conversion. Since (I would probably avoid calling this activity "remapping" because in my mind that term is reserved for interpolation from one grid or mesh to another, but that's beside the point.) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
MPAS-Ocean temperature is given as potential temperature whereas Omega (with nonlinear EOS) temperature is given as conservative temperature. Somewhere we need to convert one of these.
Should this be located in IOStep's write/read model dataset? This would mean that the remapped initial condition file would likely be given in potential temperature (and thus usable by both MPAS-O and Omega) and then Omega would do the conversion from potential to conservative temperature when writing its output files.
Beta Was this translation helpful? Give feedback.
All reactions