v2.3.1

Bug fix release of SATFC 2.3

Fixes an issue with the previous assignment decorator check not accounting for possible domain modifications

v2.3

• Default portfolio is now 8 cores
• Host of bug fixes

v2.2

• Mainly updates to SATFCServer, which is now more memory efficient

v2.0.1

This is a bug fix release of SATFC 2.0

• Fixed bug where interference constraints were not being loaded properly by the secondary verifier
• Fixed bug where the RTLD_LOCAL flag was being set to an incorrect value on mac.

v2.0

New release of SATFC adding SATenstein

v1.8-BETA

• ADJ+2 and ADJ-2 constraints
• Enforce arc consistency as a form of preprocessing
• Expanding neighbourhood UNSAT presolver
• Identify conditionally underconstrained stations
• Improve underconstrained station finding heuristic
• Upgrade to clasp 3.1.3

v1.7.1

• New required command line parameter for the server, constraint.folder, that tells the server where all of the data folders are so that it can properly size cache entries
• Upgraded to clasp 3.1.2

v1.7

• New feature, parallel portfolios, allow SATFC to execute multiple solvers in parallel, returning a result as soon as any solver succeeds. Previous versions of SATFC applied each solver sequentially.
• Enhanced the presolver technique to look beyond a station's immediate neighbours

v1.6

• Upgrade from clasp version from 2 to 3, along with new better performing configurations.
• The SATFCserver now has a clever clean up procedures to prune away unnecessary entries if the cache becomes too big.
• The cache is now updated on the fly. This means instances solved are immediately accessible to future cache queries (improving performance), and the cache server does not need to be restarted to have access to new data (improving usability).

v1.5

• New feature, containment cache, that uses previously solved problems to solve new, related problems. Our experiments with this feature show that it provides significant performance increase, not only by taking care of problems that are seen often (e.g. from very similar auction runs), but also improving solving time of new, unseen problems. This cache is implemented as a standalone server, the SATFCserver, to allow multiple SATFC solvers to use the same cache and reduce memory overhead. This server in turn uses redis as its backbone cache data structure.