Volume 9 Supplement 6

## Symposium of Computations in Bioinformatics and Bioscience (SCBB07)

- Research
- Open Access

# MLIP: using multiple processors to compute the posterior probability of linkage

- Manika Govil
^{1}Email author, - Alberto M Segre
^{2}and - Veronica J Vieland
^{3}

**9 (Suppl 6)**:S2

https://doi.org/10.1186/1471-2105-9-S6-S2

© Govil et al; licensee BioMed Central Ltd. 2008

**Published:**28 May 2008

## Abstract

### Background

Localization of complex traits by genetic linkage analysis may involve exploration of a vast multidimensional parameter space. The posterior probability of linkage (PPL), a class of statistics for complex trait genetic mapping in humans, is designed to model the trait model complexity represented by the multidimensional parameter space in a mathematically rigorous fashion. However, the method requires the evaluation of integrals with no functional form, making it difficult to compute, and thus further test, develop and apply. This paper describes MLIP, a multiprocessor two-point genetic linkage analysis system that supports statistical calculations, such as the PPL, based on the full parameter space implicit in the linkage likelihood.

### Results

The fundamental question we address here is whether the use of additional processors effectively reduces total computation time for a PPL calculation. We use a variety of data – both simulated and real – to explore the question "how close can we get?" to linear speedup. Empirical results of our study show that MLIP does significantly speed up two-point log-likelihood ratio calculations over a grid space of model parameters.

### Conclusion

Observed performance of the program is dependent on characteristics of the data including granularity of the parameter grid space being explored and pedigree size and structure. While work continues to further optimize performance, the current version of the program can already be used to efficiently compute the PPL. Thanks to MLIP, full multidimensional genome scans are now routinely being completed at our centers with runtimes on the order of days, not months or years.

## Keywords

- Load Balance
- Linear Speedup
- Recombination Fraction
- Intrinsic Computation
- Root Processor

## Background

From at least as far back as 1866, when Gregor Mendel published his findings on the laws of inheritance based on experiments with pea plants, statistics has been used as an important tool for genetic studies of inherited traits. With advances in technology and the development of increasingly complex models for analysis, the use of computer science has become integral for all such statistical genetic studies.

One research area of interest for geneticists is locating on the genome the gene(s) responsible for inherited traits. This localization is facilitated by linkage analysis, a statistical genetic method. The method relies on violations of Mendel's second law of inheritance, which states that genes assort independently, to estimate the proximity of trait genes to known genomic locations (genetic markers). The model-based linkage statistic is the LOD score, defined as the log_{10} ratio of the likelihood of the observed data, divided by the likelihood assuming "no linkage." This statistic utilizes genetic map, pedigree, and trait model information (*e.g.*, the population frequency of the trait, and the *penetrance* or probability that an individual with a given genetic combination at the trait locus manifests the trait) to obtain an estimate of the recombination fraction *θ*, the traditional measure of genetic distance between two genomic locations.

A typical linkage analysis therefore involves computing likelihoods in several parameters in order to summarize the information regarding *θ*. However, complicating factors exist. While sex-averaged genetic maps are normally used in analyses, the true male-female maps are of different lengths. This use of sex-averaged maps results in map misspecification. Heterogeneity among pedigrees from different populations is another complicating factor. Finally, the trait may be complex, possessing a genetic component but not a simple mode of inheritance. For such traits, linkage analysis may involve exploration of a vast multidimensional parameter space.

The posterior probability of linkage, or PPL, [1, 2] is a class of linkage statistics designed to model both sex-specific maps and the trait model complexity represented by the multidimensional parameter space in a mathematically rigorous fashion. It also accommodates both inter- and intra-population heterogeneity by using Bayesian sequential updating over data subsets. However, the method requires the evaluation of integrals with no functional form, making it difficult to compute, and thus further test, develop and apply.

This paper describes MLIP (*Multiprocessor LInkage analysis Program*), a new, dual-language system that calculates, in parallel, two-point LOD scores by pedigree and marker over a user-specified range of genetic parameters and male and female recombination fractions. MLIP is designed to facilitate genetic linkage analysis (gene mapping) by allowing the coverage of a complex, multidimensional parameter space using partitioning and parallelization of the computation. Motivation for the development of MLIP derives from the utility of representing the underlying linkage likelihood explicitly as a function of all implicit parameters to allow computation of the PPL.

