Opened 8 years ago
Last modified 5 years ago
#4221 new defect
OmOptim crashes after model selection
Reported by: | Owned by: | Hubert Thieriot | |
---|---|---|---|
Priority: | critical | Milestone: | Future |
Component: | OMOptim | Version: | v1.11.0 |
Keywords: | Cc: |
Description
OMOptim is still not usable.
1) Start OMOptim
2) Load Modelica
3) Load Model (.mo) - I load some of my models
4) Select problem - optimization
Crash!
Win 8.1, 64b
Change History (13)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:3 by , 7 years ago
Milestone: | 1.12.0 → 1.13.0 |
---|
Milestone moved to 1.13.0 due to 1.12.0 already being released.
comment:4 by , 7 years ago
Is there an obvious/quick fix for this? Otherwise, how far back does one have to go to get a working OmOptim to play around with?
comment:5 by , 7 years ago
We didn't even ship OMOptim as part of the 1.9.4 OM release on Linux (separate package then, but I think it was broken already at that time)? I think you need to go back to OM 1.8.1 for a tested OMOptim. It might be possible to set OPENMODELICAHOME and use some old OMOptim with a newer OpenModelica, but I think some of the internal API functions called by OMOptim and some parts might not fully work if you do that...
follow-up: 7 comment:6 by , 7 years ago
And yes, I think there was basically no real maintenance of the code since 2011 except just making it compile (there are no tests for OMOptim in the testsuite).
comment:7 by , 7 years ago
Replying to sjoelund.se:
And yes, I think there was basically no real maintenance of the code since 2011 except just making it compile (there are no tests for OMOptim in the testsuite).
This is the main problem with OMOptim, that the main developer moved on to other things and the tool has not really been maintained ever since.
Is anybody interested at actively contributing to that?
comment:8 by , 7 years ago
If I understand correctly, OMOptim "just" called the compiled OM code with varying parameters determined by some algorithm and settings?
If that's the case, and we don't find a maintainer for OMOptim, maybe it would make sense to transfer this task outside, e.g. to the Python ecosystem. We would have to make sure to offer the relevant APIs/functionality in an accessible manner via OMPython, then advise users to use whatever optimization methods are out there in the scientific python stack. Ideally there is already some optimization GUI out there.
Alternatively, what's the status of https://github.com/PySimulator/PySimulator? Maybe optimization could be added as a plugin there?
Just to clarify, having an optimization suite would be really usefule for OM in my opinion, for example to do determination of unknown parameters using measurement data, but a broken/unmaintained solution is worse than none.
comment:9 by , 6 years ago
Milestone: | 1.13.0 → Future |
---|---|
Priority: | blocker → critical |
comment:10 by , 5 years ago
Has there been an update on the OMOptim maintenance situation in the meantime? I just tried using it again but did not get far/was not successful in completing an optimisation.
comment:11 by , 5 years ago
Yes, there was a change to the OMOptim situation: we no longer even compile it for the testing and builds...
comment:13 by , 5 years ago
It is still built on Windows and we will try to resurect it when we have more resources and time.
I'm seeing the same thing