3.6.3. Check: What Should Be Updating…

3.6.3.1. … in the UHDAS GUI

When a cruise is active and logging is underway, you should see:

  • green panels in the Monitor Tab, with updating strings (NMEA strings or byte count) NO RED.

3.6.3.2. … in the cruise directory:

You can check the status of logging and processing by running the python command showlast.py in a terminal on “currents”. This program is set up to list recent files in the various directories (to help identify where the problem is occurring). You can look in these directories…

3.6.3.2.1. … in ‘/home/adcp/cruise/raw/’

There should be single-ping data in each ADCP instrument directory (eg. NB150, OS75). Files are *.raw ascii data being updated to each of the serial data directories (eg. gpsnav, gyro, Ashtech)

  • TEST THIS with the following command (“l” as in “logging”)

showlast.py -l 12
  • LOOK AT STRINGS with the following command (“a” as in “ascii”). This will show the last 6 lines of each data stream logged (or the accompanying log file for binary data such as ADCP)

showlast.py -a 6

3.6.3.2.2. … in ‘/home/adcp/cruise/rbin/’

There should be files with very recent (seconds old) timestamps in all “rbin” subdirectories.

  • TEST THIS with the following command (“r” as in “rbin”)

showlast.py -r 12

3.6.3.2.3. … in ‘/home/adcp/cruise/gbin/’

There should be files in all subdirectories with timestamps 5-10minutes old.

  • TEST THIS with the following command (“g” as in “gbin”)

showlast.py -g 12