No results after successful model run

[JohannesR]

I already installed all VEDA 2.0 and GAMS Studio but unfortunately each time that I try to run a model and open the results tab the results appear to be empty there and when looking in the WrkTMS folder there is no .vd file created. This happens for both the demo_models and our internal models. Unfortunately, I am not able to share data outside of my organization but I will try to fix that and attach the demoS_002 model I am running and also the WrkTIMES result.

In the meantime, is that a problem that you had encountered before and there might be a common fix?

Attached you can find both the run file and the WrkTIMES folder.

  WrkTIMES_DemoS_002.zip (Size: 447.31 KB / Downloads: 6)

[Antti-L]

Seems to me that GDX2VEDA is not executed at all. What happens if you open a command prompt window and try to run GDX2VEDA (by typing GDX2VEDA on the command line)?

[JohannesR]

By the way, I am running the model online on GAMS Engine. Attached on the original post is the result when running GDX2VEDA

[Antti-L]

> By the way, I am running the model online on GAMS Engine.

Aha, ok, then it is something I cannot help with, but I hope the KanOrs support staff can.

But as it seems you have GAMS installed also locally, you could generate the results locally (manually).

[JohannesR]

Our internal model is unfortunately too large to run locally on my machine, and it’s encountering the same issue as the demo. That’s why I’m hoping the same solution will apply for both

[Antti-L]

Yes, I understand, but I meant that you could just run GDX2VEDA locally, not the model. I just generated the results myself from your Demos_002 run, as you had the GDX file included. And then you could load the results into VEDA.

So, assuming that you obtain the GDX file also for the big model runs from the Online GAMS Engine, you could run GDX2VEDA locally to generate the model results *.VD* files for VEDA (as a workaround, until you get a better solution).

[JohannesR]

When I run gdx2veda there is no .vd file being produced which, to my understanding, would include the results, right?

[Antti-L]

When I run gdx2veda with the GDX file you had in the ZIP file, I am getting the *.vd* files produced, which I have also verified to include the results.

So, if the GDX file you had in the ZIP file was from a GAMS Engine run, this would work as a workaround.

[JohannesR]

The GDX file was from a GAMS Engine run, but when I run gdx2veda it does not produce any vd files. For none of gdx files I have tried it with so far

[Antti-L]

Well, then I think there must be something wrong with your command line.

It should be like this (paths included where necessary):
>  gdx2veda casename.gdx vdd-filename vd-filename

[Ravinder]

Dear Johannes,

Please update your TIMES source code to the latest version via Tools → Update TIMES Code.

After completing the update, ensure that the latest TIMES source code is selected both in the GAMS root settings and in your case settings. Then, attempt to solve the case and let us know whether the issue is resolved.

[JohannesR]

Hi, I have tried these steps and it unfortunately did not resolve the issue as we are running it via the online GAMS engine.

[JohannesR]

Forget the previous post, that did fix it! Thank you!

[Antti-L]

Good to hear!   
But I remain puzzled if you were still not able to generate the *.vd files from the GDX by running gdx2veda, was that really so?  Or does that work now as well, after updating the TIMES code?

[Ravinder]

Good to hear!   
But I remain puzzled if you were still not able to generate the *.vd files from the GDX by running gdx2veda, was that really so?  Or does that work now as well, after updating the TIMES code?

Dear Antti,

We were also not able to generate the *.vd files by running vtrun.cmd (contains GDX2VEDA command) with the older TIMES source code, and thus suspected that JohannesR was facing the same problem.

We were getting the following error.




After updating Times Source to the latest version, the *.vd files were generated successfully by running vtrun.cmd.



Hope this answers your questions.