Coding detector usage across sessions

Hi all,
I have a data set consisting of 12 sessions (59 occasions in total). For 11 of those 12 sessions, the detector array was identical (200 traps arranged in a 10x10 grid, with 2 traps at each point). However, for the first session I only used a subset of those traps (90 traps in a 10x9 grid, one trap per point).
I've tried coding this into the trap file like so...
A1A -45.0 -45.0 11111111111111111111111111111111111111111111111111111111111
A1B -45.0 -45.0 00001111111111111111111111111111111111111111111111111111111
But when I go to read.capthist I get the following error -
Session 1
Conflicting number of occasions in usage matrix
capthist : 4 occasions
usage(traps(capthist)) : 59 occasions
Evidently secr is assuming all occasions are part of the same session.
Is there a better way of approaching this? All I want to do is use a different trap layout for the first session.
I've considered just excluding the first session from the analysis, but session 2 has very low capture numbers which causes further issues with calculating start values.
Thanks,
Tom
I have a data set consisting of 12 sessions (59 occasions in total). For 11 of those 12 sessions, the detector array was identical (200 traps arranged in a 10x10 grid, with 2 traps at each point). However, for the first session I only used a subset of those traps (90 traps in a 10x9 grid, one trap per point).
I've tried coding this into the trap file like so...
A1A -45.0 -45.0 11111111111111111111111111111111111111111111111111111111111
A1B -45.0 -45.0 00001111111111111111111111111111111111111111111111111111111
But when I go to read.capthist I get the following error -
Session 1
Conflicting number of occasions in usage matrix
capthist : 4 occasions
usage(traps(capthist)) : 59 occasions
Evidently secr is assuming all occasions are part of the same session.
Is there a better way of approaching this? All I want to do is use a different trap layout for the first session.
I've considered just excluding the first session from the analysis, but session 2 has very low capture numbers which causes further issues with calculating start values.
Thanks,
Tom