Skip to content
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

Merged
merged 1 commit into from
May 13, 2024

Conversation

GeorgWa
Copy link
Collaborator

@GeorgWa GeorgWa commented May 9, 2024

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.

@GeorgWa GeorgWa requested a review from mschwoer May 9, 2024 21:34
@GeorgWa GeorgWa marked this pull request as ready for review May 9, 2024 21:34
Copy link
Collaborator

@mschwoer mschwoer left a 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
Copy link
Collaborator

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?

Copy link
Collaborator Author

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"][
Copy link
Collaborator

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
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

@GeorgWa GeorgWa merged commit e5dd426 into development May 13, 2024
4 checks passed
@mschwoer mschwoer deleted the 135-fragment-types-for-library-prediction branch May 29, 2024 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants