code.org [mailto:users-boun...@gecode.org] On Behalf Of
> Mats Carlsson
> Sent: Thursday, August 11, 2016 09:28
> To: Guido Tack
> Cc: users@gecode.org
> Subject: Re: [gecode-users] fzn-gecode -mode gist and variable names
>
> Is there a way to _tell_ fzn-gecode to use free search
.se
From: users-boun...@gecode.org [mailto:users-boun...@gecode.org] On Behalf Of
Mats Carlsson
Sent: Thursday, August 11, 2016 09:28
To: Guido Tack
Cc: users@gecode.org
Subject: Re: [gecode-users] fzn-gecode -mode gist and variable names
Is there a way to _tell_ fzn-gecode to use free s
Is there a way to _tell_ fzn-gecode to use free search and to ignore any
search annotation?
On Thu, Aug 11, 2016 at 9:10 AM, Guido Tack wrote:
> The -f command line option is actually a no-op, it’s just there to
> maintain compatibility with the MiniZinc challenge (the specification is
> that yo
The -f command line option is actually a no-op, it’s just there to maintain
compatibility with the MiniZinc challenge (the specification is that you /may/
ignore the search annotation, not that you /must/…).
Cheers,
Guido
--
GUIDO TACK
Senior Lecturer
Information Technology
Thanks Guido. I need this in a context with free search, and by the way
another unfortunate thing about fzn-gecode is that any search annotation
seems to disable the -f flag.
So free search seems incompatible with Gist showing variable names... What
a pity. I hope that you will return to these poin
Hi Mats,
this is a limitation in the current fzn-gecode interpreter, we can only get
variable names for variables that are mentioned in a search annotation. So
currently the only workaround is to include all variables in some search
annotation (but of course I understand that that’s not necess
Hi, I have a problem with fzn-gecode -mode gist, Gecode trunk 14847,
MiniZinc 2.0.13.
Namely, anonymous variable names like var[123] get displayed instead of the
variable names of the .fzn file. Admittedly, the latter names are a bit
awkward, but at least they enable me to relate back to the names
