The version was pushed to 5.1.4 due to bugfixes.
JIPipe 5.0.0 introduces a variety of new features and core enhancements, including a new data viewer, new nodes, OME ZARR support, project-global parameters, enhanced project overview, automated author management, Java 21 compatibility, Cellpose 3, and more. JIPipe 5.1.0 adds some missing nodes and data types for handling HCS with OMERO (Screen/Plate/Well). JIPipe 5.1.1 fixes some OMERO issues. JIPipe 5.1.2 fixes some ZARR issues. JIPipe 5.1.3 and 5.1.4 fixes issues with the selection of artifacts.
As versions 5.1.x were released shortly after 5.0.0, we decided to repeat the 5.x changelogs.
JIPipe now has support for reading screens, plates, and wells from OMERO. We also fixed a few issues we encountered in the OMERO implementation. The annotation nodes now can annotate OMERO references with additional metadata (for example, descriptions).
In older JIPipe versions, there was no standardized display component for reviewing results. The available feature set was inconsistent; for example, the plot viewer could not show the set of text annotations associated to the currently displayed data item.
A new standardized viewer component was developed that organizes features into dock panels and has one ribbon with all commands. The new viewer automatically detects if additional information like annotations are available and adds appropriate panels to review them.
Compared to the previous iterations, the new standardized data viewer comes with some additional features:
Due to issues with the 3D viewer and its unsatisfactory performance, we decided to remove the 3D viewer functionality from the image viewer component. Instead, we added options to display the currently shown image in the ImageJ 3D viewer and Napari.
Napari is now available as artifact from within the JIPipe artifact repository. If not configured, JIPipe will automatically obtain a supported version of Napari from the repository and run it.
You can now also start Napari from the main window via Tools | Run Napari.
JIPipe now by default will request from you to setup your author information (name, affiliations, ORCID, etc.).
On saving a project, JIPipe will automatically add you as author if not already present.
We recommend to add your ORCID (ID or URL), as JIPipe otherwise has to guess based on your name if you are already in the list of authors.
The project overview panel (previously accessible via the Settings & overview button at the top right of the window) was fully redesigned.
The new interface reorganizes and simplifies the existing features, while adding new functionality.
All project-wide parameters, including user directories, parameters referenced from nodes, and the newly added project-wide parameters are now all accessible in one panel Parameters. We also added intuitive buttons to modify the set of displayed parameters.
The central main panel now displays a variety of helpful tools and information, depending on availability.
Similar to how application settings are handled, the project settings are now displayed in a dedicated dialog. This resolves usability issues we encountered with the old panel.
Commonly used panels features were moved to the right-hand side, while more advanced or rarely used settings were moved to the left-hand side.
If JIPipe detects that the current user is not in the list of authors, the project overview will open automatically. This enables users not familiar with your project (for example, reviewers) to run your workflow without getting overwhelmed by the pipeline editor.
We recommend to setup parameters, run sets, and descriptions to enhance the user experience of your pipeline.
If you click This is my project or Never do this again, JIPipe will automatically restore all tabs from the project.
The behavior can be turned off per JIPipe instance (Never do this again or via the application settings) or per project (see project settings).
The interface opened by the Run button that can be found at the top right was redesigned and now by default only shows the most important options. The new dialog also covers the execution of compartment outputs and run sets.
If you need to get the old functionality back, choose the Custom option.
The dialog will automatically select “Custom” if you have at least one exporter node present. Otherwise, it will select “Cache” as default output.
With the newly developed Run sets feature we added a way to quickly run specific nodes without navigating through the pipeline or creating workarounds using compartments.
On right-clicking a node, you can now add it to an existing run set or create a new one.
The run sets then will be shown in the Run sets panel on the project overview. Here you can also set metadata like a description or color. To run the set, use the panel that automatically appears in the project overview.
A node can be in multiple run sets. As compartment outputs are also executable nodes, you can also add those.
The new dock-based interface introduced in JIPipe 4.0.0 allowed us to add a Calculator panel into the pipeline editor.
The panel allows you to test out expressions outside running nodes.
We were able to find some performance bottlenecks and could resolve them:
We added support for Cellpose 3.x. The current version supplied by our artifacts repository is 3.1.1.1 under cellpose3
.
Due to the changes in Cellpose, we decided to implement dedicated nodes and artifacts, meaning that you
can use Cellpose 2.x and 3.x in the same project.
The new Cellpose 3 nodes and the existing Cellpose 2 nodes support the processing of 5D images. JIPipe will automatically split the images into frames, apply Cellpose per frame, and re-assemble the results.
We added basic support for OME ZARR into JIPipe. Currently, JIPipe is able to import OME ZARR images into ImageJ1 images (Image) and export them into a OME ZARR directory or ZIP.
Similar to QuPath, JIPipe will store the OME XML in a non-standard path of the ZARR until there is a solution (see here).
JIPipe now can use Tesseract-OCR to do text recognition within an image. The software is provided as artifact and runs on all operating systems.
The node will generate a table with all recognized text and its location that can be further processed with JIPipe nodes (for example, table to text ROI, table to point ROI).
Projects can now have global parameters that can be setup in the project overview window. To support global parameters, we needed to change the behavior of expressions in all existing nodes.
The following variables will now be available:
custom.<key>
and the map custom
project_dir
, string project_data_dir.<key>
, and map project_data_dirs
_global.<key>
<key>
and map of all annotations _local.annotations
Afterward the node may add its own variables.
Please note that later additions overwrite earlier ones.
We added a variety of new nodes and enhanced the features of existing ones based on feedback.
The data trace feature was updated and now can display the trace as table in addition to the graph-based view.
We modernized the JIPipe code to be able to run on Java 21, which will in future become the standard in Fiji.
Due to the changes in Java 21, our custom file chooser (open/save files etc.) lost some features. We used this opportunity to develop a new file chooser from scratch.
The new file chooser has the following features compared to the older version:
We added a new button into the status bar that helps with the management of artifacts. If there are issues with the connection to the artifacts repository, users are now notified.
Additionally, you can now also add local copies of the artifacts repository to avoid downloading artifacts from the internet.