by gstauffer » Mon Jan 07, 2013 12:18 pm
lb,
I think the key is to remember that unobservable states are defined in MARK (or whatever software you are using), not in the encounter histories (i.e., a zero in an encounter history denotes non-detection, not a specific state). Unobservable states are any states that you define in MARK that do not appear in any of the encounter histories.
For example, suppose you have individuals observable in three different states, A, B, or C, and you have reason to expect that there are three corresponding unobservable states, which you might call X, Y, and Z (but these codes of course do not appear in the encounter histories). You might set up a project in MARK and specify states A, B, C, X, Y, and Z. Because X, Y, and Z never appear in the encounter histories, you would now have defined them as 3 unobservable states. MARK will create corresponding PIMS for all the transitions. If some transitions are not biologically possible, you would set them to zero. For example, Psi (XY) might not be possible if individuals must first transition through B before they can get from X to Y.
I do have an MSORD analysis with 3 unobservable states (coded for RMark) if you think that would be useful to you. But I think once you understand how to set up the states in MARK, you should be on the right track.
Glenn