Breaking change re: legacy data files in r34120
2 views
Skip to first unread message
Rhys Ulerich
Oct 23, 2012, 6:09:43 PM10/23/12
to suze...@googlegroups.com
Hi all,
For https://red.ices.utexas.edu/issues/2579 within r34120 I introduced
a breaking change in the restart file format.
The change was moving from "/rhoe" to "/rho_E", "/rhou" to "/rho_u",
etc. Keeping the notation exact for the samples I'm cooking for APS
is worthwhile so that they match the model document. It's a minor
consistency nit, but not one that's easy to fix in a backwards
compatible way so it made sense to kill it now.
The details are in the log message of commit r23120, including how to
upgrade any existing fields using the new postproc/rename_hdf5.py
utility built atop h5py.
- Rhys
For https://red.ices.utexas.edu/issues/2579 within r34120 I introduced
a breaking change in the restart file format.
The change was moving from "/rhoe" to "/rho_E", "/rhou" to "/rho_u",
etc. Keeping the notation exact for the samples I'm cooking for APS
is worthwhile so that they match the model document. It's a minor
consistency nit, but not one that's easy to fix in a backwards
compatible way so it made sense to kill it now.
The details are in the log message of commit r23120, including how to
upgrade any existing fields using the new postproc/rename_hdf5.py
utility built atop h5py.
- Rhys
Reply all
Reply to author
Forward
0 new messages