WEBVTT 00:00.060 --> 00:05.210 Now what we're going to do is we will modify our code such that we have in synchronicity sitting right. 00:05.310 --> 00:08.780 So to implement this in resolution, the process is very simple. 00:08.780 --> 00:10.380 But what we are going to do is. 00:11.490 --> 00:14.580 We will be removing the risk from here, right? 00:14.910 --> 00:19.830 And first, we will be sensing the clock right, safe. 00:21.200 --> 00:26.180 Rising age of the clock right there. 00:27.830 --> 00:37.960 So let me just start, and I never hear if risk is high right then in that case to be one out of equals 00:37.970 --> 00:40.820 to zero else. 00:41.300 --> 00:46.220 And we'll just take it out to be equals to the right. 00:46.220 --> 00:47.470 So this completes the quote. 00:47.470 --> 00:49.150 We just need Trident and great. 00:49.160 --> 00:52.820 So we have a two o'clock, hence we need to act to. 00:53.900 --> 00:54.170 And. 00:54.920 --> 00:55.670 So this complete. 00:56.090 --> 01:04.490 Now we go ahead and try to lose an existing simulation and they perform again a behavior simulation, 01:05.090 --> 01:09.560 so let it just right click on a clock, you would clock one two zero. 01:10.810 --> 01:13.120 Period that will be choosing a nanosecond. 01:13.390 --> 01:18.710 The good idea will be that you choose a leading edge as you do, and the tooling is just one, so you 01:18.710 --> 01:23.830 could clearly understand the difference between the synchronous energy and. 01:25.070 --> 01:30.740 Synchronicity, citrate, so click OK for research, let's just use first the value of one. 01:31.100 --> 01:35.030 OK, then partly in use Wood's clock. 01:35.950 --> 01:40.900 OK, one, two zero and then be that will be choosing this latest issue. 01:40.930 --> 01:42.480 Two hundred not missing, right? 01:42.530 --> 01:47.620 If you just try to click on one button now, if you observe the. 01:49.430 --> 01:56.300 Wiffle ball research that we are utilizing is, oh, synchronicity, Sydney, so you really see we have 01:56.300 --> 01:57.910 our worst edge over here, right? 01:57.950 --> 02:01.550 So this is our first spot to do it and do that right. 02:01.550 --> 02:09.800 So from the starting instance to the to edge of a clock, we have an undefined value for deal, right? 02:09.800 --> 02:14.000 As soon as we have our basic research disincentives, research is high. 02:14.360 --> 02:15.980 We are getting a value of C, right. 02:15.980 --> 02:21.820 So this clearly indicate that our usage is reading four o'clock ish to arrive and then it is thinking 02:21.840 --> 02:23.140 our be right. 02:23.150 --> 02:28.820 So yeah, you could clearly see the difference between the synchronous and the synchronicity right now 02:28.820 --> 02:30.400 if you just try to remove more research. 02:30.420 --> 02:34.910 So right click on the reset and add a value to zero. 02:34.940 --> 02:41.610 And if you just try to execute the code again, you'll be noticing that now Ivy form is following a 02:41.630 --> 02:42.440 D, right? 02:43.280 --> 02:46.540 So this is working good in both values. 02:46.550 --> 02:49.070 Then use it, apply, reset and then use a remote. 02:49.500 --> 02:49.690 Right. 02:49.700 --> 02:54.500 So this is how we implement the sequential circuit vector offense. 02:54.800 --> 02:57.170 Now we proceed to understand how we use case.