MLIP utilizes NICE, the *Network Infrastructure for Combinatorial Exploration* [3], a network computing infrastructure for dynamic parallelization across a grid of processors. While parallelization has been considered previously in connection with linkage analysis (*e.g.*, see [4–10]), none of these approaches have dealt with computation over the trait parameter space, the focus of the present work.

## Methods

The simplest characterization of MLIP is as a two-layer model: an *inner layer* that is used to compute each individual LOD score, and an *outer layer* that oversees the systematic exploration of the multidimensional parameter space by dividing it into chunks, managing the distribution of these chunks to other processors, collecting the results, and subsequently writing them to disk.

### Inner layer: computing the LOD scores

*θ*). In other words, it is the probability that

*θ*< 1/2 given the data. For marker data

*M*, and trait data

*T*, the two-point PPL can be expressed in terms of LOD scores as [1, 11]:

In these equations, *L* indicates linkage, g is a vector of trait parameters, *θ* is the recombination fraction, *α* is the admixture parameter, and *f*(g), *f*(*θ*), *f*(*α*) are prior distributions for g, *θ*, and *α* respectively. BR(*θ*), a function of *θ*, is the direct analogue of the usual likelihood ratio (LR). Since it is also proportional to the posterior density of *θ*, the BR is simply multiplied across the data (sub)sets to sequentially update the PPL over multiple sets of data and the PPL is recomputed using Eq. 2 [12]. Nuisance parameters are integrated out of the BR independently for each set of data, thereby allowing these parameters to vary independently across data sets, while evidence regarding *θ* is accumulated across data sets. Since the integrand for computing the PPL involves several integrals and has no analytical functional form, it is approximated by averaging heterogeneity LOD scores (HLODs) over a discretized parameter space [13–15].

The inner layer of MLIP allowing computation of the LOD scores necessary for the PPL is LIPED [16], Jurg Ott's FORTRAN implementation of the Elston-Stewart algorithm [17]. LIPED has been selected as the inner layer of MLIP for several reasons. Since the program is an implementation of the Elston-Stewart algorithm, it is capable of handling the medium to large pedigrees regularly encountered in our own clinical collaborations.

Not only is LIPED both trusted and well tested, with the source code freely available, but it also has additional important advantages over some of the other existing Elston-Stewart implementations. Computing the PPL requires the flexibility to include a variety of genetic parameters in the model. LIPED supports sex-specific recombination fractions; accepts haplotype frequencies in a manner that allows modeling linkage with disequilibrium correctly; handles quantitative traits; models delayed onset; and supports *loops*, or complex pedigree structures where more than one path may exist between two individuals.

While the code is not new, when compared to more recent Elston-Stewart implementations (such as FASTLINK [18]), optimized to reduce the cost of a single LOD score calculation, somewhat surprisingly, the performance of the original LIPED code is still quite competitive overall. For some pedigree structures, it even provides better performance than more recent implementations. When tightly integrated into MLIP and with just a few small improvements, our modified LIPED core's performance is quite respectable (especially when compared to, e.g., using remote procedure calls to invoke multiple copies of FASTLINK over a network).

Finally, although LIPED is written in FORTRAN, the code is relatively compact and well documented. Since the modifications required to the original LIPED code did not involve extensive changes to its algorithmic core, our resulting calculations should inspire the same faith and confidence as those produced by the original LIPED code.

### Outer layer: partitioning over a cluster

Wrapped around LIPED is a new outer layer, coded in ANSI C. This layer is responsible for reading in the problem specification (pedigrees, markers, loop breakers, and the parameter grid) and checking it for errors; performing simple data transformations in the interests of efficiency (*e.g.*, *allele downcoding*, where the total number of alleles at each marker is adjusted down to the observed number); and breaking the space into appropriate size chunks to assign chunks to itself and other processors. It is also responsible for invoking LIPED and collecting computed LOD scores and storing them on disk. Finally, the layer ensures that the entire space is exhausted while taking appropriate measures to allow effective restarting of a previously interrupted computation via checkpointing.

*e.g.*, request that new copies of the application be spawned on the same or other machines. It also contains functions to support communication between these multiple copies of the application once they are established. Note that the library does not actually contain code specific to any application, but rather only the handful of functions that are needed to efficiently parallelize appropriately designed serial applications.

Once the NICE infrastructure has spawned the appropriate configuration of processes over the nodes in the cluster, parallelization by partitioning involves having an idle slave processor ask its master for a chunk of work and then returning the results once the calculation is completed. Since a master processor may have multiple slaves, it should be able to partition independent chunks of its own assigned work among them. The model extends recursively, with each slave potentially having slaves of its own, subdividing its own chunk(s) into still smaller ones.

There are several complicating factors. First, this is a mixed-language system (LIPED is coded in FORTRAN), which requires special handling [19]. Second, the outer layer is responsible for managing the distribution of chunks to other processors. This requires care to keep all processors working at maximum capacity. A good partitioning scheme performs *load balancing* (ensures all available processors are kept busy) and is also *fault tolerant* (robust to processor or network failure). Good load balancing in heterogeneous computing environments presents a challenge. Differences in processor speed or memory capacity, and thus intrinsic computation speeds, makes it difficult to distinguish an unduly slow slave from one that has failed. Furthermore, for hierarchically-organized processors, some processors will appear much faster than others by virtue of the processor(s) available beneath them. Finally, in the case of MLIP, we have no *a priori* knowledge of the amount of CPU time required to perform a unit of work. This is due to the fact that not all LOD scores are created equal: differences in markers, pedigree size and structure, and pattern of unknown genetic marker and/or trait data, all affect the cost of the calculation.

Since load balancing and fault tolerance are intertwined, the load balancing scheme should also handle lost processors in a systematic fashion, "recovering" and reassigning inchoate chunks that had been assigned to slower or unresponsive processors. In this manner, faster processors cover more and more of a slower processor's assigned territory. If a processor has failed, the faster processors will eventually complete its work. If a processor is truly slow and completes its work before the faster processors report back, the redundantly assigned processors can be aborted without prejudice. This strategy implies that some LOD scores may be computed more than once to keep all CPUs busy and preserve fault tolerance. The key issue here is to tune the partitioning criteria such that all chunks are finished at approximately the same time and little redundant calculation actually occurs.

Finally, since the outer layer is ultimately responsible for collecting the LOD scores and efficiently streaming them to disk, it must keep up with the high rate with which results are generated by multiple processors. For MLIP, the protocol invoked when a slave completes a portion of its work is the most expensive and the number of LOD scores returned to the root can be quite large. For example, for 50 pedigrees, a typical genome-wide analysis with 400 markers over the regular space for the sex-specific PPL [15] entails the calculation, communication, and storage of 2.7 × 10^{10} LOD scores, roughly 100 GB of output. This presents a special challenge for distributed computing. Typically, distributed applications will require that the input data sets, which can be quite large, be broadcast to individual processing elements at initialization, and that the subsequent results, which are typically small, be collected over the course of the calculation. Here, the input data sets, while not insignificant, are trivially small in comparison to the size of the results, which must be transmitted over the network for storage on disk, so that, *e.g.*, the PPL can be computed and recomputed with arbitrary priors.

To minimize communication costs, each slave node, regardless of its relative position in the hierarchy, communicates its results directly back to the root node, circumventing its own master.

## Results and discussion

The fundamental question addressed here is whether additional processors effectively reduce total computation time. While the use of N processors should, in theory, allow completion of the same calculation N times faster, few, if any, parallel computing efforts attain *linear speedup* in practice. This is because some of the work does not parallelize. For MLIP, all disk-writing costs are incurred solely by the root processor, while network communications are a necessary expense of all parallel systems.

*grid size*) are selected for each set allowing a single processor trial to take approximately the same amount of time across sets. To examine the behavior of the system as the number of processors increases, each set is tested with n = 1, 2, 4, 8, 16, and 32 processors arranged in a uniform NICE hierarchy, where each processor has at most three child processors. The grid size is increased proportionally as n increases. Table 1 gives the minimum (for 1 processor) and maximum (for 32 processors) grid size for each test set.

Grid size variation

Processors | Set A | Set B | Set C | Set D |
---|---|---|---|---|

1 CPU | 33 × 10 | 16 × 10 | 10 × 10 | 4096 |

32 CPUs | 52 × 10 | 26 × 10 | 34 × 10 | 13 × 10 |

### Speedup and scalability

*speedup*obtained as the number of processors increases, where

