Download the latest version of VEDA-FE (45828) and VEDA-BE (492014)

Veda Application Installation guide


Execution Errors after starting from Scratch
#1
Dear All,

Please let me know about the errors as I am unable to find the causes. The model before starting from scratch is working well.
Reply
#2
Tanzeel,

Please post the *.LST file.
Reply
#3
(14-11-2019, 07:12 PM)Vikrant Wrote: Tanzeel,

Please post the *.LST file.


I don't know that what's happening here. I can't attach the *.LST file here.


Attached Files
.docx   veda lst.docx (Size: 209.11 KB / Downloads: 2)
Reply
#4
Lightbulb 
I think at least *.TXT, *.DOC*, *.XLS* and *.ZIP files can be directly uploaded. For uploading other files, like listing files, I would suggest to ZIP-compress the file(s) first, and then upload the ZIP file. The size of a listing file will be much smaller when zipped.
Reply
#5
(14-11-2019, 10:52 PM)Antti-L Wrote: I think at least *.TXT, *.DOC*, *.XLS* and *.ZIP files can be directly uploaded. For uploading other files, like listing files, I would suggest to ZIP-compress the file(s) first, and then upload the ZIP file. The size of a listing file will be much smaller when zipped.


Right!

Please check it.


Attached Files
.zip   BAU-testb.zip (Size: 27.25 KB / Downloads: 0)
Reply
#6
(15-11-2019, 12:29 AM)Tanzeel Wrote:
(14-11-2019, 10:52 PM)Antti-L Wrote: I think at least *.TXT, *.DOC*, *.XLS* and *.ZIP files can be directly uploaded. For uploading other files, like listing files, I would suggest to ZIP-compress the file(s) first, and then upload the ZIP file. The size of a listing file will be much smaller when zipped.


Right!

Please check it.


Thanks. Adjusted now. Any good reference to debug model from LST file.
Reply
#7
Hi. The listing file tells us that the error is the model being "unbounded or infeasible". In addition, it tells that you have some input data errors.  These two issues could be either linked together or not. Anyway, you should correct the errors in your input data, shown at the top of the file (lines 20–90).

If your model remains infeasible, you can find the infeasibilities by enabling the Cplex Feasibility Relaxation option (feasopt 1), or by enabling the infeasibility finder option (iis 1).  See the Cplex manual included in your GAMS distribution. I am not sure how you could best diagnose an unbounded condition with Cplex.

Anyway, if the model was earlier running ok, I think you should best diagnose the problem by comparing the data only GDX files between the earlier run and the new failing run, to find the crucial differences in your input data, which are causing the problem.
Reply
#8
(15-11-2019, 08:04 PM)Antti-L Wrote: Hi. The listing file tells us that the error is the model being "unbounded or infeasible". In addition, it tells that you have some input data errors.  These two issues could be either linked together or not. Anyway, you should correct the errors in your input data, shown at the top of the file (lines 20–90).

If your model remains infeasible, you can find the infeasibilities by enabling the Cplex Feasibility Relaxation option (feasopt 1), or by enabling the infeasibility finder option (iis 1).  See the Cplex manual included in your GAMS distribution. I am not sure how you could best diagnose an unbounded condition with Cplex.

Anyway, if the model was earlier running ok, I think you should best diagnose the problem by comparing the data only GDX files between the earlier run and the new failing run, to find the crucial differences in your input data, which are causing the problem.


Thank You Antti-L.

I check this workflow more closely. As now, I am doing all these pure manually. Relaxing constraints one by one to resolve in-feasibility rather to do systematic debugging. It is really seem hard to find "Presolve found the problem infeasible or unbounded". It takes a lot of time. I check these options.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)