Volume 13 Supplement 17

## Eleventh International Conference on Bioinformatics (InCoB2012): Bioinformatics

# A linear-time algorithm for reconstructing zero-recombinant haplotype configuration on a pedigree

- En-Yu Lai
^{1, 2}, - Wei-Bung Wang
^{3}, - Tao Jiang
^{3}and - Kun-Pin Wu
^{1}Email author

**13(Suppl 17)**:S19

https://doi.org/10.1186/1471-2105-13-S17-S19

© Lai et al.; licensee BioMed Central Ltd. 2012

**Published: **13 December 2012

## Abstract

### Background

When studying genetic diseases in which genetic variations are passed on to offspring, the ability to distinguish between paternal and maternal alleles is essential. Determining haplotypes from genotype data is called haplotype inference. Most existing computational algorithms for haplotype inference have been designed to use genotype data collected from individuals in the form of a pedigree. A haplotype is regarded as a hereditary unit and therefore input pedigrees are preferred that are free of mutational events and have a minimum number of genetic recombinational events. These ideas motivated the zero-recombinant haplotype configuration (ZRHC) problem, which strictly follows the Mendelian law of inheritance, namely that one haplotype of each child is inherited from the father and the other haplotype is inherited from the mother, both without any mutation. So far no linear-time algorithm for ZRHC has been proposed for general pedigrees, even though the number of mating loops in a human pedigree is usually very small and can be regarded as constant.

### Results

Given a pedigree with *n* individuals, *m* marker loci, and *k* mating loops, we proposed an algorithm that can provide a general solution to the zero-recombinant haplotype configuration problem in *O*(*kmn* + *k*^{2}*m*) time. In addition, this algorithm can be modified to detect inconsistencies within the genotype data without loss of efficiency. The proposed algorithm was subject to 12000 experiments to verify its performance using different (*n, m*) combinations. The value of *k* was uniformly distributed between zero and six throughout all experiments. The experimental results show a great linearity in terms of execution time in relation to input size when both *n* and *m* are larger than 100. For those experiments where *n* or *m* are less than 100, the proposed algorithm runs very fast, in thousandth to hundredth of a second, on a personal desktop computer.

### Conclusions

We have developed the first deterministic linear-time algorithm for the zero-recombinant haplotype configuration problem. Our experimental results demonstrated the linearity of its execution time in relation to the input size. The proposed algorithm can be modified to detect inconsistency within the genotype data without loss of efficiency and is expected to be able to handle recombinant and missing data with further extension.

## Keywords

## Background

A *genetic disease* is caused by the abnormality in an individual's genome. Genetic diseases have been studied extensively for decades by investigating the connection between diseases and genetic variations. In the human genome, chromosomes come in pairs; each gene consists of two *alleles* that reside in different chromosomes at the same locus. One of the two alleles comes from the father and the other comes from the mother. To study hereditary diseases in which the genetic variations are passed on to offspring, the ability to distinguish between paternal and maternal alleles is essential. Unfortunately, the *haplotype* structure of a human genome is not available directly from the genotyping and the unordered genotype data does not tell us which allele comes from which parent. A haplotype is a collection of alleles at multiple loci on a chromosome that tend to be inherited as a unit. The determination of haplotypes from genotype data is called *haplotype phasing* or *haplotype inference*. Algorithms for haplotype inference are indispensable and have been intensively studied.

*pedigree*. A pedigree is a hierarchical structure that describes the parent-child relationship among members of a family. Individuals without parents are called

*founders*. There may be cycles in a pedigree, which are referred to as

*mating loops*. A mating loop arises from a couple if they have children and both of them are offspring of certain family ancestors. An example of a pedigree, coupled with genotype data, is depicted in Figure 1(a); each allele is denoted as 0 or 1 to represent its form within a gene. If two alleles of a gene are the same, the locus is

*homozygous*; otherwise, it is

*heterozygous*. A haplotype is regarded as a hereditary unit and therefore an input pedigree is preferred to be free of mutational events and to have minimum number of genetic recombinational events [1]. Haplotype inference under this assumption is referred to as the

*minimum-recombinant haplotype configuration (MRHC)*problem, which requires the solving of the haplotype structure of the input pedigree with the minimum number of recombination events [1]. Several algorithms have been proposed to solve the MRHC problem [1–8]. A special case of MRHC is

*zero-recombinant haplotype configuration (ZRHC)*problem, which strictly follows the

*Mendelian law of inheritance*, namely that one haplotype of each child is inherited from the father and the other haplotype is inherited from the mother, without any mutation [9]. To reduce the complexity of the ZRHC, some algorithms have been applied to pedigrees without mating loops (called

*tree pedigrees*) [10–12]. In contrast to algorithms targeting tree pedigrees, so far no linear-time algorithm for ZRHC has been proposed for general pedigrees, even though the number of mating loops in a human pedigree is usually very small and can be regarded as constant; the execution time of existing algorithms for ZRHC using general pedigrees is polynomial [4, 13–17]. Regardless of whether it is a MRHC or a ZRHC problem, some algorithms have been extended to handle pedigrees with mutations or missing data [5, 8, 11, 15]. In addition to haplotype inference from pedigree data, algorithms have been proposed for

*population*datasets that come from unrelated individuals. Algorithms for population datasets try to decode the haplotype structure of each individual as well as the haplotype frequencies of a population [18–22]. All the above mentioned algorithms are mainly combinatorial. Readers who are interested in statistical approaches for haplotype inference can consult a recent review [23].

In this study, we have targeted the ZRHC problem for pedigree data. If we assume we are given a pedigree with *n* individuals and *m* marker loci. Then for general pedigrees, Li and Jiang proposed an *O*(*m*^{3}*n*^{3}) time algorithm by converting the inheritance process into an equivalent linear system of *O*(*mn*) equations over Galois field GF(2) and invoking Gaussian elimination [4]. Xiao et al. improved the method to take *O*(*mn*^{2} + *n*^{3} log^{2} *n* log log *n*) time by removing redundant equations from the linear system [16]. Doan et al. proposed an *O*(*mnα*(*m*)) time algorithm by exploring constraints among marker loci rather than family members, where *α*(·) is the inverse of the Ackermann function [14]. For tree pedigrees, the execution time of the algorithm proposed by Xiao can be reduced from *O*(*mn*^{2} + *n*^{3} log^{2} *n* log log *n*) to *O*(*mn* + *n*^{3}) [16]. Li and Li proposed an *O*(*mnα*(*n*)) time algorithm using disjoint-set data structures [11]. Liu et al. further lowered the complexity of Xiao's algorithm to linear time *O*(*mn*) [12]. Chan et al. also proposed a linear-time algorithm by maintaining a graph structure [10]. Chan's algorithm, however, only produce a particular solution. A *particular solution* assigns a numerical value to each system variable, while a *general solution* describes all possible solutions of the system by designating certain variables as free variables and the others as linear combinations of these free variables.

In this paper, we presented an *O*(*kmn* + *k*^{2}*m*) time algorithm that provides a general solution for ZRHC for general pedigrees, where *k* is the number of mating loops. In human pedigrees, *k* is usually very small and can be regarded as constant. Our algorithm therefore turns out to be linear for most of the practical cases. The proposed algorithm was subject to 12000 experiments to verify its performance using different (*n, m*) combinations. The value of *k* was uniformly distributed between zero and six throughout all experiments. The experimental results show a great linearity of the execution time in relation to the input size when both *n* and *m* are larger than 100. For those experiments where *n* or *m* are less than 100, the proposed algorithm runs very fast, from thousandth to hundredth of a second on a personal desktop computer. We also showed that the proposed algorithm can be easily modified to detect inconsistencies among genotype data without loss of efficiency.

## Methods

To apply computational techniques, we transformed the input pedigree into a *pedigree graph* by connecting each parent directly to its children (Figure 1(b)). A pedigree graph is an undirected graph *G* = (*V, E*), where *V* is a set of nodes and *E* a set of edges. Each node in *V* represents an individual in the pedigree; each pair of nodes is connected with an edge in *E* if and only if the two individuals have a parent-child relationship. *G* is defined to be undirected because the computational property of each edge is symmetric in our algorithm, even if the parent-child relationship is asymmetric. *G* may contain cycles. We only pay attention to two types of cycles: a cycle due to a mating loop, which is called a *global cycle* and a cycle due to a couple and two of their children, which is called a *local cycle*. Global cycles and local cycles are referred to as *basic cycles*. For ease of cycle processing, we construct a spanning tree *T* (*G*) on *G*. A basic cycle can be obtained by adding a non-tree edge into *T* (*G*). The set of non-tree edges is denoted by *E*^{
X
}. Non-tree edges are further divided into two disjoint subsets ${E}_{L}^{X}$ and ${E}_{G}^{X}$; members in ${E}_{L}^{X}$ induce local cycles and members in ${E}_{G}^{X}$ induce global cycles. Mating loops seldom appear in human pedigrees and therefore $\left|{E}_{G}^{X}\right|=k$ is regarded as a small constant.

*G*has

*n*nodes and

*m*loci, all alleles are bi-allelic (denoted by 0 or 1), and the input dataset is free of genotyping errors. Under this assumption, the input size of ZRHC is

*O*(

*mn*). The genotype data of a node

*n*

_{ i }are represented as a vector ${g}_{{n}_{i}}$ of size

*m*. The genotype of

*n*

_{ i }at locus

*l*, where 1 ≤

*l*≤

*m*, is defined as follows:

*g*-variables can be regarded as constant (Figure 1(b)). We introduce a vector ${p}_{{n}_{i}}$ of size

*m*to describe the haplotype information of

*n*

_{ i }; the paternal allele of

*n*

_{ i }at locus

*l*, where 1 ≤

*l*≤

*m*, is defined as follows:

The vector ${p}_{{n}_{i}}$ is regarded as unknown even though we know that ${p}_{{n}_{i}}\left[l\right]={g}_{{n}_{i}}\left[l\right]$ if *n*_{
i
} is homozygous at locus *l* (i.e. ${g}_{{n}_{i}}$[*l*] ≠ 2).

We formulated the ZRHC problem as follows.

**ZRHC** *Given a pedigree graph G*(*V, E*) *with full g-constants, determine* ${p}_{{n}_{i}}$ of each node *n*_{
i
} in *V*.

The haplotype configuration of the input pedigree is identified by specifying the paternal haplotype of each family member.

### A system of linear equations over GF(2)

*G*and

*g*-constants; this system was first proposed in [16] and will be reduced to determine all

*p*-variables. Since

*p*-variables carry binary values, all equations in the linear system are defined over GF(2) whose operations addition (+) and multiplication (·) are shown in Table 1.

Addition (+) and multiplication (*·*) in GF(2)

+ | 0 | 1 |
| 0 | 1 |
---|---|---|---|---|---|

0 | 0 | 1 | 0 | 0 | 0 |

1 | 1 | 0 | 1 | 0 | 1 |

#### The building block of the system: inheritance

*n*

_{ i }and a locus

*l, n*

_{ i }passes ${p}_{{n}_{i}}$[

*l*] + 1 to its children if and only if the genotype of

*n*

_{ i }at locus

*l*is heterozygous and

*n*

_{ i }passes its maternal allele; otherwise

*n*

_{ i }passes ${p}_{{n}_{i}}$ [

*l*] to its children. We introduce two auxiliary variables ${w}_{{n}_{i}}\left[l\right]{\text{and}h}_{{n}_{i},{n}_{j}}$ to formally state the above argument. The variable ${w}_{{n}_{i}}\left[l\right]$ indicates if locus

*l*of

*n*

_{ i }is heterozygous.

*n*

_{ i }is passed to its child

*n*

_{ j }.

Therefore, ${p}_{{n}_{i}}\left[l\right]+{w}_{{n}_{i}}\left[l\right]\cdot {h}_{{n}_{i},{n}_{j}}$ represents the allele at locus *l* that *n*_{
i
} passes to *n*_{
j
}.

*n*

_{ j }receives an allele from

*n*

_{ i }. If

*n*

_{ i }is

*n*

_{ j }'s father, what

*n*

_{ i }passes to

*n*

_{ j }is the paternal allele of

*n*

_{ j }. In this case, we have ${p}_{{n}_{i}}\left[l\right]+{w}_{{n}_{i}}\left[l\right]\cdot {h}_{{n}_{i},{n}_{j}}={p}_{{n}_{j}}\left[l\right]$. If

*n*

_{ i }is

*n*

_{ j }'s mother, there are two sub-cases. If locus

*l*of

*n*

_{ j }is homozygous, what

*n*

_{ i }passes to

*n*

_{ j }must be the same as the paternal allele of

*n*

_{ j }. In this case, we have ${p}_{{n}_{i}}\left[l\right]+{w}_{{n}_{i}}\left[l\right]\cdot {h}_{{n}_{i},{n}_{j}}={p}_{{n}_{j}}\left[l\right]$. If locus

*l*of

*n*

_{ j }is heterozygous, what

*n*

_{ i }passes to

*n*

_{ j }is the maternal allele of

*n*

_{ j }and is different from the paternal allele of

*n*

_{ j }. In this case, we have ${p}_{{n}_{i}}\left[l\right]+{w}_{{n}_{i}}\left[l\right]\cdot {h}_{{n}_{i},{n}_{j}}={p}_{{n}_{j}}\left[l\right]+1$. The variable ${w}_{{n}_{j}}\left[l\right]$ can be used to indicate if locus

*l*of

*n*

_{ j }is homozygous or heterozygous, the two sub-cases can therefore be combined into a single equation ${p}_{{n}_{i}}\left[l\right]+{w}_{{n}_{i}}\left[l\right]\cdot {h}_{{n}_{i},{n}_{j}}={p}_{{n}_{j}}\left[l\right]+{w}_{{n}_{j}}\left[l\right]$. Moreover, if we introduce another auxiliary variable ${d}_{{n}_{i},{n}_{j}}\left[l\right]$ as follows,

Note that the *w*- and *d*-variables are constant by definition, and the *p*- and *h*-variables are unknowns. Equation (1) formulates the property of edge (*n*_{
i
}*, n*_{
j
}) in *G*: *p*-variables and *w*-constants are attributes of the nodes *n*_{
i
} and *n*_{
j
}, and *h*-variables and *d*-constants describe the inheritance relation associated with the edge (*n*_{
i
}*, n*_{
j
}). With the information provided by Equation (1), various constraints on *h*-variables can be generated by traversing different paths in *G*. Our algorithm was designed to first determine *h*-variables based on these constraints and then the solution to the ZRHC problem can be obtained by determining all *p*-variables based on the solved *h*-values and Equation (1). One point needs special care: if *n*_{
j
} is a child of ${n}_{i},{h}_{{n}_{j},{n}_{i}}$ and ${d}_{{n}_{j},{n}_{i}}$ are undefined. In our algorithm, we make the *h*-variables and *d*-constants symmetrical such that ${h}_{{n}_{j},{n}_{i}}={h}_{{n}_{i},{n}_{j}}$ and ${d}_{{n}_{j},{n}_{i}}={d}_{{n}_{i},{n}_{j}}$.

#### Linear constraints on h-variables

To reduce the computational complexity of our algorithm, we try to make the number of unknowns in the coming linear system as small as possible. In the pedigree graph *G*, we have *mn p*-variables and at most 2*n h*-variables (since each individual has two parents and there are at most *n* individuals). Observe that if a node *n*_{
i
} itself or one of its parents is homozygous at locus *l*, ${p}_{{n}_{i}}\left[l\right]$ is determined by definition and Equation (1). In this case *n*_{
i
} is referred to as *predetermined* at locus *l* and the number of unknown *p*-variables is reduced by one. Moreover, for an edge (*n*_{
i
}*, n*_{
j
}) ∈ *E*, where *n*_{
i
} is a parent of ${n}_{j},\phantom{\rule{0.3em}{0ex}}{h}_{{n}_{i},\phantom{\rule{0.3em}{0ex}}{n}_{j}}$ is cancelled from Equation (1) if ${w}_{{n}_{i}}\left[l\right]=0$ at locus *l*. If ${w}_{{n}_{i}}\left[l\right]=0$ holds for all 1 ≤ *l* ≤ *m*, no constraints are imposed on ${h}_{{n}_{i},{n}_{j}}$ and it becomes a free variable (or its value will finally depend on other free variables). In this case the number of *h*-variables to be determined is reduced by one, which is equipotent to the removal of edge (*n*_{
i
}*, n*_{
j
}) from *G*. Accordingly, *w*-constants can be viewed as the weight of edges in *G*; we only pay attention to edges with weight one (parent nodes that are heterozygous). To consider only the edges with weight one at locus *l*, we construct the *lth locus graph G*_{
l
} = (*V, E*_{
l
}), where *E*_{
l
} = {(*n*_{
i
}*, n*_{
j
}) | *n*_{
i
} is a parent of *n*_{
j
}, ${w}_{{n}_{i}}\left[l\right]=1$}. Moreover, the spanning forest *T*(*G*) ∩ *G*_{
l
} is denoted by *T*(*G*_{
l
}) and is referred to as the *lth locus forest* (Figure 1(c)).

