Now we're recording. All right, thank you. All right, welcome everybody to today's technical steering committee meeting. Everybody is welcome to participate in this meeting so long as you abide by the anti trust policy and our community code of conduct. Few announcements as we kick off here. The Brazil boot camp is growing ever closer. I don't know if Karen is on to speak or maybe I see Daniela is on maybe. I can actually go with this one. Um, yes, so the main thing that we needed before I was willing to pull the trigger on the Brazil boot camp was having enough session leaders, and we now have enough session leaders now my big call to the TSC and all of our project project maintainers is to help us make sure that they're all on board for your project. So if you'd like to see a project represented at the Brazil boot camp. Let me know I will be contacting a bunch of y'all individually tomorrow, but this is about making sure that we have they're getting started materials and things of that nature to get people up to so that they're able to get started and start contributing to your project. So that's what we're working on right now. And that's, that's kind of a train the trainers call you're looking for. Yeah, kind of a little bit more mentorship and one of the cool things that you'll get out of it is it's probably pretty likely your stuff will get translated into Portuguese. So they're expecting about 95% of the attendees to be from Brazil. And so they're going to be, it's going to be more in Portuguese and English, and they're going to be translating the materials as well as getting people started on it. Okay, thank you. So everybody heard that so please reach out for your respective project maintainers or contributors to get involved there. All right, cloud interop certification task force. That's awesome me. We're just now starting our journey for doing cloud interoperability certification, and I wanted to issue out a call for volunteers who want to participate in that process. So the very first portion of this we are going to be doing, you know, some of the more boring things like governance and just plain old project management. But eventually we need to make sure that we check in with all of our projects about what the certification process itself will look like. So I know that some of y'all are highly opinionated on this for good reasons, and I think that we should start talking about that now. And I'll be posting all of this to a portion on the wiki. It's going to be public, but not linked to on the menu at the beginning, simply because of the fact that it's all logistical aspects at the beginning. So once it gets a little bit more ironed out, and we don't have to worry about expectation management, then I'll make it on the menu. But at the beginning, I'm just going to have it. It's going to be there. It's going to be public. It's just, there's going to be a lot of blank pages. Okay, I don't recall is this been discussed in earlier TFC meetings or is this as of today. This is one of my goals for the year. So is to we're going to be working on a surface provider certification as well as a cloud interoperability certification. These things are the certifications and are typically run internally simply because there's a huge logistical uplift for a lot of staff to do. I just wanted to bring it all out as early as possible to the TSC that we're doing it so that people can have buy in and contribute to it earlier rather than later. Okay, so yeah, and as you get those materials together maybe just having at least a few lines describing what this is somewhere would be. So what we'll do is with like with all the task force will be doing regular updates to the TSC and recruiting from it. But you know the main difference between work groups and the task force is that something it's basically deliverables from my team. And so there are deliverable things that we have to, you know, keep moving and keep attached to. So it's a little bit different and that it's not as open and self governing. So that's one of the things that we have to accomplish. So we'll be doing that the entire time. Okay. So, well, I can appreciate that, but shouldn't you know the direction come from the TSC the direction in regards to even to do these things right. I mean, I don't have a problem having a discussion about what the right thing to do would be but it seems like you've already decided. So what do you do in regards to what aspect. I don't know what interrupt certification means to be honest. I mean, I can imagine but I don't know what it means. Well, one of the things that will be happening is for each of the projects themselves, they will be determining what their actual test nets are and what those certifications will be. So we have to put together the logistical aspects like the legal contracts, the figuring out where things are going to go all those different kind of aspects, which normally the TSC and the individuals do not do. Okay, so why don't we do this. Can you just please put together what the what the proposal is for this general work area. And then we can have a more structured discussion and have it through the TSC. Let's see if we can be clear whether or not this is an initiative that the TSC is supportive of. Sure. I'm confused by that, but I will talk with Brian about it. Great. So the project lifecycle committee. Our know has kicked off some some males about this which we've linked to in the agenda there are no is is there anything that you'd like to call out at this point. No, not really. I mean, if you follow the link you'll see I basically just send an email. I assume people have seen this on the TSC list, asking for people who are interested to be part of this smaller group, just to be clear. I mean, you know, to everybody, the intent is not to solve all the issues is to just, you know, kind of pre true issues. And so my next step worry. And so I think we'll really have quite a significant number more than I expected. But that's fine. My intent is to next start listing all the issues that I think we have to tackle. And I have actually you asked me last time how long do you think it will take. And I'm thinking, you know, I want to try to prioritize the issue list all the issues we think we have prioritize them and hopefully make progress incrementally, you know, not try to come back to the TSC with everything. Okay, we've been working for three months. This is the result. But instead, try to have a more piecemeal approach, where we can tackle issues independently as much as possible. And so last time, for instance, we talked about the project. So project I say, Well, I don't really want to, to cover it to resolve or trying to discuss this. But now I think, you know, I thought afterwards, well, if we there's no harm in having that on the list of issues if we just don't get entangled in this to the detriment of, you know, addressing any other issues that are probably easier to address. And so that's kind of my thinking now. Yeah, thanks for that night. I think that a smaller group will be a faster moving group. So I think that just so I know that the right put together the wiki page for it. Should we just start using that to start listing some of the issues that we should be talking about. Yes, absolutely. That's what I'm going to start to add some things. Yeah, feel free to do that. That's exactly what I want to offer to everybody to do. So I think that's good. And I will certainly appreciate at least pointers to how these things are resolved in other organizations like Apache or others. Cool. Sorry, where's this page on the wiki. I mean, we have a list. And for now, I just missed the people who have volunteered. But so we can expect right. Part right posted a link in that email thread. Okay, sorry. Yeah, I'm not at work right now. I don't have access to my work email, but okay. It's in the email thread. Okay, thanks a bunch. Sorry for the question then. Okay. I'll add it to the TSC challenge of our chat. Thank you. All right. Next up here, we have, I think. The, the PSWG discussion. The update was up around this time last week, which I hope people have had a chance to take a look at and then Mark wants to lead a discussion about the future direction there. So I will hand things over to Mark. And maybe if we can first hit, if there's any open questions on the update as written and then move into the directional part after that. Sure. Does anybody have any questions on it? I'm not hearing anyone. So overall, after we got the paper out, we sort of waffled or, or wanted a bit trying to figure out what to do next. And I sort of want to, we haven't, we settled on one thing and then stack, we're asked to look at working with stack and so that took us in a different direction for a month or two. So now that we're, that fell through, we're back to, do we work on Providence document for supply chain? Or, you know, what is it that the TSC wants from us and that other projects want from us? There's a lot of cross projects or working groups or SIGs. And a lot of, you know, there's a lot of new SIGs since this group was first formed. And to me, it makes sense that we should probably be off working with subject matter experts. But in the meantime, participation on the calls has dropped down to two or three of us. I'm Hock and Huey from Calipers there and Fippin and I. Todd Little from Oracle is there sometimes and sometimes Arish. And some of the attrition is also Attila and Emre will join, but they're somewhat sporadic at this point. So it's a question of what can we do to re-energize the group, but part of also, you know, what do people want from us? We had the fast fabric people come and talk with us. And, you know, that seemed to energize the group a little bit.   So let's do that as a basis for a start of the discussion and let people hop in. You know, I think one other thing to consider is we have the sort of completion criteria. I can't remember how we phrase it in the working group charters. So we should also think about, you know, declaring success and maybe stepping back for a bit and then later reconstituting a similar group. That's certainly one option. I think that continuing with the working group as is might be more productive than shutting it down and trying to spin it back up later. But I think we should always keep in mind that concluding things is an option that we have. We've concluded the working groups in the past, like we've concluded the major white paper that was oversweeping over all of hyperledger. So, I don't know that this group is done. I mean, you know, one of the reasons that we established it in the first place was because I think there was a, I think, sort of an expectation that at some point, you know, people would want to have, you know, some sort of benchmarking. But what we've defined thus far is a set of metrics that you would measure, not how they are measured necessarily, right, because we don't actually have, I mean, I think, you know, taking a look at caliper other sort of tooling and actually defining a specific test that can yield consistent results is the kind of thing that I think they were, you know, potentially going to engage with stack on but we aren't going to do that apparently because those guys have sort of disappeared. I think, you know, I think it's still on, you know, the working group shoulders to sort of start to think about what does a benchmark look like or what, you know, if we're using caliper, for instance, to measure performance of a particular framework, right, are we able to sort of do consistent things so that you could define a benchmark that could be measured consistently across the various frameworks. So, I, you know, personally, I'd like to see a little bit closer, sort of look at, you know, where are we with caliper, where are we with caliper in terms of does it support all of the certainly the active frameworks and, you know, some of the others as well. And if not, you know, what can we recommend that be done about it. And I would also, I'd like to see us get to the point where we could actually to start defining some benchmarks that people could, you know, reasonably use to make decisions because I mean I don't know about you all but I get a lot of questions from clients and from analysts and so forth about performance and scalability capabilities of the various platforms and, you know, I think, you know, we should get out in front of it. As we finished the, the white paper back in the fall, remember there were there were a few things that we had as as potential next steps, and a lot of those were around faults, because one of the things that makes blockchain special is its fault resilience. And I think if you know there were a couple different directions that the working group thought might be useful to do there. One is is around defining metrics with respect to faults, and another would be working on workloads that that intentionally introduced faults. I think what's particularly valuable about that is that if, if an architecture is designed for the happy path, but any sort of noise in the system makes it grind you a halt. That's going to be something that's important for everybody to understand. And it's also supposed to be something that is unique to blockchain stacks, or at least better about blockchain stacks and other sorts of related technologies. So I think that at least gives two options. One is, is a little bit more of the paper side of defining metrics around those spaces. And then the second would be more the hands on work of introducing faults into some sort of workload. Hi, this is Wiccan. I do support the, you know, Chris's thoughts and yours. Dan, the thing is, in terms of the, in terms of the need for the working group, I think I've always heard that everybody is looking for some objective numbers, which means either it's run by an objective party, or set up in such a way that it can be measured objectively. So for that purpose, we said, I mean, since the load on the system depends on the, on the actual payloads going in and the pattern of use. And some of the more useful stuff has come out of, let's say the settlement post rate settlement work that Accenture and DTCC did for Korda and DAH, we said that we should choose a specific use case. One of the use cases we said would be useful was the provenance one, and we started on it a little bit, but we never really settled on it. The choice of the use case is not just to describe the use case, but also to then run it in Caliper or some such tool. The natural things, natural projects that we would be associating with would be supply chain based project like grid or something else like that. So there has to be some, to Mark's point, some subject matter experts that come to this group. So that is the first thing. The fault injection part, in fact, Imre and Gang are the fault gurus. And we also have a, I wrote something about chaos engineering and the blockchain on medium, which started off this investigation, but I want to make it very practical, because the Indie guys have created a chaos framework around it, around the, you know, the practice. So that is the second thing. But all of this requires engineers and resources with three people or four people showing up to the working group is not going to be enough. So people have to say, you know, how practical is it to mark on these projects without, you know, without there being full time resources on this project. Maybe one of the things would be for interns or somebody to do this from, you know, a company who's interested in a benchmark. The last thing is without a testnet that can be spun up. I know Chris that you think that that testnet should be under some, you know, should be spun up by companies who are interested in these benchmarks, but also we kind of talked about it quite a bit here in terms of the CNCF testnet. I know that, you know, things that didn't go well or whatever. And we don't have such such a rig that can be easily spun up to do this running of the caliper itself. And even, of course, in an advanced stage to do chaos on that testnet, starting with chaos on testnet, then of course, enlarging that to go to production type systems. Anyway, I've spent enough here. So I think focusing on the lack of participation is the wrong thing to do because I mean, for a working group to be successful, you need to clearly define problems to solve. And then you need the right people to participate. But you can't have this ladder unless you have the former. So I think what's happening is, you know, you started with the working group, you figure out a problem to tackle quickly, and there were enough people thinking, hey, this is an interesting problem, I want to participate in solving it. And you issued the paper, you were very successful in doing that in actually fairly timely fashion. And now you find yourself with that really clearly defined problem to solve and so people lose interest, which is not surprising. So I think it's really a matter of whether there is a problem that you can define. I think, you know, I think there is no shame in saying, hey, we've done what we could. Nobody has another problem to solve for us and we should just shut down. I think it's better than trying to solve a problem to solve just for the sake of it. But, you know, in line with what Chris was touching on, I don't know that there is nothing else the group could do. And so I agree with them that, you know, it's a bit of a challenge at this point, but you would have to see, okay, with the basis you've already created with the first report, what is the next step you could go, you know, that would still be platform independent and would still provide some guidelines at least as to what it would take for somebody to set up a framework test bed. Hi, everyone. It's Alex from Saramitsu. I might have one proposal. I don't know if that could be interesting, but maybe since we have a white paper and framework, all the platforms that are under the hyperledger could try to perform the measurement and then submit the reports together with the data to the working group and the working group can review that and say whether the measurement was done in a way that is acceptable and then say, yes, you know, this is the result for a particular platform. I know that there are a lot of open questions, but by having maybe a very ambitious goal, we will also find ourselves discussing those things that are maybe not well defined at the moment as we were discussing the, you know, how to define the load for a particular measurement and, you know, all other things, but once we will try to do this and we are doing this for hyperledger at the moment and see the reports then the working group can will have a material to reflect on the white paper to provide feedback and then end of the day also improve the performance of the particular platforms that are under the hyperledger. This is Silas. My impression looking at Calipa, so we added a fairly simple borrow workload generation to Calipa and run that is that it's kind of fine, but the workloads being unconstrained, it ends up being pretty arbitrary. So you end up finding a simple workload that might perform well and that doesn't really constrain things. So the basic metrics of the read latency and read throughput and stuff kind of make sense.  If you look at something like the computer languages benchmarking game or something like that, that has hundreds of different problems and then you get people competing who particularly like a language to improve their implementation. So I think we're some distance off that but I think it would be useful to if there was a someone defined a standardized workload that has maybe certain things that make it hard on some platforms like some ordering requirements so you can't can't get away with MVCC in some cases or whatever different properties if we can negotiate that and then leave it down to the frameworks to implement their best version of that on a pick size network. That would actually be comparing apples with apples and probably start to build a more realistic picture. I don't find the idea of just the metrics on their own that don't paint a very clear picture really. Right and what we were trying to do and have been working towards is as you start getting into these different verticals. You know, so for supply chain, there's provenance which can apply across a bunch but take the metrics up a level so you know we think these metrics are important for supply chain and provenance in particular, but so then you're starting to define some different use cases and workloads a level up from the original paper and we had, you know, figured that would be the next logical step it's just trying to maintain interest and getting that done is Use cases would be quite hard to achieve consistently. I was thinking more something that that is more like an algorithmic style problem. I mean, maybe it can be synthetic. I think at this level, you know, like with the computer benchmarking game. I'm not sure sort of the that there'll be particular problems that are hard on a particular framework that aren't particularly use case related. I wouldn't thought and I think they should be like fairly easy to implement as well. But just straight sending of transactions that say, you know, don't have to like share state once they get executed is kind of too easy. Having a consistent like use case in a supply chain seems way too high level for I was thinking. I was thinking more like a kind of distributed algorithm at level. I think I want to agree that both performance and the scalability is really important to have a ledger and even to all the open source projects. So in the community we say it's a still hot topic and people talking about it a lot. So if if it's still important but people do not want to join the activity I guess there must be something wrong. I think we should not simply shut down the working group, but rather we should continue the work and we try to find how to attract more persons to join the activities. I think we can send the email to the mail list to ask the people what they want to see in terms of performance and scalability. I did see there are some discussions related to the performance numbers or technical reports. Maybe we can consider extended at the scope and for next step we give some numbers or doing some real evaluation results. So I'm wondering and apologies I don't recall. I think it was maybe who had suggested, you know, maybe we start with, you know, team submitting the projects I should say submitting analysis that they may have done leveraging caliber or something else. To the working group for evaluation and potentially publishing as informational right, non, you know, not as, you know, sort of definitive but as informational. Initially, again, I do think that we need to get to a point where we have some sort of a benchmark that would be my, you know, in lieu of that, being able to have something that, you know, maybe we're just using the same tool chain to do that testing and, you know, with similar kinds of configurations we can start down that path. And I think to Bella's point, you know, it's likely that, you know, if we have something that's actually delivering some meaning something that's meaningful to the various projects that we may get more involvement from them. And then, of course, we always have the problem of, you know, the vipin is trying to do by, you know, sort of brute forcing, you know, the situation with the identity working group and having, you know, doing the Ironman to two meetings a day kind of a thing, versus, I don't know, maybe just moving it around a little bit, but I know personally, I'd like to be involved, I'm actually leading the performance here for an IBM for the work we do on fabric and IBM blockchain platform, but I can't attend that time I have a conflict. So can I just ask it again, moving up a level for a minute, because I think that the concerns that Mark is expressing here are, are ones that apply to all of the working groups. I know the numbers that we see in the architecture working group have gone down. Vipin struggling with identity performance, some of these others. Is it time to step back for just a second and the model that we have right now worked well at the beginning when we were in a very formulation kind of stage. But the emphasis is clearly moved from the work in the working groups into the projects themselves. I know it's, it's a little frustrating to work at times and I don't, I didn't see Rahman this morning, but I know he would express this as well. It's a little frustrating to be in a role where we feel like we're doing nothing more than describing what's already being done in the projects, rather than having some ability to do some influence. The cadence of the groups being every two weeks means that it's much easier to like just not do anything and show up and work for an hour, which means that the pace at which things are being done is insanely slow. Is it time to kind of step back for a second and figure out exactly in general, not just for performance, but in general, what do we expect from the working groups? Do we expect them to be documentation engines that are describing what's being done? Do we expect them to actually be formulating new concepts and ideas? Are they capable of formulating new concepts and ideas better than, for example, the academic researchers who are pushing things forward or better than labs who are doing the experimentations on it? What is the right role for working groups, given the maturity of hyperledger? Well, the other thing I would add to that, Mick, is, you know, there seems to be a huge growth in special interest groups. So maybe the working groups just become special interest groups. I don't know. But they seem to be thriving. The topic specific or application or domain specific kinds of things.  So maybe, you know, instead of this being a working group, it becomes a special interest group. So, hey, this is Brian. So the point of the working groups as, you know, I've understood them when I kind of landed in hyperledger and they already kind of existed was to try to get a degree of cohesion across the projects across the actual development of code, right? So that you could talk about performance in a way that was not rooted, you know, entirely in how one framework chose to implement performance, but was actually a conversation across different projects. And it's always been the hope that working groups created output of some sort, you know, white papers as architecture has. There was even a white people working group once. That sort of thing. But, you know, these things don't have to be ever green. They can be sunsetted. That's fine. But if somebody from the outside asked, you know, does the hyperledger community care about, you know, performance or care about a common approach to identity or architecture?  And, you know, only anything in an open source project only works to the degree that there's interest and motivation on the participants to do it. I would hope that on each project, there'd be people interested in these cross cutting issues.  There's actually a, you know, somewhat of a cohesion to the hyperledger community that this is one of the ways it manifests. And to Mark's concern, this is something very distinct from the special interest groups, at least as they've evolved and we've been managing them. The SIGs are intended to the place where we try to match up the technologists working on the projects with domain experts in a field like healthcare or supply chain configuration or trade finance. And, you know, have, again, it can be cross project, it can be abstracted away from the project so that we should definitely be talking about the projects and what they're doing in this case. And then again, the output should be some sort of content, whether it's blog posts or maybe white papers or maybe just sharing of use cases and that sort of thing that might incidentally drive some requirements or drive interest in contributions back to the projects or even new projects. But there's the difference between the SIGs and the working groups. And my take is if there is momentum lost in the working groups, there's like, like Mick said, no shame in wrapping them up. But we should just recognize that we do need some forms for this cross project communication and coordination from time to time. And we shouldn't just do away with the concept of working groups. Okay, and maybe it's a failure on my part leading the group to, you know, specifically reach out to all the different projects that would be involved. You know, we've had a close working relationship with Caliper, given the nature of our work and the formation of the acceptance of the Caliper project. Yeah, actually, if you, I mean, Caliper, we actually held off on accepting it until we had created the performance working group because there was a desire to create, you know, kind of an abstract definition for what performance meant in a DLT context across things as different as fabric and sawtooth, you know, before kind of authorizing one particular benchmarking tool, which might have been rooted more in one framework than the other. So anyways, and then Mark, it's not a failure on your part or anyone's part. You know, we kind of, you know, we have to work with the interests and the people who show up in the community and what they want to accomplish. I think just making sure we get the word out, which you have been doing and by having this conversation here, this is exactly the right thing. So it's really a question back to the other 35 people on this call, you know, is talking about and having a place for performance across hyperledger across the different hyperledger projects. Important, interesting, useful or not. And if it's not, then we'll just wrap it up and find other ways to express or have those conversations. Attila, I see your hand up. Yeah, two things really picked my interest in this discussion. One is that probably every team for their own platform has some performance testing done. I know this for the bureau or also I don't have a discuss this now. So I think the performance working group would be a nice crossroad to collect these private performance tests and maybe see if some common patterns start to emerge. And it might be a stepping stone towards I don't know cross platform batch parking. I know that this would help a lot with calliper shaping its past. So we try to be platform independent on the world level. But for this we need to see how each project is performing its performance testing. The other thing that's really interesting, I think is the fourth injection and workload kind of things. So everything is kind of boring when everything is good. The interesting things happen when things start to go sideways. So for example, recovery management start to kick in crash for tolerance, Byzantine for tolerance, etc. So this could be another common view among the project to, I don't know, create some scenarios how to try to intentionally crash the systems and see how they react. Okay, so we've got two things that have emerged here one is to Mark's original question. And I guess the thing that that has resounded to me is is getting focus in the next objective and I think maybe the fastest way to do that is Mark for you just take the lead on defining that maybe bringing that back to us here as an update to the working group charter, and then we can rally support around that particular objective and see if we can drive help drive participation then towards that that new end. And then the second issue that has emerged that that Mick is raising is the overall work group efficacy. And I think maybe that probably bears some more offline consideration and discussion before we, we have some sort of action there. Okay, and I guess the other ask I would have is for the different projects. Dan participated and Chris has participated in the PSWG but what do projects want from the performance and scale working group because I think each of the projects sort of has their own performance work going on that's not necessarily in concert with what the PSWG is doing. So, you know how, how can the PSWG become involved in different projects, I guess is one way to look at it and help out. So, maybe the project leads could think about that. Yeah, definitely I think Mark has also done well in reaching out on the mail list on multiple occasions looking for input. So, I think there's, you know, you can only react to the responses that he gets and if we don't get responses there then maybe that's a sign that those aren't productive avenues to go down. All right, the, the last couple things that we have probably require some pre reads. And so I think we'll look for the taxonomy and chairs and vice chairs discussions to get introduced on the mail list first, and then we can, we can discuss those at the next meeting. Sure. I think that that brings us to a close for our agenda this week, and it looks like we'll continue to have some offline discussion on the on marks topic, maybe the working groups in general. And so I'd like people to participate in that on on chat some of that's going on in the TSC channel right now, or on the mail in list the mailing list is of course preferential for mailing list is more preferred for for this type of discussion. So we can capture that and people that aren't available in real time can still participate effectively. And with that, I think we can move this meeting to a close. Thanks Dan. Thanks everyone. Thanks everybody. Thank you guys. Bye.


