deepsignal-plant
Release
0.1.6
bug fixes
enable .gz output in extract/call_mods/call_freq modules
multi-gpu support in call_mods module
update requirements/dependences
0.1.5
make sure results of each read be written together in call_mods’ output
make –reference_path not a required input in extract and call_mods module
0.1.4
modify call_freq module for large genomes,
fix bug of extrating contig name from fast5s
0.1.3
add ranger optimizer and modify train module,
fix Queue.qsize() NotImplementedError in macOS partially, however call_mods in CUDA mode in macOS still doesn’t work,
add init_model option in train module
0.1.2
change imports in ref_reader,
change requirements,
fix and modify denoise module,
fix MKL_THREADING_LAYER error temporarily,
add –region option,
a combined 5mC model replacing CG/CHG/CHH models
0.1.1
fix bug and optimize call_mods without GPU, add call_freq funciton
0.1.0
Release the first vesrion of deepsignal-plant package
1 maintainer
Metadata
1 maintainer
Release files for deepsignal-plant 0.1.6
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 |
|---|---|---|---|---|
| deepsignal-plant-0.1.6.tar.gz | 55.3 kB | Without provenance | Details for deepsignal-plant-0.1.6.tar.gz |
Release files / deepsignal-plant-0.1.6.tar.gz
| Download URL | deepsignal-plant-0.1.6.tar.gz |
|---|---|
| Size | 55.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
246dfffdbc80f5f7287b8fe546db795e8a5fb4321b0cffb02597713595f907a9
|
|
BLAKE2b-256 checksum How to use checksums |
b89e5d42a144b758b1b3a9f4fe714bcd68b4183c3ab33ed78ea28012d9580ede
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/38.4.0 requests-toolbelt/0.9.1 tqdm/4.34.0 CPython/3.5.1
|
Security for deepsignal-plant 0.1.6
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.
