[Dart-dev] DART/branches Revision: 12456

dart at ucar.edu dart at ucar.edu
Tue Mar 20 15:30:21 MDT 2018


thoar at ucar.edu
2018-03-20 15:30:21 -0600 (Tue, 20 Mar 2018)
145
Adding a monthly spinup file from a hybrid start.
These also have the necessary bugfixes for the multi-instance finidat 
interpolation problem.




Modified: DART/branches/cesm_clm/models/clm/shell_scripts/cesm2_0/CESM2_0_setup_hybrid
===================================================================
--- DART/branches/cesm_clm/models/clm/shell_scripts/cesm2_0/CESM2_0_setup_hybrid	2018-03-20 13:11:20 UTC (rev 12455)
+++ DART/branches/cesm_clm/models/clm/shell_scripts/cesm2_0/CESM2_0_setup_hybrid	2018-03-20 21:30:21 UTC (rev 12456)
@@ -27,11 +27,11 @@
 # incorporate any needed changes into this script.
 # ==============================================================================
 
-setenv CASE           clm5_hybrid_e4
+setenv CASE           clm5_f09_spinup80
 setenv resolution     f09_f09
 setenv compset        2000_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV
 setenv cesmtag        ctsm
-setenv num_instances  4
+setenv num_instances  80
 
 # ==============================================================================
 # Directories:
@@ -89,7 +89,7 @@
 # ==============================================================================
 
 setenv refcase      clm5_f09_spinup80
-setenv refyear      1999
+setenv refyear      2001
 setenv refmon       01
 setenv refday       01
 setenv reftod       00000
@@ -98,8 +98,28 @@
 
 setenv stagedir /glade/p/image/RDA_strawman/CESM_ensembles/CLM/CLM5BGC-Crop/${reftimestamp}
 
-setenv startdate    2004-01-01
+setenv startdate    2000-01-01
 
+# The forward operators for the flux tower obs _require_ that we predict the name of
+# of the history file. The history file names of interest are time-tagged with the
+# _start_ of the forecast - not the restart time. The obs_def_tower_mod.f90 requires
+# the stop_option to be 'nhours', and the stop_n to be accurate.
+
+setenv stop_option  nhours
+setenv stop_n       24
+setenv resubmit     0
+
+@ clm_dtime = 1800
+@ h1nsteps = $stop_n * 3600 / $clm_dtime
+
+#>@todo stream template files & multiple years. Do we need to specify
+#> year 1 and year N (performance penalty?). Can we change years on-the-fly
+#> during a run?
+
+set stream_year_align = 1998
+set stream_year_first = 1998
+set stream_year_last  = 2010
+
 # ==============================================================================
 # job settings:
 #
@@ -106,12 +126,10 @@
 # queue      can be changed during a series by changing the case.run
 # timewall   can be changed during a series by changing the case.run
 #
-# TJH: Advancing 30 instances for 6 hours and assimilating took
-#      less than 10 minutes on yellowstone using 1800 pes (120 nodes)
 # ==============================================================================
 
 setenv queue        economy
-setenv timewall     0:20
+setenv timewall     00:20:00
 setenv short_term_archiver off
 
 # ==============================================================================
@@ -233,57 +251,36 @@
    exit 5
 endif
 
-# The forward operators for the flux tower obs _require_ that we predict the name of
-# of the history file. The history file names of interest are time-tagged with the
-# _start_ of the forecast - not the restart time. The obs_def_tower_mod.f90 requires
-# the stop_option to be 'nhours', and the stop_n to be accurate.
+./xmlchange STOP_OPTION=$stop_option
+./xmlchange STOP_N=$stop_n
+./xmlchange RESUBMIT=$resubmit
+./xmlchange REST_OPTION=ndays
+./xmlchange REST_N=1
 
-setenv resubmit            0
-setenv stop_option         nhours
-setenv stop_n              24
-
-@ clm_dtime = 1800
-@ h1nsteps = $stop_n * 3600 / $clm_dtime
-
-#>@todo stream template files & multiple years. Do we need to specify
-#> year 1 and year N (performance penalty?). Can we change years on-the-fly
-#> during a run?
-
-set stream_year_align = 1998
-set stream_year_first = 1998
-set stream_year_last  = 2010
-
 ./xmlchange CALENDAR=GREGORIAN


More information about the Dart-dev mailing list