search

rpgoldman / europa-pso

Automatically exported from code.google.com/p/europa-pso
0 stars 0 forks source link

Provide constraint-based versions for all resource types #143

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Resources that use constraints instead of tokens have several advantages in 
terms of efficiency and simplicity.
Currently only Reusable has a constraint-based version (CBReusable), we need to 
provide constraint-based versions for the other Resource types: Reservoir and 
Unary.

Original issue reported on code.google.com by javier.barreiro@gmail.com on 5 Oct 2011 at 8:47

GoogleCodeExporter commented 8 years ago 
From Paul:

Will these new ones be in addition to the current types of resource?  So 
the old ones will still be available?

Can you detail the efficiency advantages?  Fewer timepoints?

Original comment by javier.barreiro@gmail.com on 6 Oct 2011 at 5:02

GoogleCodeExporter commented 8 years ago 
yes, this will be in addition to the current resource types, the same way that 
Reusable and CBReusable co-exist today.

main advantages of constraint-based resources off the top of my head:
efficiency in time and space:
  - less tokens, timepoints and propagation in the constraint network

simplicity: 
  - resource violations can be reported consistently with the native mechanism implemented in europa, they don't require special treatment
  - if we want to bring resources into bounds propagation, it can be done consistently within the constraint engine framework
  - search algorithms can be written more naturally/concisely if all violations are explicitly related to constraints

Original comment by javier.barreiro@gmail.com on 6 Oct 2011 at 5:12

GoogleCodeExporter commented 8 years ago

Original comment by javier.barreiro@gmail.com on 30 May 2012 at 5:26