komonen wrote:The Gentle Introduction to Mark gives an excellent and understandable piece-by-piece introduction to the logic behind mark-recapture analysis and the Mark software. Except,
it does not tell how to technically create a .INP file (i.e transform .txt file to .inp file)?
Without this information the manual is not for "complete morons", and thus I (and many others) won't be able to use the program either.
Cheers, Atte
As stated quite explicitly in Chapter 2 (did you read it?) - wrt to creating .INP files (i.e., the simple text file containing the encounter histories).
While this is easy enough in principal, you surely don’t want to have to construct capture-histories manually. Of course, this is precisely the sort of thing that computers are good for - large-scale data manipulation and formatting. MARK does not do the data formatting itself - no doubt you have your own preferred “data manipulation" environment (dBASE, Excel, Paradox, SAS). Thus, in general, you’ll have to write your own program to convert the typical “vertical" file into capture histories. In fact, if you think about it a bit, you realize that in effect what you need to do is to take a vertical file, and “transpose" it into a horizontal file - where fields to the right of the individual tag number represent when an individual was recaptured or resighted. However, while the idea of a matrix transpose seems simple enough, there is one rather important thing that needs to be done - your program must insert the “0" value whenever an individual was not seen. We’ll assume for the purposes of this book that you will have some facility to put your data into the proper encounter history format. Of course, you could always do it by hand, if absolutely necessary!
In other words, MARK doesn't create encounter histories - you will need to figure out how to do it yourself, using either a database manipulation program of some kind (several are mentioned), or by hand. The .INP file is just a text file you've given the .INP extension to. This is also stated quite explicitly in Chapter 2:
It (.INP file) consists of an ASCII (text) file, consisting of the encounter history itself (the contiguous string of dummy variables), followed
by one or more additional columns of information pertaining to that history. Each record (i.e., each line) in the encounter histories file ends with a semi-colon. By convention, the encounter histories file
has a .INP suffix (for example, EXAMPLE1.INP). This is not required, but since MARK initially “looks" for encounter history files ending with .INP, it is recommended that you follow this convention if possible.
Much of this information is also contained in the MARK helpfile, which I guessing you didn't consult.