jhan_Tickets_6.2_part2

Thread CABLE vars through to surf_couple* layer

CABLE requires different information to that which is available in JULES. These are:

1. tiled soil and snow prognostics (aka prognostics variables)
2. some vegetation and soil type parameters (aka parameters)
3. some variables that are required to be kept between pathways and timesteps (aka working variables)

Consistent with NGMS, and following JULES methodology in this vein, we constructed 3 TYPEs containing the above variables in Ticket #???. In a this submission we aim to pick up TWO of these TYPEs at the top-level (prognostics and working) and pass them down to the surf_couple_layer. We assume that the parameters TYPE can be USEd at the surf_couple_ layer as the members of this TYPE are constant in time (albeit of vector length 17[corresponding to the number of PFTs used in CABLE]).

Subsequently we will pass these TYPEs to CABLE, and in some cases proceed to add variables to them once we have included the functioning CABLE model. For now however, the scope of this Ticket is to is to plumb these from the top-level down to the surf_couple* layer (which is the branching point between LSM_ID = JULES or CABLE). This layer is also the interface layer between the UM and JULES. Thus changes to the argument list entering this layer requires a UM linked ticket as well as changes to JULES standalone IO. Intended changes subsequent to this Ticket can be limited to the JULES code base until lsm_id=CABLE is finalized in the Standalone version.

The branches are at:

JULES

TRAC

svn

UM

TRAC

svn

For the UM there is only one revision from the trunk. For JULES, there is only 1 revisions after branching from the trunk and merging Ticket# . Here are the changesets for:

UM.

JULES.