deepsignal
Documentation
v0.2.0
make –reference_path not a required input in extract and call_mods module
handle gz file in call_freq script
v0.1.10
make sure results of each read be written together in call_mods’ output
v0.1.9
enable multi-class (>=3) training/predicting,
fix bug of extrating contig name from fast5s
v0.1.8
modify denoise module fix success_file bug update README
v0.1.7
Prevent Queue.qsize() from raising NotImplementedError on Mac OS X (github: vterron/lemon@9ca6b4b) covert raw signals to pA values before normalization in extract_feature module add denoise module add module-chosen options of model (rnn/base/cnn), re-train human model
v0.1.6
add option –positions in extract_features module, add option/function of binary_format feature file to speed up training
v0.1.5
normalize probs before output
v0.1.4
change the loss function to weighted_cross_entropy_with_logits, allow training using unbalanced samples.
v0.1.3
fix the deadlock issue in multiprocessing
v0.1.2
add MANIFEST.in file
v0.1.1
3 modules (extract, call_mods, train) supported
1 maintainer
Metadata
1 maintainer
Release files for deepsignal 0.2.0
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-0.2.0.tar.gz | 46.4 kB | Without provenance | Details for deepsignal-0.2.0.tar.gz |
Release files / deepsignal-0.2.0.tar.gz
| Download URL | deepsignal-0.2.0.tar.gz |
|---|---|
| Size | 46.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bc79548ab1fe88269a0927b968d5e93c60b34b423b55acf67829e60356c64f0
|
|
BLAKE2b-256 checksum How to use checksums |
9ba908b0295019a6097431949182842926a5473a52d46aee2eb3e7e6f2184c11
|
| 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 0.2.0
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.
