...
Volet |
---|
configexp.cfg dyn_input_table rpnstd_units.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:
...
Volet |
---|
sortie_p([CY,DR,SQAC,STAC,STSS,SK,TN,TE,R2,Q4,GR,M9] ... |
sps.cfg
Driving with fields on staggered lowest predictive model levels
1) Lvl_typ_S = 'HS' (HS= Hybride Staggered.. HU= Hybride Uniforme (toutes les variables sur le meme niveau)
2) Lvl_list = MOMENTUM LEVEL ONLY - SPS will deduce the thermo level by itself
3) ip1a=-1
ip1at=-1
For (3) , By using =-1, you let SPS figure out the ip1 using the standard encoding. (*Note that I don’t know what the “standard” is, I’m under the impression the ip1 encoding has changed with various GEM versions but perhaps it remained constant for HS levels).
If the ip1 encoding is not standard, you can override the ip1s using these 2 keys. In all cases, standard or not, you can choose to specify these.
The actual values for the lowest prognostic level + ip1s will depend on the forcing model configuration. It will vary from one GEM system to another.
Example:
Volet |
---|
@levels_cfgs Lvl_typ_S = 'HS' Lvl_ptop_8 = 1000.0 Lvl_list = 0.997502 Lvl_rcoef = 3., 15. @sps_cfgs ip1a = -1 |
Driving with fields on diagnostic levels
Example:
Volet |
---|
@levels_cfgs Lvl_typ_S ='HU' Lvl_ptop_8 =1000.0 Lvl_list =-1 @sps_cfgs zta = 2.0 zua =10.0 ip1a =93423264 |