Well, welcome everyone. Thanks for showing up, beer to follow, but we hope this is going to be an interesting lead-in to the booth crawl. I'm Ashish Mukherjee. I manage partnerships for Mirakura. I joined my first day at work, was actually the first day of the Vancouver Summit. So I know what it is to be new to OpenStack and to have to learn a lot from the firehose. And we're hoping to give you some entertainment and some good concepts of what to do if you're just starting out. Mirakura is an open platform in the spirit of openness. We are open to hardware and software and services vendors from Acosta spectrum. And we have several here. Before I introduce them, let me say we have a bunch of questions that we came up with in advance, but we would love it if you would ask the really tough ones that get some disagreement going. And whatever's on your mind. It's not about hearing our voices. It's about answering your questions so that you can really learn and thrive from OpenStack and not repeat past mistakes from history. And here we have our final fan list. Thank you, Rob. Wasn't a subtle way of doing that. Sorry. Why don't we lead off with some introductions? OK, hi. I'm Rob Esker. Working on OpenStack for, I guess, five and a half years or maybe a little bit more, whatever the math works out to within a couple of months of inception of the project. I work at NetApp, so I spend all my time in product management strategy, but have done work on the architecture and deployment end in the early days, a little bit of development as well. I guess in terms of the community, I'm a co-founder of Manila Project with Ben Schwarzlander and also serve on the OpenStack Foundation Board of Directors for the last couple of years. My name is Mark Williams. I'm the CTO of Redapt. Redapt is a systems integrator. We help companies typically in the web and tech space fill their data centers full of servers and integrated racks and networking and also help them deploy cloud technologies on top of that. I've been there for about three years. Prior to that, I was a customer of Redapt. And working at Zynga, where I had the good fortune to take Zynga during its good years of exploding into Amazon, consuming a lot of public cloud and ultimately building a private cloud based on CloudStack. And I don't know if everybody's following Zynga anymore. No, but certainly your Facebook feeds aren't, but now they're completely back in Amazon. So that's a recent development there. My name's Frank Rigo. I work for SUSE. I manage technology partners around several of our ecosystems, including OpenStack. Been around the OpenStack infrastructure since we released our first product based on Essex. We have a, if you don't know, SUSE is a Linux distribution company. We have a distribution of OpenStack that we call SUSE OpenStack Cloud. And I blame Mark for a lot of my time wasting if you're related to Zynga. I'm just saying, yeah. Hi, my name is Takahiro Kojima. I work for Fujitsu, you know, Fujitsu. And yeah, actually, Tokyo based IT company, ICT company. And I am a product manager of Fujitsu OpenStack product. So I have some experience on delivery, OpenStack system delivery to our enterprise customers and public cloud K5. So I'd like to give you some stories about struggle struggling with OpenStack in touch our customer and K5. Thank you. Thank you all for coming. I think, can you hear me? I think Takahiro gets the prize for having traveled the furthest from Japan. So, and he mentions struggles. And you know, I have these questions and some of them sound sort of negative, but it's not about that. We're all here because we think OpenStack is great or we think OpenStack at least might be great. The idea once again is that we've all made mistakes. We've all seen mistakes. You don't have to make the same mistakes. We wanna arm you to make your own mistakes, which are gonna be more interesting. So we're gonna go through these questions. You ask questions. We love OpenStack. These are tough questions, but that's it's a reflection on our collective struggle. So I see about a hundred people in the audience right now, a few more coming in. Can we get by show of hands, how many of you are operators rather than vendors? Okay, a small maybe a quarter operators. Then how many who admitted it and how many are actually running OpenStack today as a POC or in production? Okay, so there's a lot of you who might run OpenStack in the future, I guess. So there's a lot for the panel to let's say prove. I wanna start off with one of my favorite questions, one that wasn't contributed, which was like what's a great story of something that falls in the category of a disaster. It really was bad and then somehow the ship turned and maybe there's a lesson in there. Who wants to, Frank, if you wanna start? Sure. I mean, you hate to use the word favorite disaster in OpenStack in the same sentence, especially with people that are new, but from the viewpoints of an OpenStack distribution vendor, we talked to a lot of companies that initially started with getting the bits from upstream. So it's an open source product. They can download the bits and start that way. And so there's a lot of struggles that happen in that sort of a, when companies start that way, not that it's impossible, but it's just very complex. So I think that's probably pretty common that we see that. I think another very common thing is when the businesses don't get the teams that are integral to the project involved. So the OpenStack project sits in the cloud team, but they haven't integrated the storage team or the network team or the application development team as well as they should. We had a project ongoing at a fairly large company that was a proof of concept and was going fairly well. And several weeks down the road, we get a call from the company and they say, yeah, things were working great in the POC. Everything's working, we're very happy, except when we moved into production, something happened to Cinder and it just, the performance slowed way down and we're not sure what happened. And we said, well, that's interesting. Is there anything changing between your POC and your production rollout? They said, no, nothing. Well, the storage back in changed, but other than that, nothing. So it was like, well, maybe that had something to do with it and it turns out that they were different, just different things about the POC storage vendor and the production storage vendor. So the lesson there was, yeah, it's important that you don't do this as an isolated project from the cloud team and expect it to work right when you roll it on into production, when you have to hook in all these other peripheral components. Yeah, most of the disasters I see are two parts. First is, right when you begin talking to the potential prospect for OpenStack, you ask them, well, what workloads are you trying to deploy in this private cloud? Or you'll say, well, what are you trying to achieve with this? And oftentimes I get, well, my boss told me to do this and there's really nothing more than that. They're trying to have technical credibility by saying we run OpenStack and there's really no business purpose or workload that it's aimed at. And when it's kind of a big red flag for us, we'll stop and say, look, you have to really know this to make an informed decision about what architectural decisions are going to make here. The second one is further down the path, once you've collaborated with a customer, they know directionally where they wanna go. Many customers tend to want to pick all of the fringe features, not necessarily those big tent projects that aren't core, but even within the core projects, which Cinder and Glantz and Neutron all those, within there, they'll wanna make decisions that drag you into the weakest features in there that really stretch the edge just because they believe they need to integrate with incumbent technology for some reason. And that's where I've heard ISVs who have OpenStack distribution say, that's like playing with a block box of razor blades. Don't do that. And it's very hard to steer that initial customer who in their first deployment to looking at keeping things simple. Keeping things simple gets you to that next step of you learn what the behavior of our workloads are on something that's relatively consistent standard. And then now you've learned more about OpenStack. You can take that next step and begin to dabble with some of those newer features. So I don't know if I have a favorite, but maybe I can briefly touch upon two so that I can fit it into the space of one. So I guess this is in process. So it looks good. I think it's a success, but not fully complete, but a large sort of online gaming company not SINGA, who I'm not sure actually is particularly well-known, is actually an OpenStack employer and had been since the earliest of days. They were bit by a couple of things. One, having been amongst the earliest adopters and directly from the upstream. So on one hand, they derived benefit very early on. On the other hand, not much was particularly mature at that time. And in particular, seemingly pretty obvious problem of needing to go from one major release of OpenStack to another was not particularly well-solved for. I'm not suggesting that it's a seamless and wonderful experience today, but it's dramatically better now and has successfully improved from one release to the next. So they were bit with having been early adopters, having to deal with some of the early pain associated with not quite mature, but furthermore not being able to get off of it. And as of course, successive releases were made available, the problem got worse because it was OpenStack from two years prior was substantially different and it was essentially a replatform exercise. It got to the point where actually some of the talent that deployed it originally ended up leaving. And so you had a certain amount of institutional expertise that made this thing tick in the first place and then suddenly you were handing this sort of what was at that stage an experimental project and handing it off to mere mortals. So what the heck do I do with this thing? And that was certainly a failure or it was not a failure in the sense that it fell over but they couldn't get off of it. The success portion component of that I guess is that and they didn't start down this path initially once this new staff became or once the new reconstituted admin and operations team was put in place. They started looking what we'll derive from upstream directly. I think what made it a success is they went with a distribution provider who has thought about and is delivering capabilities that contemplate what it would look like to go from one release to the next and abstract a lot of the complexity and make it deterministic. And wow, even actually provide a support model for it. So it made it consumable. Like I said, that's still in process but that's maybe two separate things. One, beware the sharp edge of being on the cutting edge and two, I think there's something to be said for going with one of the distribution providers. If it makes sense to go with upstream directly and roll your own then you probably not in this, well I'm not suggesting you're in this session, I'm saying you probably have the expertise in house type deal with those problems. Wow, just within a few answers, the three of you have touched on essentially every question I had, which is great. It shows we have the right questions and those are the hot topics. So I mean, carrying on, I wanted to, oh, we have a question from the audience. Well, why not? Go for it. So a lot of times I wanna hear about OpenStack being deployed, it's a company-wide initiative. But what if you're an app developer and let's say for whatever reason you need to sprinkle resources in 50 different locations around the world, say about 100 VMs per location. Give me a gut check of what kind of investment am I gonna need to do and will it need company-wide initiative in order to get it done? I mean, is it possible for the app level to roll out something like that or would I need to hire 200 OpenStack engineers or pay somebody $5 million to do it for me? Well, there's several different approaches you can take but certainly without the governance and partnership with IT, if you're the app developer, you're probably not gonna get the funding through purchasing and that related part of your business. But to the extent that you can go into that partnership, you, and if there's no expertise of OpenStack in-house, you're probably wanting to look at something that's like a managed, dedicated, private hosting approach. Rackspace or similar have places where they can do that, Bluebox is another one. And at that point you then are shopping for, well, where does that service provider have the locations? If you really need 100 different locations, if that's what you, I can't remember if that's what you said. Cloud gaming. Cloud gaming? Okay, yeah, you're gonna need lots of little points of presence. So that'd be the starter way to go to start quickly and start determining if OpenStack as an IaaS and another platform capabilities provides the automation that you really need. Beyond that, then once perhaps you have some, critical mass of a team that can own and operate and maintain an OpenStack, you're gonna want to very quickly co-architect with either a like a SUSE or other commercial provider of an OpenStack that can help you define the physical architecture and making that consistent in every one. So again, you don't wanna create 50 different snowflakes, versions or hardware compositions in that. You want it as normalized as possible. And you want that guidance from that commercial provider to make the right decisions to stay within the boundaries and not get into the bleeding edge features. Then at that point, you can work with like a systems integrator to help you build those consistently and install it consistently from the physical layer, every version of every component in the server matters, getting all of that. And then successively move towards more independence as you do that, helpful. So big investment.   For Zynga, it absolutely was. At the time that Zynga started moving out of Amazon, like there were still growth pains in Amazon. There were lots of significant outages. Wasn't the performance that we wanted. All of those things we were able to make better in Zynga's cloud called Z-Cloud. And now I'm getting into the next, potentially the next question, but I'll save that. But anyway, yeah, it's a substantial investment. And then you're still competing with incumbent technology that your IT has as well as Amazon and other public cloud providers. And that's a hard sell. Thank you. So staying on the theme of starting with something and then preparing to grow it. I wanted to ask Tucker here from his experience with K5, what is your experience and your recommendation of starting with a POC, which many in the OpenStack world are doing today? And then how do you, while doing that POC, think forward to production? What to do? What are the mistakes people make? Okay, so I'd like to explain about my favorite disaster. Actually, my opinion is very similar to the flank. So the POC is very important for open source. You need to demonstrate. You can deliver the value to the customer, actually, you think that open source, open stack. So after that, yeah, as Frank said, yeah, you will encounter many problems when you are moving to the production. One problem we encountered in K5 testing is that compute service or compute service, that's a 250 compute in that time. At that time, all went down. How that happened? So actually, we configured a parameter in heat to increase the performance of heat, the worker's stress, increase the number of stress. Then we encountered, we found a problem in the HAProxy, you know, HAProxy, and that HAProxy, we found a error over maximum connections. So we configured the kernel of the HAProxy VM and increased the parameter for max connection. Then, all computes down. Why? So it's max connections now are maybe are 10, 10 so thousand, I think. So in that configuration, all computes try to access to the database by your conductor. So that means that all computes try to connect to mq, message queue. So many, many messages that are queued in that server. So, you know, our OpenStack service cannot work without mq, so all OpenStack API fails. So we are powered up. We scale up the message queue and wait for several days and et cetera. So what we learned from that is that in the large-scale system, it's very difficult to expect the result of a single configuration change. Even experts cannot detect everything. So you need to test in the scale of your production before upright to the production. So that's my recommendation. Mark? I just want to add, so I totally agree that establishing at proof of concept stage that indeed there is proof of concept is critical. But one of the things, and it's actually hard to expect your first question of how things can go awry or maybe things that didn't start out so particularly well are great. I've seen a lot of POCs try to lump in every possible shiny object, you know, like emerging technology into one. And apologies if this comes across this common sense, but I guess the lesson I've taken away is try to start with OpenStack alone and then layer in perhaps your neutron plugin of choice or perhaps your cinderback end of choice, but not necessarily at the same time and maybe in successive phases. You know, there's a number of emerging technologies that are synonymous in some ways with OpenStack, but not actually part of OpenStack. And while they may be valuable and you may want to incorporate them, it might make sense to evaluate them on a slightly different timeline. Fair enough, although I do think there's some neutron plugins that just make your installation so much easier. I wanted to turn to a big picture, but pretty important question as we're discovering which is you've built this great technology, but what then, do you build a cloud and hope that the developers will come? Is it a pull or push model and how do you evangelize this essentially technology or platform within the company and how does the success of OpenStack depend on adoption? I mean, it does depend on the success of adoption, so how do you drive that in line with the actual install? I'll be brief. So I've seen it work and I've seen it fail. I've seen perfectly functional OpenStack clouds not be used, not be consumed. Likewise, I've seen places that were perfect, OpenStack was perfect for and it failed technically. The point is the places where it seems to stick the most are where there's a tight coupling to the application development community or those or perhaps actually on a way other end of the spectrum, maybe like a mandate that says, hey, and this goes to the whole OpenStack as a snowflake, it's hexagonal and frozen, but boy they sure do look a lot different from one to the next and you've probably heard that, it's really not original. The point is is some come to OpenStack from a perspective of I want to actually, I want to replace or maybe augment or provide a foil to like the incumbent enterprise virtualization vendor and I won't mention who that necessarily is, but the point is is that's a very different set of motivations from those who are trying to build like the cloud, fully cloud native, like next generation buzzword compliant cloud. The application developer coupling is probably more important on the latter spectrum, on the first side of it, it works best where there's that corporate mandate to say you will move your existing application base into this particular model and the place where I guess in particular where it works is if you actually can solve for the accounting problem who actually ends up actually paying for this thing. If there's actually a mandate that states, there's not just showback, but actually charge back. Now I'm not suggesting that's an easy thing and OpenStack doesn't solve for it, but where that's been done well, it seems to succeed overall. So I had this experience in 2011 when after consuming about 20,000 instances at any given point in Amazon, I built a 4,000 node cloud stack cloud and I couldn't get a first customer to move into it. And exactly what Robert said, the motivations of developers, I mean, their priorities, especially in gaming, is to continue to maintain the satisfaction of the users of our games. They don't care about cost until it becomes a mandate, right? So it really took collaborating with senior C level executives to make sure that cost mattered and we did have accounting. So we had to make sure that the cost per unit consumed by month in Amazon versus ZCloud was different. And actually it was a third cheaper to do in ZCloud. But even with that, it took extraordinary effort to collaborate with each partner on the gaming side to actually move them. Because again, they had to spend like nine weeks with us to migrate that application because it's got active users on it and that's very hard. But successfully starting with that first anchor tenant and building confidence, getting them to be your evangelists is the key part to success long-term. Yeah, I mean, I don't have a ton, I agree with both of you. I mean, we've had experiences where the technology is so new and so shiny that people just gravitate toward it. And so we end up doing some of these POCs where there isn't really an idea of what they wanna do from an IT perspective or from a line of business perspective. And more often than not, those don't go very far because you do need to get all the other groups involved eventually to make this thing a success. And so where we've seen the most success is where actually the line of business is driving something or the application development team is driving a particular goal and those generally succeed. So I have several more questions I'd be delighted to ask but I prefer to get them from the audience. Thank you. I'm Alex. I would not mention names or colors or anything but just I work for one of the largest telcos in Latin America and I'm located in Brazil. And we moved to the point beyond the proof of concept. As telcos, we were basic, we started doing cloud and after a few attempts of doing lots of crazy stuffs, we decided, okay, OpenStack is the way to go. And we were supported by the big names in the game. And I have a story to share with you guys is that even within the proof of concept, there are certain things that you cannot prevent or you cannot foresee. And I wanna ask you guys for some thoughts about that. What do you guys advise us to do just to give you a quick example? The whole OpenStack thing might be a buzzword and as Frank said, there are some, it's Frank, right? I'm sorry, okay, there are certain things that even within the core products there are major enough to be considered production ready. There are some details that made the whole difference and currently what we're doing is we do have a large storage solution based on OpenStack and we did the proof of concept and later on we figured out that we could not measure external transferring from internet because our customers, we do private and public cloud and for object storage, the way to go is you charge for volume and transferring and the solution that we deploy it, again, I won't mention colors or names, was based on SAF and SAF is not integrated very well with SWIFT at this point. I mean, you can do lots of things but measurement, internet transferring is you cannot differentiate between what it's external and internal and we are now at the point that people at the, you know, the high cleric, I mean, the top executives that invested in the product, I mean, in the technology, they believe it and they cannot differentiate what is SAF, what is OpenStack, what is SWIFT, what is Cisco UCS and whatever, they cannot do it and the only thing that they see it's the OpenStack buzzword and they say, that's not ready, you guys told us. You see, you know, I just mentioned Cisco. Cisco is, it's pushing OpenStack all over the place so now we, I'm a product manager and I wanna deliver a product that is cost effective and I cannot do it because the top execs are not, they didn't bought it. I mean, oh, I can't believe I spend, you know, as I said, we went beyond the proof of concept that we do have many nodes running and we are not charging our customers because of a very glitch and the expectations are super low now, meaning they are thinking about getting back to, I don't know, EMC and doing the way they always did in the past and just because of very small thing and how do you guys see the bandwagon including the larger telcos, I'm sorry, the larger vendors in the arena. When it comes to these small examples, I have a few of them but just, let's just stay with this. I think you actually have a question kind of built around this which kind of goes to the point as OpenStack been oversold in some way.  You've seen the hype curve from Gartner, right?  It was big data a couple of years ago and containers and OpenStack. I mean, the technology is awesome but it's kind of dangerous. You really have to know, going into it, what it's built for and what it can do and what it can't do and sometimes that's difficult, right? Especially if you're talking to somebody who's supposed to be an expert and they're telling you one thing but in reality it's something else. I don't know actually what the solution is. These guys maybe have a better idea. I'm not gonna claim to have the solution but I did wanna riff a little bit off of what you said. So the hype cycle of innovation for those who are not familiar, Gartner's, you know, attribution to Gartner, you know, there's a peak of expectations filled with a trough of disillusionment and the slow sort of ramp towards productive use, right? It's important to understand with OpenStack that you really need to think of each different project as existing in different points on that hype cycle. So something that's very nascent, you know, a newer project perhaps on the fringe, not necessarily, you know, been around for several releases is gonna be quite a bit further behind. Something like Nova, you know, not perfect but generally a known quantity at this state. And so I guess it comes with a little bit of a maturity in having traveled down the path of working with open source projects that you need to develop some organizational confidence about the ability to adopt Open in the first place. The extreme end of it, it seems like you maybe you're encountering some of it. There's a pretty, I guess I won't mention the name, but a couple of articles that have come out where. The opposite of green, that's the only I can tell you. Yeah, no, I mean, and I'm not sure, yeah. So the point is, there are folks who are in the business of providing the proprietary alternative. And it is often expedient to impugn the open. And it's not that hard to find the warts. And so unless you've like invested in building the institutional confidence in something that is solid, you might end up burning yourself by getting too close to the leading edge with the open thing. You might have burned open in the organization for a while. So I don't have the answer, but a few thoughts. No, that's it, that's it. This is where proprietary closed commercial solutions actually have a lot of value. I was a customer of cloud.com. And we basically owned them as an engineering organization to deliver the scale that we needed. And it was huge, like we got to 42,000 nodes. You still can't do that with OpenStack and it's been six, seven years. That's particularly frustrating to me, but it kind of goes back to as somebody consuming an open product that even might have commercial support for it, you don't have as much leverage on that because it's ultimately tied to the community and the release cadence cycle of OpenStack itself. And it's extraordinarily hard. So then it becomes your fiduciary responsibility to focus on, okay, we can only do this. We can't boil the ocean to completely transform our business. We have to do more iterative consumption of this technology, improve that each point works as we go and expand as we go. That's hard to do. Okay, so we definitely cannot end on a note if proprietary solutions are better. So let's take one more question from the audience. Hi, my name is Raj and this is my first OpenStack.  So my question is regarding choosing that first project for a POC and a lot rides on it because you're kind of building the credibility of OpenStack as a technology that can be used within my organization, right? So if I look at all the use cases and at least the ones that are out there, front and center, what I'm seeing is that most of the use cases have something where the application that's developed is very custom. It needs to scale to something like 2000, 3000 nodes and things like that. So is OpenStack a viable choice for your traditional three tier? I'm running an app on Microsoft SQL Server or Oracle. Is OpenStack a viable option to move that kind of workloads into OpenStack? Or it has to be something very, requires custom development, requires scale in order for it to be successful. And we have just a few minutes left between us. So I'll talk fast. So it absolutely depends on how you compose the cloud. So take something like Nova and Cinder and Neutron, part of the power of it is extensibility. There's a lot of different plugins and different options. So I guess I contend that the capabilities of the cloud you end up with are determined by that which you compose it with. So if you intend to, for example, deliver like high SLA storage with fully open on commodity gear capability, it's probably not the right fit. But it happens that there are back ends in the storage sense that can provide terse quality of service capabilities and other differentiated storage capabilities that align to those classic POSIX built applications for which it would be appropriate. I'm not going to suggest it's completely smooth sailing. There are some things that aren't quite there that aren't fully provided for. But I can definitely tell you, just as NetApp, we have in the three digits of production customers. And among them are some of the larger enterprises, largest enterprises, at least a few of whom are actually replacing enterprise virtualization with this, inclusive of all of the applications that they're delivering. It's not without pain, but they see the ROI down the path. I'll just ask, what business outcome are you trying to achieve? Are you trying to accelerate the ability to affect change and introduce change into this three tier application? Or are you trying to save cost? Certainly the former is more conducive to what OpenStack will provide for you. If you're really just moving it as is and there's really not much more change gonna happen to it, I think you're kind of wasting your time in that particular vector. And I would maybe look for something that's completely net new. And it was covered pretty well in one of the keynotes this morning. In the bimodal, the newer innovation side is more akin to what OpenStack and even Amazon, for that matter, are aligned to. Mostly the mode two is where it happens. Oh, two, yeah. So we, unfortunately, are just about out of time because I have 30 more questions to ask. But thank you to our panelists all for joining. And I believe there's beer, but for those who would like to stick around and ask some more detailed questions, we're here. Thanks all for coming.


