1 / 31

3SAQS Technical Workshop May 29-30, 2013 Data Warehouse Update, Assessment, and Work Plan Review

3SAQS Technical Workshop May 29-30, 2013 Data Warehouse Update, Assessment, and Work Plan Review. Zac Adelman (UNC-IE) Shawn McClure (CSU-CIRA) Tom Moore (WGA-WRAP). Summary Status of 3SAQS Technical Work Completed To Date Via Cooperative Agreements.

oistin
Télécharger la présentation

3SAQS Technical Workshop May 29-30, 2013 Data Warehouse Update, Assessment, and Work Plan Review

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. 3SAQS Technical Workshop May 29-30, 2013 Data Warehouse Update, Assessment, and Work Plan Review Zac Adelman (UNC-IE) Shawn McClure (CSU-CIRA) Tom Moore (WGA-WRAP)

  2. Summary Status of 3SAQS Technical Work Completed To Date Via Cooperative Agreements

  3. Review of the 3SDW Overall System Ecosystem and Architecture

  4. Summary of Past Quarter Activities • Continued to refine the database, software, and website infrastructure supporting the data warehouse • Refined various pre-processing components • XML Generator for metadata • SQL scripts for importing modeled emissions data • Extended portions of the data import system • SQL scripts for importing modeled emissions data • Integration layer for the Emissions Management Framework (EMF) • Refined the logical and physical file system design • Refined the data verification and validation system • Refined the system for acquiring and managing emissions data

  5. Summary of Past Quarter Activities (cont’d) • Interviewed several applicants for the TSDW software developer position • Offered the position to the best candidate and received a verbal acceptance • Candidate reneged on their acceptance the week before starting the appointment • Designed an alternate plan for continuing the work plan with minimal impacts via an increased involvement by UNC • Populated the data warehouse with the full complement of WestJump Base08b CAMxInput/Output data for June/July ‘08 • Refined the modeled emissions review tool • Conducted the First Use Case Beta Test

  6. Operational Website Components • User Login Form • User Registration/Modification Form • User Profile/Account Form • User Feedback Form • Dataset Request Form • Database Query Wizard • Raw Data Download • Interactive Charts • Dynamic Contour Maps • Site Metadata Reports • Monitoring Site Metadata Browser • File Explorer Authentication and Authorization System

  7. Future Website Components • Modeled Emissions Summary Tool • Modeled-to-Observed Data Comparison Tool • Air Quality Summary Reports • Visibility • Deposition • Ozone • Other • Model Data Mapping Tool • Source Apportionment Tool • Various Unpublished Monitoring Data Tools • Backend Web Services and Processing Components

  8. User Login Form

  9. User Registration/Modification Form

  10. User Profile/Account Form

  11. User Feedback Form

  12. Dataset Request Form

  13. Raw Data Download (Query Wizard)

  14. Time Series Charts (Query Wizard)

  15. Dynamic Contour Maps (Query Wizard)

  16. Site Metadata Report (Query Wizard)

  17. Monitoring Site Browser

  18. Modeled Emissions Summary Tool

  19. Modeled-to-Obs Comparison Tool

  20. Air Quality Summary Reports

  21. Model Data Mapping Tool

  22. Future Online Visualization Tools

  23. First TSDW Modeling Use Case Report and Results

  24. First Use Case - Beta Test Steps • Testers visited the TSDW website and registered with the system to create an account • Testers visited the Data Request web page and entered their requests for the WestJump Base08b dataset • Each request was stored in the database • The system determined whether or not each request could be automatically filled or had to be manually assembled • The system sent emails to the appropriate TSDW team members to notify them of the data requests • TSDW team members assembled the dataset requests (copied the relevant data files onto hard drives) • The datasets (hard drives) were delivered to the beta testers • The system updated the dataset requests to reflect their “filled” status

  25. First Use Case - Beta Test Steps (cont’d) • Using the delivered datasets, testers ran the models and generated results • Testers returned the model output results to the 3SDW • The test results were assessed by TSDW team members • Testing outcomes were summarized for the May 3-State AQ Study Technical Workshop • The TSDW team refines the dataset ordering, download, packaging, and delivery system according to lessons learned • The TSDW team develops the nextUse Case testing scenario(s)

  26. Summer (June – October) 2013 3SAQS Technical Work Review Data Warehouse Activities

  27. Summary of Coming Activities • Implement the collaborative components of the warehouse • Implement the ongoing news and updates section • 3SDW on-line for NEPA air quality analysis projects by end of October • Out-bound data delivery and in-bound data ingestion for NEPA and other air quality studies • Data warehouse operations (hosting, data analysis and processing, maintenance, et cetera) • Plans for storage/access/visualization for modeling results and evaluation tools • Store UT BLM ARMS and other studies’ data in 3SDW after evaluation using protocols

  28. Testing and Refinement Help • All users, collaborators, and partners can help with testing • Please report bugs – don’t endure them • Use the website Feedback form • Send direct email to team members • Provide as much information as possible up-front • Stay abreast of ongoing additions and updates • Be an active part of the design process - make suggestions for features and refinements • Don’t assume it can’t be done • Don’t assume it can be done

  29. Thanks.

More Related