CIDC NGS Pipeline API
Overview
This repository serves as an interface between the CIDC and Bioinformatics teams to determine specifications and documentation related to NGS pipelines.
Repository structure:
.
├── README.md
├── cidc_ngs_pipeline_api
│ ├── output_API.schema.json
│ ├── rna
│ │ ├── rna.md
│ │ ├── rna_config.schema.json
│ │ ├── rna_output_API.json
│ │ └── imgs
│ | └── RIMA.png
│ ├── atacseq
│ │ ├── atacseq.md
│ │ ├── atacseq_output_API.json
│ │ └── imgs
│ | └── atacseq.png
│ ├── tcr
│ │ ├── tcr.md
│ │ └── imgs
│ | └── TCRseq.png
│ └── wes
│ ├── wes.md
│ ├── wes_config.schema.json
│ ├── wes_output_API.json
│ ├── wes_tumor_only_output_API.json
│ ├── wes_output_API.py
│ └── imgs
│ └── wes.png
├── tests
│ └── test_apis.py
├── requirements.dev.txt
├── requirements.txt
├── MANIFEST.in
├── CHANGELOG.md
├── setup.py
└── .github
└── workflows
└── ci.yml
cidc_ngs_pipeline_api module
-
The
output_API.schema.jsonfile defines the schema structure:filter_group: Filter under which the file would appear during faceted search. It is the GCS-URI top-level hierarchyfile_path_template: Local file path used for CLI uploadshort_description: Description to appear on hovering over file name in file browserlong_description: Longer description to appear on file documentation pagefile_purpose: Assigns a tag to show up in a particular file-browser view configuration. Permissible values:Source view,Analysis view,Clinical view,Miscellaneous
-
Within the directory for each assay:
-
The defined schema is used to structure information about pipeline-related files in the respective
< assay >_output_API.json. -
Information related to YAML configurations (which are generated by the CIDC and configured with CIMAC IDs to run the pipelines), are described in the respective
< assay > config.schema.json. -
Documentation related to each pipeline is in the respective
< assay > .md.
-
Developer Setup
Install necessary dependencies.
pip install -r requirements.dev.txt
Install and configure pre-commit hooks.
pre-commit install
Metadata
Release files for cidc-ngs-pipeline-api 0.1.24
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 |
|---|---|---|---|---|
| cidc_ngs_pipeline_api-0.1.24.tar.gz | 2.3 MB | Without provenance | Details for cidc_ngs_pipeline_api-0.1.24.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cidc_ngs_pipeline_api-0.1.24-py3-none-any.whl | Python 3 | none | any | Details for cidc_ngs_pipeline_api-0.1.24-py3-none-any.whl |
Total release size: 4.7 MB
Release files / cidc_ngs_pipeline_api-0.1.24.tar.gz
| Download URL | cidc_ngs_pipeline_api-0.1.24.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f680e6a56dbd79d2edd8bbabfa24cbb0b5e226a6d8c79e57cb9342e84f9a28a2
|
|
BLAKE2b-256 checksum How to use checksums |
a76d0daf41ca23eaf3cbe13a444dc7fb8aba5c860469d739ca4bcf67afcdc870
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / cidc_ngs_pipeline_api-0.1.24-py3-none-any.whl
| Download URL | cidc_ngs_pipeline_api-0.1.24-py3-none-any.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6aa3c42509fda8413ca39732c270093e7e4f4646967656f67ca61181c5a96d9d
|
|
BLAKE2b-256 checksum How to use checksums |
2b9ff690446b9072a14f476c4044d4c313c48c79ec3fb76fe90cd347d4f936f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for cidc-ngs-pipeline-api 0.1.24
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.