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

diaPasef: No objects to concatenate #383

Open
rednaSander opened this issue Nov 25, 2024 · 2 comments
Open

diaPasef: No objects to concatenate #383

rednaSander opened this issue Nov 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@rednaSander
Copy link

rednaSander commented Nov 25, 2024

Describe the bug
When analyzing phospho-enriched diaPASEF data using a Spectronaut TSV spectral library, AlphaDIA fails with "No objects to concatenate" error during the search. The analysis works for Orbitrap QEHF-X data with similar libraries but fails specifically for diaPASEF data. This is the case on the "main" and "development" branch (v1.8.2.) I've already tried the solutions from previous discussions on this issue, but they haven't resolved the problem.

To Reproduce
AlphaDIA_Log_Tims_diaPasef_NO_OBJ_TO_CONCAT_ERROR.txt
config_yaml.txt
test.spectronaut.csv

system:
Linux thestral 6.1.0-21-amd64 1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

@GeorgWa GeorgWa added the bug Something isn't working label Dec 5, 2024
@GeorgWa
Copy link
Collaborator

GeorgWa commented Dec 5, 2024

Thank you for submitting the bug! This should be addressable quickly.

Searching large libraries is currently not a supported use case and it might take some time to search though.

@rednaSander
Copy link
Author

rednaSander commented Dec 8, 2024

@GeorgWa
Thank you for your response.
I have some follow-up questions to better understand the limitations:

  1. Could you clarify what constitutes a "large" library in this context? My current library contains approximately 5 million target precursors.

  2. I've successfully used larger libraries with non-timsTOF PaSEF data in the past (20M target precursors). Does this mean those results might be unreliable since searching large libraries isn't a supported use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants