[Dart-dev] DART/branches Revision: 12194

[dart at ucar.edu]

thoar at ucar.edu
2017-12-08 15:47:16 -0700 (Fri, 08 Dec 2017)
415
Updated documentation to describe how the files get named with the
current 'ocean_time' (converted to days) instead of the time pertaining
to the start of the forecast (as is the custom in the 4Dvar system).

Obfuscated the project number so no accounting mishaps can happen.

Finalized some of the comments. 

Passed testing on yellowstone's LSF.
Passed testing on eddy's slurm.
Passed testing on cheyenne's PBS.




Modified: DART/branches/rma_trunk/models/ROMS/model_mod.html
===================================================================
--- DART/branches/rma_trunk/models/ROMS/model_mod.html	2017-12-08 21:56:14 UTC (rev 12193)
+++ DART/branches/rma_trunk/models/ROMS/model_mod.html	2017-12-08 22:47:16 UTC (rev 12194)
@@ -76,8 +76,31 @@
 </P>
 
 <P>
+<strong>A note about file names:</strong> During the course of an experiment, many files
+are created. To make them unique, the <em class=code>ocean_time</em> is converted from
+<blockquote>"seconds since 1900-01-01 00:00:00"</blockquote> to the equivalent
+number of DAYS. An <em class=it>integer</em> number of days. The intent is to tag the 
+filename to reflect the valid time of the model state. This could be used as the DSTART 
+for the next cycle, so it makes sense to me.
+<br />
+<br />
+The confusion comes when applied to the observation files.
+The input observation files for the ROMS 4DVAR system typically have a DSTART that 
+designates the start of the forecast cycle and the file must contain observation from DSTART
+to the end of the forecast. Makes sense. The model runs to the end of the forecast,
+harvesting the verification observations along the way.
+<br />
+<br />
+So then DART converts all those verification observations and tags that file ... with the same
+time tag as all the other output files ... which reflects the <em class=code>ocean_time</em>
+(converted to days). The input observation file to ROMS will have a different DSTART time
+in the filename than the corresponding verification files. Ugh. You are free to come up
+with a better plan. These are just examples, after all. Hopefully good examples.
+</P>
+
+<P>
 The procedure to perform an assimilation experiment is outlined in the following steps:
-<P>
+</P>
 
 <ol><li>Compile ROMS (as per the ROMS instructions).</li>
     <li>Compile all the DART executables (in the normal fashion).</li>

Modified: DART/branches/rma_trunk/models/ROMS/shell_scripts/advance_ensemble.csh.template
===================================================================
--- DART/branches/rma_trunk/models/ROMS/shell_scripts/advance_ensemble.csh.template	2017-12-08 21:56:14 UTC (rev 12193)
+++ DART/branches/rma_trunk/models/ROMS/shell_scripts/advance_ensemble.csh.template	2017-12-08 22:47:16 UTC (rev 12194)
@@ -43,7 +43,7 @@
 #PBS -l walltime=00:10:00
 #PBS -q economy
 #PBS -l select=1:ncpus=16:mpiprocs=16
-#PBS -A P86850054
+#PBS -A P8685nnnn
 #PBS -N roms_advance
 #
 #==========================================================================
@@ -54,12 +54,12 @@
 #BSUB -o roms_advance.%J.%I.log
 #BSUB -N -u ${USER}@ucar.edu
 #BSUB -q small
-#BSUB -n 1
+#BSUB -n 16
 #BSUB -W 0:10
-#BSUB -P P86850054
+#BSUB -P P8685nnnn
 
 #==========================================================================
-# STEP 0: figure out the platform-specific nuances.
+# Figure out the platform-specific nuances.
 #==========================================================================
 if ($?SLURM_JOB_ID) then
 

Modified: DART/branches/rma_trunk/models/ROMS/shell_scripts/batch_job_resource_explanation.txt
===================================================================
--- DART/branches/rma_trunk/models/ROMS/shell_scripts/batch_job_resource_explanation.txt	2017-12-08 21:56:14 UTC (rev 12193)
+++ DART/branches/rma_trunk/models/ROMS/shell_scripts/batch_job_resource_explanation.txt	2017-12-08 22:47:16 UTC (rev 12194)
@@ -28,7 +28,7 @@
 #SBATCH --ntasks-per-node=1		only put N tasks on each node
 #SBATCH --array=1-Myens_size		job array syntax
 #SBATCH --time=00:01:00
-#SBATCH --account P86850054
+#SBATCH --account P8685nnnn
 #SBATCH --partition dav			queue
 #SBATCH --exclude=node04		do not run on this node(list)
 #SBATCH --error  testslurm.%j.err
@@ -48,7 +48,7 @@
 #PBS -J 1-Myens_size			job aray syntax
 #PBS -l select=1:ncpus=16:mpiprocs=16	want 1 node with at least 16 cpus, use N of them
 #PBS -l walltime=00:10:00
-#PBS -A P86850054
+#PBS -A P8685nnnn
 #PBS -q economy
 #PBS -r n				job is not rerunable
 #
@@ -63,7 +63,7 @@
 #BSUB -J roms_cycle[1-Myens_size]	Job array syntax
 #BSUB -o roms_cycle.%J.log		output filename with unique job index
 #BSUB -o roms_cycle.%J.%I.log		output filename with job index and array index
-#BSUB -P P86850054
+#BSUB -P P8685nnnn
 #BSUB -q small				queue
 #BSUB -n 16				need at least this many tasks
 #BSUB -R "span[ptile=16]"		only put this many tasks on each node

Modified: DART/branches/rma_trunk/models/ROMS/shell_scripts/cycle.csh.template