Home page  
Home   Your Room   Login   Contact   Feedback   Site Map   Search:  
Discover this product  
About Us
Overview
Getting here
Committees
Products
Forecasts
Order Data
Order Software
Services
Computing
Archive
PrepIFS
Research
Modelling
Reanalysis
Seasonal
Publications
Newsletters
Manuals
Library
News&Events
Calendar
Employment
Open Tenders
   
Home > Research > Ifsdocs > OBSERVATIONS >  
   

IFS documentation Front Page


Table of contents
Chapter 1. Non-IFS observation processing (OBSPROC): General overview

Chapter 2. Observations: Types, variables and error statistics

Chapter 3. CMA creation (MAKEMA)

Chapter 4. The FEEBACK task

Chapter 5. The TOOLS task

Chapter 6. Central-memory array (CMA) structure/format

Chapter 7. BUFR feedback data structure/format

Chapter 8. SIMULATED-observations data structure/format

Chapter 9. NAMELISTS

Chapter 10. Processing of scatterometer data

REFERENCES
 
  Next Section
Previous Section


5.1 Basic principles




The main purpose of this task is to perform various observation-processing-related diagnostics/debugging activities outside the data-assimilation cycle. By having it as a part of the OBSPROC, one makes use of the existing code structures already developed for two main tasks, the MAKECMA and the FEEDBACK.


There are three types of activities (sub-tasks) within the TOOLS task. These sub-tasks are:
  •   CMA tools;
  •   BUFR tools; and
  •   SIMULATED-observations tools.


As their names imply they are related to the specific data structures.


The TOOLS task, as with the other two, is invoked by starting the OBSPROC, via program AAOBPPRO. The subroutine CNTOBSPR is called next which in turn, after finding out that the TOOLS task is to be carried out, branches itself and calls the TOOLS subroutine (see Fig. 1.2 and Fig. 1.3 of Chapter 1 `Non-IFS observation processing (OBSPROC): General overview' ).


Once in the TOOLS subroutine (see Fig. 5.1 ) a partial pre-set is carried out first. This pre-set includes setting up the definitions of:
  •   numerical limits (SULIM),
  •   variables' numbers (SUVNMB),
  •   level/layers structure (SULEVLAY),
  •   CMA observation and code types (SUCMOCTP),
  •   BUFR observation types and subtypes (SUBUOCTP),
  •   observation events (SUEVENTS),
  •   observation flags (SUFLTXT),
  •   various observation processing codes (SUCODES),
  •   BUFR data structure and format (SETBUFR),
  •   SIMULATED observation structure and format (SUSIM),
  •   CMA data structure and format (SUCMA),


The next step is to print the chosen run set-up by calling PREAMB subroutine. Then, depending on the status of the NAMDIA namelist switches LCMATOOL, LBUFTOOL and LSIMTOOL, it will branch itself off to an appropriate section and start the sub-task. The CMA tool sub-task is invoked if LCMATOOL=.T., whereas the BUFR tool and the SIMULATED-observations tool are started if LBUFTOOL=.T. or LSIMTOOL=.T..


Before either of these two routines is called, the CMA file is initialized (INICMAIO) and the CMA DDRs read. As the read-in DDRs are reals at this stage, their integer and character sections are worked out by calling the CONRCD2I and CONRCD2C subroutines, respectively. Furthermore, at this stage, if the NAMDIA namelist switches LOPRCMD=.T., the CMA DDRs will be printed out (PRTDDR). The NAMDIA namelist switches the LOPRCMA and LCONVER control if either the IRETCMA or ICONVERG subroutine is called next. IRETCMA is the master subroutine for printing the CMA reports, whereas ICONVERG is the master routine for the convergence test. After returning from either of these two routines, some diagnostic print takes place by calling either the CMASTA or CONVSTA subroutine. The last step is to close the input CMA file (FINCMAIO).
Figure 5.1 Subroutine TOOLS flow diagram



Next Section
Previous Section



 

Top of page 16.04.2002
 
   Page Details         © ECMWF
shim shim shim