What if I told you that that lockout lever that you have on your bike for both your front fork and your rear shock is largely unnecessary and doesn't actually improve your bike's efficiency? It's certainly a bold claim considering that it's pretty much common knowledge amongst mountain bikers that bobbing suspension robs you of power. And no, I'm not talking about keeping your suspension open on a rocky, rooty climb to maintain traction and a consistent power output. I'm straight up talking about a smooth paved road where that suspension is doing nothing for you but bobbing up and down. Certainly in this situation, suspension has to be costing you power, right? Oh, for sure, dude. Also, the eight beers I had last night probably didn't help. In this video, I'm going to be taking a look at the research to get to the bottom of this question. And I was surprised enough by the results that I actually put this question to the test myself and I'll be sharing those results with you at the end of the video. So without further ado, let's jump into the science on how suspension affects bike efficiency. There are two possible ways that leaving your suspension open while riding on a smooth surface could be less efficient. It could be less mechanically efficient, meaning that at the same power output, you're riding at a slower speed. Or it could be less metabolically efficient, meaning that your body has to work harder in order to ride at a certain power output. This study on the effects of suspension on the energetics and mechanics of riding bicycles looked at both these possibilities. In their first test, subjects rode uphill on a motorized treadmill on a road bike with steer tube front suspension while oxygen consumption and mechanical power output were measured. What they found was that the difference in both metabolic and mechanical power in both the sitting and standing trial was not statistically significant between the compliant and rigid conditions. So no difference in efficiency between having the suspension locked and unlocked, and this didn't change when they had the subject stand, which you would think would have more of an impact. Of course, this first test was done on a road bike with steer tube front suspension. And yes, if that sounds like the system that Specialized uses on their Diverge and Roubaix, then you'd be correct. But is it really all that surprising that an otherwise rigid road bike with a small amount of suspension right at the steer tube would yield these kinds of results? I don't think so. Fortunately, they did the same test with a full suspension mountain bike. What they found after test two using a full suspension was that again, the mechanical power required between the two conditions was identical. And the metabolic power average was very close, close enough that results were not statistically significant. And this goes for both the seated and standing test. All right, now we're getting somewhere. And I got to be honest, after seeing these results, I was a bit skeptical. It goes against the grain of what the cycling industry tells us and, quite frankly, what our own intuition tells us. Mashing up a climb with squishy suspension sagging under you with each pedal stroke simply feels slower. I will say, though, that just because something feels slower does not necessarily mean that it actually is. A perfect example of this is a narrow tires set to a high pressure. Riding 23 millimeter tires pumped up to 130 psi may feel fast, but we have data now that indicates that this is not actually the case. That's a topic for another video, but for now, let's get back to the science on suspension. Is there further data to indicate that the lockout on your suspension is not actually improving your efficiency? This study on the energy cost of riding with shock absorption systems had subjects perform grated tests on a full suspension, hardtail, and fully rigid bike. What they found was no difference in VO2 between the three bicycle types. They concluded that there is no significant difference in energy consumed by cyclists riding bicycles with and without suspension. The claims of many competitors who still prefer front suspension bikes or hardtails could be related to a possible significant energy loss that could be present at powers superior to 250 watts, which is what was tested here or when they stand on the pedals.  This was back in a time when most cross-country racers chose hardtails, which is why they made that closing statement about why racers might be choosing hardtails over full suspensions. Fast forward 20 years, though, and most cross-country racers have left their hardtails behind. That being said, though, I wouldn't even look to what most people are doing as evidence that it's faster. Well, yeah, not what everyone is doing, but if you're faster than me, then the only explanation is that you've got some superior piece of equipment on your bike and I'm prepared to whip out the credit card in order to fix that. Again, I go back to tire width and pressure. 20 years ago, you may be forgiven for thinking that narrow tires pumped up rock hard were faster, but since then, we've learned a thing or two. And 20 years from now, there's probably some piece of equipment that we're using that will look back and go, what were we thinking? All right, back to suspension again. These are not the only two studies coming to this conclusion. For example, this study found no difference in climbing speed and energy expenditure between a full suspension and hardtail, and this study comes to a similar conclusion as well. This review of many studies on the topic states that evidence in the literature suggests that cycling-generated power that is dissipated by suspension is minimal and probably negligible on most terrain. It simply doesn't appear from the literature that riding along with your suspension open is less efficient than locking it out. And this is the part of the video where I say the research is limited, but all the studies seem to be pointing in the same direction. The difference here is that this is actually not that difficult to test out on your own. You can do it in one ride, which is exactly what I did. I went to a local paved climb and rode up and down it 12 times to get some data points. Now, bear in mind that while these were all done on the same day with relatively low wind, these are not perfectly controlled conditions, and the sample size is just one. Me, so take these results with a grain of salt. I more so just wanted to see if I could replicate these results that I was seeing in the literature out in the real world. Doing your own test, so this is basically turned into a GCN does science video.  The bike I used for this test was my Niner RKT9 RDO Cross Country Full Suspension with a Fox 34 step cast fork and Fox Float Shock. I used my quirk power meter to collect power data. For this test, I alternated between locked out and open. So six of the runs were locked out and six of the runs were open. I also did half the run seated and half the run standing. And of course, I rode at the same power output for all the runs at 250 Watts. Here's what I found. My run times are all recorded here and just from a quick glance, you can see that they're very similar, but we'll get to that in a minute. I was able to keep my power for each run very consistent. On only three of the 12 runs, did I not hit exactly 250 Watts and was one watt off, but taking into account all three runs for each condition produced an average of 250 Watts across the board. And perhaps somewhat surprisingly, these produced pretty similar results across each of the four conditions. Here's what my average time was for each condition. Locked out seated was three minutes and 30 seconds. Open seated was three minutes and 31 seconds. Locked out standing three minutes and 32 seconds and open standing three minutes and 32 seconds. And then of course, the most relevant bit of information for this video, the average of all the locked out runs versus the average of all the open runs. 331 and 331. It simply doesn't get any closer than that right there. Interestingly enough, the seated runs appeared to be two seconds faster than the standing runs at the same power. And I imagine that this is probably due to the increase in aerodynamic drag of the standing position, but there was no difference in average run time between locked out and open suspension when I was standing. This was enough for me to say that for me on this particular bike, yeah, same power is going to equal the same speed regardless of whether the suspension is locked out or open. Now, my bike has a pretty solid pedaling platform and it's an XC race bike. If I had done the same test on an Enduro bike, what I have gotten the same results, maybe I really can't say for sure, but given the fact that the difference between locked out and open wasn't a small difference, but actually no difference. I can't see any reason to think why bumping up the suspension travel would change that. Perhaps some of you with bigger bikes can test this out for yourself and tell me if I'm wrong here. One last important bit of data to point out. I was wearing a heart rate monitor for this test and this can give us an indication of the cost on my body in each condition. This data does raise a few questions. My average heart rate for the locked out runs was 134 and my average heart rate for the open runs was 137. Now, again, this is not nearly enough data to make any sort of conclusion, but it is interesting nonetheless. One potential confounding factor here though may be the fact that I started with the locked out effort and my heart rate tended to rise throughout the course of doing these efforts, which may be skewing my heart rate up for the open runs. So what can we conclude here? Well, let's see about that. You didn't get the KOM with the suspension open or locked out. So absolutely nothing.  Again, I want you to take the data that I got on myself with a grain of salt, but given the literature that we have on this subject, I would say that locking out your suspension does not improve your bike's efficiency. Sure, a locked out bike feels faster, but just because something feels faster does not necessarily mean that it is. What does this mean in terms of how you should ride? Well, first things first, if you're in the market for a new mountain bike and you're deciding between a full suspension and a hardtail, or maybe you already have a full suspension and a hardtail and you're trying to decide which one to use for a particular race or ride for that matter. The efficiency of the bike should not be part of your decision making process because a hardtail is not going to be more efficient than a full suspension. And when you take into account all the roots, rocks and undulations that you come across when you're mountain biking, the full suspension quickly becomes the more efficient option. The only advantage that the hardtail has over the full suspension is that it's lighter, and this may be significant depending on the course, but I would say that it would probably have to be a pretty smooth course with a lot of climbing. Finally, as far as how to use your lockout when you're riding your full suspension, when you hit a road section, I wouldn't just not use it. The psychological boost that you get from feeling like your bike is faster probably does something for you, so if you have it, use it. That being said, I wouldn't be overly concerned with constantly locking and unlocking your suspension when you're riding on trail, especially if it's just another thing that you have to think about and taking away from your focus on the trail. Because at the end of the day, that lockout is probably not doing a whole lot for you. Thanks for watching. If you enjoyed this video, be sure to give it a like, subscribe for more science-based cycling content just like this, and share this video with your cycling friends. I'll see you in the next one.


Hi everyone, Joe for Jasper's casebrace.com. I'm a dumb I forgot the so excited about the Anthony Edwards that we pulled in this break and pick your team one that I forgot about the break Credit randomizer So if you bought a team straight up if you bought two teams straight up You'll get one entry for it gets you two entries six gets you three entries on and so forth now A lot of people did not buy their teams straight up I guess they didn't want break credit So the odds become a lot better for this group right here Ben got gets two entry or yeah two teams That's an entry Brian only got one David got two teams. That's an entry Jess got two teams. That's an entry Matt only got one Patrick got two. That's two entries or Patrick got four teams That's two entries Paul only got one and Sean got two teams. That's an entry So four out of the six people are gonna get a hundred dollars break credit each It's not bad now if you watch the previous video, we're gonna we're gonna use the same dice roll We would have used the same dice roll if I didn't forget so 11 times new list and Top four after 11. Good luck hundred dollars break credit each one two three four five six seven eight nine Ten and eleven in final time after eleven we've got David Patrick Sean and Patrick Congrats you Hundred dollars each going your way. I'm Joe for jaspys case breaks calm. I'll see you next time for the next break. Bye. Bye


Our focus this week is with the 50 teachers that we have is on edtech integration. The first three days were spent with teachers learning how to use new edtech tools or tools that were already familiar with them such as Google Jamboard and Google Forms. And so far they've created over 100 activities using those tools that will be made openly available to all teachers. Now we're in the second half of this training week in which they're thinking about how do they actually implement these activities and these tools strategically with their students. And so today we're thinking about in their subject areas what types of routines do they do with students on a regular basis even without technology. And now they're actually working in small groups to consider how could those routines be made more effective using educational technology. Having attended the edtech training session this week has been a great learning experience for me. As a teacher generally we are being told of tools and resources that we can use in the classroom that we can implement in the classroom. However being at this workshop we will not just told what the resources are or the tools are we will actually taught how to use it, how to implement it in our various subject areas because it would be different how you use it in math would be different from how you use it in social studies. So we were taught specifically how to use it in our various subject areas. For example Jamboard, I have been using Jamboard for a while however attending the workshop I learned so many new ways that I could use it in my classroom which will make me a more effective teacher which will make the teaching and learning process more fun and interactive for the students. It's quite a lot of things that I've learned this week including using Microsoft Forms, Jamboard, Mentimeter, Padlet, we have not only introduced to those different forms of technology but also how to use them and we also came up with our own forms of these forms, Padlet and these different things that we taught during the week. This is an ever evolving field and so most times educators try to find innovative and interesting ways to try to enhance learning for the students or how to integrate that technology back into the classroom and so this project this week gave us a little insight to more edtech tools that we can use in our classrooms and I think this week I learned a lot. I feel as an IT teacher most times we are the first ones who integrate or look for the new technology to integrate into the classroom but I found that this week I learned so many other tools that are in existence that I have not even been using as yet. We have gotten a lot more ways in which we can use these tools within the classroom for various activities other than just minimal assessments so also the framework that we have been taught in planning for using these tools in the classroom is very essential in what we're going to do moving forward for our lessons we want to ensure that we know exactly what we're going to do with our students beforehand instead of just experimenting in the classroom. So this framework really helps us plan out what we are supposed to do and how we're going to use it so that when we get into the classroom it is a seamless transition from our instructions to our students. In addition to that we were not just taught how to use the tools we actually had to create our own resources which means that when I leave the workshop I will have a number of resources that I could include in my classroom and also we will we are to share the resources with other teachers which means I'm not only going to have access to my resources but resources that other teachers have created which will be great. So overall the experience here has been great it has been wonderful I have learned a lot and I am ready to go back to my classroom ready to go back to my school to share with my colleagues what I have learned how they could use these resources to make the teaching and learning experience more effective and of course more fun and interactive for the students. As a math teacher math is very abstract and when we use these kind of forms of technology it tends to take out that abstract from our maths here so we make it a little more graphical a graphical representation for math students and I'm looking forward to going back to my school to actually pass on that information to my peers. And one of those that I liked the most was the Jamboard and it was just this interesting tool that you could use in your classroom where you could get all of the children on board in terms of putting together a vocabulary list and finding definitions and being able to work with the technology and still learning as well. And so I'm excited to go back into the classroom next term and implement some of these tools that I've learned this project as well as to see how I can support my colleagues in learning as well for the new edtech tools. Through the activities that they've been doing all week they're designing an action plan for themselves for the upcoming school year on things that they will do routines they will do on a regular basis and the explicit digital skills instruction that they'll be integrating as part of those routines so that they're better preparing students for the digital skills that they need for future work and life.


Well, if you watched my previous video on how to take a cam out, what I had done was I wired this up. So I took this gear out and I've got the chain hanging on a wire. So I'm about to remove the head and what I got going on is I got a head gasket leaking and coolants going into the piston. So what you do is you got these funny looking bolts here. You take a 14mm socket like this, it's a 12 point, it's got to be a 12 point that will fit on there real nice and that breaks them loose and you can take them out. You want to make sure that chain is wired up here because you don't want to lose that as you'll be fishing for it. So bottom you'll have to take the flywheel off. Also keep in mind after these four bolts, there are two that are down over here by the opening. Take that panel off to access the chain and the gear and it's 2.8mm bolts that get unbolted. I hope you guys can still see. Now this one I left so you guys can see how I crack it open, it's just pretty tight. Just take a hammer, give it a little pop, break it loose, take those off, I'll have to feed my chain through the head while I'm taking it off. There you have it, let's see it was leaking right here. What I should really do is unbolt the jug and put a new gasket at the bottom so I've got that gasket too but I don't think I need to worry about that, I think it's just this top that's leaking, I can see the parts where it's leaking, it was leaking right here, I think that's where it warped a little bit. So I'm going to go ahead and clean that up and then reinstall it. Alright so I cleaned everything up, you got the new gasket on, it's kind of foolproof you can only put it on one way because of the dull pins, now I'm going to put the head back in, feed the chain through, so the tricky part about this is going to be torquing everything down, feed this through, start on my hand, so I'm just taking a little oil and dipping it in there, acts like a cutting oil, so I'll do that to all four, I'll get them snug and then go through the torque process, okay so what I'm going to do is I'm going to put a mark on each one of the bolts on the top, only because this torque sequence is very weird for Polaris, so torque it down 22 foot-pounds first and then 51 and then after that you have to back it off, tighten it a quarter of a turn, back it off, I'll kind of go through everything, 22 foot-pounds in each one, we'll go a criss-cross better, snug these up 22, 22, so the next step is we'll go up to 51, 51 foot-pounds, now it says loosen it up to 180 degrees or half a turn and then tighten it at 11 foot-pounds, so that's where the marks come into play, tighten it at 11 foot-pounds, now it says tighten it another quarter of a turn and then step seven is tighten it another quarter of a turn, so that's where your marks come in, another quarter of a turn, now I'm just going off the marks, so don't pay attention to how many times I'm ratcheting, I've got marks, this mark's going straight down, I'm going to turn that a quarter turn, now the next step says give it one more quarter turn and I'm going to bump this torque wrench back up, it feels like struggling too much, what you're doing is basically you're using the threads and you're cutting it, I've got these two bolts to put in down here, those are eight millimeters and I don't know the torque specs on those, you've got an eight millimeter, just tighten until your neck muscles tighten up, that's what I always do, there you go, put your gear back on and I'll hang it back up, get it ready for the cam installation.


