keras_biological_gaps_sequences
Python package to generate on-hot encoded biological gaps to use for training and prediction.
How do I install this package?
As usual, just download it using pip:
pip install keras_biological_gaps_sequences
Tests Coverage
Since some software handling coverages sometimes get slightly different results, here’s three of them:
Available datasets
Currently, there is only a dataset of gaps available within the package: the mapping of known gaps from hg19 to hg38. In the future, we will be adding more mapping.
Usage example
To use the sequence you can do as follows:
biological_gap_sequence = BiologicalGapsSequence(
source="hg19",
target="hg38",
source_window_size=1000,
target_window_size=1000,
batch_size=32
)
model = build_my_denoiser()
model.fit_generator(
biological_gap_sequence,
steps_per_epoch=biological_gap_sequence.steps_per_epoch,
epochs=2,
shuffle=True
)
Metadata
Release files for keras-biological-gaps-sequence 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 | Actions |
|---|---|---|---|---|
| keras_biological_gaps_sequence-1.0.3.tar.gz | 4.7 kB | Without provenance | Details for keras_biological_gaps_sequence-1.0.3.tar.gz |
Release files / keras_biological_gaps_sequence-1.0.3.tar.gz
| Download URL | keras_biological_gaps_sequence-1.0.3.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a239981bc67a26398344327fdae7371bdca3078a8644728f4e1c5560bb50b43
|
|
BLAKE2b-256 checksum How to use checksums |
b7d765e395c893d7400ba40b6374aaa0431fcc8ce07ec2198920da8cd8dcf6f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Security for keras-biological-gaps-sequence 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.