ugbio_seq_qc
Sequencing QC HTML reports for Ultima Genomics runs.
This package generates self-contained, plotly-based HTML QC reports from
Sorter statistics output (the per-sample JSON/CSV files produced by the
on-tool Sorter). It lives outside ugbio_core because it depends on
ugbio_cloud_utils (cloud_sync) and boto3 for fetching inputs from S3 —
dependencies that the dependency-free ugbio_core foundation must not carry.
Reports
seq_qc_report— single-sample report. One sample's JSON + CSV → one HTML page with a summary table and coverage / read-length / base-quality / MAPQ figures.seq_qc_multi_sample_report— multi-sample report. Auto-discovers the real samples in a run (via theLibraryInfosample sheet when present, otherwise by name pattern), then renders one figure per sample grouped by metric, plus a samples-as-rows / metrics-as-columns comparison table with frozen header row and first column.
Both accept a local directory or an s3:// URI.
Usage
# Single sample — explicit files or a directory to auto-detect the basename
seq_qc_report --json sample.json --csv sample.csv --output report.html
seq_qc_report --input-dir s3://.../603559-L13064-Z0152-CATGCAACACTAGAT/
# Multi-sample — a whole run directory (local or s3://)
seq_qc_multi_sample_report --run-dir s3://.../603559/ --output run_report.html
# Multi-sample — explicit per-sample directories
seq_qc_multi_sample_report --input-dir s3://.../sampleA/ --input-dir s3://.../sampleB/
Modules
| Module | Role |
|---|---|
seq_qc_report.py |
Single-sample report: plotly figure builders (shared) + HTML assembly + CLI. |
seq_qc_multi_sample_report.py |
Multi-sample HTML assembly + comparison table + CLI; reuses the figure builders from seq_qc_report. |
sample_discovery.py |
Sample discovery: LibraryInfo XML parsing, name-pattern filtering, sample loading into SampleData. |
file_resolution.py |
Shared S3 / local file-resolution helpers (list_s3_dir, list_s3_subdirs, resolve_sample_files, ...). |
Metadata
Release files for ugbio-seq-qc 1.33.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 |
|---|---|---|---|---|
| ugbio_seq_qc-1.33.1.tar.gz | 13.1 kB | Without provenance | Details for ugbio_seq_qc-1.33.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ugbio_seq_qc-1.33.1-py3-none-any.whl | Python 3 | none | any | Details for ugbio_seq_qc-1.33.1-py3-none-any.whl |
Total release size: 27.9 kB
Release files / ugbio_seq_qc-1.33.1.tar.gz
| Download URL | ugbio_seq_qc-1.33.1.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73f677400ca9af66fa6c45d7707f31d9755dbf001c7cafa17d3432a4c11f9c3e
|
|
BLAKE2b-256 checksum How to use checksums |
770e4cf024a3a3a46ff399e59ec7a0ab04b0369a92f8295628f1479f2f9fda5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / ugbio_seq_qc-1.33.1-py3-none-any.whl
| Download URL | ugbio_seq_qc-1.33.1-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
999c525bd41bc6fbe68a7d94818e5c835e357d2c0aad8886b730e57ea3d83f9b
|
|
BLAKE2b-256 checksum How to use checksums |
9979fec5888f1616250cee22461ba19ee2d9d7b06d042ccfaaba6a4fd7e4407a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for ugbio-seq-qc 1.33.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.