Please fill in all relevant information below, deleting the red text after you have read it.
Before submitting a help request, please check to see if your question is already answered:
- Search the forums for similar issues
- Check the CIME troubleshooting guide to see if any suggestions there solve your problem
- Check any other relevant CESM documentation
What version of the code are you using?
- CESM staff members will mainly provide answers for supported model versions, as outlined in the CESM support policy, and can only provide limited help for versions that are no longer supported. You may ask questions about unsupported versions, but may need to rely on community answers.
- For CESM2.1.2 onwards run the script ./describe_version from the top level of your CESM clone to find the version
- From older model versions, provide the output from running the following commands from the top level of your CESM clone
> git describe
> ./manage_externals/checkout_externals --status --verbose
ctsm5.3.044
Have you made any changes to files in the source tree?
- Describe any changes (code, xml files, etc.)
Source code changes that add WBGT and additional variables to the HumanIndexMod.
Describe every step you took leading up to the problem:
- Describe every step you took, starting with the create_newcase command and including any changes you made to xml files, user_nl files, etc. Please try to reproduce the problem first using your own instructions.
./create_newcase --case /dodrio/scratch/projects/2022_200/project_output/bclimate/jbuzan/cases/ctsm5.3.044/i.t530.IHistClm50BgcCrop.hcru_hcru_mt13.obsclim-histsoc-default-20CRv3-ERA5-go-2048.010_64pfts_nodrops --res hcru_hcru_mt13 --compset IHistClm50BgcCrop --mach hortense --project '2022_201' --run-unsupported
Input data is modified to match ISIMIP standardization.
I get consistent PIO errors:
cesm log PIO2 pio_file.c retry NETCDF.
We use:
ESMF/8.6.0-foss-2023a
ESMF_PIO=internal.
My guess is the PIO errors are likely related to the outdated version of PIO internal to ESMF 8.6.0. The simulation seems to run slowly. My last simulation was 5 consecutive years at 2048 cores, 2x 64-core AMD Epyc 7763 CPU 2.45 GHz (“Milan” microarchitecture, 128 cores per node) 238 GiB usable RAM (~1.85GB/core), no swap 480 GB SSD local disk.
We are producing ~100Gb of land data per year, largest file is 53Gb. Restart directory is ~112Gb. It took about 17 hours for the 5 years.
If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.
- If the error occurs during the build, please attach the appropriate build log file showing the compilation error message.
- If the error occurs during the run, please attach all log files from the run (cpl.log, cesm.log and all component log files).
Describe your problem or question:
I do not understand why the timing file is not generated. I tried to set
<entry id="SAVE_TIMING" value="TRUE">
yet the timing files are still not written.
Before submitting a help request, please check to see if your question is already answered:
- Search the forums for similar issues
- Check the CIME troubleshooting guide to see if any suggestions there solve your problem
- Check any other relevant CESM documentation
What version of the code are you using?
- CESM staff members will mainly provide answers for supported model versions, as outlined in the CESM support policy, and can only provide limited help for versions that are no longer supported. You may ask questions about unsupported versions, but may need to rely on community answers.
- For CESM2.1.2 onwards run the script ./describe_version from the top level of your CESM clone to find the version
- From older model versions, provide the output from running the following commands from the top level of your CESM clone
> git describe
> ./manage_externals/checkout_externals --status --verbose
ctsm5.3.044
Have you made any changes to files in the source tree?
- Describe any changes (code, xml files, etc.)
Source code changes that add WBGT and additional variables to the HumanIndexMod.
Describe every step you took leading up to the problem:
- Describe every step you took, starting with the create_newcase command and including any changes you made to xml files, user_nl files, etc. Please try to reproduce the problem first using your own instructions.
./create_newcase --case /dodrio/scratch/projects/2022_200/project_output/bclimate/jbuzan/cases/ctsm5.3.044/i.t530.IHistClm50BgcCrop.hcru_hcru_mt13.obsclim-histsoc-default-20CRv3-ERA5-go-2048.010_64pfts_nodrops --res hcru_hcru_mt13 --compset IHistClm50BgcCrop --mach hortense --project '2022_201' --run-unsupported
Input data is modified to match ISIMIP standardization.
I get consistent PIO errors:
cesm log PIO2 pio_file.c retry NETCDF.
We use:
ESMF/8.6.0-foss-2023a
ESMF_PIO=internal.
My guess is the PIO errors are likely related to the outdated version of PIO internal to ESMF 8.6.0. The simulation seems to run slowly. My last simulation was 5 consecutive years at 2048 cores, 2x 64-core AMD Epyc 7763 CPU 2.45 GHz (“Milan” microarchitecture, 128 cores per node) 238 GiB usable RAM (~1.85GB/core), no swap 480 GB SSD local disk.
We are producing ~100Gb of land data per year, largest file is 53Gb. Restart directory is ~112Gb. It took about 17 hours for the 5 years.
If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.
- If the error occurs during the build, please attach the appropriate build log file showing the compilation error message.
- If the error occurs during the run, please attach all log files from the run (cpl.log, cesm.log and all component log files).
Describe your problem or question:
I do not understand why the timing file is not generated. I tried to set
<entry id="SAVE_TIMING" value="TRUE">
yet the timing files are still not written.
