Where Is Pit Tag Detection 437 Onthe Upper Salmon River Located

Please refer to the PIT Tag Specification Document, PTAGIS, PSMFC, for more information on the PIT Tag dataset.

PIT Tag Interrogation Sites

Reach and observation site abbreviations are used in the output for the PIT Release and Observation Summary report and the Survival Estimates and the Mean Travel Time Estimates.

* Trap locations may change.

PIT Tag Glossary

Brood Year: This field contains the last two digits of the calendar year when eggs were deposited or collected, if known.
Forklength (Lgth): The length from snout tip to the tail fork, recorded to the nearest millimeter.
Hatchery: When fish are tagged at a hatchery, this field contains the four-character abbreviation from the domain of hatchery codes.
Migration Year: A field in a Tagging File used to record the last two digits of the earliest calendar year when fish are expected to smolt and out-migrate to the ocean. In the case of adults and/or recaptured fish, this value will generally reference the current year.
Observation Date (Obs_DateTime): The date and time the fish are detected at the observation site.
Observation Site (Obs): The three character site code where the fish are observed.
PIT (Passive Integrated Transponder) Tag: A computer chip attached to a wire antenna and encapsulated in a biologically inert glass capsule. The tag is excited when it is passed through the electromagnetic field of a detector and the information on the computer chip is transmitted to the detector. See Research: PIT-Tagging and Other Research Tools, Pacific Salmon Coordination Office for a short description and illustration.
Release Date (RelDate): The date the fish was released to a stream to rear or out-migrate naturally.
Release River KM: The release location expressed in river kilometers from the mouth of the Columbia River. This is a hierarchical coding scheme from the mouth of the Columbia River to the release site (up to 7th order streams for point release sites) with each tributary delimited with a period. For example, the Release River KM for Lower Granite Dam of 522.173 reflects a distance of 522 km from the mouth of the Columbia River to the mouth of the Snake River, and 173 km from the mouth of the Snake River to Lower Granite Dam.
Release Site (RelSite): The six character site code where the fish are released. Intra-Dam Release Site Codes: These codes are appended as a suffix to the three-character dam site code and provide a specific location for release at, above, or below hydroelectric facilities. For example, a release into the gatewells at Lower Granite Dam would be coded as LGRGWL. Use of Intra-Dam Release Site Codes will be required after 12/31/99.

Code	Location
BPS	Release into the PIT-Tag Diversion System between the Diversion Gate and the furthest downstream PIT-Tag Detector
BYP	Release into the Facility Bypass Flume/Pipe
COL	Release into the Collection Channel upstream of the Dewatering Facility
DTG	Release into the Collection Flume/Pipe between the Dewatering Facility and the Collection/Bypass Gate
DWT	Release into the Dewatering Facility
FBY	Release into the Forebay within 0.5 km upstream of Dam
GAT	Release into Flume between Separator Exit and the Primary PIT-Tag Diversion Gate
GWL	Release into Gatewell(s)
ICE	Release into the Ice/Trash Sluiceway
MRT	Mortality Recovery
OFL	Release into the PIT-Tag Diversion System downstream of the Last PIT-Tag Detector
ORI	Release into Orifice(s)
RBR	Release below the PIT-Tag Diversion System Gate with subsequent Barge Transportation from the Facility
RRR	Release below the PIT-Tag Diversion System Gate with subsequent Return to the River at the Facility
RTR	Release below the PIT-Tag Diversion System Gate with subsequent Truck Transportation from the Facility
RXR	Release below the PIT-Tag Diversion System Gate with subsequent Transportation from the Facility
SEP	Release into the Flume downstream of the Collection/Bypass Gate or into the Separator
SPF	Release into the Forebay within 0.5 km upstream of Spillway
SPL	Release directly into Spill Bay(s)
SPT	Release into the Tailrace within 0.5 km downstream of Spillway
SRR	Release into the Separator Return Flume/Pipe with Direct Return to the River
STS	Release onto the Submerged Traveling Screen
TAL	Release into the Tailrace within 0.5 km downstream of Dam
TRB	Release into Turbine(s)

Release Water Temperature: A field containing the water temperature (ºC) in the stream that fish are released into to rear naturally or migrate downstream.
Sequence Number (Seq): A field in a Tagging File detail record containing a sequential number, from 1 to 9999, that individually identifies each Tag Detail record within a Tagging File.
Species, Run, Rear Type (SpRRT): The three character code represents the species, run (the season the adult fish return from saltwater) and rearing type, respectively. If the fish is reared in an environment where both wild and hatchery fish existed then it is unknown unless the fish is clipped.

PIT Tag "Standard" Species, Run, and Rearing Type codes (as determined by PSMFC)

Code	Name
11H	Hatchery Spring Chinook
11U	Spring Chinook (unknown r/t)
11W	Wild Spring Chinook
12H	Hatchery Summer Chinook
12U	Summer Chinook (unknown r/t)
12W	Wild Summer Chinook
13H	Hatchery Fall Chinook
13U	Fall Chinook (unknown r/t)
13W	Wild Fall Chinook
15H	Hatchery Chinook (unknown run)
15U	Chinook (unknown run & r/t)
15W	Wild Chinook (unknown run)
25H	Hatchery Coho
25U	Coho (unknown r/t)
25W	Wild Coho
30H	Hatchery O. mykiss (unknown migratory status)
30U	O. mykiss (unknown migratory/rearing status)
30W	Wild O. mykiss (unknown migratory status)
32H	Hatchery Summer Steelhead
32U	Summer Steelhead (unknown r/t)
32W	Wild Summer Steelhead
34H	Hatchery Winter Steelhead
34W	Wild Winter Steelhead
35H	Hatchery Steelhead (unknown run)
35U	Steelhead (unknown run & r/t)
35W	Wild Steelhead (unknown run)
3RH	Hatchery Rainbow Trout
3RU	Rainbow Trout (unknown r/t)
3RW	Wild Rainbow Trout
42H	Hatchery Summer Sockeye
42U	Summer Sockeye (unknown r/t)
42W	Wild Summer Sockeye
45H	Hatchery Sockeye (unknown run)
45U	Sockeye (unknown run & r/t)
45W	Wild Sockeye (unknown run)
65W	Wild Pink
7RW	Bull Trout
85H	Hatchery Coastal Cutthroat
85U	Coastal Cutthroat (unknown r/t)
85W	Wild Coastal Cutthroat
8RW	Wild Resident Cutthroat
90U	Other
A0W	Pacific Lamprey
B0H	Hatchery White Sturgeon
B0W	White Sturgeon
C0W	Green Sturgeon
D0W	Northern Pikeminnow
ERU	Brook Trout
F0W	American Shad
G0W	Mountain Whitefish
H0W	Walleye
I0W	Channel Catfish
J0W	Smallmouth Bass

