2011-08-02 - Current status: ImageJ 2.0.0-alpha4
The following is a status update as of 2 August 2011. Yesterday we released ImageJ 2.0.0-alpha4, and we have made great progress in many areas since the last major status update in December.
Data and displayImgLib2 library for its N-dimensional data model. As such, it natively supports many more types of images than ImageJ1, including: signed and unsigned integers of 8, 16 and 32 bits; 1-bit packed binary images (see right); 12-bit packed unsigned integers, which are increasingly common in scientific imaging; 64-bit signed integers; and floating point (i.e., real) images of 32 or 64 bits.
The data and display architecture allows for multiple datasets to be added to a single display, or for the same dataset to be displayed in different ways in multiple displays. We are still finalizing this architecture, but fundamentally it works, though these capabilities are not yet exposed through the user interface. Our goal with this functionality is to enable more use cases we have seen in the scientific community, such as tile-based image registration a la TrakEM2, and multiview orthographic projections by reference (i.e., without maintaining multiple copies of the image data in memory).
We have also expanded support for ROIs and overlays. Rather than allowing only a single ROI at a time, ImageJ2 has built-in support for multiple distinct overlays, both for defining regions of interest for processing, as well as annotating images for publication and sharing. The ROI portion of the code (i.e., is this pixel "in" or "out" of my ROI?) is defined in the ImgLib2 layer, while the overlay portion (i.e., what color is my floating text?) is part of the ImageJ display layer.
ImageJ2 pluginsextensibility framework. These plugins illustrate some of the features of ImageJ2, and serve as examples for how to bring legacy plugins up to date.
ImageJ2 supports several types of plugins depending on what you are trying to do. The most straightforward is the
ImageJPlugin, which is as simple to implement as IJ1's
Plugin interface—there is a single method,
run(), that executes the plugin command. The difference is that the plugin's inputs and outputs are explicitly declared using instance fields annotated with
@Parameter. This eliminates the need to write UI-centric
GenericDialog code as was needed in IJ1, and provides automatic scripting capabilities for all such plugins.
ImageJ2 2.0.0-alpha4 introduces another more flexible type of
DynamicPlugin. By extending this abstract class, it is possible for a plugin to dynamically add, modify and remove its inputs and outputs at runtime. This is useful for plugins that must, for example, prompt for information about each axis of the current dataset.
Another type of plugin is the
Display, which is a more complex piece of code capable of visualizing data in some way. The core ImageJ image viewer is implemented as a
Lastly, there are
PostprocessorPlugins that operate on an
PreprocessorPlugins are applied just prior to a plugin being run, allowing them to prepare the plugin for execution. For example, one
PreprocessorPlugin called the "input harvester" pops up a dialog box prompting the user to input values for the plugin's inputs, similar to
GenericDialog in IJ1. Analogously,
PostprocessorPlugins execute just after a plugin runs, and are useful to handle the results. One
PostprocessorPlugin called the "display postprocessor" takes care of displaying any output datasets that the plugin produced.
Displays are automatically invoked as appropriate when a dataset is created, and the preprocessor and postprocessor plugins are applied automatically as well when a plugin is executed. Changing the behavior of ImageJ is as simple as providing the desired functionality on the Java classpath. As such, ImageJ2 is capable of running in a fully headless environment.
There are also a full set of events that get generated whenever a command is executed. When a command is first invoked, a
ModuleStartingEvent is fired; the preprocessors are called one by one, each firing a
ModulePreprocessEvent upon completion; a
ModuleExecutingEvent is then fired indicating the command itself is running; a
ModuleExecutedEvent fires when the command is finished running; the postprocessors are called one by one, each firing a
ModulePostprocessEvent upon completion; and finally a
ModuleFinishedEvent signals the completion of the entire process.
Like in IJ1, and as you may have guessed from the terminology above, plugins are not the only type of command that can be executed. There are also scripts, IJ1 macros, and other custom code that implements the base ImageJ command interfaces:
ModuleInfo. Hence, not all commands are plugins (e.g., a command might be a script or custom module), and not all plugins are commands (e.g., a plugin might be a
PreprocessorPlugin or a
Displays, inspect the details of an image's data structure, and more. Of course, you can do many of these things with an IDE such as Eclipse or NetBeans, but providing these tools from the ImageJ application itself provides more a posteriori debugging capabilities to end users when problems occur.
Our eventual goal is to translate all existing core IJ1 plugins into the IJ2 framework. For now, much of the functionality present in IJ1 is accessible in IJ2 through the legacy layer (see below), but by reimplementing the plugins in "pure IJ2" we can slowly phase out the legacy layer. Doing so is important because there are problems running ImageJ1 headless, and thus it is difficult to use as a library. In contrast, ImageJ2's plugin framework has been designed with headless operation in mind.
We have put substantial effort into encapsulating the various parts of ImageJ2 as separate "services" that operate as independently as possible. As of this writing, the major core services are as follows:
EventService- Publishes events to the event bus, and allows interested parties to subscribe to them. The service provides the central means of communication between various parts of the codebase.
ObjectService- Tracks available objects of various types, including
PlatformService- Provides hooks for extending ImageJ's behavior depending on the deployment platform (operating system, version of Java, etc.)
ModuleService- Tracks available modules, and provides the infrastructure for executing them.
PluginService- Tracks available plugins, and provides the infrastructure for executing them (using the
DisplayService- Tracks available displays, as well as the active display, and provides the means to create new displays to visualize data.
LegacyService- Enables compatibility with ImageJ1, translating IJ2 data structures back and forth between IJ1 as needed to run legacy IJ1 commands.
ToolService- Tracks available tools—logic binding user input to behavior—as well as the active tool (selected on the toolbar).
UIService- Discovers and launches a user interface for interacting with ImageJ.
OverlayService- Tracks available overlays.
An instance of the
ImageJ class is nothing more than a collection of these services; this instance is referred to as the "application context." Whereas ImageJ1 is a singleton, with static methods to access much of its functionality, we have completed most of the groundwork needed to allow multiple simultaneous ImageJ application contexts in the same JVM.
While the core Java APIs are available on a wide variety of platforms, certain subsets of the API can be problematic in some contexts. In particular, usage of AWT can cause problems when running headless (even with
java.awt.headless=true set). We have taken great pains to avoid all references to the AWT packages in the ImageJ2 core project. We have even gone so far as to invent our own event class hierarchy rather than reuse the events in
java.awt.event (e.g., for mouse and keyboard events).
All use of AWT and Swing is contained outside of the
core projects, in the
ui projects, which implement the ImageJ2 user interfaces. Most of our development effort has gone into the Swing user interface, but we also have a prototype for pure AWT (similar to IJ1), as well as Apache Pivot and Eclipse SWT, with a console-driven "headless" UI planned too.
We hope that in the future, this careful separation of concerns makes it easier to interoperate with ImageJ from a variety of development environments, such as the Google Web Toolkit for web development, Android for mobile devices, or IKVM.NET for use within .NET applications. However, there are still remaining challenges—for example, ImageJ2 and ImgLib2 make liberal use of generics, which can limit code portability. Nonetheless, as long as ImageJ2 is fully usable from a headless context, we can expose it via a client/server architecture such as web services to enable its use from non-Java code.
Compatibility with ImageJ1
The ImageJ2 legacy layer provides compatibility with ImageJ1, allowing ImageJ2 to discover and populate legacy IJ1 plugins just as IJ1 did, with legacy plugins shown in the menu structure with a small microscope icon. ImageJ2 uses a bytecode engineering library called Javassist to intercept important IJ1 events as they occur and adjust the behavior to fit in seamlessly with IJ2. The legacy layer takes care of translating data structures back and forth between ImageJ1 (e.g.,
ROI) and ImageJ2 (e.g.,
Display) as needed, by reference when possible. This technique allows IJ1 commands to be invoked on IJ2 data structures and vice versa, without the user needing to worry too much about which plugins came from where.
Spectral lifetime image analysisImageJ plugin for visualization and analysis of combined spectral lifetime data. While this plugin is functional in ImageJ1, we plan to update it to an ImageJ2 plugin in time for the ImageJ2 release. The plugin will benefit from the more flexible design of ImageJ2 in several ways. First, it utilizes dimensions beyond space and time, so can take advantage of IJ2's N-dimensional data capabilities. Second, it presents several views into the same data, so will benefit from IJ2's separation of data and display. Lastly, it demonstrates IJ2's pluggable display architecture by implementing its own custom display.
We still have more work to do on the display architecture to fully realize all the goals and ideas described above. There are also still many bugs and limitations, particularly with overlays, that we must overcome.
Once the API is largely stabilized, and the application behaves like ImageJ1 as much as possible, we will release a beta version for community feedback. We view the community as a spectrum, with one end consisting of end users who do not program and want to be able to do everything through the UI, and the other consisting of developers who wish to call ImageJ features programmatically and embed parts of it in their own applications. Many people fall somewhere in the middle, having written a few scripts or macros to automate their analysis but also making good use of the UI. With ImageJ2 we are targeting the entire spectrum across the community.
We will also improve the means by which plugins are distributed and shared. This fall, ImageJ2 will merge with the Fiji distribution of ImageJ to provide an automatic updater, including multiple update sites that each provide their own plugins. In this way, developers can start their own collections of ImageJ plugins which are easier than ever for end users to install and keep updated—no more manually downloading JAR files from various web sites and dropping them into the plugins folder (though that will still work if you prefer).
We also plan to update the ImageJ web site. In particular, we will deploy a new section of the site with a centralized plugin listing. This listing will be as seamless as possible, with all plugins from registered update sites appearing automatically, for users to comment, rate, tag and discuss, making it much easier to find ImageJ plugins, scripts and other extensions that provide functionality across many areas.
For more information on future directions, see the ImageJ roadmap.