Package qupath.lib.plugins

package qupath.lib.plugins
Classes to support general analysis commands.

The purpose of this is to help abstract away some of the more challenging things around running the command, handling parallelization and monitoring progress.

  • Class
    Abstract plugin aimed towards cases where new objects will be detected inside existing objects (normally TMA cores or annotations).
    Abstract class to help with implementing an interactive plugin.
    General abstract plugin implementation, which defines some methods to facilitate creating plugins that do parallel processing.
    Abstract PluginRunner to help with the creation of plugin runners for specific circumstances, e.g.
    Abstract plugin used for detection tasks that support breaking large regions into smaller ones, and analyzing these in parallel - optionally with overlaps.
    A PluginRunner that simply logs progress and output.
    A SimpleProgressMonitor that sends progress to a log.
    Helper methods to convert ObjectDetectors into runnable tasks, which take care of resolving overlaps when using ParallelTileObjects after the detection is complete and firing notification events in a PathObjectHierarchy.
    Minimal interface that may be used to plugins that perform detection within a specified ROI and using a specified ImageData with set parameters.
    A temporary object, used during parallel processing to represent a tile currently being used for object detection.
    Current processing status for the tile.
    Interface to define a PathPlugin that requires a list of (user-adjustable) parameters.
    Primary interface for defining a 'plugin' command.
    Helper interface to define plugin tasks that require post-processing on a specific thread (i.e.
    Class for monitoring the process of a plugin and displaying feedback to the user.
    A minimal interface for a class capable of running tasks in parallel, giving feedback to the user.
    A utility class to help with the creation of TaskRunner instances.