-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Update v8.2.1 -> v8.3.0 or later broke flowsheet calculation in automation mode due to solver timeout #498
Comments
Hi @adwjpaul I run your code on my laptop with debian testing, I have segfault with following output: Click me
I think its a bug in mono. |
What is Debian testing? Debian 12 Bookworm was just released, so I am not sure what your system looks like. However: Does the code run using dwsim v8.2.1? Have you been able to run any python scripts using dwsim and Automation2? I see a lot of conda-related paths in your output, so your python environment is likely very different from mine. I made sure to deviate as little as possible from the official Debian repositories. For completenes' sake, here is the script I used for setting up dwsim:
|
@adwjpaul try using Automation3() and see what happens. It seems to be something related to the Python/C# interface. |
Yes, using Automation3 makes the whole thing work again. I must admit that I was not aware of Automation3, is Automation2 deprecated? |
@adwjpaul Automation() and Automation2() are based on the Classic and Cross-Platform UI versions respectively. Every time you create a new flowsheet using these interfaces, the whole GUI was being created in the background, but not shown to you. Slow and heavy on resources. Automation3() is designed to be GUI-less and consumes a minimal amount of memory. I'm not doing anything with Automation() and Automation2() anymore, to be honest. |
My python script using Automation2 to calculate a flowsheet under Linux works using v8.2.1, but hangs for v8.3.0, v8.3.5, v8.4.7 and v8.5.0 for a long time and then prints
The flowsheet calculates fine when opened in the cross-platform GUI in any version given above without any solver timeout issues. Looks like some solver setting is not initialised in automation mode which causes the solver to not converge.
To Reproduce
flowsheet_automation_bug.zip
before hanging indefinetely. The states printed are already in the flow sheet before calculation. Note the missing lines
and
compared to the v8.2.1 output.
Expected behavior
The script should work for all versions of dwsim.
Desktop (please complete the following information):
I am using dwsim under Debian 11.
`mono --version
Mono JIT compiler version 6.8.0.105 (Debian 6.8.0.105+dfsg-3.3~deb11u1 Sat Feb 18 21:26:37 UTC 2023)
but my feeling is that this is a true code bug and not an environment bug. If you need to setup a Linux test machine, I can provide you with a script that takes care of all the mono and python3 installation hassle.
The text was updated successfully, but these errors were encountered: