This structure was proposed by Jan (and Reiner ?) (27/06/2002)
Responsibilities of partners in the PSMILe development
Based on the above description of the PSMILe internal element structure
and on the definition of tasks and repartition among the partners agreed
on at the 19/04/2002 Toulouse meeting (see http://www.cerfacs.fr/PRISM/MTCI/minutes_WP3aWP4a_190402.htm),
I propose the following leaders for the development of the different PSMILe
internal elements :
- NEC-CCRLE:
- Execution tree
- Internal interface to (I/O) and coupling
- Data Management
- Metadata management
- Coupling
- IPSL:
- Calendar
- Access to SMIOC and SCC
- Internal interface to I/O (and coupling)
- Metadata management
- Input/output
- Error handling
- Monitoring (What is this? Are these the checks of coherence?)
- CERFACS
- Local transformations
=> 2 - Routines for initialisation, setup, and termination
(PRISM_init , PRISM_init_comp, PRISM_get_localcomm, PRISM_initialized (?), PRISM_setup/enddef, PRISM_decommission(?), PRISM_terminate, PRISM_terminated (?) )
=> 3 - Routines for grid declaration
(PRISM_def_grid, PRISM_set_center_xx, PRISM_set_xcorners_xx, PRISM_set_mask, PRISM_set_scalefactor, PRISM_set_angle, ...)
=> 4 - Routines for transient variable declaration
(PRISM_def_var)
=> 5 - Routines for sending and receiving transient variables
(PRISM_put, PRISM_get, PRISM_iput, PRISM_iget, PRISM_wait)
=> 6 - Different utility routines for the component models
(PRISM_query_var, PRISM_error )
=> 4 - Routines for transient variable declaration
(PRISM_def_restvar)
=> 6 - Different utility routines for the component models
(PRISM_get_persist, PRISM_def_startdate, PRISM_calc_newdate, PRISM_calc_nbtstp, PRISM_error )
=> 3 - Routines for grid declaration
(PRISM_def_grid, PRISM_set_center_xx, PRISM_set_xcorners_xx, PRISM_set_mask, PRISM_set_scalefactor, PRISM_set_angle, ...)
=> 6 - Different utility routines for the component models
(PRISM_timestamp, PRISM_restartsaved, PRISM_message)