View source for How to run ACCESS AMIP runs with CABLE2.X

{{Needs Update}}

<span style="font-family: Tahoma,Geneva,sans-serif;">The standard run saaqb (accesscollab) or vabha (accessdev) are configured to run with CABLE1.8. If you want to use a newer version, CABLE2.X, the set-up changes. vacfa (owned by rzl561) is an example for a run using CABLE2.X. The main difference is that CABLE is included as a library and you need to make sure the correct cable library and namelist file is in your /short/$PROJECT/$USER/UM_ROUTDIR/$RUNID directory.</span>

# <span style="font-family: Tahoma,Geneva,sans-serif;">Set up your environment as described on [[UM Environment | UM Environment page]]</span>
# <span style="font-family: Tahoma,Geneva,sans-serif;">set up $CABLE-AUX, e.g. pointing to you $HOME or wherever your CABLE-AUX directory is (if you do not know what CABLE-AUX is have a look into the [https://trac.nci.org.au/trac/cable/wiki/CableUserGuide | CABLE user guide])</span>
# <span style="font-family: Tahoma,Geneva,sans-serif;">make sure to have the correct cable.nml namelist in CABLE-AUX/UM. This is copied automatically as long as you do not change this behaviour in cable_start.sh</span>
# <span style="font-family: Tahoma,Geneva,sans-serif;">the default cable_start.sh in CABLE-AUX/UM copies cable.nml to /short/...../$RUNID and libcable to the same place (called at start of cable). The default version does not necessarily work for you because of hardwired project to d66 etc. So you have to change it. The cable library needs to be called "libcable-2.0.a" (hardwired in override file). You also need to have cable.nml in /short/...../RUNID as well as /short/...../RUNID/bin, create a simlink using cable_start.sh from bin to folder up.</span>

==Other useful hints (apply also for running with CABLE1.8)== 
===<span style="font-family: Tahoma,Geneva,sans-serif;">Running for longer than 2001</span>=== 
<span style="font-family: Tahoma,Geneva,sans-serif;">Some of the default emission ancillaries end in 2001. For runs until after 2001 we need to use the CMIP5 projections for the more recent period. For RCP4.5 and RCP8.5 they area available as concatenated files in the normal directory (/projects/access/data/ancil/CMIP5/).</span>

==='''ACCESS output filenames and decades'''=== 
<span style="font-family: Tahoma,Geneva,sans-serif;">Filenames: RUNIDa.p?d7mon</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">?: is output stream, normally “a” for monthly files, “e” for daily files</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">d: letter for decade, see below</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">7: number for year</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">mon: three letters for month</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">The automatic postprocessing translates this into more useful filenames, see [[Archiving Output | Archiving+Output]]</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">The restart files have very similar names except for “da” instead of “p?” e.g.: RUNIDa.dad7110</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">d: letter for decade, see below</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">7: number for year</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">110: time, restart files are written every month, 110 corresponds to beginning of year</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">Decades:</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">a 1900</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">b 10</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">c 20</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">d 30</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">e 40</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">f 50</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">g 60</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">h 70</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">i 80</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">j 90</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">k 2000</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">l 10</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">m 20</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">n 30</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">o 40</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">p 50</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">q 60</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">r 70</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">s 80</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">t 90</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">u 2100</span>

===<span style="font-family: Tahoma,Geneva,sans-serif;">Error message Bi_linear_h Error code: 10</span>=== 
<span style="font-family: Tahoma,Geneva,sans-serif;">This error can have different causes and is difficult to resolve. Causes can be:</span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">confusion over the setup</span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">bad initial data</span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">errors in code/modeling</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">This error in you output file and “RHS zero so GCR( 2 ) not needed”</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">is always a bad sign. Often it means that the model has had a floating point exception and generated a NaN somewhere. It crashes soon afterwards in bi_linear_h because the winds are crazy.</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">What you can do (e-mails from Martin Dix): </span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">To get more information: UMUI panel Scientific Parameters and Sections -> 13. Diffusion -> Diag prints-> print output on all processors</span>
<span style="font-family: Tahoma,Geneva,sans-serif;">do this for every time step, especially if the crash happens in 1st or 2nd time step</span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">Add print statements into the code, in particular if you made changes to CABLE and need to know which variables cause the problem</span>
* <span style="font-family: Tahoma,Geneva,sans-serif;">Use totalview to debug, especially second section here [[TotalView Debugging | Totalview debugging]] is particular about UM</span>

<span style="font-family: Tahoma,Geneva,sans-serif;">Ask CMS team or um_help for help if you cannot resolve it!</span>

[[Category:Unified Model]][[Category:CABLE]]