1 / 8

FRErator – the Bridge between FRE and Curator DB

FRErator – the Bridge between FRE and Curator DB. Role of Curator DB on different stages of modeling process. in development currently. Data Portal Service. FMS Runtime Environment. Postprocessing. Experiment Preparation. Model Assembling. Component Building.

santos
Download Presentation

FRErator – the Bridge between FRE and Curator DB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FRErator – the Bridge between FRE and Curator DB

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

  3. 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.

  4. 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. • 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.

  5. 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 interfacefor viewing model metadata/configdata from DB.

  6. FRErator design • 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. • The fragment of rts.xsm: _____________________________________________________________________________________________________________________________________________________________________________________________________________________________ <element name="parameterGroup"> <complexType mixed="true"> <all Group="parameter"minOccurs="0"> <element ref="parameter“ mapGroup="ParamsGroups.param_group_content_id|ParamGroup_Contents.param_group_content_id"/> </all> <attribute name="name" map="ParamsGroups.param_group_name" mapPrimKey="ParamGroup_Contents.param_group_content_id, ParamsGroups.param_group_id" mapRule="RANDOM_ID" /> <text map="ControlledParams.param_prog_name, ParamValues.param_value" mapPrimKey="ControlledParams.param_id, ParamValues.param_value_id" mapFKey="ParamGroup_Contents.param_id|ControlledParams, ParamGroup_Contents.param_value_id|ParamValues" mapRule="SEMICOLON_SPLIT,EQUAL_SPLIT,RANDOM_ID,GROUP" /> </complexType> </element> <element name="parameter" maxOccurs="unbounded"> <complexType mixed="true"> <attribute name="name" map="ControlledParams.param_prog_name" mapPrimKey="ControlledParams.param_id" mapFKey="ParamGroup_Contents.param_id" mapRule="RANDOM_ID" /> <text map="ParamValues.param_value" mapPrimKey="ParamValues.param_value_id" mapFKey="ParamGroup_Contents.param_value_id" mapRule="RANDOM_ID" /> </complexType> </element> __________________________________________________________________________________________________

  7. Will map the such tags: <parameterGroupname="diag_manager_nml"> max_input_fields = 400; max_output_fields = 500; mix_snapshot_average_fields=.true. …. </parameterGroup> <parameterGroupname="aerosolrad_package_nml"> <parametername="volcanic_dataset_entry">1, 1, 1, 0, 0</parameter> <parametername="using_volcanic_lw_files">.false.</parameter> <parametername="lw_ext_filename">"bogus"</parameter> <parametername="lw_ext_root">" bogus"</parameter> <parametername="lw_asy_filename">" bogus"</parameter> <parametername="lw_asy_root">"bogus "</parameter> <parametername="lw_ssa_filename">" bogus"</parameter> <parametername="lw_ssa_root">"bogus "</parameter> ….. </parameterGroup>

  8. 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.

More Related