-
Notifications
You must be signed in to change notification settings - Fork 44
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
Human 1.4 #180
Merged
Merged
Human 1.4 #180
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
- The Yaml file is updated by exporting with the new writeHumanYaml function.
- this optional feature allows to mute the notification messages while running the function
1. Enable automatic loading of yaml file from default location; 2. Mute notification messages while running the test.
fix: systematically add double quote to string elements in Yaml file
HMR_3851 is the only reaction in the "Nitrogen metabolism" subsystem, so this change also effectively removes this subsystem from the model.
Subsystem was duplicated with different capitalization
Evidence does not support the existence of this reaction in humans.
- Since the addition of `spontaneous` field, there could be non-string elements in array. This adjustment allows the recognition of last element regardless of its type.
The change of this commit is made through following command: `rxnAssoc.rxnMAID = regexprep(rxnAssoc.rxns,'^HMR_','MA_');`
1. Remove ids that do not start with `MA_` prefix; 2. Pad in zero to digital part to ensure the elements with identical length.
feat: add `rxnMAID`field to JSON file
feat: yaml worflow
command: git merge -Xtheirs devel
Co-authored-by: Ronan Fleming, Thomas Pfau
Fix: subsystem changes and reaction deletion
- Modify rxn JSON file by removing the id that had been deleted in #171
chore: sync JSON file content with model
previously the leftEquation and rightEquation fields became unequal in size
style: cleauthorship and timestamps
- Since the boundary mets had been removed from model, it is no longer necessary to load them into `unconstrained` field.
feat: remove the boundary compartment
It's not really obvious to me if it should be a |
mihai-sysbio
approved these changes
Jun 12, 2020
The removal of the boundary compartment is a pretty substantial change. Not necessarily in terms of work, but in terms of model changes (>1000 metabolites deleted). |
JonathanRob
approved these changes
Jun 12, 2020
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.
Main improvements in this PR:
Human-GEM
, given the built-inGithub blame
featurerxnMAID
field to JSON file #175):rxnMAID
field to reaction annotation JSON file, as discussed in feat: new sets of id for reactions and metabolites #174yamllint
andcobrapy
model import as GitHub actionsHMR_5407
,RN0001R
,RN0002N
andRN0002R
, as addressed in Remove Nitrogen metabolism subsystem #129HMR_4362
from model and reaction annotation JSON file, as proposed in Remove HMR_4362 from the model #153Yaml
, as reported in YAML format issues in modelFiles/yml/HumanGEM.yml #169