WEBVTT

00:00.270 --> 00:06.600
Now, let's modify this call so that we get to process material which will be emerging next to logic

00:06.600 --> 00:07.590
and logic.

00:07.620 --> 00:13.740
Now you'll be finding there are differences between the process, which has NextEd logic is depending

00:13.740 --> 00:17.220
on state and whereas our logic is dependent on street.

00:17.240 --> 00:24.360
So in this case, whenever you have a multiple process, depending on the multiple variables to the

00:24.360 --> 00:27.710
process, which covers the maximum variable.

00:27.900 --> 00:33.210
So, for example, this process already Kovalsky OK, but this process do not cover these.

00:33.300 --> 00:34.590
So what we'll do is we'll.

00:35.710 --> 00:41.070
Choose a signal process that is sensitive to both the variables so that we won't be getting an incorrect

00:41.080 --> 00:46.080
operation if you just make our process sensitive to see the next logical and be working fine.

00:46.120 --> 00:46.390
Right.

00:46.660 --> 00:49.480
So we will choose this process because here we.

00:50.810 --> 00:55.010
Have all the variables, one which both the processes are sensitive.

00:57.030 --> 01:05.550
Now, here, what we will be doing is so when we are in OK, independent of the we know that our police

01:06.550 --> 01:11.830
will just copy this and will not be working to check what is the value of the.

01:11.850 --> 01:16.040
And we will just be checking once we are in the should be one.

01:16.130 --> 01:16.410
Right.

01:16.650 --> 01:22.440
And then the next it can be decided on the value of this makes sense.

01:22.680 --> 01:25.500
When we are in Esswein we know that output should be equal.

01:25.570 --> 01:29.970
Students will just copy this independent of checking what is the value of being.

01:29.970 --> 01:31.430
We'll just be seeing it here.

01:31.460 --> 01:36.390
In fact, what you can do is you can just paste DL twice or so here.

01:36.390 --> 01:41.050
Also, you can be out and here also you can this deal.

01:41.370 --> 01:45.330
So that also mean that independent of the value of the deal will be OK.

01:45.510 --> 01:53.130
But the easier way you faced before or you add your day out before you check the plate, and that is

01:53.130 --> 01:56.140
what we have followed when others should be zero.

01:56.160 --> 02:00.260
So this will won't be affect our entire code.

02:00.270 --> 02:02.910
So we just be wasting it over here.

02:02.940 --> 02:03.180
Right.

02:03.750 --> 02:07.020
And then we can safely delete this process.

02:07.020 --> 02:07.240
Right.

02:07.260 --> 02:08.640
So now we have a to process.

02:08.650 --> 02:14.640
So remember, this point will be choosing a process which is sensitive or which cover all the variables

02:14.670 --> 02:17.850
on which both the process and depending.

02:19.150 --> 02:25.570
We'll just see the will proceed to perform a simulation that also will disclose an existing simulation

02:26.230 --> 02:29.200
and will proceed with a behavioral simulation.

02:32.300 --> 02:33.310
Will apply Akallo.

02:38.110 --> 02:46.180
Will first apply a reset and just apply a reset, try to execute who will be finding we are continuously

02:46.180 --> 02:52.410
in zero, then will proceed and apply when that deal will be to reset rate.

02:52.410 --> 02:58.510
So we'll just go ahead and apply zero at a reset and will try to execute code and still be finding that

02:58.510 --> 03:00.730
we are able to get a square before.

03:00.820 --> 03:01.090
Right.

03:01.330 --> 03:02.940
So the code is working fine.