-
Notifications
You must be signed in to change notification settings - Fork 5
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
It seems the annotation is empty in Mouse-GEM - causes problems in addRxns #12
Comments
I loaded the model from the .mat file. |
The |
Hmm, ok. The problem doesn't exist in Human-GEM. An alternative is to fix it in RAVEN (i.e. check these fields more carefully before using them). |
Right, it doesn't exist in Human-GEM. My thinking is that whatever is done there with these default fields is not really robust since it is inconsistent across the different file formats. But you're right, it might be that the fix belongs in RAVEN. I'm pinging @edkerk in case he knows something about this, if it would make sense to report this in RAVEN. |
I think I know how to fix it, it would be a small change in AddRxns. It looks like this (see below). So, an additional check if isempty(newModel.annotation.defaultLB) would probably do the trick. I have not tested if isempty catches this, but I would think so. The same needs to be done for defaultUB. if isfield(newModel,'annotation') & isfield(newModel.annotation,'defaultLB') |
will look into this when making new release of |
this has been fixed in v1.3 |
Description of the issue:
mouseGEM.annotation gives:
ans =
struct with fields:
the defaultLB and UB are used in addRxns, and generates a messed up vector for model.ub, it looks like incorrect memory or something, or that the whole vector is casted to char.
Expected feature/value/output:
Fill these in, -1000 and 1000 is used in Human-GEM
Current feature/value/output:
empty
Reproducing these results:
I hereby confirm that I have:
master
branch of the repositoryThe text was updated successfully, but these errors were encountered: