[Bug]: EarlySystemExit: 1

[ladderup]

Is there an existing issue for this?

• I have searched the existing issues.

What happened?

OMOTES calculation stop after 23min.

Solving report
Status Time limit reached
EarlySystemExit: 1

Steps to reproduce the problem

attached EDSLfile: RDH_P.txt

What should have happened?

Power of 'producers' should have been 'optimized'.

What browsers do you use to access the UI?

Google Chrome

Additional information

No response

[samvanderzwan]

I checked, but I think you have reached the timeout limit which has been set to avoid jobs to run for a to long time and taken up to much resources. The model is quit big, see:

@KobusVanRooyen wha are your though on this?

[KobusVanRooyen]

@samvanderzwan since you have already tried to run this can you attach the log file please?

[samvanderzwan]

I did not run it, I only opened the model, and my first though was ooh this is a big model.

[KobusVanRooyen]

@samvanderzwan I will have to run it then, because there are several time limits: a couple in MESIDO but also in OMOTES backend.

[ladderup]

I'm not use if it will work.
Good change it will stole at some misplace asset...

[KobusVanRooyen]

@ladderup can you share the log for when you got this error?

[ladderup]

I'm lost de original file (my computer died)....
I also deleted de fail run from de OMOTES server.....

But i'm rerunning the file RDH_P.txt right now.

[ladderup]

Run details.txt

[KobusVanRooyen]

@ladderup and @samvanderzwan yes this is a big network. I was able to optimize this network locally with a commercial solver (soon to be available in DTK), but it is not possible with the HIGHS open source solver (currently being used in DTK) even if I increase the time limits (6x current settings) which are currently causing the system exit. @samvanderzwan please advise? Should we wait for the commercial solver or spend time now on trying to see if this can be solved with the open source solver?

[KobusVanRooyen]

@ladderup and @samvanderzwan It is now possible to optimize this network with the new solver in the DTK test environment. As mentioned in the email that has been sent to all involved.