Suite sc11-r50
-----------------------------------------------------------------------------------------------------------
| Run | solved | sat | unsat | unknown | time | utime | stime |
-----------------------------------------------------------------------------------------------------------
| g768l | 29 | 15 | 14 | 21 | 1410.94s | 1387.34s | 0.00 s |
-----------------------------------------------------------------------------------------------------------
| ps | 28 | 14 | 14 | 22 | 1567.51s | 1555.18s | 0.00 s |
-----------------------------------------------------------------------------------------------------------
../suites/sc11-r50: ps v g768l
★ /
★
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/ ☆ ☆
/
/
/
/ ☆
/
/ ☆ ☆
/ ☆ ☆
/ ☆
★ /
/
★ ☆ ☆
★ / ☆ ☆
★
--------------------------------------------------------------------------------
★ - ps wins
☆ - g768l wins
Thanks.Out of curiosity, are you using sat solvers in visual effects pipelines?
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Sat, 30 Jul 2016, 2:22 AM Scott Cotton <w...@iri-labs.com> wrote:Thanks.Out of curiosity, are you using sat solvers in visual effects pipelines?I was using it for a new version of the package dependency resolver component of our environment management system.I was able to model the entire "repository" of software package descriptions and their dependencies. Then add the specific package selections for an environment as constraints and resolve that back into the full list of needed packages.The useful bit in pigosat is that I can have it generate the cause of the failure to solve and convert that back into human readable reporting.
On Sat, 30 Jul 2016, 2:22 AM Scott Cotton <w...@iri-labs.com> wrote:Thanks.Out of curiosity, are you using sat solvers in visual effects pipelines?I was using it for a new version of the package dependency resolver component of our environment management system.I was able to model the entire "repository" of software package descriptions and their dependencies. Then add the specific package selections for an environment as constraints and resolve that back into the full list of needed packages.The useful bit in pigosat is that I can have it generate the cause of the failure to solve and convert that back into human readable reporting.
Scott
Neat, maybe a bit like sat4j does in eclipse dependency management?
For generating the cause of a failure, do you mean "failed assumptions" in picosat speak orunsat core or some other feature (proofs, etc)?