Good afternoon everybody.  My name is Yair. I'm the product manager for the cultural heritage division at phase one. Phase one, if you are not familiar with the company, we're a small organization with about 330 employees worldwide. We develop and produce and provide digitization equipment or digitization solutions. For this market, but our core technology serves in several different market segments. If you look on the left, we have devices that can do aerial imaging. So people like Amazon, like Google, they use our equipment. Fashion photographers, architecture photographers, car photographers, landscape amateurs, professionals, everybody uses our equipment. Of course, it sits at the high end. It's not exactly a consumer level product. Most of the technology is ours, meaning that we develop the software, we develop the hardware, but we work closely with third parties. If you had the names of Schneider in Germany for optics, we have some partnerships with the small software developers and so on. Cultural heritage became a real segment for us about four or five years ago. Before that, we were always selling cameras to museums and archives and libraries. But then we looked at it more seriously and thought, well, what about all this market? What exactly the needs are? What can we offer that makes us maybe better than the competition, but also makes our solutions more suitable for the digitization project? Just a few names that we can drop and as you can see, it's worldwide known brand in the marketplace and we work with museums, with archives, with national libraries, with some private funded foundations. It goes across many, many segments. The core, let's say, three pillars of our technology or our solutions. First and foremost is the camera, the one on the left, uniquely developed for a reproduction kind of work. So it's not exactly your consumer pocket camera that you just have in your pocket. It needs to be mounted on some kind of a copy stand, the one in the middle. And it needs to be driven by a very advanced piece of software called Capture One Cultural Heritage. I'll get to that. The camera itself, let's say it's core technology, it's based on our wide experience in the aerial imaging type of work. So it's all about reliability. It's all about the best or the highest image quality, consistency. If you think about an aircraft that goes up to do some mapping work and stays in there for four hours and comes down with 40 gigabyte of images, they all need to be timed correctly. They all need to be captured accurately with the right kind of dimensions and focusing and all of that. So we sort of learned a lot from there and implemented it in this IHG repro camera. At the moment, the model we are actually demonstrating downstairs has a 100 megapixel sensor saying that literally last Thursday we announced that we are going to come out with a 150 megapixel sensor to understand what it actually means. If in the reproduction, let's say, market there's a benchmark called A0 at 300 PPI, which up until now you could only do with a large format scanner that typically is very high quality, but is also quite slow and quite complicated to operate and things like that, whereas here an A0 at 300 PPI can be captured instantly. So as long as you can turn pages or change drawings fast enough, the camera will keep up with you. We use the best optics, the best focusing ideas. We can actually use autofocus using the image the sensor is actually seeing. So we use a live view image on screen and the camera can measure distance, can calculate resolution and based on that will decide on its position and it will also guide the copy stand that it sits on to move it up or down as necessary. When it comes to the software, Capture One, some of you might be familiar with it. It's a very popular, very common, very powerful capture and processing workflow piece of software. About four years ago we decided let's use the good things from it. Let's see what is actually necessary for cultural heritage work for digitization work and we added a few bits and pieces and a few very unique tools that help you with measuring resolution, with achieving the exact kind of color, exposure, contrast, dynamic range and so forth required for things like fudgy or metamorphose guidelines if anybody has heard of them. So we provide the tools that allow you to actually achieve those targets. You don't have to worry too much about how do I set it up, which button do I need to press and so on. It's all about automation of things. So for instance if you do film scanning and you have a large collection of be it glass negatives or film negatives and you want to quickly invert them to become positive images, the software can do it for you and it takes into consideration the original exposure of the film. Of course there is some ways of adjusting and manipulating images as well. It's all based on raw workflow. So the images are raw images that you can process now, you can process later, you can archive and process in 30 years time. We capture in 16 bits so we make sure that we preserve as much dynamic range as possible especially when it comes to really all the objects. The copy stand itself like I said is controlled by the camera and by the software. There is manual override so you can decide I'm going to start this side today and see what I'm covering or I can tell the software that I'm doing a A3 job that needs to be digitized at 400 ppi and between the camera and the copy stand will adjust themselves and set at the exact position and we claim and we actually can prove that we always stay within one or two ppi from your target. At the moment this is the only camera based repro device that can actually do such a thing. In comparison let's say the motors that we use in the camera and the copy stand they can do steps that are like six micron size each step. In comparison if you compare it to your average DSLR or even some of our other cameras we're looking at a hundred microns and that's less consistent let's say accurate. More maybe interesting or maybe sexier projects that we've been involved throughout the years that are also grabbing more attraction now and getting some attraction. One of them being multi-spectral imaging and when it comes to cultural heritage this can be old manuscripts, parchment, polymps, old masters paintings and it goes from looking for hidden text on a polymps for instance if you have a piece of a skin of an animal that was used 600 years ago but somebody by somebody from one church somewhere and then you discover by doing some multi-spectral imaging and analysis you then discover that 300 years ago somebody else used that piece of skin again scraped the ink of the old one and wrote another piece on it. We use the same basic camera but with a different set of filters the camera can see a little bit into ultraviolet it can see a little bit into infrared as well and we can create what we call a perfect stack and that perfect stack can go into analysis software like ImageJ, Paléo tools or MATLAB or any other open source solution maybe the last thing 3d scanning again a very sexy word these days a project that we've been involved with together with Fraunhofer a small research institute in Germany they're using our camera on a robotic arm to scan well 3d objects very accurately in terms of dimensions texture and color which is quite unique because there's a lot of laser based scanning devices and so on that can do this but they can't really see the object much of our investment goes into automation we beat the automation one button handling of 3d scanning or going through the perfect stack in multi-spectral imaging or even the small things like cropping pages automatically or recognizing barcodes in an image automatically things like that this is where we we put a lot of effort in like I said we have a small space downstairs near the toilet so everybody actually during the day has to be there at some point and we have our camera there we have a few sample objects that we can either show you the whole workflow or just discuss software if you have any questions by all means thank you very much


