Martin Otter

Unfortunately, the issue is worse than expected: It does not matter whether results are stored at an event point (I thought this is a work-around): The FunctionCallingCallback is still called...

Any progress here? I have the following (bad) work-around: At an event instant, I call outputs!(..) myself for all time instants stored in integrator.sol.t/sol.x from the previous event until the...

The goal is to have a Modelica-compliant library and therefore only option (3) is useful (but it should not be "long term" but "short term"). Option (1) and (2) are...

Modelica_LinearSystems2 was developed a long time ago. The main purpose was to make operations on linear systems available in models or scripts. The problem at that time was that records...

I moved from Julia 1.9.4 to 1.10.3 and had various difficulties with PyCall and PyPlot. After resolving them, I am now stuck - also with a Julia crash (on Windows...

Find attached two different solutions: [NewAngleSensor.mo.txt](https://github.com/user-attachments/files/16059607/NewAngleSensor.mo.txt) - NewAngleSensor.AbsoluteAngles is based on the Sketch of @tobolar by integrating the angular velocity. The advantage is that a small linear equation system is...

Sorry, I am not good enough in github to understand the current status: Is the request from Thomas (update of release notes) included in the pull request? "This branch is...

By purpose there a blocks for different data types that provide a mathematical constant, so the output of the block does not change over time: Modelica.Blocks.Sources.Constant/.BooleanConstant/.IntegerConstant. In a similar way...

>The Blocks are too fundamental to just be considered a control systems construct. I disagree. All data given in menus of Modelica blocks are parameters (from a few exceptions). Therefore,...

> Sure. I see that it would be controversial, and that is why it isn't included as part of this PR. For this PR, the renaming discussion could be seen...