Page 1 of 1

Recovery model : Error in wtable intercept only model

PostPosted: Fri Dec 01, 2017 8:03 pm
by tlyons4
I'm trying to run a Seber dead recovery model and from the get-go, I can't get even a constant survival-constant recovery model to run. It throws the following error:

Code: Select all
STOP ERROR
MARK did not run properly.  If error message was not shown, look at most recent .out file

Model output is not available in R. Check contents of mark002.out

Error in wtable[i, cols] <- real[pim[i, cols]] :
  number of items to replace is not a multiple of replacement length


I can post a reproducable example of my data if needed, but here is what the data look like at a glance and the code I'm trying to run. I assume it's something wrong with the way I set up the data, but I don't know what I did wrong.

The data:
Code: Select all
str(CAGO.LD)
'data.frame':   810 obs. of  4 variables:
 $ ch       : chr  "000000000000000000000000000010" "000000000000000000000000000011" "000000000000000000000000001000" "000000000000000000000000001011" ...
 $ freq     : num  292 30 160 13 18 90 4 7 10 213 ...
 $ age.band : Factor w/ 2 levels "AHY","HY": 1 1 1 1 1 1 1 1 1 1 ...
 $ Band.Unit: Factor w/ 5 levels "NC","NE","PAN",..: 1 1 1 1 1 1 1 1 1 1 ...



The code:
Code: Select all
cago.mark<-process.data(CAGO.LD,model = "Recovery",groups=c("age.band","Band.Unit"))   
   
cago.ddl<-make.design.data(cago.mark)

S.dot=list(formula=~1)
r.dot=list(formula=~1)
                                                
m.0<-mark(data=cago.mark,ddl=cago.ddl,
            model.parameters=list(S=S.dot,
                              r=r.dot))


Thanks in advance for any help.

Re: Recovery model : Error in wtable intercept only model

PostPosted: Sat Dec 02, 2017 11:45 am
by jlaake
Did you do what the instructions said and look at the .out file that MARK created? That is where it will tell u what went wrong.

Re: Recovery model : Error in wtable intercept only model

PostPosted: Sat Dec 02, 2017 12:14 pm
by tlyons4
Sorry, I figured it out. I coded the LD in the recovery incorrectly. I was using the coding for a direct recovery for indirect recoveries as well. Sorry