Today is all about the top three tips for becoming a better insurance salesperson. Insurance and succeeding in sales, right, is not the easiest thing you can do. But there's three things that will help, three things we're gonna touch on today, and three big reasons why you need to stick around and watch this entire episode. So today, the first tip, is all about energy and interest. Your energy affects the outcome in sales.  So energy, would you agree with that? Energy is where it is all about energy and interest. Energy in that, hey, are you energized?  I'm gonna give you a little secret. I've never talked about this. There's one thing I would always do before I would go into an appointment. This wasn't planned. Dylan has no clue what I'm gonna say, right? Live on video, I've never said this. I would have this Cody's $100,000 CD, right? That I made this playlist that I made, and I actually used a CD back then, because there's like a decade ago, right? Nobody uses CDs anymore, but I did, okay? On that CD, it was a hype list. It was a motivation list. It was music to get me going and hyped up and jacked up and bring my energy, maybe a five or six or seven to an eight, nine or a 10. I would play that on the way to an appointment every single time, right? If I left an appointment with a sale, I had a certain song I'd play. If I left the appointment without a sale, I had another song that I would play because I didn't make the sale. So your energy, like for instance, when I go speak, or I go to conferences, or I have breakout sessions, or I do all these free live training events all over the country, like the one we have here in a little bit tonight, right? In Little Rock. Every single time I go to the stairs or the stairwell or the bathroom or to my room or the fitness center or down the hall, and I start doing jumping jacks, right? I start doing jumping jacks. I start jumping up and down. I start getting excited. I start getting jacked up. I start getting my heart racing because my energy ends up depicting the outcome of that event, of that speech, of that training. Just like your energy, when you get a chance to sit down with a prospect, ends up determining if you get the sale. So that's the first piece is energy. That's A, the B piece, one B, interest, is are you interesting? How interesting are you when you get a chance to gain interest along the way through engagement and trial closes and stay interesting and keep their attention? How do you do it? Energy and interest will help you be a better salesperson. Number one, it will give you confidence. Number two, it will give the prospect confidence in you because you have energy and it looks like you should be passionate about what you do. But either way, and I'm not saying to fake it because you should never fake anything, but it looks like you have a lot of passion for what you do. And hopefully it's true, hopefully it's real, right? But when you put out energy and interest, you look passionate, okay? So that's number one. Top three sales, for those just joining us, top three sales tips, right? For being a better insurance salesperson. Tip number one, in energy and interest. Tip number two, okay? Address the five buying decisions. There's five buying decisions when you sit down with the prospect, right? How trustworthy are you? That's why I talk about how this is a relationship game. They are evaluating how trustworthy you are as a salesperson, okay? That's number one. Number two, is are you and the company and the carrier and the agency you represent? Are they reputable? That's big. People do the research nowadays, okay? Also, what problems does this insurance sell solve for them as a prospect? They need to understand the benefits, the value. We talked about relationship, value, and you make the sell, right? So those are several things. Also, is the price worth it? If they see more value, if the value's higher than the price, people make a decision. If the value is lower than the price, right? There's less value and the price is higher than it feels, right? There's less value, they don't buy. Lastly, is this the best time for them to take action? The timing is important when someone is, so that's why as a salesperson, it's good for you to stress that the time is now, like the no call back closed. So that's the second tip. Address the five buying decisions, right? Because yes, you can have energy and interest, right? Yes, you can address the five buying decisions, right? All five of those, because if you don't address their problems, their concerns, their complaints, right? Their fears, they will feel less confident making a decision right now, okay? So that's tip number two. Tip number two, to being a better insurance salesperson, okay? Tip number three is dipping into psychology. I learned the psychology of sales at 19 years old and I was better because of it. When I say psychology, I'm talking about the fact that when they give you an objection, they do not mean it. The psychology of sales that you should always finish with a question, right? The psychology of sales that you should ask questions and get them talking more than you do. When I talk less, I make sales. When I talk more than they do, I don't make sales, right? Get them opening up, get them talking, get them sharing, open into questions, right? They will tell you why. The psychology in that they have interest, they're sitting with you, they're looking for a reason to buy. Can you help them take advantage right now, right? Or the psychology that if you pause as you lack confidence, then they will take control of the sale and the conversation and you will fail on your objective to make that sale. So when we talk about top three tips for being a better insurance salesperson, the first one has to do with your energy and interest. How energized are you and how much interest do they have in what you're talking about, right? Your energy is everything. I need to start a new video series called Energy Is Everything because energy is emphatically everything, right? It really is. Also, the buying motives, the buying decisions, why are they about to buy from you right now, right? That's tip number two. And the third one is dipping into the psychology of sales. It gives you, if you have the interest, you have the why and them connected, right? And then you know the psychology behind sales to help people make a decision, getting a lot of yeses, right? Trial closes, engagement, getting them involved, getting them, going and sitting by them and being in their bubble. All these things can be huge helpful tips for making you a better insurance salesperson. I didn't want to go really long today. Today I wanted to go direct. Today I wanted to challenge you and today I want to give you three tips to make you better. I was a new agent not too long ago. I started as an intern calling on the phone book before I knew you and I were really supposed to be doing that. I feel like I get and understand new struggling insurance agents. Most people in our business are not the dude making seven figures rolling in it and traveling the world. Most of the people in our industry are struggling. Some even have part-time jobs. I want to be the guy that they can go to to really learn some knowledge and really help them. I was very fortunate. Around 117,361 dollars and 13 cents in my first eight months. And I thought if I can do that, looking for one company selling one product, it can probably help some other people too. What is up? Welcome to Phone Phenom. If you love this, I got a video you have to watch. It's how to sell life insurance. It's amazing and it's right there. See you there. They say life insurance is the hardest product to sell in the insurance industry. If you think so, I can make it real easy if you keep watching this video. So I'm gonna teach you how to sell life insurance. My name's Cody Askins.


So, this is joint work with Mitri Kavatovic from MSR and get down from University of Luxembourg. Let me start with cryptanalysis 101. What do we have when we teach or attend a course, intro course in cryptography or cryptanalysis? Well, you hear about differential cryptanalysis, you hear about linear cryptanalysis. Why is that? Well, it turned out that these attack vectors are very, very powerful for many applications since the early 90s and many different variants have been developed.  Well, the attack vector that I'm going to talk about today is not of this type. It's a mid and the middle attack. It can be described in a very simple way, at least I have it right here. When looking at a cipher, we have a plaintext as input, a ciphertext as an output. And in case we are able to separate a key space in such a way that we can start from the input, compute forward with some part of the key that is independent of another part to compute some value v in the forward direction and do the same in the backward direction just vice versa, then we can take advantage of our birthday effect and then potentially filter out key gases faster than in a brute force way. So this is nothing new, that's a very old idea, but it was overshadowed by linear attacks and differential attacks in the last 20 years. This is now slowly changing, maybe because of the attack on the lightweight cipher cut on them from 2010. So the outline for the next 19 minutes, first I will briefly discuss the setting. We are talking about block cipher analysis here. Then I will review mid and the middle attacks and show where these gaps were in our timeline. Then I will briefly review idea of the block cipher. We will be analyzing and then describe attacks on round reduced versions of a year and also on full round idea before I conclude and wrap up. So the setting is very simple, we are given a block cipher. The goal is to find a single unknown key. We don't need any related keys, nothing fancy, very simple. Also we don't, we only ask for the possibility to choose plain text and get ciphertext back or maybe the other way around. We don't need any adaptivity here. So in the brute force attack, if we want to find this unknown key with probability one, then we need to try to decay times if k is the number of bits in our key. And then ever we find an algorithm that can do this faster, then we speak of when attack graph is speaking. So mid and the middle attacks actually are as our academic cryptography. It started with the work of, basically with the criticism of a different helmet of the differential of the data encryption standard in 97, in 77. They described a simple mid and the middle attack on a version of this when used with two independent keys. A few years later, Merck and Helman came up with a variant of this to also attack two key tripletors in a mid and the middle way. Again a few years later in 85, Schaum Evertsever refers to look into the cipher DS and perform such a mid and the middle attack there as well. The thing is DS has 16 rounds. They only managed to cover six or seven rounds. So there was a long way to begin and especially afterwards when differential linear attacks were developed that managed to cover many more rounds. This is probably one of the reasons why this attack vector was overshadowed. Now in the hash function side there was also similar applications. Maybe first Laimassie found applications of mid and the middle attacks when it came to finding second pre-images in generic iterated constructions. Then for a long time nothing happened but in a series of paper from 2008 on AUKIS, ASAC and others looked into the compression functions of various hash functions and found attacks using this attack vector. Most importantly probably the pre-image attack on MD5. Even though it's by far not practical, it's not that much faster than brute force actually but still it is certainly an important step when it comes to cryptanalysis. I give the example of Tiger here as well that I did with Gu and others because Tiger, we don't have an efficient collision attack for it even though for MD5 we have one but still this attack vector led to first attacks on Tiger as well which is a hash function that was with the cryptanalysis for more than 10 years. So then as mentioned in the beginning already, we started to look into applying this newly found attack vector, rediscovered attack vector if you want to block that again and we found a victim. The led by Zeifer Katantan and the meanwhile attacks are already almost down to 2 to the 70 showing that this is something to be taken seriously but it was still a very simple attack. Recently we introduced this framework around MD5 attacks that allows more sophisticated techniques to be applied as well under the umbrella of Big League attacks. First applied in the hash function setting Chateau and Scane were our first targets, well reduced versions of it and more recently we looked at AES as well and our results last year received some attention because we also had results on the full AES and now as a follow-up we look at idea and have more results on this as well and this is somewhat the context of my talk. The Big League approach in a single slide, well it is a formalization of the idea of Orchis Asakides first found applications in MD5 where they managed to squeeze out more rounds in the middle attack than was thought to be possible before. The beauty of this approach is that we can suddenly use tools from differential cryptanalysis in our middle attacks. We can speak about differential characteristics trails, we can use little bits, rebound techniques, all the things that we developed in recent years when it came to hash cryptanalysis actually and so far it was mostly used to squeeze out more rounds in our attacks. So let me talk about idea, it's a very old block size for relatively speaking, designed by Lai Messi and published in 1991 as a 64-bit block size 128-bit keys. It's quite widely implemented and receives a lot of cryptanalytic attention only if at all second to the AES or the DES, more than 20 research papers since the early 90s improving results, having results on more and more rounds but still the best result so far from Azure Crypt 2009 by Sun and Lai is a result on the first five rounds. It's not that much faster than brute force, 231 25.5 and needs about a megabyte data. Idea has this property that if instead of first rounds, middle rounds are chosen then the cypher becomes weaker, that's why in this setting six rounds can be attacked as well. I will keep the talk at the level where we don't need details of the cypher but I wanted to show you this round transformation anyway just to give you a brief idea. So this is the input of our round 64 bits split up into 16 birds. The operations that are used in idea are XOR, model addition and multiplication model of 2 to the 16 plus 1. So these are incompatible group operations and the security is basically drawn from this mix of these incompatible operations. And this round is now iterated eight times and then one last time we have another key addition layer. So far five rounds were the best. In order to illustrate the power of the speaker concept that we apply for the first time through a year, I'm starting with a rather new result that was first announced at the crypto rum session last year by B, Hamshami and others where they also applied this middle attack vector for up to six middle rounds of idea. The illustration is very similar to what we had before. We find some way to separate the key into key spaces such that a small part of the key space is independent of some part of the cypher execution in both directions. Then we just start from a plain text cypher taxpayer computing both directions and look for a match. This then in turn we use to filter out key guesses. One variant of this approach gives a time complexity of 2 to the 123 so somewhat faster than brute force. It only needs two plain text cypher taxpayers. So this was basically state of the art last summer. What we can do now is to immediately add one and a half more rounds without essentially not touching the 10 complexity or with this big click approach. So we have our rounds one and a half until seven and a half year. That was the part of the cypher that was attacked so far. And it turns out that this big click contraction that we are using can cover the first one and a half rounds. So this gives us basically the same time complexity for the attack. The problem is the data complexity. So after we saw this six round result it took us only a few hours to come up with this very first huge step towards four and a half rounds. But then the hard work started because we were not happy with the fact that the attack suddenly needs huge data. So we were working on trying to reduce it. So why do we have this high data complexity actually?  So now in our middle attack we look for all possibilities of kf in one direction or possibilities of the bits in kb in the other direction. Then we look for a match and let's assume we find a match where this choice was matching with this choice. So what we are now basically facing is the challenge of somewhat connecting our internal states that we somewhat started with via the plaintext input to the cypher that we have to match. And this big click structure allows us to do exactly that. So the problem is finding such a structure where we map key plaintext inputs and internal states in such a way that gives us this property is highly non-trivial. Actually if this round behave anyway random this structure is highly unlikely to exist at all. But for a small number of rounds, one or two rounds, this is something that can be constructed. The thing is we need to construct this very efficiently because this is happening in our inner loop. But there are amortization effects that allow us to do exactly that. So that's why time complexity is essentially untouched. So why do we have this idea of complexity? Well the thing is for all those white parts here, those key bits that are not used in the mid-to-middle attack, we need to guess them. And for every guess we need to construct a new big click. In the concrete attack of this seven and a half round idea, it's about 100 bits. So we need to do 300 times. And this gives us more and more big clicks. But we cover basically, we cannot avoid covering the complete plaintext space for this. This means that's the reason why we need almost a full codebook for our attack. And that's now where the conceptual contribution comes from. So we extend the big click framework by something we call narrow big clicks where we address this problem. The new trick is here that we use the degrees of freedom that we have in this big click area. Such that we can construct internal states that fit together with the concrete kickers that we have at this very moment. Such that the certain plaintexts collide on a number of bits. And the more bits that collide, the lower the data complexity will be. And this is something that resembles collision attacks and hash functions a lot, actually. The hours that we don't have a key. And we need to somehow construct pairs that have certain properties. Why we don't have a key here is that we have to construct this for every key guess. So whenever we construct this big click, we know the key because that's just the one that we are currently guessing. So that's why we draw heavily from tools that we developed earlier in Haskell analysis. The thing is I won't go into the details here. This can be very complicated. The details are in the paper and in order to get more confident in the results that we obtain, we practically verify them. That's something that is pretty important. To give you an idea of the impact of this narrow extension of the big click framework, I list here a few attacks that we obtained. So an attack for the first five rounds. The five rounds were so far the highest number of rounds that were attackable. We have a time complexity of 201.5. That's much faster than everything that existed before. And with this narrow, a big click technique, we reduce the data complexity from something that is close to the full code book to 225. Then with a higher number of rounds, these are all versions of idea that haven't been attacked before. The time complexity increases and the data complexity increases as well. This seems intuitive. It's actually a bit of a coincidence because these are all different attacks with different keyspace separations and so on. That could also be non-monotone behavior of this kind of complexities. Here I give only those results that minimize time complexity. In the paper, we have more on that. Okay, so we have now seven and a half rounds. That's already pretty close to the full idea. Idea has eight and a half rounds, so one more round to go. We tried to find attacks that would cover the full idea in this way, but we didn't manage. But what we can do, that's something the big click attack vector allows us to do, is to introduce us more brute force phase into the attack. And indeed, again, designing a new attack with new sets of kf and kb and so on and new methods to construct big clicks. The new bottleneck of the attack then becomes at least the brute force phase that needs to cover one round contributes to the time complexity. The new time complexity is then 2 to the 126, still a bit faster than brute force, but now suddenly we can make a statement about full idea for the first time. Put this into the table again. I give now here two variants. Again, it becomes more difficult, but still we can lower the data complexity a bit to 2 to the 52, for example, and the time complexity is roughly four times faster than brute force in our model. So let me conclude. I think we show two main contributions in this paper. First is a variety of new results on idea that seemed like a sudden jump in cryptanalysis. It took us almost 20 years to start from one to up to five rounds, and suddenly we have attacks on seven and a half rounds, and even full idea if we consider this trick with the brute force phase as an attack as well. So after our realization that we can immediately gain one and a half rounds with this big click trick, Behem and others also updated their work, and they now compliment our results in a nice way. They consider not only initial rounds but also middle rounds. Sometimes they minimize data complexity, whereas we are minimizing time complexity, so I warmly recommend to study this paper as well if you are interested in the state of the art in idea. Secondly, not only do we have these orders detailed results, we also add a new tool to the toolbox for the cryptanalysis. This is something that will find applications to other sizes as well. Something else that I would like to point out is that so far the big click attacks we saw on a yes and on other constructions are all very close to brute force. Here in this paper for the first time what we have is actually a demonstration that this is not necessarily the case we have variants of our attacks that are many million times faster than brute force. And if you ask now what does it mean for full idea, is it broken? Well if you like to think that a yes is broken because of our results of last year, then I'm sorry to say that it's the same for idea, it's about the same security that we get 126 bits. Well for practical purposes it's a very secure surface. It's just, our research just showed that we still can make progress with new attack vectors. So last but not least let me talk a little bit about open problems in future work. Well the big click attack vector itself came already from hash cryptanalysis and was applied to self-cryptanalysis. Now the new tools that we used and developed for this particular result again draw a lot from the know-how that we obtained in hash cryptanalysis and reasonings. So there may well be more techniques around that will find applications to self-cryptanalysis as well. When it comes to finding new targets for middle middle attacks and big click attacks there may well be other surprises lurking not only in here. And last but not least it seems we are seeing an immersion of a new subdiscipline of cryptanalysis that one could call brute force like cryptanalysis. Let's say we want to implement a brute force attack on a cypher that has a key space that is not too large let's say 80 bits. So far statements about the cost of such an attack were purely in the realm of implementers basically. But now with this combination of brute force like cryptanalysis and big click attacks suddenly cryptanalysis can help there as well and can squeeze out speedups that were simply not possible before with simple implementation tricks. For cyphers with 128 bit keys or even more this remains more of an academic discussion but for key sizes of 80 bits or less this can have very practical impacts actually and can even save lots of energy in our data centers if you want to find keys in a brute force way. Cyphers like present come to mind or also the 64-bit version of Kazumi is a very interesting target in this respect. With that I'm done. Thanks a lot for your attention. Do we have questions? Okay so maybe I could ask do you see any chances of making it better than brute force? I mean integrating some techniques. I mean it seems that your conclusion is that big click attacks are basically smart brute force attacks. Well this is only part of my conclusion really. For reduced versions what we show is that big clicks attacks can be many times faster than brute force search even a million times faster. Key schedule you need to. Exactly. Yeah less key bits. Yeah but in some sense idea is also resistant against this kind of advance of attacks because we do need this brute force phase. We still squeeze out a factor four which is certainly not negligible but that's as far as we can go at the moment. But improvements may be possible. Okay let's thanks. Thank Christian again.


The 220-hour master package with or without tutor support is ideal for new teachers looking to get the best possible general foundation for teaching English as a foreign language. The course package consists of three individual certification courses. Part 1. 120-hour Teflor TESOL course with or without tutor and videos. Part 2. 50-hour course in Business English, CTV. Part 3. 50-hour course in Teaching English to Young Learners, C-T-E-Y-L. The 220-hour master package deals with teaching methodology, English grammar and the two specialized fields of teaching, Young Learners and Business English. This course will give you an edge for a successful career in teaching English as a foreign language worldwide. After completing the first part of the course, the 120-hour certification, you will be able to apply for teaching positions worldwide. Upon completion of all course components, you will be able to teach not only effective lessons but also the specialized fields of Young Learners and Business English. All three courses included in the 220-hour master package are internationally accredited and result in embossed hard copy certificates. The course package can be studied with or without the help of a professional tutor. All course graduates have lifetime job assistance and can access our extensive job database with postings updated continuously. Additionally, we will help you write an EFL resume and prepare you for your job interview. All of these post-course services are available for as long as you need them throughout your entire teaching career. Since 1997, ITTT has graduated more than 107,000 students, with thousands of teachers teaching abroad or in their home country, thanks to an ITTT, TEFL or TSOL qualification. Are you ready to begin your new life abroad? Please visit www.teflcourse.net to apply for your course. We look forward to helping you teach English as a foreign language in the destination of your choice.


Welcome everybody for the second talk on the evaluating OpenStack session. So we have a trio of people from Ericsson who will talk about evaluating OpenStack yourself versus waiting for the help from the foundation or from the third parties to do it. So you will evaluate it exactly on the features and technology which you wanted, not what somebody else does for you. Thanks a lot. Welcome everyone. Welcome to the last session of the first day at OpenStack Summit. We are here to talk about various cloud options and some quick steps to evaluate those options for enterprises which are ready to implement their cloud strategy into action. Let me start with introduction of the team here. We are from Ericsson, cloud solutions team, and would like to introduce the speakers here, myself Nikethu Parekh, I'm a cloud solution architect. With me I have Sudeep Bhattra and Rani Haddad. We are all part of the same cloud solution team at Ericsson. And in today's topic, the things we will be discussing are primarily looking at the situation that every single enterprise is going to face. Either they have already addressed this situation or they are ready to look into the next logical step of evaluating the cloud options. Then we look at various approaches. And as part of the approach, we will touch upon step-by-step process of evaluating various options. We have tried to broadly capture them as three different phases. First one is to know the options available. Second one is to talk about the evaluation framework itself. And then last step is basically decision-making and planning exercise. And we'll conclude with the summary. So with that, I would like to hand over to Rani to kick off the discussion. Rani? Okay. Thank you, Nikethu. So as Nikethu just mentioned, this is today's problem for large enterprises. So the enterprise is realizing that we're trying to make the shift, the digital transformation or the cloud transformation, and adopt some kind of cloud strategy. So we're starting with this funny Dilbert cartoon. Employees got the directive that they need to do something. They need to fix the large enterprise problem and adopt cloud somehow. And they're just discussing cloud computing. How to adopt it? How do we go about it? And they really have no idea what to do. In fact, I mean, today I was actually surprised, pleasantly surprised. There's a lot of first timers here at the summit. And this indicates that the adoption is still ongoing. So we have a lot of enterprises that are still trying to make the move to cloud. So how do we go about this? Or what is the current problem? So a given enterprise has several departments. And all these departments have different business drivers and different goals. Like a finance department or a marketing department, IT operations, different businesses, R&D, security, etc. Everyone wants to achieve some sort of agility, some sort of quick time to market. Proximity towards end users, faster, quicker services, quicker delivery, flexibility, faster deployment of production or lab test environments, etc. Adopting or conforming to regulatory requirements. So how do they go about this in which cloud to adopt? That's the big question. So what we've done is we've come up with an approach to try to do that as an exercise within the enterprise. So we have a five-step approach. The first step or the first two steps are really to know your options. So what are the options out there? What is the deployment model? We'll talk more about the deployment model in a little bit. What is the service model? Do we want to adopt for a deployment model? We want to adopt a private, public cloud, hybrid, community. Today we even heard about another one, private cloud as a service. So what are the options out there? We'll know some details about all these options and the different components. So even if you adopt a specific service model, then what components do you need to worry about? Then after we look at all the options available, we try to come up with an evaluation framework. So we look at the different apps, different businesses, their requirements from several dimensions, technical, architectural, business requirement, etc. Then once we look at these requirements, then we look at the cost. We have a cost analysis that needs to happen. And once we narrow down the options based on these requirements, as well as some sort of financial analysis, we try to make some decisions and come up with a migration strategy in order to make that move to the cloud. So we talked about knowing your options. What are the different options? What are the different cloud deployment models? Something most of you know, we have public clouds. In fact, we heard today there's over 50 public clouds running on OpenStack around the world. And you can go to the OpenStack marketplace and look at these. And there's obviously AWS, there's Google Cloud, Brackspace, other public clouds that we all know about. And on the other hand, there's the private clouds. And enterprises are trying to deploy their private clouds. Some of them are struggling. And we've heard some of them are starting with private clouds, running it for several years, then switching. And we've heard also the other case where people have gone to the public cloud and then decided, okay, well, I've got so many problems doing this. And let me switch to try to do this with a different model, either hosted, managed service, on premise, et cetera. And then there's obviously the hybrid cloud case where we want to start with public or private. And let's say we start with a private cloud and we want to be able to be a little bit more flexible and extend to private cloud. And we connect to one or more public clouds from our private clouds. So these are our cloud deployment models. Then the service models are also something you guys, maybe most of you are familiar with. But let's refresh your memory a little bit here. So we have infrastructure as a service, platform as a service, and software as a service. So infrastructure as a service obviously provides infrastructure as a service to the users. Platform as a service where I guess the users have to worry less about one part of the stack. And so we can provide the underlying OS in middleware and runtime and then have the users only worry about their applications and data. So deploying their applications and worrying about their data. And lastly, your software as a service where the whole stack is provided to the users and the users have to basically use their applications. So we talked about the deployment models, the different service models, and whichever one you adopt. There's a set of components that you kind of need to consider when you're trying to make the move to the cloud. So what are these essential components? It's a big dinosaur obviously. And the different parts of it are the infrastructure we just talked about. So IAS where you have your compute storage and networking. And then the next level, which is platform as a service, PAS, where we provide the platform for the developers to deploy their applications. And one thing we all need to do is option management, right? One way or the other, we have to manage either the infrastructure or the platform or sometimes the applications running around it. And of course the layer that sometimes we ignore but we cannot, which is security. So security is an important part of this where we have to consider security at all levels, whether it's physical, network, infrastructure, etc. So I'm going to hand over to my colleague, Sudip here, who's going to go in a little bit more detail about the different options when it comes to infrastructure and PAS and tools for option management. So I'll throw more light on the infrastructure components that are involved that we need to decide upon. So the first criteria, of course, is to decide the Linux distribution and the three major Linux distribution that we have is the Ubuntu, OpenSUSE and CentOS. And then there are various vendors who are providing this OpenStack distributions. So that also needs to be decided. Now, when we look at this infrastructure component from the IAS, we have like three broad categories which we know, network, compute and storage. So we need to decide on those factors. So when we look at network, then there is an aspect of network segmentation which is like deciding what type of network like private network or the tenant network, the provider network or the storage network. So those aspects need to be decided. And then is, of course, the SDN software defined networking, which needs to be decided depending on your workload, characteristics, service chaining requirement or SRIOV requirement for your workloads. So that needs to be decided. And then the underlay, which is really the switching fabric, the leaf spine architecture, as well as the connectivity to the gateway router. So those aspects need to be planned out. And then we have to look at the compute aspects like selection of the hypervisor. If there is already a hypervisor being used in the organization like VMware, maybe you would need to select that. Otherwise KVM is the default choice that mostly it has been used now. The next aspect in the compute is the selection of the hardware. And for the selection of the hardware, you have to really look at the various aspect of over commit ratio or the instant size for the hypervisor. And then the workload requirements are really depending on your application requirement. If there is specific application requirement, that needs to be taken care of. So that also needs to be considered. And then we look at the storage, planning out for the FMRL storage, which is for the VM onboarding. The VM needs to be done. So that needs to be planned out and the block storage and the object storage for the files and stores. Okay. So this is, again, in case the decision is toward the public cloud, then also you have to select on the various components on the network compute storage. And again, there are various factors that need to be considered. Now, the other big area is really the operations and management components. And here again, the two broad categories, the deployment, orchestration, configuration, management, this aspect, and the logging, monitoring, and alerting. So deployment is the selection of the tool. And we have various tools like fuel, triple O, which will help in doing the production deployment. Of course, for the learning, we had been using back stack or desk stack deployment tools. But that selection needs to be considered when the deployment for production workload has to be planned out, production open stack deployment. And then there is a selection of the orchestration platform. And there are various orchestration platform. Ericsson has an orchestration platform like Ericsson Cloud Manager, which can be used for deploying the various virtual applications. With respect to whichever underlying open stack platform you have, it can be used to deploy your virtual applications. And also there is another own app that is open network automation platform based on OpenEcom, which can be used and it's really to address the telecom network orchestration. And the underlying, these tools will of course talk to the HEAT API to be able to orchestrate the VM onboardings. And we have the configuration management for our platform, which can be done using various tools like puppet, foreman, or also other tools like Ansible or Chef can be used for doing that. Then the important aspect is the logging, monitoring. Monitoring, we are considering operational monitoring, but there is also tenant monitoring, which needs to be planned out. And then for this, the initial step will be to identify the metrics that you want to monitor for your environment. And the services, the open stack services or the underlying operating system services that you want to monitor. So those aspects need to be decided. And thereafter, there is a need to plan out the various tools like logging, monitoring, alerting. Typically there's a tool like StackLite by Mirantis, which can be planned out. And if you already have an existing tool like Nagios, then there is a need to decide on the integration between that Nagios tool. And of course we have the open stack telemetry, which can be used for doing. The next big aspect is the security. Now security is really a very big factor and it really needs to have a consulting to decide on how we can do security for the entire organization and apply to the open stack distribution. Now here what we are looking at is really what are the security concerns that is there for an organization. So broadly there are six categories, cloud infrastructure, cloud security controls, multi-tenancy, cloud management, hypervisor and data protection. So the security concerns can come from the various areas. And in order to ensure that all these security concerns are addressed, we have to really apply a proper mechanism.  So each of these needs to be applied and there are various aspects like when you talk about compliance and gap assessment. So there is a need to apply some security standards, certification. And then when it's the risk assessment, you have to really look at the multi-tenance, those aspects. And security assessment and auditing for the hypervisor and applying various security mechanisms like, you know, SELinux or we are more those kind of security aspects. So each of these need to be looked at in detail when planning out the security. When we come to pass, really these are the driving factors and the deciding factors which lead to the selection of a pass. And the components are these are the components which really need to be looked at when deciding the pass components. So with that I will hand over to my colleague Nikithu to talk about the next stage of evaluation framework. We have looked at all the options available for evaluation purpose. Next logical step is basically to look into the evaluation framework. And looking at the evaluation framework that we can see in the slide, the approach that we have adopted is basically to come up with a very simple framework that is modular enough that it can be easily applied to any situation. And along with that it needs to be generic enough so that it can be applied to any kind of deployment model whether it is public versus private cloud or a hybrid cloud option being evaluated as well as any type of service model or consumption model. We wanted to make sure that the framework remains consistent across all the applicable scenarios. So along with that in terms of applicability and overall framework components what we have is basically starting with the step by step process and the first step is basically looking at the application requirement analysis where major input is based on various applications requirements. So as an output of that first step is basically looking at various feasibility options meaning that when you perform the requirement analysis the outcome of that analysis is that you have shortlisted options in terms of what cloud options need to be further evaluated down the road. And along with that you come up with a list of features which are mandatory in terms of fulfilling your cloud strategy. And the next logical step is basically to dimension the whole cloud solution that includes infrastructure dimensioning as well as various features which requires a specific dimensioning based on the situation. So as output of the cloud dimensioning is basically your overall cloud size and I guess everybody will be familiar with what the cloud size is. If you refer to the latest OpenStack Survey report you can see that there is a whole dedicated section about the cloud size which consists of various line items that need to be evaluated individually. So we'll look into that later on when we discuss the framework. And then once we have the cloud size identified the next step is basically to look into the total cost of ownership or return of investment analysis. So there are two different inputs. One of them is the cloud size and the second input to this particular step is all the cost factors. So as you can imagine for any kind of cost analysis there are various different aspects that influence the overall cost analysis. So we'll look into that further down the road. So this is basically the overall structure of the framework. Now let's look at individual components. So let's start with the requirements analysis phase. And the requirement analysis phase is basically a multi-dimensional analysis. And the typical structure you can see here is that for any given enterprise environment they must be following some kind of requirement analysis process or a model. And if we have to basically categorize various requirements independent of what application it is or what organization it belongs to you can categorize those requirements into these six broad categories. Functional, non-functional, architectural, O&M-related requirements, security-related requirements, and performance and workload-profiled requirements. And when we are doing the analysis we are not talking about reinventing the wheel here. We are trying to follow the same methodologies that are being followed for requirement analysis phase at enterprises. But what we are looking at is various business drivers. So the requirements are being evaluated against various business drivers. Some requirements may be positively or negatively impacting one business driver whereas it is completely independent or not applicable for other business drivers. So the heat map that we have shown here represents the same thing. In reality the framework itself has a positive or negative or not applicable as a scoring mechanism against these requirements that can help evaluate the requirements against business drivers for adopting the cloud strategy. And again, another dimension to that we can apply this. We can evaluate those requirements against various deployment models as well as various service models. So let's look at an example. Here we are looking at a few sample examples that enterprise has readily available meaning that these applications are cloud ready. Means architecture wise in all aspects, they are completely suitable for migration to cloud. So then when we do the requirement analysis of these applications, cloud ready applications, we can come up with a consolidated super set of requirements that basically needs to be fulfilled in order to migrate those applications successfully to the cloud. So when we have this super set readily available, what we can look at is which application requirements are not being fulfilled by a specific cloud option. And that helps us to apply the process of elimination and reduce our options which needs further evaluation. So looking at the second phase of the framework, which is cloud dimensioning. And here as I mentioned earlier, the main categories of the cloud dimensioning that we are considering here are looking at what is the size of your cloud in terms of number of computes. You need to know that primarily it's going to be a homogeneous infrastructure that you are going to deploy, you need to know the processors and number of course, et cetera, needed for the compute nodes. You need to know the infrastructure needs for the whole networking aspect. And you also need to know what type of instances that you are going to need as well as how many of those instances. You need to know the whole size of the network that needs to be deployed as underlay as well as overlay to handle the application related networking needs. And along with that, the storage aspect also needs a more detailed evaluation from dimensioning perspective. So what we have done here in this particular case, we are just trying to demonstrate that out of all these different items that are applicable for cloud dimensioning, some of them apply to public cloud and some of them apply to private cloud. So we need to very clearly identify which of this dimensioning aspect is applicable for what deployment model. Moving on to the next, as an example, what we have tried to demonstrate here is that out of those requirement analysis phase where we looked at the whole bunch of requirements, specifically talking about the performance characteristics of individual application. That application performance characteristics are primarily related to either the capacity needs of the application or performance-specific needs of that application. And on top of that, there could be virtualization-related requirements that needs to be appropriately analyzed and applied to the cloud dimensioning model. And again here, the model that we are looking at is kind of generic enough so that it can be applied to every single application that is being evaluated and dimensioned for cloud migration. And the resource requirement summarization tool that we are looking at is basically trying to summarize the overall requirement of all the applications which are ready for being migrated over to cloud. And at the end, what you have is basically a bill of material that consists of what type of hosts are needed, how many of them are needed, what kind of flavors we need, how many of those flavors are needed, what storage requirements are, as well as networking requirements, et cetera. Moving on to the next phase, which is primarily the cost of ownership and return on investment analysis. Again, as mentioned earlier, there are many different aspects and factors that influence the cost of ownership. We have given a sample of those factors, such as hardware infrastructure. Primarily that applies only to the private cloud deployment scenario because when it comes to public cloud, you are not deploying any cloud on your own. You have everything readily available from any public cloud service provider. In terms of software licensing as well, more than likely it is applicable for the private cloud deployment unless there is a specific scenario where the application virtual machines also need to carry along the license over to the public cloud deployment. Along with that, other considerations are LCM and operations aspects, both from the infrastructure perspective as well as for applications perspective that needs proper cost analysis. And one big factor is the data center cost. And here we are talking about every single data center that basically is part of the cloud strategy and applications are being migrated over to various data centers and costs such as renting the data center premise as well as all the operational aspects of powering it and HVAC and many other aspects. So again, the whole data center cost aspect is applicable only for the private cloud scenario whereas for public, we don't need to worry about that. And another big piece is the pay-per-use case where in the case of private cloud deployment, it is primarily not applicable. Whereas in case of public cloud, the whole fundamental pricing of a public cloud is based on a pay-per-use model which means that has very heavy influence on your overall cost analysis for your assessment. And last but not least, it's a training and competence building which is applicable for both public and private cloud. So let's take a quick look at how we are trying to address the total cost of ownership and return investment analysis. So here what we have shown here in this graph is basically we have picked only the material cost of the virtual machines in case of public cloud or the equivalent of number of computes that we need to deploy to match the same amount of virtualized resource requirements. So what you can see here is that we are looking at a specific configuration set of the virtualized resource requirement which is basically total 160 virtual machines on different public cloud options and then comparing the same towards private cloud where we are looking at how many number of servers are needed to provide the same number of virtual machines. So based on this specific line item as one of the factors of overall cost analysis what we have tried to show in this graph is that the cost of ownership basically between private cloud which is the blue line versus all the other public cloud options. And as you apply other cost factors into the equation you will see that the graph or the difference between the private cloud and public cloud changes. So that's the whole total cost of ownership analysis that the tool is able to accommodate. Moving forward beyond the framework then once we have the outcome of the evaluation framework which could be one or maybe maximum of two cloud options we need to go through the rest of the process of the planning various activities beyond selection. So beyond selection what we are looking at is we need to make sure that we are going through the whole formal proof of concept activity so that the team who are actually going to work on the deployment or cloud adoption they are well familiar with the cloud architecture and the cloud solution being adopted. Along with that another critical planning activity is to carry out the whole performance testing activity and last but not least is basically establishing overall cloud adoption timeline. So let's look at the proof of concept. So the main purpose we need to conduct the proof of concept is to help understand the architecture of the cloud solution being adopted and understand the nitty-gritty details of how pricing is going to work if it's a private cloud or if it's a public cloud or various other considerations. Also along with architecture, operational aspects and hands-on experience is vital for team to build the competence needed as well as feasibility of various automation aspects. So these are very typical items that we carry out during the proof of concept activity so that we are kind of taking the first necessary step to come up with high-level design for the solution and also identify various deployment tools that we are going to need as well as some high-level deployment guideline that can help us with more robust solution for deployment. So that was about the proof of concept. Let's look at performance characteristics. Again, performance characteristics testing is vital and crucial. It's not an optional activity because of the fact that performance of application is basically going to dictate whether your cloud strategy will be successful or not because we have witnessed so many cases where the deployment was successful but it was not able to fulfill the performance needs of various applications. So then it's a complete different exercise of tuning your application performances and whole nine yards related to that aspect. So before we take the final step of migrating applications, performance testing is a must step. Moving on to the next last item in this section which is about the cloud adoption timeline. And here, again, various factors influence the timeline. Just like we saw previously, the cost analysis also had various factors that can positively or negatively influence the total cost of ownership. Some of those factors also influence the overall timeline of your project timeline of your cloud adoption strategy. I won't go through the whole list here, but one important factor that is mentioned here is about the migration. And Edison has a tool that helps plan out the entire migration and I'd like to invite Ronnie to talk about the migration tool. We're running almost out of time here. So we'll go just real quickly through this. Basically, we've gone over the options and we presented the framework in order to evaluate which options to go with. And essentially, once you figure that out, you narrow it down one or two options, you need to kind of walk the walk. And there are several tools to do that. So one of them is this Ericsson Transmigration Engine, which is a tool that would help you collect all of your enterprise applications and put together a schedule and a timeline in order to basically walk the walk, like we said. And this is just various screenshots from the tool where you list your apps, list different characteristics of each app and kind of put together a timeline in order to execute this migration to your favorite cloud option. So really, in summary here, what we need to know is we look at the business requirement first and it's needed to make the shift to the cloud. So we got to know our options, evaluate our options, look at our TCO, and at the end we need to do some sort of proof of concept and benchmarking and then basically do the migration, go through the migration process. So thank you very much and we'll take any questions.


Welcome to Lecture 4, the sports biomechanics lecture series, supported by the International Society of Biomechanics in Sports and sponsored by Vicon. I've personally been looking forward to today's lecture for quite a while, so hopefully you all enjoy it. We have Dr Johans Funken from the German Sports University Cologne and Johans is the current ISBS student representative and he's going to be presenting on a really interesting topic about which he recently completed his PhD studies. So I'll allow Johans to introduce the topic, but I hope you enjoy. Okay, hello everybody and thank you Stuart for the kind introduction and for your great work on putting this lecture series together. I would also like to thank ISBS for giving me the opportunity to give this invited lecture. I will talk about recent insight in the biomechanical characteristics of the long jump with the below the knee prosthesis. And as we cannot see each other live or talk to each other after my presentation, I would like to say some brief words about myself to give you an impression of who I am. My name is Johans Funken and I received my doctorate degree from the German Sports University Cologne in 2019. Currently, I work as a postdoctoral researcher at the Institute of Biomechanics and Autopedics of the German Sports University Cologne. And since my first year as a bachelor student, I've been fascinated by the interaction between the human musculoskeletal system and any technological devices. And therefore, I'm very happy to talk about the long jump with the prosthesis. And it is a great pleasure for me to present some of my main findings from my doctorate project for you. When we think about the long jump, many of us might have Mike Paul in mind. In 1991, he set an incredible world record for non-amputees of 895 meters. But there's also this guy, Markus Rehm. During an accident, he lost his lower right leg resulting in a trans-tibial amputation. With a personal best of 848, he's the current world record holder of the long jump of athletes with a below the knee amputation, which we now call BKA. Just to get you an impression of how far this is, it's about half a meter longer than your side of a beach volleyball court. Let's have a quick look into the development of the long jump distances needed to become the Olympic champion during the last nine Olympic games. And as you can see, Mike Paul never actually won a gold medal at the Olympics. And distances to win a gold medal were usually around 850 to 870 and dropped a little during the last three Olympic games. For many years, the distances jumped to become the Paralympic champion or Paralympic champion with a leg amputation were way shorter compared to distances achieved by Olympic champions. But then along came Markus Rehm winning the Paralympics with 735 meters in London and with 821 in Rio. This world record of 848 from August 2018 would have been sufficient to win the last three Olympic games and become at least third in all Olympic games ever. After this great achievement, questions arose of whether Markus should be allowed to compete with non-amputee athletes and being ranked in the same ranking system or not. In an attempt to answer this question from a biomechanical perspective, we first had to ask ourselves, what do we actually know about the long jump and without prosthesis? For non-amputee athletes, there's a great basis of knowledge. To jump far, the athletes need to run up fast and then have an effective take-off step for redirecting horizontal run-up velocity into horizontal and vertical take-off velocity. Both seem to be equally important as a good long jump performance for non-amputee athletes is not possible without one or the other. A good take-off technique involves lowering the center of mass during the last strides and then the athlete really tries to use the take-off leg as a rigid lever to rotate over the foot. In the literature, this is called pivoting. The overall goal should be to generate a vertical take-off velocity without losing too much of the horizontal run-up speed. And what about the long jump with prosthesis? There's some comprehensive work from Nolan and colleagues and one very recent paper from Padules about run-up and take-off step kinematics. The problem was we did not have any very recent data at all. The research meant from a time when athletes jumped about one or two meters shorter than they do now. And also, in the meantime, athletes switched from taking off from the biological leg to taking off from the prosthesis now. And actually, today, almost all top-level amputee long jumpers use their prosthesis for the take-off step. And also, we do not have any kinetic data, no ground reaction forces, no joint energy, no joint loadings. But it should also be mentioned that already back then, Nolan and colleagues already compared the jumping technique of athletes who use below the knee prosthesis for the take-off step with using a springboard. However, as jump distances improved a lot since then, we didn't know if this is still true and what are the underlying biomechanics of the long jump with the prosthesis to achieve distances over seven or even eight meters. Therefore, the purpose of our multinational research project was the biomechanical comparison of the long jump of athletes with and without a below the knee amputation. And in my thesis, I worked on three primary research questions. But due to the limited time I have during today's presentation, I will focus on the first two only. And that would be, does the use of the prosthesis by athletes with BKA need to an advantage or disadvantage during the long jump compared to non-amputee athletes? And the second, are the long jump with and without the prosthesis based on the same biomechanical physical mechanisms? Excuse me. In total, we analyzed 10 athletes, three out of the four best long jumpers were the below the knee amputation who competed in the 2016 Paralympics, including the Paralympic champion. We also analyzed seven non-amputee long jumpers on different performance levels, including the 2006 Olympic champion. And as you can see, the two groups match pretty well in terms of performance and anthropometrics. Data capturing was conducted in Cologne and in Tokyo for capturing the kinematics. We used a 3D motion capturing system, a biomechanical system. And for the kinetics, we use a force plate implemented below the takeoff board. We measured running velocity with a laser gun and ensured valid force plate strikes with high speed video footage. Marker coordinates together with individual anthropometrics were then used for creating a full body model of each long jumper. And for the athlete with BKA, the lower part of the shank was substituted with the model of the prosthesis and the prosthetic anchor joint was defined at the point of the greatest coverage of the blade. From our model, we extracted and calculated the following measures. First, we calculated the theoretical jump distance. We did that because we wanted to avoid the influence of landing technique on performance. And theoretical jump distance is defined as the distance from where the foot leaves the ground to the intersection of the COM flight path with ground level. Beside others, we calculated the following kinematics and kinetic parameters. We calculated run up and take off velocity, COM kinematics, joint kinematics, COM kinetics, joint kinetics and energy distribution, ground reaction force orientation, ground reaction force, near arms and vertical stiffness. And just to give you an impression of how our model looked in action, here's a short video of two athletes doing the last few steps before taking off. In red, the athlete with BKA and the leg, the non-MQT athletes or athlete. Okay, coming to the results. The theoretical jump distance was not different between groups and all athletes with BKA used the affected leg as their take off leg. On this slide, you can see the individual horizontal velocity indicated on the y-axis for each athlete at touchdown and at toe off for the take off step. Left for the non-MQT athletes and on the right for athletes with BKA. Non-MQT athletes run up faster and had a higher horizontal velocity when touching the board for the take off step. During the take off step, non-MQT athletes lost about 1.1 meters per second of horizontal velocity. An athlete with BKA on the other side had lower horizontal velocity when touching the board for the take off, but then only lost about 0.6 meters per second. Well, at the instant of take off in the actual jump, horizontal velocity was not significantly different between both groups or athletes. For the vertical velocity, there was no significant difference between the two groups, neither at touchdown or at take off. So, where do those differences in deceleration come from? Since we know that acceleration or in this case deceleration is directly linked to the force acting on the body, we looked into the ground reaction forces. Non-MQT athletes had a pronounced impact peak in vertical direction and in horizontal braking direction. An athlete with BKA had a more or less synodial vertical force curve and lower braking forces compared to non-MQT athletes. However, vertical impulses between both groups were similar, but horizontal braking impulse was greater for non-MQT athletes. And as I said at the beginning, the overall goal of the take off step should be to generate a high vertical take off velocity without losing too much of the horizontal round up velocity. So if we now plot the ratio of the vertical to the net horizontal impulses, it reveals that athletes with BKA had a higher ratio indicating a more effective take off step. To understand this effectiveness, we now looked even a bit deeper into the take off step and analyzed the COM energy during the take off step. What you see here are individual curves for the COM work during the take off step, zero leveled for the instant of touchdown. COM energy is a combination of kinetic and potential energy and during the take off step athletes lose kinetic energy because of the braking impulse. And as we can see, non-MQT athletes lost some of their COM energy during the first two thirds of the stand space and then regained some of this energy during the last third of the take off step. However, they only regained 56% of the energy they lost. In effort with BKA, that was different. They also lost some of their COM energy during the first half of the take off step. But then during the second half of the stand space, they were able to increase total COM energy on an even higher level and was at touchdown. So how are they able to do that? Athletes with BKA store most of the COM energy in the prosthesis. Because the prosthesis is a passive elastic component, some of the energy gets lost here, but then the athletes with BKA are able to add some energy to the system by use of the active system, in this case the hip muscles. That's something we could not see in non-MQT athletes. Or with other words, athletes with BKA are able to store a lot of kinetic roundup energy in the blade in form of strain energy, regain most of this energy and then add some energy with muscular work around the hip. So as a quick sum up, athletes with BKA have a disadvantage during the run up due to a lower run up velocity but have more efficient take off step, which is an advantage. Quantifying either the advantage or the disadvantage in meters, which is the unit the overall long jump performance is measured in was hard and especially for the run up not possible based on current scientific knowledge. So at the end, when it comes to the question overall advantage or overall disadvantage, we had to admit that we cannot give a clear answer here because we could not weigh the advantage against the disadvantage in the same units. But still, there were some open questions. Specifically, how can athletes with BKA store that much energy in the prosthesis and at the same time put the hip muscles in action. We now had a look in the ground reaction force alignment relative to the leg joints and the COM. The previously mentioned differences regarding ground reaction force amplitude also became obvious when compare when compare ground reaction force alignment of the two groups during the take off step. Athletes with BKA had the ground reaction force vector more or less passing through the knee and hip joint and close to the COM. Non-ampliated athletes on the other hand had the ground reaction force vector with some distance to the joint centers and to the COM, especially during the impact phase of the take off step. This was true for the sagittic plane but also for the frontal plane. And please notice that athletes with BKA are indicated in red jersey and non-ampliated athletes with a black jersey. That's also the color coding for our next figures. This qualitative analysis was supported when we calculated mean distances between joint centers and the resultant ground reaction force vector. Compared to non-ampliated athletes, athletes with BKA had longer lever arms between the ground reaction force vector and the prosthetic anchor joint. But short lever arms between ground reaction force vector and hip and knee joints. Or with other words, athletes with BKA increase the load on the prosthesis but decrease the load on the biologic reticules at the more proximal non-affected joints. Furthermore, as stated by Bivana, a closer alignment of the limb and the ground reaction force vector increases the muscle's effective mechanical advantage at the joint. This kind of selective loading and unloading indicates that the energy changes necessary for the take off step in athletes with BKA can be provided more effectively with the prosthesis compared to the muscles surrounding their residual limb joints. Also, it should be noted that the energy stored in the prosthesis exceeds the energy storing capacities of the human muscle tendon complex. This kind of movement execution also has some consequences for the vertical CRM movement during the take off step. When storing energy in the prosthesis, athletes with BKA really sink into their prosthesis and have a pronounced and more extended downward movement compared to non-ampliated athletes. Non-ampliated athletes hardly have any CRM downward movement but really pivot over their leg lever. This is also reflected in a higher vertical stiffness during the take off step in non-ampliated athletes compared to athletes with BKA. The higher vertical stiffness is even more remarkable when noticing that knee joint flexion is much smaller in athletes with BKA. So even though athletes with BKA try to keep their residual legs stiff, their CRM vertical downward displacement is much greater than in non-ampliated athletes. And athletes with BKA cannot actively stiffen their lower leg but have to deal with the stiffness of the prosthesis. Or with other words, by relying on energy storage and return capacities of the prosthesis, athletes with BKA are also confronted with some mechanical constraints of the prosthesis which they have to deal with. So in total we identified two very different take off step mechanisms. One is based on redirection of the movement by rotating about relatively rigid leg lever. And the other one is based on energy storage and return and indeed reminds of the use of a springboard. And additionally, there are two important facts we were able to distill. First, non-ampliated long jumpers cannot adopt the technique elicited by athletes with BKA due to their limited capacity of storing and returning energy in the biological structures. And second, long jumpers with BKA cannot adopt the take off technique used by non-ampliated athletes due to mechanical constraints of the prosthesis. And to my mind, the combination of those two facts underlines how fundamentally different both movement mechanisms are and provides important knowledge for future rules and regulations. Now, let me take you on a short excursion and highlight some parallels of the movement mechanisms used by athletes with BKA similar to mechanisms in sports and biology. First, just remember how athletes with BKA store most of the kinetic run-up energy in the prosthesis and then get most of it back and additionally add energy by muscular work. Something similar was observed by our impulses and colleagues during the poleboard. The athlete stores kinetic run-up energy in the pole. The pole releases this energy and then the athlete adds some energy to the system by using his or her active system, in this case probably arm and core muscles. And for the second example, we remember the ground reaction force curves of athletes with BKA during the take-off step. When looking into the literature, we found remarkably similar ground reaction force curves in hopping of yellow rock wallabies. From wallabies, we know that their movement is based on energy storage and return from elastic structures. And of course, we don't want to say that athletes with BKA move like wallabies or like kangaroos. But to our mind, this and the poleboard example underline our finding that the take-off mechanism of athletes with BKA is based on energy storage and return. So when we come back to our two main research questions, we had to admit that we could not quantify an overall advantage or overall disadvantage based on the data we had and the current scientific knowledge. For the second question, we were able to identify two fundamentally different movement mechanisms. One based on pivoting and the other based on energy storage and return and indeed reminds of the use of a springboard. The knowledge we gained has direct implications for prosthetic design and also training protocols, training equipment and performance diagnostics might be adapted to the individual movement execution and specific demands of athletes with the below the knee prosthesis. And at the end, and as I said before, the knowledge about two fundamentally different movement mechanisms might have implications for future rules and regulations and might help decision makers. From a biomechanical perspective, we were able to gain available data set and build a sound fundament for an objective and more data-driven discussion on whether or not athletes with BKA should compete in the same ranking with non-amplities. Before I close, please let me add two comments. First, I am not saying one or the other movement mechanism is more or less demanding, they are just based on very different biomechanical physical mechanisms. And the second, this goes out to those who say, Markus is just using a spring and it's all about the spring. If this was true, Markus would not jump about 80 centimeters longer than the second best long jumper with the prosthesis. If it was all about the spring, all athletes with BKA would be able to jump that far. To my mind, the long jump with the prosthesis, just like all other sports and disciplines, is all about passion, talent and really hard work. Thank you for your attention. I would like to thank a few people for the help during my doctoral project and many fruitful discussions during the manuscript writing phase. That would be Dr. Joachim Obara, Professor Alina Kurabowski, Dr. Steffen Wilwacher, Dr. Kai Heinrich, Mr. Ralph Böhler. And of course a special thank you to my doctoral supervisor, Professor Wolfgang Potast. I would also like to thank all student helpers and colleagues from the Institute of Biomechanics and Orthopedics at the German Sports University Cologne. I would like to thank the Japan Institute of Sports Sciences for their help during data collection. I would like to thank the German Sports University Cologne for providing me with the Graduate Fellowship Grant and a special thanks goes to Japan Broadcasting Corporation and HK for financially supporting this study. Thank you very much, Johan. And I really hope that everyone else got as much out of that as I did. It's really fascinating. If anybody's got any follow-up questions to that for Johan's, then please either use the comments section on YouTube or if you take to Twitter and use the hashtag at the bottom of the screen. We'll keep an eye on both of those and try and make sure we can get a response for you. And then finally, please don't forget, on Friday we've got another really interesting talk, this time from Wouter Hoogkammer, talking about running footwear and the two-hour marathon. So again, hopefully another really interesting topic. Thank you very much and see you soon.


