Sébastien Mouthuy wrote:
I printed id's of these branching and it happens that an instance of
BrSF has the same id as BrCl.
I think I've found the problem, and it was a bug in our code. It will
be fixed in Gecode 2.0, but for the time being, you can use the patch
attached to this mail (it'
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Sébastien Mouthuy
Sent: Tuesday, May 29, 2007 12:24 PM
To: Guido Tack
Cc: [EMAIL PROTECTED]
Subject: Re: [gecode-users] order in calls to status and commit...
Le mardi 29 mai 2007 à 13:07 +0200, Guido Tack a écrit
ively in Gecode).
Christian
--
Christian Schulte, http://www.imit.kth.se/~schulte/
-Original Message-
From: Luis Quesada [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 1:27 PM
To: Sébastien Mouthuy
Cc: [EMAIL PROTECTED]; 'Guido Tack'; [EMAIL PROTECTED]
Subject: Re: [gecode-users]
Sébastien Mouthuy wrote:
I have another question: posting propagators in the commit function of
one Branching is acceptable ? The fact is that I would like to delay a
heavy propagator taht does not do a lot of pruning high in the search
tree, but is very useful down in the tree.
Could you plea
Le mardi 29 mai 2007 à 13:07 +0200, Guido Tack a écrit :
> Sébastien Mouthuy wrote:
>
> > I have one main branching, let's say BrSF. In the commit function of
> > BrSF, I sometimes post another branching, say BrCl.
> >
> > I printed id's of these branching and it happens that an instance of
> > Br
Sébastien Mouthuy wrote:
I have one main branching, let's say BrSF. In the commit function of
BrSF, I sometimes post another branching, say BrCl.
I printed id's of these branching and it happens that an instance of
BrSF has the same id as BrCl. I'm not using recomputation: c_d = 1,
a_d
= 100
gt;
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Sébastien Mouthuy
> Sent: Tuesday, May 29, 2007 12:44 AM
> To: Guido Tack
> Cc: [EMAIL PROTECTED]
> Subject: Re: [gecode-users] order in calls to status and commit...
>
D] On Behalf
Of Sébastien Mouthuy
Sent: Tuesday, May 29, 2007 12:44 AM
To: Guido Tack
Cc: [EMAIL PROTECTED]
Subject: Re: [gecode-users] order in calls to status and commit...
I found a related problem that seems annoying.
I have one main branching, let's say BrSF. In the commit function of Br
I also post some propagators inside the commit function. Is it ok ? I am
sure these propagators cannot fail when posting.
When I post propagators *and* branching in the same commit, I have the
problem I described before.
When I post branching *xor* propagators, the branching posted clones
forev
I found a related problem that seems annoying.
I have one main branching, let's say BrSF. In the commit function of
BrSF, I sometimes post another branching, say BrCl.
I printed id's of these branching and it happens that an instance of
BrSF has the same id as BrCl. I'm not using recomputation:
Sébastien Mouthuy wrote:
Could that be the problem ? Should B1 and B2 be two copies of a comman
instance of the branching ? I know descriptions and branchings use
id's.
could it be the problem ?
Hm, it shouldn't be the problem. If the branchings are always created
in the same order, the i
Le lundi 28 mai 2007 à 18:29 +0200, Guido Tack a écrit :
> Sébastien Mouthuy wrote:
>
>
> > Could you tell me what is exactly the order in which the functions
> > status and commit are called ?
>
>
> I presume you mean status and commit of a branching, right?
yes
>
> > For me it should be
>
Sébastien Mouthuy wrote:
Could you tell me what is exactly the order in which the functions
status and commit are called ?
I presume you mean status and commit of a branching, right?
For me it should be
call to status with space S. if it returns true, then copy S. let's
call
the copy Sc.
Hello,
I have one question related to the one I posted before (thank you for
the fast reply :) ).
Could you tell me what is exactly the order in which the functions
status and commit are called ?
For me it should be
call to status with space S. if it returns true, then copy S. let's ca
14 matches
Mail list logo
