atgcN_count
1 Introduction
atgcN_count is a tool to stat the counts and percentage of each base in fasta file.
2 Installation
pip install atgcN_count
There will be a command atgcN_count created under the same directory as your pip command.
3 Usage
usage: atgcN_count[-h] [-i <file>] [-v] [-d <int>] [-N]
To stat the counts of each base in a fasta file.
optional arguments:
-h, --help show this help message and exit
-i <file> input fasta file
-v also output statistics for each sequence [False]
-d <int> decimals for output result [2]
-N do not take non-ATGC bases into account when caculate percentage
[False]
Author
Guanliang MENG
Citation
Currently I have no plan to publish atgcN_count.
Metadata
Release files for atgcN-count 0.0.1
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 |
|---|---|---|---|---|
| atgcN_count-0.0.1.tar.gz | 15.6 kB | Without provenance | Details for atgcN_count-0.0.1.tar.gz |
Release files / atgcN_count-0.0.1.tar.gz
| Download URL | atgcN_count-0.0.1.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05ec8bfab818ba20593c6823dd4201a79a17df0c6b5302a9645d94975e8b9272
|
|
BLAKE2b-256 checksum How to use checksums |
3b31bbb9439790c2ba0b86a7427f4271d4c48099a3e2808c5c58b8a0f4fe0415
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.4
|
Security for atgcN-count 0.0.1
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.