Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Project Status: Inactive – The project has reached a stable, usable state but is no longer being actively developed; support/maintenance will be provided as time allows.

Regular installation

Refers to the detailed instructions on the dedicated page


  • Download a release as zip or tgz file
  • Decompress the archive
  • Install both R and the 4 mandatory packages.
  • Install the pythin package pysam
  • Install mapDamage, once in the archive folder, for a user: python3 install --user


  • From version 2.2.1 the main branch is requiring python3 as python2 is not supported from 2020-01-01.

  • Users with versions dating prior to June 12 2013 please update. A nasty bug that caused the statistical part of mapDamage to use half of the data for estimation of the damage parameters, sorry for the inconvenience.


Complete documentation, instructions, examples, screenshots and FAQ are available at this address.

mapDamage2 is a computational framework written in Python3 and R, which tracks and quantifies DNA damage patterns among ancient DNA sequencing reads generated by Next-Generation Sequencing platforms.

mapDamage was developed at the Centre for GeoGenetics by the Orlando Group .


If you use this program, please cite the following publication: Jónsson H, Ginolhac A, Schubert M, Johnson P, Orlando L. mapDamage2.0: fast approximate Bayesian estimates of ancient DNA damage parameters. Bioinformatics 23rd April 2013. doi: 10.1093/bioinformatics/btt193

The original mapDamage1 was published in the following article: Ginolhac A, Rasmussen M, Gilbert MT, Willerslev E, Orlando L. mapDamage: testing for damage patterns in ancient DNA sequences. Bioinformatics 2011 27(15):2153-5


Please report bugs and suggest possible improvements on GitHub: