-
Notifications
You must be signed in to change notification settings - Fork 3
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
FEAT allow custom fragment types #136
FEAT allow custom fragment types #136
Conversation
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.
LGTM!
@@ -257,11 +285,18 @@ def __init__( | |||
self.mp_process_num = mp_process_num | |||
self.checkpoint_folder_path = checkpoint_folder_path | |||
|
|||
self.fragment_types = fragment_types |
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.
could those variables be private?
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.
Yep, All of them 👍🏻
@@ -199,6 +200,12 @@ def _parse_modifications(mod_str: str) -> typing.List[str]: | |||
checkpoint_folder_path=self.config["library_prediction"][ | |||
"checkpoint_folder_path" | |||
], | |||
fragment_types=self.config["library_prediction"][ |
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.
introducing lib_pred_config = self.config["library_prediction"]
here might be easier on the eye
fragment_types: 'b;y' | ||
# maximum charge state for predicted fragments | ||
max_fragment_charge: 2 | ||
instrument: Lumos |
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.
just out of interest: where could the user find a list of supported instruments?
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.
That's a bit of a challenge and also applies to enzymes, modifications, instruments. They are constants in peptdeep. @vbrennsteiner and I briefly discussed a nice GUI solution for this.
This PR allows to set other fragment types and charges than
b,y
for PeptDeep library prediction.For example it allows to set
b_modloss;y_modloss
for phospho search.