Hello!
I've been working on conducting fully coupled simulations for PD (e.g., 2006-2011) and the future (e.g., 2089-2094) under different scenarios (SSP245 and 585) in CESM2.1.4 on Derecho.
I successfully conducted simulations for those periods on Cheyenne using CESM2.1.2 and the restart field I found below.
/glade/campaign/collections/cmip/CMIP6/restarts/
e.g., b.e21.BHIST.f09_g17.CMIP6-historical.001/b.e21.BHIST.f09_g17.CMIP6-historical.001.rest.2010-01-01-00000.tar
Now, I am trying to rerun the simulations using CESM2.1.4 with these restart files generated on Cheyenne, but I encountered a series of error messages.
After resolving some of the messages, I can now generate output files for the first month. However, the model run was terminated afterward with the following error message found in the cesm.log file.
Error message:
dec0662.hsn.de.hpc.ucar.edu 0: WARNING: Rearr optional argument is a pio2 feature, ignored in pio1
dec0662.hsn.de.hpc.ucar.edu 0: GPTLstopf thread 0: timer for "a:PIO:pre_pio_write_nf" had not been started.
Does anyone have any suggestions, comments, or insights into what might be happening here?
Many thanks!
Quote Reply
I've been working on conducting fully coupled simulations for PD (e.g., 2006-2011) and the future (e.g., 2089-2094) under different scenarios (SSP245 and 585) in CESM2.1.4 on Derecho.
I successfully conducted simulations for those periods on Cheyenne using CESM2.1.2 and the restart field I found below.
/glade/campaign/collections/cmip/CMIP6/restarts/
e.g., b.e21.BHIST.f09_g17.CMIP6-historical.001/b.e21.BHIST.f09_g17.CMIP6-historical.001.rest.2010-01-01-00000.tar
Now, I am trying to rerun the simulations using CESM2.1.4 with these restart files generated on Cheyenne, but I encountered a series of error messages.
After resolving some of the messages, I can now generate output files for the first month. However, the model run was terminated afterward with the following error message found in the cesm.log file.
Error message:
dec0662.hsn.de.hpc.ucar.edu 0: WARNING: Rearr optional argument is a pio2 feature, ignored in pio1
dec0662.hsn.de.hpc.ucar.edu 0: GPTLstopf thread 0: timer for "a:PIO:pre_pio_write_nf" had not been started.
Does anyone have any suggestions, comments, or insights into what might be happening here?
Many thanks!
Quote Reply