Skip to content

Computational Pathology Toolbox developed by TIA Centre, University of Warwick.

License

Notifications You must be signed in to change notification settings

measty/tiatoolbox

 
 

Repository files navigation

This visualization tool is in the process of being added to tiatoolbox, but for the moment is not usable there. This tiatoolbox fork makes it available, but it is a work in progress and will probably have a few issues. If you find one let me know! also, if there is any sort of visualization task you'd like to do which seems like it might fit in this tool but which can't be easily done with it at the moment, please suggest it.

Setup

If you already have a tiatoolbox install

If you already have a develop version of tiatoolbox set up, it should be sufficient to crete a new branch for your local tiatoolbox git from this repository, and switch to that when you want to do some visualization stuff.

git remote add tiavis https://github.com/measty/tiatoolbox/\ git fetch tiavis
git checkout -b feature-add-gui tiafork/feature-add-gui

You will also need to add a couple of extra packages to your environment:

conda install bokeh -c bokeh
conda install flask-cors

From scratch

Otherwise, pip install from this repo:

pip install git+https://github.com/measty/tiatoolbox.git

Usage

start the interface using:

tiatoolbox visualize --img-input path\to\slides --img-input path\to\overlays

alternatively just one path can be provided; in this case it is assumed that slides and overlays are in subdirectories of that provided directory called 'slides' and 'overlays' respectively.
Another option to start the interface is:
bokeh serve --show ./tiatoolbox/visualization/bokeh_app --args path\to\slides path\to\overlays

In the folder(s) that your command pointed to, should be the things that you want to visualize, following the conventions in the next section.

Data format conventions/filestructure

in the slides folder should be all the slides you want to use, and the overlays folder should contain whatever graphs, segmentations, heatmaps etc you are interesting in overlaying over the slides.

When a slide is selected in the interface, any valid overlay file that can be found that contains the same name (not including extension) will be available to overlay upon it.

Segmentation:

The best way of getting segmentations (in the form of contours) into the visualization is by putting them in an AnnotationStore. The other options are .geojson, or a hovernet -style .dat, both of which can usually be loaded within the interface but will incur a small delay while the data in converted internally into an AnnotationStore.

If your annotations are in a geojson format following the sort of thing QuPath would output, that should be ok. Contours stored following hovernet-style output in a .dat file should also work. An overview of the data structure in these formats is below.

Hovernet style:

sample_dict = {nuc_id: {
                             box: List[],
                             centroid: List[],
                             contour: List[List[]],
                             prob: float,
                             type: int
			     ... #can add as many additional properties as we want...
                             }
                ... # other instances
              }
geojson:
{"type":"Feature",
"geometry":{
	"type":"Polygon",
	"coordinates":[[[21741, 49174.09],[21737.84, 49175.12],[21734.76, 49175.93],[21729.85, 49179.85],[21726.12, 49184.84],[21725.69, 49187.95],[21725.08, 49191],[21725.7, 49194.04],[21726.15, 49197.15],[21727.65, 49199.92],[21729.47, 49202.53],[21731.82, 49204.74],[21747.53, 49175.23],[21741, 49174.09]]]},
	"properties":{"object_type":"detection","isLocked":false}
}

If your data is not in one of these formats, it is usually fairly straightforward to build an annotation store out of your model outputs.
A small script of 6-10 lines is usually all that is required. There are example code snippets illustrating how to create an annotation store in a variety of common scenarios in: documentation

Most use-cases should be covered in there, or something close enough that a few tweaks to a snippet will do what is needed.

Heatmaps:

will display a low-res heatmap in .jpg or .png format. Should be the same aspect ratio as the WSI it will be overlaid on.

Whole Slide Overlays:

Can overlay multiple WSI's on top of eachother as separate layers

Graphs:

Graphs can also be overlaid. Should be in a dictionary format, saved as a pickled .pkl file. eg:

graph_dict = {  'edge_index': 2 x n_edges array of indices of pairs of connected nodes
		'coordinates': n x 2 array of x,y coordinates for each graph node
		}

Other stuff:

Colormaps/colouring by score:

Once you have selected a slide with the slide dropdown, you can add any number of overlays by repeatedly choosing files containing overlays from the overlay drop menu. They will be put on there as separate layers. In the case of segmentations, if your segmentations have the 'type' property as one of their properties, this can additionally be used to show/hide annotations of that specific type. Colors can be individually selected for each type also if the randomly-generated colour scheme is not suitable.

You can select the property that will be used to colour annotations in the colour_prop box. The corresponding property should be either categorical (strings or ints), in which case a dict-based colour mapping should be used, or a float between 0-1 in which case a matplotlib colourmap should be applied. There is also the option for the special case 'color' to be used - if your annotations have a property called color, this will be assumed to be an rgb value for each annotation which will be used directly without any mapping.

The 'colour type by property' box allows annotations of the specified type to be coloured by a different property to the 'global' one. For example, this could be used to have all detections coloured according to their type, but for Glands, colour by some feature describing them instead.

Running models:

Regions of the image can be selected, using either a box select or points, which can be sent to a model via selecting the model in the drop-down menu and then clicking go. Available so far are hovernet and nuclick.

To save the annotations resulting from a model, or loaded from a .geojson or .dat (will be saved as a SQLiteStore .db file which will be far quicker to load) use the save button (for the moment it is just saved in a file '{slide_name}_saved_anns.db' in the overlays folder).

Zoomed out plotting:

By default, the interface is set up to show only larger annotations while zoomed out. Smaller annotations which would be too small to see clearly while zoomed out will not be displayed. The 'max-scale' value can be changed to control the zoom level at which this happens. A larger value will mean smaller annotations remain visible at more zoomed out scale. If you want all annotations to be displayed always regardless of zoom, just type in a large value (1000+) to set it to its max. In the case of very many annotations, this may result in some loading lag when zoomed out.

Other options:

There are a few options for how annotations are displayed. You can change the colourmap used in the colormap field if you are colouring objects according to a continuous property (should be between 0-1) - by entering the text of a matplotlib cmap. The buttons 'filled', 'mpp', 'grid', respectively toggle between filled and outline only rendering of annotations, using mpp or baseline pixels as the scale for the plot, and showing a grid overlay.

TIA Toolbox

Documentation Status Travis CI Status

PyPI Status


DOI DOI

Computational Pathology Toolbox developed at the TIA Centre

Getting Started

All Users

This package is for those interested in digital pathology: including graduate students, medical staff, members of the TIA Centre and of PathLAKE, and anyone, anywhere, who may find it useful. We will continue to improve this package, taking account of developments in pathology, microscopy, computing and related disciplines. Please send comments and criticisms to tia@dcs.warwick.ac.uk.

tiatoolbox is a multipurpose name that we use for 1) a certain computer program, 2) a Python package of related programs, created by us at the TIA Centre to help people get started in Digital Pathology, 3) this repository, 4) a certain virtual environment.

Developers

Anyone wanting to contribute to this repository, please first look at our Wiki and at our web page for contributors. See also the Prepare for development section of this document.

Links, if needed

The bash shell is available on all commonly encountered platforms. Commands in this README are in bash. Windows users can use the command prompt to install conda and python packages.

conda is a management system for software packages and virtual environments. To get conda, download Anaconda, which includes hundreds of the most useful Python packages, using 2GB disk space. Alternatively, miniconda uses 400MB, and packages can be added as needed.

Github is powered by the version control system git, which has many users and uses. In Github, it is used to track versions of code and other documents.

Examples Taster

  1. Click here for jupyter notebooks, hosted on the web, with demos of tiatoolbox. All necessary resources to run the notebooks are remotely provided, so you don't need to have Python installed on your computer.
  2. Click on a filename with suffix .ipynb and the notebook will open in your browser.
  3. Click on one of the two blue checkboxes in your browser window labelled either Open in Colab or Open in Kaggle: colab and kaggle are websites providing free-of-charge platforms for running jupyter notebooks.
  4. Operate the notebook in your browser, editing, inserting or deleting cells as desired.
  5. Changes you make to the notebook will last no longer than your colab or kaggle session.

Install Python package

If you wish to use our programs, perhaps without developing them further, run the command pip install tiatoolbox or pip install --ignore-installed --upgrade tiatoolbox to upgrade from an existing installation. Detailed installation instructions can be found in the documentation.

To understand better how the programs work, study the jupyter notebooks referred to under the heading Examples Taster.

Command Line

tiatoolbox supports various features through command line. For more information, please try tiatoolbox --help

Prepare for development

Prepare a computer as a convenient platform for further development of the Python package tiatoolbox and related programs as follows.

  1. Install pre-requisite software
  2. Open a terminal window
    $ cd <future-home-of-tiatoolbox-directory>
  1. Download a complete copy of the tiatoolbox.
    $ git clone https://github.com/TissueImageAnalytics/tiatoolbox.git
  1. Change directory to tiatoolbox
    $ cd tiatoolbox
  1. Create virtual environment for TIAToolbox using
    $ conda create -n tiatoolbox-dev python=3.9 # select version of your choice
    $ conda activate tiatoolbox-dev

or

    $ conda create -n tiatoolbox-dev python=3.8 # select version of your choice
    $ conda activate tiatoolbox-dev
    $ pip install -r requirements_dev.txt
  1. To use the packages installed in the environment, run the command:
    $ conda activate tiatoolbox-dev

License

The source code TIA Toolbox (tiatoolbox) as hosted on GitHub is released under the The 3-Clause BSD License.

The full text of the licence is included in LICENSE.

Auxiliary Files

Auxiliary files, such as pre-trained model weights downloaded from the TIA Centre webpage (https://warwick.ac.uk/tia/), are provided under the Creative Commons Attribution-NonCommercial-ShareAlike Version 4 (CC BY-NC-SA 4.0) license.

Dual License

If you would like to use any of the source code or auxiliary files (e.g. pre-trained model weights) under a different license agreement please contact the Tissue Image Analytics (TIA) Centre at the University of Warwick (tia@dcs.warwick.ac.uk).

About

Computational Pathology Toolbox developed by TIA Centre, University of Warwick.

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Languages

  • Python 75.8%
  • Jupyter Notebook 23.0%
  • Other 1.2%