csi_analysis: Analytical modules and pipelines for CSI-Cancer
This package contains classes and functions for running modular analysis pipelines on data types commonly used by CSI-Cancer. Currently, this only includes whole-slide images (immunoflourescent scans). In particular, this package is meant to provide abstract base classes that can be fit into an then run in a standard pipeline. This will enable more interchangeability and easier development of new modules, such as for image segmentation or feature extraction.
While much of the functionality is specific to the CSI-Cancer organization, some of the functionality and structure may be beneficial for the broader community. Other packages in the CSI-Cancer organization may depend on this package.
Structure
Currently, this package contains the main module: csi_scan_pipeline.py.
This module contains the abstract base classes for the pipeline, as well as the
ScanPipeline class, which is the main class for running the pipeline. This class
contains the run() method, which handles parallelization, logging, and passing data
between the module components. 4
Documentation
For more detailed documentation, open up docs/index.html in your browser.
To regenerate the documentation, ensure that you have installed the package and then run:
make_docs
Installation
If you haven't yet, make sure to set up an SSH key for GitHub.
- Activate your
conda(conda activate yourenv) orvenv(source path/to/your/venv/bin/activate) environment first. - Clone
csi_imagesand install:
cd ~/path/to/your/repositories
git clone git@github.com:CSI-Cancer/csi_analysis.git
pip install ./csi_analysis
Alternatively, you can "editable" install the package, which will allow you to make changes to the package and have them reflected in your environment without reinstalling:
pip install -e ./csi_analysis
This will add symbolic links to your site-packages directory instead of copying the
package files over.
Metadata
Release files for csi-analysis 0.5.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 | |
|---|---|---|---|---|
| csi_analysis-0.5.0.tar.gz | 31.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| csi_analysis-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.6 kB
Release files / csi_analysis-0.5.0.tar.gz
| Download URL | csi_analysis-0.5.0.tar.gz |
|---|---|
| Size | 31.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73ddfb3ad691c7133a2ae47cae15cbb4dd053863c0d8e2cfbbfbd1db338c91a4
|
|
BLAKE2b-256 checksum How to use checksums |
544cba51967a8daed6d71077fc797566023e1afbc24a1acc956d73705697f522
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / csi_analysis-0.5.0-py3-none-any.whl
| Download URL | csi_analysis-0.5.0-py3-none-any.whl |
|---|---|
| Size | 38.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3ecdd36d5b22c1ce70e2d55ce62ddd8fe864754bd35e013a925d30145d77f24
|
|
BLAKE2b-256 checksum How to use checksums |
908768b4d13de0f5cc7d55956d031dd53a795724c9ecaf27ba2a3914654b01c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for csi-analysis 0.5.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.