nebgbhist
Tools for building annotation histories from multiple Genbank files.
Example
$ mkdir gbhist $ neb-rev-fetch -d gbhist NC_008512 $ neb-gbhist -d gbhist | neb-diff-apply NC_008512.git $ git --git-dir=NC_008512.git gc --aggressive $ neb-validate-history -p NC_008512.git -g gbhist/2009-04-29-04-04.gbk
Playing with files
If you clone the pack repository after building you can poke around at the contents on the file system. For larger genomes with lots of edits this may run afoul of directory entry limits until I rewrite the object storage. For the Carsonella (NC_008512) example I use there isn’t an issue.
$ git clone NC_008512.git $ cd NC_008512 $ ls -1 accession dblink keywords objects/ seq/ version comment definition locus ref/ source
Files in the root directory represent keywords defined in the Genbank file. The ref and seq subdirectories contain information about references and the sequence hashes. The objects directory lists the features in the history. The files objects/known and objects/alive are dictionaries of hashes that point toward the current version of a feature at a given location. Active features are anything that is not deleted or replaced with a new version.
I recommend that you work with nebpack.Pack objects if you want to actually do anything with the objects.
Metadata
Release files for nebgbhist 0.0.5
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 | Actions |
|---|---|---|---|---|
| nebgbhist-0.0.5.tar.gz | 9.4 kB | Without provenance | Details for nebgbhist-0.0.5.tar.gz |
Release files / nebgbhist-0.0.5.tar.gz
| Download URL | nebgbhist-0.0.5.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2241788d8e7750baf41d8678d744c2a25c67214bd80228a05482d32f3a8f2c6
|
|
BLAKE2b-256 checksum How to use checksums |
65062667ac288e04c85b6d74ace3fbcd414e9444fba489d0533bda5f333ec498
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nebgbhist 0.0.5
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.