From your previous study of oscillators, you've learned that frequency stability is of the utmost importance. You might ask why all of the concern about frequency stability. As an example, let's consider a radio broadcast station. I have here a book of FCC regulations governing the operation of radio broadcast stations. One particular regulation prohibits the frequency of the station from changing more than a few cycles, and it's a pretty stiff regulation. But it must be so, so that the station will not interfere with another station operating on a nearby frequency. Now for this reason, the oscillator producing this frequency must be one with the very best frequency stability. An oscillator capable of producing such an output is the crystal controlled oscillator. We're not going to study the oscillator circuit in this lesson, but we will study the characteristics of the crystals used in such a circuit. And here I might add that the crystal will be used as the frequency determining device of the oscillator in much the same manner as a coil and capacitor was used in oscillator circuits previously covered. Now some of the items that we're going to discuss are the use of crystals. Types of crystal substance is used, crystal cutting, types of crystal cuts, crystal characteristics. You'll see the purpose of a crystal holder, the frequency stability of crystals, and a little bit later we'll discuss overtone crystals. Now there are many types of crystal substances, but not all are suitable for use in oscillator circuits. A crystal used in oscillator circuits must possess a characteristic known as piezoelectricity or the piezoelectric effect. Let's look at a definition of the piezoelectric effect. Now the piezoelectric effect is defined as the property of a crystal by which mechanical stress produces electric charges and conversely electric charges produce mechanical stresses. Now at this time you should complete item one of your TVI guide. Now this is saying nothing more than if a voltage is applied to the crystal it will vibrate. The amplitude of these vibrations are such or much greater at one frequency than at any other frequency. Now this one particular frequency is called the natural resonant frequency of the crystal. Now let's look at some of the crystal substances that possess the piezoelectric characteristics. They are Rochelle salt, tourmaline, and quartz. Now we should include these substances in item two of the TVI guide, the A part of item two. Now of these three Rochelle salts exhibits the piezoelectric effect to the greatest degree. However quartz crystal is most generally used because it has a greater mechanical strength. Now at this time let's complete the B part of item two. The substance most often used in oscillators is, go ahead and complete that blank. It is quartz crystal. Remember it has a greater mechanical strength. Now I want to show you a piece of quartz crystal in its natural form. Now if we were to examine this carefully we can see that the quartz crystal has a hexagonal cross-section. That is to say it has six sides. Also quartz crystal in its natural form has pointed ends. This one doesn't because a primary cut has already been made on this crystal. Now let's take a look at this drawing so that we can determine more about the quartz crystal. There are two views. The top view indeed shows us that the quartz crystal has a hexagon shape, six sides. While the lower view points out that indeed the quartz crystal in its natural form does have pointed ends. Now quartz crystal in its natural form cannot possibly be used in oscillator circuits. It must be cut in a specific manner to exhibit its piezoelectric properties. I know all of you at one time or another have heard of diamond cutting. The reason a diamond is cut is to give it brilliance. And the manner in which it's cut will determine its degree of brilliance. A piece of diamond in its natural form would never be used in a diamond ring. Just as a piece of quartz crystal would never be used in an oscillator circuit. Now when a piece of crystal is going to be cut, imaginary lines are used as the reference points for cutting. And these imaginary lines are known as crystal axes. Let's take a look at this drawing of a crystal and see the exact location of the crystal axes. The axes passing from point to point are end to end and directly through the crystal is known as the z-axis. Remember from end to end directly through the center. The axes passing through the corners of the crystals is known as the x-axis. Remember it goes through the corners. While the axis perpendicular to the faces of the crystal is known as the y-axis going through the faces. Now let's remember these are only imaginary lines and are used as reference points when cutting the crystal. Then at this time complete item three in your TVI guide by labeling the axes there. Now all crystals are not cut in exactly the same manner. Just as all diamonds are not cut exactly the same. The properties which a crystal exhibit are dependent on the manner in which it's cut. Now there are many different cuts but we're only going to examine three basic cuts. Let's go to this chart and see exactly how we make these three particular cuts. The first cut is made perpendicular to the x-axis which you will recall passed through the corners of the crystal. It's perpendicular to that axis and parallel to the z-axis. Now to get a more realistic view of this cut let's go to a mock-up. Remember we're considering the x-axis passing through the corners of the crystal. The cut is made perpendicular to this x-axis and parallel to the z-axis. And the cut would look something like this. You can see that it's only a small portion of the natural crystal. Now since this cut was made in reference to the x-axis it is known as an x-cut crystal. Okay let's go back to the chart and see how another cut is made. For this cut we will use the y-axis which passed through the face of the crystal. This cut will be taken perpendicular to the y-axis and it also is parallel to the z which you will recall ran through the center of the crystal. Remember perpendicular to the y parallel to the z. And again to get a more realistic view of this cut let's go back to the mock-up. Remember the y-axis passed through the face of the crystals in this manner. We'll cut perpendicular to that and parallel to the z-axis. And we come up with our second cut which in this case since we took it in reference to the y-axis would be known as a y-cut crystal. Then let's go back to our chart for the third and final cut. Now this time we're going to cut at an angle from the z-axis. Recall the z-axis passes through the center of the crystal from end to end. And for this cut we'll cut at a 35 degree angle from the z-axis. Remember 35 degrees from this z-axis. Okay back to the mock-up once more. Now in this case the crystal cut is taken right in or made right into the face of the crystal. Remember the z-axis is running down through the crystal in this manner. And we'll cut at a 35 degree angle from this z-axis. And removing the cut from the crystal. Again only a small portion of the natural crystal. We call this cut an AT-cut. An AT-cut crystal.  Now we've seen from the mock-up what these three cuts look like. Let's go over and I want to show you the actual cuts now. I have here three crystal cuts. Now as you can see they look like small thin wafers and each cut looks very similar. Each cut looks very similar. Now all crystals look the same but not all will exhibit the same characteristics. Now you'll recall earlier we mentioned the resonant frequency of the crystal. Not all crystals naturally will have the same resonant frequency. Its frequency will be dependent upon its thickness. Let's take a look at two pieces of crystal cuts and compare this difference in thicknesses. As you can see the thinner cut here, the thicker cut here. We're indicating here that the vibration of this thinner cut or the frequency is greater than this cut. Now this will always hold true. The thinner the crystal cut the higher the frequency of oscillation. Okay then at this time let's refer to item five in our TVI guide.  In order to increase the frequency of a crystal it should be cut. We just saw that. It should be cut thinner. Now another characteristic which will be different for the various crystal cuts is the temperature coefficient of the crystal. The temperature coefficient. Now this is a new term so let's define it. Temperature coefficient is the relationship between temperature and frequency change. Then at this time complete item six in your TVI guide. Temperature coefficient is actually the effect that a changing temperature will have on the frequency of the crystal. Now let's compare the temperature coefficients of the three cuts that we just considered. The X, Y, and A-T cut crystals. To do that we'll use this chart. On the left we're indicating the type of crystal cut, the X, Y, and A-T. Let's begin then with the X cut. The temperature coefficient of the X cut is negative. This means that if temperature about the crystal increases the crystal frequency will decrease. A negative temperature coefficient. An increase in temperature, a decrease in frequency. The Y cut crystal has a positive temperature coefficient. If temperature increases the frequency increases also. A positive temperature coefficient. The A-T cut crystal has a zero temperature coefficient. That is to say as long as the temperature ranges between 40 to 50 degrees centigrade. Remember as long as the temperature is within this range the frequency of oscillation will remain the same. Then the A-T cut has a zero temperature coefficient. Now at this time you should complete the chart in item 7 of your TVI guide. Now from this you should be able to reason that the A-T cut crystal would be extensively used. Now there are a few other crystal cuts with better frequency stability. But these will not be discussed in this lesson. Now when an extremely high degree of frequency stability must be maintained the crystal will be placed in a temperature oven. A temperature oven. A temperature oven is nothing more than a thermostatically controlled container used to maintain the crystal temperature in its proper range. And in doing so of course we have a high degree of frequency stability. Then let's go to item 8 in our TVI guide. When a high degree of frequency stability is to be maintained a crystal will be placed in a temperature oven. Temperature oven. Nothing more than a thermostatically controlled container. Now in order for a crystal to be used in an oscillator circuit it first must be placed in a holder. Now the crystal holder will support the crystal physically and provide the electrodes by which this voltage is applied to the electrodes. The holder must allow the crystal maximum freedom of vibration at all times. Let's look at this drawing of a typical holder. The crystal will be placed in the holder between two parallel plates. The plates have an air gap between them which allows room for the crystal to vibrate. The two plates then are connected to the pins. Now these are the pins that will allow the voltage to be applied to the plates. And also the pins will allow the crystal to be connected into a circuit in much the same manner as a vacuum tube. The spring will keep a constant pressure on the plates and hold them firmly in place. The crystal holder cover usually indicates the fundamental frequency for which this particular crystal was cut. In this case the crystal was cut to oscillate at a fundamental frequency of 430 kilocycles. Now so far we've seen the physical characteristics of the crystals. Let's now see how the crystal reacts electrically. To do this we'll look at the electrical equivalent of a crystal and its holder. The crystal itself, when vibrating, acts very similar to a series resonant circuit containing resistance, inductance, and capacitance. Remember this is when the crystal is vibrating. Now when the crystal is placed in the holder the capacitance of the holder will be placed in parallel like this. CH, the capacitance of the holder. So this capacitance represents the holder capacitance. This represents the vibrating crystal. Now at this time you should complete item nine of your TVI guide. Now just because this vibrating crystal is equivalent to or is the equivalent of a series LC tank circuit I don't want you to think that it's the same thing because the crystal will be far superior to the LC tank circuit. Now the Q of the crystal circuit is many times greater than that of the LC circuit. Let's take a look at the comparison between the Q of a crystal and an ordinary LC tank circuit. The Q of an LC tank circuit is seldom greater than 2000 whereas the Q of the crystal is sometimes as great as 30,000. And as comparing these two you can see that the Q of the crystal would be many times greater than that of the LC tank circuit. Now because of the high Q this would mean that the crystal would have better frequency stability because its bandwidth is much more narrow than that of the LC tank circuit. Then at this time let's complete item ten in our TVI guide. The Q of a crystal is than that of an LC tank circuit.  Now let's look at some of the values both physical and electrical of a typical crystal. Physical size, a typical crystal would have a thickness of about 0.025 inches. The width would be about 1.3 inches. The length would be 1.08 inches. And with these physical characteristics the resonant frequency or the fundamental frequency would be 430 kilocycles. Now with this physical dimensions or these physical dimensions let's look at the electrical value. The vibrating crystal would have an inductance of about 3.3 Henry. A capacitance of 0.042 micro microfarads. The capacitance of the crystal holder would be about 5.8 micro microfarads. And this crystal would have a Q of around 23,000. Now let's remember these values were for a crystal cut for a fundamental frequency of 430 kilocycles and will not hold true for all crystals but it does give us an idea of relative values. Since the crystal is going to be used in an oscillator circuit as the frequency determining device it must be represented on the schematic diagram. Let's take a look then at the schematic symbol for our crystal. These two plates represent the crystal holder while this area would represent the crystal itself. Now this is the schematic symbol of a crystal used in oscillator circuits. So while looking at this complete item 11 in your TVI guide. Earlier in the lesson we discussed the various crystal cuts and how each was different from the other. However they do have one thing in common. That is they can be made to oscillate at frequencies other than that frequency for which they were cut. Now when a crystal is used in a circuit in this manner it's referred to as an overtone crystal. An overtone crystal. Now getting a crystal to act as an overtone crystal is nothing more than causing it to oscillate at a harmonic of the frequency for which it was cut. And I might add here that the crystals will oscillate only at odd harmonics of their fundamental frequencies. Now for example if a crystal was cut for a frequency of 10 megacycles it can be made to oscillate at 30 megacycles. The third harmonic or the third overtone. You might ask how is this accomplished? Simply by increasing the feedback to the point where the crystal is shocked into vibrations at the odd harmonic rather than the fundamental frequency. And let's determine what's happening when this is true. Now here we're indicating the distortions that exist in the crystal when it's oscillating at its fundamental frequency. Here is representing the crystal at rest. No oscillations. Here the crystal is deformed to produce one alternation. And here it's deformed in the opposite manner to produce the other alternation. Now this is when it's oscillating at its fundamental frequency. Notice that the deformities are opposite for each alternation. Now here we're representing the crystal when it's made to oscillate in the third overtone. Now let's notice that the crystal breaks up into three layers when it's oscillating at the third overtone. Now this is representing the deformed layers to produce one alternation. Here the deformed layers for the other alternation. And let's notice that the deformities are opposite for each alternation. Now if the crystal is made to operate on the fifth overtone it breaks down into five layers. If it's made to operate in the seventh it breaks down into seven layers and so on. But I might hasten to add that a crystal cut for a fundamental frequency is limited to only a few overtones. When higher overtone modes are desired then a crystal is precision ground and mounted in a special holder and it would be used specifically for these higher overtones. Then let's start for just a moment and complete item 12 in our TVI guide. A crystal which is specially cut in ground to oscillate at more than one frequency is called an overtone crystal. An overtone crystal. Now let's recap a few of the points that we've discussed in this lesson. First we saw the use of the crystals. Now we said that the crystal must exhibit the piezoelectric effect. And we defined the piezoelectric effect as the property of a crystal by which mechanical stress produces electric charges and conversely by which electric charges produce mechanical stress. Then we saw the three substances used. Rochelle salts, tourmaline and quartz. We said that Rochelle salts exhibits the piezoelectric effect to the greatest degree but that quartz is most generally used because of its mechanical strength. Then we saw the three basic crystal cuts that we were considering. The x-cut which is made perpendicular to the x-axis. The y-cut which is made perpendicular to the y-axis. And the at-cut which is made at a 35 degree angle from the z-axis. And then we defined temperature coefficient as the relationship between a temperature change and a frequency change. And then we gave you the schematic symbol for a crystal. This represented the crystal holder, this the crystal itself. Now in concluding we can say that the one big advantage of the crystal is its frequency stability. Remember it has a very high Q giving us a very narrow bandwidth. Then we have one more TBI guide item to complete, item 13. The main asset of a crystal oscillator is its frequency stability. Frequency stability. That just about concludes the lesson on the characteristics of crystals, so until another time, so long.


A lot of people are on a different point in time where they are in their container journey, and that's why we have the awesome talk ahead of us. So let's welcome Stefan and Valentin, who are going to talk about containers, two pods to Kubernetes, Portman Desktop. Enjoy. Hello, everyone. Thanks for having us and thanks René for the introduction. So as René mentioned, we are going to speak about containers and container tools as well, that helps you in your journey to go to Kubernetes. So I'm going to share my screen now, to share the slide. Should be able to see my screen. And is it working? I think. Yes, it's working. Perfect. So to introduce ourselves, maybe Valentin, you want to introduce yourself first. Thanks, Stefan. Hi, everybody. I'm Valentin. I'm working in the Container Runtimes team. So in the Container Runtimes team, we're pretty much between the kernel and Kubernetes or also now Portman Desktop. So we take care of all the low-level container technologies. We implement, maintain tools such as Portman, Scopio, and Buildup.  Yes, thanks. And I'm Steven Lema, I'm Product Manager working on developer tools. So in the developer tools business unit, we are trying to build a tool that helps the developers to work with containers and work with Kubernetes and OpenShift in a smoother way. So as an agenda for today, we will start introducing a little bit Portman for those who are not familiar with the tool. And then we will discuss a little bit about how developers can go more easily from containers to Kubernetes with Portman Desktop. We will spend a lot of time in a demo and we will introduce the future plans that we have for the tool. And with this, I'm ending over to Valentin to speak a little bit about Portman. Thanks, Stefan. Already looking forward to your demo. They're always awesome. You're really a pirate of live demos. I'm very much looking forward to it. So before introducing Portman, I would like to dive a little bit into the containers philosophy that we have at Red Hat. I don't want to speak for the entire company only for our team. So our approach is really to provide small solutions that allow us to innovate in functionality, security, stability, and all at different paces and speeds. As I mentioned before, there is not only Portman, but also Scopio, which is the tool, like a Swiss Army knife for distributing, copying and manipulating container images. Builder, as the name may suggest, is our Swiss Army knife for building container images. So all our tools share the same underlying libraries for managing container storage, for managing container images. There's also Cryo, which is a tool also developed within Red Hat with the community together for running powering containers and container images under Kubernetes. So really we try to have a more Swiss Army knife approach rather than a one-size-fits-all solution. But arguably, Portman is the biggest of these tools. It does a little bit of everything. Next slide, please, because Portman aims at being a drop-in replacement for Docker. So it is what we call a container engine. Some call it a container runtime, but the terminology of runtime is really overloaded. There's something else actually called a container runtime. So what we define under a container engine is that it manages images, it manages containers, so-called pods, which is a group of one or more containers sharing certain resources. It manages volumes, networks, all the things we need to run and manage the life cycle of containers. So Portman stands short for pod manager and one of the initial goals of Portman was to have a drop-in replacement for Docker. So many of the people in our team have been working, contributing or have been maintainers at Docker initially, but early on there were a couple of issues that we saw in the architecture that I'm gonna talk about in a minute or so, that we didn't like, which we made for instance, and in particular, rootless support much harder than necessary. So what I mean by rootless is that we can run containers without being root on the system. So this is not only great for multi-tenant systems, but also it increases a lot the security. And this is something that Portman supported since version one and actually before. So we have a clear focus on security. And I think Portman is a great tool for developers. This is something that Stefan will focus on, but also for CIS admins. So maybe you don't see it at the outside, but I feel like an old graveyard Linux admin or old school Linux developer. So we got you covered there, but if you're on the Mac or Windows, then Portman desktop got you covered there as well. One more click please. Yes, awesome. Thank you, Stefan. So talking about the architecture, I was elaborating or mentioned just a moment ago where I said early on we saw some issues in the architecture of Docker, which is mainly shown here. So on the left-hand side, you see when you use the Docker client in a terminal dependent, whether you run it on the Mac Windows or Linux in almost 100% of all cases, you don't need to type sudo. So you can just run it as an ordinary user while the client is talking to what is called the Docker demon, which is a server running in a system D unit in Linux. This runs this route for historic reasons. Back when Docker started, many features of the kernel, such as layered file systems, but also networking really required room privileges. So it was just more convenient to put, the Docker client and the Docker group, which grants access to the Docker socket to talk to the Docker demon, which in turn runs this route.  And sometimes people say, well, Tina, I don't need to type sudo and this is fine. The client and the server are in the same group, the Docker group. So this allows the client to access the Docker socket, which in turn talks to the demon, which in turn runs this route. So the problem with that is that, from a security point of view, it's bad. Even the rare case, and the attacker manages to break out, then they have the holy grail, right? Then they run this route and then it's really hard. But also there is a common, it's quite common to mount certain paths or even the Docker socket into the container or into running containers. And then effectively, you grant the containers access to the entire route. So it's just, it can be very difficult to secure these deployments. Potman on the other side does not implement server client architecture, but really a very unique traditional fork exec models such that all containers that you run with Potman are child or grandchild processes of the initial Potman command that you, for instance, typed in your terminal. So Docker, sorry, Potman is not a demon, but voila. If I'd say it's 100% demon less, then it would lie a little bit at least because we still need a process to monitor the container. It's not a demon entirely, it's called conmon short for container monitor, which is started before the container and ends after the container. It also exits with the same exit code, which makes it a pretty, which lets Potman integrate very, very smoothly in system D. So keep in mind, there's this common process, but only for one container. So it's not managing multiple ones, it's only managing one container, which comes in pretty handy when running in system D. Next slide, please. So when I was just mentioning it, Potman integrates very smoothly in system D, which is one of the cornerstones for, you know, running Potman in edge computing. So when it comes to edge computing, this is something very, very dear to my heart. I'll try to make it brief, I could talk about it for an hour, but I wanna leave Estefan enough time for the demo. So there's a couple of things when it comes to running containers at the edge. So that means outside of our traditional server room or cloud environment, that could be a car, it could be an IoT device. So these deployments need to be reliable, we want to be hands-off, we can't just SSH in or sometimes even the network connectivity doesn't allow it. So we need a lot of automation and also these workloads need to be self-healing. So if there is an error somewhere or a bug, you know, if the workload goes down, this needs to be started automatically, it needs to be detected, it needs to detect whether the workload still running is actually healthy or not, and also update it automatically. If you're interested in that, next slide please, we block a lot, really a lot, and we did a lot of things in this space. So go ahead and look, we blocked a lot on Enable Sysadmin, well, lots of Frathead and open source blocks. But the coolest thing in this space is Quadlin. Quadlin is something that we develop together with the auto team. So now, Potman is running in cars, which is pretty dope. So initially, the workflow, when you want to run Potman in SystemD, generate a unit, wasn't necessarily where we wanted to be. So then Alex Larson from the auto team came up with Quadlin, which you can see this Kubernetes YAML or even a compose file, but for running containers in SystemD with Potman. So here in the middle, you can see a table, which Quadlin adds to the syntax of SystemD, and I can specify an image, volumes, exec, all kinds of things. So this is really, really nice. And Quadlin takes care of generating all the complexity of a SystemD unit file to run Potman smoothly, reliable, and all these things inside. So if you're interested in Quadlin, there's a couple of blocks outside, one written by Dan Walsh, which I think most of you know, and Eagle Bloom, brilliant engineer, also working on auto and many, many, many other things. So I think this is pretty much all from Myset here, and I hand it over to Stefan. Yeah, thank you, Valentin, for the introduction of Potman. I think this gives a good context of all the different capabilities that Potman is looking after. Right now, I'm going to transition to Potman Desktop. So Potman Desktop is a native application that provides an easy to use user interface to work with containers, but not only works with containers, it also enables you to more easily transition for containers to Kubernetes. So I'm going to introduce the tool, and that's very important, because in fact, when we think about local developer environments, I think we can agree that they become impractical and they lack of consistency with production. In fact, there's a lot of complicated setup when you need to get the environment up and running. And your laptop is naturally not able to run all the things that you will be running on production. You have limited resources.  We know there's a lot of many, many different pieces at work that are difficult to reproduce on a developer environment. And there's also a lot of discrepancies between the way the containers and composite applications are being created and configured to talk to each other on a local developer environment and the way they will be configured on a production environment. So to solve this, in fact, a lot of developers end up using things like Docker Compose to group applications. And in fact, it brings you in the worst of both worlds because the developers are using a technology that then needs to be translated for running onto a production environment. So this is hard. And we know that it is hard because there's also a gap in the skills that the developer have on Kubernetes in general. And that creates some disconnect between the developers on one side and the ops on another side. So that challenges from local developer environments to deployment onto production. And on your local developer environment, you may use base images that are coming from different sources with low or no security from using also different container registries. You may end up using Docker Compose as well. But on the other side, on Kubernetes or OpenShift, you need to use different type of base images. Maybe those have been created by your upstream. You may use different container registries and you will have some security constraints which will be enforced to the workloads as well. And then the way you configure the application to be running on Kubernetes obviously is going to be with Kubernetes emails. So in fact, there's discrepancies to go from developers environment to production but there's also discrepancies when there is a bug that is happening on production. And when you try to reproduce this bug on your developer environment. So as a result, there's an adoption barrier of the technology in this context. So with Spodman Desktop, we simplify the workflows and the experiences working with containers when you are targeting Kubernetes or OpenShift. In fact, we are bringing Kubernetes and OpenShift closer to the developers and we are also trying as much as possible to minimize the discrepancies between the desktop environment, the developer environment and the target Kubernetes environment. So we aim to bridge the gaps between developer environment and production so that when you are working locally, you have an environment that is as close as possible to production. And in fact, with Spodman Desktop and you will see that in the demo but you can start with containers and they can then be translated in pods natively in Spodman because that's what you saw in the intro from Valentin is that you can run pods with Spodman and in fact, Spodman also provide compatibility with other Kubernetes objects. So once you have these pods running locally you can then transition more easily to a Kubernetes pod. You can run that onto a Kubernetes local environment or into a Kubernetes remote that you can connect to as well. So Spodman Desktop 1.0 has been released a month ago. It provides capabilities to install and configure the container engine as well as Kubernetes local. You can install it and run it on Windows, Mac and Linux. It will provide capabilities to work with containers.  And it also provides capability to bridge between your local environment and remote environment. And we will see that in the demo just now, just now. So I'm going to stop presenting and present my entire screen. I think there we go. So this is the dashboard of Spodman Desktop. On this dashboard, you can see that you have Spodman which is running. I have access to the list of different images that I have been pulling in my environment. And if I take this one, which is an HTTPD image, I can see that summary, the story, and I can also run it. So I can, for example, just run it here and it will be shown in the list of containers that are running here. So I can access the container. I can see the logs. I can also access the terminal. And in fact, let's see a little bit. I have another container which is running. It's a pretty stack container. So there's a bit more logs as you can see. I can access to the terminal and I can actually interact directly with what's running into the container. So I can set up my key and I can do a get definition and boom, I have hello. So that's very handy. I don't need to remember what is a command that I need to do in order to SSH directly into the container. So that's already one capability which is pretty nice. I have also the ability to build an image so I can choose my container file or my docker file directly and I can build it. So here I can do create.io search, donation image and I can build my container. So we will see the image building and it's probably going to run in background but once I will have this image, most probably what I want to do is I want to push this image to a registry. So inside of Podman Desktop, you have the ability to connect to different OCI registries. Could be Quay, could be Docker Hub, GitHub, but you can also bring your own OCI registry so it can be an artifactory, if you want it can be any kind of OCI registry will be compatible here. So once the image will be built and I should be able to see it in a moment just here, I then have the ability to push the image so I can directly push the image on Quay. So it's going to take care, ah, I'm not properly authorized. So I'm going to just reconnect, move. Apparently I'm not able to connect. Oh, that's because I choose, here you go. I'm connected and I should be able to push my image now and if I go to Quay.io, I will be able to see my definition image. So that's Andy. Now what I would like to show you is a different setting. So as I mentioned earlier, you have the ability to configure your proxy and your VPN. You can connect your different registries as well. And you also have preferences where you can configure a bunch of different options for the tool. You can configure the size of the editor. You can configure the different options as well for the application. There is something which is a little bit interesting with the tool is that you also have the ability to run pods. So Podman provides the ability to run pods. So here I can see that I have already started some pod but I can also just take a Kubernetes Yammer for example and I can say, hey, I want to run this Yammer file with Podman. So I have this and I can see my pod running here and I will be able to also access to the container, access to the terminal. So that's pretty Andy. The thing which is also interesting is that if I have a container, I have this cube tab which gives me the Yammer that I can use to run this container in a Kubernetes environment. So that's also something that you can use. You can take this Yammer file and you can just apply it onto a Kubernetes environment if you want. Now I have an application. It's basically an application which is built with two containers. So it's my Python application. And if I click here, I will be able to see it live. So it's just a basic application which is showing how many times I have been visiting this website. It's connected to a release database that I am using as a cache. But what I want to do is I want to run that in the context of a future deployment onto Kubernetes. So I have the ability to actually take those two containers and to modify the containers. So I can take my two containers and run them as a group of container under the umbrella of a pod. So I can do that. And here I'm asked what parts I want to expose outside of my pod. So I don't want to expose my release database. So I'm going to do that. So what it does is that it stops my containers and it recreates them as part of a pod. So here you go. I have my pod. If I access here, I can see the logs of my different containers and I can see my different containers running inside of the pod. And if I click here, I should be able to also access my application. And you see the content is reset to one because it's a new start of the application in fact. So that's good. It's running locally just with Podman and the application need to go from containers to pod. Now there is something that we are providing within Podman desktop. There is a concept of extensions and extensions are providing capabilities to support other container engines or Kubernetes distribution. So what we did is that we integrate kind. So for those who are not aware, kind is Kubernetes in Docker. So it runs, it set up a kind cluster as a container running locally.  I can access the log and you can see that control plane either is starting to retake a few seconds. And I will have the ability to get my cluster running locally, storage case. I have my kind cluster which is set up. So when this is set up, I have the kind cluster which is accessible from the list of containers. And here I can see the logs of the cluster. But interestingly, I can also do cube cluster inside of the container and I can interact with the cluster if I want. So let's say that now that I have modified my application, I want to test it onto Kubernetes. So I can take this container and what I'm going to do is that now I'm going to cubify it. So which means that I'm going to generate the pod and deploy it onto Kubernetes. So I'm generating the Kubernetes manifest. And here I have also some options related to the services and I can create the ingress for my application. I deploy and now what it does is that it deploy my application directly onto my kind cluster. And in fact, if I want, I could have take this image and I could have say, oh, I want to push this image to my kind cluster. So when it will be done, I will have my application running onto kind and I can see it directly from here. So I can see the logs as well for the application. And if I connect to the port of 1980, I should be able to see my application which is running here in kind. So that's pretty cool. So from the from Podman desktop, I have been able to go from containers to pods running locally with Podman and now onto a Kubernetes environment. We are also providing an extension that allows you to run OpenShift on your local environment. So if you are interested by OpenShift, you can install the extension directly from the list of extension. And then when you configure the extension, you will have the ability to set up which kind of presets and which kind of OpenShift local machine you want to run. It could be OpenShift local with a single node cluster or it could be based on a on micro shift which is a little bit later as well and faster to start. So I'm going to just start it. So it's going to start from here and you will see that my Kubernetes context is going to switch from kind here to micro shift. So I will have micro shift on start here and I will be able to do the deployment of my application directly from Podman to micro shift as well. I think I'm running a little bit out of time. So I'm going to get back to the slides. So that was a demo for Podman desktop. So you can see that you can go from an application that is running in containers to a group of pods of containers running inside of a pod and then go to Kubernetes or OpenShift very easily in fact. The tool is free, it's completely open and extensible and this is by default. And in fact, the way we are building it is with different components. So on Windows we are using WSL for the virtualization stack, train you on Mac and on Linux of course it's native. There's a lot of possibilities to extend Podman desktop so you can add custom actions, you can add menus, different configuration, default registries, status bar and you can even extend the system tray if you want. But it's also providing the capability to support other container and join such as Docker, Lima or other Kubernetes provider kind and there is one which is coming for MiniCube as well built by the community. So that's also the different capabilities and how we keep the tool very open for everybody. In terms of future capabilities, we are going to continue our effort on providing efficient developer flows when it's about working with containers. So we will simplify the experience for onboarding especially if you are coming from Docker. So we will show you how you can configure the Docker compatibility which allows you to simply use Podman as a dropping replacement if you want. We will also have support for the native hypervisors such as Hyper-V on Windows or VFKit on Mac. On the Kubernetes capabilities, we will continue improving the flows for podifying. So turning containers into Kubernetes objects and then running those Kubernetes objects onto Kubernetes environments. We will extend the ability to see the different Kubernetes objects directly from the UI of Podman Desktop. And we want to simplify the transition from compose to Kubernetes. So a lot of developers are using compose today but they also need to run their application on to Kubernetes. So we want to help them along this flow. On the OpenShift support, you have an extension today to work with developer sandbox. You will have the ability to create your account. We will integrate an image shaker. So when you run a container on OpenShift, there's a lot of prerequisites in terms of security. So it's all about safeguards. And we will provide tools to help you making your image compatible with OpenShift. And we will continue our exploration to integrate MicroShift for developers so that we can provide a tighter integration with OpenShifter as well. If you are interested, you can find the links here. So podman.io, you will find everything we have been discussing today. There is also a book that is available on developers.radat.com, podman in action. So you can download it from there. And I don't know if we have enough time, but a big thank you. And if there are some questions, we are happy to answer them. Yeah, so thanks a lot, both of you, Stefan and Valentin, very great talk. I'm obviously a little bit biased, but I really love podman. Just in the fact that it has a very nice UI, like a very nice UI, and I love the integration with Kubernetes and stuff. Like it's really a game changer for me personally, but yeah, really great stuff. But yeah, let's get to the question. We don't have a lot of time left. One of the question was, does podman also work as a docker-composed drop-in replacement? So we are providing compatibility, which means that if you have docker-composed installed on your environment, it's completely possible to use it in order to run your composer files with podman. And in fact, inside of podman desktop, you have a way to configure that. I have not demoed it, but it's also possible to do this. Cool, great stuff. The other question was, is it possible to divine parameters like memory and disguise through a container on podman desktop? Yeah, you have advanced settings. So when you are configuring the container, you have some advanced settings that allows you to do that as well. Yeah. Cool. And the last question which has been advised was, is there like, does it also work like if you're using WSL, like the Windows subsystem for Linux, if you're using portman in there, does it work for docker-portman desktop as well? In fact, yeah, that's the way we communicate to podman. And that's the way podman is running on the Windows at the moment. So podman runs inside of WSL images and then podman desktop communicates to podman and Drain running inside of WSL. Yeah. Sorry to keep you. Sounds awesome. All right, so that's for it for the questions for now. Again, just to emphasize again, later on in our main stage, you can ask all the different questions you might still have, get in touch with all the Red Haters there and share whatever you have in mind. And even then beyond that, you can always reach out to the Red Haters and get in touch with us and talk about all the awesome stuff. So thanks to everyone until here, especially for Sivan and Valentin for this one and Maria for the last talk. We enjoyed both of them. And I'm going to hand over to Noel who is going to do the moderation from now on. And I am going to look into the chat and watch all the sessions from now on as well. So enjoy everyone. We have like a five minute break again and we'll see us like 15 parts. So thanks again, everyone. Thanks for having us. Thank you.


2-2 draw for Stevenson against Ferdinand here this afternoon. I'm Christian Taylor with head coach Dominic Dawes. Coach first and foremost your team went down 2-1. How are you able to find your way back in? I just thought as a whole we competed a lot harder today. We played a lot better today. And that was kind of you know a lot of what we talked about going into today. And we stayed the course. I mean guys stuck with it and we had opportunity to have a lot of chances and you know we're not not satisfied at all with the result of the weekend, but you know we played better today. We've seen in the past your team have gone down and you've even said to me your team needs to do a better job of facing adversity. Do you feel like that late equalizer is a sign of some successful facing of it? Again, I just I think we played better today. No, I think we need to be mentally tougher going into weekends and we need to know what's at stake at this point of the year. We need to learn to be a championship team and that's something that we have struggled with and we've talked a lot about. There's a lot at stake every night and every game is just as important. It doesn't matter who you're playing. And I think that was case in point yesterday. I think a little bit carried over to today. But there's no excuse to drop. I mean when we drop we got one point out of four non-conference games in these last few. Those are big games for us. They're big games for our our league and I think we let ourselves down. Well, it's the eighth time that you have played for Donia. You've seen them a lot and this is the sixth of now all eight matchups that this has found over time. How on earth does this keep happening with you? I mean, it's they're good games, right? That's that's why you play them. You know, they're they're good hard work and team.  The kids compete on both sides of the puck and you know, we knew that going on the weekend. I mean we talked about that the years past. I mean pretty much you said every game has gone to gone to overtime. So, you know, they're gonna be close and we got to be better on the details to get it done. Coach, thank you very much. Good luck next weekend. We'll see you in a few. Thank you. We're head coach Don McDaws. I'm Christian Taylor and go MustangSports.com.


So we're out here at Meadowbank again today. I've got a set of these Bronson Roars to try out and review and test. Really keen to get these bearings in because I've got a pair of G2s but I've had them for almost like a year now and they're pretty dead. I've cleaned them like once but they're still going strong. They're just dead so I'm really keen to see what all the fuss is about so make sure you stick around for the rest of the video. I didn't bring a tripod today so I'm just setting my camera on top of this wooden tap thing. Hope it doesn't fall. So yeah, Bronson Roars. They look pretty interesting. Here's an unboxing. I don't have a blade to open it with so let's hope I can open this thing to begin. There we go. What is it? Is that a sticker? Oh I've got a little sticker put on my work trolley maybe. Bronson Roar next-gen shieldless bearings. Shield-free design. Tongsten coated races. Boardable speed technology. Max impact cage. Deep groove raceways. Factory fresh quality. Made in China. Let's see what all the fuss is about. These were 80 bucks so 80 dollars for bearings. I'm not sure how much they go for in the States but in Australia these are 80 dollars. As I said before I have the G2s they're just really old now and they're pretty much dead so I'll probably keep them as a spare and might clean them up. Really keen to see how these go so I'm gonna I just dropped them all over the grass. That's not good dirt and grass in my new bearings so yeah I'm gonna chuck these bearings in and then have a roll around see what I think. They'll definitely be a lot better than the G2s. I kind of wanted to try the G3s first but I just jumped straight to the the Roars so yeah. Straight out the box guys. They look pretty flash. There's some riding around the lip of the bearing. I don't know if you guys will be able to see it. No. It says Bronson Speed Co Roar so they sound good. I mean Leon said for this same price I could have got Bones ceramics but I really wanted to try the Roars out today and I've been a bit of a Bronson boy lately. Listen to that. It sounds good. Sounds quality so I'm hoping these bearings live up to the expectations of everyone else saying that they're really good or had a few people say that they're not that great because there's no shield so dirt goes in the bearing straight away but apparently they made them shieldless so that dirt could travel through and not get stuck in but I'll be the judge of that I suppose. Pop this right off. I hope my bolts go back on because it's a bit threaded. Pop these on. My hands are going to be filthy after this. Don't give me spaces isn't it? These ones no. These are the G2's. I'm going to keep these but so I'll just put them to the side there. I've got no idea if you just stare into the camera or you don't know that I'll be sick. Just give them a smile while you do it. I'm keen to try these bearings out. My board's been so slow.  Are they Bronsons? Bronson Roars. Well these ones are the G2's I'm pulling out. Yeah look at the other ones.  I shouldn't really thought which are my front wheels. I don't think it's going to matter. We'll do a bit of a wheel alignment here. What way do you put them? I'll put my cases facing the outside. Like that? Yeah. But then it has a case on it. Oh no put them the other way. I'm going to put them this way so I look cool. Oh yeah they go that way normally anyway. I need one of those things where you pop. It's like a pop pin. No you just use the truck. Is that on? Yeah she's on. Is she spinning? She's spinning. Spinning and winning. Look at these coppers one. What do we say Jon? FT what? FT. FTC film the cops. You know the big less show. Mike Nolan. You alright mate? Having a bark? I don't bark do that. Gonna have a little roll around on these and I'll be right back with you guys. Tell you how I think these bearings are going to go. How's my speech? So these bearings are straight out of the box. No lube. I don't think you're supposed to lube them. I think they have a factory lube possibly. So first thoughts out of the box. They seem to like have a lot of torque so you can like push a couple times and then just roll. I want to see how far I can roll on these though. So these bearings feel pretty fresh. Pretty new. You've got to take into consideration the type of wheels I have. They're quite hard. They're not going to be the quickest on like tarmac and stuff through the park. They're pretty smooth. So far so good. I just really want to see if they live up to the price tag and all the hype as well so I guess throughout the day I'll be able to tell you guys. Pretty good session on these bearings. They weren't as fast as I would have thought. They would have been. I thought they would have been like whoa straight out of the box but they're not bad. I guess if you were to lube them up the lube would just fall straight out because there's no shields. So I don't know. Let's see how the rest of the day planes out. You're going to open this gate for me so look at this. Good person. Thank you. Got some chicken. Oh I see he was timid enough. Yeah he was fine. Look at the mullet on him. He's got a mullet man. Bold with a mullet. Like a middle-aged rabbit-o's fan. Next car. Next car. Next car. Look at this feed camera. Make it so you're pop-pop. No you got to be like on the road so they can see you. Yeah just be like behind the car. Yeah quick quick quick quick quick quick. How's the serenity? If you think about it Sydney's not too bad. Sydney's pretty cool I suppose. What's that red hot chili pepper song under the bridge? I think it's got under the bridge or under a bridge right now. So out of the box I felt like it took a little bit for these bearings to break in. They feel really good but not as quick as what I thought they would be but they're still pretty torquey. Like if you push a couple times your board roll for longer but overall yeah they're not bad I mean 80 bucks I would like to see how like bone ceramic go because they've got cases so they might be a little bit quicker I don't know. I'll tell you one thing though the Bronson marketing is on point that's probably why I bought these because the packaging looks so good. My opinion on these bearings I'll probably give them like a six out of ten that's just me though um I honestly feel like my G2s are a bit quicker out of the box compared to these ones but yeah just depending on the type of skating you do if you're skating clean parks a lot these bearings would be sweet because not a lot of dust and dirt can get trapped in them I kind of skate a little bit of both now street and park so I'm keen to see how they go so overall I'd give them probably a six out of ten. All right if you guys made it this far in the video thank you very much for watching shouts out to all the new subscribers if you are new here make sure you hit that subscribe button leave a thumbs up leave me a comment if you're not following me on Instagram already make sure you head on over follow me at enuckism make sure you're following evening mob on Instagram as well the upcoming drop is going to be on the 20th of September Australian Eastern Standard Time be sure to be following evening mob to stay up to date with all the details thanks again for watching the video and I'll catch you all of you all in the next one. Where are you boy? Where are you skate trainers bro?


