-
Notifications
You must be signed in to change notification settings - Fork 1
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
Gapfill update #73
Gapfill update #73
Conversation
In line 200 the official code was not used for testing due to making the rest of the process faster. Changed that line back to the official code.
Now gapfill should be able to do the gap filling via an Excel table.
…gapfill-update
- Added Development - Added logo - Refined appearance
For most modules the correct imports should already be defined on the dev branch. |
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.
I would suggest merging #72 first, then adopting the new main.py, the io.py and the config to include everything gapfill related.
I resolved the merge conflicts and accepted changes from dev when neccessary. What still needs to be done is:
|
…egems into gapfill-update
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.
Looks good, the remaining docs can be updated directly on dev
.
I think we can merge
gapfill
now completely intodev
andmain
. I tested it on two of my models, and it runs through without any issues now. Additionally, the gap filled model is valid according to COBRApy.