Add special rule for time. Note that it isn't clearly stated as an 'exception', since time is an input and arguable not 'unknown'.
However, 'unknown' is explained as not parameter or constant; and clearly time is neither. In general it makes sense that inputs should be included in the analysis - but I view that as a separate topic; as it wouldn't influence how time is treated.
If time was treated as a normal unknown there could only be one partition directly using it, meaning that the goals of having any model in clocked systems would be completely broken.
If time would be ignored for the analysis then use of 'sample(time)' in 16.3 and in Modelica.Clocked.RealSignals.TimeBasedSources.Ramp would be redundant. That would also remove the 'safety' aspect of normal synchronous models; and wasn't part of the original design.
The new formulation forces time to be in the Continuous-Time or a Clocked Discretized Continuous-Time partition.
* Fix messed up listings related to quadrature examples * Local change to sentence-based line breaking * Use proper cross reference to enumeration item * Align style of custom enumeration items This is the format used in synchronous.tex, which is the variant that best matches the standard format.
Previously "flow" for operator record was forbidden, but defined! (#3094)
* Previously "flow" for operator record was forbidden, but defined - that makes no sense; so clearly allow it. ** Also allow flow on record/connector component. ** Properly define primitive elements. * Previously "stream" required that the flow-variable was scalar, but not that it was a scalar Real. (It was implicitly a Real since "flow" had that restriction - but we need to lift that.) * Additionally the text 'exactly one scalar variable ...' could be incorrectly interpreted as 'one scalar stream variable, and multiple array stream variables'. I have no idea if we could define e.g., complex flow for stream-equations, but it seems complicated for no benefit. Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>
* Make GenerateEvents imply inlining. * Clarify that diagnostics if not generating events. * Clarify that GenerateEvents=true doesn't matter if the function is called where events cannot be generated. Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>
* Specify that all strings can be Unicode. * Specify external interface. Explicitly not saying anything about non-8-bit systems. Co-authored-by: Thomas Beutlich <modelica@tbeu.de> Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>
* Provide better alternative. Closes #3143 * Remove note about old. * Apply suggestions from code review Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com> * White space
* Avoid need to define a term. The term "simulator" was used twice, and unclear if both were correct. * Update chapters/introduction.tex Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>
Attempt at defining initialization, and simulation. (#3146)
* Attempt at defining initialization, simulation, and avoid defining transient analysis. * Move definition to 'Some definitions'. * Define transient analysis and initialization. * Do not use IVP here. * Also define translation, since that ties together the simulation with the rest. * Use 'transient analysis' when appropriate. * Add more detailed description of well-determined initialization problem. * Apply suggestions from code review * Split non-normative paragraphs to make them closer to specific definitions.
Co-authored-by: Elena Shmoylova <eshmoylova@users.noreply.github.com> Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>
![[Jenkins]](/jenkins/static/7b8bca15/images/svgs/logo.svg){kind=logo}