Environmental surveillance of rivers and wastewater for SAR-COV-2 detection has been explored as an innovative way to surveil the pandemic. A recent study estimated the economic costs of conducting wastewater-based environmental surveillance for SAR-COV-2 to inform decision-making if countries consider continuing these efforts. The study found that the cost of environmental surveillance ranges from 75 to 72 per month, Blantyre site, and 756 to slash bin slash SH05 per person per year, Kathmandu site. The cost per sample ranges from 2, Blantyre, and 0 to 5, Kathmandu. The study also found that there are economies of scale for human resources and equipment costs with increased sample processing and sharing of resources with other activities. This article was authored by Lucky G. Anguira, Bhavna Sharma, Kabita Bay Trusta, and others.


We're just gonna send this as far as we can No, no Not this is not This is not good I'm trying to hold the wheel straight. Hello everybody. I'm Evor Ebbett. We're here on a set of Corsa In a no-hazze server for a bit of a force feedback challenge if you would say So we're gonna go driving in this tuned 1m If we crash this force feedback number is gonna get increased So every time we crash I'm increasing my force feedback. I do not recommend trying this at home We are on my R12 So this could get a pretty sketchy. So make sure you guys follow me on all social media all the time Subscribe box below. Let's get to it So we're initially starting off at a hundred percent And like I said every time we get into a major crash is when we are going To increase our force feedback Hopefully we don't end up breaking a bone or a thumb or anything like that once we get up into the really high force feedback So this is something I know a lot of people have probably done before But I decided I want to give it a shot here today That was that was that was almost a we almost died. I don't consider that a crash. I think we're good I'm gonna go down here. This is definitely Gonna get extremely sketchy as the force feedback gets higher especially if we were to crash with higher force feedback So we do have a little bit of gap here We got a pretty easy section right now We know it's gonna get a lot worse soon That wasn't that that wasn't crash There it is. That's gonna be it so that's That's a crash So we're gonna increase our force feedback by I'd say 25 All that oh man, that makes that much harder. It doesn't feel like it's gonna be too crazy bad right now It's giving me the crashing part. Oh, actually it's the speed variable too Like it gets a little bit stiffer in speed. I don't think we're gonna make that I Am really surprised we made that so at 26% or basically Over 26% higher than a hundred percent feedback on this R12 doesn't feel too bad yet. Oh That's gonna be it. I just do not want to hold on So that's another one We're gonna go by another 25% this is gonna get a little bit on the More sketchy side now. Oh geez get a little bit of room to run for that. We're trying to do this As far as possible Without dying you're gonna get that little bit of a gap right there. We're gonna shoot over here Yep, you can tell it's getting a little bit more intense with the feedback. Oh Oh, we're not gonna make that. Oh, we did. Okay Well, I Don't really want to keep going up higher in the feedback, but we're gonna keep going On 75 now. Yeah. Oh, man Yeah, you don't want to let go of this Art's well at 175% in the game. I don't want to crash already. Oh Geez That's uh Getting a lot harder to make quicker movements No, no, we got it. We're gonna make that. We're gonna make that. Oh, I don't know how we made that There's like very little sections of paths that we can take I Don't know if we should have taken that But I think we're getting this now. I don't think we're gonna be Up in the feedback much, but this is definitely an arm workout right now. Oh No, oh Okay So we're gonna be going up to 200. I don't know how this is gonna work. Oh Oh That is We're peaking our force feedback in our game and that's making it extremely hard to turn So I'm not really sure why my game decided to want to freeze my wheel cam and then crash We're back at 200% and we're gonna see maybe that's what crashed My game where at 200% force feedback as you can see we are Definitely peaking our for our Wheel just by doing minute little movements. Oh As you can see Just doing normal turning to weave through traffic is peaking. We're gonna get a little run room here So definitely would not recommend trying this. It is quite Quite scary to say the least Because the moment we crash The moment we just need to let go of the wheel like that. Just let it go so we don't die All right, so now Since we crashed We're gonna keep going We're just gonna go up by 50s now So we're at 250 now. Oh man Like I said, just barely turning it. We're already peaking the feedback. I don't consider that a crash We're gonna keep going. Oh, man So if you guys want to see more funny stuff and stuff like this here on the channel Let me know down in the comment section down below. I appreciate all the support It's really wobbly at speed Yep, that Audi is just staring at us. I don't know if we're gonna we're just gonna go 300 We're gonna go straight to 300 We're gonna go send Maybe the lap. Oh my god. No Maybe the last level we go up For today's episode. Make sure you guys follow me on all social media all this front skier spot. Well, oh Yeah, there's there's no way If I just let it go just a little bit this wheel wants to go crazy So It's always I appreciate you guys to come back and watching make sure you guys sub the channel appreciate support got some Thing brewing in the works for all you newer drifters That are trying to learn So make sure you guys subscribe to the channel and Hit that bell notification. You guys won't be the first for the videos when they come out As always, I appreciate the support. We're just gonna send this as far as we can Not good. I trying to hold the wheel straight I don't know why we haven't crashed yet. No No, we're dead. We're dead. Now. I'm just gonna let it go.