Okay, here we go. My name is James Pitt and this is about semantic Ethereum and When you talk about semantic or some semantic technologies like the semantic web It starts with metadata So you so what is metadata? It provides context to the data that you have and so when you're marking up HTML your your Creating context for the data that you've included in your web page and it in that context can run very deep and Regular metadata that we usually deal with as HTML developers It it's it's a bit of a burden when you do it But if you want to go to something like the semantic web it has it's a quite a big endeavor so the semantic web was proposed by Tim Berners-Lee who created the web and When the person who created the web proposed Proposes a new idea a new concept a new set of standards We're inclined to pay attention to him because we're grateful and it's he's a genius so a Lot of people got very excited and I drunk the Kool-Aid myself I got extremely excited about it and so he started with web of content Which is the current web and then he would he expanded it to be a web of data and a web of trust And as we all know, we're solving the trust aspect of this and The deeper sense of what he's talking about is that Once you establish all this context and once you know the source of the context you You you create something that's almost a not so much of a thinking being but something that is Meaningful that that all the information is connected together in a very formal way And that can make that made a lot of people very excited and a w3c which Which maintains its standards of the web develop the standards of the semantic web and many many tools came out standards Lots of interesting diagrams like that to describe how things connect together But it largely failed and You'll find many articles about how the semantic web was a complete bust But the thing is there there's there's a lot of standards that are out there but They just weren't useful for people and they're a bit of a burden to work with And famously Corey Dr. Rowe even before the semantic web was really formally a set of standards He actually took on just metadata itself the whole concept. He said it's met a crap and Very snarky, but it was very insightful, too He talked about insurmountable obstacles Lies laziness stupidity impracticality And it's a great article if you look it up the seven straw men of meta utopia We ourselves are utopians in a way so we can learn a lot from people who just simply say things like that Perhaps Tim Berners-Lee should have listened to that a little bit But the thing is even though semantic web is a failure or perhaps not to people who are still working on it Metadata is ubiquitous anyone who's worked with web pages knows and the simple fact is apps share data and that data has important context and Much of the data as as web developers know is is embedded in HTML and that's the standard micro data API calls are out there and the documentation behind a fight API calls can be considered metadata And that's in it. It's one of the reasons why we must maintain great documentation And much of this of the semantic web is out there Not really forming a full semantic web not really forming something that everyone uses, but it's out there in it It's useful. For example, Wikipedia has been converted into a database and you you can so wiki data You can go in there and pull a lot of data relate things together. It's very useful So often we use metadata without really realizing it for example the emails that you receive and Gmail about your flight actually contain Tags metadata micro data in there and that's what Google will generate from those from that micro data and GitHub actions Often when you do search results, you'll see these little info boxes, which are somewhat controversial Google grabs this data from various places and actually creates a summary much like Wikipedia and Yeah, those are called info boxes So the thing about there's sort of a conundrum about metadata in general is if if you're if you're too loose about it It it's you're not clear right a famous lawyer said what you know what is is what is the definition of is Sometimes we can be unclear So and it can lead to ambiguity And if you over structure data, of course, it's burdensome And here's some well-known connect to characters If you think about the personality people who keep correcting you and saying you can't say it that way, you know this You can't do it that way Too much structure is annoying and developers don't want to deal with it, right? So Let's go look at what the semantic web is right highly formalized metadata. So It's it's very strict. So whether something conforms to to What what your ontology is or not is really clear It's layered on top of the open web But lots of standards data and tools And here's the things that it provides. It's really important is There's linkage and There's lots of reference through your eyes the other one is the descriptions like how what things are and Like somebody is a person What is a person? Well, you might have a resource that describes what a person is sounds ridiculous But if you want to do something more automated, it might be good to know that this object is a person and this object is an airplane And the deeper side of it is reasoning That you structure your data in a way that something can reason about it And so here's why this is what Tim Berners-Lee Wanted and this is what he was proposing. This is why we all go through this This work to build a semantic web, which many people didn't and ideas saw for agents. That's a big one That the notion was that if we all have the structured data out there something could comprehend it and create Automated services for us a range air plane flights agents things like that and I think I think one of the more interesting aspects of it was like an ecosystem of value chain of data if all the data is More formally connected you can you can build things on top of it reliably and in a way That's one of the great benefits of smart contracts So I'll give you that I'm gonna go over an interesting example some others a tool called protege and that's how you create ontologies and protege that people did protege did really humorous ontology called pizza and this this pizza ontology will help you bake the Perfect pizza data and you can't violate it like you can't put a hamburger bun on top of that thing and call it a pizza And you can actually validate this verify this thing so Think about linkage So here's some standards that that deal with linkage and you have your eyes which we're all familiar with but There's actually really specific ways to use your eyes And XML namespaces and you've probably seen these things in a lot of HTML You don't know what they are But essentially these are defining With with these your eyes what these names namespaces are as they're used later on in this HTML or in this case in this RDF and You can see down here how they're utilized how these namespaces are utilized Like right there. You have a creative commons license and you can see right there terms license What is a turn what are terms? What is a license? Well, something automated can go up here and and look at and And go to that URL and go find out what terms are and if you go to that URL about terms You can learn and see data about what those terms are if that URL still works That's the problem with the web is that these URLs might not work anymore often These servers go down So descriptive meaning It's it's essentially symbols like what what is describing what what is the name of something and it seems silly to us because we just talk we understand the stuff but you know something automated really It's it has to know so an assertion that we might make is Los Angeles it is a city the assertion on a semantic web would be broken up like this Subject predicate object this object is a URI to really clear what? Los Angeles is it's a type of and all this stuff right here This is at the basis of a standard called RDF This is called a triple and RDF is all about declaring many many many triples To create something. It's meaningful and and then it even connects so Descriptive meaning standards how how it would be expressed in the pizza ontology So you have toppings right you want to talk about what a topping is it's a functional property and ingredient of pizza And this is how you would declare that for a machine a machine could possibly understand what a topping is Not that the machine understands what a topping is but the machine would be able to interact with topping data in a way that is reasonable, right It's as a developer it seems ridiculous however that you go through this effort to help something automated So to take it one step further and it gets further and further and deeper and deeper the more you dig in structural meaning To be able to reason about something you have to know how these things might relate how these entities that you're talking about pizza toppings Mushrooms how they might relate and what is appropriate? Like it might not be appropriate to put a pizza as a topping on top of a mushroom and Still call it a pizza. That's not valid So that's ridiculous, but to a machine that really might count if it's making pizza. So Here's how the standard might come come about there's There's something in in in the In the ontology standard w3c owl. It's called transitive property now here This is the almost philosophical notion about it, but it's philosophical ingredients of ingredients are ingredients of the whole and The idea is that you you have an ingredient on a pizza That ingredient may have a sub-ingredient But that sub-ingredient is still an ingredient of the pizza and it's amazing But you have to tell a machine about that otherwise it's gonna get very confused and possibly make a pizza that isn't isn't gonna work out, right? So here's here's how that looks Again as a developer, I might be terrified of this But I might use a tool that would generate this Not enough tools are out there that are easy to deal with not enough tools are out there generating this kind of thing So here's here's a here's one of my favorite topics these crazy pizzas they make in places like Taiwan and Japan Probably Hong Kong this pizza has little baby hot dogs little Ketchup's on top of each baby hot dog and then you can kind of see the logic Now if you want to make an automatic pizza make baker It's it could use that ontology and potentially make this pizza and still be a valid pizza according to the ontology But it's kind of ridiculous. That's why I chose this Um Really, it's It's pedantic like it's it's it's too much work and that's man who's spawning called it right there And he actually worked on many standards at the W3C And he started digital bizarre which is a really interesting company right now And I consider him sort of an anti-hero. He developed a new standard called Jason LD and The idea is that you're going to add context to data with a lot less work as a developer now Jason LD is becoming a very important standard like for example the in Google accepts it if you're an airline and you want you want the the Flight tickets to show up in your email that way Google will accept Jason LD. So Jason LD has become quite quite a large standard and here's what it looks like It's a lot less ponderous than the RDF that you saw earlier. It's not XML It's Jason very developer friendly, but it still has a lot of elements that are semantic or Provide context So when you think about semantic Ethereum Like what's the appropriate level? How far do we want to go? I I consider it. I'm thinking about it And I think it's important to foster creativity, but not to overdo it right just enough for for us to have Composability and you know, this is a good metaphor. You create a standard for Lego brick But you let people build whatever they want with it, but you need to have some structure And Ethereum obviously has a lot of metadata involved addresses signatures token balances You know, we're gonna have identity claims the URIs are associated there in the descriptive side, you know, you have ABI's documentation, of course and structure enforced in the EVM like you you can have As many objects as you want and you know that nobody is going to mess around with it. It's done right so One of the reasons why we we should put more metadata if possible into our work Is the permanency of it? We might not be around and this this application is still being used in the future and Obviously ecosystem Thinking about tokens or identity these these are Identity itself is potentially creating great ecosystems You create these footholds when you do metadata when you do it, right? and swarm itself is actually quite an opportunity because You can use JSON LD in there and you can connect Connect all these things together like right now. We're thinking you'll you'll refer to JSON LD that's hosted on swarm in your contract But you should do it the other way around too so that all your documentation all your data all your contracts everything Somebody could figure it all out even if you're not there to explain it even if your documentation is on the web that no longer exists So the lessons are pretty clear Be light be light about standards If if we have standards, it's more like documentation and we really encourage people to do it. It's fun And the key is steal the good stuff from the W3C because they really do have a lot of good ideas We don't have to do it all but just explore it and you'll find it. There's there's a lot of very interesting stuff in there Just don't explore it too much because it's quite overwhelming. It's for it's ridiculous sometimes But still the vision of it is quite amazing. It's it's very interesting history. So that's it Hope this helps you make your applications That's it


Which of the five versions of a Course in Miracles should I read? Has anybody ever heard that one? Which of the five versions? Now let's take what Jesus says in the Course and let's apply it to that question, okay? When you decide upon the form of what you want, you lose the understanding of its purpose. Basically that's an ego question. Which of the five versions of a Course in Miracles should I study? You see? Because Jesus is saying all form is the same. In the introduction, he says, you know, free will does not mean you can establish the curriculum. It just means that you can decide what you want to take at a given time. And then in the manual for teachers, Jesus even comes out and says that you cannot even decide the form of the curriculum. Isn't that lovely? Now if you cannot, if you take Jesus to heart to what he's teaching in a Course in Miracles, why would you ask which version of a Course in Miracles you should be studying? When Jesus has already said you can't even pick the form of the curriculum. That it's all part of a pre-arranged plan. That everybody, Helen Shuckman was told, everybody's, the world's worsening to an alarming extent and everybody's been called to accept their part in a pre-arranged plan. What if the script is written? What if there is no escape from what must occur? What if you're just asking questions that aren't real questions? They're just ego ponderings, you see, because they're pondering about the form. Which form is better? Which form is better? That's what the ego is doing all day. Which form is better? What if there's no hierarchy of illusions? What if there is no better form or worse form? Because they're all the same mistake. Every form is the same illusion. Like lesson number one, nothing I see means anything. Now that is getting into the practical application of a Course in Miracles, you see. That's taking you more towards a transcendent state of mind that's so peaceful that finally you understand who you are. And when you understand who you are, you have just solved every ego question in the world. Every single ego question of the trillions were just a defense against remembering who am I. And Jesus is saying, actually it's a very simple answer. And the Christ never asked the question, the Christ is the Christ. The Christ has always been the Christ. The Christ will always be the Christ. So this is what we mean by practical application.  And then watch how easily everything else in your mind falls away. Watch how quiet you become when you devote yourself to that purpose to really do that. Watch how the questions start to disappear. Maybe you had questions. Go into the light and the stillness in your mind and watch how the questions disappear.


In this video we will show you how to join a video meeting. There are three ways you can join a video meeting. Using the notification pop-up, by opening the appointment, using the preview and the side panel. Ten minutes before your meeting is about to begin, Super Office CRM will warn you using a notification pop-up. You can click the Join Meeting link to automatically start your video meeting. You can also join a video meeting by opening the appointment in your diary and clicking the Join Meeting button at the bottom of the appointment. When you click the link, your video meeting will automatically start. If you use the preview screen in the side panel, you can click your appointment in your diary to open the details of this appointment. The preview screen allows you to join the video meeting by clicking the Join Meeting button at the bottom of the side panel. When you click your video meeting will automatically start. You can open the preview by selecting it from the drop-down menu at the top of the side panel. We have now shown you three ways to join a video meeting. Thank you for watching. For more information on how to improve your productivity with Super Office CRM, please visit our community website.