*speedup*, S

_{n}, is defined here as the ratio of the LODs/second on n processors to the LODs/second on a single processor: thus S

_{n}= n represents linear speedup.

Clearly, as seen from the plot, linear speedup is not being achieved for each of the test sets. What is interesting here is that the observed performance appears to be clustering by set, with B, C performing better than A, D.

To understand the reason behind this observed performance, we need to take a closer look at computation, disk-writing, and network costs of the root processor. Of these three, only the first represents work that can be distributed to other processors. Furthermore, while we expect that disk activity should remain relatively constant (since roughly the same number of LOD scores are always being written to disk, modulo any redundant calculations undertaken to ensure fault tolerance), we might also expect to see network activity increase, given that the root processor must now receive relatively more results from other machines.

Set A, on the other hand, is the least computationally-intensive of the four sets. However, the grid space for this set is at least twice as large as the space for any other set. As the number of processors grows, the amount of calculation performed by the root processor diminishes to the extent that with n = 32 processors, almost all of the root processor's workload comprises disk and network activities. Test sets B and C represent the most favorable setup here with fairly complex data, and a sufficiently large grid space for distribution.

### Behavior over time

*load*or the total number of log-likelihood scores computed as a percentage of the original grid size, versus the elapsed time for data set C, normalized to account for grid size differences.

The single-processor curve shows steady progress through the test, with each regularly-spaced data point corresponding to completion of one of the 32 identical pedigrees in data set C. Since there is only one processor, there is no additional overhead to complicate matters.

The two-processor system also produces a regular, smooth, line, while working its way through its load at about twice the speed. With additional processors, the slope of the lines in the plot continues to increase, although the relative margin of improvement declines. Furthermore, from a qualitative perspective, three striking changes can be seen in the lines generated. First, the spacing of the data points increases and is much less regular than for n = 1 and n = 2. Second, the slope of the line decreases towards the end of the calculation, forming a pronounced "knee" near the end of the trial. Finally, each line generally extends beyond 100% load.

These visual cues tell an interesting story: the increased spacing implies that the root processor is spending relatively more of its time supervising the collection of data from slaves as opposed to making progress on its own calculations. The fact that the spacing is irregular and tends to decrease towards the end of the calculation is because the chunks being handed out to idle slave processors are getting smaller as the remaining workload decreases, leaving less work for the root to complete a pedigree. Moreover, it becomes increasingly difficult to find work for idle processors as the size of the remaining calculation decreases, so some processors are simply told to remain idle. Since the idle slaves are not producing LOD scores, the overall rate at which the load completes is reduced, resulting in a lower slope. Finally, as the number of processors increases, proper load balancing also becomes tricky, leading to an increase in the number of redundant LOD scores computed notwithstanding the fact that the homogeneity of this data (replicated pedigrees) represents a best-case scenario for load balancing.

### Reducing network and disk overhead

The time devoted to network communication and disk access represents a significant obstacle to better performance. Two design changes are evaluated here to help sidestep these obstacles. In the original LIPED implementation, LOD scores are calculated as double precision floating point numbers. Since only 4 to 5 decimal digits of precision are needed for computing the PPL, the cost of disk storage can be halved and the data rate on the network doubled, simply by casting double precision LOD scores to 32-bit floating point.

A second improvement comes from the manner in which these values are written to the disk. The file on the disk is as an ordered repository of LOD scores, indexed by pedigree and parameter space values. Since each processor generally produces LOD scores in sequential order, collections of LOD scores can be efficiently streamed to the disk at the same time, thereby amortizing disk access time and producing higher throughput.

### Improving performance via better load balancing

One of the hardest problems for any distributed system is how to best keep all available processors equally busy. The granularity issue briefly mentioned previously is one incarnation of this more general problem that arises when the space remaining is not easily apportioned to all available processors. For some datasets (e.g., dataset D) the problem is particularly acute, but it arises to some degree with any dataset, albeit perhaps only at nodes that are nested deeply within the NICE hierarchy. A related problem occurs when the root processor is unable to keep up with the results being generated by all the slave processors in the hierarchy. In this situation, the slaves queue up, lying idle while they wait for service from the root processor. The problem is compounded because any idle slaves wanting additional chunks must also wait in line for service. Finally, inefficiencies arise when the allocation of processors within the hierarchy of processors is suboptimal. Unfortunately, what constitutes the optimal allocation depends on the specifics of the problem being solved, and is not always easy to predict when the data are not as well behaved as our simulated data sets.

