How to adjust the VTRUN.cmd in Parametric Runs

[philip]

Dear All, 
 
I would like to perform parametric runs with different CPLEX options. 
To this end I try to instruct the VTRun.cmd to create an option file by using CmdF_top attribute which before the GAMS call will add something like:
 
timeout /t 10 /nobreak
REM create/overwrite cplex.opt in current working directory for Parametric
echo * BA120-7 > cplex.opt
echo advind 0 >> cplex.opt
echo baralg 1 >> cplex.opt
echo barcrossalg 2 >> cplex.opt
echo barepcomp 1e-11 >> cplex.opt
 
for this purpose.
 
I have tested the use CmdF_top with a regular scenario and works fine, however it doesn’t work in parametric scenario, 
as in all cases the VTRun.cmds are not aware of any additional line.
 
Is this behavior expected or do I miss something?
Is there an alternative way to perform Cplex options parametric runs?
I attach my parametric scenario.
 
Thank you
Philip Siakkis

[Antti-L]

I am not a VEDA developer, but as there is no response from VEDA support, I can maybe suggest trying to use SFCmd_top / SFCmd_bot instead of CmdF_top. Just write the commands creating the cplex.opt file into the parametric scenario DD file, using GAMS syntax, e.g. the following lines:

  $onecho > cplex.opt
  * BA120-7
  advind 0
  baralg 1
  barcrossalg 2
  barepcomp 1e-11
  $offecho

I think it should work like this, just the syntax being a bit different.
I tested it, but only directly with GAMS (modifying a parscen DD file), and that worked well. So, what would remain to be tested is that using SFCmd_top / SFCmd_bot will indeed write those lines out.

[Antti-L]

Ahh... it appears that neither SFCmd_Top / SFCmd_Bot nor CmdF_Top / CmdF_Bot appears to work with Scen_Par* files, but RFCmd_BOT does work. Actually, I had made that conclusion already earlier on the Forum, but had forgotten about that. But anyway, I tested with RFCmd_BOT now, and it worked fully as expected, and like I understood you were wishing. And Cplex did indeed use the cplex.opt written out by those GAMS statements for each parametric case.

[philip]

Ahh... it appears that neither SFCmd_Top / SFCmd_Bot nor CmdF_Top / CmdF_Bot appears to work with Scen_Par* files, but RFCmd_BOT does work. Actually, I had made that conclusion already earlier on the Forum, but had forgotten about that. But anyway, I tested with RFCmd_BOT now, and it worked fully as expected, and like I understood you were wishing. And Cplex did indeed use the cplex.opt written out by those GAMS statements for each parametric case.

Dear Antti,
Thank you for your suggestions.
RFCmd_BOT works fine and the user must be careful when ordering the lines to be added.
I can verify that RFCmd_DD works also fine in parametric runs.

Please allow me to share with other users a Parametric scenario template for using diferrent cplex options.

I still cannot introduce a timebreak between parscen runs, but I hope that in the future CmdF_top will work in parscen mode.

Thank You
Philip

[AKanudia]

https://www.dropbox.com/scl/fi/xp97zu9agro1oklmltotr/Veda2.0_localhost_4.3.2.1.zip?rlkey=44wbsm95ck3x0a7384cy8kh0p&dl=0

This version supports all cmd attributes in parscen.

it will be released as the next production version soon.