cjacobs wrote:I somehow misintepreted my data when I posted it....this is what I meant to put ( only slight changes)
10101010101010101010101010101010101010101010101010101010101010 2 0;
10000000000000000000000000000000000000000000000000000000000000 1 0;
00101010101010101010101010101010101010101010101010101010101010 0 5;
00110000000000000000000000000000000000000000000000000000000000 0 1;
As you can see it contains 31 occasions (in LDLD format for Known Fate) and 9 individuals, 3 of which were tagged during the first week, and 6 of which were tagged during the second week. (The MARK manual says that I need a frequency column for each group). My complete data set includes 21 groups, so I have 21 frequency columns. While all of the individuals listed above are part of Study Area 1, I am unsure where I would include the information to differentiate Study Area 2 once I add it to the encounter history (I was going to just add 0's up to the week when these Study Area 2 individuals were tagged in November). Would I simply make the first freq. column (or first two depending on how I want to code it) code for the Study Area...and then just add the staggered entry after? I dont see how this would work...
Caitlin,
Your on the correct track with the structure for the different groups (21, which I assume are some sort of sex/age class designation?). As for including study area, if you follow the current .inp format you are using, you could just expand the 'groups' to 42 frequency columns giving you one unique column for each combination of group and area. Renumbering and labeling these groups in MARK will allow you to manipulate each PIM (representing a single group-area combination) independently, which I think is what you are after.
But, with 42 unique group*area combinations, will you have enough data to fit the models you are interested in? If you have 31 sampling occasions, you could, in theory, be talking about a lot of estimable parameters to deal with if you have group*time models that are of interest. So, be judicious in your model development.
Bret
PS: Sorry for being slow on response, was not anything to do with your question, I was on vacation.