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
The drift time values (in msec) are being imported into MS-Dial and displayed as 1/K0 values, which is leading to incorrect spread of data and CCS calculations.
The text was updated successfully, but these errors were encountered:
To elaborate, this is using version 5.5.24111, and occurs with Agilent .d files for IM-qTOF data which have been imported into MS-Dial.
The drift time in milliseconds for each peak (as confirmed with Agilent IM-MS browser) is being interpreted by MS-Dial as a 1/K0 value - the numerical values are identical. As mentioned, this is leading to peaks being displayed incorrectly with regards to their mobility, and CCS values are also incorrect as a result.
Hello!
Sorry for the late reply and about the unit!
We are using fixed units for IM units just for now, but peaks should be correct (units are incorrect for some instruments, sorry). Can you send us an example of a peak displayed incorrectly?
Thank you for your cooperation!
The drift time values (in msec) are being imported into MS-Dial and displayed as 1/K0 values, which is leading to incorrect spread of data and CCS calculations.
The text was updated successfully, but these errors were encountered: