Organize, visualize, and analyze histology images.
Project description
Organize, visualize, and analyze histology images.
HistomicsUI organizes and manages whole slide image (WSI) files using Girder. It has a dedicated interface to select WSI, add annotations manually, and to run analysis and algorithms on all or parts of images.
Girder provides authentication, access control, and diverse storage options, including using local file systems and Amazon S3. WSI images are read and displayed via the large_image module. Algorithms are containerized using Docker and are run using the slicer_cli_web Girder plugin. These can be run on multiple worker machines via Girder Worker and celery.
A set of common algorithms are provided by HistomicsTK.
License
HistomicsUI is made available under the Apache License, Version 2.0. For more details, see LICENSE
Community
Installation
Linux
In linux with Python 3.8 or newer:
Prerequisites:
MongoDB must be installed and running.
An appropriate version of Python must be installed.
HistomicsUI uses large_image sources to read different image file formats. You need to install appropriate sources for the files that will be used.
# install all sources from the main repo
pip install large-image[sources] --find-links https://girder.github.io/large_image_wheelsor
# install openslide and tiff sources
pip install large-image-source-tiff large-image-source-openslide --find-links https://girder.github.io/large_image_wheelsNow install the histomicsui package, have Girder build its UI, and start the Girder server. Note that at Girder may still require an old version of node (14.x) to build correctly – nvm can be used to manage multiple versions of node.
pip install histomicsui[analysis]
girder build
girder serveTo use Girder Worker:
pip install girder_slicer_cli_web[worker]
GW_DIRECT_PATHS=true girder-worker -l info -Ofair --prefetch-multiplier=1Girder Worker needs the rabbitmq message service to be running to communicate with Girder. Both Girder and Girder Worker should be run as a user that is a member of the docker group.
The first time you start HistomicsUI, you’ll also need to configure Girder with at least one user and one assetstore (see the Girder documentation). Additionally, it is recommended that you install the HistomicsTK algorithms. This can be done going to the Admin Console, Plugins, Slicer CLI Web settings. Set a default task upload folder, then import the dsarchive/histomicstk:latest docker image.
Reference Deployment
The standard deployment of HistomicsUI is the Digital Slide Archive. The associated repository has tools for readily installing via Docker, VirtualBox, or shell scripts on Ubuntu.
Development
The most convenient way to develop on HistomicsUI is to use the devops scripts from the Digital Slide Archive.
If you are making changes to the HistomicsUI frontend, you can make Girder watch the source code and perform hot reloads on changes using the --watch-plugin argument to girder build. See the Girder docs for more information.
Annotations and Metadata from Jobs
This handles ingesting annotations and metadata that are uploaded and associating them with existing large image items in the Girder database. These annotations and metadata are commonly generated through jobs, such as HistomicTK tasks, but can also be added manually.
If a file is uploaded to the Girder system that includes a reference record, and that reference record contains an identifier field and at least one of a fileId and an itemId field, specific identifiers can be used to ingest the results. If a userId is specified in the reference record, permissions for adding the annotation or metadata are associated with that user.
Metadata
Identifiers ending in ItemMetadata are loaded and then set as metadata on the associated item that contains the specified file. Conceptually, this is the same as calling the PUT item/{id}/metadata endpoint.
Annotations
Identifiers ending in AnnotationFile are loaded as annotations, associated with the item that contains the specified file. Conceptually, this is the same as uploaded the file via the annotation endpoints for the item associated with the specified fileId or itemId.
If the annotation file contains any annotations with elements that contain girderId values, the girderId values can be identifier values from files that were uploaded with a reference record that contains a matching uuid field. The uuid field is required for this, but is treated as an arbitrary string.
Funding
This work was funded in part by the NIH grant U24-CA194362-01.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file histomicsui-1.6.1.dev52.tar.gz.
File metadata
- Download URL: histomicsui-1.6.1.dev52.tar.gz
- Upload date:
- Size: 723.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.11.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 60efa952b38f87785b80836d01ea3e8742c94a84630cb03653dd1a9c3cf6523d |
|
| MD5 | 499418fd65c28270e7612b5d11ffb1a6 |
|
| BLAKE2b-256 | 127c460753729473adbfa2317f7ff9783fb15c32db17049f2b471331e0d4bfb9 |
File details
Details for the file histomicsui-1.6.1.dev52-py2.py3-none-any.whl.
File metadata
- Download URL: histomicsui-1.6.1.dev52-py2.py3-none-any.whl
- Upload date:
- Size: 221.8 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.11.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 8de080b062f4c0a47b34b5c178d9a99a57bd79856d703d1acf15fcc93db1382b |
|
| MD5 | 24f01c8b92f924f08668db61f013e68e |
|
| BLAKE2b-256 | 08f7a262785c748e88ff74fed3ebcf477531d4fcd7c027d57869815c34186b36 |
