Charlie Zender

Yes, that would solve the version churn that I mentioned due to different OS's producing different ANTLR files. However, it would be a significant modification to the build system. And would need to be rock-solid in CMake (and preferably Autoconf too) before being adopted. Volunteers welcome :)

Hi Brett, Your interpretation of the role of antlr2 is correct. I am not a fan of the Antlr dependency either. I suppose NCO could bundle the Antlr files instead of building them from source. I think we did so 10+ years ago. It's also possible for you to fork NCO and experiment with generating a useful distribution with the Antlr files included. If you succeed and it seems portable we could merge your changes in from downstream. One problem I seem to remember from the old days is that different OS's...

That command will all the values in the snowfall variable. If the units of snowfall are absolute amounts per day (and not, e.g., rates per second each day) then the sum will be the total snowfall during the period.

First, Is the file that you are modifying a netCDF4 file or a netCDF3 file? I think the size increase is due to the underlying format. In netCDF4 it could be due to an inept chunksize. In netCDF3 it could be due to expanding the size of the record dimension. If time is the record dimension, then increasing it's size will allocate enough space to hold those extra records for every variable that includes the time dimension. Second, the "c" mode in your ncatted command requests "create" mode. This will...

In this first step we use ncwa to average-out the time dimension from the target variable (emi_co). We also extract it's spatial coordinates (which will not change) into a new file, out.nc. The -C prevent associated coordinate variables (like time) from being pulled into the output file. ncwa -a time -C -v emi_co,lat,lon in.nc out.nc In this second step we append the three time-containing coordinate variables from the original file to the output of the previous command. ncks -A -v date,datesec,time...

Every file needs to be the same shape, and have the same variables with your command. However MIROC-ES2L.nc, contains time_bnds but CanESM5-1.nc does not. Furthermore, CNRM-ESM2-1.nc is four times the resolution of CanESM5-1.nc. These files need to be regridded and regularized before they can be averaged.

Hello Again, I noticed you are at PNNL and work with E3SM colleagues so I bumped-up the priority of this feature. As of today and NCO 5.2.5-alpha03, ncclimo supports --exclude in timeseries mode. You can test the new executable in /global/homes/z/zender/bin_perlmutter/ncclimo. Please LMK how it works for you. Charlie

Hello Koichi, Thank you for brining this to my attention. Unfortunately this is an undocumented limitation of the --excludeoption for ncclimo, and there is no simple workaround. I just updated the manual to mention it. I have added removing this limitation to the general feature request list. However, it will require deep dive on my part. If your project is DOE or NASA-funded and this would be useful, then send me the details and I can prioritize it on the feature list. Charlie