-
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
[WIP] Multiplex reporting #2286
base: master
Are you sure you want to change the base?
[WIP] Multiplex reporting #2286
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2286 +/- ##
==========================================
- Coverage 91.92% 91.92% -0.01%
==========================================
Files 133 134 +1
Lines 20272 20290 +18
Branches 2824 2826 +2
==========================================
+ Hits 18635 18651 +16
- Misses 1156 1157 +1
- Partials 481 482 +1
|
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.
Overall looks great, just had two questions before aproval
return ionLabels; | ||
} | ||
|
||
public double[] GetMultiplexIonIntensities(MzSpectrum scan, double ppmTolerance = 10) |
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.
Is this tolerance settable by the user? If not, should it be?
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.
I don't think so, but honestly I haven't thought about it too deeply. Ten is a heuristic value that seems to be working, but it's possible that we could implement it as a user specified value in the future.
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.
tolerance should match fragment ion tolerance for the file
|
||
foreach(var psm in Parameters.AllPsms) | ||
{ | ||
psm.SetMultiplexIonIntensities(MultiplexMod); | ||
} | ||
return; |
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.
For each psm, are you only setting the multiplex (diagnostic) ion intensities of a single modification?
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.
Yessir. When Multiplex Quant is enabled, the user can only select one type of multiplex modification (e.g., TMT11 on K + TMT11 on N-terminus). We only need to store the ion intensities for that one multiplex mod.
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.
Looks good, no problems running
Small refactor to multiplex ion quantification to increase speed and code quality. Introduced MultiplexMod class to handle all multiplex operations.