Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected empty set of conflict terms #46

Open
balasub opened this issue Jul 21, 2023 · 0 comments
Open

Unexpected empty set of conflict terms #46

balasub opened this issue Jul 21, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@balasub
Copy link

balasub commented Jul 21, 2023

The following unsolvable partial model generates an empty set of unsat terms.

domain Mapping
{
Component ::= new (id: Integer, utilization: Real).
Processor ::= new (id: Integer).
Mapping ::= new (c: Component, p: Processor).

// The utilization must be > 0
invalidUtilization :- c is Component, c.utilization <= 0.

badMapping :- p is Processor,
s = sum(0.0, { c.utilization |
c is Component, Mapping(c, p) }), s > 100.

conforms no badMapping, no invalidUtilization, invalidUtilization.

}

partial model pm of Mapping
{
c1 is Component(0, x).
c2 is Component(1, y).
p1 is Processor(0).
Mapping(c1, p1).
Mapping(c2, p1).
}

@balasub balasub added the bug Something isn't working label Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant