The following notes are provided with the release of WinRiver version 10.01
Data files format: ddddMMMx.NNN
dddd Filename prefix (set in Settings menu, Configuration Settings, Recording tab)
MMM TRANSECT number. This number starts at 000 and increments each time you stop and then start data collection.
x File type (assigned during data collection or playback)
r – Raw ADCP data
w – copy of the configuration file created during Acquire mode
c – Unique configuration file (DOS TRANSECT only)
n – Navigation GPS data
d – Depth Sounder data
t – ASCII-out data (This convention is the default for ASCII-out data, but you can use other names and extensions.)
NNN File sequence number. This number starts at 000 and increments when the file size reaches the user-specified limit (set in Settings menu, Configuration Settings, Recording tab).
Examples:
NOAA001r.001 (deployment name = NOAA, ADCP data file, transect number=001, file number = 001)
SN11005w.003 (deployment name = SN11, configuration data file, transect number = 005, file number = 003)
These files contain all data sent from the ADCP and other devices during data collection. Refer to the ADCP Technical Manual for a complete description of the format of raw ADCP data files. For any specific deployment, raw data files contain the most information and are usually the largest. Data for these data files are collected through WinRiver’s Acquire mode. WinRiver’s Playback mode accepts raw ADCP data files for display or reprocessing. The structure of raw data files has not been modified and is the same as those recorded by Transect. Note that processed data files cannot be read or created by WinRiver.
These ASCII files contain user-specified setup and deployment information. Different configuration files can be created to suit specific applications through the Settings menu, Configuration Settings.
Unique configuration files are created when data collection is stopped (Acquire menu, Stop Transect). In this manner, the starting/ending edge distances to shore, commands etc. are stored to the correct configuration file.
A unique configuration file is created and stored with each data file. These unique configuration files are stored in the same disk directory as the collected data. The configuration file name uses the same convention as other WinRiver data file names, but uses a "w" character. For example, if WinRiver is recording raw (r) and navigation files (n) with the Filename Prefix set to USGS, the following would be a listing of the files after two complete transects.
USGS001r.000
USGS001n.000
USGS001w.000 (unique configuration file for transect 001 data files)
USGS002r.000
USGS002n.000
USGS002w.000 (unique configuration file for transect 002 data files)
The *w.000 Configuration Data File is a copy of the *wrc configuration file used to collect data. The Playback mode will automatically load the *w.000 configuration file that was created while acquiring the data and the *w.001 file if it exists. Any editing changes made to the *w.000 file are saved to the *w.001 file. If the *w.000 or *w.001 files do not exist, then the default settings are used. If a *c.000 (DOS TRANSECT unique configuration file) exists, it will be used.
NOTE: DO NOT edit configuration files with a text editor as was the recommended policy for Transect. Only edit configuration files using the dialogs in WinRiver.
Extension Description
*.wrc Original configuration file used to collect data.
*w.000 Copy of the *.wrc configuration file created when the transect is completed (recording stopped) that saves the Setting menu, Configuration Settings items.
*w.001 This file contains the changes (if any) made to the *w.000 file during playback.
The *w.000 Configuration Data File is a copy of the *wrc configuration file used to collect data. The Playback mode will automatically load the *w.000 configuration file that was created while acquiring the data and the *w.001 file, if it exists. Any editing changes made to the *w.000 file are saved to the *w.001 file. If a *c.000 (DOS TRANSECT unique configuration file) exists, it will be used.
All items except the Chart Properties 1 and 2 tabs in the Setting menu, Configuration Settings will be grayed out in the Playback mode meaning that the values are used from the *w.000 configuration file. Once the data file has been loaded, changes can be made to the configuration file by right-clicking the item. Select among the following choices.
Right-Click Option Description
Use *w.000 value Returns the item to the value as data was collected.
Enable for Editing Changes the value for the current *w.001 file only. Editing changes are saved to the *w.001 file.
Edit and Freeze Changes the value for the current *w.001 file and will stay in effect for each data file used in the Playback mode. Use this mode if the same correction is needed for playing back multiple transects. For example, if the ADCP depth was incorrectly set for all transects, after loading the first data file, change the ADCP depth by right-clicking the ADCP Depth on the Setting menu, Configuration Settings, Offsets tab and select Edit and Freeze. Enter the correct value. When the next data file is opened, the correct ADCP depth value will be in effect.
In the Settings menu, User Options, General tab the user can specify that the last configuration file opens on startup and/or auto save the configuration file on close of the application. Configuration files can be loaded/saved through the File menu.
Binary file that contains information about open windows, their size, and position. The acquire mode has different window selections and sizes than the playback mode. This only affects how WinRiver looks and does not affect any data files!
In the Settings menu, User Options, General tab you can specify if the last workspace opens on startup and/or auto save the workspace on close of the application. Workspace files can be loaded/saved through the File menu.
These files contain ASCII data collected from an external navigation device during data acquisition. WinRiver reads the navigation data from a user-specified serial port.
These files contain ASCII data collected from an external Depth Sounder device during data acquisition. WinRiver reads the depth data from a user-specified serial port.
These files contain a fixed format of ASCII text that can be created during post-processing. During playback, data can be subsectioned, averaged, scaled, and processed. You also can write this data to an ASCII file. These files can then be used in other programs (spreadsheets, databases, and word processors).
Note: There are minor differences in WinRiver ASCII-Out files than from previous versions of Transect.