*h*-variables by traversing paths in the locus graphs. Consider a path

*p*=

*n*

_{0},

*n*

_{1}, ...,

*n*

_{ i }in

*G*

_{ l }. Assume that

*n*

_{0}and

*n*

_{ i }are predetermined and all other in-between nodes are non-predetermined. Adding up all

*h*-variables on the path will produce the following equation by Equation (1):

*n*

_{0}and

*n*

_{ i }are predetermined and all

*d*-constants are known,

*b*is a constant. The constant

*b*is said to be the constraint of path

*p*. Note that the constraint

*b*does not depend on the direction that path

*p*is read because the

*h*-variables and

*d*-constants are symmetric. Moreover, if the path is a cycle

*c*=

*n*

_{0},

*n*

_{1}, ...,

*n*

_{ i }

*, n*

_{0}in

*G*

_{ l }, we would have the following equation:

Again, since all *d*-constants are known, *b*' is also a constant. The constant *b'* is said to be the constraint of cycle *c*. On the basis of Equations (2) and (3), we can generate constraint equations with only *h*-variables for cycles or for paths that connect predetermined nodes in *G*_{
l
}. Constraints can be classified into two categories with respect to the spanning tree *T*(*G*): *cycle and path constraints* derived from paths containing non-tree edges, and *tree constraints* derived from paths containing only tree edges.

#### Cycle and Path constraints

Adding a non-tree edge *e* into the spanning tree *T* (*G*) generates a basic cycle *c*. If *G*_{
l
} contains *e*, there are two cases of *c* in *G*_{
l
}.

**Case 1** *c* is in *G*_{
l
}. A *cycle constraint b*_{
c
} of cycle *c* can be obtained by Equation (3). The constraint is denoted interchangeably by *b*_{
c
} or (*b*_{
c
}*, e*), which is also said to be the cycle constraint of *e*.

**Case 2** *c* is broken into several disjoint paths in *G*_{
l
} by predetermined nodes. Since these paths are disjoint, there is exactly one path *p'* of them containing *e*. Along the path *p',* we identify a subpath *p* = *n*_{
i
} ...*n*_{
j
} containing *e* such that *n*_{
i
} and *n*_{
j
} are predetermined and all other in-between nodes are non-predetermined. A *path constraint b*_{
p
} of the subpath *p* can be obtained by Equation (2). The constraint is denoted interchangeably by *b*_{
p
} or (*n*_{
i
}*, n*_{
j
}*, b*_{
p
}*, e*), which is also said to be the path constraint of *e*. Path constraints are symmetric because (*n*_{
i
}*, n*_{
j
}*, b*_{
p
}*, e*) = (*n*_{
j
}*, n*_{
i
}*, b*_{
p
}*, e*).

#### Tree constraints

For each connected component of *T* (*G*_{
l
}), we arbitrarily pick a predetermined node *n*_{
s
} as the seed. For the unique tree path *p* that connects *n*_{
s
} and another predetermined node *n*_{
k
} in the same connected component, a *tree constraint b*_{
t
} of path *p* can be obtained by Equation (2). The constraint is denoted interchangeably by *b*_{
t
} or (*n*_{
s
}*, n*_{
k
}*, b*_{
t
}). Tree constraints are symmetric because (*n*_{
s
}*, n*_{
k
}*, b*_{
t
}) = (*n*_{
k
}*, n*_{
s
}*, b*_{
t
}). Note that if there exists a component that has no predetermined nodes, locus *l* must be heterozygous across the entire pedigree and no tree constraints will be generated.

### Our algorithm in relation to the ZRHC problem

Our algorithm consists of four steps. We begin by initializing required data structures in the *preprocessing* step. The initialized data structures are subject to the *constraint generation* step to construct a system of linear constraints on *h*-variables. There are two issues should be addressed. First, since all constraints are derived from locus graphs that come from the same pedigree graph, there is usually redundancy in the system. Second, we actually do not need to know all *h*-values to solve the ZRHC problem. For a child node *n*_{
i
}, there are two *h*-variables related to it and its parents. However, from Equation (1) we know that one of the two *h*-values is sufficient to determine ${p}_{{n}_{i}}$. So it is easy to see that the (*n* - 1) *h*-variables in *T* (*G*) form a minimal sufficient set to solve the ZRHC problem. In the third step, *constraint reduction and transformation*, we therefore try to eliminate redundancy in the system and transform as many path constraints into tree constraints as possible. Finally, in the *haplotype determination* step, we introduce an efficient way to solve *h*-variables and further *p*-variables based on the reduced system.

#### Step 1: preprocessing

- 1.
Transform the pedigree into a pedigree graph

*G*= (*V, E*). Each node*n*_{ i }in*V*is equipped with its genotype vector ${g}_{{n}_{i}}$. Since each individual has two parents, there are at most 2*n*edges in*G*, so we have |*V*| =*O*(*n*) and |*E*| =*O*(*n*). - 2.
Construct a spanning tree

*T*(*G*) on*G*. - 3.For each locus
*l*,- (a)
generate a locus graph

*G*_{ l }, - (b)
generate a locus forest

*T*(*G*_{ l }), and - (c)
identify predetermined nodes as well as their

*p*-values, all*d*-constants, and all*w*-constants.

- (a)

The operations applied in this step are graph traversal and spanning tree construction, both operations can be performed in time *O*(| *V* | + | *E* |) = *O*(*n*). The time complexity of this step is therefore *O*(*mn*).

#### Step 2: constraint generation

A system of linear equations on *h*-variables over GF(2) will be constructed in this step. The system consists of three sets *C*^{
C
}*, C*^{
P
}, and *C*^{
T
} that contain different kinds of constraints. *C*^{
C
} contains cycle constraints, if any, of all non-tree edges at all loci. Similarly, *C*^{
P
} contains path constraints, if any, of all non-tree edges at all loci. Finally, *C*^{
T
} contains tree constraints at all loci. To reduce computational complexity, repetitions of set members are forbidden in our algorithm; we do nothing if an existing member is going to be added into the same set.

There are *O*(*mn*) trials to generate a constraint for a non-tree edge since there are *m* locus graphs and each of which contains *O*(*n*) non-tree edges; in each trial we perform a cycle detection procedure to generate a cycle constraint or a path constraint, so we have | *C*^{
C
} | + | *C*^{
P
} | = *O*(*mn*). The cycle detection procedure is usually implemented by depth first graph traversal and its execution time depends on the length of the cycle. Consequently, if a non-tree edge induces a global cycle, the cycle detection procedure takes *O*(*n*) time; otherwise the procedure takes constant time because each local cycle contains only four edges. The time to generate *O*(*mn*) cycle and path constraints is *O*(*kmn*) since there are at most *km* trials to generate global cycle constraints. To generate tree constraints within a locus graph, we perform tree traversal on its locus forest. This procedure generates *O*(*n*) tree constraints in *O*(*n*) time. So we require *O*(*mn*) time to generate tree constraints at all loci. The time complexity to generate our constraint system is therefore *O*(*kmn*) + *O*(*mn*) *= O*(*kmn*).

#### Step 3: constraint reduction and transformation

Redundancy arises in the constraint system if a constraint can be represented as a linear combination of other constraints. We are especially interested in the following two types of redundancies.

**Type 1**Assume there is a basic cycle

*c*in

*G*and it can be decomposed into two edge-disjoint paths

*p*

_{1}and

*p*

_{2}both connecting nodes

*n*

_{ i }and

*n*

_{ j }. There must be exactly a non-tree edge

