While using the debug output in ESCET, I see that the printing of saturation information makes the controller synthesis much slower (more than 10x). I found out that the call to setSaturationCallback (see
|
public void setSaturationCallback(SaturationDebugCallback<BDD> callback) { |
) is causing this.
Quite often these operations are not even used for the debug printout, since if
before is equal to
after, no debug info is printed, hence wasting computations.
It would be good to have another implementation of this method that only invokes the callback when
before is not equal to
after.
While using the debug output in ESCET, I see that the printing of saturation information makes the controller synthesis much slower (more than 10x). I found out that the call to
setSaturationCallback(seecom.github.javabdd/src/main/java/com/github/javabdd/BDDFactoryIntImpl.java
Line 143 in a939fc8
Quite often these operations are not even used for the debug printout, since if
beforeis equal toafter, no debug info is printed, hence wasting computations.It would be good to have another implementation of this method that only invokes the callback when
beforeis not equal toafter.