Originally posted by: SystemAdmin

[dant said:]

Hi,

I've just generated an LP file from ILOG OPL. However, some of the decision variables have '#' while other don't - see example below. Is this a problem? What does it mean?

id3688: - 10 x#4#1#0 - 10 x#5#1#0 - 10 x#6#1#0 - 10 x#7#1#0 + l({1,1,3})(1)(1) <= 0<br />
Thanks.
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[afleischer said:]

Hi,

you could have a look at the Big map naming threshold setting in the documentation.
Below this limit OPL indexes are not kept and replaced by #numbers

Alex
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[afleischer said:]

PS:

I meant beyond this limit
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: dant

Hi...

Yes, I managed to get to this option. However for some reason I can't save the .ops file. That is, the save or save all option isn't available when I increase the map size.

I tried making some changes to the .mod file and clicking on save all. But the map size reverts to the original 100.

Can someone please, please tell me what's going on.

I am quite frustrated with OPL. This should be a simple matter, yet there's no clear solution. I couldn't find anything in the help files. The installation itself was quite a pain.
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: Didier Vidal

I happened to have this issue with parameters in former versions of OPL (I don't see this with OPL 6.3).
The solution was to hit the 'enter' key when the cursor is still in the field of the text field parameter to validate the change.

Didier.
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: dant

Hey Didier,

Thank you very much for replying. You don't know how much you've helped me ! It works now...
#DecisionOptimization
#OPLusingCPLEXOptimizer