Open etiennesky opened 2 months ago
Thanks for the reports, Etienne.
Almost everything should be addressed in #61.
I am uploading a CO2_em_anthro
and a CO2_em_AIR_anthro
test file into /forcings/emissions/2024-07-01
to test whether that works for you (internet is not the best, could take a while).
Does not matter to us. I set them now to yearly full chunks consistently, ie. 360x180x25x1 in cdo-speak, since that was a simple rule. Please test if that is good enough or whether we need to manually set additional level and sector chunk sizes.
The level
coordinate variable did not have the bounds: "level_bnds"
attribute which confused cdo. Fixed.
xarray chose int for us automatically, since i guess int was good enough for the times we need to encode, but i forced it to double (even though i did not find anything in CF saying it should be double).
I don't understand what you mean by:
Also, time units are missing the 0:0:0 to be fully standard.
Currently our time:units
attribute is set to days since 2015-1-1 0:0:0
. Anything there to dislike?
Etienne, please test whether the new files work. Then we'll close the ticket. They finished uploading.
thanks @coroa I will test as soon as I get better (running on survival mode right now).
Sorry to hear. Thanks
when processing the latest CO2 emissions I have run into a few issues
compare this to one of the input4MIPS files
After running this command I was able to compute a global integral and vertical sum in much less time.
ncks -4 -h --cnk_dmn late,180 --cnk_dmn lon,360 --cnk_dmn level,13 --cnk_dmn time,1 CO2-em-AIR-anthro_input4MIPs_emissions_RESCUE_gn_201501-210012.nc.bak CO2-em-AIR-anthro_input4MIPs_emissions_RESCUE_gn_201501-210012.nc
if I add a
cdo -delvar,level_bnds
command before the processing, it works without problems.Also, time units are missing the 0:0:0 to be fully standard.