Hello everyone, welcome to today's class. So what we discussed last time was briefly the dioxiranes where we discussed the mechanism and also the sheep oxidation etc. And then we started looking at the transfer of oxygen or nitrogen via oxaziridines. And we discussed that how reactions such as hydroxylation, amination, epoxylation etc. can be carried out using oxaziridines and different kinds of oxaziridines that can be prepared. And depending on the substituents that are present on the oxaziridines, there is a possibility of maneuvering or selectively doing nitrogen or oxygen as electrophiles, transferring them to the nucleophilic substrate such as enolates or enamines, enols allyl ethers, simple double bonds and like that electron rich molecules. Obviously, electron deficient olefins do not react easily with such with oxaziridines. And now we will go further and see how we can make use of this in a chiral fashion. So what are the n-sulfonyl oxaziridines as I discussed last time that preferentially people use n-sulfonyl oxaziridines more popular than other oxaziridines. And one of the most useful oxaziridines is this type where you have an aromatic ring on to the carbon of the oxaziridine and n-sulfonyl group which is present here on the nitrogen. Now this is an chiral oxaziridine and this can be utilized for reactions with either a chiral substrates or even chiral substrates. So one can make from the chiral substrates enolates or any of that kind enamines, enolates, enols allyl ethers and then react with this and transfer oxygen on to the molecule. In a similar fashion, even this type of n-sulfonyl oxaziridine has also been utilized it. Now these are both chiral molecules whereas one of the most highly cited and used substrate which from camphor is this particular oxaziridine which is very useful and leads to very high optical induction or asymmetric induction. And it has been popularized by Franklin Davis as I mentioned earlier. So you can easily start from the camphor and prepare this highly reactive and sterically hindered camphor based oxaziridine. Now one can prepare chiral enolates that means enolates from chiral substrates and you can use a chiral oxaziridine. I mentioned to you that oxaziridine of this type which is a chiral can be utilized for transferring oxygen to a chiral enolate. So this is the part of the enolate which is formed from this substrate which is again camphor based substrates. So as you can see that if there is a nitrogen here and then SO2 which is part of the camphor based molecule and then you generate or attach this particular part of a ketonic type of molecule then there is a possibility of a deprotonation here. This hydrogen can be deprotonated and you can make the corresponding enolate of this type and which can be like this. Now there is a possibility of somewhat like this and since the large part of the molecule is on this side therefore the small group which is hydrogen goes backside. So this is a favorite possibility of an enolate where the hydrogen the large group is coming towards us because the backside is having steric hindrance of this type. So therefore the hydrogen goes backside and R group comes from this side and now when the oxaziridine is reacted the reaction occurs from the lower side that means from the bottom side. The olefin is flat, hydrogen is backside, this path is backside and then this enolate and R are cis to each other and the oxygen is transferred from the lower side and once oxygen is transferred from the lower side the geometry of the hydroxy groups comes in this fashion. One can see very easily that you have here say you get a ketone here like this and the hydrogen is backside. So you have like this where the oxygen is coming below. Now if oxygen is coming below and if this is backside and the R group is in the front this can be rotated further and this is can be equal to a ketone here and now we can imagine that we have we can remove this and redraw to see that this particular molecule is very similar to. So basically what is done is you rotate it here so that the R group which is coming towards us goes into the plane this is in the plane if that happens then this hydroxy group which is in the plane will come towards us that is how it is shown here. So basically the main thing that is happening is that that enolate ion is formed in such a fashion that the R group which is the larger group is towards this side towards us and the small group goes behind because at the backside the there is a big steric hindrance due to this large camphor based group camphor based substituents and that is how and as you can see that the hydroxylation that has been introduced that has been the hydroxy group that has been introduced is having a tidal center at this stage and if we hydrolyze this then we can get the corresponding alpha hydroxy ester for this diastereomerular show which is shown is actually for this molecule and you can see that it is 20 is to 1 so only very small amount of the corresponding other enantiomer will form during this process. Now there is another pyrrolidine methanol based chiral auxiliary that also has been used now this is the auxiliary in which this part is actually the chiral part and it is introduced with a ketone like this so one can easily prepare it say if one can start with you can start with this and if one takes the corresponding chloride here then we can make this by taking this nitrogen based nucleophile to attack on to this acid halide once this substrate is formed we can do the LDA that means deprotonation of this proton here there are 2 protons we can do the deprotonation and we can make the corresponding enolate and then react it with this oxaziridine to introduce the hydroxy group here. So as you can see that if we take LDA lithium diisopropyl amide you introduce the hydroxy group in this particular fashion with the enantiomeric induction being at this stage like this. On the other hand the same substrate is taken and the base is sodium hexamethyl disilamide actually it is like hexamethyl hexamethyl silamide that deprotonates again in a similar fashion and it introduces the oxygen in a different way than the corresponding lithium diisopropyl amide and both the cases the diastomac excess or diastomac ratio is very high 97 is to 3 and 96 is to 4 and the yield is also fairly good. Now how does this happen we should see that like in the case of lithium as a counter cation when the deprotonation occurs when the deprotonation of this hydrogen occurs from here the also oxygen of the OH is also deprotonated and we have the lithium here which is coordinating to both the oxygens and due to this the lower part of the because this is alpha oriented this is alpha oriented or it is at the bottom of the double bond it is towards the lower part of the double bond therefore the nucleophile attacks from the top side which is what is C C orientation C means now we have something like S configuration we talk in the case of double bond as C configuration. So we have the top part if you can see that it is C configuration it is rotating in the anti-cochloroase. So it is from the top the hydroxy group interacts and therefore what we get is this product. On the other hand when the sodium base is used then sodium is a counter cation and sodium is a counter cation which is not a very good in terms of chelating as much as the lithium plus is there. Now we also have enolate which is having this type of counter cation where there is a sodium plus and here also the OH is deprotonated and you have a sodium plus. Now in comparison to lithium plus the sodium plus the anion is more separated and therefore there is a repulsion dipole repulsion and therefore the two anions as opposed to the lithium type of thing where you can have coordination to both the oxygens there is no possibility of such coordination in the sodium plus therefore there is a dipole repulsion and the molecule turns that this particular part of the auxiliary turns in such a fashion that now this is beta oriented. So this part and this part are away from each other and during the process where this was alpha it has now become beta. So therefore the beta means the above part. So the top part or the beta part is no block because of this particular group and therefore the attack of the nucleophile occurs from the lower side that is alpha side and that leads to the formation of the alpha hydroxy group which is eventually let leads to the alpha hydroxy acid. What is done is that after the transfer of the oxygen as I showed you earlier you can hydrolyze this particular carbon nitrogen bond here by means of 2 mol sulphuric acid 2 mol of sulphuric acid and then you can cleave it and get the corresponding acid. So basically it is an alpha hydroxy acid which is formed which is formed in a chiral fashion by this use of auxiliary which is spirulodine methanol chiral auxiliary and deprotonation and reaction with oxaziridine. We can also look at the other auxiliary such as this oxaziridinones kind of substrates of these two types and you can use the lithium bis trimethyl silyl amide we used earlier sodium bis trimethyl silyl amide you can also use lithium and you can deprotonate here and once the deprotonation is done then of course the corresponding enolate reacts now since these two groups here these two groups here are beta oriented therefore the hydroxy group comes from the alpha side. On the other hand if one takes this as a alpha oriented substituent the group which is transfer comes from the beta side so opposite opposite to this side and as you can see the diastromic reaction is very large and yield is also good. Obviously this is the major product this is the major product in both the cases and the minor products from here the minor product will be this one and from here the minor product will be this one. So we can control the reaction in such a fashion that we can get the major product depending on what kind of oxaziridine known we use it. Now how do we make camphor based oxaziridine molecules which will be useful for reacting as chiral oxaziridines for introducing alpha hydroxy group next to a ketone or any other oxidation. We start with camphor sulfonic acid which looks like this and react it with PCL5 so that we get the corresponding sulfonyl chloride that is SO2Cl and then it is reacted with ammonium hydroxide so that we get the corresponding sulfonamide. Now this sulfonamide is then heated in toluene in the presence of amber list catalyst which is an acidic resin catalyst and there is a apparatus which is called a Dean Stark apparatus which continuously removes the water from the reaction medium. It is required that we continuously siphon off the water from the reaction medium otherwise the product that is going to form that means if this amine here sulfonamide condenses with the carbonyl group here then we get this particular intermediate but then this particular intermediate under this amber list catalyst condition can get protonated and further hydrolyzed and go back to the starting material or even it can go back to the sulfonic acid. And therefore water has to be continuously removed by the use of these Dean Stark apparatus and once this particular product is formed then this is reacted with oxone under basic conditions. Since there is a methyl group on the exoside therefore the oxidation of this amine part of the molecule occurs from the endoside that is from the lower side and then we get this particular reagent which has a complete endo attack of the oxygen. Now this is how camphor based oxaziridine is prepared. Now we can also see that this type of camphor based oxaziridines can be utilized that means before the introduction of the camphor based oxaziridine I had discussed the enolates to be formed from chiral auxiliary based molecules. Now what we are doing it is we have the substrate of this kind where enolate is formed from this chiral substrate. So if we can say for example you take this substrate this enolate here like this. So this is a chiral. So we have a chiral enolate that reacts with the chiral oxaziridine chiral oxaziridine and the transfer of the hydroxy group occurs from the lower side and we get the 84% yield of molecule with 95% enantiomeric excess finally. In a similar fashion here also one can introduce the hydroxy group from chiral this alpha side and can get the corresponding alpha hydroxy lactone here or alpha hydroxy ketone there with high enantiomeric purity. Now how does this happen? Why should it happen in from the lower side? As I mentioned earlier that the enolate attaches to the lower part of the oxaziridine with hydrogen group that is smaller than R1 group being backside and the larger group comes towards this side and thus the oxygen is transferred from the top and that leads to the formation of this molecule here where the hydroxy group has come from the top. As one can see that this is the same as this. That means we just turn in such a fashion that R1 group goes on the top the hydroxy group will come at the bottom. Now if we have a substrate like this when there is no hydrogen but there are two different substrates like H R1 and R2 and if R2 is smaller that means R1 is large then R1 group will come towards us and between the two the smaller R2 group will go on the backside and accordingly the hydroxy group will come from the top when the smaller group is on the backside and then we get the chiral molecule of having configuration of this kind as the major product. So, you have a major product. So, we have seen now two types of things where we have one a chiral oxaziridine other is chiral oxaziridine. Now what can also be done is interestingly that the olefins can react with a molecule of this type here one can take even as a chiral substrate here for example of this kind and when this is reacted with an olefin of this kind which is highly electron rich olefin is like an enamine. What is formed under these conditions with dichloromethane and methanol is final product which is formed is basically this and this can be converted to the corresponding actually it should be hydrogen here hydrogen. So, what happens is the epoxidation takes place from the alpha side to form this alpha epoxide because this group which is a large group which is a beta. Therefore, the double bond forms an epoxide and then this particular lone pair of electron pushes it out and opens up the epoxide to form this alpha hydroxy ammonium ion here to which methanol attacks. So, the methanol basically is attacking onto the ammonium ion here and this positive charge is neutralized to form this where the methoxy group has come from the beta side. Now under acidic conditions here trifluoracetic acid this oxygen is lost and you can generate the similar type of ammonium ion. But then instead of that means we get this here I will not write the lower part of it but then you have positive charge here and hydroxy group here and of course the remaining part. Now this is the one that is reduced with triethylsilane it is a reducing agent and that introduces the hydrogen at this stage. So, one can convert a molecule of this kind to a natural product which is of this type whether is a hydrogen and the hydroxy group has been introduced in a highly stereoselective fashion. Now we will start with another interesting oxidation which is oxidation at the unfunctionalized carbons. It is called as Barton reaction and then there are variations of Barton reaction they are called different types of reagents are utilized and therefore we will group them in Barton and related reactions. Now what is unfunctionalized carbon it is very easy for say you have a ketone and if this hydrogen which is alpha to the carbonyl group or if you take a symmetrical substrates at both the alpha carbons are equally available. So, the alpha carbons are basically activated because of the carbonyl group and therefore it is easy for functionalizing the alpha carbon. But if we have a substrate of somewhat like this we have a substrate where we have hydroxy group here and the hydrogen that we want to functionalize is away here. If we want to functionalize this particular carbon atom then we can oxidize this to the corresponding aldehyde and then one can easily prepare the aldehyde of this type and you can functionalize here you have a hydro. But functionalizing here it is not that easy. That is what has been done by Barton DHR Barton who got the Nobel Prize in 1968 and he has shown how this type of nitrate esters can be utilized for the functionalization at unfunctionalized or oxidation at unfunctionalized carbon. So, we will take it up this particular part in the next class and in the meanwhile you can go through the oxaziridines and look at what are the advantages and disadvantages of that reagent. Thank you, we will see you next time.


This paper predicts that CCUS can decrease 3.8% of China's carbon emissions in 2040, with the greatest reductions occurring in the power in chemical industries. This article was authored by Ping Chen Wang, Bei Bei Shui, Nan Li, and others.


It's finally time. After the craziness that was the gameplay trailer for FNAF Security Breach I am so excited to sit down and listen to the brand new 8-bit big band song for FNAF. Okay, legitimately I cannot express actually how much I adore their last song So I am so excited to hear their rendition of it's been so long You know the man behind the slaughter song ever since they announced it dude I've been so hyped and so I'm so excited to take a break from security breach Maybe we'll get back to it, but I really want to listen to this song Okay, a reminder that links to download the song stream it wherever you want on any musical platform You can it's linked down below all the people that worked on the song to link down below I'm not like sponsored or anything.  This is so hype. All right. You saw me put these headphones on That means it's time.  All right. It's a four minute long song I'm hyped as hell. I just want to jump into it final reminder Everything's linked down below go show some support and let's hop into the 8-bit big band version of the FNAF 2 song It's been so long Also, if the song's a bit loud, who cares? We're here for the song anyways Oh, let's go I love this Oh, I love the arcade. That's great. Oh, this is so good This feels like it naturally works well Oh, I like that This is so good. This is so much better than I thought it would be. I love this singer All right. I love this chorus This feels like it just naturally works well. Gosh, I love this so much. I love the jazz Absolutely phenomenal. I love the uh children in the background too and proper guy Dude, I love when they do that line delivery Good mix up. I love how they managed to make it work. You know Guys, I love this singer She's doing such a great job Legit, this is awesome Little proper text hell. Yeah, dude There's not much I can say because it is just music. So I am trying to listen But I love listening to this this is awesome I love the winking proper guy too. I can I can imagine myself rocking out to this Actually hype. I just love dancing dude. This is great. That's hype. That's awesome. Dude, that was awesome Yes Dude, I love These people they make such great music. Oh my gosh That was everything I was hoping for and more It is very difficult to do a reaction when you're listening to a song because I want to listen to the song Which means I can't really talk But if I'm not talking or if I'm just saying the same thing over and over again like oh man, this is great This is amazing. It's because I am so Intrigued and invested in listening to the song Which is the best thing that can happen Maybe won't make for a good reaction video But that means I legitimately enjoy the song and I do this song is hype as heck. I really want to see them Do more songs. I hope they're not done making you know FNAF songs because I think when they released the the last video They said that they were gonna make it's been so long this time. They didn't say all right now We're gonna do um die in a fire, which is the next living tombstone FNAF 3 song But I hope they do it Um, it is very different from the first two but at the same time, excuse me But at the same time FNAF 2 was very different than FNAF 1 So I want to see what they're gonna do with it legitimately big round of applause to everybody who worked on this You managed to recreate the magic yet a freaking gem and I hope to see much more from you guys in the future Some unfortunate news is that the animations were canceled But kota's uh reasoning for it is completely justified. I completely understand. I'm not upset at all If you're somehow watching this first off. Thanks for clicking on my little video. Also, let it be known I'm sure you don't have to hear it from me a complete stranger on the internet But legitimately the whole community has your back and we wish you the best of luck kota So I'm gonna go jam out to this for the rest of the night. Thank you guys so much for clicking on the video Hopefully you guys enjoyed my reaction of me saying this is great 10 times over again for the span of four minutes Final time links to everything linked down below and please go show support. I'll see you all on the flip side. Goodbye


