murray.efford wrote:I beg to differ: there may be no recaptures purely by chance, especially if the treatment has lowered density (we have very little to go on in the original post). Also: different methods for different treatments will give misleading results if the methods differ in bias, as they often do. Better to apply one method that works.
murray.efford wrote:Yes, Density has trouble automatically finding initial values for the parameters when there are no recaptures in a session. The way around this is to click on 'Manual' in Options | ML SECR and give it something plausible (I'd guess 2/ha, g0=0.1, sigma=40 m in your case, assuming a halfnormal detection function). Hope this works! (Remember to pool detection function parameters across sessions - 'constant' for g0 and sigma on the between-sessions page of Options | ML SECR).
murray.efford wrote:It's great you can make a some progress. Remember when you come to interpret the results that you've got there by assuming the same detection function applies in the two treatments. Without recaptures in both there's no hope of testing this. For good biological reasons, detection functions usually do change when density changes; you might mention this, but such issues are probably minor given the likely uncertainty in your estimates. A nonspatial (e.g. Zippin) approach does not provide a way out because you would then still have to assume equal movement.
Buffer widths in Density are not critical. unless they are too small. Having got an estimate of sigma you could safely set the buffer width to 4 x sigma or 5 x sigma and recompute. Try ML SECR | 2-D integration in the Help index if you want to get in more deeply.
Users browsing this forum: No registered users and 0 guests