She was physically abusive.  She was verbally abusive. She, exactly what you said in terms of, you couldn't have picked me a better father to be here. You purposely chose a married man to have a baby by. My mother had me at the age of 14. Right? At the age of 14. She had you. So that means she was pregnant at 13. Yeah. So she had me at the age of 14. At the age of 15, she was a heroin addict. So just imagine growing up where your mother, your biological mother, who's supposed to be the first state of nurturing to you is not that. I had distrust for women my whole life. It was never trust. If the person that can bring me into the world abandoned me in that way, I could have trust the woman who said she loved me. That impacted my whole life to this day. Hey, if you ask me, do I trust the woman?  Yeah. Have you guys seen the video? All right. So to put it in the short version, there's this little kid. I think he's like 10, right? And he's famous, social media famous, because he'll be having conversations with his mom. And he's real witty and things like that. So they were attending this YouTube event slash adult prom looking thing. And his mom was just, I don't know if she was drunk, high or whatever, but she was having a good time just twerking on the back on this other YouTuber. And he was filming while she was throwing it back. And the little boy ran in and pushed her off of him. And he started crying because he was so embarrassed.  When I looked at the comments, motherfuckers were laughing, right? And often when we're trying to have some of these conversations, what tends to come up is, who hurt you? But your mama black and things of the like without understanding that a lot of men's trauma, distrust of women, disdain for women even comes from their toxic mom. And some of women's trauma comes from their toxic mom as well. But I think we overemphasize male toxicity. My dad wasn't there. And we don't talk enough about female toxicity. She couldn't pick a better father for me. The son husband complex, coming in to defend his mom, whether the father is nowhere to be seen. And he's that de facto hubby or emotional tampon, for lack of a better term. He's seeing this. This is my mom. I shared these because he might be mama's boy or what, two chains, a titty boy or whatever. He's just used to being around his mom and don't want no man touching her. And that's probably what he's become used to. You glorify in modern day prostitution. But you might not think so. You know, you always talk about what a man got to do for you. How he got to come to the table? What he got to provide?  But you ain't saying that. But there's so many ways you're saying it. So for me, it's like, where is the real nurturing of a mother? What I see, what I see most of the time is even with women who have children by Debbie dads, what they want to call Debbie dads, how much she plays a role of being more attentive to that male figure in her life, that child that she would do than the person that she had the child with. So she'll love on him. Like you said, she'll jump in the bed with him. She'll show him love and affection. But she won't do that with a man that has done the providing, that has done the financial provision. It's more like, I ain't going to give you that time and attention, but I'm going to give it to him. You know what I'm saying? Like sometime I go through that. I'm like, well, my old lady, we got a little son together. I'm like, she'll say, Rob, come here. She'll just give him all his love and attention. I'm like, but I don't get that.  Like when they want to watch a movie, they're hugged up with the son. Or when they're doing any type of intimacy or want to, I don't want to say love bomb, or basically just get some type of affection. Emotional labor. Yeah, they want the son to take responsibility of that. And even going as far as dressing the son up, like, you know, they're their man. They want him looking fly, you know, so on and so forth. And this even leads up to when he gets into a relationship later on in life, she wants to be the other wife. I had that conversation with my old lady. I told her, your reflection of your mother, she didn't like the hair. She didn't want to hear it. But it hurt her so it hurt her so much that it made her internalize it. When she had to look in the mirror and start making changes. Because when she's seen a mother, she didn't like a mother. She didn't like the way her mother carried herself. You know, their relationship was rocky. So I came in to, you know, to bring a healing to the relationship. But when she's seen the way her mother treated her when she was growing up, they didn't have a good relationship. But she acted just like her in a lot of ways. The most egregious part wasn't even a twerking, ironically. The most egregious part for me was when after he pushed his mom and the dude backed up, everybody started laughing. That was what was egregious, including his mom. Part of the reason, like, you know, people talk about they ain't no man no more. Part of the reason is because a lot of black boys are not taught how to be men, number one.  He was essentially emotionally castrated in that moment. Because his pain wasn't validated. His maturity and foresight, like you put it, wasn't validated. She didn't think enough of him. She didn't respect him enough to think to conduct herself differently in his presence. So he's either going to grow up and go one of two ways.  Or women can do no wrong. Super simple. And we don't realize that a lot of what, because, you know, you have this example that was captured on camera, there are a lot of boys who grew up seeing different men coming in and out in the mom's bedroom. There are a lot of boys seeing how different men at the barbershop talked about their mom. About how their moms pretty much prostituted themselves in the community. Nowadays, we're talking about my mom is on only fans and things like that. And we don't realize we are literally castrating these boys. Because in the future, they don't think they deserve any better than their moms. And it's the same reason a lot of girls end up with shitty dudes because they don't think they deserve better than their dads. My dad was literally distant. So I want a man who's emotionally distant because that's what I'm used to. For me to be the type of man that never had a mother growing up with a mother, I was always the one, the man that was educated enough to try to save the woman. But the woman never wanted to listen. And I went through that for 20 years with my ex-wife. I was the savior, right? Because I was like, damn, I don't want that. You know what I mean? I want to trust the woman so bad that I'm willing to give her everything she needs. But it never played in my favor. The energy was like, I just like being what I am. And that's I am what I am. You met me that way, so accept me that way. But it was always like, why are you not opening up to me? Because I don't trust you. And I'm laying it out there for you. And I'm telling you why I don't trust you. Because your actions show me that you don't trust you. It's kind of like what me and J.R. were talking about. Like on YouTube, the more substantive your content is, the harder you have to work. For sure. And as a man, especially with women, it seems that way.  The brother who is working a lot and because of that, he can't spend as much time with the woman, that's who gets left. And that's who has to not only pay the mortgage of the house he gets kicked out of, he has to finance her and her deadbeat boyfriend. So like, and this is kind of what I've been saying because men are eating this stuff.  It's easier being an ancient nigga. You get better treatment from women.  He's not buying me enough gear. One girl, she was like, the dude, like he lying her house with roses and stuff like that. She looked at the man and said, well, it doesn't quite look like the TikTok videos. Hmm.  And my biggest thing is like, okay, we can complain about that and stuff like that. But the next generation of boys, this boy in this clip that we're talking about, they're seeing this and they have one of three choices to make.  Either I'm going to leave and take my resources to another community, another country to hold nine.   And you have to start telling the truth.  Those niggas get it the worst.  Without mentioning rich niggas get treated on the most. For sure. For sure. Poor guys. Oh, we're going to say he got a good dick just to rationalize it. But they get undying affection and love and commitment in the whole nine. He's at home playing 2K. He don't do shit, but it makes you feel good to take care of this puppy that you have. This grown male puppy that you have. But versus a man who if you could only empathize with the root of what caused his disposition and what maintains his need to be stoic in the whole nine, you would get the sun to move just like you said last time from this man. But again, there's that disconnect and it pisses me off sometimes. But it seems like that empathy isn't there.


