Closed aekiss closed 5 years ago
Actually all of the bld/config.nci.auscom.*
data is also in the output file ice/ice_diag.d
so would be much easier to read from there.
we can also pick up these from ice/ice_diag.d
No. of categories: nc = 5
No. of ice layers: ni = 4
No. of snow layers:ns = 1
instead of bld/build.sh
setenv NICELYR 4 # number of vertical layers in the ice
setenv NSNWLYR 1 # number of vertical layers in the snow
setenv NICECAT 5 # number of ice thickness categories
ice/ice_diag.d
also has a lot of timing info we should harvest
This is tricky, as it is determined at compile-time.
We'd probably need to maintain a (say, yaml) cache file indexed by cice exe name that contains the data from the
bld/config.nci.auscom.*
script for that hash and resolution. This data in turn would need to be obtained by (say) downloading that script from github (e.g. https://raw.githubusercontent.com/COSIMA/cice5/123hash456/bld/config.nci.auscom.3600x2700), running it, and reading the resulting environment variablesNTASK
,RES
,NXGLOB
,NYGLOB
,BLCKX
,BLCKY
.We could also use the same approach to get data from
bld/build.sh
master script, though we'd want to trim off the actual compilation part before running it.