So we're going to talk about productivity and this core belief that we all seem to be carrying here about I'm not doing enough I'm not doing enough and this is a question from Lara and I'm going to answer Lara's question with some pointers about what to do with this kind of belief and you know a real it's It's it's it's a felt sense that I'm not doing enough. I need help. I need help doing more, right? So we're going to talk about well some of the thinking patterns around this and also Ways to simplify things so Lara's question is David I want to thank you for creating your in-depth course. It was insightful and helpful and This is the course on procrastination on my website and I've been struggling with this issue for as long as I can remember I Felt relief and support from you with every video I watched from the course and your understanding of the issue really spoke to me and Your generosity and compassion was palpable You have been a godsend truly so thank you Lara for that If I may and you may I Would like to request some support with making a schedule for working from home for adult professionals So I've been following your scheduling system Enjoying my breaks and working in 30 minute slots So if you don't know the the approach I take is a big elaborate plans for the day are actually unhelpful Because quite often we make these good intentioned plans well intentioned plans and then fail to follow through on them and then feel guilty So my approach is all about ending a cycle of feeling the emotion of guilt Once we can remove guilt by not making elaborate plans But taking it step by step making small commitments and having really clear boundaries with your work The guilt goes away and the productivity just naturally improves by itself So that's been working for Lara and what I have found is I am not able to keep up with the workload Because I only end up doing a few hours of work per day. I Enjoy what I do, but I would like To also be able to get more done Please let me know if you can help me out or perhaps this will be a good topic for a video Thanks for the work that you do So Lara, thank you for that and I want to just point something out. Okay What you're doing here first of all is Fantastic, you should be giving yourself a lot of credit for the fact that you're actually consistently engaging with the work But we'll talk about that. But one point I wanted to make is that So many of us have this idea that I'm not doing enough Right now the Bureau of Labor Statistics actually did some research on this and they observed people in their daily work And what was the average amount of hours that people were actually working, you know, not talking with colleagues or not taking, you know Online shopping or something like that, right? You remove all that stuff and they found out that on average People are doing about two hours 53 minutes of actual work per day so Let's just Gain a little bit of perspective here about the significance of this problem Okay, the fact that you're doing a couple of hours of work a day Okay, maybe you want to improve on that you're open to improving on that. That's absolutely fine But you have to give yourself credit this we don't want to start framing this as oh my god I'm I'm terribly unproductive and I need to do something urgently about this Let's start off with some validation for where you are and that goes to everybody watching this video We have to validate and come to accept and encourage ourselves from where we are right now today Self-improvement is all about someday in the future. I'll be good enough and I'll be okay And then I'll deserve some validation and self-compassion It's essential that we start to give ourselves some validation right now Where we are so because that's going to be more helpful moving forward here So I just wanted to point that out, right? We we we go into these social comparisons of other people must be doing a lot more work and in truth I mean, there's statistics on it. It's about like two hours 53 minutes a day So we got to see where we are right now as a win and with procrastination if you're struggling with productivity and We're not doing enough All we really want to establish here And maybe you're not you're not doing as much as Larry's right? All we're trying to do a procrastination fundamentally is raise our baseline of consistent daily effort from what is our typical baseline if we have procrastination as an issue It's nothing days will go by when I don't do anything. I certainly had that issue So all the success here to start off is raise my baseline from I can't do anything today I procrastinated all day. I didn't do anything to I did something today The difference between something and nothing is everything, right? So yes, we can look at increasing how much we actually do But it is a success already if you have consistently raised your baseline to some small step forward towards this goal as opposed to been paralyzed by procrastination and not being able to take any action at all what I always say is yes, we see we see where we are right now as a win and Once we start to develop this consistency The philosophy becomes can I can combine consistency with rare moments of Greatness or rare moments of days when I can and feel inspired to do a lot more work so Why I like that is it's about emotional realism There's not it's not going to be the case that every single day. I'm going to be hyper productive Some days I'm not going to feel so good and all I'm looking for is can I raise my baseline from zero to anything? that's the consistency piece and then there will be days when you feel more energized more motivated and Those days you can enjoy and see how far you can go with your productivity So combining consistency with rare moments of greatness Because it's emotionally realistic to do that Now what I would say a few pointers here is Okay, if you if you really want to start to look at now, can I really start to push on my productivity? The first session of the day the first productivity session of your day is by far and away the most important one Okay, so that's because if you if you can do something productive early in your day it will make it much more likely there's a this psychological momentum that starts to build and Because of the the positive emotion that you will feel from that first session. It starts to make subsequent productivity sessions Seem a lot more enticing Okay, so what I would suggest is what we're trying to do productivity is get out of indecisiveness So when you wake up in the morning you do your morning routine, whatever that might be You might even do some journaling or self-reflection or something like that But then pick your start time for your work first thing do it early, okay? Now if you know anything about my system of boundaries with work I'm not saying be productive first thing I'm just saying end the decisiveness and pick a time for when you intend to start early in your day If you don't follow through on that There's an many videos. I've made about what happens when that happens in when that occurs Which is really about enforcing a boundary With it and stepping away from work, but I'm not going to get into that too much here The point they're making is pick your start time very early. That should be your first priority every day Because all we're trying to do is get out of the indecisiveness Okay, procrastination is really in decision I should start don't want to start when should I start maybe I'll start soon And then this this pattern of maybe I should start soon goes on all day So what we want to do is make a decision Now it should be a loving decision. It should be a compassionate encouraging decision about well Maybe I need some rest first with that this point in my day. I'm going to start So that's the first thing we can do make that decision as early as you possibly can That will help and also if you can hit that first one it will make all subsequent productivity sessions very very Very easy much easier the other thing to talk about here is yes We're focused on productivity here and there is a part of us that needs productivity and needs to take responsibility and That's a very valid emotional need, but I would also suggest Look at your other emotional needs outside of productivity. There's a book I have on my website It's called forget happiness. It's all about what are your emotional needs? And the idea is if you can find out about these other emotional needs that you have outside of productivity and Start to meet those emotional needs what you're going to find is you're developing emotional compliance with yourself There's no longer this emotional stuff that is resistant to taking steps forward with productivity because it feels that they feel that they're their needs have been met There's five basic emotional needs in the model that I use and you can find it find that in the book But meet your own emotional needs master meeting these other emotional needs. You can do that very quickly It's not actually that hard to meet your own emotional needs It's not actually that time and energy intensive at all But that will certainly lead to a lot more compliance in your in your desire to be productive productive So the other thing is boundaries. Okay. Now again, we're just looking for a baseline and consistency with your effort here So you might say to yourself, okay We're talking about boundaries with your work Try and have a minimum amount for yourself every day for okay Zero is not great. I want to avoid days and I'm not doing anything towards my productivity goal What's the minimum I'm looking for here? And again, as I said, if you can reach that minimum, it could be 30 minutes Give yourself a pat in the back. The other thing is what is your maximum for today? So you're talking here Lara and this question about well I'm doing a couple of hours a day and it's I'd like to do more now I am not hearing what is an upper limit for the amount of work that you're going to put in this project Every day and that's an issue because all we're trying to do a productivity We're not trying to become super disciplined or anything like that. The only issue of productivity is That your nervous system needs to be compliant Now your nervous system when it hears all I have to commit to today is 30 minutes It was okay. I can do that so it seems achievable. This is why we have minimums Minimum today is 30 minutes if I can do that pat on the back and now I'm into kind of bonus territory anything I can add to that is helpful But we also add but there is an upper limit to the amount of time I'm going to put into this Now whatever that number is going to be for you Lara is a personal choice but just by having an upper limit of Today the maximum I'm going to do is four hours It could be five or whatever the number is for you personally When your nervous system hears you make that that commitment to limiting your exposure to this project It starts to become much more compliant because it realizes. Okay, she's not going to expand all our energy Which I need to keep her safe. The nervous system is all about safety. It doesn't care about personal gold If there's an upper limit the nervous system will hear that and say okay, I can I can do that That seems okay Now I'm not saying you have to reach the upper limit I what I'm saying is if you get to the the upper limit that you said you must stop working for today Once you make that commitment to your nervous system to your body You have to step away from it. So be super strict with that. Again. I've said this in many videos before the person who can't stop work is This is in the workaholism kind of category we're talking about here the person that can't start work is the procrastinator Both of them have a problem with boundaries Right when should I start when should I finish? It's the same problem. So boundaries in this whole issue is essentially important to look at Now one final thing about the psychology behind this This is not a trivial point. I'm going to make here We have this this inner dialogue it comes from childhood It comes from self-help to be honest and self-improvement. I'm not doing enough. I'm not doing enough I'm not doing enough and we look around and we make comparisons and everything else If you take it day by day and stop worrying about the intentions for tomorrow next week I need to become much more productive. I Want you to start changing your story about today. Just focus on today Today I Did enough work for today now. I'm not talking about tomorrow or next week Your story really that inner dialogue the self-talk should become I always do enough work each day Every day I do the perfect amount of work This is the kind of dialogue that we want to be talking about here And remember it's not saying just because I did this much today It means I'm going to do the same amount tomorrow You can be open to doing more tomorrow and next week, but today I did enough work I always do enough work every single day. This is the story We want to be telling ourselves because it's that encouragement piece. That's missing for most of us so take a day by day and Give yourself some some positive feedback on that's okay. I did something today. That's that's good enough for today So Laura, I hope that's helpful The big thing I guess from today's video is this social comparison of other people are doing more than me Statistically speaking, that's probably not as true as you think it is So just keep that in mind and for anyone watching this the takeaway I want you to take from this video is just focus on increasing your baseline From nothing to anything anything you can do any small step towards your goal Here's a really great thing. You don't even


Today I am back with a new series for Borderlands 3, a series where I showcase your guys clips to the world. Today marks the first of my Borderlands 3 Top 5 series. How's it going guys, my name is dpj and today I bring you another BR3 video. If you do enjoy it leaving a like really helps me out and subscribe if you do want to see more. Also guys before we go any further for all your gaming needs no matter the platform you play on with great weekly deals check out g2a the link to that video description. So doing top 5's have been quite popular with covering over a thousand top 5's in the past from various other games but I think it's time to start afresh with Borderlands 3.  So that's it people, let's show the world your clips. So this first video is basically a demo or concept of how they will work just to get you guys attention so you can submit those clips you have. The clips you'll see today are just quickly gathered from a couple of pals, myself and a couple of people on discord, nothing spectacular and what you'll witness today I wouldn't really base this whole series on because obviously it's going to get way way better. So the kind of clips you should submit if you have them or get any are funny moments, wtf moments as in what their flip, amazing or lucky loot drops, something out of the ordinary obviously for example you open up a toilet and it drops out through legendos is actually happened to me once. Two or three legendos when I open a toilet I mean pretty cool.  A weird glitch or bog and no I don't mean the current state of mayhem 10. Even a unique build you haven't copied from anywhere else demonstrated by destroying a boss and submit that, that would be absolutely great. Obviously without the inclusion of mudded items though. Now clips of old I will accept but ones relating to builds I think I will give a miss, demonstrate any good build you have people upon mayhem 10 as I don't think anybody wants to see old builds within old mayhem molds. But clips in terms of lucky loot, wtf moments, funny moments and things like that, the date on them doesn't really matter much. But there are rules to follow people and they are. Clips must be recorded and submitted in HD. So note recorded with your mobile phone please. Clips recorded on your Xbox also can be found, Xbox clips and Game DVR, both I will link within the video description, you go to these websites, search your game attack, find your clip and then link me the URL to the submissions email, which is on screen and linked within that video description. Clips recorded via Playstation I do believe can be directly uploaded to YouTube from the console. From there, link me the YouTube URL to the submissions email. Clips under a certain size can be sent directly through email but make sure quality isn't lost via compressing the files down to fit. Clips submitted cannot have music playing in the background, such clips will be ignored but obviously if it's in-game music that's completely fine. Just don't get adding any M&M to your clip and then submitting it to me. If you have multiple clips to send, do so within the same email, just so you don't spam. And also leave a brief description of the clip or clips you are sending, just so I know what I'm looking at. Now the few clips you'll see on screen now are just a demo of what can be sent in, and this one right here is what happens when you leave someone's lobby but they are in choo roo. Or this one here by Benedict Ward. Zane's super speed allowing him to almost become Superman making an incredible jump. Or this one here by Lastella. Killing three unexpected teammates at the same time, like wow. And this clip here by Dead School Five at all A's. Now I'm not sure what's happening with this enemy here, I mean it seems like he's kind of stuck, he's elastic-y, just absolutely crazy. Now this is a real proper bogging out, it really is, and this is the kind of clip I'm talking about. And what about this one here by Jason D. Killing Grave Ward, Mayhem 10, one shot on Zane with that yellow cake. I know people will say this is easy, it's yellow cake, but at the end of the day it just takes great timing with that shot. And being smart with that Digiclone 2 saving yourself. Great, great clip. So yeah guys, anything you feel the world would be interested in seeing. Submit those now. The email address which she's on screen and linked within the top of the video description is top5borderlands at outlook.com. So yeah guys, let's get this series going and submit now. On that note, we have come to the end. If you guys enjoyed it, leaving a like really helps out. If you're new around here and want to see more top 5 borderlands, be sure to subscribe. And if you never want to miss a video I upload, you can turn notifications on by hitting that bell button. But guys, thanks as always for stopping by. Hopefully you enjoyed the video and hopefully I will see you on that next one.


And welcome on the first day of December. Good to see you all. Looking like it's going to be an interesting day. Couple of good little moving stocks that are going on. I think a lot of you guys have been benefiting from this ALT, right? Let me hear a little bit. Anyone wanna be a train that ALAT?  Big buyers showed up right around this $4.20 right here and after that, things just went just skyrocketing. It was like two bucks. Good, good, good to see you. Linda, new trial member in the side group room. Welcome aboard. Good to see you all. Alex, good to see everybody. All right, everyone. So a couple of good things happened yesterday. Pre-market was off the charts again. And I don't know if anyone saw my reel that I did on Instagram, but the VVOS was a phenomenal run-up. I just wanna bring that up because I wanna show you what happens with these stocks. So anyway, that stock had a very, very crazy run-up. You could see there that was a big run from Wednesday started in the pre-market, really, really cheap. Hovered right around $12, ran to about 18, sucker ran all the way to about 48, was a phenomenal, had a couple of good moves, but you could see that this was a short squeeze. We saw it coming. We know how to trade short squeezes. I know you guys, students were in class with Josh yesterday, and we did cover a lot of level three and time in sales. And you know what? You could get scared at it, but when you get better at it, you'll know how to trade these. That stock was a phenomenal run, but that wasn't the real big thing that I wanna talk about. There was a lot of crazy good run-up that we had another one that did it yesterday, which was SNGX. I mean, right out of the gate at 9.30, this thing just popped from about 60 cents, got halted, went to $1.10, shot up to about $1.90, came back down. Obviously, you know where I'm going with this, right? You know, the time went to trade, went not to trade. Everyone out there watching on YouTube and Facebook and everything. So that one did exactly that, but it was a nice, nice, cheap, inexpensive stock, SNGX. Snapchat was also pretty good yesterday, but then it kind of died. Had a really nice big move early, and then just kind of a little slingshot right here, snapped it well. AMPE was another great run-up yesterday. Look at this stock. This was a stock that ran in the afternoon. You can see here at 4.30. You know, we have two very valuable times when we do our events. We do one at 9 a.m., which is right now, and then the afternoon. I'll show you it again, okay? The green is the best times.  So that one worked out pretty well right there. You can see how we had a nice little run on that one. Stock ran from 3.30 all the way to $7.00. What a beautiful, beautiful, trending stock right there. Nice little run. What else we have? We had a couple other ones too. SNFL was also a nice little short squeeze, about $2.00 stock to $5.00. AGRI, another short squeeze, another dollar to about $3.00, and came back down, and last but not least, IMNM. That was all right. That thing gapped up huge in pre-market. It's just a great runner-up. You can see it right here. A lot of you guys did really well in the pre-market on that one, and then after that, it kind of like died. And you should have been done just on that alone. So it was a shockingly very active, lot of stocks moving yesterday in the early mornings. Now regarding about the market, listen, the market was moving up pretty nicely yesterday.  Huge run-up. You can see here on the Dow, what a great run-up. But you know what's crazy? I was looking at some of the stocks that were moving yesterday, some of the brand names, Tesla didn't go up. What we have right here, what else we got up here? Google didn't go up. A lot of things didn't go up. Microsoft didn't really go up other than that. It did move a little bit with the market. I mean, a lot of the brand at Amazon, you know, I'm just bringing some of the last bit of things. But these things did pop, I guess, right at the end, but they didn't have that big run-up that I thought they were gonna have with the market. Must be other stocks that are moving that made those Dow's that move. But the S&P and everything else, this way you gotta be a little cautious, okay? So obviously good news, they come out around 330. That's what you could see what happened there. But going into December, I just wanna give you a heads up. I'm out of all my swing trades. I mean, I got my investments long-terms, whatever, but we are at a major, major, major, major resistance levels. S&P is at 4,600, the Dow Jones right now is just kind of broke through that big resistance levels right here. That's probably where you got that pop right there. But I'm a little skeptical right now. It's Friday, it's the first day of the month. December, people are trying to close out their positions. They're taking care of tax stuff for 2023, getting to 2024, which we call a lot of mutual funds and hedge funds, they're all gonna be doing that right now. Even some of you probably your accounts are on the phone with you and telling you that. So it's a really kind of weird month to trade, but it's a great time to learn. So there's no better time to jump in the cyber group. By the way, if you're watching on social media, like we always say, take your phone. You got that little QR code on the top left hand side. If you wanna join our trading room, you're more than welcome to join us. And you can see what we do all day long with our traders. So please go out there and make sure you like us and friend us. Now, let's go over what's talking about what's moving this morning. Cause this morning we had some really, really nice moves. I was actually quite shocked. First of all, there's this one stock that just got halted. Oh, did it open up? I'm not getting any quotes right now on level two. So it must be a penny stock. If you don't get any level two quotes, that means the stock is not on the Nasdaq National. But you can see, my God, it's getting crushed right here. Look at that, $4. It was all the way up to about 11. I'm just looking at time and sales right here. So I don't know what the story with this stock is. I'll probably not gonna know until the market opens up, but it is up around 200% right now, NEXI. And we'll go out there, we'll find out in the news. We'll go to our buddies over there at Benzinga. We'll check out the news on that and we'll share it with you guys. But the real nice mover this morning was the ALT. So what a nice little pop right here. Yesterday it was on 320. It shot up to about $5. Yeah, I don't know if that was probably earnings. It looks like maybe an earnings play. But this morning it moved great. You can see how it started around eight o'clock this morning at 4.20, ran to 5.20. Now regarding about orders, I got a couple of orders that are showing up right here. Why does it stay freezing up on me? It's starting to freeze up on me. There we go. I hate when it does that. So we got a big seller right here around six. It's not huge. It's not really that big. It's about 15,000, 5,000. So right around $6 is having that tough time breaking it. So you could see how it hit it there right here. And it kind of like backed off right there. That has a lot to do about that big order out there. If he releases it or he gets executed, which we cover in class. I mean, it was somebody at seven, which is a dollar away, but he just pulled his order. But that's the stock we really want to keep an eye on this morning. I know a lot of you already jumped on it in pre-market. Once again, if you're on social media, you can always come and join us and see how we trade early in pre-market. But that one's going on the watch list. And always remember, like yesterday, it's never too late to trade. The market's not even open yet. Only for us traders that have access to pre-market. This stock I also found this morning, I was looking at, there's nothing really going on.  You know, you could see that there are buyers here at $1.10, $1.20, not really going anywhere. It did trade six million shares. It is a cheap stock. It did have a short squeeze.  It ran from $3 to almost $14. And it did that a couple of times. So it is going on my list, okay? Because who knows? It might be quiet now and it could be that sleeper. We've traded it. We know how it trades. We put it on the watch list. This stock got destroyed, okay? I don't know what happened to this thing. This thing got hammered. It was, I don't know, did you ever see a $10,000 stock end up being a $10? So that must be a reverse stock split, reverse stock split, reverse stock split. But you know what? It's up today and that thing is down about, do you imagine you want to stock at 11 and it goes to $10,000 next year? I don't know, have we ever seen that before? I don't think we ever seen that before. We know we have seen before. We've seen a $10,000 stock go to $10 and you're seeing a one right now. But you know a big bottom fishing person. I love stocks like this. Who knows? It might come back. It might get a little bit of a push here. So let's put it on our watch list, PIXY. Who knows? Maybe, you know, it's up 30%, 300,000. It's number four on the list.  What else we got going on here? This one right here was a nice little trader. We traded this last couple of days. It had a good move, CMNX. It's moving up, okay? It's a medicine stock. So it must be a pharmaceutical stock. It's up about 25%, million six already traded. Spreads a little wide though on that CMND. Listen, you know how we feel about Fridays, okay? And especially today's the first day of the pay period. Nobody likes to get super nuts. But we're already at 24% and number seven, I mean, there's a lot of stocks that are moving on a day like today. We just need volume. This one's 12%, ultra. This stock is, wow, this one's up today. Wow, I made it number 10 on the list of $50. Good for ultra. I think that's the, I don't know if I remember correctly from my memory, but I think that's a makeup company. One of the biggest in the world. Anyway, well, it's trading at 400, so it has to be, right? Let's check out the losers. What's happening here? This is another one that we saw yesterday. Getting destroyed. Yeah, it's beauty supplies. So, wow. So I guess it is cosmetic. So I remember, okay. There you go. This one's getting crushed, but just when you think like you own it at 100, the thing can't go any lower and that's what happened. But it had a nice little move a couple of days ago, but we're not gonna be trading that one. New York Stock Exchange, you don't get too much in New York. I saw this one, PAPL, you know, it's, but it's an IPO. It's new. It's up a little bit this morning. I had a big popper at eight o'clock this morning right at the 320, down back down to $1.40. Do I have it up here? Yeah, I have it on level four. What do I got going on here? Okay, so there was nothing that explained why it came down around eight o'clock, but we are getting some channeling going on between two and we're getting this $1.50. Lot of, I mean, not a lot of big iceberg orders, but it did trade 1.2 million shares. I'll put that on the watch list, PAPL. Could be another sleeper. Anything else out there? This one has some good volume, $22 stock.  All right, so we've got a pretty good, we've got a couple of good stocks out there. We've got one, two, three, four, five, six. All right, anything else, everyone? Anybody in there? Anyone else? We're missing an integer and missing. I think that's pretty much does it. We got, so I'm gonna post this.  So you guys are gonna get it first if you don't write it down fast enough. Just remember, everyone, today is Friday. Don't get too cocky. Don't get too greedy. And you know, just try to make your days pay. I know you had a crazy week this week.  So listen, if you missed them, don't worry about it. We'll get another one next week. Tuesdays, Wednesdays and Thursdays are always the best days to trade. But just make sure you go into your classes. Just be careful on your swing trades and some of you are on your options trades. All right, everyone? Thanks, everyone. We'll be back. Don't go anywhere. We'll go live in about 15 minutes. Once again, if you're on social media, you can always join us to click on that little link or take your phone, scan that QR code on the top left-hand corner and you can come and join our trading room and be there all day. All right, see why we've been around for 30 years and the most popular and the most well-named brand in the trading community. Good luck, everyone. Happy trading and we'll see you in a little bit. Don't go anywhere.


