Acoustic positioning telemetry in a case study on the Albert Canal (Belgium): VPS and YAPS positions
Bibliographic record
Abstract
Description This dataset contains data of an acoustic positioning telemetry study on the Albert canal, in a 200x150 m area directly upstream of the navigation lock complex of Kwaadmechelen, Belgium. European silver eels (Anguilla anguilla) and Atlantic salmon smolts (Salmo salar) were tagged with 69-kHz acoustic transmitters (Vemco, Halifax, NS) and detected by acoustic receivers attached at the canal walls and ship guiding structures of the navigation lock complex. The study comprises 3 deployments between 2015-11-25 and 2017-06-16. At the end of each deployment, receivers were offloaded and the detections were sent to Vemco for processing and calculation of the VPS positions. Additionally, we used the raw detection data to calculate positions by use of the YAPS algorithm. Files metadata.csv: definitions for the fields in deployments.csv, receivers.csv, transmitters.csv, detections.csv, positions_vps.csv, positions_yaps.csv and gps_track.csv. deployments.csv: Start and end date of the 3 deployments. At the end of each deployment, receivers were offloaded and the detections were sent to Vemco for processing and calculation of the VPS positions. receivers.csv: Positions and specifications of the used receivers (VR2W and 1 VRT2-x). Receivers with short_id ST8 and ST8-2 have the same receiver_id because it concerns the same receiver deployed in another position (changed on 2017-04-05 08:47). The short_id denotes this position. transmitters.csv: Specifications of the used transmitters. Position and start_date/end_date are only specified for fixed transmitters (i.e. reference-Rx and synchronisation-Sx transmitters). S8-2, S9-2 and R4 were added during the last deployment, and have therefore start dates that differ from deployment start dates. Synchronisation transmitters Sx were collocated with receivers with corresponding STx-id. S8 and S8-2 have the same transmitter_id because it concerns the same transmitter deployed in another position. detections.csv: Raw receiver detections with millisecond time accuracy, needed to perform the YAPS positioning algorithm. The synchronised time was calculated from the original time by use of the synchronisation transmitters: JennaVergeynst. (2019, November 13). JennaVergeynst/time_synchronization: Code for time synchronisation of an acoustic positioning system (Version v1.0.0). Zenodo. http://doi.org/10.5281/zenodo.3540681. positions_vps.csv: Positions of fish, synchronisation and reference transmitters and test tracks from the Vemco Positioning System (VPS). positions_yaps.csv: Positions of fish, synchronisation and reference transmitters and test tracks calculated with YAPS (Yet Another Positioning System): Baktoft, H., Gjelland, K. Ø., Økland, F., & Thygesen, U. H. (2017). Positioning of aquatic animals based on time‐of‐arrival and random walk models using YAPS (Yet Another Positioning Solver). Scientific Reports, 7(1), 14294. https://github.com/baktoft/yaps. The used code to prepare the synchronised detections as input data for YAPS, can be found on JennaVergeynst. (2019, November 13). JennaVergeynst/prepare_toa_for_yaps: Code to prepare TOA-data for YAPS (Version v1.0.0). Zenodo. http://doi.org/10.5281/zenodo.3540683 gps_track.csv: GPS positions of 2 test tracks: a track on 4 August with transmitter 255 and 53429 and one on 5 August with transmitter 16200.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.006 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".