Timeline
2014-02-27:
- 20:01 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
- What do you mean by Erroneous display? The bug is probably already fix …
- 16:27 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
-
Priority changed
- 16:26 Ticket #2344 (OMEdit - Erroneous display of two MSL 3.2.1. components) updated by
- I've found other cases of graphical misbehaviour of OMEdit. Naturally …
2014-02-26:
- 21:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) closed by
- fixed: Fixed in r19323.
- 21:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
-
Status, Owner changed
- 21:38 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Yep. The unwarranted assumption was that appropriate quoting would …
- 21:25 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to janssen: > But if this function is being …
- 21:23 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I think old-world Mac just used CR, anyway.
- 21:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- You think it would run on old-world Mac? It probably should just …
- 21:20 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to janssen: > There is no world in which \n …
- 20:59 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Replying to lochel: > I don't get the both else cases. I …
- 20:57 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- The nl flag comes from above to tell this function to either escape or …
- 20:50 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I don't get the both else cases. I would just leave them out - but I …
- 20:47 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- There is no world in which \n followed by \r is a newline, so the case …
- 20:43 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- What's this nl flag doing, and what code generates it?
- 20:38 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I guess not too many unwarranted assumptions as this would have been …
- 20:33 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I guess that's one way to look at it. But it seems that the code …
- 20:26 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I asked sjoelund.se to have a look at this. Seems is working if …
- 20:23 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I use omc on the command-line to generate the simulation code, then …
- 20:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Sorry, I should have said I was using a Unix machine. A Snow Leopard …
- 20:07 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Ok. You're right. Seems I can reproduce this on Linux.
- 19:58 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Ouch. Sorry about the config.log. How do you try to build the model? …
- 19:39 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Checked out an update, and rebuilt. Same problem. <Gripe> "make …
- 19:37 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) updated by
- A workaround for now is this: […] A fix for this is in the …
- 19:33 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Well, my OM is from last week's sources :-). I'll update and rebuild.
- 19:28 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Just for posterity, I tested with r19322 and compilation works fine.
- 19:22 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Seems the error comes from MSL Media PartialMedium or all the other …
- 19:18 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) updated by
- Hi, This is a known bug and a fix is on the way. Mostly because we …
- 19:15 Ticket #2604 (Frontend - setState__pTX error using different Media (Modelica.Fluid and ...) created by
- Using OM 1.9.1+dev (r18571) If you are using not only one Medium but …
- 19:04 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- I got an email from janssen which (non public) model has this issue. …
- 19:00 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Which is why we have code that escapes string literals... I would …
- 18:41 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
-
Status changed
- 18:27 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) updated by
- Traced this back to an assert statement in the library I'm using. It …
- 18:12 Ticket #2603 (Code Generation - generated C code contains newlines in string literals) created by
- My generated simulation code doesn't compile, because of constructs …
- 11:26 Ticket #2602 (Frontend - Handle function default arguments better) created by
- We need to handle function default arguments better. Either by saying …
2014-02-25:
- 04:42 Ticket #2565 (New Instantiation - Problems with code generation - package constants in ExternalMedia) updated by
- Bug #2412 (with the IncludeDirectory/LibraryDirectory) is now fixed. …
- 04:40 Ticket #2412 (Frontend - Include and Library annotations for external function do not work when ...) closed by
- fixed: Fixed in r19290.
2014-02-24:
- 08:38 Ticket #2593 (OMNotebook - Examples not defined properly) closed by
- fixed: That seems reasonable, fixed in r19272.
2014-02-22:
- 22:00 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) closed by
- fixed: Fixed in r19255 (see also #2601).
- 21:59 Ticket #2601 (Backend - attributes get lost for optimization models) closed by
- fixed: Fixed in r19255.
- 18:48 Ticket #2601 (Backend - attributes get lost for optimization models) updated by
- cross reference: this is somehow connected to #2597
- 18:45 Ticket #2601 (Backend - attributes get lost for optimization models) updated by
-
Status, Owner changed
- 18:45 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
-
Status, Owner changed
- 18:36 Ticket #2601 (Backend - attributes get lost for optimization models) updated by
- Probably I can fix it. I did some changes and get now: […] …
- 13:21 Ticket #2601 (Backend - attributes get lost for optimization models) updated by
- The max attribute is set correctly, because it is parameter dependent …
- 12:25 Ticket #2601 (Backend - attributes get lost for optimization models) updated by
- Using +d=dumpindxdae shows that the min attributes are somehow present …
- 12:18 Ticket #2601 (Backend - attributes get lost for optimization models) created by
- Some variable attributes get lost for the following model […] If …
2014-02-21:
- 19:11 Ticket #2600 (Build Environment - Reduce size of reference files) created by
- The reference files currently take up ~1.8GB out of 2.4GB in the …
- 18:40 Ticket #2599 (Backend - Handling of (tuple) = f(...) when solving non-linear) updated by
-
Description changed
Replying to sjoelund.se: > Are you actually allowed to … - 18:07 Ticket #2599 (Backend - Handling of (tuple) = f(...) when solving non-linear) updated by
- Are you actually allowed to output both a continuous-time and …
- 17:32 Ticket #2599 (Backend - Handling of (tuple) = f(...) when solving non-linear) updated by
- Yes, the code we would produce is wrong, since for all non-linear …
- 16:52 Ticket #2599 (Backend - Handling of (tuple) = f(...) when solving non-linear) updated by
- Replying to wbraun: > We try to solve the equation > …
- 16:39 Ticket #2599 (Backend - Handling of (tuple) = f(...) when solving non-linear) created by
- Examples like following were handled wrong in SimCodeUtil: […] We …
- 15:45 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) reopened by
- OMEdit is not using that attribute. I used it for an old …
- 15:12 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
- Replying to lochel: > BTW: I am not sure if we need the …
- 13:51 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) closed by
- fixed
- 13:38 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
- I changed the handling for nominal values in r19239. Now, the XML file …
- 12:51 Ticket #2555 (Frontend - Missing cast for integer array) closed by
- fixed: Fixed in r19238.
- 10:19 Ticket #2555 (Frontend - Missing cast for integer array) updated by
-
Status, Owner changed
- 08:24 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
- I propose to introduce new Boolean entities "dependentNominal", …
- 07:54 Ticket #2555 (Frontend - Missing cast for integer array) updated by
- You get the wrong result (and/or a simulation crash) even if the cast …
- 06:20 Ticket #2598 (OMEdit - Difference in results obtained from MAT and CSV output formats) created by
- During Simulation of the DoublePendulum example, the plots obtained by …
2014-02-20:
- 19:12 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
- No, it is not correct. Please, check the following example from the …
- 16:01 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
-
Owner, Type changed
This statement useNominal=false, nominal=1.0 is correct. We don't use … - 15:54 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
- same for start, min and max.
- 15:48 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
-
Owner changed
Come on - you can fix it. Any comments on how to fix it? The … - 14:53 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) updated by
-
Status, Owner changed
- 14:49 Ticket #2597 (Run-time - *_init.xml and bounded nominal values) created by
- The *_init.xml file contains if a nominal value is used and if so also …
- 12:28 Ticket #2596 (OMEdit - Re-simulate with changed options) updated by
- Good ticket – I also wanted to create it for a while. I am not sure if …
- 12:02 Ticket #2596 (OMEdit - Re-simulate with changed options) created by
- Currently, when you choose re-simulate you do not get an option to …
- 11:55 Ticket #2594 (OMNotebook - Examples not defined properly) closed by
- duplicate: Duplicate of #2593
- 11:41 Ticket #2595 (OMEdit - new button for buildModel) created by
- I would like to have a new button to run buildModel (no simulation).
Note:
See TracTimeline
for information about the timeline view.
