NetCDF error

[Jay Zhu]

Hi all,

I would like to run a case for BSSP585cmip6 compset with f19_g17.

When I submit this case, the case stop with following message:



It happened when open the file ozone_strataero_WACCM_L70_zm5day_2015-2100_SSP585_c190529.nc

what should I do to fix this bug?

Any help would be greatly appreciated!

Jay

 

[erik]

Hmmm, it's not completely clear that's what's at issue here. But, I would use 'ncdump -k" to make sure that file is NOT in NetCDF-4 format to start with. I'd also make sure you can just read it using "ncdump -h". Since this is a file read in by CAM, I would make sure you check the atm.log file as well as the cesm.log file.

It also matters exactly what CESM version you are working with, and if you've made any code modifications to it. It's good to be successful with a simpler case before you move onto the case that you actually want to run. So you might try a simpler comset/resolution before you move up to the case you want to run. So first try an I compset, then an F, before moving to the B compset.

 

[Jay Zhu]

Hmmm, it's not completely clear that's what's at issue here. But, I would use 'ncdump -k" to make sure that file is NOT in NetCDF-4 format to start with. I'd also make sure you can just read it using "ncdump -h". Since this is a file read in by CAM, I would make sure you check the atm.log file as well as the cesm.log file.

It also matters exactly what CESM version you are working with, and if you've made any code modifications to it. It's good to be successful with a simpler case before you move onto the case that you actually want to run. So you might try a simpler comset/resolution before you move up to the case you want to run. So first try an I compset, then an F, before moving to the B compset.

Hi Eric,

Thanks for your reply. Following your advice, the file is "classic" using "ncdump -k" and can be read using "ncdump -h". In addition, no problem occur when I run f09_g17 resolution. I had the same problem when running default BSSP585 compset.

In the attachment, I added the log file and took the screenshot of the problem part.

Thanks!
Jay