Fix reference naming
This commit is contained in:
parent
2efce9ef96
commit
47dcc6e3bf
@ -540,7 +540,7 @@
|
||||
doi = {10.1016/j.artint.2012.04.001},
|
||||
}
|
||||
|
||||
@inproceedings{gokberk-2020-ess-incr,
|
||||
@inproceedings{kocak-2020-ess-incr,
|
||||
author = {G{\"{o}}kberk Ko{\c{c}}ak and {\"{O}}zg{\"{u}}r Akg{\"{u}}n and
|
||||
Nguyen Dang and Ian Miguel},
|
||||
title = {Efficient Incremental Modelling and Solving},
|
||||
|
@ -1101,7 +1101,7 @@ At its core, however, the \gls{rewriting} of \gls{ess-prime} works very differen
|
||||
For each concept in the language the \compiler{} intrinsically knows how to rewrite it for its target \solver{}.
|
||||
In particular, \glspl{decomp} for \constraints{} are not declared as predicates and functions in \gls{ess-prime}, but hard-coded in the compiler.
|
||||
|
||||
Recently, \textcite{gokberk-2020-ess-incr} have also presented Savile Row as the basis of a \gls{meta-optimization} toolchain.
|
||||
Recently, \textcite{kocak-2020-ess-incr} have also presented Savile Row as the basis of a \gls{meta-optimization} toolchain.
|
||||
The authors extend Savile Row to bridge the gap between the incremental assumption interface of \gls{sat} \solvers{} and the modelling language and show how this helps to efficiently solve pattern mining and optimization problems.
|
||||
Consequently, the usage of \gls{meta-optimization} in Savile Row reiterates the use of \gls{meta-optimization} algorithms in \cmls{} in general and the need for incremental bridging between the modelling language and the \solver{}.
|
||||
|
||||
|
Reference in New Issue
Block a user