-
Notifications
You must be signed in to change notification settings - Fork 52
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
fix: COBRA introduced a conflicting function with RAVEN #183
Comments
@BenjaSanchez could you give examples or descriptions to clarify the conflicts between them. |
@Hao-Chalmers the name is the same, so if I have both toolboxes in my Matlab path and I call let's say RAVEN's |
Should we ask COBRA developers to change the function name from their side? This function was introduced in RAVEN earlier than in COBRA, so I think we have a right to ask them so. The similar case was with |
Yes, I did that before for another function But it seems this issue should be addressed to COBRA, instead of RAVEN. |
One more reason to get #184 running :) |
@Hao-Chalmers @simas232 thanks for the feedback, I was not sure where to raise the issue. @tpfau thanks for the quick fix in opencobra/cobratoolbox#1373 |
This is now fixed on the |
@laurentheirendt @tpfau thanks for the swift fixing. I think this issue has been nicely resolved. |
Description of the issue:
On the latest release of COBRA, the function
removeGenes.m
was introduced, which conflicts with our ownremoveGenes.m
.I hereby confirm that I have:
The text was updated successfully, but these errors were encountered: