errcheckplcf: Looks to see if the 'plcf' of a fish seems faulty

In reumandc/fspack: Working package in support of synchrony analyses of fish movement

Description

Flags plcf records that seem faulty in various ways. Takes a single plcf and returns a code indicating whether it may be faulty and how.

Usage

errcheckplcf(obj, reldatetime, upstreamthresh, timethresh, distthresh)

Arguments

obj	A plcf object
reldatetime	Date and time of the release of the fish in the same numeric units used in obj$bpts
upstreamthresh	A threshold distance (km) of all-at-once upstream motion that disqualifies a record as unrealistic
timethresh	A threshold time (days) without being detected that is tolerated before a record is recommended to remove
distthresh	A distance threshold (km) without being detected that is tolerated before a record is recommended to remove. Both this and timethresh need to be exceeded before the record is removed for this reason.

Value

errcheckplcf returns a numeric code indicating whether the record seems faulty and if so what seems wrong with it. Codes are: N: no problem detected B: detections before the release U: went upsteam, in one shot, more than upstreamthresh T: went for too long AND travelled too far without being detected It is possible multiple problems occur; the error codes are concatenated.

Author(s)

Daniel Reuman, [e-mail]

Examples

#Not written yet but need some

reumandc/fspack documentation built on May 17, 2019, 7:46 p.m.