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
However, the original and refactored tools produce different outputs. hybrid.R tends to detect more features and shift retention times of features that match between two outputs. For features that differ they often do so at just the 3rd or 4th decimal place of m/z. This is apparent by the fact that rounding features to less decimal places leads to more aligned features between the two outputs (example).
Since semi.sup.R is a part of apLCMS Two-Step Hybrid, understanding where the two tools differ would make possible to replace semi.sup() with hybrid() and split apLCMS Two-Step Hybrid into separate Galaxy tools.
hybrid.R
is a refactored version of Hybrid method, originally implemented insemi.sup.R
. Both scripts follow the same procedure, that being:More detailed description on Emory's web.
However, the original and refactored tools produce different outputs.
hybrid.R
tends to detect more features and shift retention times of features that match between two outputs. For features that differ they often do so at just the 3rd or 4th decimal place of m/z. This is apparent by the fact that rounding features to less decimal places leads to more aligned features between the two outputs (example).Since
semi.sup.R
is a part of apLCMS Two-Step Hybrid, understanding where the two tools differ would make possible to replacesemi.sup()
withhybrid()
and split apLCMS Two-Step Hybrid into separate Galaxy tools.Inputs: https://umsa.cerit-sc.cz/u/hechth/h/unnamed-history-2 QC_1.raw & QC_2.raw
Output difference between two methods:
The text was updated successfully, but these errors were encountered: