nonresidence events are only considered if the individuals monitored move from a station to another. Nevertheless, if an animal comes back to the same station, even after a long time (longer than the threshold set with the iTimeThreshold argument), the detection gap is not considered as a nonresidence event.
in the residence event file generated by the RunResidenceExtraction function, 'receiver' was automatically assigned to the ENDREASON variable if the individual's next detection occurs at a different station, even if the real reason for the ending of the residence event is that the residence time out. For example, if I set a 30-minute threshold with the iTimeThreshold argument and an individual is detected at station A on a given day and then at station B 4 hours later, "receiver" appear in the ENDREASON column, even if the residence event ended because the individual left the detection array for more than 30-minutes.
Raised by Benjamin Marsaly
nonresidence events are only considered if the individuals monitored move from a station to another. Nevertheless, if an animal comes back to the same station, even after a long time (longer than the threshold set with the iTimeThreshold argument), the detection gap is not considered as a nonresidence event.
in the residence event file generated by the RunResidenceExtraction function, 'receiver' was automatically assigned to the ENDREASON variable if the individual's next detection occurs at a different station, even if the real reason for the ending of the residence event is that the residence time out. For example, if I set a 30-minute threshold with the iTimeThreshold argument and an individual is detected at station A on a given day and then at station B 4 hours later, "receiver" appear in the ENDREASON column, even if the residence event ended because the individual left the detection array for more than 30-minutes.