Hello and welcome. In the last lecture, we had established the basis for generating a curvilinear trajectory through consideration of a two-dimensional motion model and we had also examined the set of equations for the possibility of extracting the closed form solutions and we had mentioned that there are three possible solutions that we can obtain which also have a practical utility. So, we are now going to look at these solutions one by one. The first one that we are going to consider in this lecture is a solution that we obtain through the eruption of pitch rate being constant. So, let us begin. So, let us see what are the features of such a solution and how we can obtain it. In this case, that is the case in which we assume the pitch rate to remain constant throughout the trajectory. The rocket is commanded to track a specified pitch rate d theta by dt so that velocity solution is obtained directly as shown below. We know that theta dot which is the pitch rate is a constant.  Then we go to the second equilibrium equation that is theta dot equal to g a tilde sin theta by v and we directly get the v solution as g sin theta by q naught. So, we see that v is a sinusoidal function of theta and is also inversely proportional to q naught indicating that we are going to get a higher velocity for a higher theta and for a lower q naught value. So, what are the features of this solution that we have obtained just now? So, we note that if q naught is a constant throughout the trajectory including the starting point at t equal to 0. It has to be valid at all the points. So, obviously the same relation is also valid at the initial point or the start of the gravity turn. So, we can write down the applicable relation for velocity at the start of the gravity turn as shown below and this relation is nothing but q naught equal to g sin theta naught by v naught where v naught and theta naught are the initial values of velocity and the pitch angle theta. Now, as q naught is a finite quantity it automatically means that there are going to be certain restrictions that theta naught and v naught will have to satisfy. For example, if you start from theta naught equal to 0 even though v naught is not 0 your q naught will become 0 and if q naught is 0 that is not an admissible solution. Similarly, if we start from a finite theta naught but if we make v naught equal to 0 it results in finite q naught which is also not an admissible solution. So, we come to the conclusion that both v naught and theta naught have to be non-zero values before we can start our gravity turn. Of course, the reason for this is not far to seek because our gravity turn depends on the normal component of gravity to the velocity vector and for theta naught equal to 0 the gravity vector does not have any component normal to the velocity vector for a vertical motion which obviously means that the gravity turn can also not be started when the vehicle is vertical and that it must have some finite inclination from vertical before the gravity turn can start. Moreover, we also note that not only gravity turn can be started only after it acquires a certain attitude with respect to vertical it also needs to acquire a finite velocity and this is where we need to take a view of how such a thing is going to be achieved particularly because our lift off is basically vertical. The velocity vector is pointing in the vertical direction even though once the rocket clears the launch tower it will have a finite velocity but if it does not have an inclination with respect to vertical you cannot execute a gravity turn maneuver as we have established and this requirement is usually met by giving a pitch kick or executing what is called a pitch down maneuver on the vehicle at an appropriate time. The implication of this pitch kick or a pitch down maneuver is to give a lateral impulse generates a pitching moment instantaneously and this generates a pitch disturbance that starts the pitching motion and because of the pitching motion it acquires a finite theta it is given in the form of an impulse actually so that we acquire a constant pitch at the end of the maneuver which becomes our initial pitch angle at that velocity v0 which is what we treat as our initial time t0. We also need to note from the relation that we have seen for q0, theta0 and v0 that as this is a constraint relation only two of these three can be actually specified and third one will be determined from the constraint for example if you specify q0 and v0 you can determine theta from that relation or if you specify v0 and theta0 you can determine q0 so this also has to be kept in mind while setting up the configuration for a gravity turn with the constant pitch rate maneuver as we have discussed just now. Now let us go to the next equation in the context of the gravity turn that is the velocity equation but you immediately realize that we already have the velocity solution so what is it that the velocity solution is going to give us the velocity solution now is going to give us the mass profile because from the second equation we already have the velocity for a given pitch rate and we already have theta solution as a function of time so the only unknown now left is the mass solution and the tangential equilibrium is going to be used to write a differential equation for mass as shown below. So we are going to convert this into a differential equation for mass through basic calculus based manipulations change of variables so by doing that we can show that the tangential equilibrium differential equation can be rewritten as dm by m equal to minus 2g tilde cos theta dt divided by g0 isp and what we do now is also the change of variable of dt which is converted to d theta through the basic expression of d theta by dt so using theta dot expression we change the variable from dt to d theta now this differential equation if we integrate we are going to get the solution of mass as a function of theta and not an explicit function of time but we also realize that as theta is already an explicit function of time by substituting that solution into the mass solution we can also generate an explicit solution for mass in as a function of time so we are going to have the velocity and mass and theta all as an explicit function of time so let us go through with the integration process and we find that this leads to the basic result that ln of m0 by m is 2g tilde by q0 g0 isp into sin theta minus sin theta naught so this is the solution for mass fraction that is executed under a constant pitch rate maneuver so we find that similar to velocity mass is also a sinusoidal function of angle theta and also inversely proportional to q0 so if q0 is small the mass fraction is going to be larger now what is the implication of m0 by m being larger the implication is that m by m0 will be smaller so that we will require a larger propellant to support a larger velocity which is going to automatically result for a smaller q0 that we have already seen we also note the converse of it that if you use a large q0 we are going to get a smaller terminal velocity and if you realize an important fact that by appropriately choosing a q0 value it is possible for us to design a trajectory that is going to have different terminal conditions and conversely it means that if you want to achieve different terminal conditions you just need to tweak your q0 value which is going to be not very difficult as this would be just the part of your control algorithm where you may want to define a different reference for a constant pitch rate solution you need to also realize that as the trajectory solution is extremely sensitive to this q0 value you need to be very careful with the selection of this number as we will see through an example that we will conduct next but let us now look at the solution for time and solution of time also as a function of mass so because now there is an interplay of variables we can express different variables in terms of different quantities so if we are given the starting and the terminal condition along with q0 we can directly get the solution for the flight time that is how long the mission will last on the other hand if we are given the mass and initial condition it is possible for us to determine the terminal inclination through the mass profile specification so if we know what is the burn out mass and what is the lift off mass there is a mass fraction if we know the initial angle and if we know the pitch rate we can directly calculate the terminal angle through this trigonometric expression the last two solutions correspond to the trajectory parameters that is the profile in terms of the altitude and the horizontal distance so let us first take the altitude equation which is nothing but our dh by dt equal to v cos theta that is if I take the vertical component of the velocity and integrate it I should get my altitude so again we do the same trick of changing variable from t to theta and then we get a differential equation for h which is a simple differential equation of g tilde sin 2 theta divided by 2 q0 square if we integrate this I leave this for you to verify the integrating complicated expression you get h as a function of theta and as you know theta is a function of time so we can also obtain h as a function of time now we find that h is a cosine function of 2 theta and we know an interesting feature that for theta equal to 90 degree the altitude will reach its maximum value which is a result that we already know from our projectile motion this is something similar to the projectile motion that we have seen in the basic rigid body mechanics let us now look at the horizontal distance solution as the solution of the differential equation dx by dt equal to v sin theta so again we do the same change of variable of dt into d theta and arrive at the integrand that is g tilde sin square theta by q0 square this is a simple trigonometric integration and now we get a solution for x as containing two terms theta minus theta naught and sin 2 theta minus sin 2 theta naught let us now see all these relations through an example that we have been following from our first idealized solution case but the fact remains now that we cannot really start our gravity term with velocity and theta equal to 0 so we assume that the vertical lift off has only occurred for some time and at the end of that vertical lift off a small pitch kick has been given which has resulted in an inclination from vertical off about 5 degree and by this time the vehicle has achieved a velocity of 85.4 meters per second of course in the process it has consumed 6 tons of propellant and it has also acquired an altitude of about 415 meters let us now assume that from this point forward we are going to conduct the gravity term maneuver and let us try and find out what would be the terminal parameters if we conduct a constant pitch rate maneuver for the next 90 seconds assuming the sea level gravity so in this case I have specified the time I have specified the initial angle and I have specified the velocity which are the only parameters that I can specify all other parameters now we can calculate using the expression so let us see how those parameters can be calculated and what their values are so q naught which is g tilde sin theta naught by v naught comes out to be 0.01 radians per second which can be converted to degrees per second as 0.57 v degrees per second the moment I know the q naught I only know theta naught so I know theta at 90 seconds that is theta naught plus q naught into the delta t which is 90 and if I do this I get an angle of 56.6 degrees so this particular trajectory when executed will result in the inclination from vertical as 56.6 degree at the end of 90 seconds we can also use the velocity expression that we have derived for obtaining the velocity at the end of 90 seconds which uses the theta at the 90 second of 56.6 degree and gives the value of 890 meters per second so that is the velocity at that point now with theta 90 known and q naught known we can solve for the mass fraction m naught by m 90 which comes out to be 0.62 and through that we find that mass at 90 seconds would be 39.7 tons so please note we have started from 74 tons and at the end of 90 seconds 40 tons of mass is left so which means that we have approximately consumed 34 tons of propellant during this process which effectively means that we still have about 20 tons of propellant left and during this time we have acquired an altitude of around 34 kilometers and have traveled about 26 kilometer over the surface of the earth which is not a very large distance so possibly our flat earth approximation is still valid now let us explore this problem a little further as I had mentioned there is still about 20 tons of propellant left but and we have not reached 90 degree which in many cases would be a requirement from terminal conditions so let us hypothetically say that we would like to reach 90 degree and we want to find out if by burning the remaining 20 ton propellant we can reach 90 degree obviously we know that the time will not be 90 seconds but it will take a little longer time but we are not sure we don't know whether it will happen or not so if it happens let us try and find out what are those burnout parameters which we are going to get but if it does not happen then let us find out the reason as well as to say that when it reaches 90 degree what would be the final burnout mass I will leave you to work with the formulae that we have derived now that we have seen in the previous example those formulae I suggest that you become a little bit more familiar by practicing them and you will find that it does not happen in fact you see a very very surprising result that from 56.6 degree that is for 90 seconds to 90 degree it just requires an additional 2 tons of propellant from 39.7 tons to 37.4 tons by burning additional little more than 2 tons of propellant it has covered an angle of practically 34 degrees so by the time it reaches 90 degree you still have about 17 tons of propellant left which obviously means that we will not be in a position to consume all the propellant by the time we reach 90 degree so this brings us to the conclusion that there is some disconnect between the rocket mass configuration the propellant and some of the trajectory parameters that we have assumed so please note an important parameter that we had assumed was theta naught because that is something which was to be given as a pitch kick and it is something which is under our control and it was somewhat given in an arbitrary fashion there was no reason that theta naught would be applicable in the present case so now let us invert the problem and try and find out that theta naught which will make this particular mission feasible from a design perspective that it will burn all the propellants it will reach an angle of 90 degree let us try and find out what is going to be the theta naught that will make it happen and that is going to be a design solution so that that is the theta naught that you are going to give at the pitch kick point and with that you should be able to execute the trajectory as desired so this is the exercise that we now conduct of course we know the final mass fraction because we want to consume all the propellant so we know that the mass fraction is going to be 4 that is m naught by m b is going to be 4 and final angle also we have specified as 90 degree so now we are required to determine the theta naught for which the solution is going to be possible and that can be obtained through simultaneous solution of two non-linear equations one corresponding to the mass fraction and other one corresponding to the final angle so if we do this in fact I suggest that you do this exercise yourself you will find that for theta naught equal to 3.01 degree such a mission would be feasible but it may take 252 seconds to complete and in this case your q naught is going to be 0.345 degree per second instead of 0.547 degree per second that is what we had taken earlier so which means we are reducing q naught and as we have seen a reduced q naught automatically results in a higher burnout velocity so now we have instead of 816 meters per second we have double the velocity that is 1.63 kilometers per second also the altitude which was around 35 kilometers has gone to 135 kilometers and horizontal distance which was around 25 kilometers has become 212 kilometers so you realize that just by a small tweak of the initial angle from 5 degree to 3 degree there is a great change in the trajectory with the same propellant mass and now you realize the value and the potential of the gravity term trajectory through a constant pitch rate maneuver realize that the possibilities of generating large number of trajectories that you may desire from the same rocket just by suitably tweaking your q naught and ensuring that q naught is maintained throughout the trajectory therefore to summarize it is possible to obtain closed form solutions for trajectory under the assumption of constant pitch rate we also note that the solutions so obtained fixed at the trajectory time once the starting and terminal angles are specified. Hi so I hope you have realized that gravity term maneuver is an extremely powerful tool for designing the ascent mission trajectories what we have also not explicitly stated but can be seen from the various relations that we have obtained that for given terminal conditions it is possible to also determine the rocket configuration that would achieve a particular trajectory configuration so you realize that a simple constant pitch rate assumption has provided us with an extremely powerful tool in the next lecture we will look at the other two tools that is the constant t by m and a constant velocity so why see you in the next lecture and thank you


With Veterans Day fast approaching, Thacker Memorial Funeral Home in Pikeville has been busy preparing for their annual Veterans Day Remembrance Celebration. Recently, we sat down with Funeral Home Vice President Rolly Wells to find out more about this special ceremony. At Veterans Day event, we begin at 11 a.m. on November 11th, which is Veterans Day. It's at our Annie Young Cemetery, which is going to be at our flagpole there on top of the hill. We'll open with Richard Meek, he is a minister for Justice Field Bible Baptist Church. Then I'll do like our opening speech. We'll have David Taylor, who is a local singer. He'll do God Bless the USA. Then Donnie Hall, he is with the Voice of Victory Church. He will introduce Brother Lee Watts. Brother Lee Watts is actually the missionary to the Kentucky State Capitol. Then we have Johns Creek DAV, which is the 166th chapter. They'll do the presentation of colors and distribution of the flag. And then we have Jordan Gibson. He'll do the national anthem. And then we have Tommy England, who will do a benediction. Then Larry Thacker, which is our actual owner, who started the cemetery in 1986. He will do our closing. It's a beautiful service even before we started it in 1993. So, I guess we're going on 30 years now. When it's all said and done, though, you can look around our cemetery and see all the flags that are on our hill, because we do mark every veteran that has a marker on our cemetery. But we actually get to see the veterans that did serve there who were in attendance. And that's what Veterans Day is about, is acknowledging the veterans that are still living. Here at Pikeville Medical Center's Heart and Vascular Institute, we have assembled a comprehensive team of cardiac specialists bringing expertise from all regions of the nation and the world. We have coupled that with cutting-edge technology, providing them the best equipment and operating rooms available. The result is comprehensive cardiac care for the people of our region that is second to none. The Heart and Vascular Institute at Pikeville Medical Center. As a way of showing their appreciation, all veterans in attendance will receive a small gift from the funeral home. We will be buying every veteran that's in attendance dinner at Happy Days, which is right next door. So if you're there in attendance, we'll give you a card tomorrow and dinner will be on us for tomorrow. Wells hopes that everyone who is able will choose to attend the event as Veterans Day is of particular importance to her. I took care of a family of a man and they have lost a whole, a whole lot. But I went through his DD 214, which was his discharge paperwork. And he had went through, he had went through so many war times, but he was so incredibly decorated. He had, he had so many medals and it was like truly touching what all he had done. And I know that he, that's more of the world. Hey, like I said, but the sacrifice that he made and that his wife made and I think that really touched me more than anything. So I guess Veterans Day to me is more of like the sacrifice that they have to go through and that there's days of birthdays and childbirth and holidays. I know that we miss, but they're missing as well. And they give their life for that. And their families give their lives for that. And it's such a selfless sacrifice that they make. So that's what it means to me is that it's the, it's the littlest thing that we can do for them. For Mountain Top News, I'm Joshua Sloan.


