@@ -105,7 +105,7 @@ defined in terms of integer quantities which allow exact comparison.
105
105
This means that when executing a simulation, we can know for certain
106
106
that these two clocks will trigger simultaneously.
107
107
108
- If we wanted to create a clock that was exactly two times slower than
108
+ If we wanted to create a clock that was exactly half as slow as
109
109
``x ``, we can use the ``subSample `` operator to accomplish this. We
110
110
see this in the definition of ``z ``:
111
111
@@ -128,8 +128,8 @@ But by defining ``z`` using the ``subSample`` operator and defining it
128
128
with respect to ``x `` we ensure that ``z `` is always triggering at
129
129
half the frequency of ``x `` regardless of how ``x `` is defined.
130
130
131
- In a similar way, we can define another clock, ``w `` that triggers 3 times more
132
- frequently than ``x `` by using the ``superSample `` operator:
131
+ In a similar way, we can define another clock, ``w `` that triggers 3 times as
132
+ frequently as ``x `` by using the ``superSample `` operator:
133
133
134
134
.. literalinclude :: /ModelicaByExample/DiscreteBehavior/SynchronousSystems/SamplingWithClocks.mo
135
135
:language: modelica
@@ -142,7 +142,7 @@ Again, we could have defined ``w`` directly using ``sample`` with:
142
142
w = sample(time, Clock(1,30));
143
143
144
144
But by using ``superSample ``, we can ensure that ``w `` is always
145
- sampling three times faster than ``x `` and six times faster than ``z ``
145
+ sampling three times as fast as ``x `` and six times as fast as ``z ``
146
146
(since ``z `` is also defined with respect to ``x ``).
147
147
148
148
The synchronous clock features in Modelica are relatively new. As
0 commit comments