Chapter 4
The Parameter File


Table 4.1: Valid codes for entries in the parameter file
Code WithinIndicator for
RUNOP Line with run options
COMMENT  Comment line
PEDS Name of pedigree file
DATA Name of data file
TRNOS DAT Trait numbers (grouped input)
NAMES DAT Multiple column names (grouped input)
ANALYSIS Code for analysis type
MODEL Model of analysis
FIX MOD Name of fixed effect
COV MOD Name of fixed covariable
RAN MOD Name of random effect
RRC MOD Name of control variable
EXT MOD Name extra variable
TRAIT MOD Trait name
ZEROUT Fixed effects levels to be set to zero
PSEUDOFX Random effects levels to be treated as random
SE+USR Additional, user defined functions of covariances
SUM SE+ Weighted sum
VRA SE+ Variance ratio
COR SE+ Correlation
VARIANCE Name of random effect
RESIDUAL
ERROR
END

All information on the the model of analysis and the data and pedigree files is specified through the parameter file.

The name of the parameter file should have extension ’.par’. By default, WOMBAT expects to find a file wombat.par in the current working directory.
Other filenames can be specified at run time as the last command line option – see 5 for details.

Setting up the parameter file is straightforward, but care and attention to detail are required to get it ‘just right’. The worked examples give ‘templates’ for various types of analyses which are readily adaptable to other problems. Parsing of the lines in the parameter file is fairly elementary, hence it is important to adhere strictly to the format described in the following in painstaking detail.

WOMBAT performs a limited number of consistency checks on the variables and models specified, but these are by no means exhaustive and should not be relied upon !

If WOMBAT does find an obvious error, it will stop with a message like “exit WOMBAT” or, in verbose mode, “Programmed(error) stop for WOMBAT encountered”. Inconsistencies or errors not discovered are likely to wreak havoc in subsequent steps !

HINT: Use the -v option at run time. This will cause WOMBAT to echo each line in the parameter file as it is read (to the screen) – if there is a programmed error stop at this stage, it is easier to find the mistake as you know which is the offending line.

 General rules
 4.1 Run options
 4.2 Comment line
 4.3 Analysis type
 4.4 Pedigree file
 4.5 Data file
  4.5.1 Simple
  4.5.2 Compact
 4.6 Model of analysis
  4.6.1 Effects fitted
  4.6.2 Traits analysed
 4.7 Covariance components
  4.7.1 Residual covariances
  4.7.2 Covariances for random effects
 4.8 Special information
  4.8.1 Dependencies among fixed effects
  4.8.2 Random effects to be treated as fixed
  4.8.3 Covariance components to be treated as fixed
  4.8.4 Additional functions of covariance components
  4.8.5 Miscellaneous