1 / 21

Data Delivery

Data Delivery. Agenda- Data Delivery. Topics covered : Science/Operator/Education/Public  Use Cases , User requests and Data Product Generation , Operator Use Cases (mobile, uncabled and cabled), Command & Control

liam
Télécharger la présentation

Data Delivery

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. Data Delivery

  2. Agenda- Data Delivery Topics covered: Science/Operator/Education/Public  Use Cases , User requests and Data Product Generation , Operator Use Cases (mobile, uncabled and cabled), Command & Control Addresses: C?#2= How well will the data management plans and processes serve the OOI users as defined by the presented use cases ? Are there any gaps identified, critical weaknesses or recommendations for improvement? 1

  3. Bottom Line of ‘Data Delivery’ • Physical and functional/logical data pipeline design just presented • Now that we have all the ‘front-end’ items, it’s the user and their needs that determine success or failure • How Users Get the Data- • OOI is, to the science user, a website • How do we judge? 2

  4. How Is OOI Judged? • Initial; then Matured Use Cases • Marine Operator • Science user • Educator • Requirements Verification • Beta Testing • Validation Testing • User Community 3

  5. Existing Use Cases Many ‘system’ and not user focused 54 Use cases developed by CI for most recent release

  6. Example of Existing Operator Use Case

  7. Example of Existing Operator Use Case • Scenario for "Command Instrument" Use Case • User determines what command(s) he or she wants to give to a given instrument. • User accesses that instrument's general instrument interface supplied by CI, and learns whether he/she has access to the necessary commands. • If the user can exercise desired commands only with permission, the permissions are requested by the system. • Commands available through the general interface may be accessed directly through the interface. • (optional) User adds batch command for the instrument • Ready-to-execute commands are directed to the Instrument Agent. • The Instrument Agent uses its knowledge of the instrument to assess command validity under current operating conditions. • The Instrument Agent conveys the command to the instrument. • The Instrument Agent logs and returns any immediate response, and announces any resulting state changes. • The instrument response and any resulting operational state changes are reflected in the user's view • The instrument agent additionally returns any subsequent status or completion responses. And the capability to control the instrument is released • The previously supplied command identifier is used to identify all such responses. Many “COULD”, “AGENT”, and vague phrases

  8. Marine Operator use case summary (draft) • Perform Command And Control Of Deployed Assets • Monitor System Health And Status And Act Per Procedures • Submit Data To National Archive(s) • Perform HwAnd/OrSw Updates • Operator Synchronizes Observatory Configuration Across Data System And Document System • Manage OOI Homepage (System Information Portal) And Trouble Reports • Establish / Alter / Maintain The Configuration Of OOI • Provide External Pi Support Needed to be specific and detailed 7

  9. Example of Updated Operator Use Case NEED STATEMENT: The MIOs must perform command and control of their assets SCENARIOS: Mobile device: A glider pilot needs to change the way points and dive pattern of a single glider to lower the overall power consumption Steps: The MIO O&M Lead and MIO engineering team … Cabled device: The sampling rate for an instrument needs to be changed due to an underwater event of scientific interest. Steps: The marine operator (MO), with facility permission, logs onto OOINet…. Uncableddevice: Sudden EVENT: The METBK package on a global mooring needs to be shut down because it sent an alarm of excessive power draw. Steps: The MO on-call receives the alarm via cell phone while sleeping. …..

  10. Science use case summary (draft) • Search, Locate and download OOI data • Search, Locate and download OOI documents, reports • Add or retrieve ancillary data related to an OOI deployment/recovery cruise • Subscriptions • Examine a data product for consistency and quality 9

  11. Search, Locate and download OOI data • Most fundamental task • Pick area, find product 10

  12. Search, Locate and download OOI data • Most fundamental task • Pick time, examine/look at, download • Download formats include NetCDF, CSV, Matlab, HTML, PNG (map plot), PDF • Download URL accessible from external tools, e.g. Matlab using DAP protocol 11

  13. Search, Locate and download OOI documents, reports • Data is only part of the need • Pick array- find document, read/download •Coastal Glider, June 2011 ◦Glider specifications •Open Ocean Glider, October 2011 ◦Glider specifications •Global Hybrid Profiler Mooring, May 2012 ◦Top-level drawings •Global Mesoscale Flanking Mooring, May 2012 ◦Top-level drawings •Global Surface Mooring, July 2012 ◦Top-level drawings •Coastal Surface Mooring, July 2012 ◦Top-level drawings •Coastal Profiler Mooring, July 2012 ◦Top-level drawings •Endurance Array Benthic Experiment Package, May 2012 ◦Top-level drawing •Operations and Management Component, January 2013 •AUV/AUV Dock System, February 2013 •Uncabled Coastal Surface Piercing Profiler, Sept 2013 •Cabled Coastal Surface Piercing Profiler, Mar 2014 12

  14. Add or retrieve ancillary data related to an OOI deployment/recovery cruise All arrays have pages • For a summary of the July 2013 Station Papa Deployment, click here » Click to download a PDF of all Infrastructure Tables Click the below links for individual Instrument Tables (A) Hybrid Profiler Mooring(B) Flanking Mooring A(C) Flanking Mooring BMobile Assets – Gliders Technical Drawings » Click here for the online Technical Data Package Click the below links for High-Level Technical Drawings (A) Hybrid Profiler Mooring(B, C) Flanking Mooring 13

  15. Subscriptions 12 predefined “events” can be subscribed 14

  16. Examine a data product for consistency and quality Check the Metadata 15

  17. Educational Community use case summary 16

  18. User Request and Data Product Generation User Interface Infrastructure / Database- Postgress Product Catalog Product Generation 17

  19. Output Data Product Variables • Each L1 and L2 product has the following variables (i.e., columns in the time series): • Time • <measurement>_L1a (e.g., Conductivity_L1a) • <measurement>_L1b_Post_Deployment_Cal • <measurement>_L1b_Post_Recovery_Cal • <measurement>_L1c • QC_Flag_GlobalRange • QC_Flag_LocalRange • <additional QC flags> • Single “Parsed”(Combined) product per instrument, with all variables for applicable L1 and L2 products, additional time stamps

  20. Output Data Product Metadata • In the metadata (i.e., ‘Metadata’ link from ERDDAP page, AND metadata on Data Product facepage on OOINet UI): • Calibration coefficients (as a comma separated list) • QC Look Up Table (as a url) • Data Product Algorithm code (as a url) • DPS for Data Product Algorithm (as a url) • QC Algorithms (as urls) • DPS’s for QC Algorithms (as urls)

  21. Summary Data Delivery Issues Use case completion User Interface completion Visualization options

More Related