Enable users to limit the number of chimeric identifications per spectra #2364
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.
Added a field to common parameters and the search task GUI enabling the user to limit the number of chimeric identifications per spectra.
This new parameter does not have any affect on the search or FDR calculations. The filtering is only performed after FDR has been calculated. The chimeras are grouped then sorted by QValue, then PEP, then score, keeping the top n identifications before writing the output. The default is currently set to 7.
I also added a custom comparer class that can be used in linq statements to group or select by multiple properties and have created a custom chimera comparer for PsmFromTsv and SpectralMatch.
The FilterSpecificPSMs method inside PostSearchAnalysisTask was not functioning. A list was passed in and modified in place without being saved to the original list. This was corrected by adding the ref keyword to the passed in list.