Hello, everyone. My name is Matt Tosola. Today I'll be presenting our recent work called Automating Instrumentation Choices for Performance Problems in Distributed Applications with Viya. Diagnosing performance problems using logs is extremely challenging and time-consuming. With the emergence of distributed applications, problem can not be anywhere. It could be in one of the many components that constitute the distributed application. It could also be due to intercomponent interactions. As a result of these challenges, developers heavily instrument their distributed applications. Instrumentations, such as logs, are the de facto data source engineers used to diagnose performance problems in their applications. However, it's difficult to know a priority where these logs are needed to help diagnose problems that may occur in the future. And exhaustively recording all possible application behaviors using these logs is invisible due to resulting overheads. As a result of all of these issues, distributed applications end up containing lots of log statements, but rarely the right ones in the right locations needed to diagnose a specific problem. Currently, enabling the right instrumentation requires manual iterations of test and check. You gather more data from instrumentation, you try to localize your problem. If it's not enough, you instrument more and then gather more instrumentation data. This takes a lot of valuable developer time. It increases downtime for your application. This also comes with additional costs of money. To reduce diagnosis times, researchers have developed automated techniques to choose needed logs for performance diagnosis. However, existing literature have major drawbacks. First of all, they focus on correctness problems, not performance. For example, log 20 helps diagnose correctness problems by enabling logs to differentiate unit co-pads in your application. However, this is not directly applicable to performance problems because fast co-pads, for example, need not to be differentiated for performance problems. And the slow ones, even after they are differentiated from the fast ones, they will require additional logs to pinpoint problems further. Another problem is that some other works are not designed for distributed applications and they ignore very critical context information, which is request workflows. Request workflows are necessary to know information of what services, processes, and methods involved in a user request. Engineers need this context to efficiently debug their applications. For example, log 2 is designed for performance problems. It is indiscriminate because it ignores request workflows, thus will enable logs in the areas of application that are not really performance sensitive or not really contributing to end user requests. To overcome these mentioned shortcomings, we present the variance driven automated instrumentation framework, which we call WAV. In response to needless observed performance problems, WAV automatically searches the space of possible instrumentation choices to enable the logs needed to have diagnosed problems. To work, our framework combines distributed tracing, which is an enhanced form of logging, with the insights about how response time varies can be decomposed into the portions of the request traces. In the rest of this talk, we will be presenting requirements for the automated logging frameworks, then we will discuss our approach for addressing them, we then go through our design and present our findings for empirical evaluation. So let's first review requirements for automated logging frameworks. Past research has argued that logs needed to localize source of one problem may not be useful for others. The lack of one-size-fits-all logs leads to a tussle to identify which log statements are actually most useful and should be enabled by default. For example, Sahar et al. state that Hadoop, HBase, and ZooCooper family of applications have been patched over almost 30,000 times just to add, remove, or modify static log statements embedded in their source code. This challenge results in the following requirements. So our first requirement would be, logging frameworks must allow logs to be enabled selectively in response to performance problems observed during runtime. Let's now go through our second requirement. Even modesty-sized distributed applications will have large search spaces of instrumentation such as hundreds or thousands of possible log points in the source code. For example, we can assume a distributed application that allows log points to be inserted or enabled at every function's entry, exit, or exceptional return. To address this scalability challenge, we refine our first requirement to require logging frameworks to automatically enable trace points. We further read the requirements stating that automated logging frameworks must be also capable of narrowing down the search space when exploring what possible additional logs are needed to localize need logs or problems. Our last requirement would be the following. Existing logging infrastructures capture huge amounts of data. For example, in the paper from Facebook's Canopy, we see that this infrastructure captures gigabytes per second of trace data, and each individual trace actually contains thousands of trace points. Problem diagnosis, even with the needed instrumentation is present, becomes trying to find a needle in a haystack, because there are thousands of available instrumentation, and you don't know which one is contributing the problem most. This challenge is actually partially addressed by requirement line, so we automatically choose what instrumentation is to enable. But to avoid the needle in a haystack problem further, for the cases, for example, when there are multiple problems simultaneously in your application, we add the following requirement. So the requirement tree would be automated logging frameworks must be capable of explaining their decisions to the developers or to the operators. We next discuss insights and enableers that let us address the requirements. We follow the insight that because with similar critical paths that are required to process similarly by the application, we'll have similar response times. If not, this unknown behavior may be a performance problem such as log functions, resource contentions, or so on. This is a useful insight, an existing use of this that is as follows. Operators use separate performance counters for different types of requests or API calls, such as, for example, beat and the right attribute in a distributed storage application will have different performance counters. And the expectation is that requests of different types will have different critical paths, thus will have different response times. Furthermore, as a second insider enabler, we use distributed tracing, which is an enhanced form of logging. Because distributed tracing provides us the discriminant context we need. These are series of causally related distributed events that come together to contribute end-to-end request workflow, which is essentially key for effective diagnosis. By using these contacts, we can know which specific request to which API is experiencing what kind of problem and what component of these traces is contributing to problem. Third, high variance, high response time variance can be localized to sources of high variance between critical pet portions of the request workflow traces. Then it will give us insight into where more trace points must be enabled to explain this unknown behavior further. Building on these critical enablers and insights, we present the design of our framework. So let's talk about our approach. Wave identify requests whose traces exhibit identical critical paths, but which exhibit high response time variance. Wave then identify edges of these traces that contribute most to the variance. From there, it will enable additional trace points in the code regions corresponding to these high variance areas. This way, Wave is able to differentiate slow code paths from past ones, and from these slow code paths, it will isolate code with unpredictable performance. Let's now go through an example. Example on the right shows how to differentiate high variance due to caching operation. In figure A, the response time variance of lead to cache is high. The figure shows that the trace site spanning the storage node accesses is the dominant contributor to response time variance. From there, we see figure 2B and C shows that enabling trace points to differentiate caches from cache misses distinguishes fast paths from the slow ones. By doing so, Wave addresses requirement 1, which is to enable trace points in response to performance variations in the request workflow, and it also narrows down the search space so it will just focus on the caching operations within that region. Wave further maintains the history of trace points enabled on behalf of high variance along with the statistics that motivated these decisions. By doing so, Wave can explain why it makes the decisions in order to localize the problem, thus addresses the requirement tree to explain these decisions to the users. Let's next discuss the design of Wave. The main goal of Wave is as follows. During nominal operation, Wave operates identically to distribute the tracing and generate traces with a developed level of trace points enabled. When need problems occur, developers can use Wave to automatically enrich traces with additional trace points to localize them. Wave localizes problems due to slow code or the one with the high variance. Similarly, similar to dynamic instrumentation, our approach reduces the burden of deciding of which log points to enable upfront, and it also additionally eliminates the manual effort required to search the space of possible trace point choices. So figure on the right shows our design. It is comprised of distributed tracing infrastructure that allows trace points to be enabled and disabled, and the control logic where the enabling trace point decisions are made according to the performance variation insights. It has control plane on the top and instrumentation plane on the bottom. Components in the control plane implement the control logic which is to localize problems and further enriching traces. Instrumentation plane implements control logic trace points hypothesis which is to enable and disable trace points, and our framework operates in a continuous loop which is shown in the arrow which we will discuss next. So at each iteration, Wave's instrumentation plane components gather new traces which is marked A in this figure. Control plane components then examine these traces to identify hypothesis of which trace point should be enabled next, which is marked B in this figure. Hypothesis are then sent to instrumentation plane components shown in marked C which enable the relevant trace points and the cycle repeats. While doing all these steps, Wave also maintains a history of his decisions and their effects under the data structure called hypothesis first. So we first started the expectation that identical request types should perform similarly as we discussed in our insights. For example, our first expectation is that this request should perform similarly as a high-level expectation, and then Wave collects traces and group them by the request type so the list request are grouped together. It then iteratively drives hypothesis, so it enables some trace points to refine these expectations. For example, a refined expectation will be list request with cache should perform similarly, list request with cache should perform similarly. In the next round, Wave will group traces according to this new expectation, and in this new group, the list request are going to be together. Under that, it will group according to cache sheet and cache map. This hypothesis creates nodes in the tree, then new groups of traces are populated under these new leaves, which are analyzed in the next round to find the problem or to elaborate the problem further. And we consider any group of traces that show either high coefficient of variance or high mean latency as problematic. We have some statistical threshold, so if a group has higher statistic than the statistical threshold, then we point this group as a potential problem. And then we will start localizing the problem and make trace point enabling decisions. To know actually what can be enabled on behalf of a group, Wave has an applied profiling phase where it constructs a search space. The figure on the right shows an example search space for a given workflow. Wave represents search space as a set of paths observed in a request workflow. The search space is a collection of unique paths observed during search space collection. For requested exhibit concurrency, each concurrent path is stored separately, and the paths themselves are stored as JSON or dot files in our prototype. The nodes of these paths are trace point names and the edges are happens before relationships. And additionally, hierarchical relationships between edges are represented by nested start and end annotations and the trace point names. These paths are learned by running workloads against the application. And this is often the case during the code coverage, regression, or integration test. So let's now go through our search strategies. At runtime, when Wave observes a problem, it employs search strategy with problematic groups to determine next set of trace points to enable. Figure on the right is an example of distributed trace. It consists of a span, which is a logical unit of work with iteration. For example, A refers to a client operation from start to end, B, C, and D are the other methods executed during this call. We present two out-of-the-box search strategies and depict them in this figure. The first strategy is called hierarchical search, which explores top down by enabling trace points that denote a child level using the hierarchical search as shown in this figure. For example, in this figure, if the problem is in A, then the hierarchical search strategy can enable B or D spans. Our second strategy is called flat search, which uses a binary search light strategy and enable the middle trace point using happen before relationships. For example, if the problem is in A, it will then look at the hierarchical happen before relationship, so it will see that B, C, and D are executed in this order, and then it will just enable the C trace point. Let's not talk about why it's output and have to use it. Why it has two outputs? The first output is need traces whose critical paths are enriched with additional trace points needed to localize trace problems. During the time of problem, developer will take a look at the trace and she'll be able to find out that trace points corresponding to the problem will be already there. And the second output is attached to each trace containing the corresponding hypothesis tree that explains the result of Wave's hypothesis. For example, it may show that enabling the trace point around the cache differentiated critical paths and generates two new groups and increasing predictability for one group and isolating unpredictability for the other group. By using this stack, developers will leverage Wave API to query about hypothesis history for the corresponding trace. So we provide the CLI for interaction and expose an API for accessing and querying the hypothesis forest. By doing so, developers can also query hypothesis forest directly, identify a group of requests with high response line variation or which are considered this low. Some capabilities include, for example, identify all groups or request types that are really problematic in terms of high variance or mean. We also surface statistical summaries, for example, mean variance, coefficient of variance for per group, per trace point per request type. And also you can access to ranked ordering of problematic groups. For example, you can query top 10 problematic groups in your system or top 10 problematic trace points in your overall application. In this section, we present and discuss some of the limitations of our current implementation. First of all, we cannot identify if the observed variance or slow response times are a result of the code in the lower layer such as virtualization or the current. This is because current tracing infrastructures we use are limited to capturing elements of request workflows in the application only. Second, our method of enabling trace points cannot provide value for transit problems that disappear before we collect sufficient number of samples. We also cannot provide value for very rare problems that occur only once or twice, or they occur with very large periods that Wave cannot actually catch. And third, if the search space that we populate in the offline phases is incomplete, then we will not have complete visibility into trace points it can enable. So we require periodically populating this search space during the integration tests. However, even though there are these limitations in our evaluations, we will show that we can still provide value for OpenStack, HTFS and Uber and Death Star benchmark social network application despite these issues and we are able to find interesting performance bugs in these applications. So let's go through our implementation. We wrote two prototype implementation for OpenStack and HTFS by modifying their tracing infrastructure, which are OS provider and X-rays. Our modification to existing trace infrastructure are really minimal if you just add conditional checks before the trace points to check if they're enabled or not. And we also have a control plane component, which intends to be modular. For example, in both of these applications of HTFS and OpenStack, we use the same control plane components and which is implemented in the Rust language. And in our experiments, we created search spaces for OpenStack and HTFS using Workload Generator P Custom Build. Our generators uniformly issues a mixture of request types such as create, list and bleed. And we randomly select number of concurrent workers per round and then we populate our search space. And in the experimental evaluation, we use different systems and large trace datasets. We use the let wave run for against these applications and we will show that it's able to find different problems or interesting problems from these applications. We have two large distributed applications which are OpenStack and HTFS and two trace datasets from Uber and the social network application. Our setup has nine nodes with Ubuntu on bloodlap environment. And each of these nodes has eight core CPUs and 64 gigabytes of memory. We first investigate the trade of between flat and the hierarchical search strategies. And we try to understand if Wave can actually find the problems using these strategies and how do they differ from each other. To realize this, we choose random edges that correspond to random code locations in the OpenStack to inject problems. The chosen region in the source code is delayed following your normal distribution similar to our literature. First figure shows the average number of trace points enabled to localize problematic regions for both search strategies. We find that both search strategies localize problems within 15 trace points on average out of thousands of available in the search space. We also observe that flat search strategy improves performance over hierarchical search. And the second figure on the right shows the distribution of trace sizes for Wave compared to default tracing which we call vanilla in OpenStack. We find that Wave finds problems with 100% precision while reducing trace sizes by up to 90% on average compared to the vanilla case. So in Manila, developers will take a look at the traces and she will face thousands of trace points in a single trace. Whereas if she were to use Wave, she will only see critical path trace points and reach with significant trace points that are actually needed to diagnose performance problems. And in this case, it's shown to be less than 90% of the original traces. Overall, Wave serves as a fundamental step for developers to diagnose performance variation and localizing them to a specific array of the system. The table on the right provides an overview of the cases we found during our experiments using three different applications. We find that Wave reduces trace sizes for all these applications about 90% on average while finding interesting performance bugs. So for the sake of time, let's just discuss one case study from the table. All instances on OpenStack can be listed using the command VMList. So we set up Wave with the OpenStack, we let it run, and after a while we check that we find out that Wave finds a problem in the VMList request that shows high variance. And when we analyze the Wi-Fi hypothesis for us, we find that it first localized problems, it localized problems to problem source to three different edges. From there, we find the following. The two edges correspond to the identity service called Keystone, which is utilized for authentication token. Another edge corresponds to a function, which is getAll function that constitutes 2,000 lines of code and performs numerous database lookups to get every instance, including deleted ones too. So we also corroborate these findings in the bug reports as well. So these are actually existing performance bugs in the OpenStack, the version that we are using. So in this case, we find that Wave helps diagnose performance problems by isolating latency to first, specific service and operation, and second, to inefficient function. In this work, we presented Wave, a distributed tracing framework and variance-based control logic to automatically adjust instrumentation in response to performance diagnosis approach. We demonstrated the efficacy of our implementation by using it to diagnose problems in OpenStack, HTFS, social network, and Uber applications. And thank you again for very much for listening to my work. All right. So thank you for your talk. That was really, really cool. So I'm not seeing many or really any questions in chat, but we can get things a minute or two. I guess in the meanwhile, I'll just make the announcement. So right now we have a 30-minute break, after which we'll be resuming the track. Our next talk will be at 3 o'clock Eastern time by Alexander Bulikov on bending input space to fuzz, virtual devices, and beyond. Sounds very complicated, so I'm assuming it's going to be super interesting. I guess we did just get a question, so I'll just read it out. So Heidi asks, if there are any plans for VAI app to be applied at the infrastructure level? Yes. So we had this in our mind from the beginning, although it has been very challenging to merge application level traces with the kernel level traces, because even in the application layer, there are thousands of trace points, again, putting us along and hard work to localize performance problems. But starting this summer, we've been exploring some ways to stitch these traces together, and there are actually ongoing works to stitch them together. And once we can get to work together, get them to work together, stitch together, so you have requests going through your system, and at the end of your request, you will have like trace points from the application layer, from the kernel layer, but they're all in a single graph. If you can get this, I am very hopeful that VAI will be able to find very, very interesting bugs and performance issues in an application, even though the problem resides in the infrastructure level. Let's give people a second for a follow-up questions. It'd be nice if Poppin showed us that. Oh, there you go. So she says you could just look at it, or you could just look at the infrastructure, even without the application being traced. Yeah, that's also correct. One of the things that we've been doing actually, which I didn't include in this presentation for the sake of time, is that, for example, there's metrics collected from the infrastructure level, right? So these metrics are sometimes, according to the application, developers are included in the traces already. So in the case of that, we have lots of labels. Yeah. So in the case of that, for example, these traces can include some text or key value pairs, which correspond to these metrics or these indicators, whatever they are. For this case, we have key value pair correlation with the end-to-end latency. So in our paper, we have one case study where there is a contention issue due to the number of concurrent workers exceeding the limits. The request getting slow and slow. And then once we have this key value pair or the tag, and we correlated with the end-to-end latency, we are able to find that this is actually causing the problem. So similar to that, for example, infrastructure level tags or the metrics can be correlated with the end-to-end latency. So if you're just talking about not using traces at all, that's also possible, then you get a little bit distracted from the application layer, too. The last thing I had asked was that it would be very exciting to try the MOC. Yeah, I agree. And thank you for your insightful questions. Well, thank you, everyone. I'll see you all in half an hour. Take care. Bye-bye.


Hello everyone, welcome back to another CapCut tutorial. This one, I'm gonna show you how to take dark footage that you've got on your phone or whoever you filmed it, and I'm gonna show you how to brighten it and lighten it correctly. Let me show you what I'm talking about here. I've got this lady here in this footage. I've deliberately selected very, very dark, almost too dark footage where you can just see her, she's doing her thing and she's completely in the dark. And then I've added in some adjustments and I'll just move it to the start here so that you can see what it looks like. And then now I've relit this scene using just CapCut to do this. So how did I do that? Let's go through it step by step. So I'm just gonna go ahead and select this and delete it. Okay, so again, we've got our footage, we're starting from scratch.  The most important one of course is you've probably guessed is brightness, but when you jack up the brightness all the way, it's brighter, but do you see how it's put in a color cast? So we've got a very, very cool and a very blue tint to the film or to the footage that we don't necessarily want. In most cases, unless you're filming a horror film, maybe then you can keep it in. So we're gonna go ahead and make a couple of other extra changes. Contrast, we wanna pull the contrast down a bit because that gets rid of a little bit of the blue. Same with the saturation, you can adjust it, but generally you want the saturation to come down quite a bit because again, we're trying to nullify the blue. The exposure usually will go up a little bit because that allows it to be brighter footage and that's what we're going for. We're going for a brighter look. So again, we're just going through this here step by step. The other one you wanna do is the HSL which stands for huge saturation and lightness. In particular, you'll probably want to adjust, in this case, the blue. So I've clicked on this darker blue and then you'll see here I can adjust it up and down depending on what you want. The hue, not a huge factor, but again, I'm gonna pull the saturation down a little bit and I'm gonna increase the luminance just a little bit. That meaning making it a little bit brighter. Luma is basically brightness. So we've gone ahead and completely changed the look of the shot here. Let's go through one more thing. I'm gonna show you the temp. This is the temperature of the shot.  So if I push this up or if I push this down, obviously in most cases we wanna move this up. We want the temperature to go up. So I'm gonna go ahead and there, adjust it to that point. Now, you'll see here, now if we look at the original shot, I'll go back here, this is the original shot and this is the adjusted shot. This is a lot brighter, we see a lot more of her. It's not perfect. If you wanna do great color correction, you can use a tool like Premiere Pro or DaVinci Resolve. There's a lot of really, really good ones but this is how you do it. And now, if I wanted to go in and make it even extra brighter, I have a few other options. I can either go in and make some adjustments so I can just click on this and then just start making adjustments again. I've already made some or I'll show you another really cool trick. You can click on it and then watch this hit copy and it applies a second layer. Now, this is way too bright. It's blown out, I get that but you can go into the second layer and then you can start making adjustments like you can, you know, we can decrease the opacity, we can reduce all sorts of things. So that is generally how you get dark footage. Put it into cap cut, make it brighter in just a few minutes there. Thanks for watching guys, ton more stuff coming up, stay tuned.


