Skip to main content

MethylPurify_v2

This script is used for predicting subclone purity.

Get Dependent data

Get the version of genome fasta that you mapped your fastqs, we support hg18 and hg19 genome fasta now, take hg19 as an example

## use built-in script
cd methylpurify/db
bash genome.sh hg19

Get Dependent software

  • samtools, version 0.2.0

  • numpy, version 1.8.2

  • pyfasta, version 0.5.2

Easy to start

Input: BAM file, this should be mapped with BSMap with -R option * BSMap

Currently, we only support hg19 and hg18 genome index mapped BAM file.

If your fastq mapping is done with hg19 index, use following command:

MethylPurify -f input.bam -b 300 -c 10 -s 50 -i methylpurify/db/CGI_hg19_slop1000.bed -g /path/to/hg19.fa --cnv

The results would be placed into input folder: alpha1.pred, MethylProfile.bed

Options

  • -f: input BAM file

  • -c: coverage level

  • -b: genome bin size

  • -s: sampling times

  • -g: species genome fasta file

  • -i: CG island specified, can use methylpurify/db/CGI_hg19_slop1000.bed for hg19, methylpurify/db/CGI_hg18_slop1000.bed for hg18

  • –cnv: use cnv data or not, only available for hg19, for other assembly, do not use this

Metadata

Release files for MethylPurify 2.0-20141116

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for MethylPurify 2.0-20141116
File Size Uploaded Provenance
MethylPurify-2.0-20141116.tar.gz 582.5 kB Without provenance Details

Release files / MethylPurify-2.0-20141116.tar.gz

Download URL MethylPurify-2.0-20141116.tar.gz
Size 582.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b1d597b1b570cbca846489e7b187374a7ef07fcfb7fb881d24b5454ef50f2391
BLAKE2b-256 checksum
How to use checksums
d2baeadb6f01b39aa51d250790650f11436eb86af9ca479b3cb39f0204f6f635
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for MethylPurify 2.0-20141116

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page