What remains to be done
At the moment the planning case has been implemented, it is possible to call it using mincom and the "mintemp" option while using the --planning option. It would be interesting to change this feature to only need to use "mintemp". Maybe by creating a file "miscoto_planning.py" in which we would outsource the processing to realize a planning case.
A generic method has been implemented in query.py to allow the use of the Telingo solver and to give a list of generated models as output.
Moreover it is possible with the --outputCSV option to download the Telingo output as a CSV file.
However, I noticed that the transformation of the Miscoto generated knowledge base to be used by the telingo program community_minexch_nohost_temp.lp generates generates a result that is not correct . This is due to reversible reaction problems. Initially the Telingo program used a fact base where each reaction had a unique identifier and the products and reactants were duplicated. I think I have adapted the code, but it does not work
Two ways to do it
- Find a way to transform the fact base for which function with the Telingo code
- Change the way the SBML files are parsed to use them only when using the Telingo solver.
We also find the same problem with the explanation case, so it is important to find a solution.
For the case of explanation it is also necessary to make a new python file ("miscoto_explanation.py") able to treat this case. It is also necessary to create a function able to parse a CSV file provided by the user to generate the observations and the necessary information.
At the moment the explanation case only works for one observation in the internship project