diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2020-12-14 00:35:53 -0800 |
---|---|---|
committer | Tamara Dahlgren <dahlgren1@llnl.gov> | 2021-02-17 17:07:25 -0800 |
commit | 27f6b3df9254b44777ec25f05dac2cb6203ee3f1 (patch) | |
tree | f71f0a3527b2a6a194a26122c71fdc17e5dcac0e /.gitignore | |
parent | 802c5bdff7b32e425514f25a7ab55c2df5aa5b83 (diff) | |
download | spack-27f6b3df9254b44777ec25f05dac2cb6203ee3f1.tar.gz spack-27f6b3df9254b44777ec25f05dac2cb6203ee3f1.tar.bz2 spack-27f6b3df9254b44777ec25f05dac2cb6203ee3f1.tar.xz spack-27f6b3df9254b44777ec25f05dac2cb6203ee3f1.zip |
concretizer: remove clingo command-line driver (#20362)
I was keeping the old `clingo` driver code around in case we had to run
using the command line tool instad of through the Python interface.
So far, the command line is faster than running through Python, but I'm
working on fixing that. I found that if I do this:
```python
control = clingo.Control()
control.load("concretize.lp")
control.load("hdf5.lp") # code from spack solve --show asp hdf5
control.load("display.lp")
control.ground([("base", [])])
control.solve(...)
```
It's just as fast as the command line tool. So we can always generate the
code and load it manually if we need to -- we don't need two drivers for
clingo. Given that the python interface is also the only way to get unsat
cores, I think we pretty much have to use it.
So, I'm removing the old command line driver and other unused code. We
can dig it up again from the history if it is needed.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions