Timeline
2012-12-19:
- 12:58 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- - a good work around could be to report not the warning but add an …
- 12:53 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) closed by
- fixed: I guess you are totally right. But anyway, this is not handled as you …
- 10:01 Ticket #1991 (New Instantiation - StateSelect Attribute with unfixed parameters wrong evaluated without ...) updated by
- Note that it is valid for a tool to reject non-fixed structural …
- 09:52 Ticket #1991 (New Instantiation - StateSelect Attribute with unfixed parameters wrong evaluated without ...) updated by
-
Description changed
- 09:50 Ticket #1991 (New Instantiation - StateSelect Attribute with unfixed parameters wrong evaluated without ...) created by
- Consider the following model. The state select attribute is set via …
2012-12-18:
- 11:21 Ticket #1890 (New Instantiation - Flatten classes in SCodeInst) updated by
-
Priority changed
Lowered priority since the most important part is done. - 10:47 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- Maybe I miss something, but there are lots of other cases where …
- 09:37 Ticket #1990 (Backend - Symbolic Jacobian fails for functions) created by
- I tried the new Symbolic Jacobian feature on a msl32 model that …
- 09:35 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- I guess it is not that clear in the spec. Our approach is to provide …
- 08:10 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- - example from the Spec3.3 Page 91 […]
- 07:50 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- Yes, you are right. We support those special cases as well. But the …
- 07:43 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- - We do also support Parameters with final=true and …
- 07:30 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- Currently we do just support constant variability for the …
- 06:21 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
- simple example with the same issue: […] test1 works fine, but …
2012-12-17:
- 16:56 Ticket #1973 (Backend - Problem with initial equations affecting valve models in Modelica.Fluid) updated by
-
Status, Owner changed
The problem is, that the fixed attribute of CvTypes.Av depends on … - 16:39 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- Per fixed some of these issues in #1989. I'll look into how to apply …
- 16:26 Ticket #1989 (New Instantiation - Fix propagation of modifiers in new instantiation) closed by
- fixed: Fixed in r14429.
- 11:59 Ticket #1987 (Frontend - Unbalanced model) closed by
- fixed
- 11:59 Ticket #1988 (Frontend - Inner class definition is removed by dependency analysis) closed by
- fixed
- 09:46 Ticket #1989 (New Instantiation - Fix propagation of modifiers in new instantiation) created by
- The propagation of modifications in the new instantiation doesn't work …
- 08:53 Ticket #1981 (Run-time - wrong handling of events for the first evaluation) closed by
- fixed: fixed in r14417
- 08:29 Ticket #1981 (Run-time - wrong handling of events for the first evaluation) updated by
-
Status, Owner changed
The problem is in the handling of introduced help-vars for event …
2012-12-16:
- 23:11 Ticket #1988 (Frontend - Inner class definition is removed by dependency analysis) updated by
- Hopefully fixed in r14412.
- 23:11 Ticket #1987 (Frontend - Unbalanced model) updated by
- Hopefully fixed in r14412.
- 22:49 Ticket #1988 (Frontend - Inner class definition is removed by dependency analysis) created by
- See this model: […] and instantiate Bug.B. […] will be removed.
- 19:53 Ticket #1987 (Frontend - Unbalanced model) updated by
- Yep. We don't support inner/outer classes yet. I'll see if I can add …
- 19:32 Ticket #1987 (Frontend - Unbalanced model) updated by
- for comparison dymolas output […]
- 19:22 Ticket #1987 (Frontend - Unbalanced model) created by
- I've found another source of unbalanced models. Consider the following …
2012-12-14:
- 16:22 Ticket #1984 (Build Environment - Improperly tests simulations) updated by
- Is fine for now just after simulate(). Maybe we should call it after …
- 16:20 Ticket #1984 (Build Environment - Improperly tests simulations) updated by
- That could perhaps be done. It might mess with output in if-statements …
- 15:49 Ticket #1984 (Build Environment - Improperly tests simulations) updated by
- I've added getErrorString() to the models mentioned. However, I am …
- 13:02 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- Or actually, perhaps it helps to view redeclares and modifications …
- 12:58 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- Replying to adrpo: > Hmm, i wonder what the specification …
- 12:53 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- Hmm, i wonder what the specification say about this. Should we keep …
- 12:37 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- *FlattenRedeclare.replaceElementInScope should do: […]
- 12:32 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
-
Summary changed
- 12:31 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
- I guess the when applying component redeclares to the env we should …
- 12:27 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
-
Cc, Keywords, Component changed
It seems this also happens with the new inst: […] It seems we don't … - 12:25 Ticket #1956 (New Instantiation - Merge modifiers from the original component when redeclaring components.) updated by
-
Status changed
- 12:11 Ticket #1881 (Run-time - Glycol47 segfaults in LAPACK routine) closed by
- fixed: This simulates fine now.
- 12:08 Ticket #1921 (Run-time - Oscillator executable fails without message) closed by
- fixed: this can be even simulated now.
- 12:03 Ticket #1896 (Frontend - Error occurred while flattening model ...) closed by
- fixed
- 11:23 Ticket #1691 (Backend - M.E.Digital.Examples fail to run backend) closed by
- fixed
- 11:17 Ticket #1318 (Backend - Bootstrap the compiler) closed by
- fixed
2012-12-13:
- 23:37 Ticket #1986 (Frontend - Wrong Warning about usage of variable before defined) updated by
- - add Modelica ticket about that …
- 23:27 Ticket #1986 (Frontend - Wrong Warning about usage of variable before defined) closed by
- invalid
- 23:25 Ticket #1986 (Frontend - Wrong Warning about usage of variable before defined) created by
- For the model Modelica.Electrical.Spice3.Examples.Graetz following …
- 22:00 Ticket #1985 (FMI - FMI import fail to use input varibles) created by
- Input variables (for example Modelica.Blocks.Interfaces.RealInput …
- 16:03 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) closed by
- fixed: Fixed in revision: r14351 [with additional fixes in r14354, r14355, …
- 16:02 Ticket #1917 (Frontend - Instantiaten lost Parameter Binding) closed by
- fixed: Fixed in revision: r14351 [with additional fixes in r14354, r14355, …
- 10:53 Ticket #1984 (Build Environment - Improperly tests simulations) updated by
- I would say getErrorString() should be added after each API command …
- 10:48 Ticket #1976 (Backend - val return different result on windows an linux on event point) updated by
- Aha! Found it.... Sent an email about this yesterday: […] And …
- 07:14 Ticket #1984 (Build Environment - Improperly tests simulations) created by
- When doing simulation tests, you need to call getErrorString() after …
2012-12-12:
- 17:50 Ticket #1982 (Backend - issues with circuits containing diodes) updated by
-
Description changed
- 13:05 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- Ok. This seems a bit serious. I'll have a look at it asap. Cheers, …
- 13:03 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
-
Cc changed
- 13:01 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- see also Ticket #1917
- 12:55 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- For example the model …
- 12:43 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- Good to know […] I am sure this is not handled in the backend if …
- 12:38 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- As far as I've seen only the warning is wrong. The bindings do appear …
- 12:37 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- I guess this task should have a higer prioriti. Because of final …
- 12:29 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- Is it only the warning that is wrong, or is there a chance of …
- 12:26 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) updated by
- I've seen this too in some cases. Is a bug. In some cases even if you …
- 12:11 Ticket #1983 (Frontend - Parameter has neither value nor start value, and is fixed) created by
- Hi, I always wondered about those strange warnings and created a …
- 10:07 Ticket #1982 (Backend - issues with circuits containing diodes) updated by
-
Description changed
- 10:05 Ticket #1982 (Backend - issues with circuits containing diodes) created by
- It has been known since a long time ago that OM has problems when …
- 08:09 Ticket #1981 (Run-time - wrong handling of events for the first evaluation) created by
- […] dump LOG_EVENTS […] There is no reason to trigger an event.
Note:
See TracTimeline
for information about the timeline view.