Tag Coordinator: The Coordinator ID code is the initials (two or three) of the project leader responsible for the PIT Tag data (not necessarily the person conducting the tagging or creating the Tagging File).
Tag Count: The total number of fish tagged during that particular release; it can range from single digits to thousands of fish.
Tag ID (Tag_ID): A unique 10- or 14-character hexadecimal code recorded on the computer chip in the PIT tag.
Tag Site: This field contains a code (between three and six characters) denoting the site where the fish were marked (see Tag and Release Site Codes). During a recapture event, this code designates the recapture site.
Tagging File (Tag_File): A file containing information from a PIT tagging session during which PIT tags are implanted in fish. A data file containing information pertaining to the original marking, release, recapture, or mortality of PIT-tagged fish.
Tagging Temperature: The temperature (ºC) of the tagging bath during the marking operation.
Travel (Days): The difference between the release date and the observation date. Note, this may include time spent in rearing and is therefore not a good estimate of actual migration time.
>USGS Hydrologic Unit: An eight-digit code representing the primary through quaternary classifications of geographic mapping in the United States. The US Geological Service assigns code designations to watersheds; this eight-digit code defines the location of the release site. This information can be useful in GIS (Geographical Information Systems) applications. See USGS Hydrologic Units Maps for more information.
Weight: A field in a Tagging File used to report the weight of the fish, recorded in tenths of grams.

Survival and Travel Time Estimates

Survival Estimates

The survival estimates are calculated for a population of PIT-tagged fish as defined by the query.

The Survival Estimates tool uses Cormack-Jolly-Seber (CJS) estimates. The query results provide estimates and standard errors for the survival and detection probabilities, and the product of the final survival and detection probabilities. The standard error of all estimates are reported in parentheses. The estimate of the overall survival probability, i.e., the product of all the survival estimates, is reported as well.

For the CJS estimates to be valid, the following assumptions must be met:

Individuals marked for the study are a representative sample from the population of interest.
Survival and capture probabilities are not affected by tagging or detection. That is, tagged fish have the same probabilities as untagged fish.
All detections are "instantaneous." That is, detection takes a negligible amount of time or distance relative to the length of the reaches between detection events.
The fate of each tagged individual is independent of the fate of all others.
All tagged individuals alive at the beginning of a reach have the same probability of surviving until the end of that reach.
All tagged individuals alive at the beginning of a detection site have the same probability of being detected at that site.
Each individual detected at a particular detection site has the same probability of being removed, and the probability of removal is independent of the survival process.

There are several limitations to the Survival Estimates produced by this tool.

Depending on the selection criteria, the survival estimates will tend to over-pool releases.
If you do not define the PIT Tag group specifically by a release site, then different release sites (and travel distances) will be included in the group; hence the assumption that all individuals have the same probability of survival may be violated for the first reach (release point to the first dam). Survival estimates for the other reaches (dam to dam) will be fine.
If the PIT Tag group includes fish released from the same location but at different times, then the estimates will be a weighted average over time as a function of release size. If the probability of survival varies over time, the assumption that all individuals have the same probability of survival may be violated.
The Survival Estimates tool is unable to produce estimates for the last dam because detection efficiency cannot be distinguished from survival for the final reach.
Survival estimates are generated from capture histories for each fish that are based on data downloaded from the PTAGIS database system. The particular data used for these estimates contain only last detections and therefore do not take into account the full detection history for a fish at a given site and may not account for errors in detection sequence recording. This may lead to minor over censoring of the data that in turn may lead to slightly higher standard errors in parameter estimates when compared to systems that use the full detections history of the fish.

Mean Travel Time Estimates

The mean travel times are calculated for a population of PIT-tagged fish as defined by the query.

The travel time estimates are based on the release date for each pit-tagged fish as recorded in the PTAGIS database (and uploaded to the Columbia River DART database) and the first and last detection times at each downstream detection site. Travel Time estimates for release to downstream detection site are calculated using the release time and the time of the first detection at the downstream detection site. Between detection sites travel time estimates are calculated using the time of the last detection at the upstream site and the time of the first detection at the downstream site.

Arithmetic Mean Travel Time

( reach travel time ) / number of unique fish detected at the detection sites

Harmonic Mean Travel Time

number of unique fish detected at the detection sites / ( (1/reach travel time) )

When dealing with travel times, we are primarily interested in the speed with which fish travel from point A to point B. A good statistic for describing a particular group's speed is the harmonic mean. A harmonic mean is used when working with rates of speed, usually the number of days to travel a set distance. A benefit to using the harmonic mean is that it is more robust in the presence of outliers (i.e., a very fast or slow fish).

ESU (Evolutionarily Significant Unit) and DPS (Distinct Population Segment) Glossary

ESU (Evolutionarily Significant Unit) is a distinct population listed for protection under the Endangered Species Act (ESA). DPS (Distinct Population Segment) is a distinct steelhead population listed for protection under the Endangered Species Act (ESA). See ESA Listing Pages, Protected Resources, NMFS, NOAA, for detailed information on ESA listings and ESU/DPS status and descriptions of specific stocks.

Chinook

