File tree Expand file tree Collapse file tree 7 files changed +1082
-0
lines changed Expand file tree Collapse file tree 7 files changed +1082
-0
lines changed Original file line number Diff line number Diff line change
1
+ The following files are available to assist developers in JEDI Phase 3 validation.
2
+
3
+ run_gsi.py and run_jedi.py
4
+ - stage files to run the indicated analysis executable
5
+ - create a batch script the user can subit to run executable
6
+
7
+ config_gsi.yaml and config_jedi.yaml
8
+ - set batch job configuration variables
9
+ - specify key directories
10
+ - specify the application exeutable and parameter file
11
+
12
+ atmanlvar.yaml
13
+ - sample yaml file to configure 3DVAR JEDI analysis
14
+
15
+ gsiparm.anl
16
+ - sample namelist to configure 3DVAR GSI analysis
17
+
18
+
19
+ A Phase 3 validation workflow would entail
20
+
21
+ 1. modify atmanlvar.yaml and gsipmarm.anl to get the desired configuration
22
+
23
+ 2. modify config_jedi.yaml and config_gsi.yaml to point at the configuration
24
+ files from 1 and the executables to be run. Set the RUNDIR in which the
25
+ jobs are run
26
+
27
+ 3. execute run_gsi.py and run_jedi.py. The syntax is "./run_gsi.py -y ./config_gsi.yaml"
28
+ and "./run_jedi.py -y ./config_jedi.yaml". The run*py script will
29
+ (a) populate the specified RUNDIR with the files to run the given app
30
+ (b) create a batch script with the runscript name specified in the input yaml.
31
+ The batch script is created RUNDIR
32
+
33
+ 4. cd to the specified RUNDIR to submit the batch script. The job log file is written
34
+ to RUNDIR
35
+
36
+ 5. examine ouput upon job completion
You can’t perform that action at this time.
0 commit comments