You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's some feedback from a user I talked to this morning. It appears that in xcms findChromPeaks (xcmsSet), with Centwave algorithm, we lost the number associated with the "Integration method" parameter when updated from 2.xxx to 3.xxx. (originally, it was written bellow the parameter something like "1 - blabla" and "2 - blabla", and then it was switched with only the blabla without the number).
The problem is that, when you use xcms process history you only get the number, and if you already archived your project and thus have no access to your history anymore, you can not use the relaunch button and thus just have to guess what 1 and 2 corresponds to...
So the idea here: "Please put back the '1 -' and '2 -' in the text of the corresponding options!"
So here come the issue.
Bye,
Mélanie
The text was updated successfully, but these errors were encountered:
Hi @lecorguille
Here's some feedback from a user I talked to this morning. It appears that in xcms findChromPeaks (xcmsSet), with Centwave algorithm, we lost the number associated with the "Integration method" parameter when updated from 2.xxx to 3.xxx. (originally, it was written bellow the parameter something like "1 - blabla" and "2 - blabla", and then it was switched with only the blabla without the number).
The problem is that, when you use xcms process history you only get the number, and if you already archived your project and thus have no access to your history anymore, you can not use the relaunch button and thus just have to guess what 1 and 2 corresponds to...
So the idea here: "Please put back the '1 -' and '2 -' in the text of the corresponding options!"
So here come the issue.
Bye,
Mélanie
The text was updated successfully, but these errors were encountered: