Hi, I guess you mean you want to use the specialised propagator, but from a MiniZinc model? That’s indeed missing right now, thanks for pointing it out.
As a workaround, you can use the cumulative constraint in MiniZinc but with capacity 1. The Gecode version will detect the special case and use the disjunctive propagator. I’ll add support for the MiniZinc disjunctive constraint for the next release of Gecode/FlatZinc. Cheers, Guido -- Guido Tack http://www.csse.monash.edu/~guidot/ > On 19 Sep 2015, at 4:31 am, Sebastian Kosch > <sebastian.ko...@mail.utoronto.ca> wrote: > > Hi, > > I'd like to use Minizinc's disjunctive constraint in Gecode, but no such > thing is provided. The gecode_schedule_unary constraint requires known > processing times and isn't an option. > > Now, there Gecode has a version of the unary constraint that has flexible > processing times, but also takes in an array of end times (which it then > doesn't propagate on, so I don't really get the point). I've created a > binding for it in the registry file and have given my model a dummy array of > end time variables, and that appears to work okay. > > Still, it'd be nice if Gecode supported Minizinc's disjunctive(var[], var[]) > out of the box. > > Is what I'm doing kosher, and could a "proper" version of this be added to > the trunk? > > Many thanks, > Sebastian > > _______________________________________________ > Gecode users mailing list > users@gecode.org > https://www.gecode.org/mailman/listinfo/gecode-users
_______________________________________________ Gecode users mailing list users@gecode.org https://www.gecode.org/mailman/listinfo/gecode-users
