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
EuBIC 2020 developer’s meeting #15
Comments
Thank you for the suggestion. We had similar thoughts (although not specifically for TIMS). |
Of course, we are going to submit an abstract (MsBackendRawFilereader) to EuroBioc 2019. The registration page is not available yet. Right? |
Not yet. Probably needs another 2 to 3 weeks. |
Hi again, are you interested to meet at the bioc2019 in the framework of the User/developer sessions? So far no Greetings, |
Yes, of course - I will be creating an issue for a MS/proteomics/metabolomics session in the coming days. |
I wonder if we could focus our discussion on R for MS-related issues only (Spectra/Chromatogram packages and their exiting and future MsBackends). |
Sure - to be discussed in the coming issue. There could also be sub-groups, depending on number of participants. |
A related question: Will anyone of you present at EuBIC developers meeting ??? |
I plan to - given that my talk will be accepted... |
Hi R for MS developers,
not sure if you are aware of this:
CP & me were wondering: Would it make sense to submit a project proposal that aims at developing a computational framework for trapped ion mobility spectrometry (TIMS) in R?
Michelmann, K., Silveira, J. A., Ridgeway, M. E., & Park, M. A. (2015). Fundamentals of trapped ion mobility spectrometry. Journal of the American Society for Mass Spectrometry, 26(1), 14–24. http://doi.org/10.1007/s13361-014-0999-4
This could boil down to a MSbackend that can read Bruker tdf formated data. This data is novel in the sense that it contains an additional dimension (4D) compared to LC-MS data recorded on qTOFs or qOrbi instruments. Therefore, I expect a lot of challenges for visualisation and analysis. The tfd format is also unique with respect to its internal structure, since all metadata is stored in a SQLite DB, while the peak lists sit in a binary container that can be queried using an API. PASEF data recorded on the timsTOF Pro is stored like this.
What do you think? Would any of you be willing to go there and drive such a project?
Greetings,
Tobi
The text was updated successfully, but these errors were encountered: