Outcfg.out general : Différence entre versions
m (→General information) |
m (→General description of the file outcdf.out) |
||
Ligne 1: | Ligne 1: | ||
== General description of the file '''outcdf.out''' == | == General description of the file '''outcdf.out''' == | ||
+ | ===== General information ===== | ||
+ | |||
+ | First one needs to define at least one type of '''grid''', one set of '''levels''', and one set of '''steps'''. | ||
+ | These will then get used in the '''sortie''' (for dynamic fields) resp. '''sortie_p''' (for physics fields) declarations. | ||
===== Example outcfg.out ===== | ===== Example outcfg.out ===== | ||
Ligne 13: | Ligne 17: | ||
sortie_p([MF,MY,MG,ALVIS,DLAT,DLON,WFLUX] ,grid, 1, levels, 1, steps, 1) | sortie_p([MF,MY,MG,ALVIS,DLAT,DLON,WFLUX] ,grid, 1, levels, 1, steps, 1) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
===== Output GRID definitions ===== | ===== Output GRID definitions ===== | ||
Version depuis le 11 de septembre 2020 à 20:15
Matières
General description of the file outcdf.out
General information
First one needs to define at least one type of grid, one set of levels, and one set of steps. These will then get used in the sortie (for dynamic fields) resp. sortie_p (for physics fields) declarations.
Example outcfg.out
grid=1,model; levels=1,eta,-1; levels=2,pres,[1000.,850.]; steps=1,hour,0.; steps=2,step,<0.,6.,1.>; sortie ([ME,PN,P0,PT] ,grid, 1, levels, 1, steps, 2) sortie_p([MF,MY,MG,ALVIS,DLAT,DLON,WFLUX] ,grid, 1, levels, 1, steps, 1)
Output GRID definitions
Examples:
grid=1,model; grid=2,core; grid=3,free;
General syntax:
grid=gridid,[model/core/free]; gridid - number to identify gridset to relate to sortie statement model - total grid of the model core - in LAM: model grid minus the pilot region free - in LAM: only the free area, excluding blending (Davies sponge) and pilot area
IMPORTANT NOTE:
Limit the number of definitions for "grid" to improve the efficiency in the output routines. The maximum number of definitions is 4.
Output LEVEL definitions
examples: levels=1,eta,-1; levels=2,eta,0; levels=6,eta,<1,12,2>; levels=5,pres,[1000.,850.,700.,500.]; general syntax levels=levelid , pres/eta,{list} levelid - number to identify levelset to relate to sortie statement eta - model levels (eta) - the integer corresponds to the "nth" defined model level thus make sure that the largest digit <= # of elements defined in hyb pres- pressure levels '-1' with "eta" levels will give all model levels. '0' with "eta" levels will give the ground "G_nk" level [a,b,c] means level a,b and c are requested <a,b,c> means levels a to b, every c are requested IMPORTANT NOTE: Limit the number of definitions for "level" to improve the efficiency the output routines. The maximum number of definitions is 32. The maximum number of levels defined in each "level" command is 201 VERY IMPORTANT NOTE: No physics variable output on PRESSURE levels
Output FREQUENCY definitions examples: steps=1,step,-1; steps=2,hour,0.,3.,6.,12.,24.,48.; steps=3,hour,<0.,48.,3.>; steps=4,init,hour,<0.,6.,1.>; steps=5,hour,<0.,24.,3.>,<24.,48.,6.>; steps=6,step,<0,5,1>,[6,12,18]; general syntax steps=stepid, [init],step/hour,{list}; stepid - number to identify stepset to relate to sortie statement 'init' - means this command only applies to output during the initialization period 'hour' - output in hours 'step' - output in timesteps in the model '-1' with "step" will give every timestep of the model [a,b,c] means a,b and c are requested <a,b,c> means a to b, incrementing every c are requested
IMPORTANT NOTE:
Limit the number of definitions for "steps" to improve the efficiency the output routines. The maximum number of definitions is 32. The maximum number of step/hour defined in each "steps" command is 50000