Transformations and options

[Bart Bogaerts]

Transformations (e.g. GraphFuncsAndAggregates) should always behave the same. They should not be influenced by the current set of options. At least, not by options like groundwithbounds or cpsupport.

Now, they do behave differently depending on other options that might not even be relevant at the point where the option is called. For example in getGenerator() in the grounderfactory, we really want to graph all functions and aggregates, no matter what the value for cpsupport is...

SOLUTION: pass these flags in the constructor instead of asking for the global option.

[Broes De Cat]

Additional issue: nbmodels (an MX option) is used to distinguish whether to make an equivalent GROUNDING or not. This should not happen, as nbmodels then changes the grounding behavior even when not doing mx. Solution: add an option to ground, which when doing mx is set according to its number of models within the call to ground.

[Bart Bogaerts]

see f8d8372bb404

[Bart Bogaerts]

see #168: fixes the additional issue

→ f45b7b03087c

[Bart Bogaerts]

see #168 also for the funcconstraints

→ 8f18c0779d3d

[Bart Bogaerts]

checked the falses in GraphFuncAndAggs. Fixes #168

→ 776f92de6cca

[Broes De Cat]

Removing milestone: Later (automated comment)