Addition of "AlphaLP" as a new term - refinements and suggestions welcome #367
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
…S identifier and added name, synonyms and definition to the term alphaLP
…S identifier and added name, synonyms and definition to the term alphaLP
…S identifier and added name, synonyms and definition to the term alphaLP
This was referenced Jan 28, 2025
|
Thank you for preparing the term. For proteases, we usually associate the term itself with a regular expression describing how the protease cleaves an amino acid sequence. Is this a correct translation of your description? /(?<=[TSAV])/ |
|
yes, thank you - would I generate another term and add it as a regex via the "relationship" metadata? |
|
Yes, please. |
mobiusklein
approved these changes
Jan 28, 2025
|
Okay, this looks ready to go. Are there any final changes you want to make before we merge this? |
|
no - thank you for the quick review! |
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.
Please see: #366 for more details.
I used the script in this repository,
find_next_available_number.pyto find the biggest gap in the identifier space, and picked the next from that gap: