FRErator – the Bridge between FRE and Curator DB

Uniform, Economical Approach  DB makes easy the reusability of blocks needed for building and configuring new model and running experiments.  Metadata giving full description of models, platforms, and runs helps in analysis and making decision.  Metadata written in Curator DB during experiment is used for Data Portal support. Automation saves user time in registering new experiment and making it published on Data Portal Automation saves user time in registering new experiment and making it published on Data Portal Metadata about current experiments runs updated in real-time informs users about status of their jobs Metadata about current experiments runs updated in real-time informs users about status of their jobs

Role of Curator DB on different stages of modeling process Curator DB Curator DB Metadata and Configuring Data - Curator DB Component Building Model Assembling Experiment Preparation Postprocessing Data Portal Service FMS Runtime Environment in development currently

Modes of working with database  Research mode - modeler introduces new algorithmizations and new components from newly developed modules for future usage in coupled models. New components are to be described in database manually (not from rts.xml). The model runs conducted for this developed purpose are not to be recorded in DB excepting final ones proving physical correctness of new approach.  Production mode – experimenter composes coupled model from available components described in database, builds scenario, postprocessing plan using GUI and runs experiment. All this activity is recorded in database automatically.  Automatic mode – applications fill metadata and config data into database grabbing it from rts.xml file (created manually) during running FRE tools.

Current usage of Curator DB  DB serves for GFDL Data Portal web site for data discovery and navigation: IPCC CM2.1. The daemon screens Data Portal storage seeking newly put data files and records metadata extracted from files and system information about them into DB. IPCC CM2.1IPCC CM2.1  DB is used for bringing metadata consistency data files on Data Portal with accepted standards (described in DB). The application accesses to DB for metadata standard for given file and compares/fixes it in the file.  DB contains aggregation datasets and used by automatic tool for configuring THREDDS Aggregation Server.  Curator DB is a backend DB for GFDL LAS (LASurator)  And perspective usage – FRE backend DB and metadata/configdata resource in modeling process workflow.

What we have now  Designed Curator DB intended not only for model configuring data but also for metadata describing models.  Automatic tool FRErator mapping and writing rts.xml into Curator DB. It’s highly configurable to handle wide range of xml schemas. It will be invoked (by user’s desire) from FRE tools. (See life demo)  Pilot version of web interface for viewing model metadata/configdata from DB. interface interface

FRErator is easy configurable tool working with arbitrary xml schema. FRErator is easy configurable tool working with arbitrary xml schema. Configuration file rts.xsm (xml schema mapping) has xml schema syntax expanded with mapping attributes: map, mapGroup, mapPrimKey, mapFKey, mapGlbFld, mapRule, Group, mapGroup. Configuration file rts.xsm (xml schema mapping) has xml schema syntax expanded with mapping attributes: map, mapGroup, mapPrimKey, mapFKey, mapGlbFld, mapRule, Group, mapGroup.  The fragment of rts.xsm: _____________________________________________________________________________________________________________________________________________________________________________________________________________________________ <element ref="parameter“ <element ref="parameter“ mapGroup="ParamsGroups.param_group_content_id|ParamGroup_Contents.param_group_content_id"/> mapGroup="ParamsGroups.param_group_content_id|ParamGroup_Contents.param_group_content_id"/> <attribute name="name" map="ParamsGroups.param_group_name " <attribute name="name" map="ParamsGroups.param_group_name " mapPrimKey = " ParamGroup_Contents.param_group_content_id, ParamsGroups.param_group_id" mapPrimKey = " ParamGroup_Contents.param_group_content_id, ParamsGroups.param_group_id" mapRule ="RANDOM_ID" /> <text map="ControlledParams.param_prog_name, ParamValues.param_value" <text map="ControlledParams.param_prog_name, ParamValues.param_value" mapPrimKey =" ControlledParams.param_id, ParamValues.param_value_id" mapPrimKey =" ControlledParams.param_id, ParamValues.param_value_id" mapFKey = " ParamGroup_Contents.param_id|ControlledParams, ParamGroup_Contents.param_value_id|ParamValues" mapFKey = " ParamGroup_Contents.param_id|ControlledParams, ParamGroup_Contents.param_value_id|ParamValues" mapRule = "SEMICOLON_SPLIT,EQUAL_SPLIT,RANDOM_ID,GROUP" /> mapRule = "SEMICOLON_SPLIT,EQUAL_SPLIT,RANDOM_ID,GROUP" /> <attribute name="name" map="ControlledParams.param_prog_name" <attribute name="name" map="ControlledParams.param_prog_name" mapPrimKey="ControlledParams.param_id" mapPrimKey="ControlledParams.param_id" mapFKey="ParamGroup_Contents.param_id" mapRule="RANDOM_ID" /> mapFKey="ParamGroup_Contents.param_id" mapRule="RANDOM_ID" /> <text map="ParamValues.param_value" mapPrimKey="ParamValues.param_value_id" <text map="ParamValues.param_value" mapPrimKey="ParamValues.param_value_id" mapFKey="ParamGroup_Contents.param_value_id" mapFKey="ParamGroup_Contents.param_value_id" mapRule="RANDOM_ID" /> mapRule="RANDOM_ID" /> __________________________________________________________________________________________________ FRErator design

Will map the such tags: max_input_fields = 400; max_output_fields = 500; mix_snapshot_average_fields=.true. …. …. 1, 1, 1, 0, 0 1, 1, 1, 0, 0.false..false. "bogus" "bogus" ….. …..

What we need else  Automatic Tool generating canonical rts.xml from DB  Editing GUI allowing user to select needed preexisting components and configurations from DB, edit them on a fly write into DB and generate new rts.xml.