General information
SPS 6.1.1 uses the same physics version as GEM 5.1.1.
I suggest you create yourself a directory under your home for your source code, scripts and config files, for example:
mkdir -p ~/SPS/v_6.1.1
cd ~/SPS/v_6.1.1
mkdir Abs Configs Scripts
Scripts
The name of the scripts directory:
~/SPS/v_6.1.1/Scripts
is mandatory!
In the above directory you need the following scripts:
SPS_launch
SPS_prepare_job.sh
SPS_link_pilots.sh
r.run_in_parallel
sps.sh
o.set_array.dot
task_setup.dot
task_setup.py
task_setup_cachegen
Executable
a) Create directory for executable
To create an executable first create yourself a directory under your home for the source code; preferably under ~/SPS/v_6.1.1/Abs and change into it, for example:
cd ~/SPS/v_6.1.1/Abs/My_Abs
b) Get the basename of abs-directory
Get the basename (last part of your directory path) of your abs-directory for later use:
'base_dir' should now be set to 'My_Abs'. You can verify it with:
echo $base_dir
c) Clone the SPS Git repository you want to start from, for example:
d) Create working directories
So the object files, libraries and executables will not be under your home, create links for the directories 'build' and 'work'. Pick a place under which you want to keep the object files, libraries and executables under your data space, or example:
Create the directories and the links (using ${base_dir} from above) :
mkdir -p ${work_space}/${base_dir}/work
ln -s ${work_space}/${base_dir}/build
ln -s ${work_space}/${base_dir}/work
e) Acquire a compiler
Only needed once per window/terminal. Same as for GEM 5.1.1.
f) Set the variable 'abs_dir'
Set the variable 'abs_dir' to the name of your executable directory, including the 'gem' directory (needed under e))
g) Change into 'build' directory:
h) Create make files and dependencies
Only need once at the beginning and whenever you add any new routines or add include files or module "use" lines to an existing routine.
i) Compile and create executable
You can also use n cores in parallel by adding the '-jn', for example to use 4 cores:
make -j4 mainspsdm
Config files
You need the following config files:
configexp.cfg
sps.cfg
outcfg.out
dyn_input_table
physics_input_table
rpnstd_units.dict
rpnstd_units.rdict
sps.dict
outcfg.out
SPS does not have the possibility to write and continue from restart files. Therefore, at the end of each job all fields needed to start another simulation need to get outputted. The next job will then use the output of the previous job as initial conditions. To make the output of fields at the end of a job easier, steps=1 and steps=2 are now hard coded to:
steps=2 will automatically get set to the last timestep of the current job.
ISBA
The following is a list of mandatory initial condition fields for ISBA:
SD : VD=snow depth DN : VD=relative snow density I0 : VD=surface and soil temperatures I1 : VD=soil volumetric water contents I2 : VD=soil volumetric ice contents I3 : VD=water retained on the vegetation I4 : VD=water in the snow pack
I5 : VD=snow mass
I6 : VD=albedo of snow I7 : VD=sea ice temperature I8 : VD=sea ice thickness I9 : VD=glacier temperature
FLake
The following is a list of mandatory initial condition fields for FLake:
CLASS
When running CLASS, in addition to the ISBA fields above one also needs to output the following fields: