A client to upload reads to minoTour
A command line client for uploading sequencing metrics from Oxford Nanopore Technologies MinKNOW to a LooseLab minoTour server instance.
MinFQ only supports minknow core 4.X.X as it uses ONT’s minknow-api, which is only compatible with said version of MinKNOW.
However, base called data can be uploaded from any version of MinKNOW/Guppy.
To install -
pip install minFQ
Example Commands
In the example commands below example parameters are:
your_user_key: is the long string found in the profile section of your minoTour account.
url_to_your_minotour_server: Probably 127.0.0.1, could be a remote address like minotour.nottingham.ac.uk
port_for_your_server: Probably 8000
To monitor both live and fastq data.
minFQ -k [your_user_key] -w /path/to/your/fastq/files -ip 127.0.0.1 -hn
[url_to_your_minotour_server] -p [port_for_your_server]
To monitor just live data from minKNOW.
minFQ -k [your_user_key] -ip 127.0.0.1 -hn [url_to_your_minotour_server]
-p [port_for_your_server] -nf
To monitor live data and enable limited remote control of minKNOW.
minFQ -k [your_user_key] -ip 127.0.0.1 -hn [url_to_your_minotour_server]
-p [port_for_your_server] -nf -rc
To monitor just fastq data.
minFQ -k [your_user_key] -w /path/to/your/fastq/files -hn [url_to_your_minotour_server]
-p [port_for_your_server] -nm
To monitor fastq statistics only. (Note you will not be able to run subsequent analysis on the server which requires sequence data).
minFQ -k [your_user_key] -w /path/to/your/fastq/files -hn [url_to_your_minotour_server]
-p [port_for_your_server] -nm -s
To start an analysis remotely whilst uploading data. Note reference Id may not be required.
minFQ -k [your_user_key] -w /path/to/your/fastq/files -hn [url_to_your_minotour_server]
-p [port_for_your_server] -nm -j [job_id] -r [reference_id]
minFQ Gui
We are in the process of rebuilding a minFQ gui. Watch this space.
Metadata
Release files for minFQ 1.4.7
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 |
|---|---|---|---|---|
| minFQ-1.4.7.tar.gz | 37.3 kB | Without provenance | Details for minFQ-1.4.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| minFQ-1.4.7-py3-none-any.whl | Python 3 | none | any | Details for minFQ-1.4.7-py3-none-any.whl |
Total release size: 103.5 kB
Release files / minFQ-1.4.7.tar.gz
| Download URL | minFQ-1.4.7.tar.gz |
|---|---|
| Size | 37.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
685bfb6e3c4a30172e7e884bb72364849a7808099afa13240f5681f82c2e6aa7
|
|
BLAKE2b-256 checksum How to use checksums |
f1d3a2087265819052338ccba9457caae60a7c12fe1589443c5d301dafaa71e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Release files / minFQ-1.4.7-py3-none-any.whl
| Download URL | minFQ-1.4.7-py3-none-any.whl |
|---|---|
| Size | 66.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70e454695d66b4b57ec5170ed1fa072ed9e54eda2922167e00507b905ebd3daa
|
|
BLAKE2b-256 checksum How to use checksums |
0ef85fd19d17b372ebc7ac56365877643b1a7946430c9d526555d131c4e9a41e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for minFQ 1.4.7
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.