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

Regarding bruker .tsf files #25

Open
douweschulte opened this issue Aug 22, 2024 · 3 comments
Open

Regarding bruker .tsf files #25

douweschulte opened this issue Aug 22, 2024 · 3 comments

Comments

@douweschulte
Copy link

Our machines produce Bruker .tsf raw files. I have very little experience with Bruker data file formats but how feasible is support for .tsf files within the current timsrust?

@sander-willems-bruker
Copy link
Collaborator

Hi @douweschulte, thanks for checking in! At the moment .tsf is not supported, but I am not against having support for it in TimsRust. It might be relatively straightforward (as a concept) to implement it (haven't touched that format myself yet and only have secondhand knowledge on it), but one would need the time to do so of course. I'll leave this issue open for others to comment/request/implement/... and hope to get back to it "someday", which unfortunately might be months if not much longer...

@sander-willems-bruker
Copy link
Collaborator

Side note, it should just be data without ion mobility dimension and it should be supported with Bruker's closed source SDK and thus most software suits that use this SDK, such as Timsconvert

@douweschulte
Copy link
Author

douweschulte commented Aug 22, 2024

Thanks for the insight. I found timsconvert and it indeed seems to produce nice mzml files which I should be able to use. As a bit of background I was thinking of making my rust crate rustyms support timstof data. This to support some colleagues that want to use my annotator with timstof data directly.

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