Welcome back to theCUBE's coverage of HPE's GreenLake announcements. My name is Dave Vellante, and you're watching theCUBE. I'm here with Holger Moeller, who is an analyst at Constellation Research, and Matt McCow is the Global Field CTO of Esmeral software at HPE. We're going to talk data. Gents, great to see you. Great to be here. So Holger, what do you see happening in the data market? Obviously data's hot, digital. I call it the force marks to digital. Everybody realizes, wow, digital business, that's a data business. We've got to get our data act together. What do you see in the market is the big trends, the big waves? We're all young and old enough to remember when people were saying data is the new oil, right? Nothing has changed, right? Data is the key ingredient which matters to enterprises, which they have to store, which they have to enrich, which they have to use for their decision making. It's the foundation of everything. If you want to go into machine learning and iPart, it's growing very fast, right? We have the capability now to look at all the data in enterprise, which we were able 10 years ago to do that. So data is main center to everything. Yeah, it's even more valuable than oil, I think, right? Because with oil, you can only use once. Data, it's kind of polyglot. I can go in different directions and it's amazing, right? It's the beauty of digital products, right? They don't get consumed, right? They don't get fired up, right? And no carbon footprint. No, wait, wait, we have to think about carbon footprint, different story, right? So to get to the data, you have to spend some energy. It's that simple, right? I mean, it really is data is fundamental. It's got to be at the core. And so Matt, what are you guys announcing today and how does that play into what Holger just said? What we're announcing today is that organizations no longer need to make a difficult choice. Prior to today, organizations were thinking, if I'm gonna do advanced machine learning and really exploit my data, I have to go to the cloud. But all my data is still on premises because of privacy rules, industry rules. And so what we're announcing today through GreenLake Services is a cloud services way to deliver that same cloud-based analytical capability, machine learning, data engineering through hybrid analytics. It's a unified platform to tie together everything from data engineering to advanced data science. And we're also announcing the world's first Kubernetes-native object store that is hybrid cloud enabled, which means you can keep your data connected across clouds in a data fabric or, Dave, as you say, mesh. Okay, can we dig into that a little bit? So you're essentially saying that, so you're gonna have data in both places, right? Public cloud, Edge, on-prem. And you're saying HPE's announcing a capability to connect them. I think you use the term fabric. I'm cool, by the way, with the term fabric. We'll parse that out another time. I'd love for you to discuss tech stunts, fabrics, right? For me, every fabric breaks down in a mesh if you put it in a microscope. Oh, well, now that's really, that's too detailed for my brain right this moment. But you're saying you can connect all those different states, because data by its very nature is everywhere, you're gonna unify that. And what, that can manage that through sort of a single view? That's right, so the management is centralized. We need to be able to know where our data's being provisioned. But again, we don't want organizations to feel like they have to make the trade-off if they wanna use Cloud Surface A in Azure and Cloud Surface B in GCP. Why not connect them together? Why not allow the data to remain in sync or not throughout a distributed fabric? Because we use that term fabric over and over again. But the idea is let the data be where it most naturally makes sense and exploit it. Monetization is an old tool, but exploit it in a way that works best for your users and applications. In sync or not, that's interesting. So it's my choice. That's right, because the back of an automobile could be a teeny, tiny, small edge location. It's not always gonna be in sync until it connects back up with a training facility. But we still need to be able to manage that. And maybe that data gets persisted to a core data center, or maybe it gets pushed to the cloud. But we still need to know where that data is, where it came from, its lineage, what quality it has, what security we're gonna wrap around that. That all should be part of this fabric. Okay, so you've got essentially a governance model. Maybe you're working toward that. Maybe it's not all baked today, but that's the North Star. Is this fabric connects single management view governed in a federated fashion? Right, and it's available through the most common APIs that these applications are already written in. So everybody today's talking S3. I gotta get all of my data. I need to put it into an object store. It needs to be S3 compatible. So we are extending this capability to be S3 native, but it's optimized for performance. Today when you put data in an object store, it's kind of one size fits all. Well, we know for those streaming analytical capabilities, those high performance workloads, it needs to be tuned for that. So how about I give you a very small object on the very fastest disk in your data center and maybe that cheaper location somewhere else. And so we're giving you that balance as part of the overall management estate. Holger, what's your take on this?  We're not going halfway house. We're never going to do on-prem or only in the cloud. So that basically says, okay, he's ignoring pretty large market by choice. You're not, Matt. You must love those words. But what do you see as the public cloud players, kind of the moves on-prem, particularly in this realm? Well, we've seen lots of cloud players who were only cloud coming back towards on-premise, right? We call it the next generation compute platform where I can move data and workloads between on-premise and ideally multiple clouds, right? Because I don't want to be logged in into public cloud vendors. And we see two trends, right? One trend is the traditional hardware supplier of on-premise has not scaled to cloud technology in terms of big data analytics. They just missed the boat for that in the past. This is changing. You guys are a traditional player and changing this, so congratulations. The other thing is there's been no innovation for the on-premise tech stack, right? The only technology stack to run modern application has been invested for a long time in the cloud. So what we see since two, three years, right? The first one being Google with Kubernetes, that are good GKE on-premise, then Anthos, right, bringing that tech stack with compromises to on-premises, right? Acknowledging exactly what we're talking about that data is everywhere. Data is important. Data gravity is there. That's just the network's fault, why the networks are too slow, right? If we could just move everything anywhere if we want, like juggling to bars, then we'd be in different place. But that's not enough investment for the traditional IT players for that stack and the modern stack being there and now every public cloud player has an on-premise offering with different flavors, different capabilities. I want to give you guys Dave's story of kind of history and you can, of course, correct and tell me how this, Matt, maybe fits into what's happened to the customer.  But then Hadoop comes in, lowers the cost and then S3 kneecaps the entire Hadoop market, right? I wouldn't say that, I wouldn't agree. So, it's your history, right? Because the fascinating thing what Hadoop brought to the enterprise for the first time, you're absolutely right, affordable, right, to do that. But it's not only about affordability because S3 has the affordability. The big thing is you can store information without knowing how to analyze it, right? So, you mentioned stuff like that. No schema on right. Before it was like an Oracle database, it was a star schema for data warehouse and so on. You had to make decisions how to store that data because compute capabilities, storage capabilities were too limited, right? That's what Hadoop blew away. I agree, no schema on right, but then that created data lakes, which created data swamps and that whole mess and then Spark comes in and helps clean that. Okay, fine, so we're cool with that. But the early days of Hadoop, you had companies would have a Hadoop monolith, they probably had their data catalog in Excel or Google Sheets, right?  What do they do? They got an option to go to the cloud. I'm hearing that you're giving them another option. That's right. So, we know that data's gonna move to the cloud, as I mentioned. So, let's keep that data in sync and governed and secured like you expect. But for the data that can't move, let's bring those cloud native services to your data center. And so, that's a big part of this. The announcement is this unified analytics so that you can continue to run the tools that you want to today while bringing those next generation tools based on Apache Spark using libraries like Delta Lake. So, you can go anything from Tableau through Presto SQL to advanced machine learning in your Jupyter notebooks on-premises where you know your data is secured. And if it happens to sit in existing Hadoop data lake, that's fine too. We don't want our customers to have to make that trade off as they go from one to the other. Let's give you the best of both worlds or as they say, you can eat your cake and have it too. Okay, so now let's talk about sort of developers on-prem. Right, if they really wanted to go cloud native, they had to go to the cloud. Do you feel like this changes the game? Do on-prem developers, do they want that capability? Will they lean into that capability? Or will they say, no, no, the cloud is cool? What's your take? I love developers, right? But it's about who makes the decision who pays the developers, right? So the CXOs and the enterprises, they need exactly this, why we call the next-gen computing platform that you can move the code assets. It's very hard to build software. So it's very valuable to an enterprise. I don't want to have limited to one single location a certain computing infrastructure, right? Luckily, we have Kubernetes to be able to move that, but I want to be able to deploy it on-premise if I have to. I want to be able to deploy it in the multiple clouds which are available. And that's the key part. And that makes developers happy too because the code you write is going to run multiple places. So you can build more code, better code, instead of building the same thing multiple places because a little compiler changed here, a little compiler changed there. Nobody wants to do portability testing and rewriting, re-certifying for certain platforms. So the head of application development or application architecture and the business are ultimately going to dictate that. Number one, number two, you're saying the developers shouldn't care because it can write once, run anywhere. That is the promise. And that's the interesting thing which is available now, capable now. Thanks to Kubernetes as a container platform and the abstraction which containers provide. And that makes everybody's life easier, but goes much more higher than the head of apps, right? This is the digital transformation strategy, the next generation application company has to build as a response to a pandemic, as a pivot, as digital transformation, as digital disruption capability. I mean, I see a lot of organizations basically modernizing by building some kind of abstraction to their back end systems, modernizing it through cloud native and then saying, hey, as you were saying, okay, run it anywhere you want or connect to those cloud apps or connect across clouds, connect to other on-prem apps and eventually out to the edge. Is that what you see? It's so much easier said than done, though. Organizations have struggled so much with this, especially as we start talking about those data intensive app and workloads. Kubernetes and Hadoop, up until now, organizations haven't been able to deploy those services. So what we're offering is part of these Green Lake Unified Analytics services, a Kubernetes runtime. It's not ours. It's top of branch open source and open source operators like Apache Spark, bringing Delta Lake libraries so that if your developer does want to use cloud native tools to build those next generation advanced analytics applications, but prod is still on-premises, they should just be able to pick that code up and because we are deploying 100% open source frameworks, the code should run as is. So it seems like the strategy is to basically build, now that's a Green Lake is, right? It's a cloud. There, here's your options. Use whatever you want. Well, and it's your cloud. That's what's so important about Green Lake is it's your cloud in your data center or colo with your data, your tools and your code. And again, we know that organizations are going to go to a multi or hybrid cloud location and through our management capabilities, we can reach out. If you don't want us to control those, not necessarily that's okay, but we should at least be able to monitor and audit the data that sits in those other locations, the applications that are running. Maybe I register your GKE cluster. I don't manage it, but at least throughout central pane of glass, I can tell the head of applications what that person's utilization is across these environments. You know, and you said something Matt that struck resonated with me, which is this is not trivial. I mean, not as simple to do. You see a lot of customers or companies, what they're doing vendors, they'll wrap their stack in Kubernetes, shove it in the cloud. It's essentially hosted stack, right? And you're kind of taking a different approach. You're saying, hey, we're essentially building a cloud that's going to connect to all these estates. And the key is you're going to have to keep and you are. I think that's part of the reason why we're here. Announcing stuff very quickly. A lot of innovation has to come out to satisfy that demand that you're essentially talking about. Because we oversimplified things with containers, right? Because containers don't have what matters for data and which matters for enterprise, which is persistence. I'd have to be able to turn my systems down or I don't know when I'm going to use that data, but it has to stay there. And that's not solved in the container world by itself. And that's what's coming now on the heavy listings done by people like HPE to provide that persistence of the data across the different deployment platforms. And then there's just a need to modernize my own premise platform, right? I can't run on a server which is two, three years old, right? It's no longer safe. It doesn't have trusted identity, all the good stuff that you need these days, right? It can be operated remotely or whatever happens there. Well, there's two, three years is long enough for a server to have run their course.   Hardware isn't necessarily evil. You abstract that hardware complexity away from me. It's like TSA. Let me buy it. It's like Tia, let me buy it. I want to go somewhere, but I have to go through TSA. But that's a key point. Let me buy a service. If I need compute, give it to me. And if I don't, I don't want to hear about it, right? And that's kind of the direction that you're headed. That's right, isn't it? No, that's what you're offering. That's right. And specifically the services. So GreenLake's been offering infrastructure, virtual machines, IaaS as a service. And we want to stop talking about that underlying capability because it's a dial tone now. What organizations and these developers want is the service. Give me a service or a function like I get in the cloud, but I need to get going today. I need it with, in my security parameters, access to my data, my tools, so I can get going as quickly as possible. And then beyond that, we're going to give you that cloud billing practices. Cause just because you're deploying a cloud native service, if you're still being deployed via CAPEX, you're not solving a lot of problems. So we also need to have that cloud billing model. Great. Hogan, we'll give you the last word. Bring us home. It's very interesting to have the cloud qualities of subscription-based pricing maintained by HPE as the cloud vendor from somewhere else. And that gives you that flexibility. And that's very important because data is essential to enterprise processes. And there's three reasons why data doesn't go to the cloud, right? We know that. It's privacy residency requirements. There's no cloud infrastructure in the country. It's performance because network legacy plays a role, especially for critical IPers. And then there's not invented here, right? Remember Charles Phillips saying how all the CIOs are now if they're going to go to the cloud or not, right? So it's not invented here. These are the things which keep data on premise.  It's physics, it's laws, it's politics, and sometimes it's cost, right? It's sometimes too expensive to move and migrate. Guys, thanks so much. Great to see you both. Dave, it's always a pleasure. All right, and thank you for watching theCUBE's continuous coverage of HPE's big GreenLake announcements. Keep it right there for more great content. I love for you guys to-


Welcome to the next session of embedded software testing unit 2 series, this is lecture 21. So today we study more about the white box testing techniques and continue our white box testing understanding with more details and we will try to conclude this unit 2 in today's session if not in the next session. And in yesterday's session we discussed about the other techniques of white box testing such as branch condition testing and before that we studied statement testing, branch condition testing, data flow testing. So in branch condition we know that testing does source code which finds out decisions and individual program operands and the Boolean operands within a decision conditions will be tested with all power decision condition testing or this also called as branch condition testing. The next type of testing which is also called in terms of aerospace industry, NCBC branch condition combination testing where the testing aspects will be done on the resource code which recognizes the decisions and the individual Boolean operands within the decision conditions, all the possible values that are going to be fed into the Boolean operands within the decisions will be tested. So accordingly the test cases will be designed such a way that the individuality is achieved. Then we have studied about modified condition testing where the outcomes especially the result whatever it is going to arrive at will be tested. Also the last one linear code of sequence and jump of S6, here we have seen three types of TER test effectiveness ratios where TER one is a number of statements, statement coverage basically, TER two is a number of control flow branches versus control flow total branches, the last one is LCACJ is executed so they used to use it initially but nowadays they use the other type of testing. So we also went through some of the samples and this is a LCACJ table and the total number of LCACJ numbers with the start line, finish line and the jump line will be addressed. The last one is the D1 standard the specific testing is called NCDC, basically the D1 standard the life cycle of the processes addressing to each life cycle activities such as planning, development and testing, testing is called as integral process and under development it has requirements design coding and integration. And we have studied a few examples of the AND gates the OR gates where truth table can be arrived so this type of testing is also called as a truth table approach where all the possible combinations which yields the independency as well as the outcome of the testing will be tabled and accordingly the test will be driven okay. So in today's session we will be talking about gray box testing as I said in the class it is a mix of both white box as well as black box sometimes what will happen is the black box may not be sufficient to support the coverage or the justification in terms of testing. Similarly the white box sorry the black box also may not be enough so we need to balance between both of them especially the integration test cases and the system some of the testing cases on some of the white box of coverage we need to be balanced so the type of gray box testing that is addressed white box test can be intimately connected to the influence of the code they can be more extensive to known to known black box test because of the complexity and other factors. Test that only we know a little about the influence of components called as gray box test here what I said is some knowledge of the internal will be known gray box test can be very effective when coupled with error guessing so another type of matter called error guessing where the errors are guessed based on the knowledge of the unit under test and that will be implemented the test design will be applied so these tests are gray box because they cover specific portion of the code they are error guessing because they are chosen based on the guess about what errors are likely that means the test will be carried out as a pre-test sort of a thing then user has a knowledge about what could be the likely failures that could come and based on its knowledge about the system and about the code so he will balance between specific portion of the code as well as the black box features so he will apply certain test cases those test mechanism is called gray box testing so this testing strategy is useful when you are integrating new functionality with stable base of legacy code so that means that we have a base code which is working most of the time and which does not have much issues or unknown issues and there is a new piece of code or functionality is being added so what we do is we will try to understand how the functionality will be moving with the help of a piece of code and with the help of a system understanding of the knowledge we will try to apply new test cases so these kind of new test cases mechanism is called as gray box testing the next one is all basically the additional details what I am trying to give in terms of white box testing the main methods in white box testing in terms of coverage and all we have covered in earlier we will add to that there are different testing methods and the testing philosophy and the test details that needs to be studied okay so we will study about the test driver and the test tub so what is the test driver what is the test tub you might have heard about this so all the embedded systems I mean embedded system testing mechanism will apply this test driver M test tub it is particularly useful for software testing where unit testing is done so okay a test driver so software which executes software in order to test it that means test driver is again a piece of software it is a test software which executes what the software that is embedded software unit which is under test to test it so providing a framework for setting input parameters executing the unit and reading the output parameters I have a diagram in next play I will explain you can understand better so what will happen is sometimes some of the input parameters execution and expected output may not be possible with a realistic inputs so what we need to have is development of a small driver which drives all this inputs and calls the piece of software under test and expect the result so with the help of test driver this is this will be done a test tub imitation of an unit used in place of the real unit to facilitate testing so this is the complement basically of the test driver on the other side where the actual piece of software which is supposed to work will be replaced with a stub so that we know that test driver is working or not properly to see that what is expected and the same thing will be replaced with the actual piece of software to compare the expected result and arrive at the conclusion that the tests are being passed or failed so that is how a test hub is used you go through this diagram this will give you a clear picture of how the test driver and the test hub is used so basically the book refers to this diagram of course test bed is a test setup or environment having both the driver on the one side and stub on the other side and the unit is used in the middle you can see the driver calls unit under test and the unit under test can be replaced with the help of stub it is like a wrapper we can have for this so what does the wrapper do basically whatever the information that we need to get it from this unit will be driven from this driver and wherever the possible expected output that is expected from this unit will be done with the help of the stub so stub is going to replace the actual unit which is unit under test so that is the basic of test hub and drivers so interfaces between two systems two system parts can how it is used basically test hub and test drivers are basically for the interfaces so two system parts in order to test the interface so on the one side we use the driver because the other side we are going to have an interface and when they are closely in conjunction we may not be able to test it so for example so we have a UUT1 and suppose we have UUT2 and you want to test UUT1 with parameters such as parameter 1, parameter 2 and expected output as expected output 1, expected output suppose and how does this UUT1 is going to be done is with the help of UUT2 so what will happen is there is a interaction between these and what we are going to do is we are going to replace this piece with the help of test driver and similarly vice versa while testing this piece of interface with the parameters we are going to use a test driver here may be one we can call here in this case it is so likewise the interfaces between two system parts can be tested with the help of this mechanism if both systems are available here available means available for the tester to test it independently that is what it means or if it is not available then we are going to club both of them and drive it at a higher level so this can have consequences for the testing time because the time is more required for this actually so why this and to start testing the system part as early as possible steps and process means still suppose some functionality in the embedded systems completely developed and other functionality is not being developed how we are going to test that implemented already functionalities with the help of drivers their specification detail problem and with the help of inputs from the parameters the test drivers are developed and tested basically it is useful for testing the interfaces so a step is called by the system on the test and provides the information the missing system part should have been given and a driver calls the system part standardization and a use of a test bed architecture basically if you have this test bed architecture defined in the early stage of the project it will be very good for each piece of the software unit under test so it will greatly improve the effective use of stubs and drivers the test bed provides a standard interface for both the tester to construct the construct and execute test cases and for the stubs so each separate unit to be tested must have a stub so we need to have a stub as well as a driver to test both of them interchangeably and techniques for test automation such as data driven testing can be applied effectively where data is very important and all the type of data what we have studied in all the operations like pks, cks, cus and all that can be tested with the help of this the combinations of inputs that needs to be driven can be done with this actually. So such a test bed architecture is the testing of any unit the use of such test during integration testing and large scale automation of lower testing is easier basically so considering all these aspects we need to have test stubs and drivers okay so that is about test stubs and drivers and a day box testing with the white box testing mechanism now we will come to the various coverage testing tools that are used in the industry in general so logic analyzer, software performance analyzer, timing analyzer, vector cast, LDREA, RTRT there are lot of tools like this so which will help which will basically used for having the coverage and the instrumentation unit testing etc will be done with the help of this it could be one tool or multiple tools depending on the complexity of the embedded software that is being used okay let us try to study understand the basic thing about these tools okay vector cast this is a tool from vector cast corporation in aerospace is being used more where they define different levels and they do the instrumentation of the source code and they run that tool and we will get the report such as this what is being shown below so for a database sort of application in aerospace this is being used we can see the matrix what are the matrix it generates so with the help of this matrix the conclusion will be done so as to see that whether the vector cast tested the output is 100% coverage done or not done you can see there is a database total number of database have been tested here and the complexity is 5 state for testing and due incident be level a state is 100% that means all the statements or the decision or the conditions that are there for each of these there are about 10, 10 out of 10 have been executed saying that the coverage is 100% similarly you see another piece of software that is been tested with the help of vector cast some functionality or a package for the manager and this has a 1, 2, 3, 4, 5 types of sub functionality like place order, player table, get check total etc each of them have been tested with the help of vector cast with the instrumentation mechanism and you can see the complexity it has a complexity of 5 we will try to understand what is complexity in the next unit I guess unit 3 and complexity of other pieces is 1, 1, 2, 3, 4, 3, 4, 5, 2 so there are total 12 complexity measures that have been tested here with the help of vector cast and the coverage is something like 63% in the first where the place order is being executed and the coverage is 14 out of 22 that means to say that the complexity sorry the coverage needs to be done for 22 executable statements or decisions or whatever it is but out of which only 14 of it have been covered saying that 63% have been covered similarly for the next you can see 100% coverage and this one is 77% 7 out of 9 and the last one is 0% none of the statements have been executed or have been invoked with the help of this tool whatever instrumentation we have done so all together they generate the matrix of course we study about test matrix and all that in separate session in detail but to have a glance of what tools commercially they are using I am just trying to present it the various tools. The overall coverage is 71% and I can say the new column that is for a different piece of functionality or things that will be showcased the next one is LDRA it is from LDRA and it is also one of the popular tool that is being used in the aerospace industry here also similar to what instrumentation we have seen so the report can be generated which will help in terms of doing the in testing we can see how many test cases have been used what are the past so what is the report and likewise we have a complete coverage of the unit under test. So the next one is being RTRT this is also one of the good competitor and popular tool that is being used in different industries including application, finance, embedded automotive, telecom, aerospace etc widely it is used but they have a different variants of this tool such as RTRT embed likewise so it is from IBM you can see the details in that website or their website there is a data sheet and all that which talks about this so the rational test real time is called as RTRT so what it does is the source code such as C C plus S or whatever it is fed into that RTRT tool so what it does is the below steps are there part of the RTRT in terms of configuring and using it so the environment will be defined first test harness will be created and with the help of test harness steps will be generated then we will have executables for the corresponding test harness then actually we execute the test after execution of the test on the target environment we have the results and the results will be used to report it what is the coverage and all you can see on the reference is the code coverage, performance, memory, trace analysis all these aspects of the testing white box testing will be done and similarly test results will be reported to support this coverage or justify the coverage to analyze it and it uses the cross compiler as GNU, VCC etc to compile the developed test harness and the builds and it uses the target such as micro controllers it could be having the RTOS or it could be with the host machine simulators or emulators on the target machine so that is how the RTRT will be structured to use on the white box testing methods okay so that is what is about commercial tools used for white box so let us try to study what is the logic analyzer basically logic analyzer can record memory accessibility in real time it is a potential tool for measuring test coverage what it does is we have various test hooks in the embedded system and the test hooks will record different data in a dedicated piece of memory and that memory can be recorded with the help of this analyzer that analyzer is called logic analyzer and there are logic analyzer probes that will be hooked into the memory and with the help of probes it will acquire the data in real time and will have the coverage and will provide the coverage results and reports. The logic analyzer is designed to be used in trigger and capture mode that means the logic analyzer can be used as triggering and capturing mode for the memory or the interfaces that will be hooked for that piece of it is basically hardware and software both the logic analyzer has I may not have a diagram here it is a plot I will go to show how it looks the logic analyzer is the logic analyzer is designed to be used in the trigger and capture mode it is difficult to convert its trace data into coverage data so what it means is the trace data whatever we got it we may not be able to cover it we may not come convert that into coverage with the help of this but what it does is the overall measurement it does we do a sampling method it is called statistical sampling with the help of this logic analyzer can be used to have a coverage on the trace data on the triggered mechanism in continuation of the logic and level in particular it is difficult for sampling methods to be a good picture of ISR test especially the piece of software having ISR is nothing but interrupt service routine you must be aware of this so basically this is the pattern parcel of the embedded software where an interrupt occurs for the normal flow that interrupt has to be handled with a piece of control flow or functional flow or whatever the action that is needed that action and all will be part of the routine code interrupt service program a good ISR is fast meaning to say that ISR has to be short and sweet it needs to get fast and come out of that routine that means it needs to do certain flag settings or certain minimum option so that it can come out very fast ISR cannot be bigger it cannot be complex and it cannot take effort to take more time if an ISR is in the infrequent that means the frequency of the ISR happening in the embedded life cycle is less the probability of capturing it during any particular trace event is corresponding to load that means capturing the trace data is lower because ISR is happening very less frequency that is easy to set the logic analyzer to trigger on ISR access so but easy to set the logic analyzer because the capturing mechanism will be easier this coverage of ISR and other low frequency core can be measured by making a separate run to the test suite with the logic analyzer set to trigger and trace just that core so what can happen is we are trying to focus only the piece of software which are part of the ISR so what we can do since ISR is very fast and very frequently happening within the system and the system having complexity to improve more number of ISRs what best can be done with the logic analyzer is that we can comment out the rest of the core and focus only on the ISR what is and trigger that and capture the data what ISR is supposed to do and analyze the capture data with the help of logic analyzer and do the coverage whether ISR is capable of doing or covering all the intended result. So there is another set of tool it is called software performance analyzer so performance could be in terms of memory performance could be in terms of memory that means memory has to be accurate or intended for certain portion of it suppose say requirement could say 50% of buffer memory to be resolved for feature upgrade or scalability etc so what will happen is we need to say that for example if you have a 1 MB of memory we should have 512 KB of memory as we go against 1 MB so that is the requirement and how do we test how much the software is taking so there are a lot of methods and there are a lot of tools also so those are all coming under performance analyzer by using the information from the link of your map these tools can display coverage information on a function or modular basis model basis rather than raw memory so this is a map file for each of the embedded project this will be done with the help of this compile plus link with the help of this map file will be generated this map file will have all the information such as the addresses the top codes and the BSS stack and all the information with the help of that memory map we know that how much it is going to take this build for that particular project with the help of that we should be able to arrive at the performance of that particular unit so for that there are tools analyzers from different vendors but mostly it will be done manually or statistically basically okay so performance testing performance testing and consequently performance tuning are not only important as part of your function testing but also as part of important tools for the maintenance and aggregate base of the embedded life cycle so another important aspect of the performance is memory we know speed, speed with load they say so it is very important to have the performance of the embedded system stable and continuous without the change and with efficient with efficiency having the scalability on modular this is one of the performance requirement they use it not only it is enough to have memory satisfied speed means not fast basically with various conditions on the field we should be able to perform consistently and scalably etc the other thing is timing it should be accurate and stable so this is also one of the performance measure they have it so performance testing and consequently performance tuning are not only important as part of your function testing but also as important tools for the maintenance and the upgrade, upgradability is more because embedded system is ever living and growing because of the fixes in the requirements in the embedded life cycle. Performance testing is crucial for embedded system design and unfortunately is usually the one type of software characterization test that is most often ignored that means as seen and many of the embedded system world industries they give less priority to performance testing and tuning especially in the beginning or the middle of the problem but they struggle in the end because they would not have met the criteria of performance and lot of bugs and errors will occur due to the performance issues that is very important to have an understanding of what is the performance of the embedded system accordingly we need to have testing mechanism especially on the memory speed timing and the load of the unit and we should use the analyzers that is performance analyzers on map files now probably we will try to touch base simple map file to have an understanding of what it does but basically it is part of the embedded system course I will try to just address it in the future okay the next one is I have said memory usage what sort of a memory usage is there in the embedded system so basically we use a memory map with the help of memory map we will be able to analyze the stack inbuilt memory it could be the RAM ROM ROM is it could be flash or we can have a small footprint in terms of faults and all that usually that will be stored in MEM it is also called as e-square prompt electrically irresistible programmable data on the memory so there are various types of tests for example for e-square prompt they use the patent test and for flash they use the integrity test integrity test can be done with the help of working ones where each memory cell is tested with zeros and ones that means whether each cell is capable of flashing or programming a zero a programming one so that is also called as a patent test usually they use if it is 16 bit 5A, 5A, 5A, 5A you can see why 5A it is because 5A is nothing but I will write it on in binary 4 is 5, 0, 1, 0, 1 whereas A is 1, 0, 0 is 10 so we know that the cells the first cell is addressed here this with 0 and the same cell is addressed with 1 similarly the next cell is addressed with 1 and then next the same cell is filled with 0 so likewise we are going to have a patent test or working one test where each cell in the memory will be tested so on the memory like flash or RAM the same testing is done so mostly these tests are basically built along with the code because there are requirements which talks about these tests have to be there frequently should be done in the embedded systems so they will have a implementation in the embedded system itself at certain frequency when the system is running but we need to log whether there are any failures for such tests, these tests are called built-in tests built-in tests there are different types of built-in tests that is not scope of this depending on the embedded systems and all this will be logged with the help of those tests so that is part of the memory usage and memory testing in the embedded software testing okay the next one is the timing analysis so there are stringent timing requirement to test and analyze the timing how much the system is taking, timing analysis have to be conducted and mostly the timing analysis are done in the help of the time machines and trace machines which are available in the debug itself the ID is nothing but integrated development such as multi-lotard by code warrior etc all these debuggers have inbuilt time machines or trace machines and that will be used that is helpful in finding the timing requirements in terms of unlocking code and putting the break point and measure the time how much it is taking and all so we can validate with the help of that some of the embedded systems will provide the ports and that port which are the LEDs you can say can be instructed or IO ports so which will toggle for certain range or certain frequency and that can be put into the scope, scope means oscilloscope we have multi-channel oscilloscope from Agilent we can use any of the oscilloscopes to measure it so such embedded systems so we will have to have ports available but it may so happen that the ports may not be there because it is additional hardware and they may not be able to they cannot or they may not be able to afford to have that because it is going to occupy a space and no current etc for intermediate testing before the last build they may be having it within the part of the board or the target board of the FPGA over this with the help of that the timing can be tested where the embedded software will be triggering upon certain events and that events can be captured in the oscilloscope and for ISRs we can analyze through IDE where ISR so we can have a counter and how much the counter is between the counter also can have registers the timing registers can be used along with the counters to arrive at how much time it has taken so manually this will be done to analyze the ISR timings etc then we have inbuilt registers on the target systems such as watchdog and all stuff with the help of those we can test it watchdog registers, timing registers, RTCs, RTCs in the remote time clock all this can be used for doing the timing analysis so with the help of this we can do the timing analysis okay so having understood the various tools involved the applicability we need to understand for the life cycle coming to the testing tools so there is a life cycle that is being categorized so we will try to understand in brief what is this tools life cycle basically it is called the various tools how they are getting used how they are getting categorized so what do they use and all that quickly we will try to understand based on what are the type of tools that we need to have in the embedded software testing okay so you can see a diagram here that depicts about the various tools related to the testing life cycle so we know that there are as per the TM method or the liter principles what we have studied there is a life cycle PSEC the preparation, execution and all the stuff completion and all that stuff so we have various tools for P preparation we have a case tool analyzer complexity analyzer for specification we have a test case generation or test case generator that will help in developing the test cases and for execution we have test data generator record and play back to load and stress tools and we have a number of tools does not mean that all need to be used but it is a categorization basically that need to be applied and planned these are all be part of the planning software verification planning which we have studied in our earlier sessions similarly for completion we have a reporting mechanism and all that and overall for P and C planning and control we have different tools in terms of defect management, test management, configuration management, scheduling and progress monitoring code okay so this is how the life cycle data or the life cycle aspects of the testing will be considered in terms of categorizing the testing tools and we will try to study some of them as we go through some of the sessions like defect management or test management, configuration management in the future classes okay so that is about the life cycle we will try to quickly understand each tool such as planning and control there is a defect management tool a defect management system is used for defects, press them and generate the process and status reports defects detected during the test process must be collected in an orderly way it should be organized properly but a small project a simple file system with a few control procedures is sufficient whereas a more complex projects need to have at least a data base sort of a thing with the possibility of generating progress reports that tool should help basically this will help it is in team to analyze where they are so defect management tools such as bugsy law can be used for management of the defects so that is part of the planning and control the next one is a test management tool so the tools so with the ability to link system requirements of test cases basically all the tests are managed how they can be based all this will be part of this so the tool should have a ability to link the requirements into the test cases they have become very useful if system requirements are changed or might change why this we need all these tools is very important to have control of the changes so how do we do so with the help of these tools so it is very easy to change it to plug with the new requirements or initial requirements etc so all this can be done with the help of test management tool then we have a scheduling and progress moving tool there are number of tools available for scheduling and progress monitoring such as MPP and all there are different tools also which can be integrated along with the test management tools such as this link or bugsy law for defect management so it is very easy with the help of these tools for scheduling and progress monitoring very useful for a test manager combined with information from the defect and test management systems and preparation phase and specification phase tools on the left hand side you can see is the preparation phase and specification phase there are case tools analyzer complexity analyzer first case generator we will try to understand what are those probably we will try to detail it out in the future sessions okay case tools generator preparation phase they use it specially for those where we use object oriented as one of the systems or model based systems the tools such as UML based tools are used for consistency checks and all that so they will be able to help in terms of the preparation phase so they can be used to check whether or not the design has omitted anything so this is basically testability review of the test basis what we is getting planned in terms of preparation. So the next one is the complexity analyzer we try to study the complexity software complexity basically this complexity analyzer understand for physical process from sky tools is capable of giving indication of the complexity of the software the degree of complexity is an indicator of the chance of errors occurring and also the number of test cases how much we need involved to test the system thoroughly so for this they use a standard called the macaday complexity is one of the important or good complexity measure generally they follow in the industry which identifies the complexity this is basically getting identified I can explain that in one of the next class with the formula and all that we need to know about agent nodes basically we know that embedded software can have multiple edges and nodes on the software with the help of that the complexity is arrived the next one is the test case generator this for the specification test specification or test cases so there are test case generators such as MATLAB, lab use and all that but sorry lab use and all are used as a script and all this stuff so using something like excel sheet based tools or DC or Python even or these can be used from inputs such as requirements to test cases so with the help of for this tool test cases can be generated and consistently it will be used for different requirements engine requirements and all that so that is how test case generators are used in the preparation and specification course of the embedded software system testing so next one we have the execution the execution can be done with number of tools and the various types of things that we have definitely minimum 3 to 4 tools to be used for any of the embedded systems having a normal complexity and here is the list of the type of tools that are used in the execution phase test data generators, record and playback tool load and test test simulators we know we have studied the books from simulators, steps and drivers we studied this because we know that ID is something that is above for code analysis and all that we have a static source code analyzer such as understand for ccbc, cc lane likewise and cover T is also another code analyzer error detection tool in the code performance analyzers memory analyzers and we have code coverage analyzers such as instrumentation analyzers, vector cast, RTLT and LDRA request so we have a thread end event analyzer where we use in RTOS which is living with the multiple threads and all that then other one is called thread detection tool the specific tool where if there is a thread to the embedded software system due to error code or a dangerous way of having the crash etc that can be identified with the help of this mechanism with this tool so that is how the execution phase the tools are categorized so having understood this testing tools and all that we will try to understand the testing terminology and all that stuff in the next class is a configuration management tool also we will try to go through that in the next class


Hello everybody! In this video, I'm going to show you how to remove a hidden Bitcoin mining virus from your computer. Hello friends! If you need to recover deleted data, view or restore removed browse in history. Hetman Software products will help you. Follow the link in the description. Download the necessary program for free. Install it and analyze the disk. The utility will show you the data you can recover, so you will be able to view it or get it back. In our channel and blog, you will find solutions to any problem, from installing an operating system or configuring it to fixing possible bugs and errors or optimizing mobile gadgets. Our specialists will answer any questions you ask in your comments under the videos or articles. If you notice that your computer, while you are not using it, still behaves as if it works on a complicated task, or if it becomes very slow when dealing even with simple office routine, it could be a mining virus working inside your system. If you never heard of a mining virus, here is the explanation. It is a virus that uses computer resources to generate some cryptocurrency. You can watch one of our videos to learn more about mining cryptocurrencies. Find the link in the description. Such mining operations take place automatically without the user's knowledge, and unfortunately your PC won't show you any warnings about it. Software like this can appear on your computer when you download files from doubtful websites. So, before you download an app from a website you never heard of, check the link with a service virus tunnel. Just copy the link to the file and paste it into this field to check it. You will see the result and then decide if it's worth downloading from such website. You will find the link to this service in the description. This kind of virus makes your computer work at full capacity, so that it can become slow even during simple operations. This work in such conditions affects the computer's hardware, which may break down pretty soon. In the first place, it reduces the lifespan of your graphics card, processor, system memory, and even the cooling system. The first sign of a mining virus on your computer is lagging even in simple tasks, and the cooler working at maximum speed all the time.  If the lags have disappeared and the CPU cooler has become considerably quieter, that is almost a certain sign that you've got the mining virus on your PC. Recently, such viruses have become very good at disguising themselves. They can be a dedicated process controlling such mining virus, and it can suspend the mining activity when you start a resource-intensive game. So that you will never notice any lags or freezes resulting from the virus activity. As soon as you exit the game, the virus will start mining again. And the most dangerous types can even disable antivirus scanners on your PC. So, to detect the virus, the first thing is to scan the computer with an antivirus having the latest database. In case of a simple mining virus, you are not going to have any difficulties. They will be detected easily and removed, but the virus is hiding from the scan will make it try harder than that. A helpful tool in finding a hidden mining app is the Task Manager. Scan it by pressing the key shortcuts Ctrl-Alt-Delete or Ctrl-Shift-Escape, for some time watch the active processes, but don't forget to close all programs you are using. If a process puts a lot of load on the system, it could be the virus you are looking for. For example, on Lightning Peter there is a process with the name System.exe that makes the operating system work hard. For more information, click on the tab Details and find this file here. As you can see, it is launched by the user, while such processes should be launched by the system, and it's a certain sign there is a virus. By right-clicking on it, you can search online for more information on this process, or try to end this task, open file location and try removing it, if possible. Most mining viruses prefer using the graphics adapter, not the processor. In this case, you may never see them in the Task Manager, especially on all the versions of the Windows operating system. On the contrary, when Windows 10 Task Manager, you can see how loaded both the central and the graphics processors are, and if the computer is idle but the load values are close to 100%, your computer is very likely to be mining. Some minor viruses can even disable the Task Manager just a few minutes after you start it, and this is also a very prominent sign of threat. Also, some of them may stop when the Task Manager is started, so you won't see them in the Task Manager window. However, special software can help you, for example AIDA and the Task Manager, Process Hacker and other similar apps which can track the system load over time. When you start any program from this list, you may find a picture very different from what you see in the Task Manager. You can find the download links in the description below this video. There are also situations when the Task Manager shows excessive load from the browser. Then, it can be a web mining application that works from a certain website. In this case, you'd better stop using the browser or add an extension to block ads which will prevent websites from mining on your computer. You can also watch another video about useful browser extensions. The link is below, as usual. To remove the virus, scan the system with an antivirus having the latest virus database. You might have a simple mining app which is not hidden so the antivirus will find and destroy it easily. If it didn't happen, and you find the suspicious app in the Task Manager, you can try removing it through the registry. To do it, open the Run window and use the command raggedys. Go to Edit, find, type the virus name and remove any coincidences you have found. If you are not sure that such file can be deleted, then don't remove it, as it can be even more harmful for the system. And if you are going to make any changes to the registry, we recommend exporting the registry file. You can watch another video on our channel to see how. The link is below, as usual. If you haven't found anything in the Task Manager, but the computer behaves strangely, use the utility called Enviro Task Manager. Start the program and examine all running processes. If anything looks suspicious, put the cursor on the application to see the information about it. Then right-click on it and select Detailed info, then Performance. Choose one day to view the load on your PC during this period of time. If the process puts much load on the system, note down its name and path. Right-click on the process and select Kill process. As you can see, Ever process is assigned a risk level to make it easier to monitor viral activities. Follow the given path and try to remove the virus from this folder. Most likely, it will be hidden and you won't see it unless you have enabled Show in Hidden files. To do it, click on View and check the box next to Hidden items and the elements will appear. Or, give the name of the virus and find it in the registry using the method I have shown before and remove all the cane synthesis. After that, it is recommended to scan the system again and remove the detected threads then restart the system. If you don't feel too confident about your antivirus, use one of the portable utilities like Dr. Web Curate. It is often used to search for hidden miners. This is a free utility and you can download it from the official website by following the link below this video. It is important to use the latest version. Just download the program and open it, start the scanning and wait until it is complete. Then you will see the list of all detected threads and possible actions you can take to eliminate them. And that is all for now. Hit the Like button and subscribe to our channel. Leave comments to ask questions. Thank you for watching. And good luck.


Hi Friends We will discuss other important component of IPM That is, life management ñ by modifying insect development and its behrayer through both natural and synthetic chemicals In this lecture Iím going to deal with the communication in insects Behavioral aspects of the insects and same-year chemicals and furomones, allelic chemicals, then chitin synthesis inhibitors, then afterwards attractant, repellents and also antifidents. On this earth, each and every organism has developed its own communication system. In vertebrates, the communication system is through auditory and visual, but in case of insects, apart from auditory and visual, the another system of communication is through olfaction and also tactile. In insect, the communication system through olfaction, it is strong and this olfaction behavior of insect can be well established and this can be used in pest management programs. Through insect behavior, it is through producing some chemicals either by insects and also some host plant species. Some of the volatile compounds and also non-volatile compounds produced by the plant species actually they deter the insect species by changing its behavior. This was involved in the pest management strategy through trap cropping system. So another way of modifying insect, it is through food lures and also some of the beds which are being used in the pest management program both in household pest management and also field insects. However, even though we have long history of adoption of this technology, but its adoption in agricultural system is slow. It is because of availability of cheaper chemicals which have broad spectrum activity against various insect pests and at the same time they are cheap, they are quite convenient to handle and thereby farmers, they have obtained the chemical protection than other means of production. Then they learnt about the more bad or ill effects of these broad spectrum insecticide. To quote one example here, when the DDT was used in USA, the same DDT residue was about 0.0002 ppm in the lake water. When the fish was taken out from the same lake, the magnification of this DDT was magnified to 15 times. So the residual toxicity of this hazardous chemical was accumulated in fishes and thereby environmental protection agency, it seriously acted upon this DDT and ultimately they banned this DDT product from the use in agricultural ecosystem and started using the alternative management practices, among them one is manipulation of pest behavior. So it is one method which is based on the principles of ecology since it does not have any ill effects on the environment and it is going to save the natural fauna and flora also. So these chemicals which affect growth, development, biology and the ecology of pest species can be differently looked into. So thereby these chemicals which are actually safe to the natural enemies since they have low toxicity in the nature. So for their communication insects most of the times they depend on chemicals and their chemical cues. So this phenomena was used in the pest management. The much work on the chemical technology, it is going on since three to four decades and this resulted in the discovery, identification and synthesis of specific chemicals. So that regulate the and also mediate which affects the development and species behavior of the insect. Such chemicals when they use they cause premature death that is abnormal molting or metamorphosis at the same times other chemicals they are going to attract or repel towards the source. So this behavioral alteration of the chemical it is defined by scientist called Foster and Harris during 1997. The manipulation of pest behavior is defined as the use of stimuli that either stimulate or inhibit a behavior and thereby it is going to bring out some changes in the expression of the insects. So the another chemicals which changes the behavior of the insects they are called Cmeochemicals. So the word Cmeon it is actually derived from Greek word that means to say a mark or signals. So those chemicals that are able to modify behavior of a insect in its perception which is going to cause changes behavior at very low level they are called Cmeochemicals. These Cmeochemicals can be divided into naturally secreted ones and which are not naturally secreted ones. So under naturally secreted Cmeochemicals we have furomons and also allelochemicals. So these furomons they actually communication between one species and this is between intraspecific that is that means to say that is between two different species. Then in this we have allelomons, chyromons, synomons, antimons and also nemons. So in furomons we have two groups that is religiore furomons and also primer furomons. So from the point of pest management we have more information about these furomons which are being used since many years for modifying the insect pest behavior for the advantage of the pest management program. In next class we are going to deal more about these furomons and their application in the pest management program. Thank you.


Hi and how are you all today? Let us discuss the question. Say solve the inequality for real x. 4x plus 3 is less than 6x plus 7. Let us start with our solution. Now in order to solve this inequality for real x, we need to simplify this, that we can do by first of all subtracting 3 from both the sides. These two will get cancelled. We are left with 4x is less than 6x plus 4. That is after simplification. Now on subtracting 6x from both the sides, we have 4x minus 6x is less than 6x plus 4 minus 6x. We have on simplification minus 2x is less than 4. Now on dividing both the sides by a negative number, that is minus 2, we need to change or reverse the sign of inequality. And after simplification, we are left with the answer, that is the value of x is greater than minus 2. So for real x, the solution set consists of all the real numbers that are greater than minus 2. And hence the solution set is equal to minus 2 to infinity where they both are not included. So this completes the question that was given to us. I hope you enjoyed. Take care.


Okay, we're back live here at the Velocity Conference in Santa Clara, California. This is theCUBE, siliconangle.com and wikibon.org. Flagship program, we go out to the events, extract the signal from the noise, and that's what we do, we talk to everyone we can, we go to the events, and we find out what's going on. We track the keynotes, we find out what's going on with the players here and find out what the stories are and what the sentiment is. I'm John Furrier with Dave Vellante, analyst at wikibon.org, and we're breaking it down for you, Dave. I got to say that Velocity Conference is more of a cloud show than what it appears. But I think it's not a cloud show, it's a web performance show with an app design on the front end tied to the back end, a DevOps show, a new kind of cloud show. So I put it to you, Dave, what's your take? Do you agree and what's your assessment of the Velocity Conference, day one? Well, I think there's no question, John, you're right on, that cloud is an adjacency to this event, and actually I think, I'd like to see more enterprise players participating here. Why? Because the development community is critical to the growth of the enterprise, open source. This all comes down to one thing, John, and that's mobile, and whether it's mobile apps, mobile apps in the cloud, scale, it's all about mobile, mobile performance, and actually getting those applications to run well. Of course, where are they going to run? They're going to run in the cloud. And I think that's a big focus here. That's the big shift that we're in the middle of. Mobile apps run poorly relative to laptop apps or browser-based apps, and mobile is the future, and you're going to see all the action there, but I think you're right on. I think cloud is really the big opportunity for this event to expand. Yeah, and I think the other thing I want to share with everyone is that this is SiliconANGLE and Wikibon theCUBE, and we have a business relation with O'Reilly Media, and O'Reilly has been such a great franchise and brand, and bringing theCUBE to their events has really been a fun thing for us. And Dave, I got to say that this show is breaking out into the mainstream, and I'll give you some examples, but this is classic to me, O'Reilly community. A really great community of thought leaders and real developers, the insiders, the guys making the industry happen. But what you're seeing here is, we heard on theCUBE today, state farms here, other enterprises are starting to come in. This is, you see this every time, Dave, in the trends. The breakout trends always have that core community at the center of it, pulling the market, crossing the chasm, and when you start to see the technology, the methodologies, the philosophies, the mindsets, cross over to mainstream in the enterprise, you know it's making it. So that's why I think it's more of a cloud show than it meets the eye, because cloud has to take into account security, SaaS, design, and DevOps is in the middle of that. So you know, I got to say O'Reilly has that core community that's from their franchise with the books. You can shop and buy all those like 35 books on DevOps, Theo told us. So again, O'Reilly has that core community, and this is a tight-knit community. These people know each other, the hallway conversations are just as good as the sessions, and that's what's happening here, and I predict that this is going to cross over into some sort of cloud show, because cloud is where the action is. I don't care what anyone says, cloud is morphing. It's not cloud as an, oh Amazon, hypervisors, infrastructures of service, or platforms of service. It's about business value, outcomes, and solutions, and that's what developers are focusing on. So I think this conference, Dave, is going to morph into that app focus, and that's going to back end and sister up with the cloud. Yeah, I think you're right, John. I mean, I think that, you know, here's the thing about this show, Velocity. The discussion here is how do you solve the really hard problems on the web? Things that Google is doing, things that Facebook is doing, Akamai, and the like. Google gave some evidence today that the internet is actually going faster, but I think the consensus that everybody agrees, including Google, we had Google on theCUBE, still not fast enough, and now you inject mobile into the equation, it's going to slow things down even more. So web pages, the average web page size we heard today is 1.5 megabytes. We heard from some folks on theCUBE that from a gaming standpoint, the average gaming web page size is 50 megabytes. We heard JavaScript is just being, you know, JavaScript creep, I call it. So the underutilization of too much code, you're loading too much code, there's a lot of inefficiencies. That's the kind of discussion that you have going on here, and frankly, I think the escape key could be hit, and I think this show could really drive more into the business value impacts. I think they're just touching upon it, and I think it's huge. Think about John, the guy from the Obama campaign, Obama for America, said that they were able to achieve a 14% conversion rate, 14% higher conversion rate by speeding up their website, and that meant $30 plus million out of $250 million in contributions. So we're talking about real business value here, so I think that's where the discussion really needs to go, and I think that's what it's going to evolve to. My summary to wrap this up, David, comes down to this for velocity conversion. What people need to know is this, mobile will no longer be, oh, it's mobile. Mobile and the web will be one. That was a sound bite we heard earlier. We're not going to, just mobile is there. It's mobile first, mobile everything is the web. That's going to be really standardized. Web performance is critical. The perception of speed is everything. Fast pathing to the right experiences for the right app. It's a user experience conversation in context to design and infrastructure. That's what velocity is about. Finally, you want to get under the hood a little bit, Dave, you're seeing stacks develop where tooling is moving up the stack. No longer, this guy has this part of the stack, this person has this part of the stack. You're seeing JavaScript owning the stack, other people owning parts of the stack, developing their own stacks in real time. Monitoring is big. Application monitoring, database monitoring, monitoring and analytics are everything. And finally, what Theo pointed out, which has been coming as a repetitive theme, is that existing workflows within large businesses in IT are changing and need to be completely reconstructed. Throw away your old workflows and look at building your own. Very prescriptive, people need to just get the playbook. So that's kind of where this is going. Very, very disruptive, very, very relevant to private cloud, public cloud, and agile application development for mobile, social and big data. So I think velocity kind of brings it all together, but it doesn't touch upon the static content. So that's my take here at Velocity. Dave, any final words for you? Go Bruins. Okay, we are calling that a wrap for day one. This is John Furrier and Dave Vellante at Velocity Conference Live in Santa Clara, California. We'll be back tomorrow for day two. So come to siliconangle.com, look for the blog posts. Go to youtube.com slash siliconangle and find all the content up there. This is a wrap, we'll see you tomorrow.


