search

GregorCH / ipet

Interactive Performance Evaluation Tools for Optimization Software
MIT License
26 stars 6 forks source link

Additional Information for Rubberband #44

Closed fschloesser closed 7 years ago

fschloesser commented 7 years ago

Rubberband assumes the existence of some particular columns that ipet used to provide, such as several "ConstaintsNumber*" columns. These should be added to the SCIP Solver class. (Maybe some code can be reactivated from the previous version of IPET?)

GregorCH commented 7 years ago

Those columns should be present, because the PluginStatisticReader reads them. I don't think you want to manually add those to the solver class, because they are numerous.

The more you blow up the solver class, the less maintainable they get. A solver should provide nothing but the most relevant solving related facts, that are solver specific. Everything else can be provided by Custom Readers, as well.

fschloesser commented 7 years ago

It is true that the solver class should not get blown up, these columns are not present though. This seems to be because it is not used, i will then just reactivate that.

GregorCH commented 7 years ago

A typical parsed TestRun has the following available data columns:

2017-08-22 17:56:26,728 - INFO -     Constraints_Number_varbound
2017-08-22 17:56:26,728 - INFO -     Constraints_Number_bounddisjunction
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_countsols
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_integral
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_xor
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_knapsack
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_setppc
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_components
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_linear
2017-08-22 17:56:26,729 - INFO -     Constraints_Number_and
2017-08-22 17:56:26,730 - INFO -     Constraints_Number_logicor