Skip to content

Releases: AdityaSavara/MSRESOLVE

Version 42.9.4

24 Nov 15:34
4a72d9b
Compare
Choose a tag to compare

Significant overhaul of the Tuning Corrector feature, including addition of a new UserInput of tuningCorrectPatternInternalVsExternal
The logic of tuning corrector is now a little cleaner in the code. Changing of External Patterns without create a mixed pattern is now functional.
The tuning corrector now returns an unaltered ReferenceData object if the feature is turned off.

The concentration finder feature now seems to be compatible with the newest tuning corrector. More testing of uncertainty propagation and also the concentration finder should be performed

Version 42.9.0

10 Nov 01:49
5128b91
Compare
Choose a tag to compare

Tuning Corrector Gas Mixture now works with the Tuning Corrector Intensity feature.

Several other improvements have also been made.

Version 42.8.2

05 Nov 16:11
1261c67
Compare
Choose a tag to compare

This release has significant upgrades related to tuning correction.

  • Until now, tuning correction required was only for pattern correction.

  • Now, tuning correction also corrects for intensity changes.

  • Until now, tuning correction required using several directories and required manually making a mixed reference pattern. Now, all of that happens all in one directory automatically.

  • The Tuning Corrector Gas Mixture feature has been implemented, so that now a person can perform tuning correction with a gas mixture collected with molecules across a range of masses rather than requiring several separate measurements.

  • The XYXY reference pattern feature has been updated.

  • Additional unit tests and other minor updates have been made.

Version 42.0.0

22 Sep 06:29
Compare
Choose a tag to compare

This is a major overhaul of MSRESOLVE. This is a bigger change than the upcoming automatic mixed pattern creator during tuning correction.
Various variable names related to ReferenceData have been changed, and much of the logic flow for ReferenceData has been changed.

Tuning correction and extracting of reference patterns have been moved out of the reference pre-processing and into the main algorithmic flow (in preparation of making mixed reference patterns).

Reference Patterns are now standardized immediately and then expected to be standardized hence-forth. A variety of reference pattern related support functions have also been made.

Version 41.2.0

13 Sep 03:26
dd53fd0
Compare
Choose a tag to compare

A serious bug in tuningCorrector usage has been fixed. The tuning corrector function was written correctly, but when Tuning Corrector was called from the main function, two of the arguments were backwards. So the Tuning Correction was being applied incorrectly (essentially, it was the "Reverse" of what it should have been doing). This issue has now been fixed.

Version 40.1.0

02 Jul 23:26
2da9a6b
Compare
Choose a tag to compare

There was an error which caused crashes during unnecessary molecules deleter has been fixed. The prototypical reference data was a pointer rather than a deep copy. The bug is fixed.

Version 40.0.0

09 May 14:58
b27e478
Compare
Choose a tag to compare

Concentration finder was already working with multiple molecules under certain scenarios. However, there was a logic flaw such that under certain circumstances the mass indices would be wrong when the reference file and the experimental collection file each had extra masses. This should never have been a problem, and was because a mass index was being pulled from the experimental array when it should have been pulled from the reference data array the logic flaw is fixed.

Version 39.5.0

07 May 19:10
Compare
Choose a tag to compare

Improved Documentation, Variable Names, Tuning Corrector instructions, Uncertainties, etc.

Version 39.4.0

11 Nov 01:00
0baf210
Compare
Choose a tag to compare

Fixed an SLSCommon bug.

Version 39.3

01 Jul 05:42
Compare
Choose a tag to compare

This is an incremental Version from 39.0. This enables the raw signals uncertainties to work correctly with timechooser. It was an oversight (essentially a bug) that these features did not work together, but that 'bug' is now fixed.