Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
sat4j
sat4j
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 45
    • Issues 45
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • SAT4J
  • sat4jsat4j
  • Issues
  • #115

Closed
Open
Opened Oct 21, 2013 by Daniel Le Berre@leberre
  • Report abuse
  • New issue
Report abuse New issue

Fix issue in Minisat Expensive Simplification

The minisat expensive simplification procedure has been fixed recently to correct a bug that could make the solver spend too much time during conflict minimization. The issue was raised by Allen Van Gelder in a paper (SAT'11 ?). The code of minisat available in github contains the fix. We might want to implement our own.

It might be the case that such issue arrises when using cardinality constraints. Need to investigate further.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
3
Labels
core prio=Major type=Improvement
Assign labels
  • View project labels
Reference: sat4j/sat4j#115