# Merge SV VCFs
This set of routines merges SV VCF files by calls, labeling calls by the callers that made them in an INFO field, Callers=. Most of the work goes into normalizing SV calls, which are treated as paired of breakpoints that are equal if they fall within a user-specified window.
1 maintainer
Metadata
1 maintainer
Release files for mergesvvcf 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mergesvvcf-1.0.3.tar.gz | 219.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mergesvvcf-1.0.3-cp38-cp38-macosx_10_9_x86_64.whl | CPython 3.8 | CPython 3.8 | macOS 10.9+ x86-64 | Details |
Total release size: 407.9 kB
Release files / mergesvvcf-1.0.3.tar.gz
| Download URL | mergesvvcf-1.0.3.tar.gz |
|---|---|
| Size | 219.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae0d8e187abb0695106f905f6855751e6e24188eb4fdfaf6ca7890ddf0b51e28
|
|
BLAKE2b-256 checksum How to use checksums |
a62b287d29086bc596a04212bffe5131a467e3ca568cc70701369ff7aca3971d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.0
|
Release files / mergesvvcf-1.0.3-cp38-cp38-macosx_10_9_x86_64.whl
| Download URL | mergesvvcf-1.0.3-cp38-cp38-macosx_10_9_x86_64.whl |
|---|---|
| Size | 188.8 kB |
| Tags | CPython 3.8 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
425daec1358ca9037ff561393c0cf55502c2fbbe88376b913cee12ba3edbd1c3
|
|
BLAKE2b-256 checksum How to use checksums |
5618afa188fb7b7c779f376ca26fa28b0b91ae874c2eb781589094a8ca214203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.0
|
Security for mergesvvcf 1.0.3
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.
