Context Navigation

Timeline

20:22 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by anonymous: My idea is that we should make it clear that values manually set in …
06:14 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by Martin Sjölund: The problem is if you have some equation like: […] Can you still …

19:05 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by anonymous: Replying to sjoelund.se: > […] Perhaps the only reason …
10:54 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by Martin Sjölund: I don't think that's a good idea. Equations should hold. Perhaps the …
07:46 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by anonymous: Maybe it is ok if we consider changeable the initial values of all …
06:28 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by Martin Sjölund: I guess the bug here is that x is marked as changeable. Is this …
04:51 test_pwm_driver.mo attached to Ticket #4481 by rahul.dutta.bits@…: PI control testing
04:51 PI_discreet.mo attached to Ticket #4481 by rahul.dutta.bits@…: PI contoller
04:51 discreetPIoutput1.png attached to Ticket #4481 by rahul.dutta.bits@…: plot 2
04:50 discreetPIoutput.png attached to Ticket #4481 by rahul.dutta.bits@…: output plot
04:49 Ticket #4481 (OMEdit - Artifacts in plotting discrete simulation using synchronous Clock feature) created by rahul.dutta.bits@…: Hi, I am testing the new Modelica_Synchronous features by building a …

18:42 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) updated by Lennart Ochel: I guess the input field only overrides the start values and doesn’t …
16:01 Ticket #4480 (OMEdit - Initial conditions are not considered properly when applying Re-simulate) created by Christian Kral <dr.christian.kral@…>: Consider the following example […] After the simulation of this …
10:50 Ticket #3781 (Backend - Fix scaling of detectJacobianSparsePattern) updated by Henning Kiel: Another question is why for the 28x28 and bigger systems the sparse …

17:36 Ticket #4146 (*unknown* - Summary of omc scaling issues) updated by Francesco Casella: It seems we no longer have methods scaling as O(N³), which is a …
17:34 Ticket #4460 (Backend - ResolveLoops scales as O(N^3) in large linear circuit models) closed by Francesco Casella: fixed: Replying to vwaurich: > Results on my machine are: > > …
09:26 Ticket #4129 (Backend - Inefficient array code generation) updated by Martin Sjölund: Cc changed
Looking through the generated code... The problem is that everything …
06:46 Ticket #4479 (FMI - FMU source build fails due to missing lambda functions) updated by Lennart Ochel: Milestone changed
06:45 Ticket #4479 (FMI - FMU source build fails due to missing lambda functions) closed by Lennart Ochel: fixed: This is fixed with …

16:25 Ticket #4479 (FMI - FMU source build fails due to missing lambda functions) updated by Lennart Ochel: Status changed
16:10 Ticket #4479 (FMI - FMU source build fails due to missing lambda functions) created by Adrian Pop: See: …

17:34 Ticket #4460 (Backend - ResolveLoops scales as O(N^3) in large linear circuit models) updated by Francesco Casella: Sounds good. I've started a run on Hudson, will close the ticket …
17:10 Ticket #4129 (Backend - Inefficient array code generation) updated by Martin Sjölund: With #4453, the generated call is sane. Still got the temporary arrays …
16:58 Ticket #4453 (Backend - Compilation Time of a model with large size arrays) closed by Martin Sjölund: fixed: Fixed the reported performance issue and cleared the …
13:39 Ticket #4460 (Backend - ResolveLoops scales as O(N^3) in large linear circuit models) updated by Volker Waurich: I have rewritten the critical part of ResolveLoops. Results on my …

15:33 Ticket #4478 (OMEdit - Show time units in Simulation Setup) updated by Christian Kral <dr.christian.kral@…>: Actually, the Intervals input field shall also show the time …
15:32 SimulationSetup.png attached to Ticket #4478 by Christian Kral <dr.christian.kral@…>: Simulation setup dialog
15:31 Ticket #4478 (OMEdit - Show time units in Simulation Setup) created by Christian Kral <dr.christian.kral@…>: In the simulation setup dialog the Start Time and {{{Stop …
12:27 Ticket #4405 (Backend - Modelica_Synchronous.Examples.SimpleControlledDrive.ClockedWith_AD_DA_E ...) closed by Volker Waurich: fixed: The new subclockpartitioning fixes this problem. I will close the ticket.

Note: See TracTimeline for information about the timeline view.