Hey everybody, this is Brian. Welcome to the eleventh Flutter tutorial. I'm hoping we can wrap up classes today. I'm not going to really cover enumerated types because it's kind of a little different, but what we're going to cover today is Mixins. Let me back up. When I say enumerated type is kind of different, it's It's more or less used as a variable. We will cover these in future tutorials, but right now we're going to really cover Mixins. So what is a Mixin and why do we need it? So it says Mixins are a way of reusing a classes code in multiple class hierarchies. To use a Mixin, use the with keyword followed by one or more Mixin names, and then some examples. And I kind of wanted a better description. So a better description is an object-oriented programming language, which is a Mixin is a class that contains methods for use by other classes without having to be the parent of those other classes. So you kind of take inheritance as a fundamental hierarchy, and you break that. And it's not really interfaces with abstraction. It's kind of like just saying, hey, I don't really want to use the whole class. I just want this little part of it, meaning I don't want to really inherit it, and I don't want to have to be tied to it. It's kind of weird. So let's just make our new project here, and this will calculate the sun, moon, and stars. There we go. Go out here. Did my music stop? I think my music stopped. Yep, I'm still listening, Pandora. Thank you for doing that, Pandora. All right, so back to what we're working on here. We are going to make a car. We're going to make a concrete class, and we're going to say IntDoors. Make a getter for this. We're going to make a black car, because why not? Black's awesome. And we want to play music in our car, and we're just going to say, boom, I don't know, just music, whatever. So we've got four doors. It's a black car, and we're just going to play some music. All right, so pretty simple class. Not a whole lot to it. Now we're going to make a truck. I'm going to make this concrete as well, and we're going to say, bull has four by four, because you need that with a truck, especially here in Michigan. Give this two door. We're going to stay a string color. Hmm, I want a... What color truck do I want? Let's make it a red truck. Giant big red monster truck. And we're going to say, void. I'll honk the horn. Why not? So we've got a car class, and we've got a truck class. Now, let's say we want to make a hybrid of those. We want a Jeep. Actually, let's call it an SUV. I own a Jeep for years and years. I loved it. So in this, we're going to import the car class, and we're going to import the truck class. I'm going to make another concrete class called SUV. And we're going to extend the truck. But this time we're going to say, with the car. What the heck? What's that mean? All right, so let's see what we got going on here. Color is inherited as a getter and also as a method. Ooh, I screwed something up here. See, there's color. Oh, yeah, that's why. There we go. Fix that problem. All right, so our SUV here extends truck with car. Hmm. What does that mean? Well, that's interesting. Let's find out. In here, we're going to import the SUV. We're going to say SUV Jeep equal new SUV. And let's just examine this object and see what's we got going on here. You can see how we have colors, doors, four by four. It has a bed and a horn plays the music. It does all the things that we want it to do. So we can actually say, you know, honk the horn. Jeep. Play the music. And let's say we want to print the number of doors and we want to print the color. Let's see what happens here. So we honk the horn. We play the music. We have four doors and it's black. Hmm. Where did it get foreign black from? That's interesting. Well, if we look at this, you can see we're extending the truck with the car. So if we look at the car, the car has four doors and it's black. So that's where it's getting that from. If we flip those around, you guessed it. We're extending a car with the truck. It will now have different properties. You'll now have two doors in red. So that's really how a mixon works. You can kind of piecemeal classes together and use the parts that you want without really having to mess around too much with interfaces and inheritance and abstraction. It's kind of a I'm not a big fan of it, to be brutally honest with you, because as you can see, if you do things in a specific way, you can change the outcome of what you expect.  So, you know, you really get some unexpected results sometime now. Some would argue, well, you know what results to expect because of, you know, the way you're ordering things and all that. Let's just for giggles here. I'm actually just going to try this, let's say. I have no idea what to call this industrial. We're going to make an industrial vehicle and we literally are just going to copy this car class here. And we're going to say this is what have we used blue. And we're going to give this like 900 doors. And of course, there's no way to play music in this thing. Let's go back to our SUV. It's funny, I always get this viewer feedback where everybody's like, we actually like watching you make mistakes. We learn from your mistakes. I'm like, you guys are so mean to me. So now we're extending the truck with the car and the industrial equipment. Let's see what this does here. We'll run this. Suddenly it's got 900 doors and it's blue. So the problem here is that it's picking up the last one. Now I'm not sure if that's actually a standard or if that depends on what sort of just-in-time compilation you go through. So if you get a different vendor's just-in-time compiler, it may take the first one and not the last one. So now you've got to actually account for those and make, you know, functions that do that. You should actually say string, color, equal. I have no idea what to make my Jeep here. Lime green. It's like the ugliest color on the planet. And then you should actually say int doors, equal. And we want three doors just because why not? We'll say it's an old Jeep and one door is messed up. Now suddenly we have the way we want it. But you can get some just kind of crazy unpredictable results with Mixins. It's not bad to use them. I don't want to deter you from it. It is an option. A lot of older programmers will stay away from them simply because they like the structure that inheritance gives or, you know, they want to know what an interface is. Or I'm sorry, they want to know that they have everything that's in the interface that you're providing because an interface is a contract. Whereas a Mixins, it's just kind of, you know, wild west, you just do what you want. So I hope you found this educational and somewhat entertaining. We're going to continue on with Dart. I'm trying to plow through these fairly quickly because I really want to get into Flutter. I really think that Flutter is going to take off in the next year or two.  So if you found this even remotely helpful, go ahead and visit my website and go to tutorials and you can download the source code for this and other tutorials. Click on contact and go out to the Void Rooms Facebook group. There are 1700 other programmers out there. And in case you're wondering, all of the website and everything is funded 100% by your donations. When you look at my dashboard, estimated revenue is $0. I do not have modernization on any of my videos. So if this helped you guys, especially if you're running a business and you're training your people, feel free to donate and help others.