Welcome to this edition of NASA Images, I'm Lynn Bondrant. During this show, we'll be focusing on historic NASA footage of airplane work. We'll see many tests, including crash tests. Let's go back to 1974 to the NASA Langley Research Center in Virginia for that. Although the safety record of light aircraft continues to improve, there still were 700 crashes in the U.S. last year, resulting in more than 1,300 fatalities. Until now, there has been no reliable method of predicting the behavior of general aviation planes when they do crash. In a joint project with the FAA, NASA is beginning a light aircraft crash safety program at the Langley Research Center in Virginia. This is one of 20 flood damaged planes that will be tested. The actual facility was originally used by Apollo astronauts to practice landing on the moon. The 240-foot-high by 400-foot-long lunar landing practice area is now laced with cables, which are attached to the highly instrumented aircraft before it comes crashing to the ground. Dummy's riding in the passenger seats are instrumented to measure G-forces. Engineers hope to learn what happens to an airframe structure when it impacts and to develop an analytical design tool that can be turned over to the designers and builders of general aviation planes. For this first check-out test, the plane is complete except for tail section and engines. Comparable weights take the place of missing parts, and the fuel tanks are filled with water for weight and balance. This first crash was made at an impact speed of 30 miles per hour. Future drops will be at speeds up to 60 miles per hour. Here you can see some of the resulting damage, most of which was confined to the nose and underside of the aircraft. Describing the program that will follow this series of crash tests, Langley engineer Bob Thompson. In the future, what we hope to learn is to integrate some energy absorption concepts into airframe design technology. This gives the aircraft designer some means of putting together the energy absorption concepts with the airframe. Crash worthiness tests like these may one day lead to the design of lightweight aircraft that can absorb much of the impact energy of a crash and hopefully reduce fatalities. In 1975, NASA Langley engineers are crash testing helicopters. It's on purpose at NASA's Langley Research Center in Virginia. In this case, a 22,000-pound Army helicopter. The big CH-47 helicopter had earlier been damaged by fire at the plant where it was manufactured, making it a good candidate for the crash-worthiness test. Watch again, this time in slow motion because the helicopter is dropped 50 feet to the concrete below. The highly instrumented craft is being used in a cooperative test experiment with the U.S. Army to improve design and safety features of future helicopters. Crash worthiness tests giving aircraft designers important structural information before they go to the drawing boards. One of the possible problems with which pilots must deal when landing planes is wake turbulence or vortices of air which trails planes. These model airplanes have something in common with these Rio planes. They are all part of a NASA research program to learn more about vortices, tornado-like patterns of air that trail behind the wings of airplanes causing varying degrees of turbulence. Dave Scott, Acting Director of NASA's Flight Research Center in California, explains. The vortices are dangerous because these bundles of energy as they follow behind the aircraft leaving awake have the capability of turning over smaller aircraft as they approach a landing. And because of this we have a great deal of concern that many accidents can be caused by the vortices or these bundles of energy as they attempt to turn over an aircraft. While all aircraft cause vortices, large heavy jets such as the 747 and DC-10 create the more serious problems. Air traffic density around major airports adds to the severity of the problem. Because of the many aircraft coming in for a landing in the need to sequence one plane behind the other, aircraft are routinely separated at safe distances to avoid the trailing vortex problem. However, this often results in increased fuel use and traffic delays. Smoke generators mounted on the wings of these planes by NASA researchers make it possible to see and investigate the whirling air patterns. The research has shown that by adjusting wing flaps at different angles and by making various design changes, the intensity of the vortices can be substantially reduced. This kind of aeronautical research today may very well result in even safer, more convenient flights in the future. For our next clip made in 1974, let's go to California where aerodynamic truck tests were made in an effort to reduce fuel use. They come in all sizes, these movers of everything from lettuce to steel. Their box-like shapes allow the packing of high-volume loads. It's believed that both trucks and recreational vehicles like this can be made more economical to operate. In the past, as trucks were manufactured larger and larger, engine size was increased to handle the heavier loads. Now with the continuing fuel problems, engineers are attempting to make the big trucks more efficient. In a joint effort, NASA and the Department of Transportation are in the midst of a research program to do just that. The tests are being done at NASA's Flight Research Center near the Mojave Desert in California on an auxiliary runway. Project engineer Ed Sultzman explains. The experience and background that we have here at the NASA Flight Research Center that bears on tests such as this goes back to the aerodynamics experiments that we've done on various aircraft. And really the means of achieving aerodynamic efficiency on aircraft isn't that different than it is on automobiles and trucks, excepting, of course, on trucks and automobiles you're working at lower speed. Starting with a small delivery van, Ed Sultzman and his team of engineers reshape the vehicle with sheet metal. The test truck has evolved from a square box to its present shape with rounded corners. The major emphasis has been on the elimination of drag, wind resistance that forces the engine to work harder. The method used to define drag is known as the coast down method. After accelerating the truck to 65 miles per hour, the gears are disengaged and the truck is allowed to coast. The deceleration is monitored closely because the time it takes to slow down can be directly converted into drag. So far aerodynamic drag has been decreased a little over 50%. The thing that we're all interested in, of course, is the savings in fuel, the miles per gallon that we can achieve rather than the aerodynamic drag, per se. And the aerodynamic improvements that we've experienced so far are translatable into fuel savings at cruise conditions when you're going down the highway at highway speed, somewhere in the neighborhood of all 15%, perhaps 20% savings in fuel. Other secondary benefits include less pollution and increased engine life. This big tractor trailer, typical of many on U.S. highways, is also being studied. Here engineers attach one of many add-on devices that will modify airflow around the truck and hopefully reduce drag. To help them visualize the flow of air patterns, six-inch long strings or tufts are attached and photographed. These have been used in aeronautical research for years. Another method involves pumping a powder-like substance over the truck as it travels along. A large tractor trailer program has just begun and it's too soon to predict how much fuel might be saved as a result of the truck modifications. A fuel savings of as little as 5%, however, would save thousands of barrels of fuel every day. The researchers are hopeful as they continue to apply aerodynamic techniques to help solve a ground transportation problem. Let's go back into the air for our next clip from 1976. The clip explains that the first day in NASA is for aeronautics. The clip ties together several of the ideas from other films used in the show. For 60 years, NASA has been pioneering in aeronautical research. During World War II, the need was for real-time problem-solving and responding to a variety of crises associated with American bomber and fighter planes. Today, research is aimed at making planes fly higher, faster, farther, quieter, and with greater safety. Consider the problem of wake vortices, invisible tornado-like patterns of air that trail behind large jets causing dangerously turbulent conditions for smaller planes following in their wake. The turbulence is so severe that flight controllers must carefully space takeoffs and landings to avoid them. Research on wake vortices has ranged from studies like these at NASA's Flight Research Center in California, where different combinations of gear and flaps are used to break up the vortex, to an experimental laser system at the Marshall Space Flight Center in Huntsville, Alabama. Working with the FAA, the experimental laser program is an effort to develop an accurate wake vortex detection and monitoring system that would permit tracking the path of the vortices produced by large aircraft. Steel-tested at the John F. Kennedy International Airport in New York, the laser research may one day help make commercial air traffic safer. Information gained by flights of the 2,000 mile-per-hour YF-12 will help the designers of new aircraft and spacecraft. Heating, stability and control, aircraft loads, these are just a few of the many tests underway, using the high-speed planes as flying research tools. The rocket-powered X-24B has completed 36 missions over the California desert near the Flight Research Center, bringing to a close experimental rocket-powered flight tests that began with the XS-1 in 1946. These unique planes have proved extremely valuable in advanced aeronautical research. Using the same aeronautical know-how used to design sleek high-speed jet planes, NASA engineers are cooperating with the Department of Transportation to test a variety of fuel-saving modifications for large trucks. Even the simple changes have provided a 40% reduction in aerodynamic drag, wind resistance that forces the truck engine to work harder. This translates directly into a highway cruise fuel reduction of 20 to 25%. An interesting ground transportation problem being aided by aeronautical research techniques. At the Langley Research Center in Hampton, Virginia, they're crashing airplanes on purpose. Engineers hope that these crash-worthiness tests will help designers build lightweight aircraft that can absorb much of the impact energy of a crash, reducing injuries and fatalities. This is a pilot's eye view coming in for a landing, but there's an easier, less expensive way to fly. It's called the Flight Simulator for Advanced Aircraft. What the pilot sees and hears in this simulator at NASA's Ames Research Center is like the real thing. Another advanced research tool for designing and evaluating aircraft performance without ever leaving the ground. First A in NASA stands for aeronautics. Research aimed at improving the quality and safety of flying. Our next clip from 1976 shows an unusual scissor-like plane design. The scene is an arid lakebed at NASA's Dryden Flight Research Center near the Mojave Desert in California. It's early morning. Engineers and technicians have been here since before sunup. Check out and preparations for the upcoming flight test are painstaking and deliberate. This is not an ordinary plane. It has a scissor-like design that could prove to be the shape of aircraft to come. Studies indicate that if the design features of the oblique wing, as this 25-foot model is called, were applied to full-sized jets, it would allow them to travel faster than sound without leaving the usual sonic boom in their wake and give them increased fuel economy. Before the oblique wing plane takes off, a television-equipped aircraft sweeps over and scans the flight path. What the camera sees will aid this man, the pilot of the oblique wing model. He actually flies the plane from inside this van. Another television camera mounted in the nose of the test aircraft lets him see where the plane's going. Watch now as the ground crews start the engine and launch the oblique wing plane. Crews carefully record how the aircraft responds to a variety of maneuvers. They compare these responses with wind tunnel predictions to better understand what the aircraft is doing and why it's doing it. As you can see, the wing on the aircraft is at an angle to the fuselage such that the left wing points forward of the aircraft. The normal airplanes, the wings are at right angle to the fuselage. On this aircraft, the wing is at an oblique angle such that the left wing points forward and the right wing points aft, and this feature allows the aircraft to have much lower transonic drag than a conventional aircraft. For a transonic airplane designed to use this wing, you would fly at 100 to 200 miles an hour with the wing at zero degrees of yaw. As the speed increases, the wing yaw is increased. Research has shown that oblique winged aircraft compared to fixed wing planes use less fuel and can reduce sonic boom levels. The plane's designer, R.T. Jones, says that using the oblique wing takes maximum advantage of wing sweep in a way that fools the wind by making it think you're going slower than you actually are. The next phase of research could include a 1,500-pound plane with a 30-foot wingspan powered by jet engines. It would have a pilot on board. These artist concepts show how the oblique wing design might be applied to transport type aircraft. The wing, of course, would swing back to a more conventional position for landing. The oblique wing, a unique design that may one day allow planes to fly faster, quieter, and use less fuel. Space engineers have even tested plane designs underwater as we see in this 1977 report from the NASA Dryden Flight Center, California. Ever see a jet plane fly underwater? Well, this model of a 747 almost does just that. But consider first what led to these interesting underwater studies. NASA researchers are trying to solve the problem of wake vortices. Those funnel-like patterns of air that swirl off the wings of planes as they speed along. The larger the plane, the larger the vortex and resulting problem. Vortices can't be seen unless smoke or dipods are attached to the wings. Here the second test plane intentionally follows much closer than normal. This allows engineers to visually observe and study both the vortex and its results. Come all together by carefully spacing takeoffs and landings. If the vortices can be reduced or eliminated, however, it will cut down air traffic delays at many of our busy airports. This is hydronautics in Laurel, Maryland. It was here that NASA recently completed a series of tests to look at the vortex problem from a different angle, underwater. The tank used is 425 feet long, 25 feet wide, and 12 feet deep. Testing an aircraft in water might seem like a strange idea, but water and air are both fluid mediums and the advantage of using water in this case is that you can simulate a Reynolds number much closer to the Reynolds number that you use in flight. And Reynolds number is one of the correlations that you do, one of the ways that you get the scale effects from model testing to flight testing. The vortex generating model is mounted on the carriage and this motor driven carriage moves the model through the water channel. The following model, the small business jet, is mounted on a separate carriage downstream of the generating aircraft. And the test lasts approximately 25 seconds and you get maybe 15 seconds of data from this test run, where the two models are moving on separate carriages through the water towing facilities. As the test progresses, dye is let out of the wingtips of the generator aircraft and this dye will swirl up in the vortex, the axial velocity, so that you can actually see the vortex in the film that we take of the test. Tests of the wake vortices research are encouraging. While NASA is having success in changing air flow over the wings using flaps and deflectors to break up the vortices, the FAA is working to develop instruments to detect and thus avoid them. All part of a continuing effort to improve the safety and comfort of air travel. Our final historic clip is called From Kites to Wings, the year is 1975. Many sports enthusiasts around the world call it hang gliding. 63-year-old aeronautical engineer Francis M. Rogalo, now retired from NASA's Langley Research Center in Hampton, Virginia, he and his wife Gertrude, who co-invented the wing, live in Kitty Hawk, North Carolina. Rogalo enjoys flying a couple of times a week from what's been called the highest sand dune on the east coast, Jockey Ridge. Turn to the left and come down. With a hang glider, as with other aircraft, you have freedom of up and down direction as well as the others. And just getting your feet off the ground and being lifted by the air is a new experience. Before Rogalo, the renewed interest as represented by hang gliding takes on particular significance. The big kites represent more than two decades of research, much of it on his own time. In 1963, he and his wife Gertrude received from NASA one of the highest cash awards ever given for an invention. The invention was not an accident at all. It was a purposeful search for a kind of wing that would be less expensive, more rugged, more practical than the conventional kind of wing. And we studied everything along that line that there had already been, like boat sales, windmills, parachutes, and airplane wings before coming up with this design. Experimenting with small gliders and kites, a good performing, completely flexible wing finally evolved in 1948. Ten years later, NASA was searching for devices that could be used to bring astronauts and their spacecraft to a safe landing on Earth. Many versions had many names, paraglider, para-wing, gliding parachute, and flexible wings. The basic design seen in all these can be seen in most hang gliders flying today. Intensive testing ranged all the way from small wind tunnel models to full-scale flight tests complete with man and spacecraft attached. While the Rogalo wing, as it is known by many, has had limited applications, Rogalo himself is optimistic that the new interest generated by some 20,000 fliers worldwide will produce other uses in the future. That's it for this edition of NASA Images. Until next time, this is Lynn Bondrant saying goodbye from the NASA Lewis Research Center in Cleveland, Ohio.