If you play in the midfield and you want to improve your game, these are some soccer drills for midfielders. If you don't know about me, I used to be a huge underachiever, but through obsessive self-improvement, I found my success. Earned a college scholarship, played for my national football team, a YouTube channel with over 100 million views. I've helped players worldwide and I'd love to help you improve faster and achieve more. If you don't have balls, you can use cones. If you don't have cones, you don't need any balls at all. You can use open space, but the purpose of this is dribbling, still keeping control of the ball, but head up, head up.  Where's the pass? Where's your teammate? But don't lose the ball, but keep that head up.  Over time, I don't even have to look at the ball. I know where it is. I can feel it with my peripherals. I can see with my peripheral vision. And obviously, you're going to have to look down every so often, but as a midfielder, you need to get in this habit of constantly being aware of where the spaces teammates are when you're in possession of the ball. This here, as a midfielder, is everything. So if you are receiving a pass and all you're looking at is the ball, you have no idea where you can get tackled from, where the defenders are coming. You have no idea where your teammates are if you want to play one touch, if you want to release the ball quickly.  But when that ball is coming, try to find where the space is. Turn, bit of skill, play that pass. Bit of skill, but play that pass, shoulder check. Cool again. So the first part of this drill is scanning the field, shoulder checking. Next part, look at how I'm receiving the ball. So as a midfielder, whenever I can, I want to try to receive half turn. That means I'm turning my body before I touch the ball. A lot of players, they want to go that way, but their first touch is here, second touch here, third touch there. If you want to play quicker, I don't even need a touch and I'm already doing the same thing that you just did. So focus on receiving the ball, either opening up your body, if the weight of the pass is soft enough that you can run with it. Or my touch, can I turn quickly and take that touch back into me? Or even just receiving here is a lot better. But you can't do that if you haven't done the shoulder checking first because if you don't know who's there and you turn into trouble, boom, get tackled. Okay, so shoulder check first, half turn, bit of skill here, do whatever you want, have fun. The final thing is quality of the pass. So as a midfielder specifically, but every player, take pride in your passing. So when I play that pass, getting over the ball, if you have a few balls and you want to try hitting it into a net, just get that ball out of your feet, play a driven pass, good technique, into the net. Try to hit the back of the net without the ball bouncing. So good technique, driven pass. Don't just have a dead ball, go and hit it because in a match that's not realistic.  Good technique, driven pass. Let's do better than that. And maybe you missed the net. But you go again, there you go, driven pass. And like always, ooh, crossbar, ooh, camera. I'm always playing with both feet. So as I said, it's better for you to practice off a dribble, it's more realistic. Get that ball down, good technique. Playing with both feet, there we go, beautiful. This drill is about shooting, but I want to make it midfielder specific. So I have my trusty box. If you don't have a teammate, find something. Like I said in another video, this is a piece of wood. So if you're going to make the excuse of I don't have a box, be creative, find something because that's a beautiful tool if you have no one to practice with. Okay, but I'm playing this pass. Here I want to focus on getting my shot off quickly, but opening up. So I'll play that. As you can see, I'm receiving that on a half turn. I'm not receiving like this and then turning and then trying to beat him. I'm not receiving away from goal if I don't have to. I'm playing this and I'm already open on him. Touch, strike, hit the net, score the goal. So again, play the pass, open up, quick touches and get it on net. It's good for me to show you guys misses because everyone misses. If you miss, get the ball, go again. There we go. But as a midfielder, it's receiving half turn. Not receiving with your back to goal, not receiving here, here, then go at him. That's the corner. Okay, so this is a great drill to practice shooting as a midfielder. If you like this content, check out the soccer success planner. You can download it for free. There's a link in the description below. And for advanced training, check out the online soccer academy.


Hello and welcome to the session. Let us cause the following problem today.  Now let us write the solution. Now let us check for one one. Let a one comma b one comma a two comma b two belongs to a cross b such that f of a one comma b one is equal to f of a two comma b two which implies b one comma a one is equal to b two comma a two which implies b one is equal to b two and a one is equal to a two which implies a one comma b one is equal to a two comma b two thus f of a one comma b one is equal to f of a two comma b two which implies a one comma b one is equal to a two comma b two for all a one comma b one and a two comma b two belongs to a cross b thus f is one one. Now let us check for on two. Let b comma a be an arbitrary element of b cross a then b belongs to b and a belongs to a which implies a comma b belongs to a cross b thus for all b comma a belongs to b cross a there exists a comma b belongs to a cross b such that f of a comma b is equal to b comma a so f is a function such that from a to b to b cross a is an on two function thus f is an on two function therefore f is a bijective function since it is one one and on two both. I hope you understood this problem. Bye and have a nice day.


The Importance of Diagnostic Tests in an ESL Classroom For teachers of English to speakers of other languages, a diagnostic test is a valuable resource that can be employed to help both the teacher and the student. A diagnostic test is given at the beginning of the course, and is intended to assess the student's current knowledge and mastery of the English language. Diagnostic tests are similar to placement tests, however, a diagnostic test is generally used to assess more areas of the English language as a whole. Diagnostic tests are important as they assist the teacher in preparing lessons and materials, can help gauge the level of the student and whether the course is a good fit, and can help students know what language areas they need to improve on. The Main Purpose of a Diagnostic Test Diagnostic tests can show the teacher what the students know and do not know about the English language. Such information can and should be analyzed by the teacher. The results of the diagnostic test are a valuable resource that can guide the teacher in creating effective lessons and materials that meet the learning goals of the course and the needs of his, her students. For example, if the teacher had the expectation that students are able to use the present perfect tense in a certain situation, but the majority of the students were not able to accurately use such a form in the test, the teacher could plan a lesson to review this material at the beginning of the course. Moreover, if a certain form and its usage that were originally going to be taught in the course appear to be already mastered by the students, it could be taught at a faster pace, giving time to other language areas. Other Benefits of Diagnostic Tests Another reason why a diagnostic test is very important to the English language teacher is because it can determine the appropriateness of the course for students. If placement tests are not used at a given school or institution, evaluating the results of a student's diagnostic test may reveal whether the course matches the English level of the student or not. As an example, once a diagnostic test is completed by students, the teacher may realize that one student is far below the expected English level for his, her class. As a result, this student may be pulled aside by the teacher or counseling staff at the school or institution to determine more formally if the class is actually a good fit for them. The Benefit to the Student Diagnostic tests can aid students in realizing what areas of the English language they are proficient in and what areas they need to work on. While this can be realized by the student during the test, it is much more worthwhile for the student to see the test and their results once it is graded. Doing so, the students can specifically see where they need to improve. They can also ask the teacher why their answers are wrong, for help in understanding certain forms and its usage, and even for advice on how to progress in their learning of the English language. Giving the student an awareness of their own English abilities is helpful, as it involves the student in his, her own progress of learning the language. Overall, implementing a diagnostic test at the beginning of a course is immensely important and can provide a solid base that can affect the trajectory of the rest of the course in a positive and effective way. For answers to a wide range of questions about TEFL courses, teaching English, and much more, take a look at our FAQ page. Are you ready to teach English abroad? Speak with an ITTT advisor today to put together your personal plan for teaching English abroad. Send us an email or call us toll free at 1-800-490-0531 to speak with an ITTT advisor today.


