WEBVTT

00:00:07.359 --> 00:00:09.420
<font face="HK Grotesk">Hi and welcome to this short introduction</c>

00:00:09.420 --> 00:00:12.200
<font face="HK Grotesk">To the main actions of
MES Model &amp; Refactor</c>

00:00:12.200 --> 00:00:13.692
<font face="HK Grotesk">From the Analyze category.</c>

00:00:14.639 --> 00:00:17.448
<font face="HK Grotesk">The first action is called
Highlight to all Sources</c>

00:00:17.861 --> 00:00:20.567
<font face="HK Grotesk">And helps you to better understand
the signal flow in your model.</c>

00:00:24.240 --> 00:00:26.098
<font face="HK Grotesk">Imagine you're working on this subsystem.</c>

00:00:27.279 --> 00:00:29.540
<font face="HK Grotesk">To better understand
the signal dependencies</c>

00:00:29.945 --> 00:00:32.295
<font face="HK Grotesk">You want to know which
of the input signals</c>

00:00:32.880 --> 00:00:35.397
<font face="HK Grotesk">Have an impact on this output signal.</c>

00:00:37.911 --> 00:00:40.403
<font face="HK Grotesk">This use case is also
called backward slicing.</c>

00:00:42.960 --> 00:00:46.682
<font face="HK Grotesk">You can try to use Simulink's highlight
signal to Source feature for this.</c>

00:00:55.840 --> 00:00:59.522
<font face="HK Grotesk">But this will stop at the first source block
of the selected signal</c>

00:01:01.520 --> 00:01:03.879
<font face="HK Grotesk">You could try to continue
with the arrow keys</c>

00:01:07.200 --> 00:01:10.527
<font face="HK Grotesk">But this is tedious and does not
help answer the basic question.</c>

00:01:19.200 --> 00:01:21.682
<font face="HK Grotesk">With MES MoRe you can simply
select the signal</c>

00:01:21.720 --> 00:01:23.120
<font face="HK Grotesk">You want to trace backwards</c>

00:01:23.803 --> 00:01:26.937
<font face="HK Grotesk">And use the Highlight to all Sources action</c>

00:01:27.439 --> 00:01:28.842
<font face="HK Grotesk">From the Analyze category.</c>

00:01:34.960 --> 00:01:38.499
<font face="HK Grotesk">The action first asks you if you want
to remove the existing highlighting</c>

00:01:40.000 --> 00:01:42.388
<font face="HK Grotesk">And then highlights all
signal lines backwards</c>

00:01:42.586 --> 00:01:44.563
<font face="HK Grotesk">That have an impact
on the selected signal.</c>

00:01:46.720 --> 00:01:48.339
<font face="HK Grotesk">This way you can now easily see</c>

00:01:48.364 --> 00:01:51.720
<font face="HK Grotesk">That the output signal is only
influenced by the first input signal.</c>

00:01:56.111 --> 00:01:58.277
<font face="HK Grotesk">You can also change into the subsystem</c>

00:01:58.616 --> 00:02:00.505
<font face="HK Grotesk">To see the details of the signal flow.</c>

00:02:10.160 --> 00:02:13.259
<font face="HK Grotesk">Now i could ask the same question
for the second output signal</c>

00:02:14.800 --> 00:02:16.204
<font face="HK Grotesk">And get the answer quickly</c>

00:02:16.229 --> 00:02:18.641
<font face="HK Grotesk">Using MoRe´s
Highlight to all Sources action.</c>

00:02:30.930 --> 00:02:34.081
<font face="HK Grotesk">The next action is called
Jump to Usage Destinations.</c>

00:02:36.720 --> 00:02:38.069
<font face="HK Grotesk">It helps you understand</c>

00:02:38.094 --> 00:02:41.045
<font face="HK Grotesk">Which blocks in your model
are using a particular signal</c>

00:02:41.440 --> 00:02:43.394
<font face="HK Grotesk">By analyzing the data flow forward.</c>

00:02:46.346 --> 00:02:48.393
<font face="HK Grotesk">Imagine you're working on this subsystem</c>

00:02:48.457 --> 00:02:51.830
<font face="HK Grotesk">And want to know which blocks
are using this selected signal c.</c>

00:02:54.092 --> 00:02:55.512
<font face="HK Grotesk">This could be for example</c>

00:02:55.537 --> 00:02:57.584
<font face="HK Grotesk">Because you want to
track an error in the model.</c>

00:02:59.200 --> 00:03:02.033
<font face="HK Grotesk">Or you might have changed
the behavior of signal c</c>

00:03:02.058 --> 00:03:03.962
<font face="HK Grotesk">And now want to analyze the effects.</c>

00:03:06.800 --> 00:03:08.440
<font face="HK Grotesk">You can try to use Simulink's</c>

00:03:08.450 --> 00:03:10.950
<font face="HK Grotesk">Highlight Signal to Destination
feature for this.</c>

00:03:15.120 --> 00:03:18.159
<font face="HK Grotesk">But you will then have to
manually navigate through the model</c>

00:03:18.199 --> 00:03:19.850
<font face="HK Grotesk">To get to the destination blocks.</c>

00:03:21.200 --> 00:03:24.046
<font face="HK Grotesk">In large models this is
tedious and time consuming</c>

00:03:24.371 --> 00:03:26.736
<font face="HK Grotesk">And some destination
blocks can easily be missed.</c>

00:03:31.974 --> 00:03:35.410
<font face="HK Grotesk">With MoRe you can simply
select the signal you want to analyze</c>

00:03:36.823 --> 00:03:40.672
<font face="HK Grotesk">And then use the
Jump to Usage Destinations</c>

00:03:42.319 --> 00:03:44.730
<font face="HK Grotesk">Feature from the Analyze Category.</c>

00:03:48.774 --> 00:03:50.297
<font face="HK Grotesk">The action opens a dialog</c>

00:03:50.377 --> 00:03:54.043
<font face="HK Grotesk">That lists all the destination blocks
that are using the selected signal.</c>

00:03:56.487 --> 00:03:59.146
<font face="HK Grotesk">You can then simply double click
on the items in the list</c>

00:04:00.799 --> 00:04:02.775
<font face="HK Grotesk">To jump to the corresponding blocks</c>

00:04:02.862 --> 00:04:05.886
<font face="HK Grotesk">Which are additionally
highlighted in their subsystem.</c>

00:04:16.269 --> 00:04:17.894
<font face="HK Grotesk">When you have finished your analysis</c>

00:04:17.919 --> 00:04:20.276
<font face="HK Grotesk">You can simply jump
back to the selected signal</c>

00:04:22.240 --> 00:04:24.126
<font face="HK Grotesk">Where you have started your analysis.</c>