2020 EarthScope-Oceans Steering Committee Meeting

Session 1: 00:00-3:00am Tuesday 22nd (Princeton day/time)

Session 2: 08:00-11:00am Tuesday 22nd (Princeton day/time)

Agenda

Session 1:

1/ Welcome.

2/ We voted Joel Simon, Ph.D., to Data Committee.

3/ We voted Sébastien Bonnieux, Ph.D. to Technical Committee.

4/ Joel Simon/Tim Ahern

The ESO data standard, and its deposit with IRIS (biggest  
        data center, richest data products, but not the only possible data
        center!)

International outreach with FDSN (standard setting under IASPEI,
        one of two such bodies, the other being the CTBTO)

Standard for positional data. GeoCSV, they turn it into XML.

Should ESO join FDSN? Yes. Then we’ll have a vote.

Coordination between ESO partners concerning station naming 

        Station codes must be unique within the MH Network domain

        Who is going to do this coordination? OSEAN please continue  

to watch this issue. We will need updates to our colloquial  
        numbering scheme as numbers get reused. But serial numbers
        are unique and ESO will adapt.

Detailed notes about the data formatting discussion:

StationXML, formerly Dataless SEED. GeoCSV is the simplest and then the data centers can turn it into StationXML. Which then can be turned into other exchange formats like JSON etc.

Response to be figured out properly, no reason to delay data deposit. Tim, Yann, OSEAN, will be following up.

Princeton data will go to IRIS imminently. We have permission to package the Geoazur data also. We need to confirm before we will enter SUSTECH and JAMSTEC/KOBE and STANFORD data into IRIS as well.

ISC, EMSC, NEIC and (“parametric data centers”) specialize in hypocenters and phase picks. In “isf” format. (IRIS does accept “products” but if you want to interact with data centers through web services, that’s better.)

What about our noise data (Pete) and the PSD data (Stanford)?

Will need to talk about buffer/triggered/requested timings.

Will need to talk about PSD as a data “product” (not unlike cross-correlation data). Ebru is on the IRIS Data Standing Committee.

5/ Adopt-A-Float app (Peter Mwesigwa)

6/ UNESCO-IOC calls. Frederik & Karin following up.

7/ Stanford deployment in the Mediterranean, early 2021. Communications handled by Princeton server. Spanish contacts (Barcelona) exist. Multiple deployments and recovery.

8/ Future institutions. Louisiana Lafayette. Puerto Rico. KAUST.

9/ Japanese instruments had high-pass filter removed. We’d want an update. 1000 m parking depth. Capturing wave height.

10/ Encourage ourselves & community to make requests, e.g. T-phases, surface waves. 1-year buffer!

11/ Alessia: surface waves & uncertainties of much interest.

Student Franck Latallerie.

12/ Ebru: waveform modeling of MERMAID data. Combination of arrival-time data with MERMAID records. 2D FWI tests.

Student Rachel Willis.

13/ Jessica, Frederik: new postdoc Mathurin Wamba.

Session 2: 

1/ Welcome. Recap.

2/ OSEAN: Yann Hello, Olivier Philippe & Nathan Jallet

Mermaid Lander: early design with tripod and feet was too noisy; latest design has a guiderope. Prototype phase passed and first trial completed.

Mermaid CTD. Seabird OEM integration ready. OSEAN does prefer another vendor, RBR, with which it has experience, and which delivers long-term robust sensors at a lower cost. The little Mermaid that could, B51 completed many months and profiles, all the while collecting numerous earthquakes. She then went off to the Weddell Sea. Maybe she needs to be put up for adoption. Argo is amenable to buying CTDs to ride along seismic Mermaids, have us collect data (completely separate acquisition and storage system), and to pay for communication costs (we do RUDICS/Iridium, they normally do SBD since a profile is only 1 kb), and to provide ship time for their deployment. Consensus is that ESO should manage CTD profile data as well. Regular sampling in time? Profiles are of acoustic value to seismic and geodetic interests. Save raw data for possible Argo mandated reprocessing.  IRIS does too deal with meteorological data for land stations, Mars Insight keeps atmospheric pressure data. ESO needs to think pro-actively about the issue. Mermaid Argo, here we come! Who are our friends in this area? IFREMER/JCOMMOPS, JAMSTEC, Stanfor/MBARI?, Princeton/GFDL? ESO to continue to ingratiate itself with other communities. Possible NSF-OOI funding source. Rutgers.

Mermaid 4000 m ready soon.... Suitable test locations using Geoazur contacts in Galicia. Also possible through Princeton with DBV and Bermuda, where 5200 m deep water is close-by, and where Atlantic Explorer can do CTD casts. Frederik been going there, will go there again, likes a Mermaid connection so NSF can provide shiptime.

Mermaid PSD. Stanford edition. Hydrophone is rated 6000 m. These will be new data formats!

3/ SEATREC: Yi Chao & Trevor Henningson

        Solid-Liquid phase transition material. Freeze-melt, contracts, draws
        in oil, when temperature rises, pressurization feeds generator.

4/ Pete. Weird and wonderful data.

If you’re registered for AGU, Pete’s talk can be watched here: https://agu.confex.com/agu/fm20/meetingapp.cgi/Paper/669366 until 15th Feb.

Joel’s poster (on the Princeton SPIMM deployment so far) is here: https://agu2020fallmeeting-agu.ipostersessions.com/?s=BA-D0-B1-A4-71-E1-3E-50-01-11-CE-D2-E8-C0-7E-FD and likewise should be accessible until 15th Feb.

Goodbye.

--------------------------------------------------------------------------------------------------

As yet unordered thoughts:

* EOS article

* Acoustics Today

* Joel Simon / Sebastien Bonnieux on AutoMaid

--------------------------------------------------------------------------------------------------

Suggestions:

Can the ES-Oceans web site get updated to include for instance membership of the various committees? Not sure who does this work Frederik? I got started. Also fixed the broken deployment pages. We had a major CSS switchover... Waiting for Jonah Rubin to come back online and that will get better.