White Paper Contributions

White Paper motivation and requirements:

Original submissions were before September 25, 2020.

New contributions are accepted through the first day of the workshop (April 6th)

Motivation: We are trying to gather information to help development of a community vision of what is needed for seafloor geodesy in support of the upcoming workshop’s goals (below). Your white paper could: include information on an existing or near-term project; describe specific existing, emergent, nascent or technologies; explain proposals for community experiments with the new instrument pool; discuss opportunities to grow a diverse, thoughtful and inclusive community; describe management structure and community development ideas for a stand-alone or integrated seafloor geodetic facility.

Virtual workshop to be held in Spring 2021 with the goals to:

• Identify the active community, and their interest in performing experiments and working with seafloor geodesy data/equipment.

• Get community feedback on input on interests in seafloor geodetic instrument pool usage, including getting input on preferences for community-versus PI-led projects, and the levels of technical support, need for a facility, and data reduction PI or community users would like.

• Evaluate possible targets; particularly should community targets dominate discussion.

• Seek feedback on inclusive and diverse workforce development to grow the community interested in ocean-going seafloor geodetic research.

• Inform the community of the technologies and seek feedback on the instrument mix or technologies that should be considered for future development for seafloor geodesy. What are the opportunities that can spur innovation in seafloor geodesy?

Requirements for White Papers:

• Length: Two pages and a figure. Please no longer, as we want all material to be easily digestible. Links to publications welcome.

• Recommendations: If writing a white paper for a ‘shovel-ready’ to ‘blue sky’ research project, try to include as much of the following:

  • Project objectives/motivation/hypotheses

  • Community or PI-driven

  • Alignment with programmatic/community objectives (with links to supporting docs)

  • Proposed locale(s)

  • Maturity/readiness for experiment

  • Types and approximate numbers of instruments needed and for how long

  • What logistical/organizational level of support would be required/desired to complete objectives, including field, data processing and archiving, management

  • International/institutional collaborations needed/desired

For a paper describing an instrument or processing method, try to include:

• Designed/potential applications

• Readiness

• Approximate costs (try to include information on ship requirements

• Type of observations (absolute/relative velocity, baseline, tilt, etc.)

• Accuracy/repeatability information, expected or otherwise

• Benefits given existing methods

• Requirements, including and potentially proprietary existing technologies/techniques

Facility, community papers:

• Stand-alone or merged facility

• Facility operations approach and why (describing data & instrument management, community development and organization)

• Plans for developing and maintaining inclusive community

• Cooperative partners, including specific agencies/industries, international interests