Ship to shore: ROV dive logging and data acquisition
Notice bibliographique
Résumé
The Observatory Operations Division at Ocean Networks Canada (ONC) is responsible for the maintenance and operation of the entire digital and marine infrastructure across the VENUS, NEPTUNE, and Cambridge Bay facilities. Depending on planned work, environment and scheduling limitations, various ships and Remotely Operated Vehicles (ROVs) are contracted for the numerous expeditions conducted each year. For instance, during August and September 2015, ONC will be conducting four major expeditions concurrently with multiple ships (EV Nautilus, RV Thomas G. Thompson) and ROVs (Hercules, Argus, Jason/Medea) in the North East Pacific, divers in Cambridge Bay, and a 24 hour shore support centre. This paper focusses on the enabling digital infrastructure that is serving to streamline ROV data acquisition, enhance shore support and multi-vessel expeditions, and enable derivative applications and outreach initiatives. ROV instrumentation commonly includes video cameras, digital still cameras, navigational sensors, scientific sensors (e.g., CTDs, oxygen sensors) and sonar. Leveraging high-bandwidth satellite communications, ONC has developed a ship-based version of Oceans 2.0 that interfaces with selected ROV instrumentation and data streams for data collection, parsing and viewing purposes on the ship. It also transmits that data to shore where it is automatically integrated into the main ONC data repository and instantly available to anyone via ONC's data distribution platforms. High resolution video is typically archived on the ship (and archived on shore post-cruise), while lower resolution video is streamed to shore to be recorded, archived and made available through SeaTube in Oceans 2.0. In the last 2 years, ONC has started to incorporate audio into the video streams and recordings that capture the dialog between ROV operators, ONC staff and other participants. This networked ship to shore data acquisition approach streamlines the data archival process and allows shore-based personnel and scientists to engage in cruise activities. In conjunction with specialized Oceans 2.0 modules and an audio communication system, these high-bandwidth communications and transmitted data streams also enhance shore support capabilities. ONC has recognized this as an opportunity to conduct dive logging operations from shore and to include participants whose guidance is needed for specific operations, reducing the burden of limited ship berths. The two-way audio communication system permits dive loggers to engage with ROV operators and the dive chief almost as if they were on the ship. The SeaScribe dive logging annotation module, first developed by ONC in 2013 and presented at Oceans '13 in San Diego, has recently been extended to support annotations on up to 10 servers on multiple vessels simultaneously. Annotations are synced from one server to another whenever communications permit. Other features to improve usability and functionality have also been added since its initial conception. Shore support duties like systems operations, data stewardship, data commissioning, and public engagement also benefit from these enabling technologies. Derivative applications and outreach initiatives demonstrate further advantages from the integrated data and dive log annotations. Examples of derivative applications include the Oceans 2.0 SeaTube module, a Marine Protected Areas geodatabase for Endeavour Ridge, and scientific analysis on visual survey transects. These applications have in turn driven improvements to the dive log annotation syntax, filtering and export options. Outreach initiatives surrounding expeditions, such as the Wiring the Abyss website, feature live feeds of the video, audio and dive logs. Video streams from webcams showing on-deck and lab activities are also incorporated. The level of coordination between shore personnel and multiple ship/ROV crews would not be possible without this sophisticated digital infrastructure. Further intended improvements include data acquisition support for additional ROV instrumentation, more automated video transcoding and integration, and better support for recording deck operations.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,002 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,000 |
| Bibliométrie | 0,003 | 0,002 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,002 | 0,001 |
| Science ouverte | 0,001 | 0,002 |
| Intégrité de la recherche | 0,000 | 0,001 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,013 | 0,019 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».