CERVUS3.0说明书(10)

parentage analysis program整理自软件help文件,下载过的朋友可以直接在help里查看。

5. The Cervus 2.0 simulation conflicted with certain antivirus software (e.g. McAfee).

Cervus 3.0 loads all input files into memory at the start of each run avoiding any conflict with antivirus software. Users of Cervus 2.0 affected by this conflict will notice a large

increase in the speed of simulations with Cervus 3.0.

6. In Cervus 2.0 identity analysis, the minimum number of matching loci used in analysis

was one greater than the value specified by the user. This bug has been fixed in Cervus

3.0.

Known problems and workarounds in Cervus 3.0

The following problems have been reported by users of Cervus 3.0.3. In each case, workarounds are suggested:

1. I/O error 206 "The filename or extension is too long" can occur during analysis,

particularly if the option to save distributions of LOD or Delta scores is selected in

Simulation Options. Workaround: ensure folder and file names are short and reduce the number of nested folders.

2. Cervus can occasionally crash when an input file is selected, most commonly a genotype

file. Workaround: turn off "Preview Input Files" on the Options menu.

3. Range check error or memory error occurs when conducting parent pair analysis with

very large numbers of candidate parents, typically 3000+. Workaround: 1) Reduce

number of candidate parents, or 2) Identify the ten or twenty most likely single parents

first, then use only these individuals as candidate parents in the parent pair analysis; this approach may mean each offspring has to be tested separately.

4. Floating point overflow occurs when conducting a simulation with very large numbers of

loci, typically 5000+. Workaround: reduce the number of loci. Note that reducing the

number of loci to, for example, 2500, will not generally affect the ability to assign

parentage.