unclear warning... about cmor

[durack1]

Can you point to the config, presumably on p and readable somewhere? It would be interesting to see the output and run CMOR with debugger statements on. @mauzey1 will likely know far more than I.

[gleckler1]

Everything needed to execute in repo dir or on gates via /home/gleckler1/git/obs4MIPs-cmor-tables/demo

python -i runCMORdemo_CMAP-V1902.py
output path would need to be changed for permissions. Using
cmor 3.7.3 py311hc372c84_0 conda-forge
xcdat 0.6.0 pyhd8ed1ab_0 conda-forge

[mauzey1]

That is a warning message that I have seen when not passing the number of time steps being written when using cmor.write. Although it does pass all of the data, it will say that no time steps were passed if you don't use the parameter ntimes_passed to pass the number of time steps. cmor.write is supposed to assume that all time steps are being passed if ntimes_passed is omitted when writing variables with time dimensions.

We'll need to set ntimes_passed to the size of the time dimension if it is omitted from cmor.write.

[gleckler1]

@mauzey1 Thank you for explaining this - problem solved!

[durack1]

@mauzey1 is this potentially an issue that we'll see now that cdms transientVariables are no longer the default objects being passed to CMOR? Just wondering if the documentation etc needs a tweak?