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 necessarily what you want to do). I had a look at fixing this at some point, but it turned out to be more than just a few lines of code so I had to leave it for the time being.
Cheers, Guido -- GUIDO TACK Senior Lecturer Information Technology Monash University Level 6, Room 6.40, Building H, Caulfield Campus 900 Dandenong Road Caulfield East VIC 3145 Australia T: +61 3 9903 1214 E: [email protected] <mailto:[email protected]> http://www.csse.monash.edu/~guidot/ <http://www.csse.monash.edu/~guidot/> > On 19 Jul 2016, at 6:39 PM, Mats Carlsson <[email protected]> wrote: > > 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 of the > MiniZinc model. But I have no idea how to map the var[...] names to the > names of the .fzn file. I have tried to edit the .fzn file in various ways to > make Gist use its names, but it has not helped. Is there some work-around? > > See the attachment for an example. > > -- > Mats Carlsson, SICS > www.sics.se/~matsc > <http://www.sics.se/~matsc><tree.pdf>_______________________________________________ > Gecode users mailing list > [email protected] > https://www.gecode.org/mailman/listinfo/gecode-users
_______________________________________________ Gecode users mailing list [email protected] https://www.gecode.org/mailman/listinfo/gecode-users