The Snake River Spring/Summer Chinook ESU includes naturally spawned spring/summer-run Chinook salmon originating from the mainstem Snake River and the Tucannon River, Grande Ronde River, Imnaha River, and Salmon River subbasins. It also includes spring/summer-run Chinook salmon from 11 artificial propagation programs: Tucannon River Program, Lostine River Program, Catherine Creek Program, Lookingglass Hatchery Program, Upper Grande Ronde Program, Imnaha River Program, Big Sheep Creek Program, McCall Hatchery Program, Johnson Creek Artificial Propagation Enhancement Program, Pahsimeroi Hatchery Program, and Sawtooth Hatchery Program. Definition implemented by Columbia River DART: March 2015.

Listing Status, West Coast Region, NOAA

The Snake River Spring/Summer Chinook ESU Wild Only Subpopulation includes naturally spawned spring/summer-run Chinook salmon originating from the mainstem Snake River and the Tucannon River, Grande Ronde River, Imnaha River, and Salmon River subbasins. The ESU Wild Only Subpopulation does not include the 11 artificial propagation programs that are part of the Snake River Spring/Summer Chinook ESU. Definition implemented by Columbia River DART: March 2015.

The Upper Columbia River Spring Chinook ESU includes naturally spawned spring-run Chinook salmon originating from Columbia River tributaries upstream of the Rock Island Dam and downstream of Chief Joseph Dam (excluding the Okanogan River subbasin). Also, spring-run Chinook salmon from six artificial propagation programs: Twisp River Program, Chewuch River Program, Methow Program, Winthrop National Fish Hatchery Program, Chiwawa River Program, and White River Program. Definition implemented by Columbia River DART: March 2010.

Listing Status, West Coast Region, NOAA

The Upper Columbia River Spring Chinook ESU Wild Only Subpopulation includes naturally spawned spring-run Chinook salmon originating from Columbia River tributaries upstream of the Rock Island Dam and downstream of Chief Joseph Dam (excluding the Okanogan River subbasin). The ESU Wild Only Subpopulation does not include the six artificial propagation programs that are part of the Upper Columbia River Spring Chinook ESU. Definition implemented by Columbia River DART: March 2010.

