OASIS abort if too high RUNTIME value - Correction #32
Labels
bug
Something isn't working
Milestone
Comments
alexis-barge
changed the title
alexis-barge
added a commit
that referenced
this issue
Oct 31, 2024
|
Done with #37 |
alexis-barge
added a commit
that referenced
this issue
Dec 6, 2024
* generalize arch dir lib * add eophis container * Workflows to build container images * remove arm64 build * generalize * Eophis amd container (#31) * add eophis container * Workflows to build container amd64 image * rm compiler flags * cleaner make.gnu * installation from container * Update install.rst * Solve issue #32 (#37) * increase version * error messages if runtime too high * unit tests for is_in and find_pos * clone release and not main * Update apptainer_eophis.def * replace fake earth by toy earth * add tutorial material and documentation * add reference to tutorial * install matplotlib in apptainer * fix wrong script name * move tutorial in tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OASIS parser is limited to 8 digits numbers when reading exchanges frequencies.
If defining STATIC exchanges with RUNTIME bigger than 8 digits, OASIS will read truncated values. Leading to synchronicty errors.
For instance:
Correction : raise an error from Eophis if STATIC frequency is too high. Error tells user to lower ITER*DT and run several segments instead , or not to use STATIC exchange, or to upgrade to at least v1.1.x.
preprod mode : check and raise error in namcouple._finalize --> -1 STATIC and RUNTIME known
prod mode : during make_and_check() --> RUNTIME known from read namcouple and STATIC are spotted for check
The text was updated successfully, but these errors were encountered: