Hi, I'm John McGregor. I work for Robert Busch GMBH in Germany in software research. This edition of ELC seems to be morphing into a Cooke's tour of home and work offices of Linux enthusiasts across North America and around the world. So I'd like to welcome you to my home office. Unfortunately circumstances have not permitted that I show it to you, but welcome nonetheless. Coons, age ago, I worked as a Unix developer programming in C. More recently, about 10 years ago, I worked at Bosch on Android applications in IoT. During that activity, I started attending embedded Linux conferences. About five years ago, I got the opportunity to work with the Cil2 Linux MP project, which is a privately funded public project that tried to certify Linux-based safety critical application at the Cil2 level under IEC 61508. When that project ended, I started working with the ELISA project, which is a Linux Foundation project that is working on enabling the use of Linux in safety applications. ELISA isn't focusing on any particular standard, but a considerable portion of the participants come from the auto industry and the interest in the ISO 2662 aspects of safety certification is considerable. Last year at the Embedded Linux conference in Europe at the Safety Summit, I made a presentation that basically said that we should learn to walk before we try to run with safety certification of Linux and I presented a number of measures that we could use in that direction. One of them was ensuring that the safety uncritical parts of the system still meet the expectations of the creditors and the safety certification agencies. This presentation is a result of the investigation that we did into that. My co-author, Nicol Papler, who worked as an accreditor, and I decided to start with ISO 262. That turned out to be a good start because 26262 is tailored to a more representative cross-section of industry that produces consumer products for the mass market. The authors have made some thoughts about how to use components in the development process. The topic is obscure and the corresponding terminology is obscure. I've tried to make the presentation more accessible, but it's hard to know exactly who's going to be watching it. I assume that it's either Embedded Linux enthusiasts that are interested in safety aspects or people from the automotive industry that are interested in certifying open-source software. It may not be admirable of me that I decided to record this presentation, but it has the advantage that when I will be attending the presentation and as the presentation unfolds, I'll be able to answer your questions in the chat and I invite you to provide questions. So the next question is obviously, how's it going to unfold? Well, we're going to take a look at the challenges involved and the situation in which they occur. Then we're going to look at the quality management areas that ISO 262 touches. Then the role that quality assurance plays in ensuring functional safety for safety critical products. Then after that, we will look at the strategies for using safety on critical software in a safety critical application and take a look at how those strategies would be applied to Linux. And then we're done. So the situation is that system integrators in automotive companies are looking at complex safety critical automotive systems. You can have software controlled power window control units when you want, but I don't think you'd really consider using Linux for those products. You're probably looking at products like in-vehicle infotainment applications where it's not exactly safety critical, but there are safety critical aspects or in instrument cluster applications as well. In some part, people are even considering using Linux in autonomous driving applications. And there, yeah, the safety criticality is a considerable factor in the overall system. At any rate, the systems consist of components, and components can be in themselves safety critical or they can be safety uncritical or they can have a mixture of safety critical and safety uncritical functionality. The point is however that components are off the shelf and that means that rather than being developed from scratch, they're integrated into the system. If you take a look at open source components, obviously the source code is available, but that source code could be provided by commercial agencies, not necessarily taken directly from the open source projects repository. It might be from a distributor or it might be from a consultant. Because the development process is critical to the safety application considerations, hopefully there's some information about the development process that was used in producing the component. Because it's a selection process, the source code should not be modified, but it could be trimmed up extraneous functionality before you try to certify it. That simplifies the challenge quite a bit. This presentation is about safety, but when you're selecting a component, there are other considerations. The component may have security vulnerabilities, you'll have to investigate that. Actually security aspects are also safety significant because when the system is hacked, the behavior of the system is not predictable. There are also aspects of embargo constraints that certain governments may not allow products coming from another country or including components from other countries. You have to understand the target market and the source of where the components are coming from. There's the typical Linux product problems of licensing and the component could be vulnerable to patent trolls and licensed trolls. These are all selection issues and not necessarily safety relevant, and this presentation is only about the safety relevant aspect. In a safety critical system, there is safety critical functionality, which is functionality that maintains the system in a safe state or brings it back to a safe state after a hazard event. This is the parts of the software or the system that is actually certified by a particular standard and it's accredited according to its integrity level. Depending on the severity of the impact of a hazard event, the standards may require higher levels of integrity in the component. That usually means that a higher degree of rigor is required in the development process. Safety critical functionality is usually just developed with the normal blog standard quality process. Contrast to safety critical functionality, the safety critical functionality or off the shelf components in general are qualified to be used in the safety critical systems. That means that the system integrator first has to choose a particular component. In the case of operating systems, you could have the choice between using an RTOS and Linux perhaps. And then after the system integrator has made its decision, then he has to justify that decision to the creditor. A basic problem is that open source projects don't manage quality like commercial organizations. At the beginning of the 2000 years, the British Ministry of Health commissioned a study into the bookability of Linux to medical devices.  And similarly in black British humor, the implication was that open source doesn't have this pedigree because they don't use the standard development process and they're more like Mongrels. So the goal of this presentation is to explore the actions possible to get QM accreditation for safety and critical functionality. The Silt to the Linux MP project, Eliza, Zephyr and Zen projects are all addressing safety certification of open source components.  The vast majority of the code in the system is going to be safety uncritical and it's probably a good idea to look at that first. So what is QM? What is ISO 26262 think about QM? As I heard conversations at the office, I didn't quite understand what they were talking about. It turns out to be quite an enigmatic term. QM designates what was obvious, what's the QM quality management system, but it's also an integrity level. What is an integrity level? Well, that basically means that the quality management system has produced a component with integrity equivalent to a commercial component. And over and above that, the QM qualification process involves demonstrating that the open source quality management process is essentially equivalent to the quality management process required by ISO 26262. So what does 26262 actually say about QM? First of all, sort of the obvious, the system integrator has to have a quality management system that's compliant with IATF 16949 in contraction with ISO 9001. ISO 9001 is probably reasonably well known as a quality management system certification standard and IATF 16949 is the automotive industry adaptation in the international context for quality management system. That means that there were different standards in different geographical areas for automotive quality systems, say in Japan or North America or in Europe. And this IATF standard amalgamates them all for use across all companies in the world. The next requirement took me a bit by surprise. 26262 has a way of classifying hazards based on how likely it is that you're going to encounter that hazard, how severe the harm is to people's lives or well-being resulting from the hazard and the ability of the driver to control the situation and avoid the damage. And the standard says, well, if the hazard is not that dangerous, if it doesn't look like it will cause much harm, then you can handle the safety critical functionality to support that with the quality management system in force in the company. It's a standard quality management system. Regardless of that, all functions in the system that have no safety requirements must be specified according to the quality management system in force. That means that there must be a specification for all of this functionality. There can be complex components where you can break them down into a part that's safety critical and a part that's safety uncritical and then use different measures to qualify or certify those components. So what does the 26262 expect for qualification of a software component? First of all, they gave a definition of component, which was nice because they also use a lot of synonyms. There's everything from items or elements or systems and systems and systems and then there's components. And what they defined for component is that it's actually a unit of functionality, either hardware or software, that could be good to stand alone testing and that it is defined at the architectural level. Definition of component was posed for hardware and software and therefore software component is just the same definition of software. So what do you have to do to qualify a software component in general? That means in safety critical applications as well. You have to define the maximum safety integrity that the component will expect. Then you have to define the intended use of the component in the system. You have to investigate and describe the known anomalies for the component. You have to specify its functional behavior and then the behavior in different types of exceptional situations. When the component fails, when the system gets in an overload situation, what does the component do? What are the response time and resource units requirements for the system, for the component? Also, you have to document the safety requirements in the current process and also the numerical accuracy of the component, which seems like a little bit of a strange requirement in the context of what we're talking about, but actually the standard was thinking of a software component more in terms of a math library, where you try to find something like the sign of 60 degrees and get an answer of 0.86 rather than more complex. At any rate, after you've selected the component, then you have to do an acceptance test and then integrate it in the system, and that's done with the usual procedures that are specified in the standard. What is the relevance of quality assurance to save the critical system? We have the situation where QM is now considered to be an integrity level, and the system to greater has a quality management system, and the open source project only does quality assurance, which means testing and reviews and coding standards and things like that. So the question is, how do we achieve QM integrity? The answer is by addressing and eliminating failures in the product. So a little bit of a digression to testing 101. There are error chains. I learned this as a mechanical engineer, but I'll take a computer science type of an example. A software component can have a fault, which is something like a coding error, which exists. But until the code is compiled and linked and installed in a system and the system runs, it doesn't have any effect on the system itself. At that point when the fault is encountered, it can produce an error, but depending on the type of the error and the type of the system, it may not be critical or interesting to the system itself. When the function returns a value or doesn't do it in time, then perhaps the last value can be used and is still tolerable. But then there are errors that lead to some sort of catastrophic event, which would be a failure. And it's the failures that we have to worry about in the safety context. So what are the possible causes of errors? First of all, there's what I just said, erroneous functionality. There are also hardware errors that occur from random events like radiation or cold that affect the hardware. There are systematic errors where the failure doesn't occur in the component itself. The component itself is correct, but another component is incorrect. And the failure cascades to the component under question and causes the component itself to fail. And then there are dependent failures where a good example is when the hardware fails, then the software will fail too. Then there are overload situations where the system is not performing because of lack of processing or memory resources or capacity on various communication links. So there are two basic strategies to addressing failures. One is to avoid them and the other is to tolerate them. And how do you avoid them? Well, you try to eliminate them in the development process by examining the context and developing appropriate requirements, developing measures to eliminate them, to avoid particular areas of errors being introduced into the software through review processes and testing. And on the other hand, you can introduce mitigation mechanisms to tolerate failures that occur when the system is running. First of all, you can use encapsulation to avoid, to put particular functionality in a partition that does not access the safety critical functionality and does not influence it in any way. You can have redundancy strategies where you have more than one example of a component and then if one instance fails, then another can replace it. You can have diversity to detect systematic errors. That means a good example of that would be to take a component and compile it under as 32-bit or 64-bit and have two different components. And then because there are different memory mappings and possibly different instructions being used, the probability of the two components having the same incorrect behavior at the same time are lowered. You can monitor the performance of the system, you can introduce checkpoints and validate the system producing correct results or you can take a look at the resource consumption in order to detect the causes of these problems. You can have diagnostics, in the worst case you can have a watchdog that resets the system when it doesn't respond and in certain cases you can substitute a more performant functionality with a less performant functionality and have a limp home mode for the system. This is a compliant development process for safety applications and the basic idea is that the system integrator defines the system and its context and looks at the hazards that occurs and then defines safety mechanisms and safety functions. That produces a safety concept. Then these safety functions and safety mechanisms are defined in the architecture and then at the architectural level you allocate the safety criticality to the particular architectural elements and then technical safety requirements. Like response time or resource consumption to those elements. Then you develop the safety mechanisms and you do that with the measures and techniques that are codes that have the rigor required for the particular integrity levels. After that you have to verify that the requirements have been made through testing. The idea of the testing is that you follow the requirements from the architectural levels of the design and the implementation and then you devise unit tests and integration tests that verify those requirements. So there's a traceability down through the development process for the requirements and across to the corresponding development steps in the verification. So now we're going to look at how to qualify a software component at the QM level. What does that mean? Well, that means that the system integrator will want to demonstrate to itself or after that to the accreditation agency with sufficient assurance that all interfaces of the open source component have been developed and are being maintained to an industrial level of quality. That it's an industrial strength component and that would make it suitable for integration in a safety critical system. And the special aspects of QMR that you still have to consider all of the error mode that can occur that would normally occur in a product that's not safety critical but you can neglect the hazard mitigating functionality. And that is in the context of reuse of an off the shelf component, not that's being developed from scratch. And consideration that we really haven't talked about so far that you have to consider the hardware on which the software component has previously been used. Safety safety community doesn't really believe in right once and run any everywhere. It's obvious that particular hardware components have particular vulnerabilities and have particular faults and each hardware platform has to be documented. And the experience on that platform for the software component has to be documented as well. So at the overall level there are a number of considerations that don't necessarily influence the strategy and one of them is simply the source of the source code. The system integrator has the choice of taking it direct from the project repository or from a distributor or some sort of amalgamation. Examples of that would be OpenELEC or Debian. There are two usual sources of source code for safety critical applications. In the first case then the QMS is only the open source projects QMS and in the second is the amalgam of the distributor QMS and the open source projects QMS. The next consideration is the essence of 26262. 26262 was derived from IEC 61508. IEC 61508 is a generic safety standard. It's actually a safety standard for developing for defining safety standards. And the idea is that based on the philosophy in 61508, particular industry branches or domains can define a domain specific standard. And 61508 talks about two types of product that can be certified. The Type A product is a well-known product. The failure rates are well defined and the behavior under fault conditions are well known and can be completely determined. An example of that might be an airbag control unit where we've had airbags for, I don't know, 30 years now and they're in most cars. And they come from a variety of suppliers and are used in a variety of automobiles. So the failure mode of an airbag control unit is well known. How often it fails is well known and the effects and the impacts on the system from a failure are also well known. I see 61508 in the case of Type A products then the industry is welcome to make a domain specific standard. Otherwise for Type B you should use 61508 and that's the fly in the ointment because if you take a look at the complex applications that we're talking about, such as autonomous driving, you can't say that there are well defined failure modes or that your rates are well known at the moment or that the behavior of the failure of an autonomous driving system has a particular effect on the behavior of the car or its environment. But on the other hand 26262 says that it's applicable to all road vehicles and then it becomes a question between the accreditation agency and the system and greater. What exactly that means? Another consideration is what I briefly talked about before. The clause in 26262 that addresses component qualification talks about simple components where the response that you get from an input is not dependent on the state of the component. In the case of a math library it's pretty simple. Like I said, it's assigned at 60 degrees, a bit of processing and outcomes 0.866. That's not the case for an operating system. The response at a particular interface may depend on the state of scheduling, whether a process has been preempted, whether there's intermittent processing going on, what's happening with the memory management, and so forth. In those cases you have to take a much closer look at what the exact requirements are for timing and resource consumption and what the responses must be. That usually depends on the knowledge of the components within the subsystem and that's called white box testing. And like I said previously, you have to consider the hardware platform where the system will be run. So when you're looking at QM, you have to account for all the failure modi, so even at the quality management level. And there the avoidance requires something like an industrial development process. In the context of the automotive industry that would be stipulated by ISO 26262. Fault tolerance means that you have to define and investigate the faults that occur while the system is running. And two typical safety measures for doing that is to identify the relevant faults. It's a failure modend effects analysis or a fault tree analysis. I won't go into the details of them. After you've done those analyses, then you have to take a look at the capability of the fault tolerance mechanisms that the component has. And then take a look at what the organization's normal bog standard quality management system would require to account for from interference and cascading failures. And then assess the gap between those two and define ways to fill those gaps. So basically the approach depends on the complexity of the component you're looking at. ISO 26262 doesn't specifically address whether you should use black box or white box testing at a particular integrity level. But what they do say is that at the lowest integrity level, structured based testing is recommended. Recommended is optional. You don't have to do it. That means that it's a question for the system integrator whether or not they consider it relevant to do. And if that's not the case, then you can say that the component is not complex and it can be qualified under the class that we've already seen. If the QMS in the system integrator requires structured based testing at ACL-A, then you have to qualify the component as if it was ACL-A. And yeah, I've been a bit of a wag here and said, okay, then if you're doing that, then QMS ACL-A-A or ACL-0. IEC 61508 has safety integrity levels from 1 to 4 whereby 26262 goes from A to D. And the mathematics makes more sense for a CIL-1-1 than you get a CIL-0. There again, in the end, you have to verify the component selection with an acceptance test and integration tests as you would normally do according to this. So, well, we discussed the Part 8 class 12 qualification requirements in slide 11. Yeah, basic review here. You prepare a specification of the component which then serves as the requirements for the component and then you have to demonstrate that the component complies with those requirements. Over and above that, you have to ensure that the component is suitable for its intended use in the specific product. And that would again mean an analysis of the hardware failures. And yeah, the components development process must be compliant in some way with a recognized standard. What ISO 26262 says is that you could also look at IEC ISO 12207, which is a software development process standard, which is interesting because things like ISO 9001 are pretty binary, either you're compliant or you're not. But in 12207, you can say, well, in this process area, what do I know, configuration management, we're compliant, but in this other one, we haven't quite made it like in review processes may not be thorough enough. And then you can document that and say, okay, we've partially achieved compliance and then it would be up to the system integrator to take a look at that and decide whether or not additional measures need to be taken to ensure that the overall compliance of the system is met. And so, yeah, basically, you have to prepare and execute a plan to accept the component and integrate it into the system. On the other hand, if you take the hypothesis that, yeah, we have a safety critical element that isn't safety critical, then you would follow the ACL A minus A approach. And what the standard does say is that when you have a safety critical element, the integrity levels are just for particular control flows through the component where they have to meet particular timing requirements or resource requirements. And the rest of the component, yeah, should be ACL. And that means that, yeah, if you have an element that doesn't have any integrity requirements, then you still have to produce it at the rigor required for that ACL level. You also have to account for all of the error modalities that are listed in the quality management system previously. And yeah, if you were doing this by the book, then the components QMS should be equivalent to IAT 6949 plus ISO 9001. Yeah, the first thing is that it's typical auto industry practice to substitute an A-spice assessment for the 9001 certification. A-spice is an automotive standard for assessing the maturity of a development process, which means that a customer is assured of getting the product that the supplier commits to. In the case of a QM open source component, perhaps you could drop the IATF 6949 part of it and simply try to certify that under ISO 9001, or even in ISO IEC 12207 as would be done in the qualification cause. Or yeah, you could try to accredited it at A-spice level two, which is a relatively low level of maturity. So what does this mean for Linux? Well, everybody I talk about who wants to put Linux in safety critical applications believes in Linux. Linux is in all kinds of high availability applications and also in all kinds of embedded systems like routers that have to be reliable. Nobody really doubts that Linux has the requisite quality and reliability to be put in a safety critical system. But unfortunately safety standards requires that one demonstrate the integrity of the system. Integrity is a matter of the technical properties and of reliable implementation. So it means that the error handling within the software has to be reliable and the system has to be stable. And the development process must avoid bugs as much as possible. But regardless of what you believe, you still have to demonstrate it or prove it in order to do that. So where could you get this evidence? Well, when you're taking a look at whether or not the kernel development process is suitable, there is a definition at kernel.org. And you could compare that to the requirements in 26.262 and see how far they agree. Other than that, there are other parts of the development process like requirements and design that are done within the community but not necessarily reflected in the development process at kernel.org. And it may be possible for particular parts of Linux to ask the community for additional information to support the certification effort. And then, well, for technical properties themselves, basically you're going to have to do it yourself and define the requirements that could be put on the kernel for safety critical functionality. And then you would basically do that by defining a use case and look at typical applications of safety critical software in embedded systems and see what the functional requirements and control flow requirements are on the Linux kernel. I mean, which interfaces in the Linux kernel are being used. And, yeah, in order to understand those interfaces, then you're going to have to look at the architectural requirements and understand how the kernel would be integrated into the system in general. So, yeah, if you look at the requirements management requirements in the standard, you could look, you could mine discussions in user groups and mailing listings, but unfortunately there is no defined set of valid requirements. And these requirements are needed to trace the, to be traced through the development process to validate the testing and the functionality that's produced by the development process. Similarly, there's no central architecture model. Basically, Linux was developed ad hoc based on different examples of different Unix systems and other academic systems like Minux at the time. It wasn't designed top down from the architectural model. Probably, for me, the biggest failing of Linux at the moment is that there's good focus on quality assurance, meaning testing and coding guidelines and continuous integration, configuration management. But when you ask, yeah, what is the quality of the system that is produced by the development process? How good is Linux at meeting the requirements? Yeah, it's not really known. And then the next question is, yeah, if the quality is not sufficient, what do you have to do to get it to be sufficient? What things can you do? And there again, that's not the way the open source community works. If the quality is unsatisfactory, then you have to introduce your own measures to improve the process and perhaps submit a new patch with the appropriate functionality. Over and above that, yeah, what can I say? Linux is more agile than the waterfall models that the state standards seem to prefer. And when you take a look at it, yeah, you can often argue that it produces the same results. And the Linux development process has strengths in functional development and testing and configuration management get is probably the best configuration management system in the world. There are small weaknesses in the requirements and traceability and change management, exactly how a change gets proposed and approved and implemented is not formally defined. And yeah, there's no tracking that it's consistently done in a particular way. And then there are larger weaknesses that requirements and definition is not done at all and that the architecture is not defined and that makes the requirement traceability much more difficult. So you can also take a look at what the facilities are that are already in the kernel and there are facilities for freedom from interference. Second, for example, limits the system interfaces that can be called by an application after a certain point. There are container technologies, which for different processes, depending on their group, they have different accesses to access abilities to different resources, which is regulated by control groups and name spaces and access controls. There are robustness facilities, Linux has a watchdog functionality and logging and diagnosis. So, yeah, it's not like you're starting from square one. There are things there that just have to be identified and defined and then brought into the context of safety qualification or certification. So a little bit about the Eliza project. The Eliza project is divided into three working groups at the moment. And yeah, basically, there are domain specific working groups for automotive and for medical at the moment. And these domain specific work groups should provide use cases where the use cases basically are a safety app running on user space lives. And somehow rather than this diagram, they've forgotten the obvious that user space lives are on top of Linux and yeah, Linux is running on particular hardware. The use cases contribute a safety function definition for that domain. And then some idea of the context in which these safety applications are running so that one can validate or understand the technical safety requirements that the domain has. So have for a particular part of Linux and the architectural assumptions that go into that. Yeah, the architectural group takes the technical safety requirements and the architectural assumptions and looks at how that will be positioned to facilitate the different safety mechanisms. They also look at the particular freedom from interference and fault. Mode analysis that could be done for the Linux and they will in the future define safety requirements that can be allocated to the kernel to ensure integrity features and provide conditions of use for Linux safety mechanisms that means describing the things that you have to do in order to use the Linux safety mechanisms safely in a particular product. The process working group is looking at how to demonstrate that the Linux development process is equivalent to the development processes that the standards expect and they're also working on Linux qualification. So what have they achieved so far? Liza's been running for a year. The process group has defined a reference project that combines the aspects of a number of safety standards and then they've surveyed the Linux development activities. With respect to those reference processes and are defining an initial gap. They're also doing work on patch impact testing and mining the kernel as I explained before patch impact testing quickly is one of patches accepted for a current release. Then it's back ported to various long term Linux versions and the system integrator has to constantly assess whether or not a particular patch in the current release affects the long term release that it is using. Over and above that the process group is doing a survey of static analysis activities in the Linux development process at the moment. The architecture group has identified and are investigating a number of architecture variants with hypervisors or co-processor container technologies and they're now working on a particular memory management safety app as a demonstrator. The automotive working group has just formed and they're working with the automotive grade Linux project taking a pilot application that HL is defined and working with the architecture group to look at the safety aspects of that pilot application. The medical devices working group has started examining the artificial pancreas system which is a system that takes a blood sugar measurement device and an insulin pump and combines them with a raspberry pi so that the blood sugar in the blood level remains acceptable automatically. It prevents a diabetic from having to measure it himself and inject insulin. They're all appropriate to the coronavirus problem at the moment. The group has also started to examine open source ventilator. So that's pretty well it. What have we learned? Well, Linux is stoop and it's not QM out of the box but a pure bread dog is not better than a pure bread. In this sense, there is nothing to say that Linux is not as good at QM level as a commercially developed product. Similarly, you would think from the title that QM is an issue for the development process but that's not true. It's an integrity measure and there are the aspects of fault tolerance. You've probably seen the safety accreditation is not simple and it's exacting and demanding and that QM qualification itself is a massive amount of work but because it's not safety critical, it doesn't really depend on any particular safety use case and it's an area where different companies should be able to cooperate. So the outlook is that the ELISA project is working on the topics that we've talked about today. The Zephyr project is an open source RTAS project also under the Linux Foundation and they have a more conformant development process and they're closer to safety certification at a higher integrity level. Regardless of that, we will need new certification approaches for open source software because the old ones are not necessarily appropriate. Thank you for your attention and that ends my presentation and now I'd be glad to talk to you and address your questions.


Live from Orlando, Florida. It's theCUBE, covering Pentaho World 2017. Brought to you by Hitachi Ventura. Welcome back to theCUBE's live coverage of Pentaho World. Brought to you, of course, by Hitachi Ventura. I am your host, Rebecca Knight, along with my co-host, James Kobielus. We are joined by Stefano Cellati. He is a Pentaho Solutions Consultant at Binova. Thanks so much for coming on theCUBE, Stefano. Thank you for having me. So, I should say congratulations are in order, because you are here to accept the Pentaho Excellence Award for the ROI category on behalf of Lazio Crea. Tell us about the award. Yes, as I was saying, I'm really proud of this award because it is something that is related to public administration savings, which is a good thing. First of all, for me as a citizen, let's say. This project is about healthcare spending. In Italy, the National Healthcare Services allows to drug store to sell medicines to total partial reimbursement by NHS itself. And they also have the possibility to replace the medicine with a generic drug which normally costs less to the people and also to the health service itself. So, a couple of years ago, the Regione Lazio, which is the political area to which your own belongs, just to explain, launched a new project to monitor, analyze, and inspect the spending flow in drugs. So, we partnered with Lazio Crea to create a business analytics platform based on Pentaho, obviously, and which collects all the data coming from the prescriptions and store it in an analytical database that is Vertica and uses PDI ETL tools to store this data. That's Pentaho data integration. Yes, PDI is Pentaho data integration, good point. And after that, we present the data in terms of reporting, analysis, dashboards, to all the people that are interested in this data. So, we talk about region managers, we talk about auditors, and also to local district users which are in charge of managing the expenditure for drugs. The outcome of this project was really impressive because we had an expenditure fell by 3.6%, which in a region where we have more than 200 million prescriptions every year means 34 million euros in a year. Wow. So, it was really huge result. We were very happy about that. And it was so simple because simply monitoring better the expenditure, monitoring how they deliver the drugs out, what kind of medicine they prescribe, and targeting what pharmacies sell to the end user, just gave these impressive results. And this year they are forecasting for 41 million euros in savings more. So, it's a huge result. It's something that is really for us really a good result. So, here in the US, I mean, we have problems very similar to what you just described in Italy. And just putting the transparency around the data would be a huge revelation for the United States too. How big a departure was it in Italy? Well, it was really a big problem to start because they didn't have any system to collect all this data. So, they had to set up everything from scratch, let's say, just by acquiring the paper where the physician writes the recipe. So, it was not that easy to build it from scratch. But after that, the region has had the opportunity to monitor this data and also to publish this data, which is something that in Italy is really relevant in this moment because we are talking about open government, we are talking about open data. And so, again, the result was really impressive. Do you see any follow-on opportunities to use this data for other purposes other than the initial application? Yes, we already experienced a different usage of this data because during the last major earthquake we have in 2016 in this area, those guys from Lacercarea were able to produce a list of the most needed drugs in that area just in a couple of hours, just by using the ETL and setting up this list that somehow helped the first aid units in giving the right assistance on time. And next steps will be about hyperprescriptions because we want to monitor if there are any doctors that prescribe drugs that are not really necessary. And also, we will also try to move our inspection also to hospitals because when you do a surgery, you get medicine, you get a lot of assistance in the hospital. So we want also to monitor that kind of the expert, which is, again, in charge of the health system. To make sure that the right medicines are being distributed to the right patients at the right time for the intent, the likely... This could also lead to something that is correlation analysis, meaning what is your pain and what are you assuming so that they can have an historical data that they can use to prescribe better medicines? But the anecdote he was sharing about the earthquake, too, is really compelling, too. If you think about a public health crisis, an outbreak of some sort, to be able to get drugs quickly to those in need, it's really astonishing. Again, this morning we were talking about data lake. This is a sort of data lake. We found several ways to use that data, to fish them back from the data, let's say, from the lake. And it's really impressive what you can do if you have the right information and you know how to use it. How do you see the market developing over the next year, next five years? Yes. The problem in Italy is that the market is not so responsive to innovation like others, let's say, US or UK and Europe. So for this reason, my company, Binova, set up an annual event which is called Big Data Tech. And the purpose of this event is to spread the knowledge about big data systems, products, architecture, and so on, which helps companies in knowing better what they can do with these platforms. So in the next months, we see a lot of opportunities. Generically speaking, data mining field. We start talking about predictive analysis with us, start talking about smart cities and other stuff like that. So again, we will need maybe to enter in a new phase of, let's say, evangelization because companies like Binova and others that operate in this field of business analytics need to put to general knowledge what other innovative companies are doing. So in the next months, we will, for sure, move to new architectures, new technology, and we will have to support all the companies with this kind of stuff. In terms of the new technology you're moving to, is there a role for the internet of things, both in your plans and really in terms of the Italian market? What sort of potential applications are there for IoT related perhaps to the use of it with health data? Going forward, in Italy. Yes, also for healthcare, but in Italy, the IoT team is a parallel line that is growing thanks to a governmental initiative which is called Industry 4.0 which encourages the use of interconnected machines connected to the internet. So the classical approach of the IoT field. So with this new approach and government sustain, we believe that the IoT will have a big improvement in the next years. Again, we're talking about Italy, so we are not so fast in growing. But again, we are starting to talk about smart cities for energy saving, sustainable energy and other stuff in which the IoT plays a key role. So as far as our business is concerned, that is business analytics. So on top of that, we see a lot of opportunities coming from predictive analysis which means to prevent the maintenance of a machine, for example, or to use virtual reality to simulate a laboratory test and other stuff. So with this opportunities, for sure, the usage of data mining tools such as WECA when we talk about Pentaro solutions could be a great advantage because you will apply the knowledge to your data. So you will not only analyze the data but you will also extract some sort of knowledge from the data which can help companies. Of course, Italy is where the renaissance began and this sounds like a renaissance use of analytics to help the Italian people and the Italian economy to continue to grow and innovate. Yes, yes. So I want to see not a data lake, a data coliseum. That's good. That should be on your desk. I want a data gallery with lots of data masterpieces hanging on the walls all around Italy. Right, exactly. You'll be the new Leonardo and Michelangelo. Oh, I guess so. Definoce Lazzi, I love it, great. Well, thank you so much for coming on theCUBE. Thank you for having me. I'm Rebecca Knight for Jim Covellis. We will have more from Pentaho World just after this.


Live from Stanford University, it's theCUBE, covering the Women in Data Science Conference 2017. Hi, I'm Lisa Martin, welcome back to theCUBE. We are live at Stanford University at the second annual Women in Data Science Conference. It's a one day tech conference and we are joined by Julie Yu, who is the founder and chief data scientist of Pymetrics. Julie, you are on the customer panel today. So welcome to theCUBE. Thank you, great to hear. You have, it's great to have you, such an interesting background. Thank you. Neuroscience meets engineering or engineering meets neuroscience. We'd love to, for folks to understand a little bit more about those two, how they're combined and also about Pymetrics. But give us a little bit of a background as a woman in the sciences, how you got to where you are now. So as you mentioned, my background's in computer engineering and I went into PhD program in ElectroPoint and computer engineering because I wanted to study artificial intelligence. I was fascinated by the notion of artificial intelligence. So my research topic started in automatic speech recognition system as in building computers to decode and decide for human speech. And after a couple of years, I got sort of frustrated with just the engineering approach or statistical methods based approach to improving the existing speech recognition systems that are out there. Because I thought myself, we're trying to make computers understand human speech and mimic human function when we don't really understand how our brain works. And I don't really know exactly what happens when you listen to you speak, when I listen to you speak and when you listen to I speak. Like what is going on? We didn't really have a good sense. So I wanted to study neuroscience. So I quit engineering and I went into PhD program in neuroscience. And there I started doing a lot of neuroimaging study, just looking at human cognition and just figuring out what is going on when people perceive and process these signals that are out there. And was your idea to eventually marry the two? I didn't really think about it that way, but it just sort of happened. As in like my background in engineering did sort of hold me into doing some of the projects that I did when I was doing my PhD and my postdoc. And while I was doing all of that, I just sort of evolved to be a data scientist without really me realizing I was doing everything that a typical data scientist would do. And this was even before 2008. The job title of data scientist wasn't even around then. So it sort of happened because of where I came from and because what I was interested in. And as I was doing that, like it just ended up being a good marriage. And then there it was. Talk to us about, tell people what Pymetrix is and what the genesis of this company was. Right, so Pymetrix is a platform that uses neuroscience based games and data science to promote predictive and bias free hiring. So how it became a product was because I was going through postdoc and my co-founder was also going through business school and we were both going through the phase of, okay, we don't want to stay in academia. What do we want to do with our lives? And at the time we realized a lot of the career advising tools that are out there were not scientific and they were not data driven. And we felt that there is a clear need for a tool that can actually use all these data that are out there to help people figure out what they should be doing with their lives. So I thought, we thought that we were uniquely positioned to use our background in engineering and neuroscience and build a product that could actually solve this challenging problem. And that's how we started Pymetrix. That's fantastic. You started about three years ago in 2013. So really getting rid of some of the biases, share with us what some of the biases are is it test scores, SATs, MCATs, GPAs? Well, there are many, many different kinds of biases in the hiring process right now. I think there is a preconception of what an engineer should look like and I think that plays a lot. And when you do going to an interview, like how you look and how you dress, that adds to the bias. There's ethnic bias, there's gender bias and there is bias based on test scores and what school you went to. So we want to sort of remove ourselves from that and really get down to what kind of person you are and are you really, I guess, have the right set of skills to succeed in certain job functions. And we do that by measuring yourself. Instead of taking your subjective answers from questionnaires, we do that by objectively measuring your behavior and these games are based on neuroscience research. So we know that they actually measure things that we want them to measure. Like for instance, your ability to pay attention, your risk appetite on all those things that we think matters as to what makes you good at certain things and not so good at some other things. So we use these objective data and data science and predictive modeling to come up with predictions as to how good you will be in certain career versus some other career. Really incredible need for that. So it's game based. So it's an actual game that people will play that will help understand more of who they are as a person, their behaviors, those patterns. Tell us a little bit about the invention of the game. What was it like? Who was it for? Right, so the games were actually sourced from neuroscience research community. We did not create these games. What we did was we actually just took them from research and medical settings and applied it through hiring.  So why not use it for hiring and just career advising? Because it makes sense. We're trying to measure your qualities, your soft skills and whatnot. Why not just use it for something that could really benefit from these sort of data? What we did though is we actually made these games. They're not really called games in research community, but we made it shorter and we made it more applicable to the things that we are trying to use it for. Because you took feedback from some of your early adopters who were saying, maybe it's taking me too long, maybe some of the recruiters might say, they gave you some very viable feedback that have helped you optimize the products. Right, I mean, as a data scientist, I always think the more data, the better. But that also means that people would have to sit in front of their computers and play an hour-long battery of games. A lot of people were thinking that it might be just a tad too long and companies felt that spending 45 minutes to an hour could be a discouraging thing and people felt to take effect and we could see that in the results. So we ended up making it shorter. We went from 20 games to 12 games and we cut it down to 25 minutes long and I think now we're in the sweet spot where we do get enough data, but at the same time we're not making it an hour long. Right, so this is really targeted for people coming out of university programs, whether it's bachelors, masters, doctorate, et cetera. And also what type of companies who are looking to hire, what's kind of your target market for that? So I think mostly Fortune 500 companies because a lot of these companies do hire in large volumes. So it helps to have us go to these companies and build their models based off of their employees. And if a smaller company comes along and they only have 10 employees in the job function, then it's extremely difficult for us to build a model based off of their 10 employees. Whereas if it's a larger corporation, then we can have 200 employees play and we can build a model based on their data. So yeah, so generally large corporations is our target client. I'm curious in terms of some of the data that you were saying that you were analyzing, are you seeing, if we look at data science as a great example of the event that we're at, report from Forbes recently that said it's the best job to apply for in 2017. We're looking at now what's going to be happening predicted over the course of the next year and that's a shortage in talent. Are you seeing with some of the data that you're taking in, are you seeing things that are mapping to that, like people that are really geared towards that? Or are you seeing more companies that are looking for computer industry data science type roles? Is that increasing as well? I think companies are definitely looking for more data scientists and I think also people are figuring out that there are data science programs like graduate school programs and I think the supply of data scientists is definitely increasing but at the same time or more so, the demand for data scientists is increasing and not to mention the available data that's out there is increasing at a faster rate than anything else. So yeah, I mean it is I think the best time to be a data scientist right now. And let me ask you one more question about looking at skills. So we have such a great cross-section at this event of leaders in retail and obviously what you're doing in the neuroscience gaming merging world. We've got professors here. It's such in data science is such an interesting topic. It's obviously very horizontal from a skill set perspective kind of the traditional skills of being a statistician, mathematics, being a hacker. A lot of things that we've been hearing around the show today and really aligns with what you're doing is more on the behavioral insight side of you have to be able to communicate what you're seeing and be able to apply it. I'd love to understand the profile of an ideal data scientist that you guys are seeing from your data. What are some of the other behavioral attributes that maybe you're some of the non-teachable things that you're seeing that really come up that this would be a great career path for someone? I think personally, I think like intellectual curiosity is number one and they would have to have strong self-motivation and discipline because you could love like analyzing data and you could just be doing that for how many days I don't know. And that said, you need to be to actually come up with a good story. You got to be a good storyteller. And if you have artistic flair to make the data vis like beautiful, then even better. But it is important to go from beginning of the project where you have a bunch of data set and actually come up with actionable results that people can use. And you're not only always going to be communicating with the data scientists. So you do need to be able to present your data in a more succinct and easily digestible way.  Give us a little bit, last question here, just a little bit of an overview of what your data science team looks like at Pymedrix as you're helping to leverage this data to give people opportunities with careers. What does your team look like? Our team has very diverse backgrounds. We have a few PhDs in physics and we, well I have PhD in neuroscience and there's another data scientist with PhD in physics. We actually have one guy measured in data science and we have another guy who measured in bioengineering. And yeah, so it's definitely diverse background but general theme is that you do need a good quantitative foundation. So whether it's engineering or physics, it is helpful to have that statistical or analytical mind and if you can actually apply that then I actually love solving problems and I think data scientists is a right role Sorry for interrupting. You're on the career panel at Woods 2017. Is that the advice that you would give to kind of the next generation of kids that are interested in this but aren't quite sure what industry they would want to go into? What industry? I think if they're even remotely interested in going into data science I would encourage them to pursue it. I think it is one of the most fascinating fields right now and there's never going to be a shortage of needs for data scientists. So if you like it, if you think you are going to be pretty good at it I say go for it. Fantastic. And you've got a great audience here. This is being live streamed in 20 cities. I think across the globe are 75 cities. I have to get the stats right. But there's a big opportunity here to be an influencer and we thank you for spending some time with us today. Best of luck on the panel. Thank you. Thank you for watching. We, I'm Lisa Martin. We are live with theCUBE at Women in Data Science 2017 hashtag WIDS 2017. Stick around. We'll be right back.


Everybody, Steve McFarton here at Monview Dodge. I'm with Zach, came from Lethbridge, picking up his 2020 Longhorn 2500 diesel, gorgeous truck. Hope everything went well for you, Zach. Truck is what you wanted. You bet, Jeff. Everything. Awesome, well, out here, remember your mask. So come to Monview Dodge, see me, Steve McFarton, and Zach, thank you very much for coming all the way up here to get a truck from us. Thank you very much. All right.


Hey people, I'm Ginny Metherall and I am a fourth generation witch. Today we are back with my ever popular Almanac series looking at all the witchcraft rites and rituals that you might do throughout the month of May. As always with these videos what I'm going to do is to give you a general overview of the witchcraft trends that are happening in May and then we'll get into the nitty gritty detail of the day and what witchcraft works best on which day. So to the general overview I love May, don't you? It is literally one of my favourite months of the year and I think it's madness to leave the UK in the month of May because it is bedecked in the gloriousness of its Hawthorne or May blossom and it's so pretty and smells so amazing and ladies laces coming out and bluebells are here, the birds are singing, it is just glorious. I love the Hawthorne and this is what makes May so magical, this frothy, creamy, wonderful flowery-ness. It is a flower but bedecked literally the whole of the UK in its white bridal glory and in fact it was used in bridal bouquets to signify purity and it is also one of the trees that is beloved by the fairies because May is the month of the fair. You've got to beware, the first and third of May are the particular days when you must beware of the fairies because that is when they're holding their revels and the fairies are incredibly jealous of beauty and so if you have a beautiful newborn babe they might swap him for one of their own little changelings but they've taken your beautiful babe down to their kingdom. It is between the first and the third of May when you are most at risk of having a changeling substituted for your beautiful babe that is lying prettily in their cot so what you must do is take primroses and line them across your doorstop and this will prevent the fairies from entering because it forms a barrier for them. Primroses are very associated with the fairies and they're like a gateway flower so you can use them in seeing the fairies, in using them toward off the fairies and if you brew them into a delicious wine you can transport yourself with your primrose wine into the world of the fairies. They are a gateway drug to the land of the fairies. I mean watch out they're pretty fickle creatures fairies and easily angered and not above a bit of kidnapping so do take care to not anger and upset the local fairies. May is also a time where traditionally witches would go to the sacred grottoes and wells and springs to bless them to ensure that the water flowed for the coming year so should you be in Derbyshire you might know this as well-dressing. They decorate their local wells with wonderful flower panels which is made by the local populace so on the Isle of Iona which is off the coast of Scotland there is the well of eternal youth. This one's a bit like the Blarneystone in Ireland where if you kiss it you will have great communication skills and talk non-stop. I don't know if that works actually because my father kissed the Blarneystone and he was known as being very silent but actually he could communicate quite well through his silence so maybe however back to Iona go and bathe in the well of eternal youth there and you will keep your youthful glow for the rest of your life. May is the time of the flowers and of course there is the beautiful Hawthorne which is currently bedeck the hedgerows of the British Isles at the moment but there is also the marvellous Lily of the Valley. Victorians adored Lily of the Valley they said it represented chastity and purity and so it was often put into wedding bouquets so the bride was obviously saying that she was chastened pure. However there is a wonderful story that the Lily of the Valley actually was brought into existence because it sprung up from where the blood that of the last dragon that was slayed in England had fallen on the floor the Lily of the Valley sprung up and May is also the time for the Dawn Chorus. The Dawn Chorus which is starting at about three o'clock in the morning I think at the moment I did actually wake up this morning to listen to the Dawn Chorus by mistake you know I just woke up and as it got light I did hear the first bird start to sing which I think was a robin by the time I went back to sleep about half an hour later it was rowling around with all of the birds singing the little hearts out it was very very charming and finally for May May of course is named after the goddess Maya who was a Roman goddess of growth and fertility and we'll get on to this in a bit later in the video with the jack in the green who is a symbol of fertility who dances through the streets of our villages and towns to bring in the May which is just a celebration of everything fertile that you could possibly want anyway so that's my overview for the month make sure you beware of the fairies because it is their time and you spend a lot of time with flowers you need flowers in your life during May so with that said let's get into the details so of course May starts on the first now the first of May as we all know is the Sabbath of Beltane but I'm not going to talk too much about Beltane in this video because I've already done a couple of videos because it's a sort of two-part about how to celebrate Beltane I'll put the videos up here for you so if you want to go and have a look and see what they say there's two of them because Beltane is a feast of two halves so it's the 30th of April and then the first of May but apart from that the first of May is a huge day it's one of the biggest witch's Sabbaths of the year and it's so pagan it has been celebrated by ancient Britons right through the ages and although lots of historians say that it was the Victorians who regenerated May Day celebrations well they might have done however they were quite big in Henry the 8th's time otherwise May Day very important that you do dance around the made pole and try and watch the Sun as it rises because when it rises up above the horizon you will see it take three leaps for joy in honor of this day and if you want to help out a friend take them a branch of May and leave it by their door don't take it inside their house leave it near to their door because this will bring them luck for the year there are certain days of the year that just have that magic about them a shimmer in the air or sparkle in the smile and May Day or Beltane really is one of those days there is such a frisson and that's sexual climax May Day is a very very auspicious day to get pregnant on so try your hardest if you're looking to have a baby to get pregnant on May Day the fifth of May is the day of the full moon the full moon is in Scorpio and Scorpio is a water sign and is deep and filled with passion so should you wish to make some moon water on this day the moon water that you create will be great for any spells that concern relationships this month's moon is known as a bright moon a flower moon or a milk moon in May cows can be milked up to three times a day I mean and so month of May is all a flowing with milk this moon is slightly special because this is the day when there's going to be a penumbral eclipse meaning the moon passes through Earth's shadow and there is a lunar eclipse so lunar eclipses attend to be looked on with great suspicion and dread watch out tradition states that should you be pregnant on the fifth of May and you go out into the moonlight the moon will not give good blessings to your unborn child so pregnant women stay indoors third of May is one of the unlucky days of the year so don't start a journey begin a task or get married on this day don't do it on the third of May just stay indoors and watch box sets on telly because this apparently was the day when the heavens expelled the dark angels now I'm not into the Christian version of the god expelling you know a golden st. Peter and st. Michael expelling Lucifer from the heaven however there was some altercation and today is the anniversary of that the 7th May is the day of the accurate meteor shower and what do you do when you see a shooting star which you might well do if you go outside on this night you make a wish wish magic is a complex magic systems you want to make a wish on this day the best thing I would suggest that you do is make the wish for yourself don't wish for other people or anybody else wish for you it is also the last day of the actual belting festival now belting festival of the old days although it started on the 30th of April it finished on the 7th of May so communities would celebrate belting somewhere between these dates not necessarily on the 1st of May they might have gone out on the 1st of May of part of their May Day celebrations but the belting festival does last for seven days apparently children born betwixt the belltains i.e. between the 1st of May and the 7th of May have great power over man and beast if you're a belltain baby and your birthday falls between the 1st and 7th of May let me know in the comments below because you do have a particular energy to you the 8th May is one of my favorite festivals of the west country and this is the helst and furry dance which is where the townsfolk dance up and down throughout the town in and out of each other's houses um i think they do it four times in different parts of the community do it at different times but it is something that's been going on for so long and it's obviously the leftover of some pagan festival of May it's the spiral dancing with your partner it's all about you know winding the energy of the earth up go and have a look at it if you're in Cornwall because it's a fabulous day out the 13th of May is known as Old May Day due to the vagaries of the calendar changing over the years Old May Day will May the 1st used to be on the 13th and many communities in the UK still celebrate the 13th of May as Old May Day for example Garland Day in Abbotsbury which is just around the corner from me this is where they parade through the village with garlands of flowers carried by the children it is quite a witchy area that if you go to the top of the tour which is by Abbotsbury you'll find St Catherine's church there which is actually built on an old pagan site as the Christians often did and it's really it's a leyline cross up there and if you want to go and feel some leyline energy do go take your dowsing rods have a go at finding where that leyline cross actually is the 19th of May is the night of the new moon new moons are believed to have a particular energy depending on what star sign they are in this new moon is in Taurus which is an earthy and steady sign of a practical nature who is very protective and likewise family orientated if you have a family orientated new task why not start it today the 23rd of May is a spectacular day for palm readers should you wish to have your future told by a palm reader go to them today because today their prognostications will all come true so traditional witchcraft states it's not known as palm readers day it's just known that this is a great day for palm reading divination so this is what you can do on the 23rd and so that concludes the daily nitty gritty ideas of witchcraft on what you can do and when may as I said is one of my favorite months and I love the belting festival almost above all others possibly not halloween though I can't decide but belting and halloween have equal attractions for me personally belting is such a special time it is one of days where the veil between the worlds is at its thinnest so you can do lots of divination spirit work on these days and I would suggest that you have a go let me know in the comments what you think I would love to hear your thoughts and otherwise don't forget my coven meeting will be coming up in a couple of weeks so go to patreon.com forward slash a ginny mezzaroll for all the information I hope to see you there we are having a thrilling time at the moment everyone's come on so well you know leaps and bounds the whole of the coven I'm very pleased with the all well done coven please also don't forget to like and subscribe because it really helps my channel and enables me to continue making these videos for you I will see you therefore in another few days


Hey guys welcome back to my YouTube channel, this is Daniel Rosal here. Another video about the Canon XA40 professional camcorder, an absolute beast of a device from Canon. The bottom really of their 4k capable professional camcorder range beautiful product. Absolutely loving every single day shooting with this guy. And as I'm learning about the camcorder through daily use and you know thinking of things too that might be of interest to other users I'm just throwing up these videos. So one of the points I realized using this is there's actually three different ways to control zoom which if you're coming from a DSLR mirrorless might seem a little bit ridiculous but that's kind of the beauty of the camcorder form factor and that's why these half historically remained the normative or really popular choices amongst people working in ENG electronic news gathering broadcasting documentary work because where DSLR mirrorless pack a lot of stuff into the menus the beauty of camcorders is that you've got a ton and ton of switches it sometimes looks it reminds me a little bit like the you know flight control panel on a Boeing 747 you've got knobs and dials and buttons everywhere but that's actually a real advantage when you're out training get stuff done quickly just want to you don't be reaching into menus you want to just be eventually it kind of becomes a muscle memory that's the idea behind this so the three ways to control zoom on this camcorder so firstly you have at the front of the camcorder you have a ring there's a single ring here and this is an interchangeable ring that can be used to either control the focus or the zoom now the way that that is controlled is in itself a switch I'll just lift up the camcorder here and I hope you can make that out just to the just to the left of the viewfinder there is a knob that toggles this between focus and zoom so I currently have it set to zoom and if I flip that up to focus this ring is now controlling focus so that's if you like the manual feel of actually moving a ring as you adjust your zoom you'll really like this it just feels so so good now one one other good point I'm just going to clear off my desk a little bit to try whoops one other point about this worth mentioning is that you can control the zoom speed for all these three things differently so that might be really useful if you want to say well I want the zoom speed on the ring to be fast and on the rocker which is going to be the second thing I want to show you guys rocker is right here and the rocker is slow or at the top handle is slower so you can actually have different zoom speeds for each of the three ways so that's number one is you're going to show you the menu options for adjusting those speeds momentarily it's a little bit off-balance because of the weight of the shock and microphone here so number one is using the zoom ring number two is using the zoom rocker and this is probably the way that a lot of people will be most familiar with it's their labels w and t which stands for wide and tight so this is tight and this is going wide this for reference is the battery and the viewfinder so as I'm pushing down I'm going wide and as I'm pushing in I'm going tight and as the optical zoom is in transition you'll get on the menu a little sort of it's like an arrow and it shows you as you're moving from from wide to tight and finally I know I'm using this guy always with the top handle connected because I bought this camcorder specifically to have accessorization and to get the procamcorder look so I leave it like this and on the top handle you have here you can see I've got a light in the cold tube but just before the light I have a start stop button for record and just to the left of that there is our third zoom tight and wide again and this one is a smaller one so these can all be controlled as I mentioned using the menu so I'm just going to show you guys how that process works interestingly you can actually disable so I actually was finding when I first started using this this a little bit annoying because I kind of accidentally zoom when I didn't want to but that's up to you so go into the menu and you have soft zoom control is off so if you actually want a fourth way of controlling zoom you can do that in other words soft meaning it's going to be on the menu you can actually enable digital zoom as well you've got your 400 times or digital tele converter I haven't used digital zoom because to be honest the 20 times optical zoom just gets me so far I've never needed I never even I rarely even needed the full telephoto length of it zoom speed level right so this is your normal fast and slow grip zoom operation enabled grip zoom speed now you have to look at the manual to know which one of these are but this is important handled zoom operation so this refers to the zoom rocker here and this is where you can enable or disable that so again if you're using the camcorder a lot like this and this is how I use it frequently you might find that you're you know your kind of knuckle is rocking up against that zoom handle and causing you to zoom unintentionally or the record button that's why I imagine the record button actually has a locker you can lock off the record button so the zoom rocker on the top handle doesn't have one but what you can do instead is if you want to you can disable it using the menu here let's just see what else there is handle zoom speed okay so here's the one I was looking for so I'll end up with this on page four of the camera menu you have a focus zoom ring operation so remember that this little ring towards the front can be either focus or zoom you can actually disable it so if I disable it now it's going to do nothing enable it is good and the zoom ring direction and zoom ring sorry zoom ring direction ah zoom ring direction if I too much coffee as usual before shooting a video can be normal or reverse so that's something to bear in mind as well there so there's no way to soft change that so you just have to go in there and toggle between zoom and focus so that's it those are the three ways you can control zoom on your Canon XA40 and I believe the 50 and the 55 and the 45 all have the same functionalities just to summarize quickly you've got a you've got a ring that a physically operated ring at the front of the camcorder and that can be interchanged between zoom and focus by that little knob just to the left of the OLED viewfinder secondly you have your classic zoom rocker located just to the right of the of the OLED and that's the one I probably use most on a day-to-day basis and finally on the top handle you have an additional record button and you have an additional zoom rocker there that you can use and that should give you plenty of options and you can adjust the zoom speed in the menu and you can also if you want finally just to give yourself all the possible options you can enable soft zoom control that can be controlled with the touchscreen LCD hope that video is useful if you own the XA40 or XA series of Canon pro camcorders and if you want to get more videos from me about a whole miscellany of topics please feel free to subscribe to this youtube channel


Hi everyone, Joe for Jaspy's casebreaks.com coming at you with a one box break of 2020 Topps inception at baseball with a chance to win two transcendent spots in this one. That's pretty nice. In break, it says two right here, it's actually break number three. Big thanks to all of these folks for getting into it. We sold 29 spots because there's no cardinals. So let's do the break first and then we'll re-randomize your names in a different dice roll at the end just like it's break credit and then we'll see who wins the two transcendent spots. Let's roll. Let's do the break first. Five times for each list on this one, one, two, three, four, and five. After five times, we've got Robert down to Stephen after five. Five times for the teams. After five times, we've got the Halos down to the tribe. All right. So there is a list right there as is. Zach with the Mariners, last spot mojo, sort by column B, by team, TWC, trade window closed. Let's print, let's rip, and then let's see who wins those transcendent spots. Could be a monster hidden here too. The inception is pretty nice stuff. There's the final print out right here. Then we've got Luis Areas, 78 out of 245. That's for the twins. That'll be for McCarthy, the whole point of this, of course. Who's going to win those spots? Just once is fine, Joe, and we've already done those. All right. Let's roll it, randomize it, two out of three, five times for this list. Top two names. Top two spots. Get spots in transcendent Hall of Fame number three, two, three, four, and five. After five times, congrats to, and thanks everyone for giving this shot. There'll be more opportunities to try this as well, try to get into transcended. We got Robert and Wade, nice. So congrats to both of you. We'll see you for that break. Thanks everyone for giving this a shot. I'm Joe. I'll see you next time for the next one. Bye-bye.


Now that the holiday season is in full swing, so is the annual Kettle Campaign for the Salvation Army, but many locations are in need of bell ringers. In Bemidji, there are six Kettle locations that are in need of bell ringers. Volunteers are needed to work two-hour shifts now through Christmas from 9 a.m. until 7 p.m. Even though some locations have already been ringing, the need is now, and there are plenty of shifts that still need to be filled. Usually it takes a couple weeks into December maybe to start more so the ringing. We did have some ringing over Black Friday and the day before Thanksgiving, but most of them start the second week in December. Many Kettle volunteers say the experience is fun and extremely rewarding. Last year's Kettle Campaign brought in over $45,000 locally, and volunteers say that bell ringers are a crucial part to the success of the campaign. Some locations and some communities, they just put a Kettle out, and when you have somebody there at the Kettle and you can interact with people, we seem to do a whole lot better. For more information on how to get involved, we have posted contact information on our website at lptv.org slash news. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Hi everyone, Joe for JaspysCaseBreaks.com coming at you with 17-18 Prism Salo Pack Break Number 4. Random team break, we can win 4 spots in that break right there, which is close to being sold out. So, we're going to give away 4 spots at the very end of the break, but let's do the pack break first. Big thanks to all of these people for getting into the action, really appreciate it. All 30 teams are in. Let's roll it, let's randomize it. 6 and a 3, 9 times for each list. 1, 2, 3, 4, 5, 6, 7, 8, and 9th and final time. After 9 times, we've got James all the way down to James. Alright, 6 and a 3, 9 times for the team. 7, 8 and 9th and final time. After 9 times, we've got the Charlotte murder hornets down to the Cleveland Cavaliers. Alright, there you go, McCarthy, no, this is a 17-18 breaks. Where's Boston? There you go, Mike Sommage, Boston Celtics. I mean, that's pretty much what we're looking for, right? Jason Tatum's in the 17-18 Salo Packs, maybe a couple others. But there you go, no trade window, it's just a quick little pack break. So let's get all this on one screen, if possible. Can I get this on one screen? Alright, there we go. Let's sort by column B by team. Let's print, then let's rip. Alright, trade window closed. TWC, trade window closed. Alright, so there's the final print out right there, same as the previous screen. So let's do this little pack first. Kyle Kuzma's a rookie in this too, that's right. There he is. De'Aaron Fox, can we find silver versions of them? No, Jalen Brown, Celtics. N.O.O.B, Joe Johnson. What have we got here? Kyle Ulis, Marcine Gortat, and Cinderius Thornwell rookie. Alright, nothing too major there. But the major thing, of course, is seeing who's going to win those spots. So once again, four spots in immaculate basketball at full case break on jaspyscasebreaks.com. Let's grab everyone's names here, new list, just like we're giving away a break credit. Let's roll it, let's randomize it 11 times. Top four after 11, good luck. One, two, three. In 11th and final time, thanks everyone for giving this a shot and congrats to the top four, McCarthy, Daniel, Dustin, and Andrew. There you go. So you'll be in that full case break of 2018-19 immaculate basketball. Thanks for watching. Thanks for breaking with us. I'm Joe, and I'll see you next time. Bye-bye.


someone on one of the videos commented that they'd like to have a breakdown of what my avionics what my systems on board are so I've got a NEMA 2000 network this is a new heading sensor Garmin heading sensor I've had to add that because up there and I'll show you from the outside that's a point one GPS and heading sensor but it's got a knob and an anomaly which means that I've had to add another heading sensor up there is a Bluetooth receiver for the wind and it's still that's two years that's been disconnected so this is the NEMA 2000 which one is it's this one here which comes down here that's the VHF radio and down here and here we've got the end of the backbone that's the resistor there so connected here is the heading sensor the Bluetooth receiver for the wind and the point one GPS receiver down here is the connection for the the log and speed the DST 800 and this one's spare now because my Wi-Fi dongle has just failed bastard so I should have cleaned up before I made this so down here that's the DST 800 speed depth and temperature and the and the network goes in this conduit the backbone goes in this conduit and it comes up into here here's the other end of the of the backbone and the terminal resistor is on the far end there so connected to this we've got the display in the cockpit the radio the AIS transponder and the autopilot now here's the radio it's a v50 radio and I don't know if you can see anything it's too dark probably but that's the Camino AIS transponder in the back there here is my my fuse box I've moved it from behind here where I couldn't get it without taking off some screws to behind here added some extra structural to because of the bending there yeah this little buzz bar here is internal light buzz Poz and neg there's my custom panel this is the Simerine Pico battery monitor and so this is the main screen barometric pressure time you can set this UTC or local battery condition main battery condition and charge or discharge state I haven't got the the charger plugged in yet what other pages so there's the house battery with the condition the current voltage and time until the discharge or fully charge when it's charging so more than 10 days discharge and then separately I've got a voltage measurement for the starter battery and the two but I'll show you in a moment with two batteries have got a voltage sensitive relay between them so regardless of whether I'm charging from the alternator or from solar or from shore power they'll both get charged that's the internal temperature I could add more temperature gauges and tank gauges but I just haven't got around to it to be honest I wouldn't mind a fresh water tank gauge except I don't know how much goes in there so I would have to calibrate it as well and the barometer which is cool because you can see you've got a long-term trend there three-day trend but you can set it to three hours 12 hours 24 hours or long-term three days so you can see in there the green going arrow going up tells you that the pressure is going up in you get ours going down and it also does some kind of flashy if it's changes by too fast a rate which I can't remember what the rate is switches for the network NEMA 2000 autopilot the Wi-Fi is not for the Wi-Fi anymore it's for the transponder my internal 12-volt USB sockets out one of which is here I've just I've just fed these guys so one here and the other one is here so they're now in convenient places for where the stuff actually is when it when it needs charging I used to have you might have seen on the old videos a big thing on here but I've taken it off now and I gave that a slap of paint as well just to tidy up a bit my main house battery is in this compartment here which is a dedicated battery compartment because it's a very heavy battery it's 218 ampere hours of weighs 60 kilos so it's extremely secure in there and then in here what have we got in here obviously I'm not in sailing mode which is why it's all a bit of a mess so this is a starter battery in here it's a 75 ampere start about just more than adequate it's always charged negative mean a neg buzz there my initial design was a bit off so I had a big buzz here and a small buzz behind there really I should have had them the other way around and now I've got a big pause and neg buzz behind here so this one hardly gets used at all there's a positive stud here which actually the boat yard in Falmouth fitted that when they when they built the battery box for me but it's not really what I wanted I wanted a buzz rather than a stud but you know it's too late it was already fitted this is the solar controller here and this is the battery charger from shaw power here which I even when I'm sitting here in the marina I rarely plug that in because I don't need it because the solar power does everything and this is the shunt for the battery monitor that's the VSR the voltage sensor relay which will connect the two batteries together whenever there's a charging source on either side on one side is the alternator and that's on the starter battery side and on the other side is the shaw power and the and the solar they're both Victron products the shaw power and the solar charger they're cool oh and here is the battery switches to combined it's a dual switch so it turns both the batteries on or off and you can combine them using this setting here there's a combined function on the VSR but I don't use it if I was going to use it actually I've used this once or twice just to check that it works and then you get both of the batteries going to the starter motor but to be honest the engine starts up perfectly on there every time on the on the engine battery she just takes a couple of revs to put out the the low oil pressure warning we just have to start up just because you know she's loose loosey-goosey and it's a Yanmar 2 Q M15 from from the 1970s there she is a little bit dirty like everything so that's the 2 Q M throttle and the stop is there obviously that's the fuel control unit and filter that's the water pump is here so to get to the impeller which is in the housing here you have to take the whole water pump off you have to undo two bolts here get it off get the belt off turn it around then you can take the backing plate off so obviously more modern engines have got a much easier access to impellers than this one luckily I never seem to have any problems with it back there's my Reco filter on the fuel line here that's the water in the plate seat got the strainer is always good checked it recently what else to see ah this is the the greaser for the stern tube old-fashioned greaser these cables go down to the bilge pump which is down there it's too dark to see the compression lever is there I have hand started this twice I failed to hand start it about a dozen times so I don't bother trying I guess if I was really desperate the adrenaline would kick in and I might eventually get it going but yeah started off I mean I was really surprised the first time I tried it I succeeded but after that next time I tried it didn't work alright I got to put the camera down to put this back so then we'll go outside so the autopilot is connected to the network and now that I've got the new heading sensor fitted everything's working properly so I can show you this is the the truck Triton to display which is really got everything you could ever want in a in a sailing instrument so this is a sales dear page with true and apparent wind the indicators the yellow dot there is the waypoint and I set the waypoint in the radio because the radio's got a nav function it's connected to the network so if I set a waypoint in the nav radio it shows up on here so I can steer to it this is the boats course over the ground you see we're not moving so it's parked on north right now and heading and then port and starboard tack and it calculates those lay lines for you you can set various parameters for the AIS display is here heading display this is this one I use for performance because here we've got apparent wind angle and speed and VMG so that's a performance page this is a easy heading page although we can see my super cool old compass right there and they are now because I've just literally in the last two hours I've spent an hour and a half motoring in circles to calibrate the compass correctly and it's finally finally calibrated so look there's the autopilot in standby mode and back here is the autopilot it's actually I've upgraded to a TP32 the 22 was fine but in in heavy courtroom winds it struggled a little bit and it started to make funny grinding noises it still works perfectly well but I thought I'd try 32 and so far it's been brilliant so I can put it into autopilot mode and we can see on here that it's now in heading hold mode but if I was sailing along and trying to you know trying to sail on the wind I could put it into wind mode to put it in wind mode you push these two together and there we can see it would now hold an apparent wind angle which is good for going upwind but it's no good for going downwind because when you're going downwind the apparent wind angle changes rapidly as you accelerate and decelerate off waves the boat would end up steering all over the place if you tried to sail on apparent wind downwind which is why I'll put this back into standby now so you can see it's back in standby mode that's why all the raceboats use true wind steering downwind because apparent wind steering sends you all over the place yeah so that's it autopilot what else systems wise have we got well for navigation I've got the iPad iPads currently in its relaxation stand there so I can watch movies and YouTube while I'm not enough to sleep and of course the Garmin in reach in reach Explorer plus or whatever it's called that's my track an old tide computer there which still works but it's much easier just to look it up on my iPhone and that's about it really I've got some washing up to do but that's my galley that's all I've got little handheld radio oh here's new you might have seen on some of the old videos it was a big like a pipe sticking out of here like a chimney but it was actually a homebrew mount that the previous owner made for his little handheld Garmin it was a bugger to get it off but I've replaced it with something fancy this looks looks nicer just a vent so yeah that's finally gone that's one of the many little modifications I made this time round yeah so that's it really that's all the systems are to show you the receivers so that you saw them from below and this is from above that's the point one and that's the Bluetooth receiver for the for the wind and they're my Doraid Doraid boxes in deep need of some scraping and and varnish and that's going to be my job next week after I've been sailing again for a bit