Drop something. Oh, you're gonna mark it. I hope so We might be building this like a pad Stevie under these steps of slate. Oh, yeah We're just going with what I got for steps. I'll just tack it up here with a gun That's all there That's all there now. I'm just starting to poke through. This edge wants to be even here I think what we're gonna have to do is hold each hole one of those And gun is that got 16s I put 16s in there.  No, that'll come my way Beautiful. Thank you. You done with us for a minute? Yeah All right, you you want to start wrapping? Yeah, you'd like me and then I can hang down below a little bit You want it down below or no, I don't know we did in my house, but I'm not just cutting it off probably bring it down to the Bottom of these six by six you want it that well To match up the backside. We may have to put a board in there eventually Down the whisk of Joey. Let me match this board. Let's match this board. All right Wait These Stevie are the staples for this gun. Okay, and these are the staples for this gun. All right, I'll keep it tight I'll just go right across the top of it. Yeah, yeah Whatever you do some lower right Donnie or no, yeah my stand Looks pretty good looks different on the window, but you have lined up with the board Let me do some in the middle. Yeah Yeah, I'm gonna swing really hard How much overlapped you want on the car actually how much wall are we wrapped up on the whole thing? How much overlap? All right, I think you come down to that look top line just the top line Okay, I might put it in the top so I'm cutting the top Do I think that's how we figured it Oh, do you want to get to the front? Did you get the front already?  Yeah. Yeah How's it going like this right? Yeah, take us in Johnny. I saw a piece of board Yeah, right now This minute We'll put another wrap on it. I got about me not a foot or so. There we go Yep, pull a little more Joey this way Couple right there. Yeah The technology Donnie do yep, but do you have the will power that's the key It's gonna be a bunch of rocks Munch of slate slate would be good wouldn't it a lot slate? Yep Probably have to build the ground up with gravel out here To something. Yeah Whole lot of slate Well Sean's pretty lost by now. Yeah, I'd say two more hours will give him Call game wardens Yeah, they lost for days We give them two more days Stevie you slinging Gatorades Yeah, what do you want? What do you want one Donnie? Yeah, please? I don't see that you have one Thank you Yeah, that's the side in for Till next summer, maybe what are you gonna do with that Stevie? Put it up on the roof. Oh Brings good luck Yeah, I've seen it a roof before yeah, what do you think Stevie think we can throw enough slate Flat slate in there to bring that up Fill up your tailgate two or three times when we can back up to it. Yeah, they look good Donnie Yeah, I'll put a couple steps on yeah, I'll dig some out some of them boards out for you. I Got one here geez What's our finish shreds gonna be 10 or 11's put a riser board on it? No on it. No, I don't think we do No, I don't either not with snow and I'd probably bring it out a little bit Ten and a half Doesn't look too bad not at all Like those wide steps.  I'm gonna find out. I said I know I mean I'm exactly the same way I gotta be more like Joe Adam send send me and Donnie up for a weekend Yeah, that last step is a doozy Oh, I don't know if he trusts it, darling. He's getting more blocking Oh All right, I'm not Steve you've got all the orange. He wants you guys No one's gonna be here and Sean gets here. No, you'll think it's the wrong place. I recognize your No, yeah, you got room for both of us TV. Oh, yeah Well, I'd say the work day is about done then I'm done. He's changed right around your camp a pretty yeah Oh, I feel like I don't feel like doing much more. I know I can carry some board, but That is gonna be somebody else's detail. Are you saying a lower skill? Without why yeah, unless unless We don't know the skill level I think we do you do We're looking at it. I wouldn't take that Stevie Stevie crushes it if somebody was to over there help him. He's got it. He's got it What time you have Donnie? Oh 10 or 4. Jesus. Why am I so friggin tired today? That's only 10 hours Well, I think our viewers would like to see some grouse hunting From the comments we get. Oh, yeah. Yeah, for sure. They were bombed out when we only had the Waltents set up video and nothing else after it Lots of comments on that What do you think should we go whack on? Gotta see what How's that for break? Well guys, we're gonna go for a little bird cruise Got Donnie in tow in the back He's ready Stevie over here, and I'm right here and we heard it's gonna be a terrible year for grouse because of how wet and cold It's the wettest year in my entire lifetime For the spring and summer and everything so it's not good on the eggs is not good on the young on the brood So So that might be a bad year, but we're we're gonna cruise around on these dirt roads You don't need a seatbelt up here in the north main woods. We're gonna go about 10 miles an hour It's just back woods logging roads and see if we can see a bird from the truck or usually they come out and pick for gravel and if we see a Good-looking area with a bunch of alders. We might even jump in and see if we can kick one out You just getting here or what? No, that's what we did You just getting here. Yeah, that's a good time. I was like where is everybody?  It's like a beaver chewed on it. What do we open it up here, Donny? Get the pot anyway, this is a grumpy old man's unboxing Brand new saw I hope there was a blade in the box. Oh, there it is Is it lighter Probably got no battery for blade It's a beauty that's all right. No, no take over. I'm good so John Brandon said you work carpentry for five years. No, bring those. That's made out dog I did I just don't put away. No, that's all right. I'm just gonna put them in I was a labor. I don't know a ton about building houses. Neither do we. I sure don't John This guy's talking he's in like board shorts like to serve. He was here when I got there. Yeah Am I yeah, I got all day real He just pulled in when I got there.  I must have been just behind you Probably I think I saw you if you said if you got a ladder stick. I did that pass you Know you Yeah, I don't know if you that was you or not. No, it was I had a ladder on back silver. Yeah, but I Don't know I saw a bird in the road And I slay my brakes on and then this truck came up like right behind me But I don't remember if that was the one of the ladder or not. Well, let's just say it wasn't You can get if you get close enough to the vehicle that's great You can like just get off the side and just ride there and most of the time they'll pull over And the bird hunters and stuff. I didn't know who was I just was like let me roll