mcmelnychuk wrote:How many receivers in the lake are we talking about (and are they grouped into clusters)?; how many tagged fish do you have?; what kind of a study duration & tag life do you have?; and do you tend to detect fish consistently after tagging (say most weeks, months, or seasons), or only sporadically? The requirements for estimated parameters (p, survival, transitions) may be too great for your dataset, but there could be the possibility of estimating p at each receiver over the given time step (weekly, monthly, seasonally...), especially if you can reasonably assume p's at a given receiver are either constant over a full year, or p's for all receivers vary individually but follow the same seasonal trend.
To follow up on Murray's comment, are you interested in p per se, or only as a means to estimate survival etc.?
I am interested in determining the probability of detection at each receiver only. Not survival nor the transition probability. I would like to use this data to better understand the number of fish entraining over Grand Coulee Dam that were missed by the receivers downstream.
There are anywhere from 4 up to 26 non-clustered receivers that were in my array, ranging from 1.5 to 6.5km apart. My receivers are mostly in a straight line (you can see a map of the study area here:
https://docs.google.com/file/d/0B-fbyPv ... sp=sharing ), except for a few along the two primary rivers that flow into the reservoir. We share data with folks upstream who have two more receiver arrays. Most individuals (n~25 per year) are detected continuously for several months. The transmitters pinged every ~2 minutes (1-3 min randomized delay).
Most years of tracking data have about 500,000 independent detections (and therefore occasions because each one has a unique time stamp).

It's a tremendous amount of data, which presents an issue with the numerical optimization step in MARK, and even working within the PIMs becomes a headache.
I'm concerned that any type of condensed time step (days, weeks, seasons) results in a loss of the very data I'm trying to enumerate. I toyed around with condensing the input to a daily step, but had lots of issues with fish being detected at multiple receivers in that one occasion. For instance, some individuals were detected moving back and forth between receivers upwards of 50+ times in a single day (e.g. multi state encounter history: ABCE...). This is the micro-movement data that I am most interested in - all those little misses between consecutive receivers where the fish SHOULD have been detected A--> B-->C-->D-->E ...etc. assuming it moved from A -->E.
... there has got to a better way to tackle this issue!