Speedups by branching factor (bf)

bf | Set A | Set B | Set C | Set D |
---|---|---|---|---|

3 | 4.62 | 5.07 | 5.60 | 3.87 |

5 | 4.52 | 7.39 | 4.88 | 2.74 |

9 | 4.19 | 8.76 | 3.27 | 2.74 |

17 | 3.42 | 5.03 | 1.08 | 2.05 |

The message here is that load balancing is difficult: no single strategy is likely to be optimal for all possible datasets. Even with the simple, uniform, datasets used here (replicated pedigrees, etc), effective load balancing is likely to rely on a set of heuristics or a collection of adaptive mechanisms that can help fine tune performance while the calculation is underway.

### Performance on real data

The most striking observation is that Figure 8 is decidedly less smooth than Figure 6. This fact is to be expected, given that the computation time of an individual pedigree is likely to vary significantly with real data. In particular, one pedigree encountered about 25% of the way through the serial run required about 10% of the overall runtime (this is the plateau in the single processor curve, the central data point on the plateau corresponds to a system checkpoint, not completion of a pedigree). The effect is less noticeable as more processors are added, since the other processors continue to generate LOD scores while the one exceptionally expensive pedigree is being handled.

As with Figure 6, the increased spacing between points with the addition of more processors reflects a change in root processor workload from computation to disk I/O. However, this change is particularly marked here for the 32 processor case. In Figure 8, it can be seen that with 32 processors, the root processor completes the space for its first pedigree only when over 90% of the total LOD scores have already been computed. For both Figures 6 and 8, spacing between successive data points tends to decrease as the trial completes, indicating smaller chunk sizes. Percentage of effort also increases beyond 100% as processors perform redundant calculations in an attempt to ensure fault tolerance. For the real data, however, Figure 8 reveals that the wildly differing costs of each pedigree contribute to broad fluctuations in final percentage of effort.

## Conclusion

This paper described MLIP, a new multiprocessor two-point genetic linkage analysis system that enables statistical calculations based on the full multidimensional parameter space implicit in the linkage likelihood. Empirical results on a broad variety of data have also been provided to support the claim that MLIP does significantly speed up two-point LOD score calculations over the grid space of model parameters necessary for computing the PPL. In keeping with the requirements for the statistic, MLIP not only provides needed flexibility in model parameter specification, but it also stores individual LOD scores, providing users with the ability to create data subsets and change priors during post processing. Obtaining the output in this form provides some additional benefits as well. The likelihood surfaces tend to be irregular with extensive interaction among the parameters. The output produced by MLIP can also be used by visualization software to allow the user to interactively explore the likelihood surface [20–22].

From the infeasible to the feasible

Large Ped. (500; No Unknowns) | Nuclear Ped. (50; Some Unknowns) | Large Ped. (50; Some Unknowns) | |
---|---|---|---|

LIPED Base | 2 years | 32 years | 59 years |

16 CPU MLIP | 9 hours | 19 days | 232 days |

The immediate task is to continue making incremental improvements in the load balancing strategy. The current partitioning strategy is not sensitive to predictable differences in expected computation time required for different portions of the grid space. A more fine-grained partitioning strategy would at the very least postpone the granularity problems described earlier. Adaptive partitioning strategies that take cues from observed run times in the course of a calculation are also possible.

While the distributed computing approach adopted here is more coarse-grained, it may be useful to also consider parallelization at the algorithmic level. In such a situation, a hybrid distributed computing infrastructure-allowing both distributed and shared memory-may be a possibility. Use of a grid computing type of infrastructure may perhaps facilitate better time results as opposed to a hierarchy of processors.

Another area of interest is the definition of the grid space itself. Currently, by use of a simple grid specification language, the grid space is defined a priori by the user when the MLIP job is started. Since much of the space might be expected to be relatively "flat," standard adaptive quadrature techniques from numerical integration might be used to allow MLIP to effectively "design its own grid" over the course of an evolving calculation.

