SICStus, global constraint dispatcher 
Author Message
 SICStus, global constraint dispatcher

Hi,

does anybody know, if you can find out, what event has triggered the
global constraint? Specifically, from a list of domain variable changes,
which can trigger the global constraint, which one has changed? If there
is something indicating this, it would save a lot of computational work.

Thanks for your answers in advance,
  Ole



Mon, 09 Feb 2004 17:26:57 GMT  
 SICStus, global constraint dispatcher

Quote:

> does anybody know, if you can find out, what event has triggered the
> global constraint? Specifically, from a list of domain variable changes,
> which can trigger the global constraint, which one has changed? If there
> is something indicating this, it would save a lot of computational work.

Unfortunately, no such information is maintained.  If you are looking
for bound adjustment events, a simple idea is to store the current
bounds in the constraint's state.  When it wakes up, compare for each
variable the saved old bounds with the current ones.

--Mats Carlsson



Mon, 09 Feb 2004 20:59:21 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Printing clp(FD) constraints in SICStus

2. SICStus users and the SICStus module system

3. New gf dispatcher for d2c

4. Op-code dispatcher

5. null ranges and index constraints (was constraint error question)

6. Extend/Embed Python Method table Dispatcher

7. CFP - A special issue of the Constraints journal on Constraint Agents

8. tcltest::test -constraints <constraint with ::>

9. Is global really global.

10. global or not global?

11. Sicstus, is it possible toI clear the constraint store whithout backtracking?

12. SICStus Prolog Call Interface for Dolphin

 

 
Powered by phpBB® Forum Software