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?
- We only support certain versions (CESM support policy). We can only provide limited help for versions that are no longer supported.
- 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
Have you made any changes to files in the source tree?
- Describe any changes (code, xml files, etc.)
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.
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:
Hi,
I’m attempting to run an ENSO model with CESM version 2.1.5.
I’m receiving the error "iyear0 does not match start year" and am puzzled as to where that could be coming from. My run_env file has the REF_DATE stated as "1731-03-01" and the RUN_STARTDATE as "0001-03-01". My initial run_env file was replaced with a new one so this could be where the issue lies. However, I've had previous sample runs work with the aforementioned date configuration.
Help with this would be greatly appreciated.
Thanks,
Ian
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?
- We only support certain versions (CESM support policy). We can only provide limited help for versions that are no longer supported.
- 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
Have you made any changes to files in the source tree?
- Describe any changes (code, xml files, etc.)
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.
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:
Hi,
I’m attempting to run an ENSO model with CESM version 2.1.5.
I’m receiving the error "iyear0 does not match start year" and am puzzled as to where that could be coming from. My run_env file has the REF_DATE stated as "1731-03-01" and the RUN_STARTDATE as "0001-03-01". My initial run_env file was replaced with a new one so this could be where the issue lies. However, I've had previous sample runs work with the aforementioned date configuration.
Help with this would be greatly appreciated.
Thanks,
Ian