c-PMAT : PSR STAIN PREPROCESSING WORKFLOW
c-pmat Computational Preprocessing of extracellular matrix
c-pmat is a interactive user interface, allowing user to easily preprocess, quality control (QC) and generate quantitative extracellular matrix features.
Preprocess constitutes generating tiles and the corresponding metadata from the whole slide images. Quality control is dependant on annotations and this retains the tiles free of artifact and tiles belonging to the annotated regions and ensures enough tissue on the tile is present to perform downstream analysis.
Through the usage of the step by step process, user will be able to preprocess, extract and quantify extracellular matrix features.
Understanding data preparation
In this section we will summarize the organization of directory structure to enable the end user extract the information needed to directly interact with the annotations which comes as a string or different names provided by the pathologists (generic).
In the below example we have a first whole slide image with 6 regions of interest and they are named as ROI1, ROI2, .... ROI6 respectively and the second whole slide image with 3 regions of interest ROI1, ROI2, ROI3 respectively. These annotations are free hand polygon annotations drawn on the tissue by the pathologists to infer the changes in the extracellular matrix components with respect to the individual ROI and cater for inter-tumour and intra-tumour heterogeneity and its implication of features at slide and ROI levels.
Currently, we have the support for the annotations performed by the pathologists using Imagescope on the PSR stained whole slide images.
Once you have annotations, it will retain the ROIs with respect to the individual slide automatically and extract the tiles corresponding to each ROI.
Note: This code can be generically used for other brightfield images and extraction of the annotations performed on Imagescope.
ROI stitching at low resolution
It also helps to restitch the ROI's at a lower resolution for sanity check so it can be further processed by TWOMBLI
Extraction of features within PMAT framework
Reference
Metadata
Release files for c-pmat 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| c_pmat-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for c_pmat-1.0.3-py3-none-any.whl |
Release files / c_pmat-1.0.3-py3-none-any.whl
| Download URL | c_pmat-1.0.3-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c4b9dfec8db4a04b1b24d012cb855b64443284ae3e8922858812263b838d30d
|
|
BLAKE2b-256 checksum How to use checksums |
4f613a71d5d28549049480fe59f7ed307d5211715b855de1b962b9a79e14da0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.14
|
Security for c-pmat 1.0.3
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.