Open GoogleCodeExporter opened 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
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
Original comment by javier.barreiro@gmail.com
on 30 May 2012 at 5:26
Original issue reported on code.google.com by
javier.barreiro@gmail.com
on 5 Oct 2011 at 8:47