filter_fish_detects: Example fish detection data which has been prefiltered and...

In filteRjsats: Filter Raw JSATS Acoustic Telemetry Files from Lotek, ATS, Teknologic

Example fish detection data which has been prefiltered and has fish data

Description

Example tag detection data representing a single file which has been processed using the prefilter() and add_fish() functions.

Usage

filter_fish_detects

Format

filter_fish_detects

A dataframe with 5,000 rows and 39 columns

ReceiverSN

the serial number of the acoustic receiver which heard the detection

Make

The Manufacturer of the acoustic reciever

DateTime_Local

The local date and time of the detection tz = "America/Los_Angeles"

Tag_Decimal

The decimal value of the tag ID code

Tag_Hex

The hexadecimal value of the tag ID code

Tilt

The tilt of the acoustic receiver from a vertical axis

Volt

The voltage of the on-board battery of the receiver

Temp

The water temperature outside of the receiver

SigStr

The strength of the acoustic signal in dB

Freq

The frequency of the acoustic signal in kHz

Thres

The relative amount of external background noise, signal threshold

CheckMBP

A calculated field from the first filter checking the time between acoustic transmissions from the same tag was >0.3secs

TagInFile

A calculated field from the add_fish filter which queries whether the tag code of the detection is associated with a fish.

fish_id

Identifies the fish that was tagged. It is unique in that no two fish have the same FishID. Format is 2 or more letters that describe the type of the fish (e.g. WR for WinterRun), followed by the year (YYYY), followed by a dash, then a sequential three digit number (e.g. 001 to 999)

study_id

Identifies a group of tagged fish that belong to a study. Format is text description of place followed by year (YYYY). A single StudyID can have fish release on multiple days within a year and/or at multiple locations within a year.

fish_type

Describes the fish tagged. Generally a part that describes where it came from and a part that refers to the common name.

fish_origin

Describes where the fish is from or where it was collected. Example: Hatchery, Natural, Sacramento River.

fish_date_tagged

The date and time that indicates the time the tag was activated and implanted into the fish. Tags are usually activated several minutes before implanting into fish in PST.

fish_release_date

The date and time of release in PST.

tag_id_hex

The hexadecimal form for the tags code. This is not unique in that two fish can have the same Hex Tag Code. This is usually from the same tag code being used in different years. This is why all queries must be based on Fish ID.

tag_id_decimal

The decimal form for the tags code. This is not unique in that two fish can have the same Decimal Tag Code. This is usually from the same tag code being used in different years. This is why all queries must be based on Fish ID.

tag_weight

weight of tag in air

tag_model

The model of the tag.

tag_pulse_rate_interval_nominal

The nominal (aka approximate) pulse rate interval. This is how often the tag transmits its code signal.

tag_warranty_life

The minimum number of days a tag is expected to transmit its code. Generally tags transmit for at least 1.5x the warranty life.

fish_length_type

The way the fish was measured. Fork length = FL, total length = TL, standard length = SL. If unknown = NA.

fish_length

Measured fish length in millimeters

fish_weight

Measured fish weight in grams (in air)

release_location

The name of the place that the fish was released.

release_latitude

The latitude of the release location.

release_longitude

The longitude of the release location.

release_river_km

The river km of the release location. The Golden Gate Bridge = rkm 0.0. Values increase the further upstream.

email

the email address of the point of contact that grants approval for using the data from each fish.

release_rkm

The river km of the release location. The Golden Gate Bridge = rkm 0.0. Values increase the further upstream.

tag_life

The minimum number of days a tag is expected to transmit its code. Generally tags transmit for at least 1.5x the warranty life.

length

Measured fish length in millimeters

weight

Measured fish weight in grams (in air)

CheckDT

A calculated field which checks whether the detection occurred after the release of the fish

CheckBattLife

A calculated field which checks whether the detection occurred before the tag battery is expected to expire (2x tag life)

filteRjsats documentation built on April 10, 2023, 5:07 p.m.