You need a financial advisor with the freedom to focus on your specific needs. Whatever your goals, Reed Potter can create a game plan tailored to you. Call Reed at 432-0777 at Pikeville, Kentucky to learn more. The Tug Valley Chamber of Commerce and Williamson Park and Recreation are hosting a summer arts and crafts market as well as the third annual Young Entrepreneurs Day program on Saturday, July 16th. From 10 a.m. to 3 p.m. at the Williamson Fieldhouse. The Young Entrepreneurs Day, like I said, it's our third annual event. It's basically an event where youngsters in the area are able to set up a business for the day. So we'll have, I think, nine kids there this weekend.  In addition to Young Entrepreneurs Day, where children have the opportunity to run their own business under the leadership of a Chamber of Commerce member, there will also be the Arts and Crafts Market. The Chamber sponsors and hosts several Arts and Crafts Markets throughout the year. And as I said, this one is running in conjunction with the Young Entrepreneurs Day. And I think we have just over two dozen vendors at this show. Most of them are local, I think, but we do have one vendor coming as far away as Princeton, West Virginia. And so you'll have a lot of different arts crafts, homemade jewelry. Just all kinds of really neat stuff. We'll have gourmet food that is locally sourced. All kinds of neat stuff there. Young Entrepreneurs Day and the Arts and Crafts Market are free for anyone to attend. For more information about the event, visit the TVCC Summer Arts and Crafts Market Facebook page. For Mountain Top News, I'm Kelsey Dean.


Hi everyone, Joe for jaspyscasebrakes.com. So not everything went, but we were feeling generous, Nick was feeling generous. We got within a handful of brakes, so we're still going to give away a little bit of money. We're not going to give away the whole boat, but we're going to pretty much cut it in half and still give away a little something, better than nothing. So we've reconfigured it where spots four or five and six will get $25 of brake credit to jaspyscasebrakes.com. Spot three gets $50, spot two gets $125, and the top spot gets $250 of brake credit. Just as a little, a little thank you to everyone who got into all of the brakes today. So every brake that filled and that I broke today counts, right? Prestige pack three, contenders 12, Chronicles 797, Blaster 2, 798, Noir, Donner's Optic, Prestige pack, NTSocker, Prestige pack five, Sterling two, the Sheriff mixer, Choice four, which unlocked the Fishing for Trout mixer, the Certified Picker team two, the Premium sock filler brake, and the Donner's Optic football number nine. So that's 500 people on this list right here. See that number right there? 500. But hey, I appreciate everybody getting in. So let's put all the names here. Let's roll it and randomize it four and a three lucky seven times. Good luck. One, two, three, four, five, six, and seven. And final time. There we go. Four and a three, seven. There's seven right there. Hey, big thanks everybody for getting involved. It's always nice to do what you would just normally do anyway. Join a few brakes here and there. And then maybe stumble into a little bit of brake credit if you're one of the top six. So all the way up to spot seven, Kenny, sorry, just a little short, but congrats to the next three. One, two, three, right, four, five, six, some brake credit, Capola, more brake credit, Andronic with another bit of brake credit, Brian, and then Mark with the most brake credit. So let's match you up with what you got. Boom. There you go. Mark, 250 bucks of brake credit going your way, Brian, 125 bucks, Andronic, 50 bucks of brake credit, and Capola, Evan, and Ian with $25 of brake credit each for doing what you normally do. Just join in our brakes in supporting jaspeyscasebrakes.com. Thank you very much. We'll be emailing that to you after I go off and I'll probably do it from home. But I'll email all these brake credits to you at some point tonight. They'll go to your email. It'll show up as a gift card code, check your spam folder if you don't see it. And if you have multiple email addresses that you order from, check all of them because I'm just grabbing whatever I see first and then sending it to them. All right. There you have it. Congrats to all. Thank you to everyone. I'm Joe for jaspeyscasebrakes.com. Have a great night. I'll see you tomorrow. Bye-bye.


Keep the control now, he's on the next day as well. Yeah, just come up on that. Are you all right? Good run? Yeah, apart from the late start, it's always it's our fault. Other than that, we made up time, we were about an hour late, so we were half an hour late, half an hour late into your week. Yeah, we're continuing the circumstance, and having a good run. OK, we're not going for diesel to take us back. Sorry? Just staying up there for diesel. Yeah, you're right back up here. You OK? You see that? Yes, it's Julie's phone. We're in your two and three times. Yeah, we're coming up again on Wednesday. You fancy it, don't you? Children, do you know what those yellow rings on the left-hand side here are for? They're the letter H. Can you see them on here? Tren, do you know where Tren was at? It's not a Tren. What's the choice? Tren truck wasn't there? No, Tren, that's all right. What is it? What flies? Helicopter, well, Tren. Very good. Have you seen the windmill up on the hill on the left? Yeah, look, see the windmill? We've been there, haven't we? We've been in there, haven't we? Oh, the water tower as well. Oh, the water tower. Everything is here. Oh, the water tower. Oh, I think there is. A full-time tourist. Well, absolutely. Your city's new football pitch no more. All right. No more. No more. No more. Yeah, sorry. It was never new to me. It's not new to you. It's not new to me. It's built out of water. It's built out of shops, and then built out of it.


Welcome to part three of the Habitable Zone Unplugged, a four-part conversation about exoplanet science with Dr. Robert Hurt and Dr. Johanna Teske. I'm Calico Field. So in this series, of course, our explorers get to travel to these exoplanets and look down on them, and that's how they know what the compositions are. In 2018, we're a little more earthbound. So how do exoplanet scientists actually learn about the composition of planets now? Right. I would love to be able to go and travel to an exoplanet, but we can't do that at least not yet. And so one of the fundamental measurements that we used to guesstimate the composition of exoplanets is their density. And so the components of this are the mass of the planet and the radius. And with that, and assuming it's a sphere, you can get the bulk density of the planet and match those measurements to theoretical compositions, potential compositions of the planet and know whether it seems more to be iron-rich or is more like earth where it has a mix of rocks and iron. The hard part is that measuring the radii of small planets, we have gotten sort of good at that. But the masses are still really hard to measure, especially for stars that are farther away and thus fainter. And so right now, the population of planets that we have the measured bulk densities of is actually still pretty small. Actually, one of the things that they do in this show is because they do get to stand in the system and fly around, it's more like how we investigate our own solar system than the way that we have to be more creative in understanding what things are made of around other stars. But in the story, one of the things that they talk about is how once they get into orbit around the planet, the cast is able to tell you what the mass is. And so this is sort of getting at the idea that it's really hard to figure out what a mass of a planet is without seeing how it affects other objects around it. So if we just see a planet around another star, we might not be able to make that measurement easily or directly. But if you're actually there in the system, you can go in orbit, then that's how you would make that measurement. So they have a much easier time at figuring out what the planet density is. But what about looking to the future? What are you really looking forward to in terms of what you're gonna be able to learn about the composition of these planets and maybe their habitability? Absolutely, yeah. So one of the main missions that has helped detect a lot of exoplanets is the Kepler mission that was staring at one patch of the sky and looking for signs of planets around stars. But that type of measurement gives you the radius of the planet, whereas measuring the mass, the instruments that do that are all based on the ground. And so it's harder to get that type of measurement for a lot of planets. One thing I'm excited about actually is that there's a new NASA mission called the Transiting Exoplanet Survey Satellite or TESS and combined with that mission, which will be serving closer by stars with another instrument that NASA's building for one of these ground-based telescopes, then we should get a larger population of small planets that have radii and masses measured than we can know their densities. So water is something that comes up in the episode and that's obviously important for humans if we want to go live on a planet. Can exoplanet scientists detect water on exoplanets now? Right, so I talked a little bit about measuring the bulk density of a planet and from that you can say it might have this percentage water somewhere on it. But what we're really interested in is surface water or water maybe in the atmosphere. And so there are a couple of different ways that we can do that. One that's been used, at least so far, more on giant planets is what we call Transmission Spectroscopy, which is if you're the telescope, the star is here and the planet comes between you and the star. The light from the star filters through the exoplanet atmosphere and in that process a fingerprint of the composition of the planet's atmosphere is left on that light. And so that's one way that we can know whether there's water or methane or sulfur in the atmosphere of that planet. The other technique which future NASA telescopes will hopefully be able to do is measuring the light that comes off of the star and is reflected from the planet. Planets themselves don't radiate enough light for us to observe, but they get the light from their star and we can observe that and know then whether it might have surface liquid water. This actually came up with the script too because in a very early draft that I circulated I made reference to, I believe Kara made a comment that the telescopes were looking at the light from the planet and detected water but they didn't yet know that it was ice and one of our exoplanets scientists caught that and said, by the way, if you're looking at scattered light from the surface you would already know that that was in crystalline form because it would have a distinctive signature. So we changed the dialogue to reference looking at the atmosphere of the planet. They picked up the vapor in the atmosphere but they don't get to see it until they get up close where they actually find the crystalline form. We wrap things up in our next video by talking about the kinds of life scientists want to look for on other worlds. Spoiler alert, it's not just human life.


