Re: [Choco-users] Two caveats that can turn into BIG BUGS

[Eric A. <am...@ev...>]

Hello Hadrien,

Thanks for your answers, episodes are getting
more and more interesting {;-)

I'll try the new jar asap.
It would be nice indeed to be able to check out=20
anonymously from CVS directly, to get last evolutions quickly.

About my contribution: I don't consider myself as being
knowledgeable enough to develop new constraints myself.
Maybe in the next months.
However, I may contribute right now to the documentation,
as I have struggled through the docs & api.
Some parts of the wiki could be developed for the dummy=20
first-time users.
Please give me your feeling about.

--Eric=20

=20
  ----- Original Message -----=20
  From: Hadrien=20
  To: Eric Amram ; cho...@li...=20
  Sent: Tuesday, May 23, 2006 9:40 AM
  Subject: Re: [Choco-users] Two caveats that can turn into BIG BUGS


  Hello,

  1/ pb.nth( IntVar index, ... ) --> index must be from makeEnumIntVar() =
!!

  Yes ! BoundConsistency is not implemented on the element constraint. =
But it seems to make=20
  more sens in ArcConsistency. Anyway I have added a clear error message =
...=20

  2/ pb.getSolver().attachGoal() is protected. --> Should be public !!

  Yes ! thank you, it is now public

  3/ Is the SourceForge CVS the main repository ?
  I don't find the Solver.setVerbosity() that is documented is the user =
guide...

  Yes sourceforge is the main repository. Let me send you the last jar =
privately until guillaume has published the new
  one and a guideline to checkout the cvsroot as an anonymous user. (He =
promised to do it tonight... :))

  4/ Last but not least: how can I help to contribute to this great =
project ?

  For the moment, the easiest way to contribute is to implement =
constraints. You can send us the code of a constraint and a set of tests =
so we can add them with the corresponding api in Problem. If you want =
then to do more, francois may give you the developper status !


  Hadrien
    ----- Original Message -----=20
    From: Eric Amram=20
    To: cho...@li...=20
    Sent: Friday, May 19, 2006 6:52 PM
    Subject: [Choco-users] Two caveats that can turn into BIG BUGS


    Hi all,

    I would like to notify 2 caveats I've spotted (actually that
    made my code crash {:-((

    1/ pb.nth( IntVar index, ... ) --> index must be from =
makeEnumIntVar() !!

       It is said to take a IntVar, but if you provide a variable
       from  pb.makeBoundIntVar, it crashes :
       IntervalIntDomain.getIterator  throws an exception.
       That was a tough bug to find...

    2/ pb.getSolver().attachGoal() is protected. --> Should be public !!

       So the only mean to set the FIRST goal of the solver
       is to setVarSelector / setValSelector / setValIterator
       before the generateSearchSolver()
       That's a little bit tricky, and prevent from using anything else =
than AssignVar.

       The wiki doc "Define your own tree search" is not in sync with =
the code
       (it uses attachGoal).


    Hope it helps to make Choco better !!

    --Eric