Regenerating UHDAS data components

Depending on the reason for single-ping processing, one may need to regenerate some of UHDAS intermediate files. UHDAS data have a specific directory structure. A description of the data directories is available in the CODAS+UHDAS At Sea section, on the Cruise directory contents page.

rbin files:

For UHDAS data, it is usually unnecessary to remake rbins. Try processing the data without remaking rbins and if there are unexplained gaps, start over at the rbin stage. This is the most efficient strategy (if you save all your notes!). For VmDAS data, rbin generation is a normal part of the procedure and instructions include this at the right stage.

Reasons to remake rbins

• to be thorough

  • modern, batch mode rbin generation might fill gaps in a very old cruise

• cruise was broken into several legs (segments)

  • advisable: sometimes multiple segments means missing rbins

• rbins do not exist, eg:

  • VmDAS ENR processing

  • a serial message was logged but not parsed

In order to remake rbins, the parsing program needs to be told what kind of NMEA message is present. This link has more detail about parsing NMEA data into rbin files.

gbin files

For UHDAS data, it is prudent to remake the gbins. It doesn’t take that long, it is often necessary, and unless you know your gbins are exactly what you want, it is better to go ahead and remake them.

Reasons for remaking gbins

• gbins were produced by Matlab processing: they do not work with Python processing

• the cruise was broken into several legs (segments); rejoin the raw and rbin segments and make new gbins

• you are reprocessing the data with a different serial device (eg. different GPS feed

• gbins do not exist (eg. processing ‘reformed’ VmDAS data)