The software now supports reading modulation information (single period and variable modulation) when importing LECO ChromaTOF .PEG files.
The software now includes expanded support for importing additional versions of LECO ChromaTOF .PEG files and importing .PEG files acquired using dual FID/SCD detectors, with a prompt to select the desired data channel during import.
The software now supports importing LECO ChromaTOF .SMP files generated from .PEG source files.
The software now supports importing certain newer versions of LECO ChromaTOF .SMP files containing non-spectral signals.
Note: Not all .SMP files are supported, and newer profile-based .SMP files with MS data are currently unsupported.
The software now supports importing Bruker timsTOF .TSF data files.
The software now includes JEOL's msAxelDataReader version 1.4 and supports data files acquired with JEOL AccuTOF GC-Alpha (JMS-T2000GC).
Edit > List Operations and View > Journal now present a dialog with a table of operations, a Find bar for searching, and a detail pane that displays parameter details upon row selection.
A new Undo Multiple button has been added to Edit > List Operations. It allows the user to select and revert a sequence of operations up to and including the selected row.
The Method Editor now has a more polished user interface, including a new Find bar that enables searching and filtering across available operations.
The Apply Template method operation now includes new options:
A new Load Template method operation is now available, offering two parameters:
A new Save Blob Table operation is now available, which allows the entire Blob Table to be saved to an Excel or CSV file in the same format as the save button on the Blob Table.
A new Save Area Table operation is now available, which allows the Area Table to be saved to an Excel or CSV file in the same format as the save button on the Blob Table when the Area Table is selected.
A new Save Blob Set Table operation is now available, which allows the Blob Set Table to be saved to an Excel or CSV file in the same format as the save button on the Blob Set Table.
The Method Editor now supports adding descriptive text to the entire method and to individual steps. These descriptions accept basic HTML formatting, enabling headings, styled text, and lists, and are displayed before and during interactive runs.
Methods can now be executed in Interactive Mode as an alternative to running them all at once. This mode provides greater control by allowing execution step-by-step, with opportunities for manual verification and adjustments between steps. Interactive Mode is available only when running a method on a single image.
The new Run Custom Operation steps can be incorporated directly into a method to invoke executable plugin commands.
The Summary Report can now be saved directly as an HTML file, with HTML set as the default file type.
The Filter Report can now be saved directly as an HTML file, with HTML set as the default file type.
The Save Summary Report method operation now includes a Preferred Report File Type parameter, allowing selection of HTML or Excel in addition to XML file type.
Compatibility: When batch processing within a project, report file names are not auto-populated if the HTML or Excel type is chosen, while the XML type continues to auto-populate the report path when the operation is the final step in the method.
The Tools > Slice Report for Boiling Range Distribution now supports the use of an external calibration table stored in a CSV or Excel file.
The Plugin Manager now has an improved user interface, including a redesigned plugin table that prioritizes important columns, a Filter bar for searching plugins by name, and an enhanced import process that prompts whether to remove an existing plugin before updating in a single step.
Opening an image failed with an uncaught exception if a linked .gccm calibration file was missing.
Affected Versions: This bug only affects v2025r1.
Workaround: Add the missing .gccm file back at the expected path. An empty .gccm file at the location can also be used to fix the error.
Saving an empty Blob Set table as an XLSX file resulted in an empty file without the expected column names header row.
When saving the Blob Set Table with one or more periods in the file name, portions of the file name might be trimmed when saving the file.
Workaround: Avoid the use of period characters in the name. Alternatively, the exported file can be renamed afterward.
When applying a template that had customized, non-default associations with more than one ISTD peak, the custom associations were sometimes not applied to the matched blobs as defined in the template.
When appending multiple templates by loading using the 'Add to active template' option, custom ISTD associations in the templates were reset in some cases, if the templates contain multiple ISTD peaks.
In rare cases when editing a method, if an error occurred while saving the method, the method files became corrupted or were deleted. Known cases for this were related to the method files having their file properties or permissions altered externally, causing an IO error.
Workaround: Ensure file access before editing the method (e.g., check that the method directory and all files have read/write access and are not marked as hidden).
In some cases, if one or more errors occurred while creating a method, the save action failed and continued to fail even after addressing the errors.
Workaround: Close the Method Editor and create it again, taking steps to avoid the error before clicking Save.
When editing a method with an Apply Template step with the From Current Image option, adding additional Apply Template steps that use the From Current Image option resulted in the existing templates being lost. The additional template steps overwrote the previous files instead of creating new template files.
When running a method with an Apply Template step, no error was shown if the method step's template file was missing or could not be read.
When running a script with a Register Image command, no error or an unrelated error was shown if the register image command used an unknown or unsupported transform type. This may occur when the transform is from another version of the software or from a plugin that is not installed.
The Register Image action is irreversible but did not show an appropriate error or warning message when the step was attempted to be undone via the Undo action.
If one or more steps of a method were unrecognized in the current version of the software, an uncaught error occurred when running the method. This may occur when running methods created in a later version of the software.
When running a method with the Apply Template step while the Template Table dialog was open, the table was not automatically refreshed.
Workaround: Use the Refresh button at the top of the Template Table dialog, or close and reopen the dialog to refresh the table.
If multiple exceptions were thrown during execution of a single method step, these exceptions were displayed incorrectly and inconsistently in the journal. Initially, only one generic warning was displayed in the journal. After saving and reloading the image, the journal included all warnings, but also included an unexpected blank line.
When performing batch processing within Project, under certain conditions, the numeral suffixes added to report and log file names were inconsistent between paired report and log files.
Run data files containing a "#" character in their file name could not be linked to a project.
Workaround: Remove the "#" character.
CSV and text reports could not be shown in the project report viewer if the file or project contained a "#" character in their file path.
Workaround: Remove the "#" character.
If the plugin table was sorted, importing a new plugin did not re-sort the table.
In Tools > Compare Images - Side-by-Side, the Difference view did not properly apply the Included and ISTD normalization options.
Affected Versions: This bug only affects version v2025r1.
The Migration Wizard did not detect old installations of version 2.9 and before.
Affected Versions: This bug only affects version v2025r1.
Several miscellaneous UI messages were not properly displaying apostrophes.
The Method Editor no longer includes the + toolbar button. Operations must now be added exclusively through the Available Operation list.