paramlink (version 0.7-0)

linkdat: linkdat objects

Description

Functions to create and display 'linkdat' objects.

Usage

linkdat(ped, model=NULL, map=NULL, dat=NULL, freq=NULL, verbose=TRUE, 
        missing=0, ...)

## S3 method for class 'linkdat':
print(x, ..., markers)

## S3 method for class 'linkdat':
summary(object, ...)

## S3 method for class 'linkdat':
as.data.frame(x, ..., famid=F, markers=seq_len(x$nMark), 
        alleles=NULL, missing=NULL, singleCol=FALSE, sep="")

## S3 method for class 'linkdat':
subset(x, subset=x$orig.ids, ..., markers=seq_len(x$nMark))

write.linkdat(x, prefix="", what=c("ped", "map", "dat", "freq", "model"), 
              merlin=FALSE)

Arguments

ped

a matrix, data.frame or a character with the path to a pedigree file in standard LINKAGE format.

model

either a linkdat.model object (typically y$model for some linkdat object y), or a single integer with the following meaning: 1 = autosomal dominant; 2 = autosomal recessive; 3 = X-linked dominant; 4 = X-linked rece

map

a character with the path to a map file in MERLIN format. If non-NULL, a dat file must also be given (next item).

dat

a character with the path to a dat file in MERLIN format. (Only needed if map is non-NULL.)

freq

a character with the path to a allele frequency file in MERLIN (short) format. If NULL, all markers are interpreted as equifrequent.

verbose

a logical: verbose output or not.

markers

a numeric indicating which markers should be included/printed.

x, object

a linkdat object.

famid

a logical indicating if the family identifier should be included as the first column.

alleles

a character containing the allele names, e.g. alleles=c("A","B").

missing

a character of length 1 indicating how missing alleles should be represented.

singleCol

a logical: Should the two alleles for each marker be pasted into one column or kept in separate columns?

sep

a single character to be used as allele separator if singleCol=TRUE.

subset

a numeric containing the individuals in the sub-pedigree to be extracted. NB: No pedigree checking is done here, so make sure the subset form a meaningful, closed pedigree.

prefix

a character string giving the prefix of the files. For instance, if prefix="fam1" and what=c("ped", "map"), the files "fam1.ped" and "fam1.map" will be created.

what

a character vector forming a subset of c("ped", "map", "dat", "freq", "model"), indicating which files should be created. All files are written in MERLIN style (but see the next item!)

merlin

a logical. If TRUE, the marker alleles are relabeled to 1,2,..., making sure that the generated files are readable by MERLIN (which does not accept non-numerical allele labels in the frequency file.) If FALSE (the default) the allele labels are unchanged

...

further arguments.

Value

• A linkdat object, or a list of linkdat objects. A linkdat object is essentially a list with the following entries, some of which can be NULL.
• pedigree
  data.frame with 5 columns (ID, FID, MID, SEX, AFF) describing the pedigree in linkage format. (NB: Internal labeling used.)
• orig.ids
  the original individual id labels.
• nInd
  the number of individuals in the pedigree.
• founders
  vector of the founder individuals. (NB: Internal labeling used.)
• nonfounders
  vector of the nonfounder individuals (NB: Internal labeling used.)
• subnucs
  list containing all (maximal) nuclear families in the pedigree. Each nuclear family is given as a vector of the form c(pivot, father, mother, child1, ...), where the pivot is either the id of the individual linking the nuclear family to the rest of the pedigree, or 0 if there are none. (NB: Internal labeling used.)
• markerdata
  a list of marker objects.
• nMark
  the number of markers.
• available
  a numeric vector containing IDs of available individuals. Used for simulations and plots.
• model
  a linkdat.model object, essentially a list containing the model parameters. See setModel for details.
• initial_probs
  (Not relevant for end users.)

Details

The file (or matrix or data.frame) ped must describe one or several pedigrees in standard LINKAGE format, i.e. with the following columns in correct order: 1 Family id (optional) (FAMID) 2 Individual id (ID), 3 Father id (FID), 4 Mother id (MID), 5 Gender (SEX): 1 = male, 2 = female, 6 Affection status (AFF): 1 = unaffected, 2 = affected, 0 = unknown, 7 First allele of first marker, 8 Second allele of first marker, 9 First allele of second marker, a.s.o. Only columns 2-6 are mandatory. The first column is automatically interpreted as family id if it has repeated elements. Internally the individuals are relabeled as 1,2,..., but this should rarely be of concern to the end user. Some pedigree checking is done, but it is recommended to plot the pedigree before doing any analysis. Details on the formats of map, dat and frequency files can be found in the online MERLIN tutorial: http://www.sph.umich.edu/csg/abecasis/Merlin/

See Also

setModel, modifyPedigree, linkdat.utils

Examples

data(toyped)
toyped
x = linkdat(toyped, model=1)
x
summary(x)

# test read/write:
x = modifyMarker(x, 1, alleles=c('B','C'), afreq=c(.9, .1), chrom=2, name="SNP1", pos=123)
write.linkdat(x, prefix="toy")
y = linkdat("toy.ped", map="toy.map", dat="toy.dat", freq="toy.freq", model=1)
unlink(c("toy.ped", "toy.map", "toy.dat", "toy.freq", "toy.model"))
stopifnot(isTRUE(all.equal(x,y)))