Page 1 of 1

Success with Mark v5.1 but fail with Mark v6.1

PostPosted: Thu May 22, 2014 10:25 am
by TomK
Hi all

I analysed my data (305 individuals, 23 primary period, 3 secondary occasions) with MSORD successfully with Mark v5.1 and RMark 2.1.5. with Windows XP machine in the past.
I recently found that the same script and input data fail on some models (Markovian movement) with Mark v 6.1 and RMark 2.1.7 on my Windows8 paralleled on Mac machine.

Error message is:

"At line 142 of file chprob032.f90
Fortran runtime error: Index '0' of dimension 1 of array 'parm' below lower bound of 1
Error in if (loc[1] == -1) loc = regexpr(" = ", out[x]) - 1 :
missing value where TRUE/FALSE needed
In addition: Warning message:
running command '"c:/Program Files (x86)/Mark/mark64.exe" i=mark011.inp o=mark011.out v=mark011.vcv r=mark011.res threads=-1' had status 2”

I do not understand the nature of the problem. I would appreciate very much if someone can explain.
I’m submitting the R script and input data and I’d like them to work in the latest version!

Re: Success with Mark v5.1 but fail with Mark v6.1

PostPosted: Thu May 22, 2014 10:34 am
by cooch
TomK wrote:... I’d like them to work in the latest version!


You might start by actually trying the latest version -- 7.2

http://www.phidot.org/software/mark/dow ... /setup.exe

Re: Success with Mark v5.1 but fail with Mark v6.1

PostPosted: Thu May 22, 2014 12:34 pm
by TomK
Thank you Gary

I installed Mark v7.2 and tried

unfortunately error (slightly different) again

error message is:
At line 142 of file chprob032.f90
Fortran runtime error: Index '0' of dimension 1 of array 'parm' below lower bound of 1
Error in if (loc[1] == -1) loc = regexpr(" = ", out[x]) - 1 :
missing value where TRUE/FALSE needed
In addition: Warning message:
running command '"c:/Program Files (x86)/Mark/mark64.exe" i=mark013.inp o=mark013.out v=mark013.vcv r=mark013.res threads=-1' had status 2

Re: Success with Mark v5.1 but fail with Mark v6.1

PostPosted: Mon Aug 04, 2014 9:42 pm
by bdt
TomK,
Did you solve this problem? I'm getting a similar error message.
bdt