-
Notifications
You must be signed in to change notification settings - Fork 46
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
Invert qvalue calculation #2327
Merged
trishorts
merged 23 commits into
smith-chem-wisc:master
from
trishorts:invertQvalueCalculation
Jan 11, 2024
Merged
Invert qvalue calculation #2327
trishorts
merged 23 commits into
smith-chem-wisc:master
from
trishorts:invertQvalueCalculation
Jan 11, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2327 +/- ##
==========================================
- Coverage 92.69% 92.67% -0.02%
==========================================
Files 136 136
Lines 21280 21321 +41
Branches 2926 2930 +4
==========================================
+ Hits 19726 19760 +34
- Misses 1072 1081 +9
+ Partials 482 480 -2
|
…vailable for pep so no pep calculated
…mputed and a library gets generated
…peptides with qvaluenotch less that point 01 so that spectrum library will update
trishorts
requested review from
Alexander-Sol,
YulingDai,
elaboy and
nbollis
December 27, 2023 18:22
elaboy
approved these changes
Dec 28, 2023
nbollis
reviewed
Jan 2, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do Target/Decoy curves change based upon this implementation?
nbollis
approved these changes
Jan 2, 2024
Alexander-Sol
approved these changes
Jan 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have never used the correct calculation for q-value, which is (decoy count + 1)/(target count). This is because, the highest scoring PSM would have q-value = 0.5. Bill Noble alerted me to an alternate strategy for computing q-value that would eliminate this problem and allow us to use the correct formula. This is accomplished by computing q-value from lowest scoring PSM to highest scoring PSM subject to the following rule. Whenever the current q-value is greater than the previous q-value, we keep the previous q-value. Now, the highest scoring PSM will have a q-value equal to the q-value of the highest scoring decoy PSM. It will never be zero. c est la vie.
overall we expect to see a higher yield of both peptides and PSMs with q-value < 0.01.
An unfortunate by product of this update is that some unit tests with low psm count fail to have sufficent psms with low q-value. In certain instances, this prevents PEP from being calculated. This problem was solved by adding another mzML that could boost the psm count to a sufficiently high level to allow all unit tests to complete successfully while testing what they were intended to test. Please note, some test assertions had to be changed to accommodate the new results.