Timeline
2020-07-22:
- 20:13 Ticket #6062 (OMEdit - Proper handling of changed global settings) updated by
- Replying to olivleno: > My point is that changes to global …
- 20:10 Ticket #6063 (OMEdit - Disturbed model view in plotting mode) updated by
- Please try the stable 1.16.0-dev.03 version or the latest nightly …
- 16:25 Ticket #6062 (OMEdit - Proper handling of changed global settings) updated by
- Nothing against having local setting for compiler flags. My point is …
- 16:10 Ticket #6063 (OMEdit - Disturbed model view in plotting mode) updated by
- I'm using OpenModelica v1.16.0-dev-331-g8c4285669 (64-bit)
- 11:42 Ticket #6063 (OMEdit - Disturbed model view in plotting mode) updated by
- This may have been fixed already, see #6032. Are you using the latest …
- 11:39 Ticket #6062 (OMEdit - Proper handling of changed global settings) updated by
-
Priority, Milestone changed
@olivleno, this was discussed with @adeas31 some time ago, the … - 11:14 Ticket #6059 (OMEdit - Compiler flag -d=aliasConflicts takes no affect) updated by
- Replying to olivleno: > Now I recognized the disclaimer in …
- 11:05 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- Replying to Karim.Abdelhak: > If i understood you …
- 10:41 Ticket #6061 (OMEdit - Compiler flag -d=evalOutputOnly takes no affect) closed by
- invalid: This is not an problem of the compiler flag but of the global settings …
- 10:14 Ticket #6059 (OMEdit - Compiler flag -d=aliasConflicts takes no affect) closed by
- invalid: Okay, glad i could be of help. I will close this ticket. …
- 10:13 Ticket #6063 (OMEdit - Disturbed model view in plotting mode) created by
- After simulation the model displayed in plotting mode is not properly …
- 10:02 Ticket #6062 (OMEdit - Proper handling of changed global settings) updated by
-
Description changed
- 09:59 Ticket #6062 (OMEdit - Proper handling of changed global settings) created by
- As reported in …
- 09:36 Ticket #6059 (OMEdit - Compiler flag -d=aliasConflicts takes no affect) updated by
- Thanks for sharing the test case. This helped to narrow down the …
- 08:16 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- Well i understand what you mean, but i am not entirely sure how to …
2020-07-21:
- 22:20 Ticket #6060 (OMEdit - OMEdit crashes when changing connector names) updated by
-
Priority changed
Thank you @ceraolo! We'll try to get this fixed for 1.16.0, or … - 22:18 Ticket #5817 (Backend - Usage of three-phase Aron sensor got problematic last December 2019) updated by
-
I'm not sure I get this, in the second model
Mthe first … - 22:12 Ticket #3689 (Backend - Missing warning for StateSelect.always) reopened by
- Replying to Karim.Abdelhak: > As you can see in …
- 18:09 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) closed by
- fixed: I merged the PR and I will close the ticket. If there are any issue we …
- 14:57 Ticket #6059 (OMEdit - Compiler flag -d=aliasConflicts takes no affect) updated by
- Consider following model: […] This is such a conflict since the …
- 13:41 Ticket #6061 (OMEdit - Compiler flag -d=evalOutputOnly takes no affect) created by
- I compared the graphml output with and without -d=evalOutputOnly. The …
- 13:41 Ticket #6060 (OMEdit - OMEdit crashes when changing connector names) updated by
-
Description changed
- 13:39 Ticket #6060 (OMEdit - OMEdit crashes when changing connector names) created by
- Steps to reproduce: 1) load Test.mo 2) open Test1 3) open …
- 13:38 Ticket #6059 (OMEdit - Compiler flag -d=aliasConflicts takes no affect) created by
- In a model I received this error message: [1] 15:33:36 Symbolic …
- 11:50 Ticket #5817 (Backend - Usage of three-phase Aron sensor got problematic last December 2019) updated by
- Replying to casella: > I don't really think we should. …
- 11:42 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- As you can see in …
- 11:27 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- Replying to Karim.Abdelhak: > I reverted it to a warning …
- 11:13 Ticket #3689 (Backend - Missing warning for StateSelect.always) closed by
- fixed: I reverted it to a warning in …
- 10:49 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- For the time being please keep on using trac :)
- 08:19 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Yeah, that is what I implemented, returning fmi2Error if a doStep with …
- 07:44 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Replying to adrpo: > The question is what should we do if …
- 06:32 Ticket #5817 (Backend - Usage of three-phase Aron sensor got problematic last December 2019) updated by
- > @ceraolo, you can use this as a temporary fix to avoid the …
2020-07-20:
- 22:27 Ticket #5817 (Backend - Usage of three-phase Aron sensor got problematic last December 2019) updated by
- Replying to Karim.Abdelhak: > I guess i will have to also …
- 22:20 Ticket #5669 (NF API - OMEdit crashes expanding Modelica.Media.Air) updated by
- @nruchti, if you find any specific issue that is not already covered …
- 18:56 Ticket #5817 (Backend - Usage of three-phase Aron sensor got problematic last December 2019) updated by
- I am really confused by this case. In general i think i get what is …
- 17:27 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- thank you for the help
- 16:47 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Yes, that is the place: […]
- 16:25 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- I think it is in /usr/include/omc/c/fmi-export/ but I'm not near a …
- 15:54 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Replying to adrpo: > > As a workaround for previous …
- 13:59 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- PR: https://github.com/OpenModelica/OpenModelica/pull/6679
- 13:52 Ticket #5669 (NF API - OMEdit crashes expanding Modelica.Media.Air) updated by
- I get the same/similar crash on 1.16.0. I Run Windows 7 64 bit. While …
- 13:35 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Hm, I looked more a the existing code and it seems we could use the …
- 13:29 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- From my side I vote for just ignoring the defined stopTime, I'll ask …
- 13:26 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- The question is what should we do if the simulator asks to go beyond …
- 13:23 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- Thank you for the quick reply Adrian. From looking at the code you …
- 13:02 Ticket #6037 (FMI - FMI2.0 Co-simulation: Defining stop time in setupExperiment causes ...) updated by
- The problem seems to be here: …
2020-07-17:
- 17:22 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- Honestly I don't see much of a difference. In both cases you must do …
- 17:18 Ticket #6058 (FMI - CVODE FMI variables stuck) updated by
-
Milestone changed
If this is confirmed it is quite serious, we should fix it in 1.16.0 … - 14:28 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- I re-visited my commit and noticed that it does not hard quit on some …
- 14:13 Ticket #6058 (FMI - CVODE FMI variables stuck) created by
- I've been trying the CVODE with FMI and I think I found a bug. The …
- 13:48 Ticket #3689 (Backend - Missing warning for StateSelect.always) updated by
- After consulting Hans Olsson, it is probably better to make this a …
- 13:47 Ticket #3689 (Backend - Missing warning for StateSelect.always) reopened by
2020-07-16:
- 15:20 Ticket #6057 (Run-time - impeuler poor performance and Restart Kinsol: change linear solver to ...) updated by
-
Cc, Priority, Component, Owner, Milestone changed
@Karim, @AhHeuermann, would you mind having a look at that when you … - 12:17 Ticket #6057 (Run-time - impeuler poor performance and Restart Kinsol: change linear solver to ...) created by
- Selecting impeuler as solve produces the following message at every …
2020-07-15:
Note:
See TracTimeline
for information about the timeline view.
