短发女生穿衣搭配技巧.pptVIP

# create metadata for SST experiment ? $exp = createExperimentMetadata(avhrr_sstModel); $exp_step = createExpStepMetadata($exp, avhrr_sstExpStp); ? addValue($exp_step, avhrr_sstExpStp.base_temp, $base_temp); addValue($exp_step, avhrr_sstExpStp.temp_step, $temp_step); ... ? saveToDB($exp_step, avhrr_sstExpStp); closeMetadata($exp_step); # connect input and output images to experiment ? registerExperimentInputs($exp, $L1B_ID); registerExperimentOutputs($exp, $SST_ID); ? # finish recording ESSW metadata ? endXMLBld(); AHVRR Level 1B product Multi-channel sea surface temperature algorithm Sea surface temperature (SST) avhrr_ sstModel avhrr_l1b avhrr_sst Wrapper Example: Lineage Links Process graph reconstructedfrom ESSW database ESSW Lessons Providers are customers ESIPs aren’t much good unless scientists are happy to put information in them A light touch is the right touch Wrapping is easier for scientists and their programmers to deal with than complete re-engineering Scientists do write scripts, but not necessarily Perl Scripting (gluing stuff together) comes naturally to scientists Scientists don’t write DTDs Nobody calls metadata APIs ESSW was automatic, but not automatic enough… Lineage Capture, Take 2 The ES3 experience ES3 : Earth System Science Server ESSW++ data lineage tracking BUB data storage ROCKS processing clusters Alexandria Digital Library Microsoft TerraServer MODster OpenDAP MODIS Corona AVHRR Watershed-scale snow product Global-scale snow product From ESSW to ES3: Summary Perl wrappers ? “Probulators” Perl API ? web services + XML messages MySQL ? XML database(s) From Wrappers to Probulators Wrappers: Active Lineage + Complete control over what gets recorded Single language/API for all wrapped events Not tied to execution You can even lie about what happened – Must explicitly script everything Scripts can drift from reality You can even lie about what happened From Wrappers to Probulators Probulators: Passive Lineage + Record what