summaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorMassimiliano Culpo <massimiliano.culpo@gmail.com>2023-04-03 19:23:29 +0200
committerGitHub <noreply@github.com>2023-04-03 19:23:29 +0200
commit9d681008914f33ca6a09c623906caa707b7f597b (patch)
tree7e08376591fc52509b5bb1c9ca86d4652732a177 /NOTICE
parentebffc53b93d37815674988d2f438fe810a554c3a (diff)
downloadspack-9d681008914f33ca6a09c623906caa707b7f597b.tar.gz
spack-9d681008914f33ca6a09c623906caa707b7f597b.tar.bz2
spack-9d681008914f33ca6a09c623906caa707b7f597b.tar.xz
spack-9d681008914f33ca6a09c623906caa707b7f597b.zip
Rework error handling within the ASP logic program (#36536)
* Reduce effort on grounding by employing cardinality constraints If we use a cardinality constraint instead of a rule using pair of values, we'll end up grounding 1 rule instead of all the possible pair combinations of the allowed values. * Display all errors from concretization, instead of just one If clingo produces multiple "error" facts, we now print all of them in the error message. Before we were printing just the one with the least priority. Consolidate a few common patterns in concretize.lp to ensure that certain node attributes have one and only one value assigned. All errors are displayed, so use a single criterion instead of three. * Account for weights in concretize.lp To recover the optimization order we had before, account for weights of errors when minimizing. The priority is mapped to powers of 10, so to effectively get back the same results as with priorities.
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions