we need four so it is a new session series it is on software integration and the embedded software integration aspects of embedded software testing we know we need to have a software integration basically there are two things so that we need to be understanding embedded software integration as such is an activity of the embedded software life cycle and it should be considered as an activity from both developers as well as testers perspective that means to say that we are going to have integration definitely integration is the integral part of the embedded software development life cycle meanwhile we are going to test as an integrated unit how it is going to be so the second aspect in terms of integration testing we are going to focus so audience should not get confused with the software integration from developers perspective as well as the testers perspective so it should be separate entity developers have they have their own life cycle aspects in terms of integrating the various models basically here we focus on testing part of embedded software integration that is what we will try to focus on understand okay so to recap on some of the levels of testing just in order to understand what is embedded software integration we will see the three levels of three layers of software testing we know that there are about for example 12 components in an embedded software unit how they are going to be tested at different levels we know that component and unit level we are going to test it individually with the help of stubs or any other drivers or any other methods that is all a part of the unit testing where the individual units are under the focus and those units are closed with their objects data parameters and all that and on the higher side I am coming to the bottom part of the type of a levels of testing system level where all these 12 units are the components of the embedded software systems is completely put together and tested externally you can see the arrow mark outside the complete box you can consider M1 to M2 as a complete unit as a system and this system is being verified externally with external triggers or events or signal feeds and fault injections likewise so this system level the first one being component level the one that we are trying to focus in this series of session is on integration where there are different modular boxes which will be integrated to make it your system so we start with this component we have tested it the components are fine or the units are okay then these units basically grouped into the logical units so these logical units one logical two we have a logical unit three it can have multiple modules or single module whatever the way how it can be logically grouped so logical grouping is again based on the various aspects as I said in earlier sessions like its functionality complexity and any performance related any closed loop control system related all these feature files depending on the type of system that we have we are going to have the various logically divided units into different groups so that is what we do so here here we example we have one two three four units and one M1 as a one here the logically we cannot separate this M1 which separately put so this is what we do in integration where logical units are integrated so may be different types of integration testing software like bottom of top down big bang and all we will study that one more and the primary intention is to see that these modules when it is getting integrated how they what is the interactions what are the inputs and outputs that is getting handled by these logical groups is what is getting tested in the integration software testing that is the main focus of the embedded software integration process okay so now we will go in deep into integration testing the embedded software integration testing so we will try to understand the definitions scope objectives then we have considerations strategies we will take up the examples in the series of sessions of integration testing okay integration is the process of aggregating components to create larger components as I said we have different components we are going to aggregate them like M1 M2 M3 M4 or individual components we are going to aggregate as one logical group so we are going to aggregate those components so that will become a larger component we can call it as a component or a group group component whatever it is so there are five groups here in this example and we are going to integrate that that is what integration does so while integrating there are different types of testing aspects we are going to create test suite with the help of test environment and get the values for that group and try to get the output that is what the process of integration is going to take care integration testing done to show that even though components were individually satisfactory the combination is incorrect or inconsistent so testers goal is to make sure that it is fine and testers goal is also make sure that there are errors there are issues with certain types of inputs when they are combined each other so it is not just enough to satisfy individual component like M1 M2 M6 they may work individually fine but when they integrate each other what is the behavior of that so that is what we are going to the tester is going to test it so the objective is to make sure that the combination of these individual components are satisfactorily working or if there are issues that has to be brought out and the inconsistency incorrectness all this will be one of the errors or the failures that it could occur while doing the integration testing okay going with definitions that various people industry and web resources that we have just try to understand an integration strategy is a decision about how the different models are integrated with a component system the objective of integration testing integration testing in the small according to on the B standard 79251 is to find bugs related to interfaces between models as they are integrated together that means the objective is to find bugs related to interfaces between model as they are integrated together that means we do not have to integrate everything together we can do a progressive integration in terms of first you integrate the objective group 1 2 then 2 3 3 4 4 5 etc then incrementally add it and see the behavior how it is going to behave that is what we do with the modules as and when they are integrated each other the integration course both hardware and software as I said in one of the earlier sessions there are two aspects of integration software question which we understand so we have hardware involved software involved hardware is involved for what from a software perspective there are interfaces right interfaces could be using any of the hardware part like it could be a memory it could be a communication device or it could be a any signals all these are hardware parts so there is a driver also called device driver involved so there are of these interfaces we are going to interface with the hardware so that is what we do with the hardware integration software what we do we have calculations of the data algorithms on the complex features then we have a program flow plan in plan out I will not go in deep but you know that software modules difference different software modules can be integrated together it could be app like the data usage transformation into different low-level or high-level aspects like just to depict what we have is a three-layer actually let us draw simple mention the first player is talking about the app application second one is middle one middle layer you can also call it as a wrapper or you can also call it as a driver level etc the third one will be the actual hardware so we have a scope for integration into aspects what are those one is between these two this and this this and this other one is between this and this so the one between this and this as well as this and another application so we know that applications can be multiple right between application to application or application to another subsystem in case of any sub-process or partition the apps or autos components likewise you may have so all this will be called software software integration whereas the other part where you use the hardware and software involved such as application to drivers here application could be a middle layer or wrappers which will interact with the driver so this is called hardware software integration please remember that two aspects of software integration software software integration hardware software integration both have to be considered and taken care while doing the integration testing some industries what they do is they may not have the segregation of hardware software and software software they might have a purely software software they take care of the small device device drivers interfaces signals and all this between the software itself they do not have that configuration they can call it as a in general integration software or software integration but also the industry we have like aerospace or we have hardware to software integration software to software integration both are very important so integration covers both the aspects that is what this means integration covers both hardware and software the next one the integration strategy depends on availability of the integration parts that means if any subsystem library or apps third parties are software as a memory or any signal equipment etc so that availability is very important for doing the integration because we need to integrate them also as part of the complete embedded system the next one is the size of the system that means what is the size that system has how it can be broken up further include different integrated or modular elements so that is all driven based on the size your size means not the lines of code please remember as I said in my earlier class that size is not the LOC or lines of code it is the structure and the complexity of the system that is underneath the test of the integration software testing so that also matters in terms of working out the integration strategy the next one being the weather it is a new system or an existing system with added change so we know that the system is working stable and qualified and we want to enhance it or you want to modify it or we want to add some features so that information is also important in terms of integration so that the strategy can be one then the features of the functionality that is also important so what are the various features that needs to be tested like features could be extremely triggered or all these matters so basically a system knowledge is very much important in terms of hardware software integration or software integration is a very key element of the embedded software testing the integration testing the last one being the architecture you know that architecture basically has all the modeler and different blocks and cases use cases and sequences and classes and all that information so that is also very important in identifying the integration test testing strategy okay so we will move to next so from the web but I have collected some of the important embedded software integration definitions system integration the other aspect of the integration so we have studied about software hardware integration software it can also be called as the embedded system next one is the embedded software integration software the third being the system integration where all the individual complete components like external memory internal memory external signals on field related inputs in terms of firmware hardware so all this will be put together as a complete black box and tested that is called system integration it is also can be called as system testing but basically they define system integration that is third level of integration before that software integration and hardware integration complete system integration the task of creating a properly functioning system from its constant components so what are those constant components one is hardware other is firmware other is software so all these are constant components of the system integration the next one being the system hardware integration are the components wired together correctly that means whether here wired means not the we are going to check the harder part as such in terms of any wiring soldering that is not the purpose once that is fine we are going to make it validated make it sure that we are able to interact with those wired components that is all hardware or plug-ability aspects whether you are able to interact read and write through the memory and read and write to the memory or the external communication with a specified border rate and specified speed all these aspects are important just wiring may not be sufficient it has to be done appropriately such that we are able to do the interactions in a intended way what specification or the requirement talks about so that is what the system hardware integration does the next definition is system software integration is typically assumes hardware integration is largely complete is the above part is almost done the initial step before acceptance testing and deployment so this is the last step they say but during the software integration is also one of the type we do for putting all together the build the compiled software piece into the completed hardware so that is what we do with the system software integration so we have hardware hardware hardware software hardware software and complete system so these three levels of integration testing we will do it the next thing of the integration so basic of the integration what are the things that we are going to take care of this primarily what I am trying to put here is integration itself is an activity this can be taken credit from the testers perspective as well as developers perspective definitely developers will have to follow some of these strategies or elements of the integration like you need to take care of software software software hardware involvement but its focus will be from the developers point of view whereas testing testers perspective is from unit perspective in terms of integration and how they are integrated and how we can make it fail or what are the injection in terms of error or faults that we can try so that the maximum performance will be done so integration testing basic steps are as per below create a list of all software components as I said we live with different components in the earlier example slide I have put about 12 components so what are the software components that we have the next step is identify the grouping and dependent between each of them so once we identify different components identify the grouping aspects like how these individual components are coupled each other and what is the dependency of each of them because a one functionality or couple of functionality or functionalities cannot be implemented definitely we have to break it down into individual software components so we need to identify what is the dependency and the intricacies in terms of the grouping between each of them that is another aspect that we need to identify then in the next example I think what we are going to do list out the strategy to perform these categories of integration that means we have identified the grouping and the dependencies how we are going to test this grouping how we are going to test these dependencies between each of the couple that is what the strategy the strategy will bring out all the aspects of integration like hardware software software and system software or the system integration to perform these categories of integration so basically the list should identify the category of integration such as well let me the category of different categories of testing strategy so what are those functionality performance system or structural integration we have a database we have interfaces we have control security or safety conformity so these are some of the steps that are to be taken care so I will just try to draw a small table here so what we do with this is we will try to identify the various list various integration aspects first provide the list of all software components they want to identify grouping aspects they want to identify strategy then may be in another column we can have category so these four things are first identify in a typical integration test strategy tool or a sheet I would say this is basically a identifier which identifies these aspects what are the steps that are involved for integral so first we are going to create a list of software components so this will list right I am just trying to draw an example of how we can restore the steps so first thing is you create a list of component like we did there M1 M2 M3 we have M2 right in the earlier slide so we are going to group together so maybe we can group M1 M2 M3 M4 as one group then M3 M4 M5 M6 like this so we are going to identify group with that name group 1 group 2 likewise we have group N so how we are going to group perform the grouping is basically identifying the similarities of different software functions is how they can be grouped and the dependencies that each group or the software functionality is that it has is one of the identifier with the help of that these two columns are next for each of this group what kind of a strategy I can have what kind of integration strategy I can have whether this can be done with the functionality in terms of externally injecting some values and this can be done with the help of any tools in terms of memory or in terms of speed or communication aspects this can be tested with a large database and any database modifications of different types of database that we can use all the strategy will be part of this third column called strategy and this strategy strategy will have its own type of test environment type of testing aspects like strategy 1 strategy 2 3 4 etc we have strategy N so for each of the strategy what kind of a category we can make like whether it is depending on the hardware software any tool likewise we can have a list like what kind of a category this category has a sub system dependency then any database or database automation we need then we need any interface or signal specific inputs for this strategy all this will be listed so with the help of this we are going to conduct the integration so these are some of the main basic steps of the integration testing okay the list should identify the category of integration such as functionality performance so system of structural integration database interfaces control security or safety conformity etc conformity is something like whether the integrated part can be come confirmed with the values of whatever the intended inputs similarly safe security and safety aspects something like if the requirement says within this limit this has to behave it has to behave and upon certain security threat they should lock those kind of a requirements can be there that also needs to be taken case taken care while doing the categories of integration so each category will have its own sort of inputs conditions and expected results against that we need to write the test cases and draw out the integration test procedures and execution that is what it means okay so we have seen the definition of integration we have seen the integration basic steps software integration will send what is our goal basically to expose faults in the interfaces and the interaction between integrated components that means it is not just enough to find out the faults but also to see the interfaces are properly behaving and interfaces are properly giving in terms of speed performance any issues in terms of a full load not possible or it is collapsing after some time durability all the suspects will be exposed that is one of the integration objective next one is to find the collaboration and interoperability problems and isolate the causes that means interoperability operations we are going to have along with the external systems also system how it can interoperate with those systems is what we are going to find out while doing the integration testing also see the collaboration of different components as we have studied in the earlier slide the next one is to reveal interface and cooperation problems as well as conflicts between integrated parts so it is very important to identify the intention of the different integration parts why because those parts are basically developed by different people and if he has a different perspective in terms of requirements understanding and he would have implemented wrongly or he would have objected those modules wrongly so all these conflicts in terms of requirements would come come out easily when doing the interface and cooperation testing in terms of software integration why I am telling this is because we cannot point out the fault in terms of integration as well integration alone but it could be a problem in terms of specification or design also so all this will be directly or indirectly identified if any flaws are there the requirements or the specification or the customer inputs those conflicts will all will be brought out while doing the software integration so these are some of the software integration goals and objectives okay so now testing types we have seen the levels like hardware software software software and system software integration how we can achieve those and what are the types that we have and we can pick up any of this or both of this or all of this depending on the complexity of the embedded software system but all of this have their own advantages and disadvantages the first one is the big bang integration the next one is a bottom-up integration and the last one is the top-down integration so we know that we have different modules and the components how we can integrate like what aspects of integration we can take care whether we can start with the lower level or we start with the higher modules or we can directly attack the entire bundle so all this will decide in terms of the integration testing type definition so based on that we can categorize the testing types as big bang integration bottom-up integration and top-down integration we try to study each of them in brief big bang integration the strategy can only be successful if a large part of the system is stable and only a few modules are added the system is rather small or if the modules are tightly coupled and it is too difficult to integrate the different modules stepwise so big bang integration basically this is not used very heavily I would say in the industry but in the industry where we have difficulties in terms of integrating that individual modules or if it is the individual modules are tightly coupled or it is too small to test it integration level what we do is we will go with the big bang integration where we will put together those modules and the small modules which are apart from the main modules together and we will try to integrate we will bang it in terms of feeding the values on the field or on the simulation of whatever the testing element that we have that is why this strategy will be applicable for those kind of systems so the last part of the system is stable I mean we know that the system is working we do not want to break it but some features or some modules are added or some components have been taken out or modified so what we will do we will verify that data interface or that aspects which are being added or modified only so we take with the big bang integration strategy for those basically and the system is too small as I said we cannot disintegrate and difficult to test it the modules are tightly coupled so that we cannot make it apart and it is too difficult to integrate the different modules stepwise you start with the module 2 3 4 then 5 6 7 like that so it must happen that 2 3 4 we can disintegrate whereas 5 6 we cannot we have to test 5 6 as together when it is integrated the higher level with 2 3 4 or any other modules those kind of a situation what we do we will test it as a whole that is called big bang integration the next type of software integration testing is bottom-up integration here what we do is okay so there are few words for big bang integration after all components are unit testing we may test the entire system with all its components in action that is what the integration testing does may be impossible to figure out where to fault occur unless faults are accompanied by component specific error messages that means here with this meaning is we may have to take the credit of components so what will happen is component testing we have some errors right so component testing where we have issues or faults or if any pass fail situation is there so we will also consider that while doing the big bang testing because we are not sure if we face some issues or faults as we have not disintegrated completely so but still we see some issues or faults are occurring so what we do we will focus on the individual components and we try to attack the complete target in terms of big bang integration that is what we do with the big bang integration there is a meaning so the next type of software integration testing is the bottom-up integration in this so what we do is basically we take up the low-level or the low-most models we start with that and where the minimum dependency there is dependency with other components are there we start with that and we will do it one by one step by step and we do the higher-up basically this is very useful in the systems because it could be anywhere and it is easier to identify when you start with the lower-most part so that the higher-level models are easier to integrate at later stage that is what the usefulness of the bottom-up integration starts with low-level models with the least number of components using drivers drivers not the higher-level drivers the drivers for the models itself test drivers that is called here we have a stubbed caller which calls for the intended low-level model and the expected results are expected with that drivers and the report will be generated during the test drivers the report will be generated during the test drivers the report will be generated with the help of printf or whatever this but see it is the same as the component testing how do how we do with the instrumentation but it is then at functionality integration level basically because the intention is to integrate on the lower-level models to the higher-level that is the idea the integration can start very early in the development process why this statement is produced the development process we will be done with implementation of the lower-level layers and still the complete integration is not done so without the development team is done with the complete integration of the entire system it may be difficult for us to do the top-down integration aspect so this can be started as well as the lower-level model so that is a good thing about bottom-up integration and also it will lead to an early detection of interface problems and these problems can be isolated easily so before we attack the complete system as an entity complete entirety it is better to start with the lower models identify the interface issues and the integration issues so that the higher-level issues are less but the disadvantage is that many drivers have to be used in carrying out the strategy and it is tedious you can understand this why because we are attacking from the bottom most layer of the embedded software system where we target lower-level models and there are numerous lower-level models and each models will have their own dependencies and identifying that working with strategy testing each one of them is definitely a time-consuming and that is the disadvantage of bottom-up integration if there is a scope money and resources are available I would suggest to follow this type of integration in a system where it is not very complex it is more modular complex and this model moderately bigger not very big medium sort of embedded system this strategy can be used as per re-experience so this is referred basically from embedded software testing book by bark bark brokman and Edwin, we will take an example how bottom-up testing is done this is basically from the web source see you take there are two level or two layered architect architecture design is there and a is the higher-level component b and c are at lower level how are you going to integrate with the help of bottom-up integration test okay the first step is test bc individually we are going to test it that means first we are going to verify b but we are going to verify c so with the help of drivers that means drivers means test drivers for example driver c we call the c function with parameters and data whatever it is that is intended for calling the c and once individually we are done with this most it is done with the level of component level the next step is test a such that it calls b so we are going to test it a to make sure that it has to call b so that we know that the interface between a and b are verified similarly test a such that it calls so that the interface between a and c are so if an error occurs we know the problem is in a because we already tested b right in the first step or in the interface between a and b so the error could be at a or a and we know that we do not have issue with a b because only we have tested with individually at a lower level and now we are trying to test a and we are going to call with the test driver such that a is going to call b and a is going to call c and if we find out an error or a fault we are sure that there is no problem with b but there is a interaction problem either a is calling wrongly b or b is not getting called properly or there could be error within the a so that is how we bring out the issues in integrating a and b similarly once we are done with a and b we are going to call a testing such that any interface between a and c are tested along with any issues in the a side so this is how we take care of integration testing from bottom of aspect so the problem is we are going to test it after b and c are done by a that is what an 80 point about this bottom up testing next we take up the integration testing top down approach what we do with the top down approach it is exactly the opposite way of doing the bottom up so what we do we start with the top most elements higher level and reach the lower level so it has its own advantage and it has its own disadvantage what are those we will try to control structure is developed in a top down sequence so the inter structure of the flow or the sequences that is being used in the embedded soccer system is being developed and those will be used for top down integration sequence testing so at every new level the connected modules at the corresponding level are integrated tested that means we start with one level at a higher up and as we progress we are going to connect the next level next level next level elements or the modules one by one and we are going to test it we are going to integrate and test it non-existent modules is input with steps so if there are as I said in earlier that slide we have seen the complete models would not have been developed so but still we have the higher level models but those models sub level models we can stop it and we can test it stopping is also useful when we are not able to provide a different negative values for the higher level values so that the system can be modified very tested for the different types of instrumentation advantage is that an early look and feel of the entire system can be achieved this is what the very important aspect of embedded software testing integration to understand the system how it behaves based on the knowledge that we have or the complexity that we understand the best way to test it is just completely put the box under the various conditions tested from an independent view how it is going to behave as per the expected system behavior so then pick up the individual modules individual functionality and try to understand where it is going to reach where it is going to take up the lower in modules so that we have an understanding of the system we have a look and feel of the entire system but that is the great advantage of top level top-down integration testing this is typically important where we have a larger or very complex embedded software system so but too huge or too large complex system they basically then they can divide also to conduct both levels of integration testing they can either do both of them the bottom-up as well as top-down like in that case what would they do is they segregate the different pieces of the software accordingly so that is how they take care in a larger complex systems but both of them have to be done meticulously it is an advantage is that impact on lower level modules may lead to changes in top level modules and number of steps needed to test every integration stuff so here also stubbing is important why because some of the unimplemented modules or some of the modules needs to develop with the help of the steps so those steps will have to be developed more and there is a disadvantage and it may impact the low-level modules because low-level modules would not have taken care so that could lead in terms of changes in the top-level modules so that is a disadvantage so basically we use the stubs in top-down integration and use the drivers in bottom-up testing example testing integration so we will take up an example the same example where we have three main modules ABC with an example how it is going to be tested integrated integration tested with the top-down approach okay the first step is test A individually use stubs as I said for B and C that means definitely we need stubs because A needs to call in one of the executable that it has executable line that it has so we are not going to be or we do not have B so we are going to have a small stub which is similar to actual B and similar to actual C so first we will test A individually whether with this stub it is fine or not with the help of B and C stubs then we are going to test A so that it calls to stub for C so this is very important because A is going to work along with B and C and it can call B or it can call C each one has to be tested with actual B and the other one is stub when we are testing C the B is stub that is the third step test A such that it calls C the first time it calls B sub second time it calls C the first time we want to have the same stub for C the second time we are going to have the same stub for B so that we know that the working behaviour or the actual expected output is same in all this that is what the approach so if an error occurs we know that the problem is in B or in the interface between A and B so we know that while doing the integration testing definitely there could be an interface issue or the issue is definitely with the stubbed part because we have stubbed it and A is getting called and we are getting the error so if an error occurs we know that the problem is in B or in the interface between A and B similarly that the third step is test here such that it calls C with stubbing B and if there is a error we know that the problem is in C or in the interface between A and C in terms of calling mechanism or whatever it calls so this is how all the errors of A B C and A to B A to C will be brought up so that is what we do or we will bring out the top down integration issue this is exactly the other way of doing here here what we do we start with B and C and we will identify the interface issues either in A or in the interface with the help of B and C here we use the drivers drivers are at the A level because that is going to drive B and C so in top down it is the other way we are going to do with with the help of stubs in B and C. Stubs are used to simulate the activity of components that are not currently tested and disadvantage is that you may require many steps that is what is going to happen in top down integration testing this is an example okay so overall integration testing of top down and bottom up advantages and disadvantages we missed about top down advantage is that the drivers are not needed or only the simple ones are required because the high level components that have been tested serve as main part of the environment the disadvantage is that low level components must be replaced by stubs this can be costly because there is a definitely effort and cost involved for developing the stubs by the team and team has to have a knowledge of the B and C for developing the stubs and the bottom up advantage is that no stubs are needed because we are going to drive it in visual modules but disadvantage is that high level components must be simulated by test drivers so in bottom up we need drivers top down we need stubs so it is up to the test strategy team or the test plan team or the test manager or the test lead to decide what sort of a strategy is going to work for the particular embedded software testing it again depends on the various factors as I said the complexity functionality performance subsystem top down integration databases what sort of a database it has whether we have a confidence that it will work or we need to test for each of the data with the help of all that boundary value analysis partition equivalence etc and control how the control flow is there for the entire embedded systems what are the security aspects or the safety aspects all this need to be considered for deciding the bottom up or the top down integration we can have both as well does not matter or does not impact in terms of standards or any compliance both can be taken care okay so we need to plan accordingly for a indefinite so what is the importance of planning the integration is that by enabling successful integration with critical factors such as objectives responsibilities and source planning so basically it will enable we will have an impact on the outcome of the project or product lifecycle because without integration we do not know what is going to behave in the field or with the customer so definitely it is very important and it has an impact on the total outcome of the product of the life cycle so this is one of the critical part of the product or project lifecycle of the embedded software time resources and personal are identified for planning that are enable that enable successful integration so as part of the planning of the integration testing based on advantages types of the integration testing the time resources planning the personal planning or the tools all this will be identified so without having the integration we cannot identify this so we need to have a planning for the integration and conducting the integration that is where the importance of the planning integration so integration considerations what are the aspects that we need to consider for integration system decomposition how the system is decomposed basically this is drawn from the design or the architecture it could be higher level architecture or low level design then we need to have a architectural consideration is in terms of open or closed that means the architectural elements can be open or be closed in terms of the downwards layers and integrated or modular that means the modularity is required or the integrated parts as a whole is required all these considerations we need to take care for doing the integration testing and the interfaces how the system is going to interface externally internally or the subsystems or the partitions applications etc then we need to understand hardware considerations we need to know what sort of hardware is used whether it is a real target or evaluation board all this will have to be considered and tools of course that tools can be having a hardware dependency or hardware simulation likewise we need to have this very much important particularly in a bigger systems where we have a automatic testing equipment it is so hardware consideration is one of the important element of the integration testing HSIT it is called as hardware software integration testing software considerations where we need to consider software components such as algorithms there could be a check sums or it could be a stringent computations all these have to be considered so that is where we do the planning of the integration software testing okay so we will continue in the next class in terms of integration test strategy and other aspects of the software integration testing