*e*in

*c*, and without loss of generality, we assume that

*e*belongs to path

*p*

_{1}. If there is a cycle constraint (

*b*

_{ c }

*, e*) of

*c*, a path constraint (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{ p }

*, e*) of

*p*

_{1}, and a tree constraint (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{ t }) of

*p*

_{2}, we have

*b*

_{ c }=

*b*

_{ p }+

*b*

_{ t }by Equations (2) and (3). That is, these three constraints are linearly dependent and each of them can be represented as a linear combination of the other two constraints (Figure 2(a)). A path constraint can therefore be transformed into a tree constraint by the equation

*b*

_{ t }=

*b*

_{ p }+

*b*

_{ c }, which is the basis of the reduction of our constraint system.

**Type 2**Assume there are three tree constraints (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{1}), (

*n*

_{ i }

*, n*

_{ k }

*, b*

_{2}), and (

*n*

_{ j }

*, n*

_{ k }

*, b*

_{3}) of paths

*p*

_{1},

*p*

_{2}, and

*p*

_{3}, respectively. By definition we know that a tree constraint is the summation of all

*h*-variables along a unique path in

*T*(

*G*), so we have

*n*

_{ l }is the node closest to

*n*

_{ i }on the path

*p*

_{3}. We then have three paths

*p*

_{4}between

*n*

_{ i }and

*n*

_{ l }

*, p*

_{5}between

*n*

_{ l }and

*n*

_{ j }, and

*p*

_{6}between

*n*

_{ l }and

*n*

_{ k }such that

*p*

_{1}=

*p*

_{4}+

*p*

_{5},

*p*

_{2}=

*p*

_{4}+

*p*

_{6}, and

*p*

_{3}=

*p*

_{5}+

*p*

_{6}. The tree constraints can therefore be rewritten as

Because all constraints are defined over GF(2), we conclude that *b*_{1} + *b*_{2} = *b*_{3}; the three tree constraints are linearly dependent and each of them can be represented as a linear combination of the other two constraints (Figure 2(b)). The above argument implies the following lemma.

**Lemma 1** *For any three nodes n*_{
i
}*, n*_{
j
}*, and n*_{
k
}*, the tree constraint of the path between n*_{
j
} *and n*_{
k
} *is equal to the total tree constraint of the path between n*_{
i
} *and n*_{
j
} *and the path between n*_{
i
} *and n*_{
k
}.

Lemma 1 still holds even if *n*_{
i
} is on the path between *n*_{
j
} and *n*_{
k
} (*n*_{
i
} = *n*_{
l
} in Figure 2(b)), which means that if a tree path is partitioned into two disjoint sub-paths, the tree constraint of this path is equal to the total constraint of the two sub-paths.

In this step, we remove the type 1 redundancy by transforming as many path constraints to tree constraints as possible, and remove the type 2 redundancy by reducing *C*^{
T
} to an equivalent set whose cardinality is at most (*n* - 1).

For each non-tree edge *e* ∈ *E*^{
X
}, if cycle constraint (*b*_{
c
}*, e*) exists, we remove all path constraints (*n*_{
i
}*, n*_{
j
}*, b*_{
p
}*, e*), if any, from *C*^{
P
} and add tree constraints (*n*_{
i
}*, n*_{
j
}*, b*_{
c
} + *b*_{
p
}) into *C*^{
T
}. Since the size of *C*^{
P
} is *O*(*mn*), this procedure can be carried out in time *O*(*mn*), and the new *C*^{
T
} is of size *O*(*mn*).

*C*

^{ T }, we construct a

*constraint graph G**of

*G*. The constraint graph

*G**shares the same set of nodes

*V*as

*G*; for each tree constraint (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{ t }) ∈

*C*

^{ T }, we introduce an edge connecting nodes

*n*

_{ i }and

*n*

_{ j }in

*G**with weight

*b*

_{ t }(Figure 3(a)). An example of constraint graph is depicted in Figure 3(b). The constraint graph is used to reduce the size of

*C*

^{ T }. As shown in Figure 3(b), a constraint graph may not be connected. Within each connected component in

*G**, we randomly choose a seed

*n*

_{ s }and try to assign each node

*n*

_{ i }a variable

*W*[

*n*

_{ i }] to represents the tree constraint of the tree path between nodes

*n*

_{ s }and

*n*

_{ i }in the pedigree graph

*G*. The assignment is carried out by the following steps in each connected component of

*G**.

- 1.
*W*[*n*_{ s }] of the seed*n*_{ s }is assigned the value zero, - 2.
start from

*n*_{ s }, perform a breadth-first-search traversal via tree constraints, i.e., we can traverse from node*n*_{ i }to node*n*_{ j }if (*n*_{ i }*, n*_{ j }*, b*_{ t }) ∈*C*^{ T }or (*n*_{ j }*, n*_{ i }*, b*_{ t }) ∈*C*^{ T }, - 3.
as we traverse from

*n*_{ i }to*n*_{ j }through (*n*_{ i }*, n*_{ j }*, b*_{ t }) or (*n*_{ j }*, n*_{ i }*, b*_{ t }), if*n*_{ j }is unvisited, we assign*W*[*n*_{ i }] +*b*_{ t }to*W*[*n*_{ j }] based on Lemma 1; otherwise we do nothing.

Since *W*[*n*_{
i
}] represents the tree constraint (*n*_{
s
}*, n*_{
i
}*, W*[*n*_{
i
}]), it can be regarded as the summation of *h*-variables along the unique path on *T*(*G*) from the seed *n*_{
s
} to node *n*_{
i
}, which implies the following lemma:

**Lemma 2** *The h-value of a tree edge (n*_{
i
}*, n*_{
j
}*) in T(G) can be obtained by*${h}_{{n}_{i},{n}_{j}}=W\left[{n}_{i}\right]+W\left[{n}_{j}\right]$ *if n*_{
i
} *and n*_{
j
} *reside in the same connected component of G**.

Therefore, if we can assign *W*-values to all nodes in *V* and make *G** connected, *G** would be equipotent to a reduced *C*^{
T
} of size (*n* - 1) that covers *h*-variables of all tree edges of *T*(*G*) and is sufficient to solve the ZRHC problem. The construction of the constraint graph takes *O*(|*C*^{
T
}|) = *O*(*mn*) time.

The constraint graph *G**, however, may not be connected with fully assigned *W*-values. We therefore introduced an extension procedure to extend *G** by adding extra tree constraints, if any, into *G**; we would like to reduce the number of connected component in *G** as much as possible. To explore more tree constraints to be added into *G**, we examine those non-tree edges *e* ∈ *E*^{
X
} that do not have cycle constraints in *C*^{
C
}. The basic idea is that if we can synthesize a new cycle whose constraint is the same as the expected cycle constraint of *e*, we may obtain new tree constraints by transforming known path constraints of *e*.

*e*without cycle constraint, we try to synthesize a cycle only if $e\in {E}_{G}^{X}$. We do nothing if $e\in {E}_{L}^{X}$ because no extra tree constraints of

*e*can be obtained by cycle synthesis. To see this, suppose the local cycle induced by

*e*connects a couple

*n*

_{ a }and

*n*

_{ b }and their two children

*n*

_{ c }and

*n*

_{ d }; without loss of generality, we assume

*e*= (

*n*

_{ a }

*, n*

_{ d }) (Figure 4). We can examine the possible constraints derived from this local cycle. Constraints of a single edge with predetermined endpoints are not of interest and can be ignored because the

*p*-values of the endpoints are known; we need only pay attention to constraints whose path lengths are longer than one. In the

*l*th locus graph, if ${w}_{{n}_{a}}\left[l\right]={w}_{{n}_{b}}\left[l\right]=1$, a local cycle exists and we have cycle constraint (

*b*

_{ c }

*, e*) (Figure 4(a)); if ${w}_{{n}_{a}}\left[l\right]=1$ and ${w}_{{n}_{b}}\left[l\right]=0$, we only have the path

*p*

_{1}=

*n*

_{ c }

*n*

_{ a }

*n*

_{ d }with path constraint (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ p }

*, e*) (Figure 4(b)); if ${w}_{{n}_{a}}\left[l\right]=0$ and ${w}_{{n}_{b}}\left[l\right]=1$, we only have the path

*p*

_{2}=

*n*

_{ c }

*n*

_{ b }

*n*

_{ d }with tree constraint (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ t }) (Figure 4(c)); if, ${w}_{{n}_{a}}\left[l\right]={w}_{{n}_{b}}\left[l\right]=0$ all four nodes are predetermined and we can determine their

*p*-values directly (Figure 4(d)). No useful constraints other than (

*b*

_{ c }

*, e*), (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ p }

*, e*), and (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ t }) can be derived from this local cycle. Here we already know that (

*b*

_{ c }

*, e*) does not exist. If (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ t }) is already in

*C*

^{ T }, it is the only useful tree constraint of

*e*and we are finished. If (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ t }) does not exist in

*C*

^{ T }, we cannot obtain (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ t }) by combining

*b*

_{ c }and

*b*

_{ p }because (

*b*

_{ c }

*, e*) does not exist, even if the path constraint (

*n*

_{ c }

*, n*

_{ d }

*, b*

_{ p }

*, e*) is available. If this case holds for all 1 ≤

*l*≤

*m*, our linear system actually provides no information to obtain the tree constraint of

*p*

_{2}; the

*h*-variable of each edge on

*p*

_{2}will eventually be assigned a free variable, or its value will depend on other free variables. Therefore we do nothing if $e\in {E}_{L}^{X}$.

Assume that *E*^{
S
} is the set of non-tree edges in ${E}_{G}^{X}$ without cycle constraint. Cycle synthesis is carried out by concatenating paths with known path constraints or tree constraints. The extension procedure is applied to *E*^{
S
} as follows.

*e*∈

*E*

^{ S }, we check if there is an odd number, say 2

*t*+ 1, of path constraints of

*e*that link different connected components in

*G**to form a

*synthetic cycle*(Figure 5(a)); a constraint is said to link two components

*A*and

*B*if one of its endpoints resides in

*A*and the other resides in

*B*. There is a special case whereby we can also obtain a synthetic cycle if two endpoints of a single path constraint reside in the same connected component (

*t*= 0). If no such 2

*t*+ 1 path constraints are found, we cannot synthesize a cycle of

*e*and do nothing; otherwise we perform the following tasks:

- E1.1assign the constraint $\left(\hat{{b}_{c}},e\right)$ to the synthetic cycle, where$\hat{{b}_{c}}=\underset{\left({n}_{i},{n}_{j},{b}_{p},e\right)?{S}_{e}}{?}W\left[{n}_{i}\right]+W\left[{n}_{j}\right]+{b}_{p},$(4)

*S*

_{ e }is the set of the chosen 2

*t*+ 1 path constraints;