Okay, I think I'm ready. Let's see. Jacob are you all right? What's that? Are you okay? Oh, yeah, I'm in the hospital trying not to give anybody else a disease. It's not me. Cool. So the people who are immunocompromised. That makes sense. All right, so it's one minute past the hour so I'll just get started. Thanks everyone for joining. Happy Monday. I'll start with this slide. We have a new team member joining on May 3rd. Her name's Sarah. She'll be our UX lead so we're super excited to have her on board. Next I'm going to talk a little bit about some of the UX issues that we've been working on for 9.2. One of the larger features is related issues. The design uses the token that we have for our new search design and it will display the status of the issue, the issue number as well as the title. You can quickly add new related issues in a similar way that you can add a new issue to an issue board and in the future there'll be multiple types of related issue relationships including blocked by related to a part of and multiple others but this is the first iteration and it just includes one-to-one relationship that related issues us. We've also made some improvements to our markdown styling so you can see the current one on the left and the new design on the right. The new design is much more spacious so it'll really help with readability and we use the markdown throughout multiple areas of the site including comments, wikis, readme's, etc. So it'll really help improve readability throughout all these different sections. We're also working on lots of design updates to the customer purchase flow. The changes are mostly visual but it'll really help give the flow a more professional look. From this initial screen you can see that we've removed the red which really looks more like a warning. It seems pretty bad when you want someone to purchase something you don't really want them to stop or second-guess themselves so we've replaced it with cooler blues and purples and we've also added the pricing and cleaned up the pricing cards themselves and there'll be lots of other changes to the whole flow. With 9.2 you'll be able to run pipelines on the schedule and this means that you can set them for a time in the future for a specific branch or tag and you'll you can find this on a new schedule tab located under pipelines. This is related to the last slide but it's not currently scheduled for 9.2. I wanted to share it anyway since it's pretty related and the designs have already been worked out so one of the next steps for being able to run a pipeline on a schedule is being able to run a scheduled pipeline just once so you'll be able to choose between running a pipeline one time or repeatedly. We've started the first iteration of linking between project pipelines. I think I shared a little bit about this the next iteration in the last UX update but in this view it'll show which pipelines cause other pipelines to run by displaying inbound and outbound connections. With 9.2 we're allowing the deletion of protected branches. Mike talked about this a little bit in the kickoff meeting. We've added this ability because there's currently no way to delete a branch that is protected under a wild card so this forces the user to remove the wild card in order to remove the branch but this would also open up a possibility of problems with other branches that use that wild card so we've created a flow that allows masters to delete the protected branches. In order to do this you have to confirm in the confirmation modal that you see by typing the branch name and we're still continuing improvements to our search design. In 9.2 you'll see the avatar of the user when searching for an author and a sign. You also see the related color when selecting labels and you'll be able to clear a token by clicking on the X to dismiss it. So next I've included some projects that the UX team has been working on that currently aren't scheduled. One of those issues is improving mass editing of issues. I talked about this in the last UX update but I want to make sure it keeps getting traction because there's some confusion with mass editing since the filters look like how our old filters used to look so we've drilled down a design and you can check that out in the issue more. Another search improvement we've been working on is a new filter type that would allow for boolean type filters so this could include start issues, confidential issues, issues with a closing merge request, etc. This type of filter would give a lot of flexibility for adding different search parameters so in this issue we're talking a little bit about the wording so you can feel free to contribute. You can see from this screenshot we've talked about flag has is so we're just trying to drill that down. We've also been working on the ability to batch merge request comments. This would allow you to bundle and save comments until you're done reviewing and then you can post them all at once. So from the view here you can see a list of comments that you've already made and then you can click on a comment and it would link back which would allow you to quickly make edits before publishing them. One of the larger projects the team has been working on is improvements to our navigation. You've heard us talk a lot about it I'm sure already. In our testing we found that there's a lot of confusion regarding global versus contextual content so global refers to the navigation elements that are kind of always available to you so your projects, your issues, your merge requests, exploring GitLab and contextual content refers to the navigation that changes based off the page reviewing. So for example a group page has a different set of feature links than a project page has but because our global and contextual links often use the same language like you have your issues and you have project issues it's really easy for new users to get lost. So this isn't a super easy problem to solve. We've had two rounds of navigation testing to kind of determine where the problem areas are and then we've been having a few brainstorm sessions in order to create the mock-ups that you see here. Chris transformed these designs into prototypes that we are using to specifically test the global versus contextual problem. The major difference between these two designs is how we're displaying the project breadcrumb in the upper left corner. You can find both of the prototypes in the research issue which is number seven and so feel free to play around with those and we have a navigation channel if you want to share your ideas or thoughts there. So there's also a number of issues that the UX team has been working on that are ready to be implemented. I shared some in the last functional group update so I decided to just pick some more for this time. Part of that part of the work we've been doing is ensuring that our guide is constantly updated. Whenever we have a new guideline we want to make sure we add it so it can easily reference by everyone. There are a few guidelines that we've added that haven't been implemented yet so this is one of them. The idea is that within a dialogue or form the dismissive action is placed to the left and returns the user to the previous state so an example of that would be cancel and affirmative actions are placed to the right and continues towards the user goal and an example of that would be like save or continue or okay. Another guideline that isn't fully implemented is ensuring that each of our icons uses a tool tip so we just want to make sure that these guidelines are also seen throughout the website. When changing issue templates the issue description is currently lost and it's replaced by the new template. This can be really frustrated and lead to the loss of content if you're unaware that that happens. So in order to prevent that we'd like to add a confirmation step when changing templates. This would only happen if you've added content to the to the template that you're currently using and that would mean that changing templates would mean a loss of data so if you if you wouldn't be bothered by the confirmation if you change templates that haven't been edited. Responsive tables is something that I would love to see worked on. We have a design drilled down for the environment spews specifically which you can see here. Currently the tables scroll horizontally and they're very difficult to use on mobile or even on desktop some of the time so the new design would just show the essential information and clicking on the environment would display all of it in a new mobile friendly design. We also want to add time tracking to the milestone view. Last time I checked the issue has about 17 likes and it seems like a really easy win because the design is really simple and it just duplicates what you see on the issue page. So those are just some of the issues we've been working on or that we've worked on already so I'll stop sharing somehow and look through the chat. On the pricing page should we make a clear difference between you host and we host? Yeah we I tried to differentiate them but I will take a look at that again if it's not clear enough. Yeah I put that in I think like people might not know like what's the difference between EE and getlaw.com because we run EE on getlaw.com and stuff like that. I don't have a suggestion how to do it but I'm just afraid that might be yeah something people wonder about. Yeah that's a good point thank you. I answered Rebekah's question. Yomi I like your comment. All right let's see are there any any work for readability for long length? So yeah I mean that's directly related to the markdown stuff that we've been working on. I think that improving the readability there will help with the line length because there's just going to be way more spacing and it will everything won't feel so smashed together but we also do have the meta issue for the line link to continue the work that we've done there throughout multiple areas of the site. So we've done issues and merge requests and there's wikis, remes and a few others that where we use all the markdown. Any other questions going once twice getting a left. So we're getting a left nav bar again it's a possibility we're testing it right now. Great well I will give you guys all 15 minutes back of your day and I'll see you on the team call. Thanks everyone.


There's a line in the Course that what Jesus says, what you do comes from what you think. So that's probably the clearest statement in the Course of the connection between the doing and action to always proceed forth from thinking. And it's a sheer background in profession as an architecture. I know we've talked briefly about form and content or form and purpose. How form should be pretty much guided and shaped by the principle or the purpose that's underneath it. We've talked about it in terms of like use of space, you know, what's efficient, getting away from just aesthetics for the sake of aesthetics to how does the purpose, the underlying purpose or content really guide and shape the aesthetics. And it's pretty much the same with thinking and action that we have to really become really consistent and clear in our thought processes for the actions to flow from those thought processes. And when we think of them as two separate things and not being connected, then there isn't a sense of harmony. It's more of a sense of autonomy as if actions are just completely autonomous. And what I would say is this whole world is kind of like the Pinocchio syndrome. The story of Pinocchio is that Gepetto is a puppet maker, he makes the marionette, and Pinocchio is a marionette on the strings. You see, when a marionette is on the strings, there's a direct connection between the one who holds the crossbow and the movement of the puppet because of the strings.  This is the problem of the world is that human beings believe that they're autonomous boys and girls and men and women and they don't acknowledge the strings anymore. Even though it's important to acknowledge the strings, because even though the body seems to act independently and it seems to have autonomous behavior that's separate from all the other people, it's not so when you go deeper into spirituality, you realize that whether the strings are now gone and none of us have the strings anymore, so we don't consider ourselves puppets in a physical sense. Some of us still feel much like we're puppets of the system or we're puppets to our partners and spouses or to our parents. We still act in certain ways like puppets when we're around our parents. People tell us so. You're not the same person when you're with your mother and father.  But there are mental strings that are moving the puppets and we have to start to acknowledge those invisible strings and conditions. So there is a very direct connection between action and thought and it seems pretty invisible because the ego belief is that we have lines of our own, we have thoughts of our own and we have bodies of our own and all of that would support that we are completely autonomous beings. The human beings are autonomous individuals and nothing could be further from the truth. That is all a lie. It's all a misperception and it's all part of the ego's plan to come up with something that will be kind of satisfying and fascinating and curious and intriguing to take the place of pure oneness, which to the ego is boring, boring, boring.  Even when we talk about romances we would say, how's the chemistry? We like to have some spice in there. How did your first date go? We are completely the same. We are totally the same. We had our whole conversation with sameness, sameness, sameness and we talked about our life together, we could share with all of our sameness. The spice is the chemistry, is the differences. That's what makes it alluring, that's what makes it juicy. If you are both identical, it's like, what's the sun in that? Just relating to yourself, spiritually that's a good thing. Relating to yourself, to the ego, it's a bad thing. You need to spice it up.  And so he listens to what we should say, he doesn't really listen to Jiminy Cricket. Jiminy Cricket is the Holy Spirit, is the voice of his higher self, his consciousness. Who's there to guide him and help him navigate and to come back to a sense of hoveless and harmony. But he doesn't listen to Jiminy Cricket and he goes to Pleasure Island. Immediate gratification, that's the ego, it wants just immediate gratification. And it's got its own sense of it wants to play, it wants to have pleasure. And then the little boys turn into half-donkeys. It's quite a strong consequence for not listening to Jiminy Cricket. And it's a shocking consequence. And the same thing that we experience in this world, when we don't tune into spirit, we try to do it on our own in an autonomous way. I can do it better than God, I don't need any guidance, I don't need any help, I can do it all on my own. There's some shocking consequences. We may not feel like half-person, half-donkey, but we feel very disconnected, fragmented, lonely, isolated. You know, there are shocking consequences that are not natural to our peace of mind. And we tend to feel very conflicted, we tend to face a lot of drama, we go from crisis to crisis. And instead of just flowing in joy and love and happiness, our life turns into crisis management. How do we handle the next crisis? How do we handle the next drama? And even when we're flowing a little bit, we start to put so much attention and energy into the future potential crisis. So we get locked up into insurance schemes and guarding against the repeating of horrific past consequences. And we spend our time not really living in the moment, but all caught up into believing all these hurtful consequences are real, having a lot of painful memories and hurts and grievances, and then skipping over our present joy and focusing all our attention into doing things for the future to avoid those past consequences. And therefore, you know, believe we're black gliding down the highway when in fact we're slip sliding away, as Paul Simon would say. So that's why we, it's very important to understand that connection between the thoughts and the actions and to, I would say, to get back on the strings, but realize that the Holy Spirit is the one that we're, we talk about back on the strings, letting the Holy Spirit guide our thoughts, joining with God, thinking with God, and then letting the actions flow from that connection in mind. That makes it easy. That's actually how things flow. So everything we think and say and do is in perfect integrity and perfect harmony. If you look at the Gospels too, you see that Jesus, he doesn't talk a whole lot about the future. You know, he says things like, let the morrow take care of the morrow. He's not really big on planning either. Much unlike most human beings, you don't really see Jesus doing a lot of planning. His idea of planning is turning to the apostles and saying, we go to Bethesda, or we go to Copernicus, or you know, that's his idea of planning. That's pretty spontaneous. We go, whoa, whoa, whoa, we go. We like it here, we go.  It's too dangerous there. You know, harm could come to you. You could be killed if you go back there. We won't let you. And everybody, you can remember his response to Peter. Get thee behind these Satan. Doesn't want anything blocking that spontaneity. I go. Oh, no, you don't. Oh, yes, I do. Get thee behind these Satan. I go. The script is written. I have a life that I'm demonstrating, a connection with God, and there is no interrupting what is given from spirit in thinking and the actions. It wasn't a debate. It wasn't a democracy. He didn't say, okay, there's 12 of you. Let's take a vote. How many say I go? How many say I stay? It's just like I go. And that's what we want. We want the certainty of being inspired, so we don't have to have a big committee meeting about what we're going to be doing. That is just given. That it just flows spontaneously. We don't have to figure it out. All the energy we spend on analyzing, comparing, contrasting, weighing the pros and the cons. That's a lot of work to make a decision, which we've all felt could be a lot simpler than all this meeting and synthesizing and analyzing. There must be a way, must be a better way to live than that kind of analysis.


So now this is something very intuitive, so let us just observe what is happening in this. A pendulum is swinging and what do we see when we see the pendulum. You are able to see the pendulum, swing. Now let us view this pendulum through a window, now I have put a window, you are able to see that. Window is big enough and you are able to see it. Let us make the window a bit smaller, what will happen, possibly if I make the window smaller I may not be able to see the full swing of the pendulum but what will happen if I wait long enough. If I wait because of gravity physics says that the swing of the pendulum will become smaller, even if my window is smaller I will be able to see the full swing. Let us make the window much smaller again, what will happen, maybe still I cannot see all the swing. But again I wait more longer enough, again I will be able to see. So what I am saying is I will be able to see the position of the pendulum in every window however small the window is. You will say the limiting position of the pendulum is the horizontal one, is that okay and that is what is convergence of a sequence. Position of the pendulum call it as an. So given a window of some length all the an's are inside, that is convergence of a sequence. I will write that as mathematically saying as follows, a sequence an is said to converge if there is a number l which is a real number such that given any window across length of the window. So given any epsilon look at that window, the length of the window is l minus epsilon to l plus epsilon. So what should happen, the pendulum should be visible maybe after 10 minutes. So there is a stage, so call that stage as an not such that an comes inside l minus epsilon and l plus epsilon and stays inside. So for all n bigger than n not, some stage or some weight everything is visible to me. All the terms of the sequence are visible to me. So mathematically saying that this happens right or you can write it as if you like, you can write it in terms of, there is a notion of absolute value of numbers, does everybody know absolute value of numbers for any number x real number, absolute value of x is defined as x if x is bigger than 0 and it is defined as minus x if it is less than 0. So this is essentially geometrically saying it is the distance of a point on the number line from the point 0, distance is always bigger than or equal to 0. So this is the convergence of a sequence of real numbers. So it is quite clear to everybody what is the convergence of a sequence, an is convergent if it comes closer to a value, so I have to say what value. So there exists a number l such that an comes closer to l, what does closer mean? I give you any window, so length of the window is epsilon right, so given epsilon bigger than 0, look at l minus epsilon n, l plus epsilon everything after some stage should fall inside it. So an is inside the window that means absolute value of an is distance from l, either this side or that does not matter, so absolute value of that an minus l distance is at the most epsilon from n bigger than n0 right. Another way of understanding this would be, you see an keep in mind that area thing, say an is an approximation to l right and what does an minus l indicate? It is the error you are making, actual value is l, you are taking an approximation a l, so the error is an minus l, that error I want small, how small? I will specify how small, so epsilon is a Greek letter for e okay, that is why one it has stuck as epsilon, so given the margin for error that is a distance for error epsilon, I will specify it should come that close, so an should come close to l, how close? That error should be less than this for all n bigger than n0 after some stage, so keep in mind for a sequence convergence depends only on the tail of the sequence, from some stage onwards for large n, it does not depend on the first few terms, there could be anything because what we are interested in is what happens for n very very large, after some stage if they all come inside that window for every epsilon, every window then good enough, what first 1 million, 1 trillion, it does not matter how many terms you have to forget, forget them right, so it is a tail of the sequence which is important for analyzing whether it is convergent or not clear, so that is what is called convergence okay, so this is what, so let us look at some examples I think, so let us look at the sequence 1 over n, so limit, so we write as limit n going to infinity that a n limit n going to infinity equal to l, so what is the meaning of that, that is only a symbol, that is only a rotational way of writing saying for every epsilon bigger than 0, there exist some n0 such that a n minus l is less than epsilon for every n bigger than n0 right, so let us look at the sequence 1 over n, so whenever you want to analyze whether a sequence is convergent or not you have some way of making a guess of that thing, what you think is possible happening, so let us most of the time you will have to do that and then prove it okay, so make a guess what happens to 1 over n, as n is becoming larger and larger, so n becoming larger meaning 1 over n 1, 1 by 2, 1 by 3, 1 by 4 becoming smaller and smaller, so guess, so this is my guess limit 1 over n is equal to 0 right, so how do I prove it, I have to prove it according to this, so let epsilon greater than 0 be given, then we want a n minus l less than epsilon for every n bigger than n0 right, so what is a n minus l here, we analyze that, the error we want to make it small, so let us analyze what is the error actually in our case, so that is 1 over n, so l is 0, a n is 1 over n, so this is 1 over n, so we want this to be less than, so we want 1 over n less than epsilon, what is epsilon, epsilon fix right, that is given to be a margin, that is same as saying that 1 over epsilon is less than n right, so that means given epsilon, I want n, so is that 1 over n should become less than, is it possible yes, because of Archimedean property right, a real number, given any thing I can go across by choosing n large enough, so that is Archimedean property says yes it is possible, so for that particular epsilon, for given epsilon become, there is a n0, so is that 1 over epsilon is less than n0 right, by Archimedean property, so that is same as saying that 1 over n0 is less than epsilon right, so if n is bigger than n0, then what happens to 1 over n, that is less than 1 over n0 and that is less than epsilon, so we got an a n less than epsilon right, that is how you write the proof that 1 over n has limit which is equal to 0. Let us do one more example, let us look at that sequence in the example that was minus 1 to the power n, n bigger than or equal to 1, so I have to make a guess, guess this convergent or not right, so what are the terms, so this is one way of right, look at the few terms of the sequence at least, it may give you a hint right, so terms are minus 1, 1, minus 1, 1 and so on, so if I look at the number line, here is 0, here is minus 1, here is 0, so the sequence is visiting minus 1 and 1 at every time point n and these are the only positions where it goes right, so intuitively it looks quite clear that it cannot converge to anything other than minus 1 or plus 1 right, if at all it converges the possibilities are either minus 1 or plus 1, so these are the only places occupied by it, so as a first step we want to show that, so guess is it does not converge right, so how do I write a proof of that, so we want to write a proof, so guess the sequence is not convergent, that is equivalent to instead of writing not convergent, not convergent, let us give it a name, we say it is divergent, something which is not convergent will be called as a divergent sequence, so we want to say it is a divergent sequence, so if possible let this sequence minus 1 to the power n divided by n bigger than or equal to 1 converge to let us say plus 1 or okay, we can do all of them 1 by 1, so here is 0, here is plus 1 right, here is, now intuitively if the sequence has to converge it has to come closer to some value and we are saying it is coming closer to the value plus 1 after some stage, but I know that whatever stage I choose right, after that positively it is going to come to minus 1, it is going to come away from it right, so that says to me that let us take epsilon equal to, epsilon bigger than 1 such that 1 minus epsilon is bigger than 0, so let us take here is 1 minus epsilon, I want to show it does not converge to plus 1, I have to say that there is a, okay, so this is important, saying something is not convergent what does it mean, so that is, let me discuss that first, if this thing does not happen, my guess is the sequence does not, then what I have to do to prove convergence given epsilon I have to find a stage n not, to prove it is not convergent what I have to do, I have to show that whatever l I choose right, whatever l I choose this thing should not happen, that means what, that means I should be able to, there is, if I want no l to be the limit right, that means I should be able to find at least one epsilon, one window right, so that whatever stage I say something goes out of it, everything after that is not visible, so something goes out of it, so let us write that that is important, so before I write everything a n does not converge to l, a n no I think better way of writing is a n is not convergent is equivalent to saying for every l bigger than 0, for every l which is a real number, see limit exists means there exists one l, I do not want that to happen that means for every l something should go wrong, what should go wrong, for every epsilon there exists some epsilon bigger than 0 such that for every stage n not, there exists some n bigger than n not with a n not, not belonging to l minus epsilon to, is that okay, saying that convergence means there is a l for which something is true, false for every l something is false, what is false for every l I can find at least one window that means there exists some epsilon, so that if I look at that window and look at any stage n not then there is one stage at least after that which goes out of it, because convergence says everything must be inside, so not true meaning whatever stage I give you I can find at least one point after that stage, so that it goes out of that window, it is something like in that pendulum, if after sometime I give a kick, I keep on giving a kick, so I can find always a window it will go out, it will not be convergent, something like that should happen, so not convergent, so let us look at that example that minus 1 to the power n divided by, sorry not divided by minus 1 to the power n is not convergent, so case 1 let, so this is my a n let limit minus 1 to the power n n going to infinity be equal to l, be equal to say plus 1, so let us assume, so if this is plus 1, this is 0, I know the sequence goes to minus 1 whatever stage, if the stage is even then at the odd stage next odd stage it will come out, it will go to minus 1, so positively it will go out of this kind of a window, so I have to select there exists an epsilon, so find an epsilon say that this is 1 minus epsilon 1 plus epsilon that is why I said let epsilon bigger than 0 be such that 1 minus epsilon is bigger than 0, then for every n not there exists n odd such that minus 1 to the power n does not belong to l minus epsilon n l plus epsilon, it will go out, so it will be minus 1 somewhere here at the odd stage that is outside, not only once it goes out whatever place I give you after that I take any odd stage it will go out, so this cannot be plus 1 cannot be the limit, similarly minus 1 can be the limit because then I will go to even, can something in between be the limit, this is 0, this is minus 1, this is plus 1, can this l be the limit, so obviously again if I take a window like this if I take a window like this then no n is going to be inside it, because n is only plus 1 or minus 1, so for this case I will choose minus 1 less than l minus epsilon less than l plus epsilon less than 1, so I choose for this kind of epsilon, so this is going to be my window, so nothing is going to be inside, leave aside something going out, so this cannot be the limit, so neither plus 1 can be the limit, neither minus 1 can be the limit, nor anything other than plus and minus 1 can be the limit that proves the sequence does not converge, so this is how we will write a proof of something not converging, right, is it time to stop, I do not know what is, what time we are supposed to be having lecture, what is the time now, 12.30, so let us stop here, so what we have done today is I have tried to give you some indication of why rationals are not good enough, why we need reals, what are reals, what are the important properties of reals which distinguish them from the rationals that is namely one completeness property and you look at the sizes, rationals are countable in infinite, reals are uncountable in number, that is something, then we looked at the why we need sequences, right and how do we analyze what we are interested in, when n becomes large what happens to the sequence n, we define the notion of convergence of a sequence, okay, let us stop.


