-
Notifications
You must be signed in to change notification settings - Fork 4
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
ValueError: not enough values to unpack (expected2, got 0) #29
Comments
@AlexandreHutton was going to add direct support for prosit libraries. Let's see if that works because that would avoid any problems with library conversion. Lex can you please update us where we are with that? |
I found this exact error while working with the FragPipe library. I thought it might be a problem with the library itself, but it sounds like it's an issue with the code. |
Thanks Lex for the update. I have some ideas. If there was a way to convert a library that we know works to the other formats then we could rule out or confirm the issue relates to edge cases with the library format. Since you think the problem is with fdr calculations and adding decoys gets past the error to produce empty output, I wonder how the fdr calculation deals with the case where there are no decoy hits. This could happen if the library contains no decoys or by luck in some rare circumstances. @LiaSerrano, does your library have decoys? @AlexandreHutton does the frag pipe library have decoys? |
The library I was using has reverse sequence decoys predicted by prosit. This error actually doesnt happen to me when I take out the decoy entries. Let me know if you would like me to send an example! Thank you |
It does not. I converted some entries from another (functional) library and added them in, which resulted in the empty output mentioned previously. |
I wonder if the decoy is the same as the label CsoDIAq looks for. It might help us understand if you can share the exact library you're using. You could email it to Lex and I if you want to keep the library private. |
Please do! |
I'll shoot over an email, thanks! |
Thanks Lex, It might be how it handles where the decoys are hit. If it hits a decoy within the first 100 proteins (sorted by MaCC) then I believe it should return an empty list. I don't remember how @CCranney made it handle when it never hits a decoy but that could be another place to look. It might help you debug if you can look at the intermediate matches list (that would be in memory) for proteins and see where the decoys fall in the order. Thanks for looking at this Lex |
Hi all, I dug into the code, looking specifically for the error @LiaSerrano included in her PDF in the first comment. Backtracing the error, I think no peptides were identified (the Breakdown of my thought process:
It looks like it tried to break
|
I tried to format a Prosit library like the TraMl lib. I am getting a similar error to what I did with an MGF massiveKB library—I think its not able to associate peptide to protein ?
I get a “file_corrected” output but the peptide/spectral FDR outputs are empty and there is no proteinFDR output. These outputs appear when I take out the decoys, however.
Let me know if you would like me to send over the library I was using if that would be helpful.
csodiaq_error_August.pdf
The text was updated successfully, but these errors were encountered: