Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobility units incorrect for Agilent instrument #459

Open
A-H-MacKenzie opened this issue Nov 21, 2024 · 2 comments
Open

Mobility units incorrect for Agilent instrument #459

A-H-MacKenzie opened this issue Nov 21, 2024 · 2 comments

Comments

@A-H-MacKenzie
Copy link

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.

@A-H-MacKenzie
Copy link
Author

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.

@Bujee415
Copy link
Collaborator

Bujee415 commented Dec 20, 2024

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants