Update xisearch.py to accept xisearch1 results #164
Merged
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
picciama
approved these changes
Jan 9, 2025
|
@lutzfischer thanks for fixing this. I merged it back into development, please check that your development branch is still synced with ours as you worked directly on development and not in a separate branch. |
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.
PR Checklist
docsis updatedDescription of changes
Currently the Xisearch class can only handle xiSEARCH2beta results. This updates the code to accept both xi1 and xi2 results.
Xi1 results are read in and then the columns get renamed to xi2 style. Missing columns (decoy_p1, decoy_p2, and linear) are generated based on protein_p[12] columns.
Technical details
Additional context