CESM 如何在一个跑过的case的基础上进行hybrid run？

福睿爱free

wfy 发表于 2019-11-14 14:21
还有最后一句声明是必须的吗？
echo ' finidat = "case名称.clm2.r.时间-00000.nc"' > user_nl_clm

请问您解决这个问题了么？我不太明白最后这个声明...

一大碗年糕

cara0229 发表于 2019-4-12 09:37
请问一下楼主，你用的是哪个版本的CESM呀？历史状态目录里的文件包括哪些呢？我的没有rest目录，所有输出的 ...

没有rest目录应该是由于short-term archiving开启了，所以转移到指定的位置下面了
Chapter 4. Running CESM
Backing up to a previous restart
If a run encounters problems and crashes, you will normally have to back up to a
previous restart. Assuming that short-term archiving is enabled, you will need to
find the latest $DOUT_S_ROOT/rest/yyyy-mm-dd-ssss/ directory that was created
and copy the contents of that directory into your run directory ($RUNDIR). You can
then continue the run and these restarts will be used. It is important to make sure the
new rpointer.* files overwrite the rpointer.* files that were in $RUNDIR, or the job
may not restart in the correct place.
Occasionally, when a run has problems restarting, it is because the rpointer files are
out of sync with the restart files. The rpointer files are text files and can easily be
edited to match the correct dates of the restart and history files. All the restart files
should have the same date.
Data flow during a model run
All component log files are copied to the directory specified by the env_run.xml
variable $LOGDIR which by default is set to $CASEROOT/logs. This location is where
log files are copied when the job completes successfully. If the job aborts, the log files
will NOT be copied out of the $RUNDIR directory.
Once a model run has completed successfully, the output data flow will depend on
whether or not short-term archiving is enabled (as set by the env_run.xml variable,
$DOUT_S). By default, short-term archiving will be done.
No archiving
If no short-term archiving is performed, then all model output data will remain in
the run directory, as specified by the env_run.xml variable, $RUNDIR. Furthermore,
if short-term archiving is disabled, then long-term archiving will not be allowed.
Short-term archiving
If short-term archiving is enabled, the component output files will be moved to the
short term archiving area on local disk, as specified by $DOUT_S_ROOT. The di-
rectory DOUT_S_ROOT is normally set to $EXEROOT/../archive/$CASE. and will
contain the following directory structure:
atm/
hist/ logs/
cpl/
hist/ logs/
glc/
logs/
ice/
hist/ logs/
lnd/
hist/ logs/
ocn/
hist/ logs/
rest/
yyyy-mm-dd-sssss/
....
yyyy-mm-dd-sssss/
hist/ contains component history output for the run.

logs/ contains component log files created during the run. In addition to $LOGDIR,
log files are also copied to the short-term archiving directory and therefore are avail-
able for long-term archiving.
rest/ contains a subset of directories that each contain a consistent set of restart files,
initial files and rpointer files. Each sub-directory has a unique name corresponding
to the model year, month, day and seconds into the day where the files were created
(e.g. 1852-01-01-00000/). The contents of any restart directory can be used to create
a branch run or a hybrid run or back up to a previous restart date.