This version improves the user interface in various places, implements a new search, and adds nodes for querying OME data and XML/Text/JSON processing.
The design of all parameter editors was refined:
The node search implemented in previous versions produced inconsistent results, as the search bar, algorithm finder, and node list utilized different algorithms for applying filtering and ranking nodes.
A new unified node search was implemented that generates consistent results for all search operations and additionally implements a new algorithm that generates better results.
The algorithm finder was redesigned to be more simple and faster. The new interface uses the new node search.
Tip: if you want to quickly add the first entry in the list, press enter on the keyboard to trigger the “Add” button.
Tip: you can now double-click a slot to trigger the algorithm finder
A standalone algorithm finder (without the need for an existing slot) can be triggered by right-clicking the graph and selecting “Add new node here …”
The new JIPipe version comes with a redesigned error panel that allows users to jump to node that caused the error.
Data tables displaying the current cache can now be right-clicked to open a context menu
The toolbar of the expression editor was redesigned to be easier understandable. An additional option was introduced that allows the selection of a path.
The script editor component was improved and now only allows one instance at the same time.
Additionally, it is now possible to edit scripts in an external editor (changes to the external file are automatically copied into the JIPipe parameter)
It is now easier to extract information from OME images
“OME metadata as table” and “Annotate with OME metadata” provide easily accessible user interfaces to select OME metadata items.
Most data export nodes were redesigned* to utilize a single “File path” attribute instead of handling the output directory and file name independently. Instead of providing many confusing options for automatically generating file names, a default name is provided via the auto_file_name variable. Customization is offered by the expression language.
* Older exporter nodes were marked as deprecated, but continue to work.
The expression allows the storage of files in various locations, including the default data directory that is relative to the project run output (data_dir), the project directory (project_dir), fully custom locations (just type in the path as string), and the newly introduced project-wide user directories.
The new JIPipe version introduces a new project-wide setting that allows to configure a set of directories that can be accessed inside various nodes.
The setting can be accessed as following:
The interface allows to create new entries that have a “Key” and “Path” setting. The key is used to lookup directories in expressions that offer the project_data_dirs variable.
JIPipe uses a Python adapter library (JIPipe-Python) to communicate with Python scripts. In previous JIPipe versions this adapter was provided with the JIPipe plugin, which makes it hard to apply updates. The setup process was converted into an EasyInstaller environment. Additionally, JIPipe now checks for updates for the Python adapter during the startup (this can be changed by navigating to Project > Application settings > Extensions > Python integration (adapter) and unchecking “Automatically check for updates”
Existing JIPipe users will be prompted to install the Python adapter once.
JIPipe now comes with nodes that allow to modify/extract information from XML, text, and JSON data
JIPipe can now generate a project report that contains metadata, dependencies, citations (including ones inferred from utilized nodes/extensions/plugins), an overview of all utilized nodes, and a generated text description of the pipeline.