You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue when running the coupled ELM-FATES model for a gridded domain. The issue is when an output file is trying to be written, an error emerges saying the output file has invalid dimension ID or name:
1: Opened file ./testYF_FATESonly1.IELMFATES.pm-cpu.gnu..2025-02-10.elm.h0.2011-01.nc to write 5
1: pio_support::pio_die:: myrank= -1 : ERROR: nf_mod.F90: 1293 : NetCDF: Invalid dimension ID or name
I have tested the same configuration with only ELM (changing only export COMPSET=IELMFATES to export COMPSET=IELM) and this produced viable output for multiple months of simulation. As a result, I am more confident this is a FATES issues and not an ELM one.
Things I have tried and/or checked which have all resulted in the same file-write error:
Changing all NetCDF files to a consistent type - “netcdf-4 classic model”
Changed the PIO version from 1 to 2 (this was a different error)
Checked the dimensions for domain and surface files
Checked the dimensions for the forcing files
Replaced the FATES parameter file with one that is compatible with the FATES version
Additionally, I need to use a specific version of ELM-FATES that is compatible to be coupled with the ParFlow hydrologic model. The versions I am using are:
E3SM - v2.0.0-alpha.2-22950-g6ece06802d
FATES - sci.1.61.0_api.25.0.0-2-g2105ed18
I have attached the E3SM and Land logs, as well as my create case script. Thanks!
Describe the issue
I am encountering an issue when running the coupled ELM-FATES model for a gridded domain. The issue is when an output file is trying to be written, an error emerges saying the output file has invalid dimension ID or name:
I have tested the same configuration with only ELM (changing only
export COMPSET=IELMFATES
toexport COMPSET=IELM
) and this produced viable output for multiple months of simulation. As a result, I am more confident this is a FATES issues and not an ELM one.Things I have tried and/or checked which have all resulted in the same file-write error:
Additionally, I need to use a specific version of ELM-FATES that is compatible to be coupled with the ParFlow hydrologic model. The versions I am using are:
E3SM - v2.0.0-alpha.2-22950-g6ece06802d
FATES - sci.1.61.0_api.25.0.0-2-g2105ed18
I have attached the E3SM and Land logs, as well as my create case script. Thanks!
lnd.log.35707822.250210-202354.txt
e3sm.log.35707822.250210-202354.txt
er_dtk_scratch_FATES_ELM.sh.txt
Relevant log output
FATES tag
sci.1.61.0_api.25.0.0-2-g2105ed18
Host land model tag
ELM - v2.0.0-alpha.2-22950-g6ece06802d
Machine
perlmutter
Other supported machine name
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: