v0.2.2

Fixes all known major bugs. It is highly recommended that this version is used over others.

Fixes:
For Thermo .raw files and Agilent .d files, it was possible for the TIC to be calculated using centroided data and the extracted values to be from profile data, leading to incorrect data, such as TIC normalized images having values >1. This was changing the method used to extract the intensities to be be the same for both, using a modified scan method from multiplierz.
There was also an issue in the interpolation step of the MS1 workflow. This had led to one ion image to be missing and another to be duplicated in most cases.
There were some errors where trying to make images without saving them would lead to an error due to an undefined variable.
Fixed bug in GUI that would not properly read whether the images should be scaled to a percentile of the intensities or to an absolute threshold.
Saving to the "image" file_savetype would reverse the image dimensions. This has been fixed.

Added:
Users can now add tick marks to "figure" style images to more easily count the number of lines or pixels per line.
Some docstrings for the GUI in preparation to make documentation.

What's Changed

• v0.2.2 including multiple major bug fixes by @EmersonHernly in #3

Full Changelog: v0.2.1...v0.2.2

v0.2.1

This release contains multiple bugs that can result in incorrect data and cause errors preventing image exportation. It is highly recommended to use the most recent version!

Adds multiple visualization options and fixes multiple bugs.

What's Changed

• Update for new version that adds features and fixes major bugs by @EmersonHernly in #2

Full Changelog: v0.1.0...v0.2.1

v0.1.0

The first public version of MSIGen.

Known bugs:
The workflow fails if any of the mass list entries are outside the mass/mobility ranges of all scans.
Titles containing special characters often cause images to fail to save.
MS2 scans may not be grouped together properly when using Thermo .raw files and cause the workflow to fail. This is known to happen when not all line scans use the same collision energy.
Units are not read properly in the GUI, causing all tolerance values to be treated as m/z even when ppm was the provided unit.

Due to these bugs and missing features, it is highly recommended to use the latest version of MSIGen.