President Mohamed Abouhari will present the 2023 budget of 19.76 trillionaire to the National Assembly on Friday, October 7, 2022. The presentation will take place at the temporary chamber of the House of Representatives. This was contained in the letter by President Mohamed Abouhari and read on the floor of both chambers of the National Assembly on Tuesday at the plenary. President Ahmed Lawan, the Speaker of the House of Representatives, by this made known through a letter sent by the President. The presentation of 2023 on Operation B, may I give the kind and guidance of the Somerset Grant me the slot of 10 hours on Friday, that's 10 a.m. on Friday, 7 October 2022, formally present 2023 on Operation B at the joint session of the National Assembly. Please accept, Mr. President, the assurance of my highest regards as I look forward to addressing the joint session. Pure sincerity, Mohamed Abouhari. And so much colleagues, the event will take place at the temporary chamber of the House of Representatives and our amendments will be made to accommodate all of us including the President as a delegation from it.


for us, preparing the wall. But it doesn't matter. Callum Cook strikes, and Bradford City are right back in this at the city ground. Angle, would have taken short for Vernon. Vernon floats one over. And here's Cook, left-footed volley, low and true. And Bradford retake the lead. It's two good raking ball. Cousin Dawson. Cook sets off in pursuit, and he might just get there. He has got there. Cook with the chip, 3-1, a hat-trick for Andy Cook. And it's a perfect one at that. One with his head, one with his left. And then, here by O'Connor. Just a little bit loose in the midfield. Here's Callum Cook. Now, Vernon goes first time. Brilliant finish. The away-and-has-gone-mental at that equaliser.