Timeline
2013-10-18:
- 15:30 Ticket #2428 (Run-time - numerical instability) updated by
-
Description changed
- 15:26 Ticket #2428 (Run-time - numerical instability) created by
- Following model behaves numerical instable: […] results with …[…]
- 08:35 Ticket #2427 (Installation program - Compilation problems in GUI, /usr/include/qt4/QtGui ?) closed by
- fixed
- 08:34 Ticket #2427 (Installation program - Compilation problems in GUI, /usr/include/qt4/QtGui ?) updated by
-
Status, Owner changed
- 08:34 Ticket #2427 (Installation program - Compilation problems in GUI, /usr/include/qt4/QtGui ?) updated by
- I think you might need to install a compiler that can handle the …
- 07:16 Ticket #2427 (Installation program - Compilation problems in GUI, /usr/include/qt4/QtGui ?) created by
- g++ -c -m64 -pipe -O2 -w -fPIC -D_REENTRANT -DQT_WEBKIT -DQT_NO_DEBUG …
2013-10-17:
- 15:58 Ticket #2285 (Code Generation - bad code generation for arrays) closed by
- fixed: => index starts with 3 and is thus too large for t2 Yes. that was the …
- 14:38 Ticket #2426 (Frontend - Improve error message for when-statement in function) created by
- A more informative error message than STATEMENT_GENERIC_FAILURE is …
- 10:01 Ticket #2425 (Frontend - Use new Modelica terminology, "restricted class" -> "specialized class") closed by
- duplicate: Duplicate of #2383 (fixed in r17735).
- 10:00 Ticket #2383 (Frontend - Change "class restriction" in error messages to "specialized class") closed by
- fixed: Fixed in r17735.
- 09:47 Ticket #2404 (Backend - Iteration variables with default zero) reopened by
- I spoke to Willi and we agreed on the following: The problem is that …
- 08:40 Ticket #1078 (Frontend - Improve error message when trying to override a final ...) reopened by
- Reopening, as there is currently no error message at all.
- 07:53 Ticket #2425 (Frontend - Use new Modelica terminology, "restricted class" -> "specialized class") created by
- To conform with the current Modelica specification, error messages …
2013-10-16:
- 10:58 Ticket #2424 (OMEdit - Support links to resources) created by
- Documentation often links to […] We should follow those links
- 04:58 Ticket #2423 (OMEdit - Crash in OpenModelica Connection Editor related to multiple variable ...) closed by
- worksforme
2013-10-15:
- 23:16 Ticket #2422 (Frontend - loadFile("path/to/library/package.mo") loads the wrong library) closed by
- fixed: Fixed in r17713.
- 23:15 Ticket #2423 (OMEdit - Crash in OpenModelica Connection Editor related to multiple variable ...) updated by
- It doesn't crash for me but I am using r17662. I suggest you should …
- 22:31 Ticket #2422 (Frontend - loadFile("path/to/library/package.mo") loads the wrong library) updated by
- Is pretty clear why it happens. We transform: …
- 22:18 Ticket #2423 (OMEdit - Crash in OpenModelica Connection Editor related to multiple variable ...) created by
- Hey all, I've never posted here before so apologies in advance if I'm …
- 21:27 Ticket #2422 (Frontend - loadFile("path/to/library/package.mo") loads the wrong library) updated by
-
Status, Owner changed
- 21:26 Ticket #2422 (Frontend - loadFile("path/to/library/package.mo") loads the wrong library) created by
-
We have:
loadFile("../C2M2L_Ext/package.mo");The directory … - 17:56 Ticket #2414 (Code Generation - Split the generated C file for simulation further?) closed by
- fixed: Fixed FMI and +target=msvc in r17700.
- 10:30 Ticket #2416 (OMEdit - Unwanted behaviour of OMEdit with syntactically incorrect models) updated by
- I would suggest that we step back a moment and agree on the …
- 06:25 WikiStart edited by
- (diff)
- 06:17 WikiStart edited by
- (diff)
2013-10-14:
- 11:52 Ticket #2414 (Code Generation - Split the generated C file for simulation further?) updated by
- I believe it's just some .o-files that are missing when linking.
- 11:48 Ticket #2414 (Code Generation - Split the generated C file for simulation further?) updated by
-
Status, Owner changed
Maybe Adeel can help us there as I'm lost on how the FMI dll is built. … - 11:41 Ticket #2414 (Code Generation - Split the generated C file for simulation further?) updated by
- Oh yeah. I committed the files for this. But FMI on Windows remains to …
- 11:40 Ticket #1739 (Instantiation - Missing error message for noEvent of discrete time expressions) updated by
- Thats's an example and non-normative, which means it carries no real …
- 11:28 Ticket #1739 (Instantiation - Missing error message for noEvent of discrete time expressions) reopened by
- The example in section 4.4.4: See equation for iff1a below. […]
- 05:39 Ticket #2416 (OMEdit - Unwanted behaviour of OMEdit with syntactically incorrect models) reopened by
- (I have not looked into the code to see how the timer is implemented.) …
2013-10-13:
- 13:29 Ticket #2421 (OMEdit - OMEdit gdb debugging - desired features) updated by
-
Description changed
- 13:25 Ticket #2421 (OMEdit - OMEdit gdb debugging - desired features) created by
- I would really like to extend the GDB debugger features in OMEdit …
2013-10-12:
- 03:54 Ticket #2419 (Frontend - Make getMessagesStringInternal called only by OMEdit return unique errors) closed by
- fixed: Fixed in r17657.
2013-10-11:
- 12:54 Ticket #2385 (New Instantiation - Missing variable declarations in instantiated model when using ...) updated by
- Okay, let's try this again. I hope that this time the model is valid …
- 12:50 Ticket #2420 (Frontend - Do not return error messages when calling checkModel (maybe there are ...) updated by
- Anyway, OMEdit doesn't need to parse it. Can just do: […] As 3 …
- 12:49 Ticket #2420 (Frontend - Do not return error messages when calling checkModel (maybe there are ...) updated by
- Does the pope shit in the woods? Yes.
- 12:49 Ticket #2420 (Frontend - Do not return error messages when calling checkModel (maybe there are ...) updated by
- can OMEdit parse tuples?
- 12:48 Ticket #2420 (Frontend - Do not return error messages when calling checkModel (maybe there are ...) updated by
- Not an array. What the hell? Come on, a tuple (multiple outputs)…
- 12:01 Ticket #2420 (Frontend - Do not return error messages when calling checkModel (maybe there are ...) created by
- Currently checkModel puts the error messages in the string returned. …
- 11:20 Ticket #2416 (OMEdit - Unwanted behaviour of OMEdit with syntactically incorrect models) closed by
- fixed: It should work in r17652. It was my mistake. The interval accepts the …
- 11:04 Ticket #2419 (Frontend - Make getMessagesStringInternal called only by OMEdit return unique errors) updated by
-
Description, Summary changed
- 10:41 Ticket #2419 (Frontend - Make getMessagesStringInternal called only by OMEdit return unique errors) updated by
-
Status, Owner changed
Or wait, OMEdit uses some other API to get the error messages. … - 10:39 Ticket #2419 (Frontend - Make getMessagesStringInternal called only by OMEdit return unique errors) created by
- As far as I can tell the connector not balanced messages are repeating …
- 07:18 Ticket #2140 (Backend - Enable Tearing by default) updated by
- In theory tearing always improves simulation speed, so there is no …
- 07:09 Ticket #2140 (Backend - Enable Tearing by default) updated by
- Maybe this should be enabled only for systems above a certain size?
- 07:03 Ticket #2140 (Backend - Enable Tearing by default) updated by
- What I did not look at are the time required for simulation. On …
- 07:01 Ticket #2140 (Backend - Enable Tearing by default) updated by
- Yes, we should enable tearing for linear systems as soon as possible.
- 06:53 Ticket #2404 (Backend - Iteration variables with default zero) closed by
- fixed: Well, that is correct. I guess we should enforce that we handle torn …
- 06:52 Ticket #2140 (Backend - Enable Tearing by default) updated by
- I ran the whole msl32 testsuite with +d=doLinearTearing this night. We …
- 06:32 Ticket #2404 (Backend - Iteration variables with default zero) reopened by
- I've just run the testsuite with +d=doLinearTearing. Then as we know …
- 05:30 Ticket #2416 (OMEdit - Unwanted behaviour of OMEdit with syntactically incorrect models) updated by
- The issue occurs instantly when auto save is set to 300 s. In reality …
- 04:52 Ticket #2417 (Code Generation - Support arrayLayout) updated by
-
Priority changed
Not used anywhere, setting prio to low: […] - 02:48 Ticket #2418 (Frontend - component modification references wrong scope) closed by
- fixed: Fixed in r17650.
- 00:03 Ticket #2418 (Frontend - component modification references wrong scope) created by
- When I run this model […] with 1.9.0RC1, I get this: […] …
Note:
See TracTimeline
for information about the timeline view.
