Changes between Initial Version and Version 1 of CDB_Out_In


Ignore:
Timestamp:
09/04/12 19:52:48 (8 years ago)
Author:
lalibert
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CDB_Out_In

    v1 v1  
     1= Using an output in another computation = 
     2The CDB was conceived in such way that it is easy to use the output from one diagnostic into another diagnostic. Among other things, this provides simple server-side processing framework. 
     3 
     4To output the result of a diagnostic for reuse into another diagnostic, one simply has the frequency and realm of output files in the CDB_CMIP5_COMP_LIST bash variable at the end of a diagnostic script. In the tas_zonal example, this list was: 
     5{{{ 
     6 CDB_CMIP5_COMP_LIST="\ 
     7${CDB_OUT_DIR}/${CDB_OUT_FILE}.daily;day,atmos,day \ 
     8${CDB_OUT_DIR}/${CDB_OUT_FILE}.monthly;mon,atmos,Amon \ 
     9" 
     10}}} 
     11This will output the .daily variables as atmospheric daily variables and .monthly variables as atmospheric monthly variables. '''Note that there must be a space between list entries for this feature to work properly.''' 
     12 
     13The output will be found in CDB_OUT_DIR/tas_zonal/in and will be structure as ESG data. If one would like to use these variables in another hypothetical diagnostic named 'tas_stats_zonal', one would move the directory CDB_OUT_DIR/tas_zonal/in to CDB_IN_DIR/tas_stats_zonal. When running the tas_stats_zonal diagnostic, the retrieval script will find the variables and retrieve them as if they were part of the local ESG archive.