Changes between Version 5 and Version 6 of AuxiliaryRoutines


Ignore:
Timestamp:
Dec 21, 2016, 1:29:50 PM (4 years ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AuxiliaryRoutines

    v5 v6  
    6767== PDAF-D_get_memberid.F90 ==
    6868
    69 This routine can be called from the model during an ensemble integration. It provides access to the number (id) of the ensemble member that is currently intrated.
     69This routine can be called from the model during an ensemble integration. It provides access to the number (id) of the ensemble member that is currently integrated.
    7070
    7171{{{
     
    7878Note:
    7979 * Using `PDAF_get_memberid` is obviously only useful if more than one ensemble member is integrated by a model task. If there are as many model tasks as ensemble members, `memberid` is always 1. In this case one can use `task_id` from the module `mod_parallel` to distinguish the ensemble members.
     80
     81
     82== PDAF-D_get_obsmemberid.F90 ==
     83
     84This routine can be called from the model during the analysis step. It provides access to the number (id) of the ensemble member for which the user-routine for the observation operator is called.
     85
     86{{{
     87CALL PDAF_get_obsmemberid(memberid)
     88}}}
     89
     90The only argument is:
     91 * `memberid`: In integer providing on output the id the ensemble member
     92
     93Note:
     94 * The routine an be useful if the observation operator does not actually operate on the state vector that is provided when [wiki:obs_obs_pdaf] is called. Their might be cases in which one likes to read model state information from a file (e.g. if the observation operator performs an averaging over time, while the state vector for the analysis step only contains a single time instance).
     95
    8096
    8197