Specifications
Table Of Contents
- Overview
- Configuration
- Configuration Profiles
- General Profile Settings
- Configuring Devices
- Activating Tag Actions
- Validation Constraints
- Audible Alert Sound Events
- Data Collection and Validation
- Importing and Exporting
- Tools
- Tag Actions
- Tag Action Manager
- Tag Action Settings and Commands
- Tip: the Replace command will import tag codes much faster than the Import command. Use the Import command only when appending a relatively small number of tag codes (less than 25k) to a tag action.
- Tip: the Delete All and Replace commands will generate a lot of empty space in the P3 database. We recommend running the Compact and Repair utility after running any of these commands to optimize the database.
- Tag Actions and Data Entry
- Digitizer Maps
- Searching Data
- Replacing Data Values
- Merging Tag Sessions
- Dot-Out Wizard
- Remove Dot-Outs
- Duplicate Viewer
- Validation Codes
- Database Maintenance
- Tag Actions
- Appendix
- Frequently Asked Questions
- Hardware Support
- Troubleshooting Common Tag Reader Problems
- Troubleshooting Common Digitizer Tablets Problems
- Digitizer Tablet Doesn't Register Pen Clicks
- WinTab Digitizer Tablet Won't Communicate with a PC
- ASCII Digitizer Tablet Won't Communicate with a PC via Serial Port
- Digitizer Tablet doesn't Communicate with P3
- Digitizer Tablet is Sending the Wrong Commands
- Digitizer Tablet is Sending Wrong Lengths
- Digitizer Tablet Hangs P3 when Connected via Baytech Multiport
- Operating the Destron 400 kHz Benchtop Tag Reader
- Configuring Calcomp Drawing Board III
- Index
Data Collection and Validation
35
This field indicates the point of release, in kilometers, and the default value is
based on a value entered in the Release Site header field. This is a
hierarchical coding scheme from the mouth of the Columbia River to the Point
Release site or stream of release (up to 7th order streams), with each river
segment delimited with a period.
A Point Release site is a fixed release location such as a hatchery or
geographical landmark, and this field displays the entire Release River KM for
this location. If fish are released away from a Point Release site, this field
allows the user to append an extension to the Release River KM to indicate
the distance from the mouth of the specified stream to the actual release site.
The default value of this field cannot be modified, however, the last segment
can be modified as an extension in kilometers for defining the exact location
of the release. The format for this field extension is a three-digit numerical
value.
Release Temp.
nn.n Cond. Mand.*
This field contains the temperature (00.0-25.0°C, inclusive) of the water the
tagged fish were released into. This field is required when the tag session
provides Release Information. A value of 25.0 should be entered if the water
temperature is not available, or the value is not applicable (e.g., a multi-week
recapture session).
Release Date
MM/DD/YY hh:mm Cond. Mand.*
This field contains the date and time of Release, in Pacific Standard Time
(PST). During a recapture event, this code designates the re-release date.
When the tag session contains records of PIT tag releases or
recaptures/mortalities collected over multiple days then, by convention, the
Tag Date field (see above) should contain the first day of sampling effort.
Under these circumstances, the Release Date field should reference the last
day of sampling effort, the actual dates of PIT tag release/recovery should be
denoted using Variable Release Times
, and the procedure should be
documented in the Header Note
.
This field can be modified using the keyboard. If the field is in edit mode
then
pressing the Control and Semi-colon keys simultaneously will insert the
current system date and time; pressing the F4 key will display a calendar.
*Cond. Mand (Conditionally Mandatory): If any of the four header fields related to
release information (Release Site, River Kilometer, Release Temp. and Release Date)
are submitted with data, then all four of those header fields must contain data. In
addition, if Variable Release Times
are declared and defined within the Tag Detail
records, all four Release Information header records must be completed.
Tag Session Header Templates