All right Good morning everyone Welcome to my talk from cloud native to cloud native. My name is Max Körbecher And I'm co-founder of a company called liquid reply. We're based in Germany and actually help our customers to implement Kubernetes platforms actually everywhere So we have edge use cases running in distributed environments going all the way up to cloud providers and even scale them throughout the globe So running on multiple continents and multiple different regions and so on So am I daily work? I most of the time are more Yeah, giving some consultancy and advisory and try to answer questions from the customer What is the right way to do my Kubernetes? How I need to configure it correctly? How I bring my teams to Kubernetes and how I make them actually use of it and so on and I need to give you a little warning for today because it's like not like there's one technical problem And there's a technical solution for it or we're talking about processes But we are speaking about something which is some way meta. It's in in between There are some technical components. There are some kind of processes, but there's a lot of Yeah, this the thing which in a company glues the team together, which is the reason why for example One team is successful with migrating to your cloud and getting cloud native And while another team is maybe not that successful And this is something which we try to find out today and where I will give you our perspective of multiple projects with multiple Customers and what we have recently seen in it and what is our observations on it? And we will also find out what you can do to actually maybe not Stack somewhere but can move forward get some light speed into it and even being successful So the thing is nowadays. It's super easy to go to a cloud You just need a credit card. It doesn't matter if you're an enterprise a small company person startup The entry boundary is very low and it is also fairly easy to use you can Just click your things somehow together or if you get more techie you can build your pipelines You can use some declarative formats infrastructure as a code and so on and so forth But it's very much about you to understand or to Yeah, decide if this is more like a one-way flight ticket through the clouds and then you somewhere will get stuck Maybe or if this is the beginning of a cloud native journey something which lasts long where you have a long time Business visit which will be the foundation of a lot of your services and implementations for the future So I give you a short time to read this beautiful dear bird And then we will proceed on why is this is so true? So the point is this is something which I have at least once in a month as a discussion with a customer It's like I have this and that problem. I need to solve that and that Can we not just containerize it and bring it to Kubernetes and the world is beautiful? Well as someone who is consultant for Kubernetes I would love always to say yes, and let's start a project who will help you But the truth is it's not always that easy because the technology can solve just one half of the story Sometimes even just one-third of the story But there's way more around which you need to be aware of Before you can do anything with a cloud native and before you can become cloud native So we always see there some kind of pyramid and The foundation for this pyramid is actually the way of thinking your methodology Maybe some engineers between you will say like hey, but what is with the infrastructure and we come to that later But the foundation for a cloud native transformation for a cloud native journey Doesn't lie in the first step in the technology itself. It is all about How you are thinking about it and what do you want to achieve with it and how much you are interested in it? Because the cloud native space is moving so fast if you're not interested in it What you will learn today is outdated tomorrow And this is something where you need to stay with your mind and be ready to to keep along with And then another part is the internal developer platform This is what we often put together. It's most of the time based on Kubernetes It allows us a lot of automation But it is more about the extensions which are implemented around which helps a development team from the Software development perspective to speed up and show integrity of the system and show the Security that everything is fine all the way into the production. And then we have something Where I always have a little bit difficulties to name it on the one hand side is the business requirements And on the other hand side at the application development Not every business requirement is a reason for developing a software which is cloud native and sometimes it would be even more expensive to go this way but It's often a good option and you should be aware of evaluated and take a look for some points where you was like well Maybe we can support here will business was building something based on microservices which is fast which can be Stateless and so on and last we have the infrastructure And the infrastructure is very interesting because from a customer perspective the pyramid looks like this The infrastructure is a big enemy in the end It's something where all the complexity lays and all the costs are somehow hidden and it's maybe scales up and down and do Weird things and then you have hundreds of regions and hundreds of services and so on and so forth But that's not the biggest problem Nowadays you can define and describe everything human readable and you can automate everything of it Yes, you need to learn about it, but Well, we also learned how to walk we learned how to speak we learn how to cook So as an engineer as a technician you for sure are very fast able to catch up what's going on in club provider and what you're able to do with it Our perspective of the story consulting major enterprises is It's all about the mindset. It's all about how the teams and the people think about to implement cloud native And how really to Yeah succeed in their journey If you're not interested in modernized your application Maybe rebuild it from scratch into smaller junks Then you will not also go the way to do something cloud native because you miss already one of the foundation and The other thing is cloud native also doesn't mean that you need to go to the clouds You can use cloud native principles wherever you are as that we build micro clouds on the edge They're totally disconnected from any kind of internet Or we scale it full up But the principles behind it are still the same counting for everything on the cloud native environment so this is a very Common picture if you search for like what is actually cloud native and you will found this and that and yada yada yada The thing is this is all unimportant because it doesn't matter so much what is written on the left side or on the right side Because depending on where you are in your integration in your step of engineering It can be true also for the other side But very important is here the mindset again and you will hear this work a lot today But it's one of the key factors when we are talking about out a cloud native transformation And we were talking about getting teams into a position where they are able to build platforms Which are ready for the future which can adopt with continuously updates and changes and replacing integrations So let's talk about a few observations something where some of you maybe will find yourself Where some of you will say well, this is an obvious one and Some of you will maybe say like well, we already passed this by but it's exactly the story which I had The first thing is and we're still discussing it. We're just quite confusing after many years that Companies think you need to suggest another hypervisor So like the ember comparable or sx v-sphere this stuff But this is absolutely not true Kubernetes is a platform. It is something which helps to build your own platform Or if you want to add one another platform, you can say it's a platform to build cross-platform platforms What it means like you can build was one solution something which runs the same way on your Virtualized infrastructure on your bare metal and then the cloud provider giving your developers in the end the same experience And Kubernetes is a system to manage. It helps you to manage your workload. It helps you to manage your Resource and extensions of the resources which you can use is enriches enrich this actually And it runs your application, but do not misunderstand running here as like a hypervisor again Running just means it takes care about all the complexity around about security about networking about authorization All those heavy liftings where you normally have already a year-long project for it if you want to set it up in a classical infrastructure and What you all see? Kubernetes is often treated as a one-time implementation and this is no joke We have seriously some customers where we've re-implemented Same kind of platform in different shapes on different cloud providers But where you really should take a look on and where you should think about it if you build a cubanita's platform Then you need to continuous available team for it a product to someone who is listening to the end users development teams someone who is listening to what is needed in the future and Also who is part of the community because the cloud native community around kubernetes and all the other tools You're using is moving so fast That you need someone a whole team for it to keep track of it on the other hand side if you do it well You don't need much more than that for operate your infrastructure If you're doing it good you get also a lot of benefits out of it Even so the workload in the beginning looks tremendous and what absolutely doesn't work is if Like myself in the past I was an enterprise architect and I draw beautiful blueprints and run to the teams like look This is the the solution for everything and blueprint, you know, it's like a recipe you follow it But it's not a guarantee that the food in the end is good or tasty or that you like it Because what is often not written in some kind of blueprint is your how you spice it up the salt and pepper You which you need to add or maybe the chili if you like and the same as was blueprint it's not a solution and it will not help necessarily your teams to succeed when you move to a cloud and Especially not when you want to get cloud native So your platform team which builds a platform also needs to be trained be good in communication and help others like an internal consultancy to understand how this platform works and I know that a few people here from companies we work with and they tell me all the time the same story I'm my workload is so much not because I have to implement something But because I have to consult the people to adopt my platform But it's a very important point and then finally one of the biggest things the most applications which we are seen They absolutely not made for being microservice oriented and most of the time also not optimized for running on kubernetes When you take a look on the cloud native survey, it's quite interesting because for example in Europe. It says like Something between 17 80% of the companies a major enterprises using containers and cubanitas But the other way around when you take a look on the cloud native developer report There's only 27 of the people who are answered telling that they use actually cubanitas in their everyday life and There is a very big gap in between For sure you want to help on the one side that no one needs to understand the full ecosystem of cubanitas and not needs to understand the 500 600, I don't know how many open source projects out there. It's not yet hugged But you need to understand the foundation of cubanitas to actually build software to run on cubanitas And we will come to this in a while So how we can stay on the cloud native side if you do cloud journey if you migrate and If you want to change our mindset Well, the first big thing is you need to be more like assertion When you do a cloud native transformation, this is not about coming with a very big hammer Just slash the wall out and move everyone into the fresh air and start somewhere This will often not help Because it's overwhelming it can leads to frustration.  You do not understand the people You have absolutely nothing where you can rely on and then someone says like well now Let's build a successful business here within the next three months And I would like that it's adopted by millions of user till the end of the year for sure when you work hard You have a chance to succeed But it's a human nature on this point to say like well, that's a little bit too much for me at this point and This will not help you So you need to be very precise you need to find the people in your corporate Who are already interested who have this drive this motivation this interest? It's maybe the young guys and girls which are here today Which are convincing their bosses their leaders to say like I need to go to this conference I need to understand what they are doing. I need to talk with the people and These are the people you need to find within your companies bring them together and give them a new playground And yes, it's really a playground There should be no rules They should have whatever they need whatever makes them fun to develop their skill set and the capability To build a platform to build a platform for your companies and to build the foundation where you can get truly cloud native so start by zero is A very important factor and I know companies do not like to hear it But the truth is if you're an expert in chemistry The chance that you will be a digital expert in chemistry is quite unrealistic because this is not your expertise The expertise is somewhere else. It works in the past. It will work in the future What you can do with digital services is to enrich your capabilities. You can make your product better faster more transparent But it's not 100% cloud native and that's why it's also sometimes doesn't make sense to compare a major Engineering company with something like a Netflix or Spotify because they have a totally different past The one is cloud born. They started with this was digital services They know all the pain and I mean meanwhile those companies are very old. They're not startups anymore and You have exactly the same experience, but with your domain with your with your specific knowledge So to make the step from the one side to the other side You need to first I don't want to say get rid of but at least try to ignore your past and get this Playground where you can do whatever you want to do and I before had you even a line in it saying like well Ideally you get rid of your CXO whoever is taking care about this department who's taking care about your money Who's taking care about some guidance and rules and whatsoever? So that you have really something where you can build from scratch and there's no one annoying you no one telling you Oh, this doesn't work in our industry or this doesn't make sense for our industry Because this way of thinking is not the way how it helps you to build a cloud native environment So again the mindset makes a difference strategic wise customers also often choose cloud provider by money and From an economical perspective I can fully understand if I can save 30 million on the one to comparable to the other one where I'm currently running It's maybe very attractive But often it doesn't make sense for example to migrate from the one club provider to the other For which reason you want to save 30 million euro But you need five years to make rate all of your workload which you have before built up already You need to retrain all your employees who know the one club provider to use know the other club provider and Even you if you don't do this whole long story and you start by zero you maybe should start by Taking a look about the technical capabilities of the cloud provider first Because there's nothing more frustrating and more slowing down the process to adopt this kind of technologies Then when the technology doesn't work Because you cannot change it if you want to implement something in the cloud provider doesn't provide it to you you have to wait or you have to wait to build it by your own and We see this quite often as one of the reason like okay We are going there and there it seems like it's a cheap but good resource for us They can do on the paper what they all club other club providers also can do But then the project takes three months is longer and you need five more people and then comes some deadlines And you want to go to the production, but this service is actually not available somewhere else So when you do this you should think from the beginning about what you will need technology-wise so that you will not get the pain in the end and Maybe and I'm pretty sure in it You will also lose absolutely no money even so like another solution maybe costs a little bit more No panic. You don't need to read it. It's just for wrapping up for someone who wants to read the slides later So when we moving a little bit more to the perspective of developers like the people who needs to build something What we experience is that quite often? Suddenly nothing works The CICD fails the git repository is not available. We cannot push something. We cannot document something and This is because resources are often saved on the development side Nowadays if something stops this is higher automation, which we normally built It means that we even cannot fix anymore anything in the cloud provider for example or in the platforms you build somewhere so the infrastructure which we use for implementing is Getting very very critical and it needs to be treated like this. It's the same like I Do not want to say your major application which brings you all the money But it's very much comparable to it Because if all the development tools fails It's getting very difficult to fix something which is maybe running in production Another thing and I mentioned already earlier. We see projects are often Timeboxed obviously you get a team 10 people five months as you build the platform goodbye This is how most of the project are working and this is normally fine If you build something which afterwards is not going to be changed so much But this doesn't work with your internal developer platforms for example based on open source or cubanitas Because we have major releases every three months Is and if you have just a default stack on cubanitas running you actually needs to do every day For example an upgrade Sure, you can model it and do it maybe once a week or every few weeks But in the end it's a few hundred updates you have to run and this is just the maintenance side You maybe have discovered this week a lot of new technologies a lot of new projects a lot of new products Which you want to use which you want to integrate Who should do it if you just give your existing cluster to an operations team Who is busy and most of the time do not have enough people and to keep your cluster alive And then you come like look here's a cool product. This will not work Because internal developer platforms When they build right are the foundation where all of your future board projects are running on and then this is something Where you continuously have to work on where you continuously have to adopt it implement new features Extended and it's getting very critical for you. So you need to treat it like a life-long living Product it's nothing which you just build and put into the corner and give it from time to time some water it's not a Cactus or something like that which just needs a little bit water and love from time to time and Last but not least and again, please don't read all of these It's just to show you that there's a lot of patterns for example in the cloud native environment These patterns must be understood And you need to train your developers But you need to train also your platform engineering teams to know exactly when to use which pattern and this patterns are often old but gold a once got asked from from a Engineer like you come with pattern. How old are you you were enterprise architect in the past like yes I was but you know, it at least helps you to understand how the things should work Because what we also see very often is that for example a conflict pattern is used as a database Theoretically nice for development, maybe okay But this is absolutely not the way to go if you would like to really use it because what also happened and you maybe Know it when you have implement once something. It's very hard to get rid of after a while it will stuck forever there and We have seen there are a lot of dirty and shady things Sidecar patterns which communicate in the wrong directions Demon patterns for distributing application for high availability It shouldn't be there not in this way So to wrap it up from the development and product management perspective if you focus so much on the IT on your teams on developing your products projects Then you also need to give the right priority to the tools around it and to the education around it Do not appear from nothing and we're not just come out of the air. It's just don't happen but if the expectation is that it's somehow between a full week of Deployments and fixing some stuff and maybe get an error done in the production stage To find then for example time like today on a cubicon or this whole week on a cubicon It's not possible if you're not actively push it if you do not make the room available for your teams to take this time to understand and to learn and Obviously, we also need to talk about Kubernetes because that's why we at least partly here and This is very basic, but it's so often done not right Just get your security in the beginning of your projects already implemented We just a few weeks ago finished a project where we had to re-implement all the security mechanisms and it's a hell lot of a work and It's nearly impossible because the output is like well if I activate now this around 120 microservices are just going to die was in one second and it's such a amount of work to fix this but if you have already the Right processes around it for our bug and security And for network policies in the beginning of your implementations You will have in the long run never ever a problem because the people understand how it works and the fun thing is that Security with kubernetes is super easy It's not like in the past you need to start fiddling around make some profiles and Harden somewhere your server for sure platform team needs to harden the server, but from a development perspective you don't have to do this and If you mess it up then in long run you will get some pains with it before you go into production This is what we often see development phase or good Testing phase also everything fine, and then it hits production nothing works and not because it's production but because suddenly you have security and network and Role-based access control which prevents that your services execute like you have done it before and on the same layer is actually also the even more simpler things Like probes startup probes for example or readiness checks health checks We see so many services even from open source project sometimes which do not have any of these implemented The fun thing is if you have this implemented It is the only thing Which guarantees that kubernetes will fight you so hard to shut down any kind of services So it's super important if you want to build the software which is reliable and highly available and in the past You also call it self-healing But if you do not have it in place kubernetes would just raise the hand and say goodbye to your service if you have it in place kubernetes will fight like a mother cat for their children Until everything is done and ready and finally we come to the master discipline Multi-cluster single cluster one cluster for everything one cluster per application Actually does not matter so much which way you go you should not choose one of the extreme Not one cluster for everything but also not one cluster per application But everything in the middle is somewhere right you can cluster your applications based on for example departments Everything what does sales everything what is for your production line? for example or for criticality Maybe it's not the best thing to put everything what is highly critical on the same cluster So this maybe you should split but for everything else you can layer it a little bit up and As long as you have a good automation in place and you take care about that everything runs smoothly The approach is absolutely Unimportant a good Some pool for it is the less scripts you have implemented in your CICD pipelines the better it is Because every script is a single point of failure every script is basically calling That you maybe do not handle any exceptions and that your whole pipeline will break in the state Which you do not want to have stored somewhere so less sometimes way better it must be easy to use and You always should first take a look that you build something which is really useful But which is not like having 500 features where you just use one out of it Because sometimes this very complete platforms have 499 features which sometimes can cause issues for yourself And you do not want to maintain something which no one uses right? So the most important thing itself is just do not over engineer Don't do it. We have seen companies which built their whole own operators to do something while there was another operator available if you're unhappy with one of these solutions you can go and contribute for example, it is way more easier and Companies in this point are often a little bit. Yeah worry about their intellectual property The thing is we do not build any business logic into the platforms. You do not sell any very specific knowledge of your industry to it But you can solve the problem for yourself for your other teams and Maybe even for companies which you are actually very close with Companies which deliver parts to you companies which deliver components to you or where you deliver things to so Don't do it yourself If you have problems with intellectual property, maybe sort it out how you as a company can also contribute to open source So that's makes it sometimes easier to fix problems and To get the things done and write for yourself and to conclude For the cloud native journey and where you're heading to You do not need to reinvent the wheel as you have seen today There are around six seven thousand people just here and around nine to ten thousand people online Just interested in exactly the same things like you are interested and they're running around so many experts in this fields Which have solved already those problems? So why not to catch them up discuss with them bring your ideas to them? And maybe in a few weeks in a few months this feature will appear in one of the open source projects keep this thing simple as Said the over engineering is sometimes killing projects from the inside because you increase the dependencies and nothing works anymore and Everything's lost you want to bring in new people, but they need to months is to get on board it The months is to understand what you have built and then you hinder yourself to move forward and obviously Design and build for change You need to adopt Changes within the environment you need to be able to accept changes and to go with this changes And you might be sometimes even need to be able to handle that different platforms have different needs But the good thing is it's not magic nowadays, and we see a lot of solutions which can help you to do it so thank you very much and If you have some time come by into our booth and have a talk. We are happy to talk with you


