-
Notifications
You must be signed in to change notification settings - Fork 10
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
How to extracted the MS1 intensity and charge state information from DDAPASEF and diaPASEF files by timspy #2
Comments
Hi, Ad 1. I don't know what tool is used to create these MGFs and what it does. I am sure that the number of peaks reported by TimsPy corresponds to all raw data points (.tdf_raw stores centroided peaks and we don't cut any away). Maybe your software aggregates out the mobility dimension? Ad 2. Tables Precursors and PasefFrameMsMsInfo store the necessary information. You can get them to pandas using table2df method of any class that connects to the data. Best wishes, |
Hi,
Best regards, |
Ad 1. Do you mean something like Compass HyStar? Ad 2. TimsPy parses analysis.tdf_bin and its contents. |
Hi
Best regards, Winnie |
Hello, Ad 1. I am glad to hear that 👍 Ad 2. I am not sure about DDA_PASEF (I will check it), but regarding diaPASEF I am pretty sure that there is no such data available in the raw data. The raw data contains simply centroided peaks that need to be analyzed with a proper algorithm. Such algorithm might be part of the onboard software that is scheduling MS2 fragmentations based on particular peaks. In DIA one is fragmenting whole windows of precursors and I doubt that the onboard software could even cope with that amount of data. Best wishes, |
Hi, Yes. For the diaPASEF files, it is true that the charge state could not be labeled. The charge state information extracted from ddaPASEF files could be done by both DB Browser and MFG files. Hope it could be done by TimsPy. How about the intensity of all features extracted from DDAPASEF files by timspy? |
Hi all,
Background:
I successfully extracted the m/z and ion mobility of MS1 from DDAPASEF data by timspy. Which was followed by the link below. https://github.com/MatteoLacki/timspy
The m/z and ion mobility information could also be extracted by the MGF files which were generated after data acquisition.
Issues:
Looking forward to your reply.
Best regards,
Winnie
The text was updated successfully, but these errors were encountered: