ApproxMCv3 is a state-of-the-art approximate model counter utilizing an improved version of CryptoMiniSat to give approximate model counts to problems of size and complexity that were not possible before. This work is by Kuldeep Meel and Mate Soos, as published in AAAI-19. A large part of the work is in CryptoMiniSat here.
ApproxMC handles CNF formulas. If you are instead interested in DNF formulas, visit our DNF counter DNFApproxMC.
If you don't have or don't know what an independent set is, first run our MIS tool:
docker run --rm -v `pwd`/formula.cnf:/in msoos/mis --timeout 300 /in
[...]
** Copy-paste the following line in the top of your CNF for ApproxMC **
c ind 3 4 7 8 10 11 14 17 18 26 30 35 36 39 42 47 60 62 67 0
Then copy-paste that line into your CNF.
Then run the updated CNF through approxmc:
cat formula.cnf | docker run --rm -i -a stdin -a stdout msoos/approxmc
To build on Linux, you will need the following:
sudo apt-get install build-essential cmake
sudo apt-get install zlib1g-dev libboost-program-options-dev libm4ri-dev
Then, build CryptoMiniSat and ApproxMC:
git clone https://github.com/msoos/cryptominisat
cd cryptominisat
mkdir build && cd build
cmake -DUSE_GAUSS=ON ..
make
sudo make install
cd ../..
git clone https://github.com/meelgroup/approxmc/
cd approxmc
mkdir build && cd build
cmake ..
make
sudo make install
First, you must translate your problem to CNF and just pass your file as input to ApproxMC. Voila -- and it will print the number of solutions of the given CNF formula.
For some applications, one is not interested in solutions over all the variables and instead interested in counting the number of unique solutions to a subset of variables, called sampling set. ApproxMC allows you to specify the sampling set using the following modified version of DIMACS format:
$ cat myfile.cnf
c ind 1 3 4 6 7 8 10 0
p cnf 500 1
3 4 0
Above, using the c ind
line, we declare that only variables 1, 3, 4, 6, 7, 8 and 10 form part of the sampling set out of the CNF's 500 variables 1,2...500
. This line must end with a 0. The solution that ApproxMC will be giving is essentially answering the question: how many different combination of settings to this variables are there that satisfy this problem? Naturally, if your sampling set only contains 7 variables, then the maximum number of solutions can only be at most 2^7 = 128. This is true even if your CNF has thousands of variables.
For most applications, we are want all solutions to the problem. To do this, you need to use the MIS tool to find a small independent set of variables to your CNF. For example, for formula.cnf
we can do:
docker run --rm -v `pwd`/formula.cnf:/in msoos/mis --timeout 300 /in
[...]
** Copy-paste the following line in the top of your CNF for ApproxMC **
c ind 3 4 7 8 10 11 14 17 18 26 30 35 36 39 42 47 60 62 67 0
You must copy the line starting with c ind ...
to the top of your CNF before running ApproxMC.
In our case, the maximum number of solutions could at most be 2^7=128, but our CNF should be restricting this. Let's see:
$ approxmc --seed 5 myfile.cnf
c ApproxMC version 3.0
[...]
c CryptoMiniSat SHA revision 17a1aed4956848404e33d514eef257ca1ed2382b
c CMS is MIT licensed
c Using code from 'When Boolean Satisfiability Meets Gauss-E. in a Simplex Way'
[...]
[appmc] using seed: 5
[appmc] Sampling set size: 7
[appmc] Sampling set: 1, 3, 4, 6, 7, 8, 10,
[appmc] Using start iteration 0
[appmc] [ 0.00 ] bounded_sol_count looking for 73 solutions -- hashes active: 0
[appmc] [ 0.01 ] bounded_sol_count looking for 73 solutions -- hashes active: 1
[appmc] [ 0.01 ] bounded_sol_count looking for 73 solutions -- hashes active: 0
[...]
[appmc] FINISHED ApproxMC T: 0.04 s
[appmc] Number of solutions is: 48 x 2^1
ApproxMC reports that we have approximately 96 (=48*2)
solutions to the CNF's independent support. This is because for variables 3 and 4 we have banned the false,false
solution, so out of their 4 possible settings, one is banned. Therefore, we have 2^5 * (4-1) = 96
solutions.
ApproxMC provides so-called "PAC", or Probably Approximately Correct, guarantees. In less fancy words, the system guarntees that the solution found is within a certain tolerance (called "epsilon") with a certain probability (called "delta"). The default tolerance and probability, i.e. epsilon and delta values, are set to 0.8 and 0.2, respectively. Both values are configurable.
Please click on "issues" at the top and create a new issue. All issues are responded to promptly.
If you use ApproxMC, please cite the following papers: AAAI19 and IJCAI16.
ApproxMC builds on a series of papers on hashing-based approach: Related Publications
The benchmarks used in our evaluation can be found here.
The old version, 2.0 is available under the branch "ver2". Please check out the releases for the 2.x versions under GitHub releases. Please read the README of the old release to know how to compile the code. Old releases should easily compile.