What's going on guys it's your boy DPJ here today with another Destiny video only today's Destiny video we're gonna take a closer look at the recent Destiny year 2 trailer that was just dropped by Bungie. In this trailer we seen some very exciting points which I feel I need to cover in a video I'll link the whole video in the video description if you guys do want to check it out. Okay getting straight into the video the first interesting point comes 14 seconds into the trailer where we see a Titan warlock and a hunter running through the dreadnought. What's interesting here is all three guardians are kicked out in their own certain faction. From top to bottom the warlock is in dead orbit gear including weapons. The Titan is kicked out in new monarchy and the hunter is in that future war cult. The Titan if you look closely is holding a new monarchy themed Su-Ross Foundry weapon. The hunter is holding a future war cult themed all-molan hand cannon and the warlock has a dead orbit a mollum weapon. It's hard to make out at first what weapon a warlock is holding but for a brief second we see the a mollum liquid ammo indicator on the side of the weapon. Whether or not this confirms faction weapon shaders or not it's hard to pinpoint because as Ms. 5000 what's pointed out to me on Twitter maybe a mollum Su-Ross and hacker could offer faction weapons themselves. Who knows you're just gonna have to wait and see. Okay moving on to 18 seconds into the trailer we see a hunter in the character menu. We can see this hunter rocking that sexy blue rare armor looking quite good to be honest. You can also see the artifact at the bottom right and you may also notice his guardian is a level 40 but has only 214 light. This is obviously because of the armor he is wearing. It also clears a few things up when he hovers over the light level. It reads your light score which I'm guessing is how we will refer to light level from now on. Your light score is an average attack and defense values across all of your currently equipped gear. A higher light score improves both your damage output and your defense. This does leave me thinking though if you can have such a low light score at a high level the highest level being 40. Can you be a low level 30 for example and still rock gear which will make you equivalent light score wise to a level 40. This meaning your defense and attack value will be equal to that of a level 40 when you are 10 levels below. This my fellow guardians is something I believe we will find out tomorrow when they stream. Another little addition they have added is the feature to see your weapons damage types by pressing our 2 or left trigger.  Here we can also see a blue rarity ghost. Now it has been confirmed that vendors will sell legendary ghost shells but it does make you wonder how you'll come across blue ghost shells. Maybe they'll be rewarded from earlier missions. Who knows we're just gonna have to wait and see. Moving on at 20 seconds in we see this incredible looking future walkout ship. Hopefully this design and ship model is exclusive to your future walkout because they don't have much else going for them let's be honest. Moving on 22 seconds into the trailer we see shacks obviously from a hunter's standpoint. We get a basic description here of how you obtain legendary marks which take over vanguard and crucible marks I believe. You can also see that shacks has legendary ghost shells. It doesn't say it doesn't say what's needed in order to obtain them but I'm guessing it won't be much different from the armors. We can also see he offers three ranks or he has three ranks. Within the first rank rank one he offers gauntlets, leg armors and class items. Rank two he offers well we can see ghost shells I also believe that's a chest armor but it's hard to make out. Rank three offers helmets. Now I'm guessing it will be the same across the board for all characters. Now moving on at 24 seconds into the trailer we see the end of what I believe is their new strike playlist. I think the strike playlist is called vanguard ursa. Now I am led to believe this because of a gaming former feature a couple days back where they did mention this new strike playlist and how it would reward us guardians legendary marks and engrams and as you can see by the feed it seems as though this is what was obtained. We also get a closer look at the future workout or moaling hand cannon which looks pretty sweet. Now moving on we see the quest menu which I cannot wait to have a better look at. We can also see that there's 16 bandit slots now. Six more than our current 10. Another thing which I noticed from this snippet which I also spoke about earlier in the video is how this dude is a level 30 but his light score is 320 which is higher than the light score. We saw the guardian who was a level 40 at the beginning of the video which sort of answers my question but not completely. Moving on pause at 27 seconds. Now I have not noticed this before and you can call me a noob but is the hammer of souls hammer really an eagle? Looks indeed to be that way. This could be based on Roar the Egyptian sun god but it also ties into the Seattle Seahawks. Seattle is where Bungie's headquarters is. Who knows? It probably relates to both. Now moving on at 28 seconds into the trailer we see the acceptance of the future workout allegiance which once accepted is I'm guessing where most your XP will go towards to level up. This is what they meant when they stage you can wear any class item you want but your XP your rep will go towards the faction you choose if you choose one. We can see cost 2,500 Glimmer to join an alliance and you can only change once per week. Moving on another second into the trailer at 29 seconds into the trailer we get a better look at the new monarchy theme Sue Ross Foundry weapon which looks absolutely incredible by the way it really does. Now at 33 seconds we see a few new features on screen such as Shader Collections, Arms Day and a level 25 character boost which will be the boost new players or if you create a new character this will be the boost you receive to allow you to jump to that level 25 so you can jump straight into the action with the Taken King if you don't want to run the story from the start. Which is a good addition to be honest but I'd still want to run it from the start. Now moving on and we get a look at the exotic blueprints vault which is something I spoke about last week when they spoke about Shader and emblem vaults I thought it would be pretty epic for there to be an exotic vault where you can keep all your exotic weapons and armors so we get that extra space in our initial vaults and it seems as though that is what's happening some interesting points here though let's start with your year one primers it's clear these are weapons we currently have but why do we see some of the same weapons in the year two primary slots with upgraded icons it's clear on the bottom row of the year two primers we have the last word the Hort Moon and the Bad Juju. On the top row we can see the Monte Carlo but what is that black and red weapon next to the Monte Carlo. Well guys I can confirm that the icon the 3D model is out of the Sewers regime and you can see this by the picture on screen now so what is this and what are these year two primary weapons are they upgraded year one weapons this leads me to believe that they are this damn trailer is leaving me more questions and answers it really is. Now at the top of the screen we can also see collection two which is obviously another page which may contain your year one secondaries and heavies and your armors but guys that is what I have scraped out of this trailer if I missed anything interesting be sure to tell me what it is down below in that comment section now we just have to wait until the stream tomorrow night which should be pretty badass all details about that stream will be in the video description but guys I hope you enjoyed the video do drop a like I do appreciate the support tell me your thoughts on what I've covered in this trailer and peace out until next time. Peace!


All right, next up is Nathan Caller about a joint paper with Itaiduna. It should be Itaiduna according to our information, but it seems to have changed, also the title has changed. So when this was submitted to us, you can see on this title, it was synchronizing optimally. Apparently in the meantime it changed to how we synchronize efficiently. And then maybe after that it will be how to synchronize practically. Yes, actually we thought that the amendments we do until they certainly will reflect in the program. So both the name of the speaker and the title will change before they certainly will. Okay, anyway, so I'm going to speak about something with that, which is about some simple and nice mathematical header, about some nice mathematics and some application to some nice things. So the integration comes from a morphic section sharing. This was introduced by a late boy, and the late boy was quite shy, he came from 16, as a practical alternative to fully homomorphic encryption. It allows homomorphic immigration and function to be distributed among the parties. We do not interact with each other. They constructed a group based, which is a scheme, but not for all functions, but those described by one particular plan. This was quite successful, but basically more scripted, then quite a few follow-ups in different conferences, many applications. Now, this is for those who understand objectives, now for those who do not, just look at the mathematical problem we have in it. So this was the main problem in the paper of the GI. So the scheme is based on some shared version, which has tables. And since it is repeated many times, then it is very important to reduce the mobility of it. So this amounts to a clear mathematical problem, the following one. We have N random numbers, a region and line. We have two parties. We can adjust and adjust the places on the line, but we do not know who of them is the first and who is the second. Now, which one can query the lines in the most intensive places? They want to see in the comments, that is to choose the same number, but without any communication. So the question is what is the minimum possible error problem? So here is a sequence of the question, which was suggested by the authors. So we have here the sequence of numbers on the line. So each party queries just to take consecutive points, starting with these points for a while, and choosing the minimum. For example, we have T with 5, here both places, and the minimum 11 is the common minimum for both, so they can synchronize. But if we have placed the first two numbers, then they cannot synchronize because one of them chooses the first number and the other chooses the other. Here it is clear that actually the error occurs only if the minimum is in the end point. So the error probability is about 1 with T. The question is whether one can do better. So there are several papers like to improve it, but there will be no asymptotic error rate of 1 with T squared instead of 1 with T. And also if we show a much lower bound, which shows that unless we can't find the script log in the short interval faster than the square root. And so in the interval, we cannot break this model in the square bound. So counting for all standard demographic groups like an entity care center, this is really optimal. At least we believe so. So the techniques are a mixture of a nice mathematical techniques. It starts with some random walks which are with some funny numbers of steps and some funny things. To prove that the random walks work, we use some mathematical theory and to prove the log, we use some discrete free analysis. So some nice mathematical work. Now, applications of that homomorphic scheduling system, this is a random application like a private integration retrieval and other things. So these are placed in our paper in crypto. And now we are continuing to work on this now with the original authors with Elendir and Ruvan about the readings which are outside the topography to some mathematical readers, some brilliant functions and some more cool stuff. So I hope it's nice. We really believe that this algorithm is quite generic and so we'll be using it in other places as well. So, thanks.


