www.phidot.org

I have the following capture data:
#SessionID AnimalID Occasion TrapID sex
PC1 Bear001 2 FD15A 2
PC2 Bear001 2 BF2A 2
PC6 Bear001 8 FD14A 2
...
and trap data:
#TrapID x y pc1 pc2 pc3 pc4 pc5 pc6
FD15A 617917 3416967 3 3 3 3 3 3
BF2A 619036 3417885 3 3 0 0 3 3
...
I have 6 sessions of data, each with 8 observations. I have coded the trap data this way because some traps were not operable during all 6 years of the study.
Density reads this fine, but secr gives me an error message that the number of occasions between the capture and trap data do not match. This format has worked fine in the past in Density, but this is the first I have tried to run a robust design in secr. Thanks in advance!
Joe

Hi Joe
I think you may be confusing sessions (years) and occasions. The 'usage' columns in the trap file(s) relate to occasions within a session. If you sampled for 6 years with 8 checks in each then there should be 8 usage columns. If usage varied between sessions (years) then you will need a different trap file for each session (year); drop rows from the trap file if detectors were not operated. In DENSITY you can load multiple trap files having set Options | Input | Allow multiple trap files. In secr read.capthist allows a vector of trapfile names (see secr-datainput.pdf p6, noting caveat on checking match of sessions to trap files afterwards).
I hope it's this simple!
Murray

PS usage is usually binary 0/1; secr will take longer if you specify 0/3, and produce different estimates of g0

That did it. Thanks Murray!