WEBVTT 00:00.610 --> 00:04.140 That you could use with a data flow modeling state are listed away. 00:04.340 --> 00:07.740 Right, so we'll just be going through each of them in a detailed OK. 00:07.740 --> 00:12.870 And we'll also be considering an example as we progress, by the way, to a logical operator to include 00:13.140 --> 00:18.360 an AR nine or X are ignoring all the. 00:19.330 --> 00:26.320 Gigs that you that you could find in a designer available with us to whenever you want to use and I 00:26.320 --> 00:30.970 know better, you just need to write and I think you were right, for example, if our system is something 00:30.970 --> 00:31.660 like this, right? 00:32.050 --> 00:34.990 So you have a system, right? 00:35.380 --> 00:40.700 And this consists of simple architecture like this. 00:40.920 --> 00:43.660 So would it be and why? 00:43.720 --> 00:44.020 Right? 00:44.310 --> 00:47.590 So in that case, we'll just be adding way and then E! 00:48.190 --> 00:48.700 And. 00:50.640 --> 00:55.710 So this is how we will be representing this date. 00:55.990 --> 00:56.220 Right? 00:56.430 --> 00:59.560 We have a discourse about an assignment operator yet. 00:59.580 --> 01:04.620 So as we progress further, we will be discussing what are the different assignment operators that we 01:04.620 --> 01:05.570 have with this today. 01:06.360 --> 01:12.900 Similarly, if this system consists of in Aldgate, you could just use an Arquilla nine nor X or ignore 01:12.900 --> 01:13.400 or not. 01:13.740 --> 01:14.010 Right? 01:14.640 --> 01:16.950 Then we have an automatic operator now, in fact. 01:16.980 --> 01:22.650 OK, so that's something that could be used to build a complex circuit with a data flow modeling standard. 01:22.890 --> 01:27.320 So even though if your system consists of just an idea. 01:27.540 --> 01:34.650 OK, so that you could also implement with the help of a little more U.S. data when we are discussing 01:34.650 --> 01:42.060 parliament is what we decided is whenever you have a situation that you replace your system with the 01:42.060 --> 01:45.130 be psychological, then you prefer to go with a little more, let's say. 01:45.540 --> 01:53.190 But if your system can be replaced with the basic automatic block again, that is also we could use 01:53.190 --> 01:54.420 data flow more say so. 01:54.420 --> 01:59.490 This is something that we have added on the top of what we have discussed about data flow. 02:00.510 --> 02:07.800 So if your system is replaced with the basic idea or subtract or multiply, then also you would proceed 02:07.800 --> 02:08.790 with that no one. 02:09.360 --> 02:13.860 So we have added so addition operator is it does. 02:13.860 --> 02:15.840 Then we have an multiplication operator. 02:15.840 --> 02:17.620 We also have a subsection operator, right? 02:17.850 --> 02:23.640 In fact, other than this, we also have some other operator, but they are not good at synthesis, 02:23.640 --> 02:23.880 right? 02:23.890 --> 02:30.720 So if you have a situation for implementing a division, OK, and that is, we need to implement our 02:30.720 --> 02:35.240 own algorithm so that it will be in most of the keys of choice, right? 02:35.430 --> 02:37.110 Instead of utilizing the. 02:38.280 --> 02:43.350 Division operated that we have in, and we did all you could just proceed with and vendor specific APIs 02:43.350 --> 02:47.020 for divide that you'll frequently find in an IP block, right? 02:47.040 --> 02:51.740 So we'll be discussing more on in the division as we progress. 02:51.840 --> 02:59.130 But other than that, we also have a shift obliterates if you want to implement a simple shift operation. 02:59.520 --> 03:05.480 We also have a shift operator with this idea, then that we also have a relational operator. 03:05.700 --> 03:12.090 So when you want to choose whether two numbers are equal or unequal, less than greater than all the 03:12.090 --> 03:15.060 relational operators are also available with it. 03:15.600 --> 03:18.390 Remember, the fundamental concept will remain sim. 03:18.420 --> 03:24.690 That is, whenever we replace the system with the basic logic, OK, we prefer to go with our flow marketing 03:24.690 --> 03:25.020 state. 03:25.260 --> 03:25.590 OK. 03:26.520 --> 03:29.200 But you will just modify that rule a bit. 03:29.220 --> 03:36.030 That is, if we could replace that system, OK with a basic, basic arithmetic block. 03:36.120 --> 03:36.450 OK. 03:36.660 --> 03:41.600 For example, our system just consists of a single I did all single multiplayer. 03:41.910 --> 03:45.000 Then we do have a second operator with us. 03:45.220 --> 03:53.340 Similarly, if a system just consists of one shifter, OK, then in that case also we could implement 03:53.340 --> 03:57.370 it with a data flow modeling state for a relational operator. 03:57.390 --> 04:03.750 We need to understand the assignment operator in detail, and there we will be utilizing the relational 04:03.750 --> 04:04.410 operator, right? 04:05.360 --> 04:08.060 So remember, these are the operators that we have with this. 04:08.540 --> 04:14.930 So even though have no more leaks, still supports automatic shift and relational operators along with 04:14.930 --> 04:15.920 the logical operator. 04:16.220 --> 04:22.310 But my recommendation is then you replace your system with the basic logic gate. 04:22.550 --> 04:29.320 OK, then only you prefer to go with the data flow modeling state forests of the cases we do have and 04:29.330 --> 04:30.690 other models still available. 04:30.960 --> 04:38.210 So instead of unnecessarily confusing us, what we could assume is, OK, these operators are simply 04:38.210 --> 04:39.080 not available. 04:39.710 --> 04:42.530 OK, so what we could do is you miss this operator. 04:42.620 --> 04:43.790 We'll get this operator. 04:44.030 --> 04:50.600 Automatic shift and religion will simply be not using with the flow modeling state, so we will only 04:50.600 --> 04:52.640 be sticking to the logical operator. 04:52.670 --> 04:53.010 OK. 04:53.060 --> 04:55.360 And that quickly simplifies ad logic, right? 04:55.640 --> 05:02.120 Because we do have another modeling state with which we could actually implement the same system. 05:02.180 --> 05:02.400 Right? 05:02.420 --> 05:06.090 So just keep this fact in mind that they do exist. 05:06.320 --> 05:11.500 Medics shift and relational operator along with the logical operator for modeling sake. 05:11.660 --> 05:17.830 But we will be offering 30W morning sale only when we replace our system with a basic logic. 05:18.000 --> 05:18.250 Great. 05:18.620 --> 05:24.830 So in the cases where you're required to have an automatic shipped or relational operator, the good 05:24.830 --> 05:28.940 idea will be that we prefer to go with that behavioral model. 05:29.630 --> 05:30.410 Remember this thing? 05:30.650 --> 05:35.630 So this is just for an information purpose that we have an automatic shift and relational operator been 05:35.630 --> 05:37.610 present in the in our. 05:38.790 --> 05:45.000 Dataflow Malling sale, along with a logical operator, but we will always be preparing to go with only 05:45.000 --> 05:46.210 a logical operator. 05:46.350 --> 05:51.780 So far, the case is very, very where we required an automatic shift or additional operator will be 05:52.080 --> 05:54.400 preparing to go with an either model. 05:54.930 --> 05:57.250 So this will keep our rule unchanged. 05:57.270 --> 06:02.700 That is, we will be utilizing the lead of the morning state only when we replace our system with the 06:02.700 --> 06:03.570 basic logic.