While I know there are necessary bugs to be fixed in the save feature, I wanted to also work on some needed upgrades for the SettingsFactory. I've been noticing that there is potential to centralize a decent amount of tools into it while reducing the risk of creating an overly complex swiss-army knife (credit goes to Dennis for that term).
First off, there's the matter of Gurobi. I would like to thank Jim for his work towards the gurobi directory finder thus far. I would imagine, given the conversations I've had with Jim, that there's a lot of benefit to knowing the directories that gurobi resides within a system. First, there is the technique of reading the environmental variable to detect whether or not Gurobi was properly installed. I might be mistaken on this, but if Gurobi has no environmental variable, it may also imply that it hasn't been activated and therein wouldn't be functional to a user. Upon further research, there exists a file called gurobi.lic that should represent an active gurobi license. I know most are already aware of the fact that FBA cannot run without an active gurobi license, and I'd imagine GDBB is the same. For more information: http://www.gurobi.com/resources/faqs#license-keys
So this is my current ambition with the project because this will be an inevitable bug if not resolved. I will make it bullet pointed with check marks on what's been accomplished thus far. Afterwards I will test it to make sure it is functional
While I know there are necessary bugs to be fixed in the save feature, I wanted to also work on some needed upgrades for the SettingsFactory. I've been noticing that there is potential to centralize a decent amount of tools into it while reducing the risk of creating an overly complex swiss-army knife (credit goes to Dennis for that term).
First off, there's the matter of Gurobi. I would like to thank Jim for his work towards the gurobi directory finder thus far. I would imagine, given the conversations I've had with Jim, that there's a lot of benefit to knowing the directories that gurobi resides within a system. First, there is the technique of reading the environmental variable to detect whether or not Gurobi was properly installed. I might be mistaken on this, but if Gurobi has no environmental variable, it may also imply that it hasn't been activated and therein wouldn't be functional to a user. Upon further research, there exists a file called gurobi.lic that should represent an active gurobi license. I know most are already aware of the fact that FBA cannot run without an active gurobi license, and I'd imagine GDBB is the same. For more information: http://www.gurobi.com/resources/faqs#license-keys
So this is my current ambition with the project because this will be an inevitable bug if not resolved. I will make it bullet pointed with check marks on what's been accomplished thus far. Afterwards I will test it to make sure it is functional