Environmental human rights defenders across the globe are upholding human rights and promoting knowledge and practices that ensure the environment and people's well-being. Among defenders, women especially strive towards more equitable outcomes of mobilization, building on their individual and collective experiences of inequality. Gender-biased laws, policies and norms affect women's daily lives and their environmental mobilizations. By denouncing and overcoming these challenges, women and environmental human rights defenders actively challenge unequal power structures. Thus, they contribute to transformative resilience, resilience of communities to prepare for external shocks and tackle the internal shocks from pre-existing inequalities. Therefore, it is crucial for actors to support the defenders' efforts and together contribute to transformative resilience.


White toddler, three, being, racially bullied, by her black neighbors. A shocking video was captured of a three-year-old toddler allegedly being, racially bullied, by older children. The footage sparked an uproar after it was posted to Facebook. Mackenzie Peterson Mackenzie Peterson with her father Sean Mackenzie Peterson was identified as the three-year-old white toddler who appears in a video that frequently makes its rounds on social media, sparking an uproar and outrage each time it emerges once again. In the disturbing footage, Mackenzie appears to be, racially bullied, by her slightly older black neighbors. Two clips of the incident were originally uploaded to Facebook entitled, When White People P Asterisk SS Black People Off, and they captured a heartbreaking scene.  Two older girls hit, push, and verbally abuse Mackenzie Peterson on video. It was later learned that the older boy, who's heard encouraging the bullies, was the black girl's 12-year-old brother, who shot the footage and uploaded it to Facebook, where it quickly went viral much to his family's dismay. Viewers, who watched in horror, quickly became outraged, calling the video's evidence of racism. A torrent of threatening calls was unleashed on the parents of the bullying children, who had no idea the incident had been filmed and posted online. The black children's dad rushed to apologize to the parents of the victim, who were equally clueless that the incident had even occurred, Daily Mail reported. Both sets of parents have said that there is no problem and everything has been settled amicably, denying that the incident was racially motivated, but some find that a little hard to believe after seeing the video. In the footage, the two older girls yell, you ugly, at the toddler as she sits on her plastic tricycle. Mackenzie is also seemingly spat at by one of the girls, who was later identified as a five-year-old neighbor. Another girl grabs Mackenzie's own hand and uses it to make the toddler hit herself. Why You Hitting Yourself? Why You Hitting Yourself? asks the 12-year-old brother of the bullies as he films the incident. Mackenzie is bullied mercilessly by the other girls until she's brought to tears. After Mackenzie begins to cry loudly, the bullies leave her in the middle of the street on her tricycle, but the incident doesn't end there. In another clip, Mackenzie is seen off her trike, still attempting to play as one of the girls says, hit her hard and slap her head like this. One of the girls grabs Mackenzie Peterson by the hand and uses it to make the toddler hit herself. In a gut-wrenching scene, little Mackenzie attempts to share a toy with one of the older girls, but the older boy interrupts and tells his sister to throw it on the ground. Listening to their brother, Mackenzie's tormentor throws the toy the toddler selflessly offered her onto the ground, causing the girl to cry and run to pick it up. As she bends down to pick the toy up, the other girls rush over to hit her. The footage was initially posted on Facebook under the name, Ray Wright, which turned out to be a fake account set up by the 12-year-old boy. When the video began to go viral across the Internet, the parents of both children were identified, and both, Eddie, the father of the bullying children, and Sean Peterson, Mackenzie's father, were upset by what they saw, and they weren't alone. One of the girls shoves Mackenzie Peterson in the head. Angry people began making threatening calls to the father of the black children. According to the dad, who's been identified only as, Eddie, to protect his identity, he has no idea where his children learned such behavior but added that they have received appropriate punishment for their actions. He also said that, after viewing the video for himself, he apologized to Sean for what his children did to Mackenzie. Prior to Eddie's apology, Sean had no idea the incident even took place. I wasn't happy with the video, obviously, Sean admitted. I am disgusted with it, he told Fox News, but both Eddie and Sean said they were dealing with the problem. He's taking care of it. Trust me, Sean said, adding that he trusted his neighbor to do the right thing. He's a good father and everything like that, so I'm not worried about what he's doing over there. Sean Peterson said he trusts, Eddie, to do the right thing. As for the allegations of, racial bullying, Eddie said that is not the way his children were raised. I honestly don't know where it comes from. We don't teach that in our household, he said. We're not racist, none of that, he added. Daily Mail also seemingly dismissed the, racism, reporting that, while the video mentions the race of all the parties involved, at no point as any racial language used by the bullies towards the little girl. Further refuting any, racism, claims, Eddie and Sean said that their children usually play together and claimed the incident had been blown out of all proportion. She's not that way, Eddie said, referring to his five-year-old daughter who bullied Mackenzie. You can see she's, there, clearly getting coached through the whole situation, he added. When I saw it, I was disgusted with the video, very disgusted. Eddie, was disgusted to see the way his children treated Mackenzie Peterson. Indeed she was coached, by her brother. Addressing that issue, Eddie said his son was disciplined for his role in the incident and that his internet and television privileges had been being taken away, but is that enough? This boy, regardless of where he learned it, displayed some very disturbing, hateful behavior. Whether, racism, was the underlying reason for it or not, he needs some help before he influences others the way he did his sisters. Parenting does matter, and this was a fail in many aspects, even if we believe it wasn't, racist. Not a single adult knew this happened until video emerged. Think about that for a second, kids were playing in the street, one of whom was just three years old, without any adult supervision. She got bullied and beaten, and none of the children were troubled enough by it to tell their parents. Then, there's the 12-year-old with seemingly unrestricted access to a phone, internet, and social media. We can debate whether this is racism, but it clearly indicates a lack of parental supervision, and we should all agree that parents need to do better.


Coming up on DTNS, the U.S. proposes making third-party app stores the law. NVIDIA faked their CEO's appearance in a press announcement with AI, and football star Lionel Messi got paid partially in NFTs. DTNS starts now. This is the Daily Tech News for Thursday, August 12th, 2021 in Los Angeles. I'm John Merritt. And from Studio Redwood, I'm Sarah Lane. And I'm Roger Chang, the show's producer. Joining us, Bloomberg Tech Editor, host of Tech's Message. Nate Langston is back. Welcome back, Nate. Thank you once again for having me. Great to be here. We were getting an excellent description from Nate about the tech behind his drum set. If you want that and more, get the wider conversation on our expanded show, Good Day Internet. Become a member at patreon.com slash DTNS. That is also where you can join our top patrons like Dan Boyles, Logan Larson, and Mike Aikens. Let's start with a few tech things you should know. Provisional findings from the UK's competition and markets authority investigation into Facebook's acquisition of Giffy would negatively impact competition between social platforms. The CMA, as it's known, could order Facebook to unwind the deal and sell off Giffy if its final report confirms these initial findings. The CMA will take comment until September 2nd before issuing a final report on October 6th. Facebook's going to change the name to Jiffy right before it spins it back up. Honor announced the Magic 3 series, its first flagship phone series since spinning off from Huawei. The Honor Magic 3, Honor Magic 3 Pro, and Honor Magic 3 Pro Plus all have the same 120 Hertz OLED screen and feature Google services. The Magic 3 Pro Plus offers a Snapdragon 888 Plus system on a chip. 50 watt wireless charging has an IPX68 rating for dust and waterproof and top shelf cameras while the Magic 3 Pro uses a smaller main image sensor. The standard Magic 3 uses the Snapdragon 888 is IP54 rated, laxes zoom lens, and the Magic 3 starts at 899 euros, the Pro at 1,099 euros, and the Pro Plus at 1,499 euros. No release date or markets were announced. Twitter began rolling out visual changes to both its site and its apps. The new chirp font is now being used on the app menus and feeds and colors have been updated to be high contrast with a lot less blue. China State Council issued a statement calling for guidelines through 2025 to produce legal frameworks around the digital economy, internet finance, artificial intelligence, and big data and cloud computing. In other words, the crackdown will continue. And the beat goes on. Chinese autonomous driving startup Pony.ai suspended its plans to go public on the New York Stock Exchange after it failed to gain government assurances in China that it would not be targeted for doing so. In positive news, though, Baidu grew revenue 20% on the year driven by its AI business. Foxconn reported a 30% rise on the quarter and 20% rise on the year driven by smartphone sales, though Foxconn did warn about some uncertainty related to worsening COVID-19 in parts of Asia. Spotify announced it will release an updated Wear OS app in the coming weeks with support for offline playback. This will work on Wear OS 2 and newer releases, though it does require a premium Spotify subscription. Alright, let's talk about that US bill, a bipartisan bill. You got one Republican, two Democrats sponsoring this called the Open Markets Act proposed in the US Senate Wednesday would impose new rules on app stores. The rules would apply to any app store, not just mobile, any app store that has more than 50 million US users, so Google and Apple. It would prohibit those app stores from requiring developers to use its in-app payment system. It also would not allow those app stores to prevent developers from having different prices in different app stores. Right now, app stores may say like, you can't sell this for cheap or somewhere else. It also would not let app stores prohibit legitimate business communication with app users. Apple has some restrictions on what you can say to your customers if you're in the app store. It would not let app stores use non-public information to compete with app makers in its store and third-party app stores must be allowed, as well as the ability to hide or delete pre-installed apps. And app store operators can't prefer their own apps in app store searches and must make all development info that the company uses for its own apps available to all the developers. Those are all the things in the bill that's being proposed in the US to become a law. If it passed, the act would put the US Federal Trade Commission in charge of enforcement, so it'd be an anti-competitive measure essentially. We don't know if it's going to become law. What do you think guys, should it become law? I think it has a very, very, very low chance of becoming law from my understanding of US politics. I think it will take a long, long time to pass through and then would be challenged all the way, as we've seen, obviously with the Epic and Apple and Google SPAT. But it has to be said that this is not something that any one government is solely going to be looking at. I know that our consumer markets authority, which was mentioned at the top of the show with regards to Giffy and Facebook, they have a probe going on that's similar to this. It's not so much a proposal of a bill, but a review of whether it's anti-competitive that's going to conclude, I think as soon as next month it's been going on since the spring. I think it would be very difficult to enforce, very difficult to police, and it would open that floodgate of how do you implement this on a country-wide and then international basis in a way that's different for each market, if you don't know me. It's very difficult. Yeah, I think what we're looking at here is the opening salvo in a war. Honestly, if left to its own devices, because it's a bipartisan bill from the start, this could get some traction, but you're going to have the full weight of everyone's lobbying, not just Apple and Google. You're also going to have Facebook and Amazon saying like, man, we don't love this idea either. Even though Facebook would like Apple to implement these things, Facebook doesn't want the same restrictions to apply to it. Should it want to qualify as the Oculus store? So I think the lobbying probably keeps it from becoming a law, but it starts the conversation. It starts the pressure. I think that's why the senators did it, to say like, look, we could do this. So you might want to compromise on something else. And you have to pay an attention to consoles just quickly as well, because they I think would apply under this too. The game stores on Xbox, for example. Yeah, I might. You're right. So Microsoft and Sony might have it. As somebody who hasn't downloaded an app recently, I kind of have the apps that I use, and that's what I use. It's easy to sort of go, oh, okay. I mean, how big of a deal is this really? And so I was going through this as we were preparing for the show. Is there anything in this proposed bill that sets off red flags? And it really doesn't. None of it really does. Like you said, Nate, it's probably a long shot of it being passed in its current form. But none of none of this is, I think, unreasonable or some sort of too much government oversight that I can see. I don't like the principle of the government deciding that at a certain level, a marketplace has to operate this way. I wonder if I don't. I haven't thought through what the unintended consequences are, but that's where my head goes in these sorts of situations. I'm sure somebody out there is going to do the work on that shortly, but there are always unintended consequences when you say like, look, we just want to let third parties on the platform and do this. Could it also harm developers in some way? That's what I'm always looking at. Well, moving on, Zoom announced a new focus mode for its desktop, and it's also its web app, which will let the host of the call hide video of participants on a call from each other. The feature can be enabled for accounts or groups or individual users alike. It's primarily aimed at classroom uses to stop students from distracting each other. So hosts, and in many cases, this would be teachers, will still have access to all participants' video and can spotlight participants to let everybody see their video temporarily if they so choose. Makes perfect sense for teachers, right? Yeah, you got goof-offs like me in the class, trying to put up funny gifts in the middle. I could totally see myself having done something like that back in the day. So this is a way to keep everybody's attention. My brain immediately went to, what other things are they going to use this for? Like our corporation's going to say like, oh, for all hands meeting, we'll use this to make sure everybody's paying attention and they're not distracted. I think there's some positive use cases too, where we've talked about before, the wearing effect of knowing everyone can see you, even when you're not speaking, this could be a relief for some. Yeah, my mind immediately went to that boss that's just micromanaging every single thing you do it on the Zoom call. This might be something that's great for the boss, not necessarily great for the people who work for the boss. But yeah, it does seem like for classroom uses, and I know some teachers who have had a real hard time over the last year plus, trying to navigate, especially with younger children, conducting a classroom experience that is enriching for kids who are easily distracted. And this makes sense. I can see it being done in the corporate world as well though. I was trying to think of an example of when that would be necessary, where you needed to hide two employees from seeing each other. And other than getting fired over Zoom and having the HR people on the call, I couldn't think of an example unless someone's doing something on the camera that they shouldn't be doing, but then there's a whole different procedure for preventing that from being seen. To me, it was the large meeting where everybody doesn't need to be seen the whole time. That was the only thing I could think of there. Also, the Verge notes that emoji's are still allowed by the kids. So you could still send your cowboy hat and skull emojis to distract your friends. Yeah, it's like throwing a spit-wad. The modern-day spit-ball. Is there an emoji for spit-ball? I don't know. I think there really should be. We should talk to them. I'll probably get them wrong if I try. Apologies to the sporting savvy out there. Bear with us, but for those who don't follow football, you should know it's biggest star, Argentinian Lionel Messi, just left the club he's been with for most of his career, Barcelona, to sign a two-year contract with Paris Saint Germain, often referred to as PSG, and that's how we'll continue to refer to him here. Why, you may ask, are we telling you this? No, it's not an attempt after our previous victory in interesting Nate in sport during his last appearance to make him love the beautiful game. It has to do with NFTs. You see, big sports stars get paid big money, and just the welcome package that PSG gave Messi was worth 25 to 30 million euros. I would like a welcome package like that. It included some PSG cryptocurrency fan tokens from Socios.com. These tokens let fans who hold them vote on some minor decisions regarding the club, like what song is played in the stadium during warm-ups, or the message that'll be on the captain's armband, for example. Socios.com says the sale of the tokens has generated close to $200 million for its partner clubs this year. They've got a good half dozen or so partner clubs. And of course, fans who buy them can then try to sell them for more than they paid them for them. And there's a brisk business in that. Trading volumes before Messi signed with PSG reached $1.2 billion. So giving Messi a bunch of them gives him a volatile asset that he could potentially sell for millions. And these things are benefiting PSG as well. The PSG fan token generated 30 million euros in sales this past week. And it's estimated PSG keeps about half of that, if not more. So NFTs, everybody's like, what are they good for? Well, they're good for moving money around and apparently paying your major superstars. Wow. I mean, if anything was going to get me interested in sports, I suppose it was this. As far as, I mean it, so he was getting like a signing bonus awarded in NFTs, right? So it's kind of like getting given stock when you join a startup any company. Sure. More of a question than a statement. Because it seems like broadly speaking, it's equivalent to that. It's not the same because the stock is a more, there's a less volatile, you know, instrument. That's all. I mean, that was going to be my point is that this, as far as what's his name, Messi is concerned. This is like having a very volatile signing bonus. It's not the majority of his bonus. It's a throw in, right? They're like, because we don't know how much of his welcome package was that, but one expects it wasn't the majority of it. True. I just think, you know, if, if, if Socio has said, what did it say, says the sale of tokens has generated close to 200 million for partner clubs. I mean, this isn't small money. And I can only imagine if this was part of a deal that got him to leave a club, like it must have been a decent part of it. Anyway, that was my first thought. NFTs is a signing bonus. I've heard of Bitcoin, you know, crypto being given as signing bonuses at companies I've written about. And particularly in obviously the crypto world, it's, it's, it's quite common. If you've got a new coin, for example, you're doing an ICO, then that can be quite lucrative. But yeah, first time I've seen this in sport. So great. Still don't care about football, but care about this. Again, let's make it clear. This was not to try to convert Nate to loving football at all.  You know, if you don't like sports, what then maybe it doesn't apply to you, but lots of sports. I mean, there are especially for stars of Messi's size. And that is, I don't know. He would even put in that category.  But to have a signing bonus, where you're getting so many millions of dollars. And, and that's all great.  Well, that's probably not going to make you any worse of a soccer player, you know, but it might be something where it's like, oh man, why did I agree to this kind of thing? And I wonder how much this sort of thing will just be a fact of life for, for the big sport stars in the future who sign these kinds of agreements. Yeah, there were a couple of the technologically interesting parts of this article that don't even have to do with Messi, just the idea that here's an NFT, kind of like we've talked about with bands in the past that gives you a something, you give you a right to do something, right? It's not just, oh, I pretend I'm the owner of the video of Messi's great goal. It's, I get a voice in some of the ways the club is operated, right? Right. And so, you know, that's interesting. Then taking those tokens and giving them to Messi, Messi doesn't want to vote on the warm up song. He doesn't care. He's just going to hold on to these things and hope they gain in value. And then his manager will trade them at a time when they think they should cash in on them. But, but that's, that's interesting too, if thinking of NFTs as compensation for anything, right? And going back to what Nate was saying about, you know, getting paid in cryptocurrency at certain startups, it's now celebrity compensation.  Like, I could just see that being another element in contracts. Well, folks, if you need just the headlines, sometimes you don't even have the 30 minutes we have for DTNS. Check out our related show, Daily Tech Headlines, all the essential tech news in just about five minutes at DailyTechHeadlines.com. NVIDIA released on Wednesday, the press announcement of the NVIDIA Omniverse system that was delivered earlier this year by CEO Jensen Wang was not delivered by Jensen Wang exactly himself. It was a computer generated version. While Wang appeared to be in a kitchen where he was frequently making announcements these days, the kitchen and the Wang in the Omniverse announcement was created from a full face and body scan of the human ring done in the back of a truck. Then an algorithm was trained to mimic Wang's gestures and expressions. The kitchen was then created by Omniverse. Facial performance used an audio clip to drive the facial performance with software called Audio2Face that mapped the movements of the face to the words. Then they used face video to video, which mapped the CG model to a photo to make it appear as natural as possible. For body movements, Audio2Gesture, the number two, was used to mask gestures to the words. Then an actor in a motion capture suit read past keynotes mimicking Wang's performance. That created the training set of movements, also generated 21 candidates, one of which was implemented in the final product. The kitchen and also Wang were done in Omniverse and other tools like Maya and Substance were used for adding textures and that sort of thing. In the end, it's what you would do for a movie effect, something that's a big special effect. Done by Nvidia, though, in secret, so they could put this out as a surprise blog post. Guess what we did? No one even knew. But one quote in the Nvidia video does stand out. Nvidia researcher Ming Yu said, quote, as an AI researcher, I come from a machine learning background and I was not familiar with the movie production pipeline. An important thing for me was to feel the pain. How difficult is it to create a digital human? And to kind of challenge myself, how can we create tools to make digital human production a much easier process? End quote. So this is a prustunt, certainly, and it's gotten a lot of attention because of that. But there might be a substantive effect here. Yeah, when I first saw this come across my feeds this morning, I was intrigued. I was like, oh, they did an AI generated Jensen Wang. Let's check that out. The more I dug into it, the more I realized, oh, they just did what anybody does for like Black Widow. They did visual effects. They were using their own products to do it and showed out how great their products are. I get that. But it's a prustunt until I hit that quote from Ming Yu that you just said. I'm like, but the fact of having done that means that their own researchers now have a better appreciation of the difficulty that visual effects artists have in their jobs, and maybe that will help make the Nvidia tools even better in the future. I had two thoughts when I read this. The first one was, even as a prustunt, I have to take my hat off and say kudos because it's very cool as a proof of concept. My second thought on this, though, was regarding nobody spotting it. In my head, I would question, did anybody watch it? Did anyone care? Is it the reason that no one spotted because no one really was paying attention to this? I'm sure it's the former. Nvidia is going to say no, it was that good, but maybe people just weren't paying that close attention. I don't know. You would have thought somebody would have noticed something. Also, I'm curious why they didn't just reveal it at the time. I would have think that would have been a dramatic reveal at the end to say like, and by the way, this whole time I was virtual, this isn't really me. And then the real Jensen Wong walks into frame or something. I don't know. I mean, I will add, it was just the 14 seconds for a very specific part of the keynote that he gave. That was the virtual Jensen. Was it only 14 seconds? Yes. If you look at the end of this, I watched the Nvidia blog. Maybe because I was looking so closely, it felt longer. That would be another reason why people might not notice. It's pretty fast. Well, and the whole idea is that they wouldn't notice at all. Right? Yeah. Yeah. Surprise. Yeah. Plex updated its Plex amp music player app to add a feature called supersonic does not involve hedgehogs. It uses a neural network to map all the tracks, albums and artists in your library to generate playlists from your library that will be full of songs that are sonically similar to each other rather than just generated through metadata. So instead of just like, here's a jazz playlist with everything that was tagged as jazz. Oh, that podcast from DTNS was tagged as jazz. It's in your jazz playlist now. It would be actual jazz like songs that are similar to each other. One example, for instance, is mixes for you that would use your most frequently played songs as a basis and then mix in other songs that are similar to those. So like, Oh, if you like these songs, you play them a lot. Here's some other songs that are similar. Now, it's different than Pandora's music genome project. That one uses human analysis supersonic is all software. It extracts 50 parameters, waits them, and then uses those parameters to determine how close two tracks are to each other. The setup is very CPU intensive. So it'll take a couple of days usually to complete depending on your library size. You can then see which tracks Plex thinks are similar to any particular song in a related tracks feature when you're looking at any particular song. You'll need to pay for Plex Pass to get this feature. You'll need to run Plex Media Server version <IP_ADDRESS> in either Mac OS Windows or Linux on an x86 processor. No arm support yet. Well, I'm a big Plex user. I don't really do a lot of Plex amp music listening. However, I do find just with the various quote algorithms that we have on music services at Pandora being one of them. But there are others, you know, that it's sometimes it's like, wow, they really know me. And sometimes it's kind of hit and miss. And that is just the way that it's always going to be when a bunch of humans are getting together trying to figure out what you want to hear next. I would, I'd be really interested to see how much something like this, if I say like, here's my genre, here's my favorite artist, give me other things, how this might give me different results. I'd love to test this out on my library. My, you know, Apple Music, I'm not in Plex, but my library is so weird that Apple Music has a very difficult job of making any kind of recommendations to me. I mean, I'm the guy that true story in the same week once saw Taylor Swift and Cradle of Filth, and I love them both equally. Not playing together either. That's the point of that story. One day, one day. So making a dream is difficult. Yeah. Yeah. I, I know for sure that my musical taste is not as diverse as yours, Nate. And yet I have problems with it going like, here, this is stuff we think you'd like. And I'm like, no, not really. So I kind of like this idea of like, we're not going to try to predict what you like. We're going to try to say like, Hey, if you want more of this kind of music, we know what fits that. Now, it'd be interesting to see how good it is at that. But that's the Pandora promise of like, Oh, I know I like this Jonathan Colton song. Give me more of that. Sometimes it works on Pandora pretty well. Other times, not so much. Kind of depends on the artist. But being able to say like, let's do some more complex stuff. Let's say like your top 10 most played songs, stuff like that, I'd be interested to see how that worked. So you have to, you have to try it out, Sarah. Sorry, you're, you're the one of us that has plex. So I'm happy to do it. Yeah, I'm happy to do it. I don't really know why I don't use plex for music, because I use it to kind of watch everything else. Yeah, I'll, I'll, I'll check it out and report back. Well, if you are interested in traveling to Nate's part of the world this year, or anywhere in Europe really, Chris Christensen has some handy websites that you might want to check out before you do. This is Chris Christensen from Amateur Traveler with another Tech in Travel Minute. If you're planning on doing some traveling in Europe in the near future, which is getting more possible, there are two resources that you should know about. One is Roma Torrio, R-O-M-E, the number two Rio.com. And the other one is O-M-I-O.com. And both of them do a similar thing. They let you put in two cities and find out not just what the flights are between those two cities, but what it would cost to fly, to do rideshare, to drive, to take a bus, or to take the train. And so especially in Europe, where train travel is much more practical, Roma Torrio and O-M-I-O.com are great resources to know. I'm Chris Christensen from Amateur Traveler. We should hasten to clarify, you cannot take a train from Rome to Rio, though. At this point. Yeah. No, you can't do it. Yeah, you can fly it. No, it's a good tip. Thank you, Chris. All right, let's check out the mailbag. This one comes from Nick. And Nate, I don't want to put you on the spot, but I thought you might be able to help us out with this email if you so desire, because Nick says, if you read this email, please use Z instead of Z when saying, you know, that last character of the alphabet, Australian versus American English law. So, Nate, would you like to take it from here? I will read the rest, yes, from Nick. Nick says, continues, I've really come to appreciate big displays built into phones. I was one of those people that were not happy when Apple made the iPhone 5 screen taller, but not wider than the 4S. Since I left the iPhone ecosystem for Android, I've used the Samsung Note line because of the big screens. I would have jumped right on board with the Galaxy Z Fold line when it started three years ago, because simply it was an even bigger screen, but I decided to wait and see what reliability was like. So far, I've not bought a Z Fold. But honestly, if a year from now, the Z Fold 3 owners are pretty happy with the reliability of their device, I'll probably get a Z Fold 4 as reliability was the one thing holding me back. The advancements in this area Samsung announced are very encouraging. Also, I should note that at the department store I work at, which is not fancy or upmarket, I do see people using Z Fold 1s, 2s, and flips. So folding phones seem to slowly be taking off as a thing people buy and use. Yeah, so I think Nick is probably representative of a lot of people, and these are the people Samsung needs to persuade, which is I'm in the Android ecosystem. I'm using a Samsung phone, but I'm still not sure your hinge is going to work. I'm still worried about that crease in the middle of the screen. I'll let a few other people try this first before I jump in there. So that's where they need to do the work. Also, I thought it was interesting that he sees the folds and flips out in the wild. That was interesting to know. Yeah, on our show yesterday, I was sort of like, they seem so great. Certainly the newest Galaxy Z Fold line is expensive, but it looks real nice. But yeah, if you're already in that ecosystem again, then you have a built-in market. And thank you, Nate, for reading that. I know it wasn't Australian English, but it was much closer than we would have gotten. I just felt like it would just be a botched job of talking. I even tried to, yeah. So thank you, Nate. Bollywood would jump out of nowhere and make fun of me for saying Zed or something. That's right. Every time he said Zed, I was like, he did it again. Oh, wow. That's really a thing people do. Thank you, Nate. Also, thank you, Nick, for that feedback. And also, everybody who sends us feedback, we doesn't always get on the show, but we sure appreciate it. And we love to read your feedback. Questions, comments, we'll take it all. Feedback at dailytechnewshow.com. We also want to give a special thanks to Chris Benito. Chris is one of our top lifetime supporters for DTNS. Thank you, Chris, for all the years of support. Thanks, Chris. You hear Chris's name in the Master and Grandmaster list as well. Been doing it for a long time. You rock. You sure do. Chris, you're the best. Also, the best, Nate Langson. Thanks for being with us, Nate. Let folks know where they can keep up with your work lately. Well, if you like the sound of my accent reading you tech emails and technology news, then do check out my show, text message, uktechshow.com. As one of the things we did for patrons that admittedly isn't on the free feed is, turns out my wife put the nothing ear one headphones that I recently reviewed through the wash. And I just recorded an episode about how that went. Badly, but anyway, uktechshow.com. Yeah, I'd be like, how did it go? But, you know, just, it's fine up from Nate. Sorry about your headphones. We are live on this show Monday through Friday at 4 30 p.m. Eastern 2030 UTC headphones or not. Find out more at dailytechnewshow.com slash live. Join us if you can. I'll be off tomorrow, but Tom will be here and Shannon Morse will be joining us as well. Talk to you then. This show is part of the Frog Pants Network. Get more at frogpants.com. The Ireland Club hopes you have enjoyed this brover.


Hello students, I am Dr. Prakash Sarunke from Mechanical Engineering Department from Alchane Institute of Technology, S.O. Lappu. Today we are going to discuss about fuel systems in SI engines, so this will be the second part from the IC engine series. The outcome expected is students will be able to explain the requirements of air fuel mixture at different operating conditions of IC engine. What are the mixture requirements for the combustion? There are two essential requirements for the mixture, supplying device or carburetor. One is that it should meter the liquid fuel in proper quantity to produce the required air fuel ratio at different load and speed conditions. And second requirement is that it should be able to produce the homogeneous mixture of air and fuel which is possible by atomizing the fuel. So what are different conditions of engine operation? Let us try to understand. There are mainly two categories of engine running condition. One is steady state and another is transient for which the requirements of the mixture are different, I mean air formation. Steady state refers to continuous operation at a particular speed and power output with normal engine temperature. And the transient state refers to changing or dynamic conditions where either one or more parameters such as speed, load of the engine are changing. Now let us see more about steady state condition. Steady state occurs under three circumstances. One is idling and low loads. Second is normal power range and third is high or maximum power range. Number one letter study, idling and low loads that is 20 percent of the power. So engine is running with no load, it means idling. In both of these conditions lesser throttle opening will be there, throttle opening and it causes low suction pressure which results in backflow of exhaust gases and air leaks from other parts. So this leads to poor thermal efficiency and higher exhaust emissions. To overcome this say there is need of reach mixture say that is required say in this particular condition. So air fuel ratio should be around 12.5 is to 1, so that is the requirement. So if we see this table and graph we will find say there are different conditions. So this is idling and low load 0 to 20 of the I mean rated power and here the problem is dilution of mixture due to products of combustion. So the air fuel ratio should be richer 12.5 is to 1 and say this is I mean written here. So if we see graphically so this is the state. So where there is a requirement 0 to I mean 20 load is I mean smaller and say richer air fuel ratio so they are required. The second condition is normal power where we produce 20 percent to 75 percent of the rated load and naturally this is the major operation area the requirement should be of the economy. Economy should be the main consideration and for achieving economy air fuel ratio are required to be leaner say 16.5 is to 1 or 17 is to 1 practically up to 75 percent of the load beyond that so it is a range of maximum power. In maximum power say again say there is a richer fuel air I mean fuel air mixture should be there. So air fuel ratio should be more I mean higher so they are around 14 is to 1 like that. So here that for normal power it is also called as cruising range air fuel ratio requirement should be 17 is to 1. And maximum power range so it is in the range of 14 is 14 is to 1 rich mixture. Now what happens in case of multi-cylinder engines mixture from the carburetor is supplied through intake manifold and they are in less to each of the cylinder. So there are chances of variation in air fuel ratio throughout different cylinders or between the cylinders because outer cylinders will be getting richer mixtures why the liquid droplets which are carried because of their inertia they will not turn immediately in the earlier cylinders and they will be carried out say in subsequent cylinders.  Now transient mixture condition these are the state state conditions. The main transient conditions of operations are starting and warm up acceleration and deceleration. Requirements in transient state are different than those of steady state because the evaporation of fuel may not be complete. Petrol is a mixture of hydrocarbons and these are having different boiling temperatures. Because having high vapor pressure and low boiling point are called as light ends while those which are opposite to it means lower vapor pressure and higher boiling point. So they are called heavy ends. In different transient conditions let us see how this affects. The first is starting and warm up requirements while starting from cold speed and temperatures both are low especially in cold weather or early in the morning. Hence much of the heavy ends do not vaporize do not they remain in the liquid form. Therefore ratio of evaporated fuel to air will be too lean to ignite. Hence much richer mixtures air fuel ratio of 3 is to 1 or sometime 1.5 is to 1 are to be supplied so that enough light ends in the vaporized form are available for combustion. Too high volatility leads to formation of vapor bubble in the carburetor and disturbs the metering of the property. While too low volatility causes condensation of fuel or cylinder walls leading to carbon deposits and dilution of engine oil so that reduces the lubrication power. Then there is an acceleration requirement for accelerating that is to increase the engine speed throttle is open fully. As a result fuel evaporated in the intake manifold moves at much faster speed and fuel in the liquid form so that forms a film on the walls of the induction system so that is not carried out. What happens the liquid lags behind temporarily and cylinder receives a leaner mixture rather than rich mixture requirement. Therefore to supply additional fuel to make the mixture rich a separate arrangement is needed and is normally provided in the form of acceleration pump. Figure 2 shows the construction of simple or basic carburetor design which is normally useful to fulfill the requirements of normal power running or in steady state conditions. Let us see this but to figure figure of simple carburetor as you can see here so this is the air inlet air inlet this is the choke valve we shall study it later. And here so this is the say reduction in area venturi is formed and say this is the throttle valve throttle valve so with which we can control the quantity. So this is the fluid I mean fuel supply chamber here there is a float from here say there are tubes or pipelines small pipelines. So we shall read say here the fuel in the supply manifold. This is air vent this is trainer and this is the fuel incoming from the tank. Now as the air comes inside say fuel will be supplied from the tank and when the pressure is low so due to suction I mean vacuum created say the fuel will be sucked here say through this jet. So by opening the throttle we can control the speed as well as the quantity of air fuel mixture inside and say accordingly say we shall be getting the required. Now this is the preliminary design of the carburetor the detailed working and modifications required will be continued in our next session. So the discussion on that because it is not possible to cover in this particular session. Now for this particular session I have taken the references from book of IC engine by Mathur and Sharma similarly this is the web site from which say I have taken certain figures so I thank to them and thank to you also.


I couldn't sleep. I'd wake up, be scared, and I want to wake my husband up, trouble him with it, but that was all before counseling. Once counseling started, that stuff didn't go away at first. It was still there, but working through with the counselor, little by little, no more flashbacks, no more dreams. I couldn't sleep. It's nice.


Live from San Francisco, it's theCUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. Hey, welcome back everyone. We're live in San Francisco, CUBE coverage for Google Cloud Next 18. I'm John Furrier, Jeff Frick. Our next guest is Carol Carpenter, Vice President of Product Marketing here at Google Cloud and Naveed Arifani Adhimi. Welcome to theCUBE. Thank you very much. Thanks for coming on. Big data for good has been a topic we were just talking about here. Day three, what do you guys do and what's your relationship with Google? Because big data for good is really with cloud computing more relevant than ever before. Take a minute to explain your project. Sure, so in South Africa, we're a social nonprofit organization. We try and connect young people that have not employed, never employed to opportunities. And we are hosted in Google Cloud and we use GCP as our sole provider. And what we try and do is we use data to be able to understand young people, understand the facets and make a young person employable and match them to opportunities that we find. And so we describe opportunities and using different data points. And so all those data points that we have, we store them in Cloud SQL and we store them in BigQuery. And then we run analytics and matching to be able to find how these young people can contribute to the economy. How's it going so far? So far it's been great. It's allowed us to think about a 10x strategy. So when we're on-prem business, we were very limited by what we could provide bricks and mortar. And now we're looking and saying, well, how do we provide as much capacity and capability to these young people using self-service channels? So it really has just opened up the world of possibilities. And we're really looking at it and we're very excited because we've taken on some initiatives in Rwanda as well. And so we're taking on a global and Africa-wide kind of strategy, which I think without Cloud, we really wouldn't be able to do. So I wonder if you could just drill down because what are some of the data points that you look at and you measure? And is it identifying the data points and then finding the match? Or is it finding the critical ones that you really need to address as a priority to get kids to that position where they can get a job? I mean, it's really interesting because what we talk about, we talk about proxies for competence. So if you think about when you go and apply for a job, you kind of go and say, hello, here I am and I've done this job for so many years and that's your proxy for competence.  And so for those things, we look and say, what are your biographic information? What's your socialization? What kind of grit and energy to bring to the job? So we try and measure those things and we have as many contact points as we can get to be able to understand who is this individual really and use those data points and we have about 155 aspects that we use right now and that match them to different entry-level jobs. Yeah. So you're the enterprise architect of Herabee Youth Unemployment Accelerator. I love that term accelerator. That's right. And I also love the term enterprise architect because both are in need of some cloud, right? So one of the themes is digital transformation which is kind of a generic term. The analysts all talk about it but really we're talking about cloud mobile digital world and the power that can bring. Accelerator on the youth side, they need an app. So you're essentially providing a digital capability not the old brick and mortar. That's right. How do you architect all this? Because you got to assume there's an app at the edge either downloadable app or website, phone. So we actually have quite an interesting problem to solve because for our young people they don't have access to apps. The majority of our young people are on feature phones, basic phones, not smartphones and data in South Africa is very expensive. So for that young person we need to provide as low a touch a connection point to our services without making that cost them something, right? So we built a very basic Mobi site, no JavaScript as blank as you can get it's very boring if you look at it. The lightweight of Mobi. Very lightweight. But it's the tip of an iceberg and so from there we collect certain information but then we have an award-winning contact center that makes 35,000 calls every month and we engage with that young person on an outbound call for about 15 minutes and it's that 15 minutes that we use to talk to this young person, understand about them, figure out who they are and what they are and use that to gather our data points. We then have assessments that we run, so we run psychometric assessments, we're competence assessments and we gather all those data points and we start understanding this young person in a way that we can go to an employer because on that side for the employer we need to be able to say you trust us that when we give you this young person that we say this person will do well in your job well you have to have trust in us to be able to do that and so we need to provide that data to say well this is how we came up with it. So we take quite a lot of effort. You're verifying in a way you're putting your reputation on the line with the candidates. Yes. At the same time you don't know when the inbound touch is going to happen, so you're going to have all that material ready to go. That's right. That's where the big data kicks in. That's right. And so the big data, the collection of that information and the understanding of it and we're on a journey to start figuring out how can we use artificial intelligence, how can we use ML in a way that improves our accuracy but at the same time leaves out anything that may be biased toward these young people. So we're taking a very cautious approach to it but it's a lot of big data. We're trying to consume it as best we can plus we're trying to think about how do we provide provision our services for the employers because again it's a demand led business so we want to find as many jobs as we can so we can take young people to those jobs. So extend our reach to the employers and heavy lifting so that they don't have to. Yeah, so they don't have to, oh yeah. Carol, talk about the dynamic with Google Cloud because this is the theme we're hearing all week. You guys do the heavy lifting and at the edge of the user experience, you take the toil out of it. The word toil has been- It keeps coming up. It keeps coming up. Taking the toil, the hard work, friction out of it. In this case, the connectivity costs make being productive at that point of transaction. Exactly. They're doing the back end heavy lifting. This is kind of like a core theme across. That is what our promise, the promise of the cloud is supposed to be, right? Which is to remove all that back end toil. I love that word too. The toil, the mundaneness of it all so that folks like Haramby can actually focus on delivering great service to both potential employers and employees. So we're trying to automate as much of that infrastructure. That's what we announced a lot around, serverless around containers. This idea of you don't need to worry about it. You don't have to provision the server now. You don't have to worry about patches. You don't have to worry about security. We'll take care of that for you. I just love your phrase proxy for competence. Cause I can't help but think I've got kids college that you know, there's this whole, that's the whole objective of the application, right? And we've got SATs and PCTs and they take a couple of data sets, but relatively a number of data sets that you described. And I would imagine the kind of the intimacy of those data sets versus a couple of, you know, an ACT and SAT and a transcript. You probably have a really interesting insight and if you can correlate to the proxies of competency, now this is something that has a much greater kind of opportunity than just helping these kids that you need to help in is really important. But that's a really interesting take to use a much bigger data set, sophistication, great tools and infrastructure to do that mapping of competency to that job. Absolutely, and we're very focused on understanding how do we use this data to provision a network for our young people to be able to describe themselves and enter. So one of the things that we found in South Africa and I'm sure it's a fairly universal problem is that if you're unemployed, one of the things that prevents you from finding employment is you cannot access a network in which people that have jobs or describe jobs, you don't have access to their network. And so the ability to stand up and say, hey, this is who I am, these people have said, this is my profile as an individual. And say Harambee or whoever it is says that, I am competent in these things, that gives them an in, that gives them some way of entering that network. And for instance, we've done a certain study that said that if a young lady takes just a basic CV that has a stamp on it from Harambee with a description of who they are and what their competencies are, that improves their chances of finding a job by 30%, up to 30%, and that's significant, right? And this is not us finding the job for them, this is them going out and looking for a job. So it's describing and helping this person enter that network by providing, again, a proxy for competence. So about the relationship with Google, what is Google working with you guys on and what's next for you guys? So Google has helped us immensely. We've received those credits and those credits allowed us to take that first step into the cloud. It gave us a little bit of breathing room, all right? So we could take that step. We've also had access to some Googlers that have helped talk to us a little bit about ML and have been helping us out on that. And in terms of the next steps, it's 10x time, it's time to grow, it's time to use the scale, it's time to use the opportunity that we have to make the real impact that we've been searching for. And connect those jobs to those folks. Absolutely, because this is not a small problem, we've got a big problem to solve and we're really excited to be able to do it. Well, I'm glad you're doing that, it's a great, great mission. Kara, I want to get your thoughts finally just to kind of end the segment and kind of end our time here at Google Cloud. Good opportunity to talk to someone who's been looking at the landscape of the products. What's been the vibe of the show from your standpoint? Obviously you've been planning this for months. It's showtime, it's coming to a close. We're at day three, you heard, it's going to close in 30 minutes. Are you happy? You want? Yeah, I mean, we're thrilled, we're thrilled. We were just talking earlier, it's been a tremendous three days of just great interaction with fantastic customers, partners, developers, it's just the level of engagement. Google Cloud is about making the cloud available for everyone, we wanted this to be a place for people to engage, to make things, to try things, to be hands on, to be in sessions with people like Harambe, to actually understand what cloud can do. And we're super excited, we've seen that in spades, the feedback has been tremendous, I hope you've heard it as well. We're really excited. We believe that the capabilities we have around what we're doing in data analytics, machine learning, on top of this incredibly robust infrastructure, we really believe there are amazing problems we can solve together. We had a couple of our reporters here earlier saying people who think Google's far behind is not here at the event. I got to say, I give you guys some props, you guys are bringing, we know you got great technology, everyone kind of knows that, who knows Google, certainly knows the size and scope of the great technology, but you're making it consumable and you're thinking about the enterprise versus we're Google, use our great stuff, because we use it, you're like Google. People aren't like Google, because no one has that many servers. So it's self-awareness, this has really been a great stride, I think you guys have shown, and the customers on stage. I mean, that's the proof in the pudding. The end of the day. They're fantastic, showing how you can actually apply it, how you can apply AI, machine learning to actually solve real world problems, that's what we're most excited about. I mean, like you said, lots of great technology, what we want to do is connect the dots. And Diane Green, I thought of my favorite sound bite was, Securities number one, worry, AI is the number one opportunity. I think that if you look at it from that lens, kind of everything falls into place. Well, thanks for coming on, thanks for having theCUBE this week, Google. And congratulations on your great venture, and good luck with your initiative. Thank you very much. All right, it's theCUBE coverage here, live in San Francisco. I'm Trevor Jeff Frick, Dave Vellante. I went home last night, he's back in our office taking care of some business. I want to thank everyone for watching, and that's a wrap here from San Francisco. Thanks for watching.