Various data types in MARK have state transitions. The multi-state data types are obvious, but the robust designs, Barker models, and the multi-season occupancy models all suffer from the same issue when the intervals between occasions are unequal.
To illustrate the issue, consider the case where an encounter occasion is missing in the multi-state data type. Consider the following valid MARK 5-occasion multi-state encounter history A.A00, where the missing occasion is shown as a dot and there are 2 states, A and B, and occasions are all 1 time unit apart. To explain this dot, several possibilities exist, namely:

However, suppose that you coded the data with the dot left out, and set the time intervals to 2, 1, and 1. That is, only 4 occasions are considered instead of 5. So the encounter history is now AA00. Unfortunately, this approach is going to give very different results from the proper parameterization above. MARK does not generate the probabilities for the transition to state B with this parameterization. The probability of surviving from occasion 1 to occasion 2 would now be
, with no consideration that the animal could have moved to state B during the missing occasion. So, even the survival estimates will be incorrect. The
parameters for the first interval are not comparable to the
parameters for the second and third intervals because they represent different time scales.I have left the time interval correction on S, but have removed all time interval corrections from
. My logic is that when time intervals are “ragged”, e.g., 1.1, 0.9, 1.05, 0.95, it may still make sense to apply a correction to S. However, this correction is inappropriate for ψ, and may even be questionable for S. So, USER BEWARE!The same general issue applies to the robust design data types and to the multi-season occupancy models. Consider the robust design with 3 primary occasions, each with 2 secondary occasions. Assume that the data were not collected for the 2nd primary, giving an encounter history of 11..11. The missing primary encounter history again can be explained by 2 possibilities:

For the robust design data type, coding the encounter history as only 2 primary occasions, 1111, with time interval of 2 will give the correct parameterization for S (i.e.
), but as above, the
and
parameters cannot be corrected with this simple trick because the possibility of leaving the encounter area is not considered. So, for robust design data types (including the multi-state robust designs), only survival rates are corrected with the time interval, but none of the transition parameters are corrected. Again, USER BEWARE! Think carefully about what unequal time intervals may be doing to your interpretation of the parameter estimates.Multi-season occupancy models also suffer the same issue, because extinction (ε ) and colonization (γ) can occur during a missing primary occasion. So, consider 3 primary occasions with 2 secondary occasions in each, with a missing 2nd primary: 11..11. Two possibilities again explain the missing primary:

So, simple power corrections to ε and γ are not appropriate, and MARK does not apply such a correction. The user will have to consider how unequal time intervals are affecting the interpretation of parameter estimates.
As shown in all the cases above, coding a missing primary occasion with a set of dots should provide the necessary correction, although issues of parameter estimability come up. That is, unique estimates of the time-varying transition and survival probabilities are not possible, so the user will have to set some constraints to make the parameters estimable.