#2971 closed defect (invalid)
Translation hangs
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | blocker | Milestone: | never |
| Component: | *unknown* | Version: | trunk |
| Keywords: | Cc: |
Description
Models that I was able to run in previous versions are now hanging during translation. I can't cancel the translation, and have to kill the process. No error message appears, it simply sits there for long periods of time for a simple model. I was able to successfully run the example models in the modelica library, but none of my personal models are translating.
Change History (4)
follow-up: 2 comment:1 by , 10 years ago
comment:2 by , 10 years ago
The models I am using are proprietary, so I'm unable to share. I understand that could limit the troubleshooting. I am using the latest official posted release, 1.9.1. What I have seen is that it gets past the "Save" before translation truly commences, but gets no further. I just confirmed today that when I uninstall that version and reinstall Beta2, everything runs fine - no hang-ups in translation. The only warnings I get are related to initial conditions not being fully specified and the number of flow variables not matching the number of potential variables on a connector.
Replying to sjoelund.se:
Which version of OMC are you running and would it be possible for us to try one of the models to try figuring out what is wrong?
comment:3 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Closing as invalid, since there's simply not enough information to work with. Please reopen the ticket if you have more information that could help us resolve this issue.
To be able to do any kind of troubleshooting on this we really would need a model that exhibits the issue. One possibility is that we sign an NDA to make sharing possible, we've done that several times before.
Another possibility is that you take one of your models and change it so that it's no longer a problem to share it with us. The way I usually do this is to choose one model, preferably as small as possible, and save it as a total model (can be done in OMEdit). A total model is simply the model itself and all its dependencies in a single file. Then comment out some part of the model and check if the issue remains. If the issue remains, remove the commented out part and repeat. Otherwise, remove some other part of the model. If the issue is in the instantiation this is easy, since you don't need to consider the model balance. Otherwise it's a bit trickier. In the end you should have a small model that still exhibits the issue, and then you can rename things if you wish to obfuscate the model further. We don't care how the model looks as long as we can use it for troubleshooting.
comment:4 by , 9 years ago
| Milestone: | Future → never |
|---|
Sorting away the closed as invalid, won't fix and duplicate tickets from Future.
Which version of OMC are you running and would it be possible for us to try one of the models to try figuring out what is wrong?