- E1.2
for each path constraint $\left({n}_{x},{n}_{y},{b}_{p}^{\text{'}},e\right)$ in

*C*^{ P }, generate a tree constraint $\left({n}_{x},{n}_{y},\hat{{b}_{c}}+{b}_{p}^{\text{'}}\right)$ and add the new constraint into*G**; - E1.3
update

*G**; - E1.4
remove

*e*from*E*^{ S };

E2. If *E*^{
S
} becomes empty (there has been a synthetic cycle for every *e* in the original *E*^{
S
}), or no synthetic cycle is synthesized (*E*^{
S
} stays unchanged), we stop the extension procedure; otherwise we go back to E1 to start the next iteration.

We thus try to synthesize a cycle for each non-tree edge in *E*^{
S
} to generate new tree constraints and update *G**. To update *G**, if more than one connected component is combined into a new one by new tree constraints, we arbitrarily choose one of the old seeds from these connected components as a new seed, and perform a graph traversal to update *W*-values within the new connected component. A non-tree edge that fails to receive a synthetic cycle in a trial of cycle synthesis may benefit from a later updated *G** and therefore our extension procedure is designed to operate in an iterative fashion; the procedure terminates only if *G**cannot be updated anymore. In this procedure, a non-tree edge may be checked many times (in different iterations) to form a synthetic cycle. In the worst case scenario, only one cycle is synthesized in each iteration, so we require *k* iterations to perform *k* + (*k* - 1) + ... + 1 = *O*(*k*^{2}) trials of cycle synthesis.

*n*

_{ x }and

*n*

_{ y }that reside in the same connected component of

*G**, we know that

*W*[

*n*

_{ x }] +

*W*[

*n*

_{ y }] is actually the tree constraint of the path from

*n*

_{ x }to

*n*

_{ y }on

*T*(

*G*). The synthetic cycle is conceptually a round trip through tree edges and the non-tree edge

*e*. The value $\hat{{b}_{c}}$ in Equation (4) is therefore the summation of

*h*-variables along the round trip (Figure 5(b)). Now we demonstrate that $\hat{{b}_{c}}$ is the same as the cycle constraint of

*e*. We first show that there is exactly one

*h*-variable of

*e*in $\hat{{b}_{c}}$. According to Equation (4), we have 2

*t*+ 1

*h*-variables of

*e*in $\hat{{b}_{c}}$. Since we perform additions over GF(2), 2

*t*out of the 2

*t*+ 1

*h*-variables will be cancelled and we finally have only one

*h*-variable of

*e*in $\hat{{b}_{c}}$. To verify if $\hat{{b}_{c}}$is the same as the cycle constraint of

*e*in

*G*, we assume that the expected cycle constraint of

*e*is

*b*

_{ c }. We generate a set ${S}_{e}^{\prime}$ by converting path constraints (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{ p }

*, e*) in

*S*

_{ e }to tree constraints (

*n*

_{ i }

*, n*

_{ j }

*, b*

_{ c }+

*b*

_{ p }). It is easy to see that the converted 2

*t*+ 1 tree constraints also link connected components in

*G** to form a new synthetic cycle, and the corresponding round trip only contains tree edges in

*T*(

*G*).

*T*(

*G*) has no cycle and therefore each edge of this new round trip must be visited an even number of times, which means that its

*h*-variable will be cancelled in the new cycle constraint. So the constraint of the new synthetic cycle must be zero and we have the following equations:

Since there are 2*t* + 1 constraints in ${S}_{e}^{\prime}$, we have ${\sum}_{i=1}^{\left|{S}_{e}^{\prime}\right|}{b}_{c}={b}_{c}$. We then obtain $\hat{{b}_{c}}+{b}_{c}=0$ and conclude that $\hat{{b}_{c}}={b}_{c}$.

For each *e* ∈ *E*^{
S
}, the time to determine if there are odd number of path constraints that link connected components in *G** to form a cycle is *O*(*m*). This time complexity can be achieved by regarding each connected component as a single node and each path constraint of *e* as a single edge, and following *O*(*m*) edges to perform a depth-first traversal. Since there are *O*(*k*^{2}) cycle syntheses throughout the extension procedure, we require *O*(*k*^{2}*m*) time to find synthetic cycles. Once we synthesized a cycle for *e*, we require *O*(*m*) time to convert path constraints to tree constraints because there are at most *m* path constraints of *e* in *C*^{
P
}. There are *O*(*k*) non-tree edges in *E*^{
S
} and therefore the extension procedure takes *O*(*km*) time to perform constraint conversion. To update *G**, we require *O*(*n*) time to perform breadth-first traversal on every connected component to modify *W*-values similar to the way we initialize *G**. There are at most *k* synthetic cycles and therefore *G** is updated *O*(*k*) times in *O*(*kn*) time. In summary, the Step 3, *constraint reduction and transformation*, takes *O*(*k*^{2}*m*) + *O*(*km*) + *O*(*kn*) = *O*(*k*^{2}*m* + *kn*) time.

#### Step 4: haplotype determination

To solve the *h*-values of the tree edges of *T*(*G*) by Lemma 2, we try to make *G** produced by Step 3 connected. Firstly, we pay attention to the founders in the pedigree. Founders cannot be predetermined endpoints of paths with either path constraints or tree constraints and therefore founders must be isolated nodes in *G**. It is also impossible to know whether an allele of a founder is paternal or maternal. We attach a founder *n*_{
f
} to *G** by assuming that it passed its paternal haplotype to an arbitrary child *n*_{
c
}. The attachment can be done by assigning weight zero to the edge (*n*_{
f
}*, n*_{
c
}) of *G**, which implies ${h}_{{n}_{f},{n}_{c}}=0$ (*n*_{
f
} passes its paternal haplotype). There are *O*(*n*) edges in *G** and therefore the attachment of founders to *G** takes *O*(*n*) time.

*G**. A non-tree edge

*e*= (

*n*

_{ i }

*, n*

_{ j }) can link two connected components

*A*and

*B*if we can find a path constraint (

*n*

_{ k }

*, n*

_{ l }

*, b*

_{ p }

*, e*) of path

*p*that, without loss of generality, satisfies the following two conditions:

- 1.
*n*_{ k }and*n*_{ i }reside in*A*and have available*W*[*n*_{ k }] and*W*[*n*_{ i }] derived from the seed*n*_{ A }of*A*, - 2.
*n*_{ l }and*n*_{ j }reside in*B*and have available*W*[*n*_{ l }] and*W*[*n*_{ j }] derived from the seed*n*_{ B }of*B*.

If we can find such a non-tree edge *e*, we can decompose *p* into three parts: a sub-path from *n*_{
k
} to *n*_{
i
}, the non-tree edge *e*, and the sub-path from *n*_{
j
} to *n*_{
l
}. The constraints of these three parts are $W\left[{n}_{k}\right]+W\left[{n}_{i}\right],\phantom{\rule{2.77695pt}{0ex}}{h}_{{n}_{i},{n}_{j}},W\left[{n}_{j}\right]+W\left[{n}_{l}\right]$, respectively. This turns out that ${b}_{p}=W\left[{n}_{k}\right]+W\left[{n}_{i}\right]+{h}_{{n}_{i},{n}_{j}}+W\left[{n}_{j}\right]+W\left[{n}_{l}\right]$. The non-tree edge *e* therefore can be used to link components *A* and *B* with known *h*-value ${h}_{{n}_{i},{n}_{j}}={b}_{p}+W\left[{n}_{k}\right]+W\left[{n}_{i}\right]+W\left[{n}_{j}\right]+W\left[{n}_{l}\right]$. Since there are at most *O*(*mn*) path constraints to be checked, this procedure requires *O*(*mn*) time.

Finally, assume that there remain *t* connected components of *G**. We arbitrarily introduce (*t* -1) edges into *G** to make it connected. Our algorithm does not impose any constraint on these (*t* - 1) edges and therefore the weights of these edges can be safely set as free variables. We then update all *W*-values within the new connected *G** (new *W*-values may contain free variables), and apply Lemma 2 to determine the *h*-values of all edges in *T*(*G*). With these solved *h*-values as well as the *w*-constants and *d*-constants, we can determine the *p*-values of all nodes in the locus graphs by Equation (1).

The update of *G** takes *O*(*n*) time. Moreover, we require *O*(*n*) time to determine all *h*-values of edges in *T*(*G*). For a locus graph, the determined *h*-values are used to solve all *p*-values in *O*(*n*) time. Since there are *m* locus graphs, we require *O*(*mn*) time to determine the *p*-vectors of all nodes in *G*. Consequently, the three procedures of this step take *O*(*n*) + *O*(*mn*) + *O*(*n*) + *O*(*mn*) = *O*(*mn*) time.

## Results and discussion

### An execution example

In the first step, we transform the input pedigree into a pedigree graph *G* and construct a spanning tree *T*(*G*) on *G* (Figure 6(b)). There are three local cycles A-H-B-I-A, D-K-E-L-D, and P-R-Q-S-P and one global cycle B-F-C-G-D-L-O-Q-N-I-B in *G*. Edges A-H, E-L, Q-R, and B-F are chosen as non-tree edges within the four cycles. From the pedigree graph *G*, we construct the four locus graphs and forests that are depicted in Figure 6(c). The *p*-values of predetermined nodes, *w*-constants of all nodes, and *d*-constants of all edges within the four locus graphs are also identified.

In the second step, we generate all cycle, path, and tree constraints for each of the four locus graphs using Equations (2) and (3). For example, cycle A-H-B-I-A in the second locus graph has cycle constraint *h*_{
A, H
} + *h*_{
H, B
} +*h*_{
B, I
} +*h*_{
I, A
} = *d*_{
A, H
} [2] + *d*_{
H, B
} [2] +*d*_{
B, I
} [2] +*d*_{
I, A
}[2] = 0 + 1 + 1 + 0 = 0, and path G-C-F-B-I-N-Q in the third locus graph has path constraint of the non-tree edge B-F *h*_{
G, C
} + *h*_{
C, F
} + *h*_{
F, B
} + *h*_{
B, I
} + *h*_{
I, N
} + *h*_{
N, Q
} = *p*_{
G
}[3] + *d*_{
G, C
}[3] + *d*_{
C, F
} [3] + *d*_{
F, B
}[3] + *d*_{
B, I
} [3] + *d*_{
I, N
} [3] + *d*_{
N, Q
}[3] + *p*_{
Q
}[3] = 0 + 0 + 0 + 1 + 1 + 0 + 0 + 0 = 0.

At the end of this step we receive *C*^{
C
} = {(0, *e*_{
E-L
}), (0, *e*_{
Q-R
}), (0, *e*_{
A-H
})}, *C*^{
P
} = {(*I, H*, 0, *e*_{
A-H
}), (*N, G*, 0, *e*_{
B-F)
}, (*G, Q*, 0, *e*_{
B-F)
}, (*R, Q*, 0, *e*_{
R-Q
}), (*N, Q*, 0, *e*_{
B-F)
}}, and *C*_{
T
} = {(*I, N*, 0), (*G, K*, 0), (*G, L*, 0), (*G, O*, 0), (*Q, S*, 0)}.

In the third step, we obtain two new tree constraints (*R, Q*, 0) and (*I, H*, 0) by (0, *e*_{
Q-R
}) + (*R, Q*, 0, *e*_{
R-Q
}) and (0, *e*_{
A-H
}) + (*I, H*, 0, *e*_{
A-H
}), respectively. The set *C*^{
T
} is therefore extended to {(*I, N*, 0), (*G, K*, 0), (*G, L*, 0), (*G, O*, 0), (*Q, S*, 0), (*R, Q*, 0), (*I, H*, 0)}. We construct the initial constraint graph *G** based on the updated *C*^{
T
} (Figure 6(d)). In the initial *G**, we choose H, G, and Q as component seeds to determine *W*-values. We can further find that the three path constraints (*N, G*, 0, *e*_{B-F)},(*G, Q*, 0, *e*_{B-F)}, and (*N, Q*, 0, *e*_{B-F)}link three connected components to form a synthetic cycle of the non-tree edge B-F with constraint zero. So we further obtain three extra tree constraints (*N, G*, 0), (*G, Q*, 0), and (*N, Q*, 0) derived from the synthetic cycle and add them to *G**.

In the final step, we try to make *G** connected to solve all *h*-values. We first arbitrarily introduce eight edges A-H, B-I, C-G, D-G, E-L, J-N, M-O, and P-R to attach the eight founders to *G**; all the eight edges are of weight zero to imply that founders passes their paternal haplotypes to one of their children. Now there are only two connected components in *G**, one of which is an isolated node, F. we attach F to *G** by set *h*_{
B, F
} as a free variable. This final connected *G** is depicted in Figure 6(e). After the final update of *G**, all *h*-values other than *h*_{
B, F
}are zero, and *h*_{
B, F
} is free to be either zero or one. Given these known *h*-values, all *p*-values over the four locus graphs can be solved by Equation (1).

### Time complexity and experimental result

According to the analyses at the end of each step in Section 3, the time complexity of our algorithm is *O*(*mn*) (step 1: preprocessing) + *O*(*kmn*) (step 2: constraint generation) + *O*(*k*^{2}*m* + *kn*) (step 3: constraint reduction and transformation) + *O*(*mn*) (step 4: haplotype determination) = *O*(*kmn* + *k*^{2}*m*). Because *k* is regarded as a constant, our algorithm is linear.

To verify the efficiency and the correctness of our algorithm, we conducted some experiments using the proposed method. Our algorithm was implemented in C and was evaluated on a desktop computer equipped with Intel Core i7-2600 3.4 GHz CPU and 8 GB of RAM. The desktop ran Ubuntu Release 11.10 operating system with Linux kernel 3.0.0-16-generic and GNOME 3.2.1 graphical user interface.

*n*) and markers (

*m*). We applied the algorithm developed by Thomas

*et al*. [24] to generate 12 tree pedigrees with different

*n*values ranging from 30 to 400. To observe how the number of mating loops (

*k*) affects our algorithm, each tree pedigree was preprocessed to produce four variants with zero, two, four, and six mating loops. For each pedigree, we examined 10 different

*m*values ranging from 10 to 300. Each (

*n, m*) combination was tested 100 times. Each time we generated new genotypes and randomly selected one pedigree from the four variants of the given

*n*. The haplotype configurations of all the 12000 trials were correctly identified. The experimental results are listed in Table 2.

Experimental results

Number of individuals (n) | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|

Number of loci ( m) | 30 | 60 | 100 | 130 | 160 | 200 | 230 | 260 | 300 | 330 | 360 | 400 | |

10 | 0.02 | 0.00 | 0.00 | 0.02 | 0.05 | 0.01 | 0.02 | 0.01 | 0.04 | 0.03 | 0.02 | 0.02 | |

30 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

60 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

100 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

130 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

(a) | 160 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |

200 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

230 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

260 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

300 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |

10 | 0.10 | 0.40 | 0.55 | 0.50 | 0.51 | 0.61 | 0.99 | 0.52 | 1.41 | 1.77 | 1.28 | 0.41 | |

30 | 0.11 | 0.50 | 0.90 | 0.48 | 0.66 | 0.55 | 2.28 | 1.22 | 1.06 | 2.94 | 1.16 | 2.71 | |

60 | 0.21 | 1.66 | 1.09 | 0.68 | 2.19 | 2.77 | 1.63 | 3.26 | 3.08 | 2.76 | 2.20 | 4.38 | |

100 | 0.49 | 1.03 | 1.79 | 1.63 | 1.93 | 2.66 | 3.21 | 3.42 | 3.63 | 4.65 | 3.42 | 3.73 | |

130 | 1.74 | 1.55 | 2.39 | 1.24 | 1.84 | 3.57 | 3.07 | 3.49 | 4.81 | 3.38 | 5.01 | 5.26 | |

(b) | 160 | 0.57 | 1.53 | 2.17 | 1.53 | 2.99 | 3.76 | 3.71 | 4.81 | 6.44 | 4.52 | 5.99 | 6.45 |

200 | 1.20 | 1.82 | 2.02 | 2.10 | 5.18 | 4.31 | 4.89 | 4.49 | 5.37 | 6.16 | 6.77 | 8.87 | |

230 | 0.70 | 2.59 | 2.34 | 2.71 | 5.52 | 3.79 | 5.28 | 6.19 | 6.63 | 7.89 | 7.87 | 9.77 | |

260 | 1.15 | 2.29 | 2.62 | 3.72 | 5.10 | 5.99 | 5.97 | 6.45 | 7.12 | 8.34 | 10.11 | 10.77 | |

300 | 1.67 | 2.31 | 3.33 | 4.27 | 5.27 | 6.49 | 6.35 | 7.11 | 8.70 | 9.12 | 11.40 | 13.22 | |

10 | 3.52 | 3.36 | 2.92 | 3.18 | 3.02 | 3.18 | 3.36 | 3.08 | 2.98 | 2.42 | 3.06 | 3.14 | |

30 | 2.96 | 3.00 | 2.98 | 3.14 | 3.18 | 2.90 | 2.96 | 3.04 | 3.18 | 3.02 | 3.22 | 2.94 | |

60 | 3.08 | 3.08 | 3.02 | 2.66 | 3.36 | 2.92 | 3.24 | 3.02 | 3.10 | 2.86 | 2.90 | 2.86 | |

100 | 3.00 | 2.90 | 2.78 | 3.36 | 3.00 | 3.28 | 3.38 | 2.72 | 3.30 | 2.66 | 2.98 | 2.74 | |

130 | 2.80 | 3.00 | 3.24 | 3.50 | 3.72 | 3.30 | 2.90 | 3.04 | 3.08 | 2.94 | 3.68 | 3.20 | |

(c) | 160 | 3.02 | 3.18 | 3.46 | 2.92 | 3.10 | 2.86 | 3.32 | 3.40 | 2.88 | 3.40 | 3.16 | 2.62 |

200 | 2.84 | 3.18 | 3.06 | 2.76 | 2.78 | 2.82 | 3.14 | 3.12 | 3.12 | 2.86 | 3.00 | 3.14 | |

230 | 3.24 | 3.22 | 2.90 | 2.74 | 3.32 | 2.86 | 2.94 | 3.34 | 3.08 | 2.70 | 2.84 | 3.42 | |

260 | 2.72 | 2.70 | 2.66 | 3.00 | 3.22 | 3.42 | 3.10 | 3.32 | 3.24 | 2.86 | 2.66 | 2.92 | |

300 | 3.24 | 3.02 | 2.70 | 2.76 | 2.92 | 2.74 | 2.94 | 2.98 | 2.62 | 3.02 | 3.34 | 3.44 |

Table 2(a) shows that unknown *p*-variables were correctly solved without assigning any free variable if the number of marker loci was not less than 30, which covers most practical cases in regular genotyping. Free variables were required only when the number of marker loci was far less than the number of individuals. In this experiment, free variables were used only when *m* = 10, and they were used at most five times out of 100 trials. The result is reasonable because the dimension of the solution space of a pedigree with a limited number of marker loci is probable less than the number of unknown *p*-variables.

Table 2(b) shows the cumulative execution time of 100 trials of each (*n, m*) combination. We received a fluctuation in execution time if *n* or *m* were less than 100. We conjecture that, because the algorithm executes very fast for small values of *n* or *m*, the cumulative execution time might be dramatically affected by the context switches within the operating system that ran many background services. Furthermore, we believe that when both *n* and *m* were larger than 100, the execution time of the algorithm became more significant than that of the context switches. From the table it is apparent that the execution time is linear for the larger *n* and *m* values.

Finally, Table 2(c) shows that mating loops existed evenly throughout all 12000 trials, with the number ranging from zero to six per pedigree, and the number did not affect the linearity of the execution time of our algorithm in relation to the input size of *n* and *m*.

### Issue of spanning tree and seed node selection

In the first step, *preprocessing*, a spanning tree *T*(*G*) is constructed on the pedigree graph *G*. As mentioned above, *T*(*G*) is constructed for the ease of cycle processing; it is merely an auxiliary data structure used to generate linear constraints of all cycles and paths between predetermined nodes in *G*. We do not impose any constraint on the construction of *T*(*G*) because predetermined nodes are defined by genotype data. Once the input pedigree is given, all the cycles and paths as well as their constraints are bound, no matter which spanning tree is constructed on the pedigree graph. Different spanning trees assign different edges as the non-tree edge in a cycle, and only affect the type of a constraint; a constraint may be a path constraint with respective to one spanning tree and a tree constraint with respect to another spanning tree. Since different spanning trees are used to generate the same set of constraints, without considering their type, the construction of the spanning tree can be arbitrary. In our implementation, *T*(*G*) was constructed by depth-first traversal.

In the second step, *constraint generation*, a seed node is arbitrarily selected from *T*(*G*) to generate tree constraints. To see why the seed node can be selected arbitrarily, assume that there are two possible seeds *n*_{
i
} and *n*_{
j
}. For any other predetermined node *n*_{
k
}, we have (*n*_{
j
}*, n*_{
k
}*, b*_{
jk
}) = (*n*_{
i
}*, n*_{
j
}*, b*_{
jk
}) + (*n*_{
i
}*, n*_{
k
}*, b*_{
ik
}) by Lemma 1, which means that a tree constraint seeded with one predetermined node is a linear combination of two tree constraints seeded with another predetermined node. Hence, tree constraints seeded with different predetermined nodes are mathematical equivalent; we can safely choose any predetermined node as seed. Similarily, the seed nodes within a constraint graph can also be selected arbitrarily based on the above argument.

### Consistency checking

*h*-value, that results in incompatible linear constraints. We may designate the following two checkpoints to detect inconsistencies within our linear system:

- 1.
*The generation of constraints*. The constraint of a path or a cycle may be computed more than one time across all locus graphs; all these computations should arrive at the same value. So each time we compute a constraint, we check if it is the same as the current value, if any. - 2.
*The initialization/update of G**. There may be loops in the constraint graph*G** and therefore it is possible that there are more than one path from the seed*n*_{ s }to a node*n*_{ i }. It turns out that*W*[*n*_{ i }] may be assigned more than once in the initialization or update procedures of*G**. By the definition of*W*-variables, however, all the assignments to*W*[*n*_{ i }] are actually associated with the same path from*n*_{ s }to*n*_{ i }on*T*(*G*) and therefore should be identical. So each time we compute a*W*-value, we check if it agrees with the current value, if any.

## Conclusions

In this study, we proposed and implemented an algorithm to solve the zero-recombinant haplotype configuration (ZRHC) problem for a general pedigree in *O*(*kmn* + *k*^{2}*m*) time. With the aid of free variables, our method provides a general solution to describe possible haplotype structures within a pedigree rather than a particular solution that only assigns a specific numerical setting to haplotypes. To the best of our knowledge, this algorithm is the first deterministic one to provide a general solution in linear time for pedigrees having small number of mating loops. Moreover, the algorithm can be easily modified to detect inconsistency among genotype data without loss of efficiency. Our experimental results confirm its linearity. In the future, we will try to extend the proposed algorithm to handle recombination and missing data in linear time for general pedigrees.

## Declarations

### Acknowledgements

This work was supported in part by the National Science Council, Taiwan under NSC99-2320-B-010-022-MY2.

This article has been published as part of *BMC Bioinformatics* Volume 13 Supplement 17, 2012: Eleventh International Conference on Bioinformatics (InCoB2012): Bioinformatics. The full contents of the supplement are available online at http://www.biomedcentral.com/bmcbioinformatics/supplements/13/S17.

## Authors’ Affiliations

## References

- Qian D, Beckmann L: Minimum-recombinant haplotyping in pedigrees. The American Journal of Human Genetics. 2002, 70 (6): 1434-1445. 10.1086/340610.View ArticlePubMedGoogle Scholar
- Albers CA, Heskes T, Kappen HJ: Haplotype inference in general pedigrees using the cluster variation method. Genetics. 2007, 177 (2): 1101-1116. 10.1534/genetics.107.074047.PubMed CentralView ArticlePubMedGoogle Scholar
- Chin FYL, Zhang Q, Shen H:
*k*-recombination haplotype inference in pedigrees. Proceedings of the International Conference on Computational Science (ICCS). 2005, Springer-Verlag, Berlin, 985-993.Google Scholar - Li J, Jiang T: Efficient rule-based haplotyping algorithms for pedigree data. Proceedings of the 7th Annual Conference on Research in Computational Molecular Biology (RECOMB). 2003, ACM, New York, 197-206.Google Scholar
- Li J, Jiang T: An exact solution for finding minimum recombinant haplotype configurations on pedigrees with missing data by integer linear programming. Proceedings of the 8th Annual Conference on Research in Computational Molecular Biology (RECOMB). 2004, ACM, New York, 20-29.Google Scholar
- Li J, Jiang T: Computing the minimum recombinant haplotype configuration from incomplete genotype data on a pedigree by integer linear programming. Journal of Computational Biology. 2005, 12 (6): 719-739. 10.1089/cmb.2005.12.719.View ArticlePubMedGoogle Scholar
- Sobel E, Lange K, O'Connell JR, Weeks DE: Haplotyping algorithms. Genetic Mapping and DNA Sequencing, Volume 81 of IMA Volumes in Mathematics and its Applications. Edited by: Speed T, Waterman MS. 1996, Springer-Verlag, 89-110.View ArticleGoogle Scholar
- Tapadar P, Ghosh S, Majumder PP: Haplotyping in pedigrees via a genetic algorithm. Human Heredity. 2000, 50: 43-56. 10.1159/000022890.View ArticlePubMedGoogle Scholar
- O'Connell JR: Zero-recombinant haplotyping: Applications to fine mapping using SNPs. Genetic Epidemiology. 2000, 19: 64-70. 10.1002/1098-2272(200007)19:1<64::AID-GEPI5>3.0.CO;2-E.View ArticleGoogle Scholar
- Chan MY, Chan WT, Chin FYL, Fung SPY, Kao MY: Linear-time haplotype inference on pedigrees without recombinations and mating loops. SIAM J Comput. 2009, 38 (6): 2179-2197. 10.1137/080680990.View ArticleGoogle Scholar
- Li X, Li J: Efficient haplotype inference from pedigrees with missing data using linear systems with disjoint-set data structure. 7th Annual International conference on Computational Systems Bioinformatics. 2008, 297-308.View ArticleGoogle Scholar
- Liu L, Jiang T: A linear-time algorithm for reconstructing zero-recombinant haplotype configuration on pedigrees without mating loops. Journal of Combinatorial Optimization. 2008, 19: 217-240.View ArticleGoogle Scholar
- Baruch E, Weller JI, Cohen-Zinder M, Ron M, Seroussi E: Efficient inference of haplotypes from genotypes on a large animal pedigree. Genetics. 2006, 172 (3): 1757-1765.PubMed CentralView ArticlePubMedGoogle Scholar
- Doan DD, Evans PA, Horton JD: A near-linear time algorithm for haplotype determination on general pedigrees. J Comput Biol. 2010, 17 (10): 1451-65. 10.1089/cmb.2009.0133. [http://www.biomedsearch.com/nih/near-linear-time-algorithm-haplotype/20937017.html]View ArticlePubMedGoogle Scholar
- Wang WB, Jiang T: Efficient inference of haplotypes from genotypes on a pedigree with mutations and missing alleles. CPM 2009, LNCS 5577. Edited by: Kucherov G, Ukkonen E. 2009, Springer-Verlag Berlin Heidelberg, 353-367.Google Scholar
- Xiao J, Liu L, Xia L, Jiang T: Efficient algorithms for reconstructing zero-recombinant haplotypes on a pedigree based on fast elimination of redundant linear equations. SIAM J Comput. 2009, 38: 2198-2219. 10.1137/070687591.View ArticleGoogle Scholar
- Zhang K, Sun F, Zhao H: HAPLORE: a program for haplotype reconstruction in general pedigrees without recombination. Bioinformatics. 2005, 21: 90-103. 10.1093/bioinformatics/bth388.View ArticlePubMedGoogle Scholar
- Gusfield D: Inference of haplotypes from samples of diploid populations: complexity and algorithms. Journal of Computational Biology. 2001, 8 (3): 305-323. 10.1089/10665270152530863.View ArticlePubMedGoogle Scholar
- Niu T, Qin ZS, Xu X, Liu JS: Bayesian haplotype inference for multiple linked single-nucleotide polymorphisms. The American Journal of Human Genetics. 2002, 70: 157-169. 10.1086/338446.View ArticlePubMedGoogle Scholar
- Stephens M, Smith NJ, Donnelly P: A new statistical method for haplotype reconstruction from population data. The American Journal of Human Genetics. 2001, 68 (4): 978-989. 10.1086/319501.View ArticlePubMedGoogle Scholar
- Wang S, Kidd KK, Zhao H: On the use of DNA pooling to estimate haplotype frequencies. Genetic Epidemiology. 2003, 24: 74-82. 10.1002/gepi.10195.View ArticlePubMedGoogle Scholar
- Yang Y, Zhang J, Hoh J, Matsuda F, Xu P, Lathrop M, Ott J: Efficiency of single-nucleotide polymorphism haplotype estimation from pooled DNA. Proceedings of the National Academy of Science of the United States of America. 2002, 100: 7225-7230.View ArticleGoogle Scholar
- Browning SR, Browning BL: Haplotype phasing: existing methods and new developments. Nature Reviews Genetics. 2011, 12: 703-714. [http://www.nature.com/nrg/journal/v12/n10/full/nrg3054.html]PubMed CentralView ArticlePubMedGoogle Scholar
- Thomas A, Cannings C: Simulating realistic zero loop pedigrees using a bipartite Prufer code and graphical modelling. Math Med Biol. 2004, 21 (4): 335-45. 10.1093/imammb/21.4.335. [http://www.biomedsearch.com/nih/Simulating-realistic-zero-loop-pedigrees/15567888.html]View ArticlePubMedGoogle Scholar

## Copyright

This article is published under license to BioMed Central Ltd. This is an open access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.