Finally, it is a fact that the current core is not fully optimized with respect to the actual likelihood calculation. Well-established differences exist among linkage analysis algorithms. Both these facts suggest that the use of a new computational core, different from LIPED, could significantly extend the capabilities of MLIP. In particular, LIPED is restricted to two-point analyses. Based on what we have learned with MLIP, we are working on constructing a multipoint parallel linkage analysis system [23] based on a reimplementation of the VITESSE [24, 25] linkage analysis engine.

As work continues to optimize the performance of the system, the "brute force" grid search method to approximate the PPL as implemented in MLIP, will continue to serve as a benchmark against which future approximations may be judged. Further development and evaluation of fast alternative numerical integration methods is necessarily predicated upon the ability of this program to carry out the calculation based on a full grid-enumeration in an efficient manner.

## Declarations

### Acknowledgements

The authors would like to thank Jurg Ott for providing LIPED. We also wish to acknowledge Mark Logue for his many useful suggestions during the design of MLIP, Martin Milder for developing the disk management code libraries used in MLIP, Rhinda Goedken for her patient assistance with debugging, and the other faculty, staff and students of the (former) University of Iowa Center for Statistical Genetics Research for their contributions. Support for this research was provided in part by the National Science Foundation through grant ITR/ACI0218491 (AMS) and in part by the National Institutes of Health through grants R01/MH76433 and R03/DE017167 (VJV). A shorter version of this paper appeared in the IMSCCS07 proceedings published by IEEE as "MLIP: A Multiprocessor Linkage Analysis System."

This article has been published as part of *BMC Bioinformatics* Volume 9 Supplement 6, 2008: Symposium of Computations in Bioinformatics and Bioscience (SCBB07). The full contents of the supplement are available online at http://www.biomedcentral.com/1471-2105/9?issue=S6.

## Authors’ Affiliations

## References