It's time for the Lawn Jean Chronoscope, a television journal of the important issues of the hour brought to you every Monday, Wednesday, and Friday a presentation of the Lawn Jean Wettner Watch Company, maker of Lawn Jean, the world's most honored watch, and Wettner, distinguished companion to the world-honored Lawn Jean. Good evening. This is Frank Knight. May I introduce our co-editors for this edition of the Lawn Jean Chronoscope? Larry Lusser from the CBS television news staff and Associated Press correspondent Francis W. Carpenter, covering the United Nations. Our distinguished guest for this evening is Dr. Charles Malick, Ambassador from Lebanon through the United States. Dr. Malick, Lebanon is a country about the size of New Hampshire with a population of about two million, I guess. Would you tell us something about the role of Lebanon in the Middle East? Well, Mr. Lusser, I don't know whether it is really as big as New Hampshire, but it's a very small country. And as to its population, it's not quite two million yet. It may be nearer a million and a half, but it's a small country both in size and in population. Yet its importance in the Near East, and I dare say in the world at large, cannot be measured by either its size or its population. For it is a unique country in the Near East. It's a country that is half Christian and half Muslim. It's the only country like this in the Middle East and in fact in history, where you have these two religions meeting with each other on a basis of complete equality and mutual respect. The Christians in Lebanon participate in Western culture and Western spirituality to the full. The Muslims who are very vigorous citizens in my country, they participate in Islam and in Eastern culture. So I should say the most important thing about Lebanon is that how these two outlooks, how East and West, meet together in freedom and in perfect mutual respect. The second thing about it is that everywhere, whether in the Arab League, to which we belong, or in the United Nations, or in any international gatherings, we try to play a moderating and mediating role. Because we believe that in the end, only such a policy is successful and worth pursuing. And finally, I will add one word, and that is about freedom. Lebanon is famous for its freedom in all of its phases. People can think what they like, they can express what they think, and they can live as they please. So I should say, as a moderating influence, as a place where East and West really meet and mingle in freedom, and as a place where freedom can flourish, Lebanon is really a unique little country in the world. Well, Dr. Malik, could we follow that up a little bit, and can you tell me, is the Middle East itself stable and secure at the moment? Is it in a stable situation? Well, now, I think that you mean by secure whether it is in danger of external attack or of internal eruptions. Is that what you mean? Yes, I'm thinking mostly of the internal situation. I don't think we need to worry about aggression at the moment in the minute quarter, but is there is a ferment in the Middle East, or are they politically stable and calm at the moment? Well, of course, there is calm and stability, but I think it's more apparent than real at the present moment, because we still have terrific problems throughout the whole area. First of all, we have not yet related ourselves on any permanent basis with the outside world. It is still a question as to how we should be related to Europe, America, or to the communist world. We are still unrelated in any permanent manner to any of these works. Secondly, even our relations among ourselves have not been fully stabilized. So it is a question also, what sort of order among the countries and peoples and nations in that area is going to emerge in the next few years? Well, Dr. Malik, do you think at the moment that the question of French Morocco and France's relations with its protectorate is capable of settlement? Well, it is capable of settlement if the French are going to yield, yes. But I find it very difficult for the French at the present moment with all their internal problems and their relations to the African protectorates to proceed with any great hope for an immediate settlement to the problem. So I'm rather pessimistic about the immediate outlook, but in the long run there must be a settlement. Because it is a problem capable of settlement if there is good will all around. Mr. Malik, you're not only the ambassador to the United States from your country, you're the ambassador to the United Nations from Lebanon, and as that ambassador, you're also entitled to a seat on the Security Council. Now, do you think that the problem of Trieste, which is coming up in the Security Council tomorrow, is capable of settlement there? Well, I marvel at your desire to see every problem capable of settlement and immediately. I don't know. I know very little about Trieste. This thing has come up all of a sudden to us in the Council. I'm going to study it this weekend. Again, there are great difficulties there, but I'm not as pessimistic in that problem as I am with regard to some of these other issues. So I think some kind of a modus vivendi will be worked out between Yugoslavia and Italy and the other interested parties. Could I go back to Morocco? The Arabs and their contentions to the Security Council said that Morocco is a threat to international peace and security. Well, now, sir, taking for granted that you have argued that from all the evidence of the case, does it really appear that Morocco is really a threat to the international peace? There's no war there. There's no aggression anywhere. Well, I don't think the Security Council, Mr. Carpenter, should be seized only of those issues which deal with war or with real threat to security. The Charter says any situation that is likely to produce international friction or international disputes. Now, certainly Morocco is producing lots of friction and lots of disputes among nations. And therefore, from that angle, it is certainly worthy of examination both by the Security Council and by the General Assembly. Well, Dr. Malik, you're not only a diplomat, you're also known as a philosopher. Could you tell us, do you believe that coexistence is really possible between the communist world and the free world? If you want my most honest opinion, I'll tell it to you, although I am seen in television now. I believe unless there is a radical, fundamental change of heart in Marxist practice and theory throughout the communist world, I honestly do not see how, in the long run, peaceful coexistence is possible. Do you see any changes in the Marxism philosophy now? I don't see any changes in the fundamental Marxist theory now. I read whatever literature I can get hold of, and I read certainly the pronouncements of the great masters living and dead, and I think it's still the same old Marxist doctrine. Well, there have been fluttering of the dove of peace since Stalin died.  Well, I read Marx, and I read Lenin, and I read Stalin, rather carefully, as much of them as I could. And I do not believe that these men honestly believe that there can be peace until they have communized the whole world. And that's what they say. I'm not saying that. It's they who first said it. Dr. Malik, besides being a diplomat, you were also the chairman of the committee that wrote the Declaration of Human Rights back in 1948. Have you seen any progress in human rights since that declaration was first presented? In the United Nations, so far as developing documents of legal binding force is concerned, we have not made much progress during the last five years. But I can assure you that the influence of that humble declaration, which we proclaimed five years ago, has been most incalculable throughout the world. I would like to pay a tribute to you at this time, because I watched you work during three long months of working that document out. I think that a great part of its value is due to the ideas you contributed.  Could you tell us what, in your opinion, is the current state of American opinion of the UN at this time? I frankly am a bit discouraged, because I find people losing faith in the United Nations at the present moment. I don't think it has the strength in this world organization and make it the real instrument that it should be. But there is a real slump in the feeling of the American people about this matter. Dr. Malik, do you feel there is any relaxation in the world tensions at this time? Yes, there is some relaxation, but it may be very deceptive and we should be most careful not to allow it to lull us into premature letting down our guards. Dr. Malik, may I ask you one final question? Could you tell us what the Arab nations really want from the United States? I think they really want simple things, Mr. Lesard. They want justice, namely that they do not feel at the present moment that they have been justly treated. They want freedom, namely wherever there is a problem where their own liberties are at stake. They want to feel that the United States would help them to achieve freedom. They want a sense of equality with the rest of the world so that people can respect them on a basis of equality. They do not feel that. And finally, they want closer cooperation among themselves. And they would hope that the United States and the other Western powers will not stand in the way of developing whatever natural, closer relations they can develop among themselves. Well, thank you very much, Dr. Charles Malik. We've been very glad to have you here tonight. The opinions you've heard our speakers express tonight have been entirely their own. The editorial board for this edition of the Laun Jean Chronoscope was Larry Leser of the CBS television news staff and Associated Press correspondent Francis W. Parker Carpenter. Our distinguished guest was Dr. Charles Malik, Ambassador from Lebanon to the United States. To watchmakers of the old school, such as Laun Jean, pride of workmanship is a traditional attribute of every detail of every operation. In truth, the smallest cog in a watch is just as important as the biggest wheel. Pride of workmanship made Laun Jean the world's most honored watch. Honored at world's fairs, by 10 grand prizes and 28 gold medals. Honored at government observatories with countless prizes and citations for accuracy. Honored as official watch of leading sports and contest associations, the world over. For you who have an appreciation of the fine and the beautiful, the pride of workmanship, so evident in every Laun Jean watch, makes an irresistible appeal. And our particular message at this time is an important one. If you wish to buy an own or proudly give a truly fine watch, you may select a Laun Jean watch for as little as $71.50. And regardless of the price you pay for that Laun Jean watch, it is made with that pride of workmanship which has made Laun Jean the world's most honored watch. The world's most honored gift. Laun Jean, premier product of the Laun Jean Wittner Watch Company. Since 1866, maker of watches of the highest character. We invite you to join us every Monday, Wednesday and Friday evening at this same time for the Laun Jean Chronoscope. A television journal of the important issues of the hour. Broadcast on behalf of Laun Jean, the world's most honored watch. And Wittner, distinguished companion to the world's honored Laun Jean. This is Frank Knight reminding you that Laun Jean and Wittner watches are sold in service from coast to coast by more than 4,000 leading jewelers who proudly display this emblem. Agency for Laun Jean Wittner Watchers. History repeated and you are there Sundays on the CBS television network.


