Scan number in MassHunter (Agilent)

71 views
Skip to first unread message

Evgenia Glukhov

unread,
Feb 2, 2018, 1:04:14 AM2/2/18
to GNPS Discussion Forum and Bug Reports
We are having a hard time to find scan numbers in MassHunter programs (Agilent LCMS) to add new compounds to GNPS library properly.

Thank you.

Louis-Félix Nothias

unread,
Feb 2, 2018, 4:28:33 PM2/2/18
to GNPS Discussion Forum and Bug Reports
Hi, 

Thanks for trying to upload your spectra to GNPS library.
Could you please provide more informations about the issue.

Mingxun Wang

unread,
Feb 2, 2018, 4:32:48 PM2/2/18
to GNPS Discussion Forum and Bug Reports
Jenia,

As I recall with Agilent data, the issue is that in conversion, the scan numbers are totally exaggerated in the mzXML. I'm not sure the reason specifically for Agilent. I'd recommend try converting to mzML and maybe it resolves that issue? 

Alternatively, you could convert to mzXML and then open the file in an mzXML viewer to find the appropriate scan for the library spectrum you want to add with the new scan number. 

Another alternative is to export a single scan as an mgf file (or mzXML if possible) from MassHunter and simply add that single spectrum to GNPS libraries. 

Ming

Pieter Dorrestein

unread,
Feb 3, 2018, 12:51:16 AM2/3/18
to GNPS Discussion Forum and Bug Reports
Conversions for Agilent often use the microscans (creates the exaggerated mzXML compared to what you see in the vender software). Try using the conversion approach we used here http://pubs.acs.org/doi/pdf/10.1021/acs.jnatprod.6b00722

Best, P
Reply all
Reply to author
Forward
0 new messages