Harmony to Organoid
Example output
Check out this page for exemplary output files.
How to Prepare
You can install the tool via pip:
pip install harmony-to-organoid
How to Run
How to run from commandline
Process your data exported from Harmony by executing the command harmony-to-organoid process.
Parameters:
--index-file: (Required) Path to the Harmony export index XML file (Index.idx.xml) or (Index.xml) located next to the corresponding TIFF files.--output-dir: (Required) Path to your desired output directory.--lut-min: (Optional) Comma-separated minimum LUT (Lookup Table) values for each channel.--lut-max: (Optional) Comma-separated maximum LUT values for each channel.--colors: (Optional) Comma-separated colors for each channel.--align-fields: (Optional) Align fields using ashlar. True by default.--exclude-fields: (Optional) Comma separated list of field IDs which should not be processed.
Example:
harmony-to-organoid process \
--index-file MY/INPUT/DATA/Index.xml \
--output-dir MY/OUTPUT/DATA \
--lut-min 100,100,100,100 \
--lut-max 2000,1000,1500,2000 \
--colors white,orange,blue,#ff0000 \
--exclude-fields 2,3,7
Output:
After successfully running the processing command, your specified output directory (MY/OUTPUT/DATA) will contain the following:
-
Projections:
Maximum intensity projection images (projections/) generated for each data group, providing 2D summaries of your 3D data. -
Plots:
Visual representations of the data are stored inplots, including group bounding boxes and projections placed within their respective areas, ensuring spatial consistency and aiding in data interpretation. -
README Files:
Automatically generated documentation (README.mdandREADME.html) that includes embedded plots for easy reference and sharing.
How to run from Jupyter notebook
Check out our example notebook notebook.ipynb.
Metadata
Release files for harmony-to-organoid 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 | Actions |
|---|---|---|---|---|
| harmony_to_organoid-0.5.0.tar.gz | 13.4 kB | Without provenance | Details for harmony_to_organoid-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| harmony_to_organoid-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for harmony_to_organoid-0.5.0-py3-none-any.whl |
Total release size: 26.6 kB
Release files / harmony_to_organoid-0.5.0.tar.gz
| Download URL | harmony_to_organoid-0.5.0.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74d4021377ca2e9261865179b16c62ff5fb696924306b6056a2f8442be8352e8
|
|
BLAKE2b-256 checksum How to use checksums |
eda9e007e19fc40110a298beb276b46b59361f81372d2570143fcdb33bee71d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.31
|
Release files / harmony_to_organoid-0.5.0-py3-none-any.whl
| Download URL | harmony_to_organoid-0.5.0-py3-none-any.whl |
|---|---|
| Size | 13.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76028575555f67577b19bf1825245acd6fb1381d2ce347840cea603dd458e30f
|
|
BLAKE2b-256 checksum How to use checksums |
ba7aa99e019be47bbe7c4e4086efd4800b54cc3d23d638f4c928bdb6b773d314
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.31
|
Security for harmony-to-organoid 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.