Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added non-normative explanation for usage of stepSize in ME #2005

Merged
merged 1 commit into from
Nov 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/2_4_common_schema.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -813,7 +813,11 @@ A tool may ignore this information. +
_[However, it is convenient for a user that <<startTime>>, <<stopTime>>, <<tolerance>> and <<stepSize>> have already a meaningful default value for the model at hand.]_ +
<<startTime>>, <<stopTime>> and <<stepSize>> refer to the unit of the <<independent>> variable.
<<stepSize>> defines the preferred <<communicationStepSize>> for Co-Simulation.
For Model Exchange and Scheduled Execution <<stepSize>> has no defined meaning.
For Model Exchange and Scheduled Execution <<stepSize>> has no defined meaning.
_[This does not prohibit the use of <<stepSize>> in the context of Model Exchange._
_For example, a fixed step size solver can use it as a default step size._
_A variable step size solver can use the <<stepSize>> as an initial step size or as result grid for the output._
_Since the required <<stepSize>> depends on the solver itself a defined meaning of <<stepSize>> for Model Exchange is impossible.]_

[[ModelVariables,`<ModelVariables>`]]
==== Model Variables
Expand Down