The questions are about the constructs. So when the questions come in about sexuality, sexuality requires judgment. It has categories. It's homosexual, it's heterosexual, it's bisexual. Some of you know the story of a course of miracles, Helen Shepman and Bill Thetford. They said for much of his life he was identified as homosexual. And then the friends of mine who he lived with the last years of his life, they lived right over in Honolulu. So they knew him intimately. They said, well actually by the end of his life he was asexual. He was non-sexual. He was a non-sexual being from years. He was one of the first two course of miracles students on the planet. It's kind of interesting to hear, okay, how did it go for him before he laid aside the body? He went to asexual. But when you look at it in terms of preferences and so on and so forth, all those categories including attractions, repulsion, likes, dislikes, fetishes, on and on and on, that's still part of the world of concepts. And really the course isn't trying to make a judgment on any of the concepts. It's just saying, come with me and empty your mind of everything you think you think and think you know and come into a place of non-judgment and stillness. And that is a transcendent experience. Even if you just have some transcendent experiences, you get a taste of it. You go, hmm, I like that feeling of that vastness, whatever that was, I can't even label it, but it feels vast, expansive. And then you keep giving yourself over yielding into that, aligning with that. And that's where you could say that the questions start to dissolve. The experience of the spirit starts to actually dissolve the questions. Because the truth of who we are just is a state of certainty. It doesn't have questions. And yet for those that open up on the spiritual journey, it's good to ask questions and feel free to ask questions, but I really feel forgiveness dissolves the questions. So it's more like Kirsten was saying, you open up more and more into an experience and you really don't have a need to define it. If you've defined sex as an act, or with a starting point and an end point on the timeline, then at some point you have experiences to go, whoa, whatever I just experienced there, it wasn't on the timeline anymore. And then it starts to dissolve the concepts of what you think is real, how you identify yourself. Because we're so much more than any of those concepts. It's just part of a dissolving process. Or even what you think sex is. Yeah, exactly. Because it's just labels. Yeah. I think for most of this, like if I mentioned the word religion, we evolve with our experience of religion. I know sometimes people will tell me, I'm not really religious anymore, but I'm spiritual. And what they're meaning is a lot of their theological concepts of dos and don'ts and good people do this and bad people and this is punishable and all these things start to loosen. And we start to go really, we start to really question this idea of punishment. Why would God punish? Even children start to say, that's pretty strange. Why would God punish? Why would love punish? And we start to question morality. And we start to question ethics and so forth. And oftentimes labels just come. People will say, well, what are your sexual tendencies? And are you polygamous? Are you monogamous? Are you homosexual, heterosexual, bisexual? You see, there's a lot of categories, just like we have categories for everything in this world. And at some point, we start to loosen from those categories. And it can be a little scary to be loosening from those categories because it's the familiar, but you do get drawn more into what we call the unknown or it's our normal thing, the known, you're drawn into the known and the categories start to drop away. And so is the guilt because the categories and the judgments and the guilt were all synonymous. So it's good. It's good news.


