MapDamage
mapDamage: tracking and quantifying damage patterns in ancient DNA sequences
Install / Use
/learn @ginolhac/MapDamageREADME
mapDamage
Installation
mapDamage can be installed via pip:
pip install mapdamage
R and several packages are post mortem damage plotting, modeling, and rescaling. Refers to the detailed instructions on the dedicated page.
Introduction
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.
Citation
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
http://bioinformatics.oxfordjournals.org/content/27/15/2153
Contact
Please report bugs and suggest possible improvements on GitHub: https://github.com/ginolhac/mapDamage/issues/new
Related Skills
node-connect
353.3kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
111.7kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
111.7kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
353.3kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
