Closed olejandro closed 6 months ago
Apologies for the delayed response. We were not able to reproduce the issue, which might have something to do with the regional settings of Windows. Can you please tell us the regional settings/timezone on the machine where you observed this issue?
To me what Olex reported looks very much like the timer had been reset to zero after 24 hrs (24 + 8:42 ≈ 33 hours), so a likely timer rollover issue. Could such a rollover be somehow caused by regional settings/timezone?
We've pinpointed the actual issue and devised a solution. It will be incorporated in the upcoming release.
Addressed in version 3.1.1.
Speaking of SolveTime reporting, it doesnt seem to ever show up in Veda when we run our models. Just updated to the new version (3.1.1.0) and it still isn't showing. See image below of two finished runs.
Apologies for any inconvenience caused. Could you kindly provide the logs and ".lst" file to us?
Speaking of SolveTime reporting, it doesnt seem to ever show up in Veda when we run our models. Just updated to the new version (3.1.1.0) and it still isn't showing. See image below of two finished runs.
We've revised how solveTime is displayed in the "Runs Status" window, now using the 'casename_run_log.txt' file instead of 'casename.lst' in version 3.1.1.0. This update is compatible with GAMS version 32 and later.
As you are using GAMS version 29, solveTime will not be displayed with the latest version (3.1.10). Your choices are to stick with the prior version (3.0.7.0) or upgrade GAMS to version 32 or newer.
Can you also comment what might be the reason for the missing ModelStatus, SolverStatus and ObjectiveValue in SDockweiler's screenshot? I assume they cannot be taken from the log file?
Hi Rahul
Thank you for the investigative work. Updated to version 37 and now everything seems to work out.
Cheers, Steffen
Currently the case manager reports SolveTime in HH:MM(?) format. What does it represent? I have a case where
08:42
SolveTime is reported, but looking at the job log file from GAMS I see ca. 33 hours reported as time to complete the job. Since the difference between the reported SolveTime and the value from GAMS is about 24 hours, could there be calculation error? Or is the difference due to something else being reported?