By 2050, more than 4.7 billion people worldwide will be suffering from myopia, also called as near sightedness. That will represent nearly 50% of the world's total population. So why are myopic numbers increasing across the world? Researchers think that longer hours spent doing near work and fewer hours spent doing outside work is primarily to be blamed for the increase in myopia. Near work is an activity that is primarily related to something very close to your eyes. It includes activities like reading, writing, watching television, or even looking at your mobile phones. So is there anything that we can do to check the rise in the myopia cases? For this, we need to understand why myopia occurs. Myopia occurs if the eyeballs are too long or the cornea is too curved. As a result, the light entering the eye isn't focused correctly and you find the distant objects blurred. Researchers believe that more outside time can delay the onset of myopia. One popular belief is that extra sunlight increases the release of dopamine into the retina and checks the growth of the eyes. So mind you, it only seems to delay the onset of myopia. It does not appear to slow down the rate of myopia once the child has developed the condition. For children who have already been diagnosed with myopia, the parents can ask the children to take frequent breaks from their long duration near works. Have them practice the elbow rule that is holding and placing the material at least an elbow lens away from their eyes. Consider methods to control myopia like myopia controlling glasses, eye drops, and contact lenses as early as possible in their life. Myopia may be a silent epidemic, but it is not a hopeless case. By creating awareness on it and acting on it can slow down or even reverse this near sightedness in our future generations.


Hey what's up guys welcome to our training reviews so I'm pretty excited this is the OnePlus 7 pro and this is the unboxing so let's just get straight into it. Okay so let's go ahead and unbox this so you have the OnePlus case here so this comes out you have the welcome pack here inside that you have the clear silicone cover for the phone you've got the invitation letter as well that comes with it and then also the sim card tray opener there as well and usually they send stickers yep they have some there and you've got some there at the bottom as well so that's pretty cool and then there's the phone so this one is the nebula blue so let me go ahead and peel that off now just from holding this you can feel actually how nice that looks so there you have the nebula blue also we have the power plug which is compatible with warp charging and then you also have your usb c superfast warp charge cable there in the classic one plus red so there you have it guys so that's a quick unboxing of what comes with the one plus seven pro now i'm going to give you a camera comparison with this and the samsung s10 plus and i'm also going to be doing a full review of the features that come with this the highlight features of the one plus seven in general and also the good points and the bad points about this phone so make sure you hit that subscribe button below and you won't miss those videos coming up very soon if you have any other questions if there's anything specific you'd like me to review specifically with this one plus seven pro then do drop a comment below so thanks for watching guys i've got tons more videos coming out which i know you're going to like so make sure you don't miss those and i'll see you guys at the next one take care


This short video is a way to demonstrate the importance the mine action and housing land and property AORs are giving to the critical issue of land rights in mine action. This video demonstrates the collective efforts being made by our two AORs to not only break down the silos, but also ensure protection mainstreaming. There is some excellent work being undertaken in various humanitarian operations in building linkages between mine action and housing land and property specialists. But these collaboration and linkages need to be systematized and scaled up to ensure collective protection outcomes and ensuring mine action and land rights are truly contributing to the peace and security human rights and sustainable development goals. Land is fundamental to the enjoyment of human rights, right to food, right to adequate housing, rights of the indigenous people, women's housing land and property rights and many others. Land is also a driver and trigger of conflict in many regions across the world. Additionally, land will increasingly become a scarce resource and add to the mix of other global challenges we face today. Urbanization, massive population growth, migration, increased food insecurity and climate change. As pointed out by Christelle, land is fundamental to peace and security, human rights and sustainable development. And the housing land and property area of responsibility thanks the mine action actors for prioritizing land across your various operations and taking leadership on the issue of land rights. Thank you. Mine action is first and foremost about releasing land. It is about transforming inaccessible areas into accessible and exploitable land. It is thus important to have as much clarity as possible on land rights and land ownership before undertaking clearance operation. Mine action, by definition, is humanitarian and we should always ask ourselves if the land is given back to the intended beneficiaries and those most in needs. To be sure, it is beyond the mandate of mine action organizations to fix land problems. However, there are a range of actions that they can take to ensure they do no harm and respond to the land issue they encounter. I will focus on a few specific actions which are mainly targeted at mine action organization. However, some of them are also relevant for other actors such as donors. First, it is important to liaise with humanitarian and development organization dealing with land issues and to take into account land rights when setting mine action priorities. Mine action organization should avoid clearing land that is disputed if there is equally high priority and disputed land that needs to be cleared. Second, mine action organization should raise awareness about land rights with affected communities and involve them in identifying clearance priorities. Informing local communities about the land rights and hearing from them about community priorities, concerns regarding land use and perception of tenure security will reduce risk of land grabbing. If this is deemed to be too delicate for mine action organization, they should partner with NGOs who are able to engage in this work. Third, mine action organization should ensure a formal and participatory handover process. It is important to involve local communities, intended beneficiaries, government representatives and so on in the handover and ensure that the release of land is widely communicated to those absent. Fourth, we need to recognize the special needs and vulnerabilities of women. After conflict, female-headed households are the most vulnerable to land grabbing. We need to ensure they are included and actively participate in surveys and consultations in order to take into account the specific needs and priorities. Fifth, it is key to report on the developmental outcomes of mine action. Success and impact of mine action should be measured in terms of development of agriculture, infrastructure and economic opportunities. It should not be limited to the number of square meters cleared or the number of mines destroyed. In addition, post-clearance assessment should be more frequent and systematic as it allows examining if originally intended beneficiaries are actually the occupants of cleared land. And last point, donors should include land rights in tendering and contracting processes. Statements of work should include land rights consideration to be taken into account by bidders and contractors. To sum up and conclude, I would say that mine action is not purely technical undertaking. It is related to broader issues and it often takes place in complex environments. Mine action can be political.