Current_Tag: see main FVcubed page
There are two sets of test cases: those defined internally in
the GFDL fvcubed dynamical core, and those which can be defined
by CAM itself. Both of these ignore the initial conditions
and set their own dynamics state. The GFDL test cases are now
considered obsolete. They are discussed in a separate page.
The CAM test cases correspond to the Jablonowski/Williamson
Test Cases reference. In order to use these test cases
the fvc_jw_case variable must have a valid value (1-6).
fvc_jw_case |
Meaning |
1 |
Baroclinic wave (steady state) |
|---|---|
2 |
Baroclinic wave (perturbed) |
3 |
Pure advection |
4 |
Rossby-Haurwitz wave |
5 |
Mountain induced Rossby wave |
6 |
Gravity waves |
Other possible namelist variables are discussed subsequently.
For fvc_case = 1..5:
fvc_case_rotation |
Tilt of earth rotation w.r.t. standard (0deg) |
0 |
0 degrees |
|---|---|
1 |
15 degrees |
2 |
30 degrees |
3 |
45 degrees |
4 |
60 degrees |
5 |
75 degrees |
6 |
90 degrees |
For fvc_case 6, the same variable denotes the case variant:
fvc_case_rotation |
Meaning |
0 |
No Coriolis, still atmosphere |
|---|---|
1 |
No Coriolis, isothermal, still atmosphere |
2 |
No Coriolis, isothermal, u0 = 40 m/s |
3 |
Coriolis, isothermal, still atmosphere |
Assuming you want to run an adiabatic test case #1 with 60 degree rotation
on bluefire with resolution 96x96 cells per face for one day from an initial file:
- Check out tag:
svn co $SVNREPO/cam1/Current_Tag
- Configure:
configure -mach bluefire -dyn fvcubed -hgrid c96 -nlev 26 -pcols 2304 -nadv_tt 4 -phys adiabatic -spmd -nosmp
- Build:
gmake -j 4
- Namelist:
build-namelist -s -case $case -config $blddir/config_cache.xml \
-namelist "&camexp start_type='startup' stop_option='ndays' stop_n=30 \
nhtfrq=-6 ndens=2 hfilename_spec='h%t.nc' mfilt=130 restart_option='end' \
phys_loadbalance=0 empty_htapes=.true. inithist = 'NONE' \
fvc_n_sponge=0 fvc_npes_x=4 fvc_npes_y=4 fvc_jw_case=1 fvc_case_rotation=4 \
fincl1= 'U:I','V:I','T:I','PS:I','PHIS:I','Z3:I','T850:I', \
'U850:I','V850:I','OMEGA850:I', \
'TT_LW:I','TT_MD:I','TT_HI','TTRMD' /"
- Run:
$runcmd $blddir/cam(architecture dependent)
For this particular run, only certain information are needed
from the initial data file; for the most part the
model initializes itself.
We recommend using the standard cubed-sphere resolutions c24 (approx. 4 deg),
c48 (approx. 2 deg), c96 (approx. 1deg) and c192 (approx. 0.5 deg) where cXX
indicates the number of cells (in x and y) within each cubed-sphere panel.
These standard resolutions guarantee better load-balancing properties.
Please get back to me with any questions or input.
Have fun!