Subject: How to prevent VEDA from generating vd-files during model runs?

[KristofferEML]

Hi,

I know VEDA has an option to automatically delete vd-files after solving a model, but I'm wondering if there's a way to prevent VEDA from writing these files in the first place.

Background: I'm running large parametric scenarios where I don't need the vd-files for reporting purposes. The overhead from writing and then deleting these files is becoming significant.

What I'm looking for: Ideally, I'd like a reporting option or setting that removes the following line from the vt_run-file:

Code:

GDX2VEDA GAMSSAVE\%$case_name% ..\..\GAMS_SrcTIMES.v4.9.0\times2veda.vdd %$vd_file_name%

Has anyone found a clean way to accomplish this, or does anyone know if such an option exists in VEDA's configuration?

Thanks for any insights!

Best,

Kristoffer

[Antti-L]

For a quick workaround, I think you could just add the following command into vtrun with cmdf_top :
  echo @echo off > GDX2VEDA.CMD
Then GDX2VEDA would execute that cmd file and would do nothing. 

[AKanudia]

why did you call this a "workaround" Antti? This should be the recommended way for disabling on a temporary basis. For longer-term and widespread application, I guess one can write something in the vdd file that would disable the reporting step?

[Antti-L]

Well, it has a drawback that may be significant:  The vtrun script is in this case terminated with that GDX2VEDA execution (because it is without CALL).  And therefore, if you have added some cmdf_bot commands, they would in this case not be executed.  Actually, it might well be that KristofferEML uses such additional cmdf_bot commands...  To overcome that, one might thus need to insert those additional commands into that GDXVEDA.CMD if using this workaround.

This problem would not exist if VEDA would use CALL GDX2VEDA instead of just GDX2VEDA.  Then the control would be returned to vtrun after executing GDX2VEDA.

[KristofferEML]

Well, it has a drawback that may be significant:  The vtrun script is in this case terminated with that GDX2VEDA execution (because it is without CALL).  And therefore, if you have added some cmdf_bot commands, they would in this case not be executed.  Actually, it might well be that KristofferEML uses such additional cmdf_bot commands...  To overcome that, one might thus need to insert those additional commands into that GDXVEDA.CMD if using this workaround.

This problem would not exist if VEDA would use CALL GDX2VEDA instead of just GDX2VEDA.  Then the control would be returned to vtrun after executing GDX2VEDA.

Thank you Antti. You're absolutely right - I do rely on cmdf_bot to execute a timesreport GAMS script, so the echo @echo off > GDX2VEDA.CMD workaround isn't viable for my use case.

@Amit, would it be possible to implement CALL GDX2VEDA instead of just GDX2VEDA as Antti suggested?

An alternative solution that works is to rename GDX2VEDA.exe in the GAMS library, then the vtrun.cmd just skips the step as it cannot find GDX2VEDA.exe.