- Vieland VJ:
**Bayesian linkage analysis, or: how I learned to stop worrying and love the posterior probability of linkage.***Am J Hum Genet*1998,**63:**947–954. 10.1086/302076PubMed CentralView ArticlePubMedGoogle Scholar - Vieland VJ:
**Thermometers: something for statistical geneticists to think about.***Hum Hered*2006,**61:**144–156. 10.1159/000093775View ArticlePubMedGoogle Scholar - Segre AM, Foreman S, Resta S, Wildenberg A:
**Nagging: a scalable, fault-tolerant, distributed search paradigm.***Artif Intell*2002,**140:**71–106. 10.1016/S0004-3702(02)00228-XView ArticleGoogle Scholar - Miller PL, Nadkarni PM, Gelernter JE, Carriero N, Pakstis AJ, Kidd KK:
**Parallelizing genetic linkage analysis: a case study for applying parallel computation in molecular biology.***Comput Biomed Res*1991,**24:**234–248. 10.1016/0010-4809(91)90046-YView ArticlePubMedGoogle Scholar - Dwarkadas S, Schäffer AA, Cottingham RW Jr, Cox AL, Keleher P, Zwaenepoel W:
**Parallelization of general linkage analysis problems.***Hum Hered*1994,**44:**127–141.View ArticlePubMedGoogle Scholar - Gupta SK, Schäffer AA, Cox AL, Dwarkadas S, Zwaenepoel W:
**Integrating parallelization strategies for linkage analysis.***Comput Biomed Res*1995,**28:**116–139. 10.1006/cbmr.1995.1009View ArticlePubMedGoogle Scholar - Matise TC, Schroeder MD, Chiarulli DM, Weeks DE:
**Parallel computation of genetic likelihoods using CRI-MAP, PVM, and a network of distributed workstations.***Hum Hered*1995,**45:**103–116.View ArticlePubMedGoogle Scholar - Rai A, Lopez-Benitez N, Hargis JD, Poduslo SE:
**On the parallelization of Linkmap from the LINKAGE/FASTLINK package.***Comput Biomed Res*2000,**33:**350–364. 10.1006/cbmr.2000.1547View ArticlePubMedGoogle Scholar - Kothari K, Lopez-Benitez N, Poduslo SE:
**High-performance implementation and analysis of the Linkmap program.***J Biomed Inform*2001,**34:**406–414. 10.1006/jbin.2002.1031View ArticlePubMedGoogle Scholar - Conant GC, Plimpton SJ, Old W, Wagner A, Fain PR, Pacheco TR, Heffelfinger G:
**Parallel genehunter: implementation of a linkage analysis package for distributed-memory architectures.***J Parallel Distrib Comput*2003,**63:**674–682. 10.1016/S0743-7315(03)00080-7View ArticleGoogle Scholar - Vieland VJ, Logue MW:
**HLODs, trait models, and ascertainment: implications of admixture for parameter estimation and linkage detection.***Hum Hered*2002,**53:**23–35. 10.1159/000048601View ArticlePubMedGoogle Scholar - Vieland VJ, Wang K, Huang J:
**Power to detect linkage based on multiple sets of data in the presence of locus heterogeneity: comparative evaluation of model-based linkage methods for affected sib pair data.***Hum Hered*2001,**51:**199–208. 10.1159/000053343View ArticlePubMedGoogle Scholar - Bartlett CW, Flax JF, Logue MW, Vieland VJ, Bassett AS, Tallal P, Brzustowicz LM:
**A major susceptibility locus for specific language impairment is located on 13q21.***Am J Hum Genet*2002,**71:**45–55. 10.1086/341095PubMed CentralView ArticlePubMedGoogle Scholar - Logue MW, Vieland VJ, Goedken RJ, Crowe RR:
**Bayesian analysis of a previously published genome screen for panic disorder reveals new and compelling evidence for linkage to chromosome 7.***Am J Med Genet B Neuropsychiatr Genet*2003,**121:**95–99. 10.1002/ajmg.b.20072View ArticleGoogle Scholar - Logue MW, Vieland VJ:
**The incorporation of prior genomic information does not necessarily improve the performance of Bayesian linkage methods: An example involving sex-specific recombination and the two-point PPL.***Hum Hered*2005,**60:**196–205. 10.1159/000090543View ArticlePubMedGoogle Scholar - Ott J:
**Estimation of the recombination fraction in human pedigrees: efficient computation of the likelihood for human linkage studies.***Am J Hum Genet*1974,**26:**588–597.PubMed CentralPubMedGoogle Scholar - Elston RC, Stewart J:
**A general model for the genetic analysis of pedigree data.***Hum Hered*1971,**21:**523–542.View ArticlePubMedGoogle Scholar - Cottingham RW Jr, Idury RM, Schäffer AA:
**Faster sequential genetic linkage computations.***Am J Hum Genet*1993,**53:**252–263.PubMed CentralPubMedGoogle Scholar - Burow BD:
**Mixed language programming.***Chep '95: Proceedings of the Workshop on Computing in High Energy Physics, Rio de Janeiro, Brazil*1995. [http://www.hep.net/chep95]Google Scholar - Logue MW, Park J, Ni J, Cremer J, Segre AM, Knosp B, Beck B, Vieland VJ:
**Interactive visualization tools for genetic data [abstract 2957].***54th Annu Meeting Am Soc Hum Genet*2004. [http://www.ashg.org/meetings/2004/]Google Scholar - Park JW, Logue MW, Ni J, Cremer J, Segre AM, Vieland VJ:
**Scientific visualization of multdimensional data: genetic likelihood visualization.**In*Current Trends in High Performance Computing and Its Applications: Proceedings of the International Conference on High Performance Computing and Applications*. Edited by: Zhang W, Chen Z, Glowinski R, Tong W. Berlin: Springer-Verlag; 2005:157–161.Google Scholar - Park JW, Cremer JF, Segre AM, Logue MW, Vieland VJ:
**Visual exploration of genetic likelihood space.***Proc ACM Symp on Appl Comput*2006, 1335–1340.Google Scholar - Huang Y, Segre AM, O'Connell JR, Wang H, Vieland VJ:
**KELVIN: a 2nd generation distributed multiprocessor linkage and linkage disequilibrium analysis program [abstract 1556].***56th Annu Meeting Am Soc Hum Genet*2006. [http://www.ashg.org/genetics/ashg06s/index.shtml]Google Scholar - O'Connell JR:
**Rapid multipoint linkage analysis via inheritance vectors in the Elston-Stewart algorithm.***Hum Hered*2001,**51:**226–240. 10.1159/000053346View ArticlePubMedGoogle Scholar - O'Connell JR, Weeks DE:
**The VITESSE algorithm for rapid exact multilocus linkage analysis via genotype set-recoding and fuzzy inheritance.***Nat Genet*1995,**11:**402–408. 10.1038/ng1295-402View 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.