You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on utilizing the MultivaluedDecisionDiagram class to handle an MDD I've constructed through knowledge compilation. This MDD is quite large, and I've already applied heuristics to minimize its size. However, I've encountered an issue with the mandatory compact() method in the MultivaluedDecisionDiagram class. This method for detecting and removing isomorphisms seems to have exponential time complexity, which becomes problematic for the largest instances, leading to out of memory errors.
Do you think it is possible to have a constructor to handle mdds as it is instead of trying to compact() them? It would call the method init(int[][] TRANSITIONS) but without calling the method compact(). Thus the call for compact() would be optionnal.
So far i've tried this on my local sources of choco-solver and it works for my large instances of MDD.
The text was updated successfully, but these errors were encountered:
I'm currently working on utilizing the
MultivaluedDecisionDiagram
class to handle an MDD I've constructed through knowledge compilation. This MDD is quite large, and I've already applied heuristics to minimize its size. However, I've encountered an issue with the mandatorycompact()
method in theMultivaluedDecisionDiagram
class. This method for detecting and removing isomorphisms seems to have exponential time complexity, which becomes problematic for the largest instances, leading to out of memory errors.Do you think it is possible to have a constructor to handle mdds as it is instead of trying to
compact()
them? It would call the methodinit(int[][] TRANSITIONS)
but without calling the methodcompact()
. Thus the call forcompact()
would be optionnal.So far i've tried this on my local sources of choco-solver and it works for my large instances of MDD.
The text was updated successfully, but these errors were encountered: