Hi Gustavo, modification events are really sets of modifications, e.g. if you have only a lower bound modification the event is ME_SET_GLB, for only upper bound it's ME_SET_LUB, but if both have been modified you get ME_SET_BB.
You guessed correctly: The testSetEventLB function returns true if the argument event contains a lower bound modification (so it could be ME_SET_GLB, ME_SET_BB, ME_SET_CGLB or ME_SET_CBB). The versions with multiple arguments test whether any of them contains a lower bound modification (the implementation computes the union of the events and then does the check). Cheers, Guido On 20 Aug 2014, at 12:33 am, Gustavo Gutierrez <gustavo.ggutier...@gmail.com> wrote: > Dear all, > > I am trying to write a propagator and I really would like to take advantage > of the modification event information offered by the geocode kernel in the > respective argument to the propagate method. To that end, I am looking at set > propagators as an example. In concrete I am looking at the code of the > intersection propagator in inter.hpp. > > That implementation calls testSetEventLB defined in common.hpp. My question > is concrete: does this function returns true when the modification event > passed as parameter signals a modification of the lower bound?. My intuition > from its definition and the internal functions it uses tell me so but I would > like to corroborate it with you. > > There are other testSetEvent* that take a different number of arguments (all > of them being modification events). For example, testSetEventLB with two > arguments. Does this one returns true if any of the two events imply > modification to the lower bounds? > > Best regards, > -- > Gustavo Gutierrez > _______________________________________________ > 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
