-
Notifications
You must be signed in to change notification settings - Fork 0
Update io_hdf5 for HDF5 1.14 #139
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
Conversation
Print errcode Add all the debug from Chat GSFC Fix fortran Fix double close Clean up debug prints Use v110 libver? Reorder for comparison ease Bring back old program Fix up program Fixes for types Remove accidental file Longer file names Add debug prints Try simple open More tries Try verbose checkcode More tests updates from Chat GPT 5 Remove debug prints
|
@weiyuan-jiang has kindly undertaken a full suite test for this. |
|
Well, huh. @weiyuan-jiang did a run for me and: The fact that a CONUS run changed makes me think it's something else instead of this PR? |
@mathomp4 : The non-0-diff results are for "agg". I doubt they matter. I can spot-check to confirm they're the usual roundoff. Was the test run using the new baselines plus the new h5? Or just the new h5? |
@gmao-rreichle It should just be the hdf5 updates, see GEOS-ESM/GEOSldas#833 which I guess I can close now...or rather should have not opened? I'm new to GEOSldas GC PRs. :) I am just now in the process of issuing new Baselibs, etc. but that'll be a longer term process since I need to build them up in places. |
|
@mathomp4 : Sorry for the silly question about h5 vs. new baselibs, I just looked it up myself. I'm about to have a few meetings, I'll check the diffs as soon as I can. It's a bit odd that the code changes in io_hdf5.F90 would create non-0-diff results even for "agg", but if the diffs are roundoff (TBC), I think it'll be ok to merge |
Oh, not silly. I sort of had to go check to make sure myself. I was doing a lot of testing and I really don't want some temporary baselibs getting into a model :) |
|
Mystery solved... The "agg" comparisons fail only for the "ldas_catparam" file. This file contains time-invariant model parameters and is generated in pre-processing. For the most part, the parameters are read from somewhere and immediately written out into the "ldas_catparam" file without any calculations. But one field ("cdcr1") involves a calculation. There's a roundoff diff in this calculation when the test is run on Cascade Lake and the baseline was run on Milan. I'll go ahead and merge the PR. |
This PR updates
io_hdf5.F90to support HDF5 1.14. Testing showed that between HDF5 1.10 (in current baselibs) and HDF5 1.14 (in GEOSgcm v12 Baselibs) something changed in how you need to open/close/etc. HDF5 files.In my limited testing (Intel conus and global), this PR seems to be zero-diff with the current Baselibs and as such, can be dribbled in now before updating Baselibs.
I'll keep draft until a full suite test can be made.