Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Isotope historical files are in NetCDF-4 format need them in NetCDF-3 or NetCDF-5 #734

Closed
ekluzek opened this issue May 24, 2019 · 1 comment · Fixed by #883
Closed

Isotope historical files are in NetCDF-4 format need them in NetCDF-3 or NetCDF-5 #734

ekluzek opened this issue May 24, 2019 · 1 comment · Fixed by #883
Assignees
Labels
priority: high High priority task to fix soon, e.g., because it is a problem in important configurations type: enhancement new capability or improved behavior of existing capability
Milestone

Comments

@ekluzek
Copy link
Contributor

ekluzek commented May 24, 2019

Brief summary of bug

@jedwards4b found that two files are in NetCDF-4 format and can't be read on the Korean system he is working in...

"I'm trying to run f09_g17.B1850cmip6 on the korean system using the 2.1.1 release candidate and am having trouble reading the files
/share/CESM/cesm_input/lnd/clm2/isotopes/atm_delta_C13_CMIP6_1850-2015_yearly_v2.0_c171012.nc

/share/CESM/cesm_input/lnd/clm2/isotopes/atm_delta_C14_CMIP6_3x1_global_1850-2015_yearly_v2.0_c171012.nc

It appears that the files were created using netcdf4 and pnetcdf is having trouble reading them. Using nccopy I made cdf5 versions of the files and that works,

General bug information

CTSM version you are using: release-clm5.0.24

Does this bug cause significantly incorrect results in the model's science? No

Configurations affected: Some external machines

Details of bug

Some external machines seem to have trouble reading in NetCDF-4 format files. This works OK on local machines. NERSC machines sometimes has this problem in addition to the Korean system. From Jim "The problem seems to be related to cray systems, but I haven't figured out exactly why." So the best way to handle it now is to change the file format to either NetCDF-3 or NetCDF-5.

@ekluzek ekluzek added type: enhancement new capability or improved behavior of existing capability priority: high High priority task to fix soon, e.g., because it is a problem in important configurations branch tag: release Changes go on release branch as well as master labels May 24, 2019
@ekluzek ekluzek added this to the cesm2.1.1 milestone May 24, 2019
@ekluzek ekluzek self-assigned this May 24, 2019
@ekluzek
Copy link
Contributor Author

ekluzek commented May 28, 2019

Note, there are some datasets for mksurfdata_map that are in NetCDF format.

This one is required to be in NetCDF-4...

lnd/clm2/mappingdata/grids/UNSTRUCTgrid_0.5x0.5_AVHRR_c110228.nc

This one doesn't have to be....

lnd/clm2/rawdata/pftcftlandusedynharv.0.25x0.25.MODIS.simyr1850-2015.c170412/mksrf_soilcolor_simyr2005.c170413.nc netCDF-4 classic model

ekluzek added a commit to ekluzek/CTSM that referenced this issue May 28, 2019
@billsacks billsacks modified the milestones: cesm2.1.1, cesm2.1.2 Jul 10, 2019
@billsacks billsacks added this to To do in High priority Jul 10, 2019
@billsacks billsacks moved this from To do to Done but not on master in High priority Jul 15, 2019
@ekluzek ekluzek removed the branch tag: release Changes go on release branch as well as master label Oct 7, 2019
High priority automation moved this from Done but not on master to Done May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high High priority task to fix soon, e.g., because it is a problem in important configurations type: enhancement new capability or improved behavior of existing capability
Projects
Development

Successfully merging a pull request may close this issue.

2 participants