Scientific Sampling Event Log
Complete a request form if you would like to use the R2R Event Logger System on an upcoming cruise.
If you have questions about the Event Logger System, please contact: firstname.lastname@example.org
A brief description of the R2R event logger system is available below or see the detailed User Guide available online.
The R2R 'event log' is a record of the scientific sampling events conducted during a cruise. The underlying concept is that each deployment of a sampling device (e.g. CTD, MocNESS, gravity core) gets logged in a digital file with sufficient information to uniquely and accurately describe that event. Each sampling event is identified with a unique sample event number. When combined with the cruise identifier, this event number is unique across the US academic fleet.
If you would like to use the R2R Event Logger System, please complete and submit a request form.
In addition to event identification numbers unique for the cruise, the scientific sampling event log will include date and time (GMT), position (latitude and longitude), station and cast identifier as appropriate to the sampling event, sampling instrument name (e.g. CTD, TM, MOC10), name of person responsible for the sampling event and a comment field to record additional information.These are the minimum fields required to document a sampling event. Additional information could include timezone and/or local time.
An event logging application has been developed for use aboard UNOLS vessels to assist the scientific party in recording these events and generating a digital event log file at the end of the cruise. In the future, a specification will be published to enable existing event logging systems to generate final cruise event log files that will be compatible with the R2R event log specification.
The objective of maintaining a sampling event log is to create an accurate record of all sampling events from a research cruise. This objective can be met in a variety of ways, but discussions with investigators have yielded some best practice guidelines.
- the final event log should be a plain text, digital file
- the event log should be initiated when the ship leaves port, and concluded upon arrival
- to minimize errors, event records should be created by on-demand sampling of information from the shipboard data stream
- controlled vocabularies should be used instead of free text fields
- at least one free text field is useful to capture comments and anecdotal information for a sampling event
- date and time should be recorded in UTC and time zone recorded to allow calculation of local ship time
- accurate position (lon/lat) data should be recorded for each event
- contents of the event log should be reviewed regularly during a cruise to ensure completeness and accuracy, and modifications made as soon as possible
The first prototype event logger application was tested aboard the R/V Oceanus and R/V Thompson during late 2008, and as 2016 the event lgger system is available on 11 vessels in the UNOLS fleet.
The event logger system is available for use aboard many UNOLS vessels. Simply complete a request form if you would like to use the R2R Event Logger System during an upcoming cruise.