SysPhS vs Modelica: If you redeclare a PhSConstant (Modelica parameter) as a PhSVariable (Modelica variable) Modelica still treats it as a 'parameter'. You can end up with an unbalanced system with one equation too many!
Figure 26: Constraint block for physical interaction in SysML Gallery Tutorial TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler] Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Parametric Diagram
SysML parameter names are replaced in the Modelica equations according to the bindings in Figure 13 [ERROR]: f is replaced by u, pos is replaced by y, x is replaced by position, k is replaced by springcst, v is replaced by velocity, m is replaced by mass. Source SysPhS-1.1
Figure 25: Constraint block for signal flow in SysML Gallery Tutorial TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler] Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Parametric Diagram
Figure 21: PhSVariables and PhSConstant in SysML Gallery Tutorial TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler] Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD)
By default, Modelica properties are continuous. PhSVariables with isContinuous=true correspond to continuous components, PhSVariables with isContinuous=false correspond to discrete components, and PhSConstants correspond to parameter variables. Source SysPhS-1.1
