1 / 74

OPUS Projects

OPUS Projects. Mark Schenewerk mark.schenewerk@noaa.gov 816-994-3067. Outline. Introduction (  30 min) Overview (  40 min) Publishing (  30 min) Discussion (  20 min). What is OPUS Projects?.

oriole
Download Presentation

OPUS Projects

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. OPUS Projects Mark Schenewerkmark.schenewerk@noaa.gov816-994-3067 OPUS Projects

  2. Outline • Introduction ( 30 min) • Overview ( 40 min) • Publishing ( 30 min) • Discussion ( 20 min) OPUS Projects

  3. What is OPUS Projects? OPUS Projects is a follow-on to OPUS offering Web-based access to simple visualization, management and processing tools for multiple marks and multiple occupations. Some of its advantages include: • Data uploading through OPUS. • Processing using the PAGES software. • Graphical visualization and management aids. • Limited support of bluebooking. OPUS Projects

  4. Why complicate OPUS? OPUS CORS5 CORS3 Session CORS2 CORS1 CORS4 Adjustment solution MCCOY solution HATFIELD OPUS Projects

  5. Why complicate OPUS? OPUS CORS5 CORS3 Session CORS2 CORS1 CORS4 Adjustment solution MCCOY solution HATFIELD session 001 OPUS Projects

  6. Why complicate OPUS? OPUS CORS5 CORS3 Session CORS2 CORS1 CORS4 Adjustment solution MCCOY solution HATFIELD session 001 session 002 session N OPUS Projects

  7. Why complicate OPUS? OPUS CORS5 CORS3 Session CORS2 CORS1 CORS4 Adjustment solution MCCOY solution HATFIELD session 001 session 002 session N network adjustment OPUS Projects

  8. Do we really need another OPUS flavor? • The practical answer is probably yes.The NGS, its partners and stakeholders have a history of projects whose specifications can’t be entirely supported by OPUS. • The academic answer is probably yes.As good as OPUS does, and that is very good indeed, sacrificing simplicity for flexibility can improve results. OPUS Projects

  9. What’s all that really mean for me? OPUS solutions = pretty good, but each treated as independent and assumes “perfect” CORS. Sessions = simultaneously-observed marks processed together in sessions increases consistency. Adjustments = interlinking sessions through network adjustments increases accuracy. OPUS Projects

  10. Are There Any Other Advantages? • Faster, simpler setup • A project’s data are consolidated in on-line storage. • Initial data quality assessments provided on upload. • The data are organized automatically. • Faster, simpler work flow • Project specific preferences and the on-line GUI simplifies running PAGES. • Software and models are always up-to-date. • The quality of the processing results is visually indicated in maps, plots and tables. • Many useful files are created automatically. OPUS Projects

  11. Any Limitations? • Internet access is required. • OPUS Static upload restrictions apply. • Dual-frequency pseudorange & phase. • 2 hrs ≤ data span ≤ 48 hrs. • Observation interval = a factor of 30 (seconds). • Minimum project size. • 1 data file from 1 mark. • Maximum project size. • About 100 marks in a single session. • Number of data files < a few hundred. OPUS Projects

  12. What does this mean operationally? Broadly speaking, we used to do something like … • Plan your project • Collect data and metadata • Gather data and metadata onto one computer • Format and organize the data and metadata • Process the data • Perform a network adjustment • Publish (if desired) OPUS Projects

  13. What does this mean operationally? Now we’ll do something like … • Plan your project • Create an OPUS project • Collect data and metadata • Upload data and metadata to project using OPUS. • Process sessions • Perform network adjustment • Publish (if desired). OPUS Projects

  14. Making Our Tech Simple. • Our stakeholders should not need to know: • The rules for our file names and formats. • The minutia of our processing software. • Our stakeholders should feel confident: • They can process data successfully. • They’ll get results quickly and easily. • Their results will be high quality. OPUS Projects

  15. G.I.G.O. • Good coordinates come from good data collected using good practices. We hope OPUS Projects can help make processing and publishing easier, but it can’t spin straw into gold. Folks still need to: • Follow their project’sspecifications. • Use best practices andcareful field procedures. • Select permanent marksof public interest. http://gis.larc.nasa.gov/ OPUS Projects

  16. OPUS Projects Training Because of its increased complexity, training is required to be an OPUS Projects manager. Workshops are small allowing ample time for one-on-one interaction with the instructor. The NGS Training Center will schedule workshops run by NGS.

  17. What Groups Have Been Trained 317 From All Groups 159 From GOV (US) As of July 30, 2013. OPUS Projects

  18. Activity To Date • 1018 projects created by 242 active project managers • 2006 - 3 • 2007 - 3 • 2008 - 0 • 2009 - 7 • 2010 - 56 • 2011 - 294 • 2012 - 474 • 2013 - 181 As of July 30, 2013. OPUS Projects

  19. What Groups Are Active in 2013 57 Managers Creating Projects 168 Projects Created As of July 30, 2013. OPUS Projects

  20. Activity In 2013 • 168 (133/35) projectscreated by 57 (38/19) managers • 495 (495/367) largest number of files • 6 ( 6/ 8) median number of files • 118( 93/118) largest number of marks • 3( 3/ 4) median number of marks • 53 ( 53/ 13) largest number of days • 2 ( 2/ 2) median number of days • 69 ( 69/ 30) largest number of sessions • 3 ( 3/ 2) median number of sessions As of July 30, 2013. OPUS Projects

  21. Resources: Command & Control • OPUS Projects czar is the internal point of contact. • OPUS oversight committee will oversee. • SRSD will have logistical control. • SDD will be responsible for Web-based interface with support from GRD. • GRD will be responsible for maintenance and development with input from GSD, OAD, SDD, SRSD and stakeholders. Transition to joint GRD, SDD and SRSD responsibility over the next year. • SAB will be responsible for training/outreach. • ngs.opus.projects@noaa.gov, the Info and Training Centers will be public points of contact. OPUS Projects

  22. Resources: Computation • An average processing request takes about 10 min, but a larger project can take significantly longer.A primary machine with 4 – 8 CPUs. • Training is a special case. Here, we can see 20 to 30 processing requests in a few minutes creating the potential for a several hour wait.A second machine with 4 – 8 CPUs. • A second machine offers the possibility of diverting resources for larger NGS projects when needed if training is not being offered. OPUS Projects

  23. Resources: Storage As a guess, NGS should prepare for (using 2013 mean): ~7 days duration ~7 CORS data files per day at 3.8 mB per file. ~32 user files per project at 0.89 mB per file. ~ 2 for solution files, reports, photos, etc. ~250 projects per month (1% of OPUS use). 0.43 gBper project = 2  (3.8 mB7 7 + 0.89 mB 32). 110 gB per month = 0.43 gB250. 1300gB per year = 110 gB 12. OPUS Projects

  24. A Quick Overview of OPUS Projects Now we’ll review some of the features of OPUS Projects. OPUS Projects

  25. The OPUS upload page is the access point for all things OPUS.

  26. Note the “Projects” link on the left. This will take you to the OPUS Projects gateway page.

  27. This is the OPUS Projects gateway page.

  28. It allows users to create projects (assuming they’ve received OPUS Projects manager training).

  29. Access a project for session processing. OPUS Projects

  30. Or manage a project including perform a network adjustment. OPUS Projects

  31. Let’s start our exploration with the manager’s page for a project. OPUS Projects

  32. This is the manager’s page for project HRDB86FC. OPUS Projects

  33. The menu at the top of the page selects the type of solution or solutions for display. OPUS Projects

  34. Once Session processing has been completed, Session and OPUS solutions will be available. Network adjustments will be available too as they are completed. OPUS Projects

  35. The sidebar on the left contains the controls for the manager’s page. OPUS Projects

  36. The map shows the relative location of the project’s marks. If the Session solutions were completed, they would be shown, but the OPUS solution results can always be displayed. OPUS Projects

  37. The sidebar on the right lists the marks alphanumerically but segregated by project and CORS marks. OPUS Projects

  38. The table at the bottom of the page gives summary of the session, marks in those sessions and the quality of the solutions for the marks in the project. OPUS Projects

  39. The summary table is also a navigation tool to other pages in the project. OPUS Projects

  40. The column headers are links to individual Sessions (and later, session solutions). OPUS Projects

  41. The row headers are links to individual marks. OPUS Projects

  42. The project manager has a number of controls available. The Preferences button opens a window with controls to change the project title and keywords, email lists and project preferences. OPUS Projects

  43. Next are placeholders for future enhancements like project design and planning tools, and specialized “bluebooking” tools. OPUS Projects

  44. Once project session solutions and network adjustments are created, they can be renamed or deleted. OPUS Projects

  45. The reports created during OPUS, Session or Network processing are available through the Show File controls. The selected files are display in a separate window for printing or saving locally. OPUS Projects

  46. A basic email tool for communicating with project participants or the OPUS Projects staff is available. Note that processing reports can be attached to these emails. OPUS Projects

  47. Session solution matrices can be combined and solved creating an network adjustment for this project. OPUS Projects

  48. Using the Review and Publish button, a final network adjustment can be selected, and its results plus the associated mark metadata published to the OPUS data base. OPUS Projects

  49. A request to delete the project can be initiated. This begins a three step confirmation process which, if confirmed at each step, results in the project being deleted. OPUS Projects

  50. And, finally, additional CORS can be added to the entire project using the Add CORS button. OPUS Projects

More Related