Ocean Science Observing Committee
Consortium for Ocean Leadership
May 16, 2012
The meeting minutes will be posted on this site when available.
OOI Science workshops: Hold Science Workshops (2 per year with geographic consideration), organized through UNOLS and OOSC with OOI collaboration:
Š Engage the broader community
Š Participation by other UNOLS Committees
Š Incorporate an early career/student component (poster sessions, etc)
Š Identify Workshop Theme (s) (refer to OOI science plan)
Š Participation by other existing ocean observing systems - HOTS, BATS, MARS, etc
Š First Workshop:
- Theme - Coastal Ocean Dynamics and Ecosystems
- Identify champions/steering committee
- Hire a Communications Facilitator
- Timing & Location – Early Fall 2012, near Portland, Oregon
- Incorporate hands-on demos – Glider Data and cyberinfrastructure software
- Link the OOI Infrastructure to science and other applications
- Participation by Data groups: NODC, NOAA Fisheries, etc.
- Reach out to the commercial and recreational fisheries community, Gray’s Harbor, Native Americans Quinaults
§ Excite community about the capabilities of OOI
§ Introduce the OOI assets that are coming on-line.
§ Educate the community on access to OOI
§ Team building - Foster science user collaborations/partnerships
Š Suggested Science Workshops Themes for Future Venues:
- Climate Studies – Sampling rate relevant to Climate Studies: organize a workshop that brings climate scientists and modelers together to provide recommendations on the sampling requirements and rates to assure data are suitable for climate science.
- Workshop that highlights the exciting science from other observatories – HOTS, BATS, MARS, etc.
- A workshop on adaptive sampling
Early Career Programs: Provide OOI opportunities to Early Career scientists including:
Š Chief scientist training program
Š Outreach to the ocean engineering students
Š Funding and mentoring support for proposal preparation
Š Provide available bunk space opportunities on ships servicing the OOI: no empty bunks.
OOI Website User Interface Screen Design Development. - OOSC review of the screen design.
During a future phone meeting, the OL “user screen designers” and the OL cyber-person can give a presentation (10 minutes) of the screen design development and how users can comment.
OOSC Review of Plan for Glider Operations - Review and provide input on the cost estimate for centralized OOI glider operations. NSF has requested OOSC feedback on the O&M impacts as well as community impacts to NSF’s recommendations regarding glider operations and staffing.
Š The objective is to keep 6 gliders in operation (12 are available). Uninterrupted operation is essential.
Š OOSC recommends that people who have glider expertise should be involved in the review (Rutgers, USC, UW).
Š Glider operations should have a recompete clause.
Š Review the Glider operation scope.
Š Review the metrics on what it takes to run a fleet of gliders and the success rate for the glider performance. (Jean has requested metrics from the Navy.)
OOSC Committee Liaisons – As appropriate, identify liaisons with other UNOLS Committees to serve as OOSC ex-officio members.
Lessons Learned – Contact the Neptune/Venus office for advise on lessons learned and methods for engaging the community.
Suggestions for Ocean Observatory Outreach Activities:
Š OOI Webinars
Š “Year for Ocean Observing” - Tie the commissioning to a big event.
Š NPR – Earth and Sky segment. A couple minute segment on ocean observing.
Š Radio Lab WNYC
Š Outreach mechanisms that reach all generations including Twitter, FaceBook, etc.
OOSC Phone Meetings – Hold committee phone meetings every 4 to 6 weeks.
OOSC Webpage - Improve and update the OOSC webpage with a brief description of OOSC. Post the minutes from previous meetings on the OOSC webpage. (Action – DeSilva)
Data Management and Quality – Insure that data quality is of highest priority. User community confidence in data quality is critical.
Š Data Management programs – Engage current cyber-infrastructure efforts– HOTS, BATS, Neptune, ARGO to learn from and explore synergies and, where relevant, possibilities of merging resources and infrastructure.
Š A separate data management review is planned in late July/August. Suzanne volunteered to participate as the OOSC member.
Š Explore how OOI data be used for alternate communities (example – fisheries)
Sea-Going Opportunities – OOSC recommends that unused berths on ships servicing OOI should be available for early career scientists and potential users in the science community. The application process can be coordinated through OOSC.
Global Array Installation and Testing Recommendation - Explore the feasibility of performing a full system test (one year) of a Global Array in a location near the US for accessibility if the need for repair arises. Begin system testing with as much of the system that is available. Additionally, the first deployment of a Global Array should not be in the Southern Ocean. Allow time for testing, repair, evaluation, and still meet the schedule of having OOI in place by end of 2015.
Pioneer Array Recommendations:
Š A Cooperative Approach to Science Research at Pioneer Array - Consider an approach for collaborative science planning for use of the Pioneer Array that will optimize its use for its planned 5-year deployment period.
Š The framework for relocation of the Pioneer Array should be developed now.
NSF Dear Colleague Letter: OOSC recommends that NSF draft and distribute a “Dear Colleague” letter announcing the opportunity to submit proposals for science use of OOI. Timeline- ASAP.
Design Reviews – Recommendation that NSF expand external community involvement in OOI design reviews.
Software Tools – Recommend the development of software tools that make it easy to download OOI data.
Water Sampling - Water sampling during the cruises that install the OOI infrastructure is essential for calibration purposes. OOSC recommends that funds to support water sampling during the cruises that install the OOI infrastructure be budgeted.
OOI Website Resources - A website should be developed that will provide information about how to prepare proposals for use of OOI (The MARS website provides a good example).
Sampling Protocols – OOSC recommends that adaptive sampling protocols be created.
Deployment/Budget – OOSC recommends that plans to ensure long-term deployments consider short-term budget cycles.
Mobile Assets – OOSC recommends that policies to allow users to optimize mobile assets be developed.
Tool Box – OOSC recommends that a community OOI toolbox be developed.