North Korean leader Kim Jong-un said the country's recent launch of a spy satellite was an exercise of its right to self-defense. As Pyongyang celebrated the event as showing it could strike anywhere in the world, state media reported on November 24.North Korea said on November 21 it had placed its first spy satellite in orbit, drawing international condemnation for violating UN resolutions that bar its use of technology applicable to ballistic missile programs, the North's state run. Television released several still photographs of Kim visiting the National Aerospace Technology Administration to applaud space scientists and technicians and hosting a reception to celebrate the launch on Thursday.


Dear Chris, over the past seven years, I've had the pleasure of watching you grow into an incredible football player. But more importantly, I've seen you grow into an amazing person. Dear Chris, I am so happy to have you as my friend. Dear Chris, ever since we were kids, you have been taking care of me from being ride buddies at Disney to the movies to walking trails. Dear Chris, I wanted to make sure I took the time to thank you for encouraging and providing me with hope. Dear Chris, in a time when it is easy for celebrities, athletes and influencers that are in the public eye to be focused on themselves, how people view them and how they can boost their own following, you have always used your platform to focus on the most marginalized in society. From the start, you have naturally had a heart driven towards service. I watched you selflessly give time to those around you so that they always felt special and loved. And now you have been able to use your platform to make an even greater impact. With your hard work, dedication and your kind heart, you have affected many people's lives from helping many teachers supply materials for their classrooms to making a special practice for your local Flowery Branch High School football team. It's funny that we met through an organization named Best Buddies because we really are best buddies. You were so kind and thoughtful. You took the time to ask me about my cancer journey and you truly dared. You will never know how much this means to the millions of individuals and families you have impacted. I have watched you impact the city of Atlanta and beyond. Whether it be taking your best buddy Michael to Mini Golf in Chipotle or supplying the families of the Ronald McDonald House with a night of fun and good food. People may not know what a kind person you are because you are so tough on the football field. I know you are a great friend. Thank you Chris. You being a Best Buddy Ambassador means a lot to me as you are helping others with the same disabilities and struggles as me. Also to helping women with cancer who struggled and continue their fight just like mom did. In closing Chris, thank you for making a difference in my life and I'll explain why.  Any treatment moving forward would merely be precautionary measures. You can imagine how happy we all were. Thanks for being a champion of inclusion for our buddies all over the world. Gratitude and friendship Anthony Kennedy Shriver. We are also very proud of you. Keep being you. Love Madison. You all be best and best buddies. Your friend Michael. Thank you for being a very humble, caring and kind person. One who sees the need and acts. The world is a better place because of this gentle giant. God bless. Know that you and Madison will forever be on my prayers. Mary. But the Chris I just described is the same Chris I knew as a kid. This is why you are being named the 2022 Elena Falcons Walter Payton Man of the Year nominee. I didn't know I was going to cry. It's an incredible honor. It's so touching and I don't think there's anything more personal than a letter but then hearing it in somebody's voice. In all the different ways of how they actually, you know, the different events and how it meant to them. It just means the world and it's just glad that the work that we do has impact and so look forward to continuing to do that.