Welcome to the next segment of our discussion of thermodynamics. So, so far we have discussed the first law of thermodynamics and find out one important parameter enthalpy, which is an intrinsic state function which defines the changes in the heat content or the bond energy during a chemical or physical process happening in a system. So, now we'll go a little bit further and find out another important parameter entropy. So, so far we have discussed the first law of thermodynamics. And in the first law of thermodynamics, what we actually find out that a change in the energy of a system is given by the heat is coming into the system and the work done by the particular system. And from there, we actually expanded it further and I find a another important term delta H, which is nothing but delta E plus P delta V, which is nothing but the enthalpy and it gives us about the heat content of the system. Now over here, the first law of thermodynamics give us a very good idea, how much heat or how much energy is actually exchanged, how much work can be done. But it never gives us an idea which side the reaction should occur, which side a particular process should go on. It gives us an idea, what will be the overall change, but doesn't give us an idea, which side is actually it favors, which side the reaction will be spontaneous. To understand that, we have to look into the second law of thermodynamics, where we get the idea of spontaneity. So again, reiterating back to the first law of thermodynamics, it is generally known as the energy conservation law, which actually says that none of the energy can be destroyed. It will be end up with a mixture of heat plus work, but you cannot destroy the overall energy. And in the second of thermodynamics, it actually given by different scientists and actually explained in different ways. So, I am just using one particular scientist version, Clausius, how he explained the system. So, he explained the system in the following way. He said we have a system and we have a surrounding. And say the surrounding temperature is Ta and system temperature is TB. Now say, temperature of Ta is less than temperature of TB. Temperature of Ta is actually less than the temperature of TB. That means, surrounding has lower temperature compared to the temperature of the system. The second of thermodynamics says that no process is possible where the sole result is the transfer of heat from a body of low temperature to the high temperature. It seems quite obvious because we generally know that heat actually moves from the high temperature to the low temperature. But this point is saying that it is not possible if there is the only thing happening or if we do not have anything happening from the outside to tune that process, the heat cannot go from the low temperature to the high temperature. So, in this case, the heat cannot go from the surrounding to the system if nothing else is happening because the surrounding temperature is lower than the system temperature. So, this is how Clausius defined the second law of thermodynamics. And you can find also the statement from Kelvin or Carnot. And you can find they actually define the similar statement in different ways. Our goal is not to distinguish between the different statesmen, but we are trying to understand the inherent understanding of the second law of thermodynamics. So, so far we have talked about the enthalpy and we know if we have a system and if we measure with respect to enthalpy, if this is my reactant, this is my product, this is a delta H greater than zero system where product enthalpy is higher than the reactant or it is known as endothermic reaction. And in the other way I can have the opposite scenario where the product enthalpy is lower than the reactant and I can say I have a delta H greater than zero system or exothermic process. Now, this exothermic and endothermic process is saying how much heat will be released and whether it is coming out of this process or it is going inside the process. But it never talk anything about the spontaneity of the reaction, whether the reaction will be spontaneous or not, that question is unanswered till now. Is it always that an exothermic reaction only occurs spontaneously because the product is a little bit stabilized with respect to enthalpy than the reactant? Does it means so what is the relation between exothermic reaction and spontaneity? Is it spontaneous? Or endothermic reaction in that way because the product has higher enthalpy than the reactant, it should never go through spontaneous reaction? Is it does it what we mean? To understand that we will take an example and we will take an example of a melting of ice. A melting of an ice piece, if you look into the change of their enthalpy, it is delta H greater than zero, that means it is an endothermic process. And if you keep a piece of ice at a particular temperature, you can easily see the ice generally melts. So, the melting of ice is generally a spontaneous process. So, it has nothing to do with endothermic or exothermic reaction pattern, but all together there is some other factor is playing a role over here. So, we try to understand what is the role of this? So, why even the melting of ice is an endothermic process, how it becomes spontaneous? To understand that, we look into the details of the melting of ice in a molecular level. And we found this another factor playing a huge role over there and that factor is known as entropy. So, what is entropy? Let us take a look into melting of ice. So, when the melting of ice is happening, there is a change from ice to water. So, it is more of a solid to liquid form. So, in the solid ice, all the water molecules are actually present in a very ordered way, because it is crystalline in nature. Whereas, in water it becomes liquid. So, there is some disorder now present. Previously, the water molecules have to be oriented in a particular way, so that it can form the crystal. Now, once it becomes a liquid, it does not have that much of a pressure to be in a particular orientation. It can be in different orientation and that brings some disorder in the system. And this disorder in the system is actually coming from the randomness of the orientations of the molecules. Now, can the molecule orient in every different way possible? It does, but it still follows some particular feature that actually controls how many different ways the molecule can move around a system. And that is known as degrees of freedom and that is actually depend how many atoms are actually present in a molecule, what is their overall symmetry and all these things comes together and give you an idea the degrees of freedom. So, once we go from a solid to liquid, the randomness or degrees of freedom or movement is actually improving. And this increase in the disorder, this increase in the randomness is the prime factor which actually drives the reaction forward. So, that randomness factor or known as entropy is the crucial factor over here which makes sure that the melting of ice is a spontaneous process. It is connected to the enthalpy, but enthalpy is not the only factor. Both this entropy and enthalpy coming together and the entropy factor overcomes the endothermic nature of the process and making it a spontaneous process. So, how we measure entropy? So, entropy is written with this symbol s is nothing but a randomness measurement or disorderness measurement and we measure that in the final state. We measure that in the initial state and if we subtract that we get the overall entropy change. So, that is the mathematical system. Now if we go little bit details of that, so during a physical or chemical process the randomness of the system is changing and that is we are trying to measure. And this particular entropy change during a physical or chemical process depends on the quantity of the heat transferred to initiate the disorder in the molecules. Now over there when this is happening if we want to measure that very carefully we measured it such a way that it is happening almost very closely lying final and initial state where the difference is very small and they are reversible in nature that means they can go back and forth very easily. And during that process if the change in the heat is dq and I am writing reversible to mention that we are looking into a reversible process. And if I divide that by the temperature exactly where it is happening because it is a reversible process we are doing in such a way there is not much difference in the temperature, temperature remains identical and there is a certain change only in the disorderness of the molecule. And then we find it out and find it out of all the process all such processes happening from the initial to final state and if we integrate all of them together then we figure it out that is nothing but delta S. And altogether we write it as q reversible by t for such process where the temperature does not change at all for an example a phase change which is actually a reversible reaction in a way and over there the change in the heat during that phase change and the temperature remain constant. If we use this particular equation we find that it is going to be the entropy change and over there one important thing this T or temperature has to be written in the form of absolute temperature that means we have to write that in the Kelvin unit not in degree centigrade unit. So the absolute temperature has to be used for finding out the entropy change during a process. Now why it is very important the entropy because the entropy actually redefines the second law of thermodynamics. Now if we go back and take a look into the second law of thermodynamics one more time and we have already defined it as Clausius actually explained it before. But now we want to explain that with the entropy factor and how does it matter because it says the change in entropy of an isolated system you have defined isolated system earlier where neither the mass nor the energy can be exchanged between the system and surrounding. The change in the entropy of an isolated system that means delta A s is always positive is always positive when it undergoes a spontaneous process. So there is a change in the entropy positive means s final is greater than s initial that means the randomness is higher in the final state than the initial state that means by delta s positive and this increase in the randomness actually drives the reaction faster and that makes the overall reaction spontaneous. So now the second law of thermodynamics is giving me an idea on the direction of the reaction. As we discussed earlier the first law of thermodynamics give me an idea how much energy will be used how much work can be done how much heat can be exchanged. So it is actually combining all those things and giving me idea like okay everything will be conserved the energy will be conserved but that does not say about the direction and the spontaneity of the reaction. Second law of thermodynamics in the presence of the term entropy is introducing that factor and that is bringing up the spontaneity and also the direction of the reaction. Now if we want to take a look of entropy of different processes how does it looks like. So we want to look into entropy of different physical changes. So for an example we start with entropy of fusion that means a melting process ice to water such thing like that. So during this process the fusion will be such that the entropy change during this fusion process will be entropy of the liquid state minus entropy of the solid state and that can be given by the heat exchange during this melting process which is nothing but the enthalpy change in this fusion process divided by the melting point. So if we put this together we will easily found the entropy change during a fusion process and as you already know delta H fusion is already positive for ice melting that is also showing that delta S fusion is also positive. Now take the second one entropy of vaporization where I am going from a liquid to a gaseous state. So delta is vaporization will be difference between S gaseous state minus S liquid state and that is nothing but enthalpy of vaporization enthalpy change in the vaporization divided by the boiling point and you can imagine this is also going to be a positive factor because from a liquid to gaseous I am actually expanding the overall volume of the system so that will increase the overall entropy of a system when it is going from a liquid to the gaseous state. Similarly the other physical change remains entropy of sublimation where a solid state directly go to the vaporization state sub this is nothing but S gaseous minus S solid and that is given by delta H sublimation and at the temperature where the sublimation is happening. So over here you can find it out that the entropy change of different physical processes can be easily find out by the enthalpy change of that particular process and divided by the temperature where it is actually happening which generally at constant temperature. Now how about measuring the entropy of a chemical reaction now very similar to the enthalpy change entropy change can be also connected. So over here I am doing this reaction A plus B going to C plus D and over there I want to find out what is the entropy change for this process so what I need to do I have to find out what is the entropy for the products. So it is entropy of C plus entropy of D and subtract that of the initial entropy of the reactant that means entropy of A and entropy of B. So which is nothing but very similar to Hesse's law what we actually discussed earlier but it is enthalpy and this is in the terms of entropy it is the entropy of the products we add it all together and subtract that from the sum of the entropy of the reactants all together and from there you can actually get the overall entropy change. Now entropy change is actually dependent upon the condition at which condition I am doing the change if I am doing that a different temperature different pressure the entropy change will vary so that is why we want to standardize it and we can standardize it by doing the entropy change measurement at standard states what do I mean by standard state that means at 298 Kelvin or 25 degree centigrade temperature one atmospheric pressure of any gas solid state is already in the standard state and all together if I measure all the system in this particular condition my entropy change becomes delta S0 or entropy change in the standard state and that is going to be constant because the entropy change for any reaction of the products minus entropy change of any set of reactants they are going to be constant because the entropy of one particular system at a particular temperature and condition especially at the standard state is constant so that is why a standard entropy change is going to be an important parameter that we can use to look into a reaction at a time and find out what will be the overall change of the entropy for this particular system so now this entropy change is also giving us an extension to a very unique third law of thermodynamics so already we have defined the second law of thermodynamics with respect to the entropy where it says that a spontaneous process will be that which has in an isolated system the entropy change is positive but it also says that how low I can go with respect to the entropy see if I want to go very low in the entropy I have to go to the most ordered state of a particular system and now we know that when we are actually putting up a temperature there would be a disorder in a system there will be some randomness in the molecule and if I want to get rid of all the randomness all the disorder I have to get rid of this temperature induced randomness so that means I have to go to 0 temperature absolute 0 temperature 0 Kelvin and that is actually where we come to the factor of the third law of thermodynamics which says all substances in their normal crystalline state at the absolute 0 temperature would be in the condition of the maximum orderly arrangement that means that will be the perfect orderly arrangement no disorder at all and it can be only achieved at absolute 0 temperature which actually can be written in this form if we want to go entropy close to 0 you have to go temperature as close as to 0 and this is actually important factor because this particular third law of thermodynamics derived from the entropy factor give us an idea how we can reach very low almost close to 0 Kelvin temperature with respect to that so that is an important factor of third law of thermodynamics so in this particular segment we discussed about the spontaneity of a reaction and we find out the second law of thermodynamics can explain which side of the reaction will be spontaneous but for that we need an another important factor the entropy entropy is nothing but the randomness or the disorder present in a particular molecule and this entropy factor defines which side the reaction would go and at the same time we also find out the entropy can be defined as the change in the heat for a particular physical or chemical change happening at a particular temperature where the temperature is represented as an absolute temperature so with respect to that we will conclude this particular segment of the thermodynamic discussion and we look forward to match you again in the next segment of the thermodynamic discussions thank you


