Dataset: event logs
Deployment: OC473

For acquistion information, read about the R2R scientific sampling event log.

This event log used a test version of the R2R EventLogger software, Elog. Elog is an open source browser-based event logger from the NSF program "Rolling Deck to Repository" [http://www.whoi.edu/page.do?pid=35716].  Events could be entered to Elog from any computer that was connected to the ship's intranet. After some research the IP address was discovered so that this was true for wired and wirelessly connected computers. Prior to the cruise, the headings were custom assigned such as the addition of transect and local time according to the specifications of the Chief Scientist. The list of instruments and names of cruise participants was created and edited in the configuration file. At first, the event entries were often missed or delayed but this improved quickly once routines were established. An event could be queued up with all the information except for the local time prior to the event. Once it occurred, the local time would be added and the event submitted At that moment, the position and UTC time were automatically updated. This was fine as long as the event was entered promptly. If it was added later, the UTC time and event number were off and had to be manually edited. Position data for late entries were also updated to the moment of submission and will need to be corrected post-cruise as this information was not readily available. The echosounder interfered with the other science acoustics and was therefore only turned on briefly prior to CTD casts. It was thought that a script unsuccessfully looking for seafloor depth resulted in a significant delay for 'new' and 'duplicate' events. When the script was edited so that depth wasn't included, it did not seem to speed things up. It took about 10 seconds for a new or duplicate page to appear. This was found to be uncomfortably long and should be examined further by the R2R team.