The Lower Columbia River Chinook ESU includes naturally spawned Chinook salmon originating from the Columbia River and its tributaries downstream of a transitional point east of the Hood and White Salmon Rivers, and any such fish originating from the Willamette River and its tributaries below Willamette Falls. Not included in this ESU are: (1) spring-run Chinook salmon originating from the Clackamas River; (2) fall-run Chinook salmon originating from Upper Columbia River bright hatchery stocks, that spawn in the mainstem Columbia River below Bonneville Dam, and in other tributaries upstream from the Sandy River to the Hood and White Salmon Rivers; (3) spring-run Chinook salmon originating from the Round Butte Hatchery (Deschutes River, Oregon) and spawning in the Hood River; (4) spring-run Chinook salmon originating from the Carson National Fish Hatchery and spawning in the Wind River; and (5) naturally spawning Chinook salmon originating from the Rogue River Fall Chinook Program. This ESU does include Chinook salmon from 15 artificial propagation programs: Big Creek Tule Chinook Program, Astoria High School Salmon-Trout Enhancement Program (STEP) Tule Chinook Program, Warrenton High School STEP Tule Chinook Program, Cowlitz Tule Chinook Program, North Fork Toutle Tule Chinook Program, Kalama Tule Chinook Program, Washougal River Tule Chinook Program, Spring Creek National Fish Hatchery (NFH) Tule Chinook Program, Cowlitz Spring Chinook Program in the Upper Cowlitz River and the Cispus River, Friends of the Cowlitz Spring Chinook Program, Kalama River Spring Chinook Program, Lewis River Spring Chinook Program, Fish First Spring Chinook Program, and Sandy River Hatchery (Oregon Department of Fish and Wildlife Stock #11). Definition implemented by Columbia River DART: March 2015.

Listing Status, West Coast Region, NOAA

The Lower Columbia River Chinook ESU Wild Only Subpopulation includes naturally spawned Chinook salmon originating from the Columbia River and its tributaries downstream of a transitional point east of the Hood and White Salmon Rivers, and any such fish originating from the Willamette River and its tributaries below Willamette Falls. Not included in this ESU are: (1) spring-run Chinook salmon originating from the Clackamas River; (2) fall-run Chinook salmon originating from Upper Columbia River bright hatchery stocks, that spawn in the mainstem Columbia River below Bonneville Dam, and in other tributaries upstream from the Sandy River to the Hood and White Salmon Rivers; (3) spring-run Chinook salmon originating from the Round Butte Hatchery (Deschutes River, Oregon) and spawning in the Hood River; (4) spring-run Chinook salmon originating from the Carson National Fish Hatchery and spawning in the Wind River; and (5) naturally spawning Chinook salmon originating from the Rogue River Fall Chinook Program. The ESU Wild Only Subpopulation does not include the 15 artificial propagation programs that are part of the Lower Columbia River Chinook ESU. Definition implemented by Columbia River DART: March 2015.

The Upper Willamette River Chinook ESU includes naturally spawned spring-run Chinook salmon originating from the Clackamas River and from the Willamette River and its tributaries above Willamette Falls. Also, spring-run Chinook salmon from six artificial propagation programs: McKenzie River Hatchery Program (Oregon Department of Fish and Wildlife (ODFW) Stock #23), Marion Forks Hatchery/North Fork Santiam River Program (ODFW Stock #21), South Santiam Hatchery Program (ODFW Stock #24) in the South Fork Santiam River and Mollala River, Willamette Hatchery Program (ODFW Stock #22), and Clackamas Hatchery Program (ODFW Stock #19). Definition implemented by Columbia River DART: March 2015.

Listing Status, West Coast Region, NOAA

The Upper Willamette River Chinook ESU Wild Only Subpopulation includes naturally spawned spring-run Chinook salmon originating from the Clackamas River and from the Willamette River and its tributaries above Willamette Falls. The ESU Wild Only Subpopulation does not include the 6 artificial propagation programs that are part of the Upper Willamette River Chinook ESU. Definition implemented by Columbia River DART: March 2015.

The Snake River Fall Chinook ESU includes naturally spawned fall-run Chinook salmon originating from the mainstem Snake River below Hells Canyon Dam and from the Tucannon River, Grande Ronde River, Imnaha River, Salmon River, and Clearwater River subbasins. Also, fall-run Chinook salmon from four artificial propagation programs: Lyons Ferry Hatchery Program, Fall Chinook Acclimation Ponds Program, Nez Perce Tribal Hatchery Program, and Oxbow Hatchery Program. Definition implemented by Columbia River DART: June 2007.

Listing Status, West Coast Region, NOAA

Definition used by Columbia River DART through May 2007. Snake River Fall Chinook ESU consists of the production from spawning populations of fall chinook in the Snake, Tucannon, Clearwater, Salmon, Imnaha and Grande Ronde Rivers.

The Snake River Fall Chinook ESU Wild Only Subpopulation includes naturally spawned fall-run Chinook salmon originating from the mainstem Snake River below Hells Canyon Dam and from the Tucannon River, Grande Ronde River, Imnaha River, Salmon River, and Clearwater River subbasins. The ESU Wild Only Subpopulation does not include the 4 artificial propagation programs that are part of the Snake River Fall Chinook ESU. Definition implemented by Columbia River DART: June 2007.

Sockeye

The Snake River Sockeye ESU includes naturally spawned anadromous and residual sockeye salmon originating from the Snake River Basin, and also sockeye salmon from one artificial propagation program: Redfish Lake Captive Broodstock Program. Definition implemented by Columbia River DART: March 2010.

Listing Status, West Coast Region, NOAA

The Snake River Sockeye ESU Wild Only Subpopulation includes naturally spawned anadromous and residual sockeye salmon originating from the Snake River Basin. Definition implemented by Columbia River DART: March 2010.

Steelhead

The Snake River Steelhead DPS includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Snake River basin, and also steelhead from six artificial propagation programs: Tucannon River Program, Dworshak National Fish Hatchery Program, Lolo Creek Program, North Fork Clearwater Program, East Fork Salmon River Program, and Little Sheep Creek/Imnaha River Hatchery Program (Oregon Department of Fish and Wildlife Stock #29). Definition implemented by Columbia River DART: March 2010.

Listing Status, West Coast Region, NOAA

The Snake River Steelhead DPS Wild Only Subpopulation includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Snake River basin. The ESU Wild Only Subpopulation does not include the 6 artificial propagation programs that are part of the Snake River Steelhead DPS. Definition implemented by Columbia River DART: March 2010.

The Upper Columbia River Steelhead DPS includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Columbia River and its tributaries upstream of the Yakima River to the U.S.-Canada border. Also, steelhead from six artificial propagation programs: Wenatchee River Program, Wells Hatchery Program (in the Methow and Okanogan Rivers), Winthrop National Fish Hatchery Program, Omak Creek Program, and Ringold Hatchery Program. Definition implemented by Columbia River DART: March 2010.

Listing Status, West Coast Region, NOAA

The Upper Columbia River Steelhead DPS Wild Only Subpopulation includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Columbia River and its tributaries upstream of the Yakima River to the U.S.-Canada border. The DPS Wild Only Subpopulation does not include the 6 artificial propagation programs that are part of the Upper Columbia River Steelhead DPS. Definition implemented by Columbia River DART: March 2010.

The Middle Columbia River Steelhead DPS includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Columbia River and its tributaries upstream of the Wind and Hood Rivers (exclusive) to and including the Yakima River; excludes such fish originating from the Snake River Basin. This DPS does include steelhead from seven artificial propagation programs: Touchet River Endemic Program, Yakima River Kelt Reconditioning Program (in Satus Creek, Toppenish Creek, Naches River, and Upper Yakima River), Umatilla River Program (Oregon Department of Fish and Wildlife (ODFW) Stock #91), and Deschutes River Program (ODFW Stock #66). This DPS does not include steelhead that are designated as part of an experimental population. Definition implemented by Columbia River DART: March 2010.

Listing Status, West Coast Region, NOAA

The Middle Columbia River Steelhead DPS Wild Only Subpopulation includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from the Columbia River and its tributaries upstream of the Wind and Hood Rivers (exclusive) to and including the Yakima River; excludes such fish originating from the Snake River Basin. The DPS Wild Only Subpopulation does not include the 7 artificial propagation programs that are part of the Middle Columbia River Steelhead DPS. Definition implemented by Columbia River DART: March 2010.

The Lower Columbia River Steelhead DPS includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from rivers between the Cowlitz and Wind Rivers (inclusive) and the Willamette and Hood Rivers (inclusive); excludes such fish originating from the upper Willamette River basin above Willamette Falls. This DPS does include steelhead from seven artificial propagation programs: Cowlitz Trout Hatchery Late Winter-run Program (Lower Cowlitz), Kalama River Wild Winter-run and Summer-run Programs, Clackamas Hatchery Late Winter-run Program (Oregon Department of Fish and Wildlife (ODFW) Stock #122), Sandy Hatchery Late Winter-run Program (ODFW Stock #11), Hood River Winter-run Program (ODFW Stock #50), and Lewis River Wild Late-run Winter Steelhead Program. Definition implemented by Columbia River DART: March 2015.

Listing Status, West Coast Region, NOAA

The Lower Columbia River Steelhead DPS Wild Only Subpopulation includes naturally spawned anadromous O. mykiss (steelhead) originating below natural and manmade impassable barriers from rivers between the Cowlitz and Wind Rivers (inclusive) and the Willamette and Hood Rivers (inclusive); excludes such fish originating from the upper Willamette River basin above Willamette Falls. The DPS Wild Only Subpopulation does not include the 7 artificial propagation programs that are part of the Lower Columbia River Steelhead DPS. Definition implemented by Columbia River DART: March 2015.

Note on Migration Year 2000:
There was an release of unmarked subyearling chinook upstream of Snake River Trap which occurred in May 2000. As the result, there was some problem in proper identification of juvenile chinook at the trap (SNKTRP) beginning with May 22, 2000. Some subyearling fall chinook were tagged as 15Ws (Chinook, Unknown, Wild) and included in the wild yearling spring/summer chinook ESU totals via detections from the SNKTRP. Detections at SNKTRP after May 22, 2000 of wild yearling spring/summer chinook have been excluded from the "Chinook, Wild Spring/Summer Yearling" category.

DART Life Stage Filter

DART categorizes PIT Tag observations into three stages: Adult, Juvenile, and Unknown. A life-stage of Adult, Juvenile, or Unknown is assigned to each salmonid PIT Tag detection using PTAGIS data specifications of migration year, release year, release length, observation year, release site, capture method, tagging comments, detection sequences, travel time, detection location and other criteria to determine the stage of the PIT-tagged fish at the time of the detection. The PTAGIS observation data set is an extremely useful resource for monitoring and analyzing the life history and migration patterns of Columbia Basin salmonids. Attaching a life-stage designation (Adult, Juvenile, Unknown) to a PIT tag detection increases the utility of the dataset and allows additional analyses including conversion rates and stray patterns. The DART life stage filter combines the tagging, interrogation, and recapture datasets to determine the life stage at tagging and each subsequent observation. The DART definition of adult is a sexually mature, upstream migrant including precocious, mini-jack, and jack fish.

DART Transportation Filter

DART transport analysis of PTAGIS dataset is conducted annually after the end of the transportation season. DART analyzed 2000 to the present for transportation at Lower Granite, Little Goose, Lower Monumental, and McNary (until operations stopped).

The DART transport filter of the PTAGIS dataset examines fish seen at transport locations and assigns a probable transport outcome to individuals. It is designed to create a list of fish that are expected to be transported based on coil detections but may have extenuating circumstances.

The psql file "Transport_Filter_NEW.psql" is the vehicle for this. Tables involved include transport_proj_list , transport_rel_list , transport_dates , trans_min_max , cbr_transport_exceptions , and trans_dates_dodo .

The first step is to examine the transport schedule as reported by FPC. The results are placed in the table transport_dates . Chinook are added separately because they have multiple run-types. A key statistic is bypass percent.

The table is improved by determining days where fish are collected but the action (bypassed, transported) is recorded on the following day. trans_dates_dodo is the table for this. Its refinements go into transport_dates .

transport_dates is then examined for the min and max transport dates for each species and project. The results are placed in trans_min_max . trans_dates_dodo is examined to extend the dates here as well, if needed.

We then create two lists: transport_proj_list table are fish seen at the transport sites with their max(obs_date) and associated coil_ids. transport_rel_list are fish identified in transportation releases. There is a little overlap here so fish listed as transport releases that are detected at the transport sites are deleted from the transport_proj_list . Project and obs_site names are forced into alignment in these two lists.

Based on PTAGIS site configuration information, fish with absolute non-transport final coils_ids are deleted from the table. The remaining fish are assigned a trans_status codes of 'T' (TRANSPORTED) or 'S' (SAMPLED) depending on the date and location of their last detection at a project. All transportation release fish are assigned an initial code of 'T'.

Any fish not receiving a status code is deleted from the tables.

Then the trans_status codes are examined relative to transport_dates . Fish that are detected on days when bypass exceed 93% have a 'B' (BYPASS) appended to their trans_status. Fish seen at projects outside the transportation date window are also appended with a 'B'. Fish that are held extra days before an action is recorded ( trans_dates_dodo ) are examined manually after the filter is completed to determine if the fish need an added bypass designation. These additional bypass dates are added programmatically to the filter.

There is significant meta-data regarding project/date combinations where transport operations were compromised. We have two methods of determining these events:

Specific expert information regarding specific releases, projects, and dates.
Careful retrospective analysis of the transportation filter results to identify project/date combinations where a significant percentage of expected transport fish were returned to the river. Subsequent downstream detections are used in this analysis. If 25% of temporally grouped 'T' or 'S' status fish are detected downstream we consider the time period to have a bypass pattern (P).

This intelligence is contained into the table cbr_transport_exceptions . Fish matching the appropriate criteria in the table are assigned the trans_status of TBP (TRANSPORT BYPASS PATTERN) or SBP (SAMPLE BYPASS PATTERN) as listed in the table.

The transport_rel_list is appended to transport_proj_list at this juncture.

There are a number of barge releases that are identified as not satisfying a 'transported' criteria. These 'bad barge trip' fish are assigned a trans_status code of '99'.

Once fish have these designations, they are examined for unexpected downstream PTAGIS detections. Fish seen at a transport site that have received a trans_status designation of 'S', 'T', 'SB', or 'TB' but are seen at a downstream location as a juvenile have a 'D' (DOWNSTREAM) appended to their trans_status.

The transport_proj_list table contains the following transport designations:

Table 1 DART Transport Status Codes

trans_status	Counts (2000-2015)	trans_status description
T	2771582	Transport
TB	284479	Transport, Probable Bypass
TBD	100362	Transport, Probable Bypass, Detected Downstream
TBP	18813	Transport, Probable Bypass, Pattern Shows Bypass
TD	5643	Transport, Detected Downstream
S	113824	Sample
SB	4872	Sample, Probable Bypass
SBD	4394	Sample, Probable Bypass, Detected Downstream
SBP	1106	Sample, Probable Bypass, Pattern Shows Bypass
SD	574	Sample, Detected Downstream
99	4799	Bad Barge Trip

Table 2 DART Transport Exceptions

Project	Year	Source	Monitor	Start time	End time	trans_status
Project	Year	Source	Monitor	Start time	End time	trans_status
LWG	2000	CBR Sites Config	RACEWAY EAST	2000-05-04 11:16:59	2000-05-04 19:36:55	TBP
LWG	2000	CBR Sites Config	RACEWAY EAST	2000-05-05 18:00:00	2000-05-05 23:38:00	TBP
LWG	2000	CBR Sites Config	RACEWAY EAST	2000-05-06 06:55:00	2000-05-06 07:55:00	TBP
LWG	2000	CBR Sites Config	RACEWAY EAST	2000-05-07 02:57:00	2000-05-07 06:57:00	TBP
LWG	2001	BADBARGE	SAMPLE TANK	2001-05-15 07:45:00	2001-05-18 02:08:00	99
LWG	2001	IHR DUMP	SAMPLE TANK	2001-05-15 07:45:46	2001-05-18 02:07:09	SBP
LWG	2001	BADBARGE	RACEWAY WEST / RIVER EXIT	2001-05-15 08:57:00	2001-05-15 13:58:00	99
LWG	2001	BADBARGE	RACEWAY EAST	2001-05-16 18:54:00	2001-05-16 20:57:00	99
LWG	2001	BADBARGE	RACEWAY WEST / RIVER EXIT	2001-05-17 01:59:00	2001-05-18 05:10:00	99
LWG	2003	CBR Sites Config	RACEWAY WEST / RIVER EXIT	2003-04-23 21:05:00	2003-04-24 05:20:00	TBP
LWG	2003	Pattern	RACEWAY EAST	2003-07-01 06:00:00	2003-07-01 12:34:22	TBP
LWG	2003	Pattern	RACEWAY WEST / RIVER EXIT	2003-07-08 04:02:29	2003-07-08 13:48:12	TBP
LWG	2003	Pattern	RACEWAY WEST / RIVER EXIT	2003-07-08 17:00:00	2003-07-08 23:59:59	TBP
LWG	2003	Pattern	RACEWAY EAST	2003-07-15 06:10:00	2003-07-15 08:30:00	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-05-04 23:12:15	2004-05-05 00:35:59	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-05-05 21:32:56	2004-05-06 07:12:58	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-05-09 00:07:23	2004-05-09 07:00:08	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-05-22 21:04:00	2004-05-23 03:39:59	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-05-23 20:30:00	2004-05-24 07:59:59	TBP
LWG	2004	Pattern	RACEWAY EAST	2004-06-24 23:00:00	2004-06-24 23:59:59	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-04-06 03:05:50	2005-04-06 05:24:29	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-04-30 03:00:00	2005-04-30 08:57:00	TBP
LWG	2005	Pattern	RACEWAY WEST / RIVER EXIT	2005-05-01 00:35:00	2005-05-01 00:49:59	TBP
LWG	2005	Pattern	RACEWAY WEST / RIVER EXIT	2005-05-01 01:14:00	2005-05-01 01:22:59	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-05-02 05:00:00	2005-05-02 13:59:59	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-05-09 08:49:20	2005-05-09 22:04:40	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-05-10 14:30:00	2005-05-10 17:32:00	TBP
LWG	2005	Pattern	RACEWAY EAST	2005-10-31 07:05:55	2005-10-31 08:05:42	TBP
LWG	2006	Pattern	RACEWAY WEST / RIVER EXIT	2006-05-20 08:00:00	2006-05-20 18:50:00	TBP
LWG	2006	Pattern	RACEWAY EAST / RIVER EXIT	2006-05-20 19:00:00	2006-05-20 23:59:59	TBP
LWG	2006	Pattern	RACEWAY EAST / RIVER EXIT	2006-05-22 01:00:00	2006-05-22 09:59:59	TBP
LWG	2007	Pattern	SAMPLE TANK	2007-04-19 00:00:00	2007-05-01 06:59:59	SBP
LWG	2008	Pattern	SAMPLE TANK	2008-04-10 04:02:06	2008-05-01 06:59:59	SBP
LWG	2009	Pattern	SAMPLE TANK	2009-04-09 02:30:23	2009-05-01 06:59:59	SBP
LWG	2009	Pattern	RACEWAY EAST	2009-04-23 18:00:00	2009-04-23 19:50:00	TBP
LWG	2010	Pattern	SAMPLE TANK	2010-04-23 00:29:13	2010-04-23 04:58:06	SBP
LWG	2011	Pattern	SAMPLE TANK	2011-04-12 01:27:06	2011-04-27 20:38:10	SBP
LWG	2011	Pattern	RACEWAY EAST	2011-05-15 07:29:00	2011-05-15 23:59:59	TBP
LWG	2011	Pattern	SAMPLE TANK	2011-05-15 10:57:57	2011-05-18 04:58:44	SBP
LWG	2011	Pattern	EAST RACEWAY 10	2011-05-15 19:09:03	2011-05-15 20:00:45	TBP
LWG	2011	Pattern	SAMPLE TANK	2011-05-22 06:02:00	2011-05-22 23:59:59	SBP
LWG	2011	Pattern	RACEWAY EAST	2011-05-22 16:29:00	2011-05-22 23:59:59	TBP
LWG	2012	Pattern	SAMPLE TANK	2012-04-12 01:06:23	2012-05-01 00:30:11	SBP
LWG	2012	Pattern	RACEWAY WEST / RIVER EXIT	2012-05-07 22:16:38	2012-05-07 22:59:59	TBP
LWG	2012	Pattern	RACEWAY WEST / RIVER EXIT	2012-05-15 22:26:12	2012-05-15 22:50:15	TBP
LWG	2013	Pattern	SAMPLE TANK	2013-04-26 01:33:58	2013-04-27 03:12:30	SBP
LWG	2014	Pattern	SAMPLE TANK	2014-04-25 06:15:18	2014-05-01 02:15:15	SBP
LWG	2014	BADBARGE	SAMPLE TANK	2014-05-08 06:00:00	2014-05-08 19:59:00	99
LWG	2014	EXTRA TRIP	SAMPLE TANK	2014-05-08 06:27:36	2014-05-09 03:59:59	99
LWG	2014	BADBARGE	RACEWAY EAST	2014-05-08 07:00:00	2014-05-08 12:59:00	99
LWG	2014	BADBARGE	RACEWAY EAST	2014-05-08 18:00:00	2014-05-08 20:59:00	99
LWG	2014	BADBARGE	EAST RACEWAY 10	2014-05-08 18:00:00	2014-05-08 20:59:00	99
LGS	2003	Pattern	B-RACEWAY / RIVER EXIT	2003-06-06 06:20:00	2003-06-06 06:49:49	TBP
LGS	2003	Pattern	B-RACEWAY / RIVER EXIT	2003-06-11 07:25:46	2003-06-11 07:41:40	TBP
LGS	2003	Pattern	A-RACEWAY / RIVER EXIT	2003-06-11 07:44:42	2003-06-11 08:19:23	TBP
LGS	2003	Pattern	B-RACEWAY / RIVER EXIT	2003-07-08 02:20:23	2003-07-08 22:38:58	TBP
LGS	2003	Pattern	A-RACEWAY / RIVER EXIT	2003-07-09 00:00:00	2003-07-09 11:59:59	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-10 08:59:00	2005-05-10 23:59:59	TBP
LGS	2005	Pattern	B-RACEWAY / RIVER EXIT	2005-05-10 13:55:00	2005-05-10 23:59:59	TBP
LGS	2005	Pattern	B-RACEWAY / RIVER EXIT	2005-05-11 00:00:00	2005-05-11 05:59:59	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-11 00:00:00	2005-05-11 05:59:59	TBP
LGS	2005	Pattern	B-RACEWAY / RIVER EXIT	2005-05-11 19:00:01	2005-05-11 23:59:59	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-11 20:19:00	2005-05-11 23:59:59	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-12 00:00:00	2005-05-12 06:59:59	TBP
LGS	2005	Pattern	B-RACEWAY / RIVER EXIT	2005-05-12 00:00:00	2005-05-12 11:05:58	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-12 13:30:00	2005-05-12 15:59:59	TBP
LGS	2005	Pattern	A-RACEWAY / RIVER EXIT	2005-05-13 03:00:00	2005-05-13 11:03:30	TBP
LGS	2007	Pattern	B-RACEWAY / RIVER EXIT	2007-05-12 04:04:59	2007-05-12 05:36:09	TBP
LGS	2007	Pattern	B-RACEWAY / RIVER EXIT	2007-05-21 11:55:00	2007-05-21 23:59:59	TBP
LGS	2007	Pattern	A-RACEWAY / RIVER EXIT	2007-05-21 12:00:00	2007-05-21 23:59:59	TBP
LGS	2007	Pattern	A-RACEWAY / RIVER EXIT	2007-05-22 00:00:00	2007-05-22 11:59:59	TBP
LGS	2007	Pattern	B-RACEWAY / RIVER EXIT	2007-05-22 00:00:00	2007-05-22 11:59:59	TBP
LGS	2007	Pattern	SAMPLE ROOM	2007-05-22 06:12:43	2007-05-22 08:53:09	SBP
LGS	2010	Pattern	A-RACEWAY / RIVER EXIT	2010-06-07 14:30:14	2010-06-07 15:19:59	TBP
LMN	2003	CBR Sites Config	B-RACEWAY	2003-05-26 22:48:00	2003-05-27 03:12:00	TBP
LMN	2004	Pattern	A-RACEWAY	2004-06-28 04:59:08	2004-06-29 13:53:04	TBP
LMN	2005	Pattern	B-RACEWAY	2005-05-08 20:00:00	2005-05-08 23:59:59	TBP
LMN	2005	Pattern	A-RACEWAY	2005-05-08 20:00:00	2005-05-08 23:59:59	TBP
LMN	2005	Pattern	SAMPLE ROOM	2005-05-13 12:53:55	2005-05-13 14:17:45	SBP
LMN	2006	Pattern	B-RACEWAY	2006-04-30 06:43:46	2006-04-30 12:47:47	TBP
LMN	2008	Pattern	A-RACEWAY	2008-05-18 18:30:30	2008-05-18 23:59:59	TBP
LMN	2008	Pattern	B-RACEWAY	2008-05-18 18:30:30	2008-05-18 23:59:59	TBP
LMN	2008	Pattern	A-RACEWAY	2008-06-08 16:45:30	2008-06-10 04:43:44	TBP
LMN	2009	Pattern	SAMPLE ROOM	2009-05-13 13:31:54	2009-05-13 14:10:43	SBP
LMN	2009	Pattern	SAMPLE ROOM	2009-05-24 12:47:25	2009-05-24 13:04:57	SBP
LMN	2009	Pattern	B-RACEWAY	2009-06-05 18:25:16	2009-06-07 05:56:40	TBP
LMN	2011	Pattern	B-RACEWAY	2011-05-15 17:52:00	2011-05-15 23:59:59	TBP
LMN	2011	Pattern	A-RACEWAY	2011-05-15 18:49:01	2011-05-15 23:59:59	TBP
LMN	2011	Pattern	B-RACEWAY	2011-06-08 18:30:00	2011-06-08 23:59:59	TBP
LMN	2011	Pattern	A-RACEWAY	2011-06-08 20:13:00	2011-06-08 23:59:59	TBP
LMN	2011	Pattern	B-RACEWAY	2011-06-26 20:50:00	2011-06-26 23:59:59	TBP
MCN	2001	Pattern	B-RACEWAY	2001-05-18 07:48:19	2001-05-18 20:14:53	TBP
MCN	2001	Pattern	B-RACEWAY	2001-05-23 06:48:04	2001-05-23 10:12:54	TBP
MCN	2001	Pattern	B-RACEWAY	2001-05-25 06:02:44	2001-05-25 10:45:49	TBP
MCN	2001	Pattern	B-RACEWAY	2001-05-27 00:38:16	2001-05-27 10:03:45	TBP
MCN	2001	Pattern	B-RACEWAY	2001-05-31 02:43:35	2001-05-31 10:17:57	TBP
MCN	2001	Pattern	B-RACEWAY	2001-06-02 04:22:54	2001-06-02 09:43:30	TBP
MCN	2001	Pattern	SAMPLE ROOM	2001-06-19 06:12:34	2001-06-19 14:37:17	SBP
MCN	2003	Pattern	A-RACEWAY	2003-07-09 01:53:21	2003-07-09 23:24:02	TBP
MCN	2013	CBR Sites Config	B-RACEWAY	2013-01-01 00:00:00		TBP
MCN	2013	CBR Sites Config	A-RACEWAY	2013-01-01 00:00:00		TBP

Calculating 10 Year Averages

The 10 Year Averages are calculated by DART for each calendar day of data at each project. For the current year and any given project/month/day, the data from the previous 10 years on that calendar day is summed and divided by the number of non-null data points available. Calendar day averaging was chosen because, historically, data observations begin on a specific calendar day. Calendar day averaging gives different results than day of year averaging.

River Environment Glossary

Barometric Pressure: Barometric Pressure is atmospheric pressure at the site, given in mm Hg. It represents an average of hourly measures. Barometric Pressure is measured at Water Quality Monitoring stations in the forebay and tailrace of most projects (see Data Sites Map) and other key locations in the basin. Prior to 1995, the data are from a variety of sources within the U.S. Army Corps of Engineers.
Dissolved Gas: Dissolved gas is a measure of the pressure of dissolved gas in the water column. When spillway water plunges into the tailrace nitrogen is forced into the water at higher than normal levels. This condition, called supersaturation, occurs when dissolved gas pressure in the water actually exceeds the atmospheric pressure. The dissolved gas value represents a daily average of hourly meeasures within the range of 600-900 mmHg and is derived from U.S. Army Corps of Engineers gas monitoring efforts. Often collected at irregular intervals, this parameter may be missing values for one or more days, or reported values may be obviously incorrect. Dissolved Gas is measured at Water Quality Monitoring stations in the forebay and tailrace of most projects (see Data Sites Map) and other key locations in the basin. Prior to 1995, the data are from a variety of sources within the U.S. Army Corps of Engineers.
Dissolved Gas Percent: Gas percent reflects the degree of total dissolved gas supersaturation in the river at the given location. Gas percent is the daily mean of hourly observations. When gas pressure is exactly the same as the atmospheric pressure, the water is considered to be 100% saturated. If the gas pressure value is higher than atmospheric pressure, gas percent values rise above 100%. Daily averages are calculated from hourly values within the range of 90% to 200%. Gas percent data is often found to be quite noisy due to rapid fluctuations in spill volumes and atmospheric pressures. Dissolved Gas Percent is measured at Water Quality Monitoring stations in the forebay and tailrace of most projects (see Data Sites Map) and other key locations in the basin. Prior to 1995, the data are from a variety of sources within the U.S. Army Corps of Engineers.
Elevation: Elevation is given in feet above mean sea level and is a daily average of hourly measures. At most sites this will change less than a fraction of a foot over normal operations. Elevation is measured in the forebay of a project.
Elevation 10 Year Average: Daily average of elevation for a selected 10 year range. For each month and day, the data is summed for the selected 10 years and divided by the number of non-null data points available during that 10 year span.
Inflow: Inflow measurements represent the 24-hour average of hourly measures, reported by the U.S. Army Corps of Engineers. Inflow is given in kcfs, thousands of cubic feet per second.
Outflow: Outflow measurements represent the 24-hour average of hourly measures, reported by the U.S. Army Corps of Engineers. Outflow is given in kcfs, thousands of cubic feet per second. This represents the total outflow at any project, including spill and fish ladder flow.
Outflow 10 Year Average: Daily average of outflow for a selected 10 year range. For each month and day, the data is summed for the selected 10 years and divided by the number of non-null data points available during that 10 year span.
Spill: Spill also is given as a daily average of 24 hourly measures taken by the U.S. Army Corps of Engineers. It is also given in kcfs.
Spill 10 Year Average: Daily average of spill for a selected 10 year range. For each month and day, the data is summed for the selected 10 years and divided by the number of non-null data points available during that 10 year span.
Spill Percent: Spill Percent is calculated by DART from the daily averaged value for Spill divided by the daily averaged value for Outflow at a project.
Temperature (Scroll Case): Temperature (Scroll Case) is water temperature in degrees Celsius. This data is measured at the scroll case (part of the powerhouse) at a project. If provided values are in Fahrenheit, they are converted to Celsius. Temperature records are typically not collected outside the salmon migration season, so they are not usually 365 days long. Values above 0 C and below 35 C are averaged for a daily value.
Temperature (Scroll Case) 10 Year Average: Daily average of scroll case temperature for a selected 10 year range. For each month and day, the data is summed for the selected 10 years and divided by the number of non-null data points available during that 10 year span.
Temperature (WQM): Temperature (WQM) is water temperature in degrees Celsius. This data is measured at Water Quality Monitoring stations in the forebay and tailrace of most projects (see Data Sites Map) and other key locations in the basin. Forebay Temperature records are typically not collected outside the salmon migration season, so they are not usually 365 days long. Daily averages are calculated from hourly values above 0 C and below 35 C. Temperatures at water quality monitoring stations were not collected prior to 1995.
Temperature (WQM) 10 Year Average: Daily average of water quality monitor temperature for a selected 10 year range. For each month and day, the data is summed for the selected 10 years and divided by the number of non-null data points available during that 10 year span.
Temperature (WQM) 7DADM: Seven (7) Day Average Daily Maximum. For each day, the maximum hourly temperature value for that day and the previous six days are averaged. All 7 data points must be non-null or the calculated value for the day is null.
Temperature (WQM) 5DADA: Five (5) Day Average Daily Average. For each day, the daily average temperature value for that day and the previous four days are averaged. All 5 data points must be non-null or the calculated value for the day is null.
Turbidity: Turbidity measures the water clarity, and by inference, the amount of particulate matter present. Turbidity is measured in the forebay or in the fish ladders of a project. Turbidity is reported in feet and measured with a Secchi Disk. In general, the Secchi disk is a 20 cm circular black and white plate. The Secchi disk is attached to a calibrated line and lowered into the water to the depth at which it disappears. The disk is then lifted until it reappears. The arithmetic mean of the two depths is considered the Secchi disk transparency or limit of visibility.

Where Is Pit Tag Detection 437 Onthe Upper Salmon River Located

Source: http://www.cbr.washington.edu/dart/metadata/pit