The Labour leader was also asked why he attended an anti-racism rally over the weekend, which critics say was closely linked with the Socialist Workers Party. So what is the SWP? It was founded as the Socialist Review Group in 1950. The party describes itself as a revolutionary socialist group. They've been involved in various campaigns over the years. For example, former leading members of the SWP helped to set up the Stop the War Coalition to campaign against the invasion of Iraq in 2003. But in 2013 the SWP was mired in controversy because it was claimed that they had mishandled sexual assault allegations against an individual who was, at the time, one of their members. Well, we did invite the SWP onto the programme but they declined. They also told us that Stand Up to Racism is not a front organisation for the SWP. The anti-Nazi League disbanded in the 80s were quickly reformed as a rival group to tap into the growing anti-racist movement. Its public face consists of anti-apartheid campaigners like the MP Peter Hain, and they've claimed support from celebrities such as Lenny Henry and Stephen Frye. But other anti-racists believe it's a recruiting front for the Trotskyite Socialist Workers Party, the SWP. More militant than the ARA, it fights racism by confronting the BNP on the streets. Its two main organisers, Julie Waterson and Paul Holbro, are both SWP activists. The only reason the A&L was reformed was because suddenly the ARA had appeared, it got a lot of attention, a lot of support, and the old SWP suddenly felt, well, I mean, let's revive the A&L, it's a way of bringing people into our party and so on. And I think it was rather cynical. I said, unite against fascism and hope not hate are taxpayer funded, they are trade union funded and they're headed up by very senior Labour Party figures. And I'm perfectly happy to come to my meetings and have an argument with me. But it's not so much fun when they're banging you over head with banners. Well that was Nigel Farage there and joining us now is Wayman Bennett, joint national secretary of unite against fascism and Suzanne Evans, UKIP's Communities Spokesperson. Welcome to both of you. Wayman, have any of your members acted violently or threateningly to Mr Farage when he's appeared in public? Absolutely, that's not the case. We have questioned him, which is unfortunately the reality if you stand as a major politician and want to win elections, the public and the electorate are allowed to question you.


Fy nid, y perthynas rydw i, oedd llawer o bwysiciaeth, rydw i'n dweud eu gwéithfolio, oedden nhw'n dweud eu gwelwch o Brwyr i'rôl coachef Rhefen, Mc Donald, yr rymdffin y ffordd yng nghyfnog? Fy nid, hynny, a heddiw, brin fyddwch i fi i ti fel yma. Fy hwnnw, ddim ddondol ar hynny. Maes gydigio am yr ymwysig i'w glwll i'i. Rydw i wedi ddaw'r iawn i'rchwil i norder ngogi hefydig. I visited an old friend there who has been working as a missionary, working with those who are living in the most extreme poverty circumstances, a nation that's recovering from a horrendous period of civil war, while there I had the honour of preaching to some 300 inmates at Gulu men's prison. Here I am a year later in these hallowed halls, speaking to those who sit at the heart of the Scottish political scene, and I stand before you unclear as to which has been the greater privilege of the two. What could this wee boy from Maryhill in Glasgow, as he grew up, what could he share today? The same wee boy who for himself recognised the importance and the relevance of Christian faith for daily life and living. Who later on would follow what he felt was the call of God to enter the ordain ministry of the Church of Scotland, serving as one of its parish ministers. What could he possibly offer for reflection this day? Perhaps the best thing I could suggest, or at least one of the things I could suggest, is the axiom that was passed on to me from a minister I worked with. He used to say, learn to agree to disagree without being disagreeable. I've used that as a maxim to live by in the life and the worship of the Church. I believe that it's a principle that has ironically held the Church of Scotland in unity, particularly in recent times. I believe that it's also a principle that applies to the political world of democratic debate and practice. All the more so as we move forward from a referendum to a national election. Some will, of course, say that this is naive for the world of politics as a dirty business. That may be so in some instances, but agreeing to disagree without being disagreeable is a goal perhaps that may just exceed our grasp. But it remains a precious ideal to aspire to. Anything outside that ideal is really a haven for discrimination. The late Reverend Peter Marshall of Scotland, who emigrated and eventually became chaplain to the US Senate. He, in one of his great prayers to the leaders of the nation, said, So may we together seek happiness for all our citizens in the name of him who created us all equal in his sight. I read the words of the Apostle Paul in that statement. For the Apostle Paul in writing to the Romans, he wrote, We who are strong ought to bear with the failings of the weak and not to please ourselves. Each of us should please our neighbours for their good, to build them up, agreeing to disagree without being disagreeable. A maxim we can all take on board. May God bless the decisions, the debate and the deliberations that are made this week.


Everybody Matt here for late in sports cars are from one box of 2023 tops archives signature series Retired player edition baseball. This is for Ronald G. Good luck Ronald. This is if on Rodriguez tops total auto one-of-one Yeah, nice Pudge that is from 04 tops total I've pointed this out before but on the archives sig series stamp at third currently Hall of Famers it Says Hall of Fame above the stamp now There you go nice one-of-one Pudge 04 tops total by back auto Congrats Ronald that'll do it for your box appreciate it. We'll get these right out or get this right out