This research study examined the prevalence of stigma and discrimination against people living with HIV in three hospitals in New Delhi, India. It found that stigma was present among all types of healthcare professionals, including doctors, nurses, and ward staff. Additionally, it identified several factors that contribute to stigma such as incorrect beliefs about HIV transmission, discriminatory practices, and attitudes towards HIV-infected individuals. Furthermore, the study found that higher levels of stigma were correlated with lower levels of correct knowledge about HIV transmission and discriminatory practices. The study concluded that stigma reduction efforts should take into consideration the cultural and economic context of the region as well as the specific needs of each individual patient. This article was authored by Vaishali Sharma Mahendra, Lailia Gilborne, Sholani Bharat, and others.


Hello all and welcome to tomorrow's Space News. We have got a loaded episode for you this week. Ryan has got a bit of pressure to talk about it. SpaceX, our sun is really starting to kick up its activity in our weekly space weather update with Dr. Tamethascove and I'll be talking about a big do-over that will be coming from Boeing. Now before we officially get started I just of course want to remind you to subscribe to us here tomorrow. If you like news go ahead and like the video and set up notifications so that way you can know when we send out new videos or when we are going live. So while I wait any longer let's go ahead and get into your Space News for April 7th, 2020 and Ryan, all yours. It's not looking good for Starship SN3 as it got pretty cold and then crumbled. Down in Boca Chica SpaceX was starting off another cryogenic test. Testing on Thursday was successful however this test did not end so well. The centre of the vehicle in simple terms sucked itself in as it depressurised causing it to crumple allowing the top half of the vehicle to tip over, fall off and smash into the ground. Now this did happen at what seemed like the end of the test so hopefully the team down there did collect the maximum amount of data that they could to ensure that something like this doesn't happen again. Elon Musk has said on Twitter that this was a test configuration error and after closer observations it seems that this failure may have been related to detanking rather than a depressurisation failure caused by the vehicle itself. Compared to the Starship Mk1 and SN1 depressurisation events this one was a lot slower and a lot less explosive making it a testing fault. The thrust section from SN3 will be reused for SN4 mainly to save time and if it's got no damage then you might as well use it. Everything has also come a long way since the previous iterations of the vehicle as it has become a lot more streamlined and neater as you can see here. And that is pretty much all SpaceX have been up to during the past week. As expected everything has very much slowed down but hope free SN4 will make an appearance very soon. Thanks for the update Ryan, I really can't wait until Starship starts doing its belly flops during its test flights and speaking of test flights that I'm really interested in seeing Boeing has just announced that they are going to fly a second test flight of their Starliner capsule. Now you'll recall that in its first test flight last December OFT-1 it was basically a near disaster. You'll recall that everything started off looking great with a flawless launch on a United Launch Alliance Atlas V in the N22 configuration meaning that there's no payload fairing as Starliner sits atop the rocket, two solid rocket boosters and a twin engine Centaur upper stage. But at this precise moment separation of Starliner from that Centaur upper stage that is exactly where everything began to go wrong. Immediately the onboard timer placed Starliner into a configuration that was incorrect for that moment in the flight. Thruster firings that shouldn't have happened were happening. Attitudes were out of control, very bad things were occurring. Now after getting Starliner into a stable orbit and a board of an attempt to dock at the International Space Station was called therefore losing its biggest milestone in this test flight. Instead Starliner was set to fly solo and work on other tests that could be done in such a configuration. Boeing hastily conducted a review of all of the software that was on board of Starliner and found that the parameters to Jettison the service module were way out of where they should have actually been. That meant that at just before re-entry when the service module was released it could have re-impacted Starliner and caused a destructive re-entry. Luckily Boeing was able to patch together new software, upload that into Starliner and the potential loss of vehicle and crew event was averted and the capsule safely landed at White Sands in New Mexico. Now a review after the flight found 61, yes 61, 61 corrective actions for Boeing to take. However credit is due, Boeing fasted up to its errors and admitted that it had made major mistakes. Now this second Starliner test flight will not be funded by NASA's commercial crew program. Boeing will rightfully eat the $410 million cost. Another note, Boeing are the ones who have called for the second orbital test flight for the Starliner capsule. NASA did not and you're probably asking yourself, well why, well NASA just announced that they are nowhere near being done with their investigation into what actually happened. So from NASA's perspective they're still working on it, but I can't imagine NASA just simply glossing over what actually occurred on that test flight and saying, yeah go ahead and stick people in it, it's not the space shuttle after all. And NASA also said that they are looking at Boeing because they have not started working on any of those 61 corrective actions yet as well. The latter half of 2020 will be the likely timeframe for this second test flight of Starliner with a crewed flight finally occurring and certainly pushed to 2021. And unfortunately we did not have any launches since our last episode, but there are a few on the horizon. And for your space weather update, here's Dr. Tamatha Scove. This week we are seeing more signs of new cycle life as we switch to our front side sun. You can see that bright region rotating into Earthview off of the sun's east limb. This is region 2759 and it has been firing off some very low class flares. In fact on the fourth it fired off a B class flare. Don't worry there were no radio blackouts associated with it, but it does show us that these new cycle sunspots are continuing to be flare active. Now since then it's kind of fizzled out just a little bit, but we're still watching it and it is still boosting the solar flux into the 70s. So that's good for amateur radio operators and emergency responders. Now as far as aurora photographers are concerned we have been getting some small pockets of fast solar wind and as of about a week from now we should be getting yet another finger like chrono hole rotating in through the Earth strike zone that could give us yet more chances for aurora with more fast solar wind coming. Now as we switch to our far-sided sun this is stereo A and it's looking at the sun pretty much from the side. You can see that region 2759 rotating off of the west limb in stereo's view, but as you notice right around the fifth you can see in the southern hemisphere yet another bright region. This is also a solar cycle 25 sunspot and it is showing a little bit of activity. So once again we are consistently getting activity from the new solar cycle and even though things are still pretty quiet right now with this kind of activity I tell you things are going to be quiet for much longer. And now for your Leo, Mio-Geo orbit outlook. As we switch to our low energy particle environment these are the fluxes that cause charging around the surface of the spacecraft including charging up the solar arrays that then can cause discharges and other electrical short circuits and performance degradation. You can see in and around Geo starting around the third this got these fluxes that are getting injected especially around the pre-dawn hours and these fluxes built up just a little bit and that's because we've been having these mild solar storms that have only been bumping us to active conditions. After about midday on the third they got flushed and things got pretty pristine but then as you can see right around the fourth we started building these fluxes again the injections happened and now we're beginning to see a nice red ring around Geo and so you satellite operators especially around the Geo environment expect that you might be dealing with surface charging issues over the next couple days. For more details on this week's space weather including when and where to see Aurora and how this new solar cycle activity is going to affect you come check out my channel or see me at spaceweatherwoman.com. Now's the time of the year where we celebrate Yuri Gagarin's Vostok 1 flight done on April 12th 1961 the first time a human went into space and Yuri's night is one way that we celebrate that big parties all over the world celebrating humans going out and exploring the cosmos but in the middle of a pandemic it's not really a good idea to get a whole bunch of people together so Yuri's night is going virtual and here tomorrow we're helping out. The global webcast for Yuri's night is happening this Saturday April 11th starting at 2300 UTC. Now you can head on over to the broadcast to set a reminder for yourself which we'll be dropping a link in the description below and there's gonna be a wide array of guests including astronaut Scott Kelly, Nicole Stott, Story Musgrave, Chris Hatfield, mechanical engineer Bill Nye, actor Robert Picardo, Bill Weir of the Grateful Dead and a few more big surprising guests. And a few familiar tomorrow faces will be there such as myself who will be helping host the global webcast. So join up hope to see you there and hopefully we can dance really awkwardly with our cameras on. Alright so to wrap up this week's space news of course I want to thank all of you who contribute to the shows of tomorrow. We really can't do this without you and each and every one of you who does this you are absolutely amazing and I cannot quantify my appreciation to what you do for us. If you'd like to contribute to the shows of tomorrow head on over to youtube.com slash TMRO slash join to do so and check out all the rewards that we have available to you at different levels of support. And of course watching our shows, liking our videos, subscribing to us and setting up notifications and sharing our videos everywhere that you can that's an incredible help as well. And that's Seco 7 for this week's space news. Until the next one remember keep exploring.


My name is David Benavides. I'm an assistant professor at the University of Maryland School of Medicine in the Department of Neurology. I also have a secondary appointment in the Department of Physiology and I'm a member of the University of Maryland Medicine Institute for Neuroscience Discovery. I was always interested in becoming a physician and as I went through my college course work that's when I really understood how one could pursue both a research and a career in medicine so I pursued training both as a medical doctor as well as a scientist. In my practice I take care of patients with multiple sclerosis, neuromyelitis, optical spectrum disorder, neurosarcoidosis, autoimmune encephalitis. In my research we're using models in the lab to help understand how the immune cells of the body may be targeting neurons and other brain cells and leading to the dysfunction that causes disease in patients. Hopefully the research that we're doing is going to aid us in knowing where to go next with regard to new treatments and new therapies so that patients can not only prevent further disability but also maybe the potential for regeneration and restoration. It is a privilege to take care of patients and I really look forward to the opportunity to undertake shared medical decision-making so that patients feel invested and they feel like they're really part of the treatment plan that they're going to be undertaking.