Varying trap effort

questions concerning anlysis/theory using program DENSITY and R package secr. Focus on spatially-explicit analysis.

Varying trap effort

Postby Prashant_mahajan » Mon Mar 03, 2025 11:48 pm

Hello,

I am trying to include effort as a covariate to model capture probability (g0). However, due to high variability in effort across detectors (range: 11 m to 7500 m), I am encountering the following warning message:

Extreme 'beta' in 'fastsecrloglikfn' (try smaller stepmax in nlm Newton-Raphson?)

As a result, my density estimates appear to be unreliable. However, when I exclude effort from the model, the results seem reasonable.

My study includes 289 detectors, with detections recorded at 92 of them. I would like to incorporate effort as a covariate while ensuring stable model performance. Could you suggest the best approach to handle this issue?

Thank you
Prashant_mahajan
 
Posts: 30
Joined: Wed Mar 31, 2021 11:14 am

Re: Varying trap effort

Postby murray.efford » Mon Mar 03, 2025 11:58 pm

There is no need to model effort as a covariate - just include a 'usage' attribute in the detector object. Pehaps that is what you are doing? Also, it may be better to use a hazard detection function (HHN, HEX) with parameter lambda0, not g0.
Murray
murray.efford
 
Posts: 712
Joined: Mon Sep 29, 2008 7:11 pm
Location: Dunedin, New Zealand

Re: Varying trap effort

Postby Prashant_mahajan » Tue Mar 04, 2025 1:05 am

Hi,

I have my summary of capthist as follows:

Object class capthist
Detector type count
Detector number 289
Average spacing 250 m
x-range 543232.1 556724 m
y-range 5261384 5286856 m

Usage range by occasion
1
min 11.81
max 7544.24

where usage 11.81 m is the min length of the transect in a detector and 7544.24 is the maximum length of the transect in a detector.

And my trap file looks like this:

X.TrapID X Y Effort
1 114 550982.1 5286142 246.74
2 115 551232.1 5286142 517.36
3 116 553232.1 5286142 76.02

The code for calling trap file is:

trapfile2021 <- read.traps(data = traps.2021, trapID = "trapID",
detector = "count",
binary.usage = FALSE)

And the model that I am using is this:

m.0 = secr.fit (coy.cap2021, model = list(D~1, lambda0~1, sigma~1),
mask = mask.2021, detectfn="HHN", method = "Nelder-Mead")

What should I put in lambda0 to make it as function of varying length of transects in each detector with a single occasion.

Best,
Prashant
Prashant_mahajan
 
Posts: 30
Joined: Wed Mar 31, 2021 11:14 am

Re: Varying trap effort

Postby murray.efford » Tue Mar 04, 2025 3:57 am

Nothing. If your detectors have a usage attribute that is automatically used as a sort of offset, by default.
murray.efford
 
Posts: 712
Joined: Mon Sep 29, 2008 7:11 pm
Location: Dunedin, New Zealand

Re: Varying trap effort

Postby Prashant_mahajan » Tue Mar 04, 2025 7:20 pm

Okay, thank you. But how can I determine the effect of effort on lambda0 when the model output only provides the intercept?
Prashant_mahajan
 
Posts: 30
Joined: Wed Mar 31, 2021 11:14 am

Re: Varying trap effort

Postby murray.efford » Tue Mar 04, 2025 7:34 pm

We are assuming a known relationship: doubling effort doubles the expected number of detections. How could it be otherwise? See Methods in Ecology and Evolution 2013, 4, 629–636. If you want a more clunky approach you can fit a detector-level covariate, but remember to suppress 'usage' (details = list(ignoreusage = TRUE)).
murray.efford
 
Posts: 712
Joined: Mon Sep 29, 2008 7:11 pm
Location: Dunedin, New Zealand

Re: Varying trap effort

Postby Prashant_mahajan » Wed Mar 05, 2025 3:22 pm

Okay great. Thank you so much.
Prashant_mahajan
 
Posts: 30
Joined: Wed Mar 31, 2021 11:14 am


Return to analysis help

Who is online

Users browsing this forum: No registered users and 1 guest