Ship and ROV Core Datastreams : Logger file transfers from ship to shore-side archive This page last changed on Jan 22, 2010 by rich. Wet-side logged datafiles on linux boxes in /coredata/data cronjob run under coredata account, calls NightlyTransfer which gzips all logr.dat files in /coredata/data (except current yrday which is still being written) ftp's gzip'd files to gr8white on-shore (user=rovctd) into /home/datatransfer/wfly_logger or /home/datatransfer/pl_logger on success, deletes the wet-side file. Dry-side on gr8white, user rovctd cronjob runs NightlyPL and NightlyWF shell scripts, which execute moveLogrFiles.perl and processNav.perl moveLogrFiles: transfers all logr.dat.gz files from /home/datatransfer to appropriate /mbari/ShipData/logger directories if its a shipnavlogr file, then make a symbolic link to the archived file in /home/rovctd/nav/(shipname)/raw processNav.perl: any symbolic linked shipnavlogr files found in /home/rovctd/nav/(shipname)/raw are processed into nav.txt files and transfered into /mbari/TempNav directories for hand editing. Downstream processing rovctdlogr and videologr files are processed directly out of the archive by sqlserver jobs that call scripts and perl programs on solstice. Attachments: Nightly Transfers to Archchive (text/xml) Nightly Transfers to Archchive (text/xml)

Document generated by Confluence on Feb 04, 2026 08:53