Everybody Matt here for late in sports cards ripping 2023 tops finest baseball hobby eight box full case break number 60 random divisions All right, here we go. We will randomize eight times. Good luck one two three four five six seven and eight Brian G down to Tom C and eight times on divisions one two three four five six seven eight NLE's down to NL West All right. We have Brian G NLE East Sean P. AL West Justin S. NL central Jonathan J. AL central Daniel B AL East and Tom C NL West Posts those results and we'll get this started. All right results are posted. There's a link. Let's do it It's on an Amazon and Asia As I understand it anyway Here we go. How about a super? There's Jordan Walker rookie Aqua shimmer to 175 for the NL central nice start and behind it NLE East rookie blue refractor auto to 150 von grissom you go NLE East Brian G Corbin Carroll rookie Pagaro Alex Braggman Refractor Tray Turner headliners Mariano Riley Green rookie Oscar Gonzalez Luba Oscar Coloss and Brett Bady rookie sky blue 300 Marta Kodaisenga rookie refractor Josh Young rookie Mr. Steer and headliners Yellich Jonathan Aranda rookie Aqua refractor to 199 Tatis headliners and NL West rookie auto Gabriel Moreno NL West Joy Vada refractor Dylan Carlson. That's extended base Christopher Morell Headliners Juan Soto rookie refractor Bo Nailer Ruiz and purple refractor to 250 Carlos Correa Francisco Alvarez rookie. All right box number two Rissum There's a Luba world spinist Gunner Henderson rookie Buxton and Machado refractor Muto headliners Ken Griffey Jr. Jordan Walker rookie and Luis Castillo blue refractor to 150 Logan O'Hoppe and Aaron judge refractor Bo Nailer Baez headliners Mookie and Orioles, that's AL East Otto Ryan Mount Castle Kodaisenga rookie Rookie design variation Christopher Morell rookie refractor Gabriel Moreno Michael Harris rookie Raleigh and Mookie Betts green lava to 99 red baby headliners Vlad Mitchell Anthony Volpe rookie Conforto refractor Nolan Gorman rookie Shane beaver blue Aqua vapor to 250 and AL West rookie Otto Shane Langleers Tris Coming up in two minutes and 35 seconds Justin Fields signs of baby I want to see that rice terrain Chipper Jones rivalries die cut Max Meyer rookie Aqua shimmer to 175 and Nolan Gorman Rissum Anthony Volpe rookie Shintaro Fuji Nami rookie refractor Headliners Randy Johnson Gunner Henderson rookie Buxton and Cal Raleigh sky blue refractor to 300 Bo Bechette refractor and NL central rookie blue refractor Otto to 150 Matthew Libretor NL central Jordan Walker rookie Headliners Bryce Harper Lou Bob Michael Conforto green speckle to 125 Josh young rookie Spencer steer Bobby Witt junior refractor Hunter Brown Francisco Lindor extended base J. J. Bladet headliners are a notto Michael Harris Ken Waldechuk rookie refractor O'Neill cruise and Brett Beatty rookie design variation refractor to 99 NL East This is NL West Otto Sean Green Jayrod Masatake Yoshida rookie Aqua refractor to 199 Jose Ramirez refractor Francisco Alvarez rookie Seager headliners Pujols Corbin Carroll rookie Peter Lonzo O'Neill cruise sky blue refractor to 300 Ezekiel Tovar rookie refractor Riley green rookie Headliners Ichiro and NL West Otto Logan Webb Vanessa Spantino and NL West rookie green wave Otto to 99 James Altman You go NL West Tom C. Kodaisenga rookie Lava to 100 Masatake Yoshida Mike trout refractor Jonathan Aranda Bryce Harper purple refractor to 250 Here in box number four Headliners Derek Jeter So two to go in 22 23 Donner's basketball team all 20 box full case number two random teams Ugly uh Devers Tony rookie design variation Gabriel Moreno. Here we go box number five Brigero and rookie rose gold to 75 Garrett Mitchell Riley green rookie rookie refractor Corbin Carroll Oscar Colas rookie design variation Shaylanga Lears Josh Young Tel Marta and NL West rookie Otto Matthew batten Bryce Harper and soda that is Sorry about that. It's an Austin Riley refractor Miguel Vargas and Logan Ohapi that is blue aqua vapor refractor rookie Al West Acunha headliners and Michael Harris rookie nice color coming back to back here That is von Grissom rookie design variation gold refractor to 50 That is NL East And NL central rookie gold refractor Otto to 50 Alec Burleson He might not be a cardinal this time tomorrow and draw some trade interests Is equal to ran hunter green refractor your Mitchell red baby headliners Cal Ripken Nolan Gorman rookie Vlad junior aqua refractor to 199 Raza Patrick how's it going? Von Grissom Anthony folk Bay rookie and Oscar Gonzalez rookie refractor Gunner Henderson rookie Headliners Winfield Cabrera X number six. Oh, did you that sucks? I hear that Shouldn't have had a head home earlier.  Sorry to hear that von Grissom rookie design variation Moreno must talk to Yoshida Beltray Logan web refractor and AL West Otto Jose Conceco Mike trout Cal Mitchell Shohei Otani worlds finest AL West Mookie and Cal Mitchell rookie green refractor to 99 Tony Zack Wheeler Fractor Christopher Morell headliners Nolan Ryan Jazz Chisholm and purple refractors to 51 Soto Francisco Alvarez rookie Francisco Alvarez rookie refractor Corbyn Carroll rookie. What is that? Is this a buyback coming? There's a headliners Otani I think this is gonna be a finest buybacks 18 up 20. That is AL West Miguel Tejada Nice finest originals buyback from 99 tops finest 18 of 20 second one of these I pulled Entering second of the Tahana. I mean, I think that's a third overall that I pulled Because we have two to go on Donress basketball team all in just 49 99 a spot Random team style 20 box case rookie design variation Brett Beatty Corbyn Carroll rookie and Francisco Alvarez rookie Seager Josh Young rookie refractor Garo and Logan Ohapi rookie Aqua shimmer to 175 AL West headliners Mariano Riley Greene Goldie Josh Young rookie and menace Marta and Gabriel Moreno Green speckle rookie to 125 This is AL East finest moments auto Carlton Fisk AL East answer steer Juan Soto rivalries Gabriel Moreno rookie lava around Juan Soto refractor a headliners Yellich Michael Harris rookie This is AL East rookie Greenway vato to 99 Kyle Stowers Brett Beatty rookie rice Harper refractor Nolan Gorman rookie J rod Frank headliners Vlad right last box Aaron Buxton Cory Seager blue refractor to 150 Kunya and Alvarez.   I Was a big peewee Herman Finn In my younger years, which I'm sure surprises everybody Jordan Walker rookie O'Naylor Adley Logan Ohapi headliners Devers and NLS or I'm sorry AL West. Hold on It's nationals NLE East rookie auto Alex Call I see the bottom of that and it tricks me. I think it's the Rangers Um codis Senga Shane beaver freddy freeman refractor 70 years old. That's I wouldn't have guessed that Benny Pascuantino Paul gulchman purple refractor to 250 masatake Yoshida simian woods Richardson rookie green lava to 99 and NL central rookie green refractor auto to 99 canon smith and jigba under christian Yellich refractor Headliners tautis Well, let's finish strong here. That is AL central rookie auto max castillo tsunami packs maybe a big parallel Christopher Morell Otani join manessus rookie refractor as Chisholm Miguel Cabrera and sky blue refractor to 300 rookie Ezekiel Doran AL West there's one Soto headliners and Zach Wheeler Let me just a second here. We'll do a recap Yeah, they're brothers All right Our autos we had NL central rookie green refractor auto to 99 canon smith and jigba AL central rookie auto max castillo This is NL east rookie auto alex call AL east rookie green wave auto to 99 Kyle stowers AL east finest moments auto Carlton fisk. He still has a great auto um AL west finest originals buyback auto to 20 Miguel Tejada AL west auto jose canseco NL west rookie auto matthew batten NL west auto logan web NL central rookie blue refractor auto to 150 matthew liberator NL west auto shawn green AL west rookie auto Shea langal ears AL east auto ryan mount castle NL west rookie auto hybril merino NL east rookie blue refractor auto to 150 von grissom NL central rookie gold refractor auto to 50 alex burleson And NL west rookie green wave auto to 99 james altman Every division got on the board. I'll do it for the break. Thank you everybody. Uh, we have tops chrome mixers up next


So today we have a special report and it's going to be about DocuScience. The stock is DOCU. I took a trade on Friday and I thought I really missed the trader. I was a bit slow maybe, but there's some information that came out and said otherwise. So in this video, I'll be breaking down something that's quite interesting and it's been happening more and more. So as usual, before getting the video, this is not financial advice. This is just my personal opinion. And also, if you're looking for the best tool to trade and invest, everything will be linked down below. So don't forget to check that out. Let's jump right in. To last Friday, I took a trade and it was on DOCU, as I mentioned. And you can see over here, I was a bit late. I wish I would have been able to get in the middle of that candle. And I also really butchered the execution just overall. Like it was a bad trade and I was frustrated, but somebody sent me something over the weekend. And let's take a look at it. So we have over here how this is allowed. Today, DocuScience received 11k a new volume on out of money option. 57 calls expiring today at 10 to 10 30 a.m. So this is the biggest part. So the volume over here, 57 calls. I mean, it can happen. Somebody can take a bet, but the expiring today and somebody buying these like random calls at 10 to 10 30 a.m. This is wild, to be honest, because it's such a big gamble and it's a pretty big amount. We can see over here, it was 30k and it turned out to be a million profit. So you're telling me that this person just took a random gamble and had no clue that this news was going to come out. I mean, it seems a little fishy to me. So we had Docu over here. Let's bring it to the intro day.  It was out of the money when he bought them. So if we bring it to 10 30, so something like right over here, decided to buy the 57, like why would he buy that option out of the money on this random day? And all of a sudden, this news just comes out right over here and now turned out to be a pretty good trade for that guy. So we've been seeing this over and over again. And it seems to be getting worse and worse. And a good example of that was also C.E.R.E. So we can see from this chart, right? It started to have like this random breakout on absolutely no news right over here, right? You're looking at the stock, you're saying, what's going on? You know, what's happening? Why is this running so much? And it starts to get on everyone's filter. And all of a sudden, a couple of days later, this news comes out, you know, that they're getting an offer to be bought at $45 a share. So, you know, sometimes it happens within the day. And it's also important to acknowledge that there's always someone that's going to know about the information. And this is true when it comes to earning. This is true when it comes to news. So this is why you have to be careful that, you know, when you're trading news, is this an exit or it's really because something is happening? So in term of information and how we can take advantage of this to make money. I think a good example, like unusual, well posted over here is looking at this really weird option volume is always a good indicator of some news is coming, because when these people are taking these trade, it always happened with the option just because if it's true, the reward is going to be so much greater than if you're just buying the stock. Because if you're trying to build a position of 30 K and turn it into a million with the stock, the stock would have to make such a big move. So tracking the option going forward, probably not going to use your software, but just any kind of software like interactive book has a pretty good software when it comes to option and finding unusual option volume just tracking, you know, what's really going on in that case, because it can prepare you for some good RPG or have some special alerts. For example, what I would consider is putting an option volume or unusual option scanner. And after that, I would look for, you know, putting this stock in a special watch list with some keyword on a news filter. This is what I would do. And I think it would be the best way to do it. There's always the other way that I do not recommend and it's to try to get inside information, but I like to live life. I don't feel like going to jail. So I'll just try to be as fast as possible when the news comes out. So I hope you enjoy this quick video. If you do like and subscribe. And as usual, thanks for watching. Peace.


A common concern by the general public is the potential for hydraulic fracturing to impact drinking water supplies. Is there really significant concern to be had there? The answer is yes and no. First let me say that there is a significant chance for contamination to occur and that occurs because of surface spills. And agencies like the Department of Environmental Protection in Pennsylvania work very hard with the operators to mitigate and prevent surface spills. And the reason for surface spills being an issue is that water typically flows downhill, downward into the ground. So then the second half of the question of course is will water down two kilometers below the surface of the earth flow upward from the hydraulic fracture treatment and contaminate groundwater? It's very important to appreciate that water does not flow uphill and is very unlikely to contaminate groundwater from below. And this is the reason why the Pennsylvania Department of Environmental Protection spends so much time working with the operators to prevent those surface spills. They're the ones that can potentially contaminate groundwater, not water coming from below flowing uphill. Water doesn't do that.


Hi, welcome. This is the What's Next OpenShift Roadmap update, but this is the developer edition. I've got a whole group of my PM friends on here to cover a lot of the developer topics. With that, we'll jump right into it. Just a reminder, so there's a series of presentations that happen with OpenShift Roadmap. There's the What's New, which talks about, hey, this was new in 4.9, and then the What's Next, what's coming in the next 6-12 months. This is going to focus on that up to 12 months. This is the look ahead, things may change. There's a lot of changes, the market conditions, other things, priorities come up. What you see here may or may not happen, just standard PM disclaimer, and this is the developer edition. We're running these alongside the main OpenShift one. Let's dig into it a little bit. I just want to talk high-level the priorities within the developer tools area for 2022. One of the quick pushes, and this is cross-Red Hat strategy overall, is around managed services. Really trying to figure out how we can take everything we've done with our open-source components and really bring them together in a single managed environment that has a great experience for delivering those pieces. You'll see things that don't necessarily bring in one-to-one here as an open-source project or an offering to a managed version of it becoming and wrapping those with an experience. That focuses on Red Hat's application cloud strategy, so sitting above and promoting OpenShift, if you will. On-boarding, continue to drive on the Dev Sandbox. It's been a great way for a lot of developers to get their hands on OpenShift and various installed tools. Continue to work on ways to improve the developer, getting the hands on our tools, software platforms, and then being very productive with them earlier. As quickly as possible, we're removing a lot of friction. Also, trying to continue to, like it's always been a goal, is that platform adoption. It's not about us winning at the best we want to have with the great tools, but it's not a single tool competitive market. Our tools are there to help drive the developer productivity with our platforms in run time, so we'll continue to push on those items. Just a reminder, we have a very broad portfolio of tools that we work on. This highlights some of them. Some of them we complement with some basic tooling, all the way from code debug with code-ready workspaces, VS code plugins, IntelliJ, Eclipse extensions as well, command line tools, developer console and OpenShift, ODOS, CLI tooling, build and package through the standard OpenShift build capabilities to which we'll hear a little bit about coming next with ShipWrite, Helm and Operator enablement, all the way to enabling different technologies like serverless, service mesh across the platform, and integration to a sneak and leveraging some of the other tools that exist for providing secure software delivery across the platform. There's a lot of tools we've covered here. As I mentioned, this fly doesn't cover everything. There's projects like the JQ, service binding, developer sandbox. We'll talk about this studio code name, so a lot of things we'll cover that aren't part of this slide itself. With that, I'll turn it over to Devon now. Hello. Hi, I'm Stevan Le Meur. Devfile, for those who don't know Devfile, they describe the best practices for end-to-end application development, and they are basically a codified definition of a portable developer environment. They help our customers and the developers to move into this everything as code era with having a developer environment which are completely repeatable and reproducible. We are using Devfile as a core foundation and enabler of the developer experience of most of the tools that we are providing for inner loop, and we are continuing the expansion of the adoption of Devfiles by all the different tools. Being Open Shield Developer Console, ODO, the different IDEs that we are supporting and Devs on Box. We will be working on adding the ability to define and configure the Devfile registry at cluster level. When a tool will be connecting directly to a cluster, the Devfile registry will be configured directly into the tools. We will provide offline support for Devfile registry, and in order to facilitate the onboarding and the setup of the toolings, we will be working on solution allowing to analyze and detect the proper Devfile for a project source code. Along with that, we will add the support for Dockerfile build in the inner loop support of the Devfile. Last but not least, Devfiles is on its way to become a Cloud-native Sunbox project as well, and we have contributors and contributions coming from the team from AWS and JetBrains as well. So great validation of our approach on this. Thanks. Moit. Thank you, Steven. Hello, everyone. I'm Moit Suman. I'm the product manager for desktop ID tooling, and I'll be going through what we have next for 2022. So we have different set of products, which we have the ID extensions for, for both VS Code, Intelligent Eclipse tooling. Starting with the OpenShift extension, the idea is to provide a seamless developer experience where the users can provision the Devf Sandbox clusters or support Podman or install their hand charts directly from the ID. This is going to be an ongoing efforts throughout the year, and we are trying to make sure users can provision all the clusters quickly from the ID and start working on it. The second one is providing a support around serverless functions. So we have a KNative extension, both on the VS Code and the Intelligent ID, and there will be a release which will be coming in a few weeks for the serverless functions, and that's going to be one of the important milestones for KNative development. The other one is having a developer experience around Intelligent Qubinitis. We already have a Visual Studio Code Qubinitis extension supported by both Red Hat and Microsoft, and we are extensively working to have the same feature parity on the Intelligent side of things, so that users can do advanced cluster resource management styles, view their logs directly and see the local push of their application directly on the cluster using the Qubinitis extension. The next one is to have a support for Tecton, the same for both IDs, basically having the support for extended pipeline history, showing the log retentions and even supporting the latest Tecton Habon cluster for any custom pass catalogs. So this will be an ongoing effect with what we are having with Tecton CLI and that will be replicated on the ID itself so that as a developer their experience will be similar. The other one we are going to work for this year will be to have a remote container support where users or customers can run their VS Code extensions within a remote container inside the VS Code and that remote container can be in Qubinitis instance or an OpenShift or a Podman instance, and that will allow them to quickly provision all those scenarios within their containers. One of the important updates we have for Code ID Studio, this has been a very successful product in the past and we have based on the telemetry and user feedbacks, we have decided to do end-of-life for Code ID Studio. That's going to be on April 14th. There won't be any future releases for Code ID Studio, but the ongoing effort will be there on JBoss tools. So whatever plugins, the middleware plugins which are there on Code ID Studio will be supported with respect to JBoss tools. So from the customer point of view, the experience will be there, we don't have to worry, the only update is it's going to be end-of-life for Code ID Studio. And as Steven mentioned, the ongoing efforts for depth file support will be there on the ID so that we have the consistent approach be it on ID experience or developer console. That's it what I have for the ID tooling. So I'll pass it on to Kasturi. Thank you. You're on mute Kasturi. Hi, my name is Kasturi. I'm the product manager for Code ID Workspaces. On Code ID Workspaces, this year's going to be a really action packed for us as we embrace a lot of new things that we're going to do. In the first half or I should say the end of first half, we're coming up with a new name, but net-net the product score value proposition remains the same, but it's just more to align with the branding the developer tools is going to undergo. So our new name would be Red Hat OpenShift Dev Spaces. And we are also in the process of revamping our architectural design with a switch to Dev Workspace. This switch has already happened in our upstream chain and will happen in Code ID Workspaces probably end of first half. And these changes are essentially driven to make things more lighter, flexible and kind of also enhance further in terms of scalability and high availability. So that's something for you to look forward to and embrace it as we kind of do the switch along with the new name. And apart from that, there has been some feedback from the customers to make things simpler and easier. And to that end, we're working constantly not just with this release but we've been doing that with a couple of releases where we would simplify constantly improve the install, making it much simpler as possible. And also, improving the startup times of Dev Workspaces. That's something we kind of all the time working to make it as quick and as easy as possible. We've heard from you and I think we are also seriously working on getting production ready support for VS Code and JetPane based editors. Tecton plugin again, something that's available in the upstream. And they're looking to get that working on Codery Workspaces on popular demand pretty soon. But these are very, very at a high level on what we're going to do but there is much more for us to do. And if you want to kind of know every single line item that kind of sums up to what's on the slide, then there is a reference on the backup slide which talks about the Codery Workspaces future in terms of the roadmap. What I also like to bring to your notice is after the 2.15 release which kind of schedule some time, February and March, installation of Codery Workspaces as an iron service and OST will be deprecated as the basement customer and install Codery Workspaces from operator hub instead. We're also dropping the support for OCP version 3.1, 4.6 and 4.7. That's something I want to bring to your notice. Thank you, and that's pretty much for me, or you, Steve-Anne and Steve. Yeah, so on our container desktop tooling initiative, we are going to start a new initiative on a developer container desktop tool. And this tool is going to provide a UI for managing containers and leveraging one man. The goal is really to enable the developer to pull, test, run, debug and inspect their containers on their local dev environments, but also to provide a bridge to Kubernetes and OpenShift. The target is really to help the developers who are working with containers, but targeting to run them on a Kubernetes or OpenShift cluster. And also into this, we want to enable self-service consumption of our managed services to the developers. So it's something new. We are starting to kick off this effort on this tooling. Hope you will hear a little bit more in the next few months. Did you have anything else, Stephen? No, I'm good on this side. Okay. Thanks. So with Code Ready Containers, which fits into the space, it's done a lot of great work to bring OpenShift to a single instance onto the developer desktop and has done some recent work to enable PodMan as well. But what we're doing is we're discontinuing the Code Ready Portfolio brand. One of those changes with Code Ready Containers is moving towards OpenShift local. And so a lot of the features you saw seen coming Code Ready Containers will move into an OpenShift local or kind of blend into this developer container desktop as well. And so one of the things we'll have go through this rename. And one area that we'll see some growth, whether it will be in one area, is how we align with other distributions of which if there's this project micro shift, which is a smaller footprint that's being used for some of the pitch deployment. And we'll look at how we can leverage that probably in a kind of a community supported kind of way first as a way for a slimmer API locally as for those that need it. And with that, I'll turn it over to Serena. Hi, I'm Serena Nichols. I'm going to be talking about Odeo right now. So Odeo is our faster and straightforward CLI for developers to write, build, and deploy apps on both OpenShift and Kubernetes. But in 2022, we're going to be releasing V3, which will start at Dev Preview. The V3 release will focus on three major themes, onboarding with guiding, guided experiences, where we're going to be looking to provide more in-tool product getting started so that developers can get the context help needed to easily start with that technology area. Here you can see an example of what Odeo and it might look like. We're also going to be providing both inner loop and outer loop support where inner loop allows Devs to work with the same IDE and local workflow that they're used to while deploying apps to OpenShift with a single command or even automatically. And we'll also, as I mentioned, we'll also be including support for outer loop and V3. Our third major theme is around increased consistency between our developer tooling with Dev Console, Odeo, and OpenShift Connector. Stevan already mentioned that where the Dev files are going to provide that consistent layer between our tooling. We'll also be working on providing consistent terminology between the products, as well as guiding users to other tools in our portfolio as opportunities for awareness and learning. So for example, now that you've deployed this, go into OpenShift Dev Console Dev perspective and monitor from the topology view. So these are some of the things that you'll be seeing in the next year. And if you want to learn more about what we're doing, you can go to odio.dev. I'll pass back over to Stevan for the next area. Thank you Serena. So on our developer services, we have Service Binding Operator, which has been GA'd back at the end of October and is getting some level of adoption and usage by our customer. So we will be working on continuing, stabilizing the APIs and working upstream on the Service Binding specification with the folks from VMware. And we will also expand the number of compatible and compliant services. So this is a specification that all the services must be confirmed with the spec so that they become enabled into our tooling. We will also look at supporting services which will be provisioned to Mcharts. That is also the way we observe the developers using quite a lot and oftenly to deploy their services. So we want to enable Service Binding Operator to work with those services. And we will look at the bridge experience that we can build between a secret management solution like Archical Volt and Service Binding Operator. So how could you inject secrets that are stored into Volt directly back into your application? So that's for Service Binding. Next slide. On Helm, so as Moit already mentioned, we have an effort that is getting done on integrating Helm in the OpenShift connector plugins. We are also working on the multicluster support and we will be looking at improving our approach on the CLI and providing Helm CLI as an OC plugin. So this will allow to interact with the same Helm engine, the one that is on the cluster and avoid the discrepancies between Helm versions that can be installed on the local environment of the developers and the one that is running on the cluster. And another interesting thing that we will be looking at is the ability to export the data to the cluster. So we want to export an existing application as a Helm chart because what we observed with our customers is that most of the customers who are creating and authoring Helm charts are starting from an existing application. They do an export of their Kubernetes resources and then they clean up all the emails and templatizing them. So we want to see how we can help on that journey the developers to leverage Helm in the goal of better packaging their application for Kubernetes. Next slide. And I think this one is back to Serena on the web terminal operator. Thanks, Devon. Yeah, so around the web terminal operator currently we're still at dev preview, but just to mention that what this does is it provides a command line terminal feature inside of the OpenShift console. So this was released a couple of releases ago, but we are going to be coming GA very soon. Over the next year we're going to also investigate a number of enhancements for the web terminal, including supporting additional CLIs in the terminal, for example, FN and PML. Also being able to retain history within the terminal so that if your terminal times out and you close it and reopen it within a single session, your history would be retained. We're also looking into supporting multiple tabs within the command line terminal and last but not least, improved discoverability of the available CLIs. So this image shows an example of what this may look like. Now I'm going to pass over to Seema to cover another loop. Thanks Serena. So OpenShift pipeline, OpenShift GitOps are the center of our loop and our mission is to enable GitOps workflows across a wide area of use cases within Red Hat product. So initially the closer to mind when we talk about GitOps workflows is application delivery, infrastructure as code and configuration management, which is what a lot of our customers are start with, but our eyes really on that wider number of use cases that together with ACM, ACS, and also Ansible, we can enable across customers cases like configuration management and edge, when the number of devices are large or fleet management through GitOps workflows, policy as code and compliance as code that is extremely top of mind for customers, MLOps and so on. And this is something that we keep in mind as we go throughout the year in each quarter. Next slide, please. Specifically on OpenShift Pipelines OpenShift GitOps would be looking at is three main themes is go through what we are focusing on right now. One is to make sure that GitOps is standardized as a workflow across both pipelines and GitOps, not only for the type of workflows that customers have on top of it, but for managing and configuring these pieces of software themselves. Secure software supply chain, that's an important theme for us and in many other products that Red Hat right now and improving the operational experience of running these customers, running these products at customers when they have platform owners that want to provide them as a service. That's another aspect that will be that's a common theme that we'll be focusing on. More specifically, when we look at OpenShift Pipelines Pipeline as code or like enabling the GitOps workflow for managing CI itself, that's a huge area of focus for us moving like hoping to reach GA throughout this year and also some of the other aspects of dealing with CI like support for approval, workflows and manual approval in the middle of a pipeline, concurrency control and features as similar to that it goes into the table state capabilities of pipelines. Around security, provenance and signing in attestation is an area of focus both applied to the images produced through CI, through a tickdown pipeline and also the pipeline itself and the task runs that the pipeline consists of when it executes. And the last bit is focusing on the operational bits from the tickdown task ecosystem. One aspect is that we want to make sure that customers have a way to create a particular set of golden tasks so that they allow their developers or SRE teams within the organization to use and be able to have that exposed within the platform and have that integrated with the rest of the ecosystem that we have, the rest of tooling that we have like Dev Console and CI and so on and also some of the other aspects of managing these pipelines on especially across a wide number of teams focusing on pipeline history and logs, for example, that right now we will lean a lot on OpenShift logging this stack and we want to bridge some of the gaps that exist there between pipelines and logging this stack, make it easier for maintaining those logs or the details of pipeline that are executed in the past. On OpenShift GitOps, we just heard from Stefan around HILM so we want to bring the experience of using HILM GitOps workflow to a much better level. There are some of the aspects of working with HILM charts and Git repo that we hear from customers in any improvement. We'll be looking at those. Bootstrapping, Argos CD and GitOps workflows is something that we have had available since last year in OpenShift GitOps we want to put a lot more focus on it going forward to get customers easily get started with Git repo that contains a particular layout that they can push our applications to. Around security secret management and integration with secret managers is a huge ask. We will be focusing a lot more on that. We won't be supporting any secret manager ourselves but we want to make sure that customers easily can use Argos CD with other secret managers and HashiCorp which is the most widely used alongside the cloud provider's key managers. On the operational experience Argos CD multi-tenancy is something that a lot of our customers deal with because most OpenShift customers out there are large multi-tenant clusters and we want to bring that experience on par with OpenShift and Kubernetes multi-tenancy. Argos CD has on top of Kubernetes has its own multi-tenancy model that gives you two options. We want to make those two a lot more aligned and similar to the rest of the software that customers manage on OpenShift and also provide a lot more guidance on managing cluster configurations through the GitOps workflows. Not everything in OpenShift or not everything about any software really is GitOps compatible. So customers look to us for guidance of how to do particular things that do not sit well within a GitOps workflow and we will be providing a lot more of that kind of guidance throughout this year. Next slide please. I think over to Rob. Yeah, I'm Rob Gormley. I'm the PM for OpenShift builds and a lot of our focus here is getting builds to like projects to tech preview and then through to GA. What we're looking at there is trying to figure out the best way to kind of begin deprecating V1 towards entity year and making sure that we have as we get through tech preview all the things we need for that solid release there. Dev console support, build triggers, pensification performance, the things that kind of are required to turn this from an early project to a full featured setup that just facilitates cube native builds and projects we're talking about things like sourced image, build packs, build etc. Providing a path for migration from builds V1 to builds V2 be that automated or guides and support for our users there. We're also looking at continuing our development and iteration on the various CI plugins. One of the things that we're looking at there is deprecating support for built-in Jenkins. We found that that's very high maintenance and takes up a lot of developer cycles and moving that to a more native C pass integration is going to be the way forward for there. Also looking at focusing particularly on GitHub actions the biggest client for CI plugins but making sure that as we build out that and shut out further we're also maintaining the ability to continue to support other CI providers Azure, DevOps, Jenkins and so forth. As you keep going through there let's see, enhancing pipelines, CMAC alluded to a bunch of stuff there in terms of making sure that we have the tools necessary to again make sure everything is product ready image signing log retention bundles and DevSecOps integrations there. Alright, back to talk about the OpenShift console and the developer experience inside of that. So in 2022 our main themes around the developer experience in the console focus around onboarding platform adoption as well as addressing request for enhancements. We're focusing on a number of new features as well as improved experiences in many areas. Let me tell you about some of the things we're working on. In our import from Git flow or bring your own code flow you'll see that we're now defaulting to secure routes. If that doesn't suit your needs don't worry just hop over to use the preferences where you can change the default settings to be used in both import and import from Git and deploy image. Now note that that's going to be released in early 2022. Things that we're also looking at is when deploying Node.js apps we are looking into enabling devs to enter optional parameters for the NCM line commands. Regarding helm charts we're going to be looking into providing a quick start in the home catalog to show the users how they create a home chart repository which is namespace scope via YAML which will pull in additional helm charts into that project. Following that will provide a form-based experience to accomplish that same user flow. We're also looking into how we can enhance our service binding close which are unlocked by the service binding operator. Things like providing form-based service binding creation for increased discovery as well as the ability for users to name their service bindings. Also looking into enhancing that operator back service catalog to provide discoverability of which services are compliant with service binding. Now let's dive into application availability. Once you've built your application in the dev console and tweak things to work exactly as you'd like we're working on a number of features which will allow you to move your application from your current project to another project or even to another cluster or even check it into your Git repo. As some of you know we already do have the ability to export your application to YAML from the topology view. This feature is currently available with the GitOps primer installed and you could even try it on the dev sandbox today. But other mechanisms that we're investigating are exporting your application to a home chart as Sivan mentioned exporting your app and checking it into your Git repo which would allow that next step to have it managed by GitOps. And we also have our migration team looking into a way to import an application from another cluster into the cluster you're currently logged into. Now moving on to the theme of usability and desirability let me share some of the items that we're investigating including feature requests that we've heard from our users. Since many of the developers don't want to touch YAML we're continuing to provide or looking into provide additional form-based flows for both creation and editing. We're also moving if we're thinking about the navigation and the developer perspective we already provide the way for a user to add custom nav items there. But the feedback that we've heard is that users want to reorder those custom nav items so we're looking into that. And regarding our topology view we're always looking at ways to make that more efficient and usable but we're also spending some time to address some scalability and performance concerns. These won't only be addressed by code changes but also by some changes in the experience. So as you zoom in or zoom out you may see automatically see more or less detail. Last but not least regarding the desirability we're working on we're working hard on providing a dark theme across all of OpenShift console. Now finally let's do a deep dive into portfolio enablement. As you know developer console allows a number of features by itself but as we install additional operators we're really unlocking additional features. So with the serverless operator, with OpenShift serverless operator we're looking into pulling in support for event syncs. We'll start with visualizing them in topology and then providing an event sync catalog for easy creation. We're also going to look into the ability to have Kubernetes services as syncable resources when working with channels and brokers and we are also providing a event sync catalog as well as Kafka Sync support. When looking at OpenShift pipelines Asseomic discussed many of these items previously some of the workflows that he discussed we'll be looking at supporting in the console in the future. So we already do have some level of integration with Tecton Hub with a pipeline builder but we're looking into supporting local Tecton Hub instances and being able to do that from inside the console. Also enhancing that pipeline's code experience and allowing for bootstrapping from the console as well as adding a git repo. Around BuildZ2 which are enabled by also called ShipWrite that Rob discussed we are talking about pulling those into the UI just to show that those resources available and then following that up with having BuildZ2 be that default build in our import from Gitflow. And finally we're working with the cryostat team as they're looking to provide a dynamic plugin which will allow developers a seamless experience from within the dev console to produce, analyze and retrieve JDK flight recorded data from their Java Java cloud workloads to help with some co-piling. And with that I think I'm going to pass back over to Brog. Thank you Sprina. Many of you are familiar with the developer Sandbox where it had OpenShift. Let's talk about the recap for last year it was launched in 2021. So overall we have launched some new things in Q1. We did a data science fans were probably seeing the Rhodes Sandbox so it enables to create data science models without having to provision OpenShift on your own. It comes bundled with the entire stack of data science. We enabled customer communications with some public Slack channels so that people can just talk to us directly onboard a bunch of new operators, serverless web terminal. We ran a hackathon for our managed Kafka service and the developer Sandbox in OpenShift experience and it was very well received in APAC with about 230 participants across nine countries. So continuously delivering new things so that we can have more folks come in onto the Sandbox to try out our portfolio try out the experience and also use it to demo it or set up projects for customers if we are reseller. Next slide please. When we look at the trials from an OpenShift perspective developer Sandbox is the highest system that is used to try out OpenShift and the good news is it also leads to the follow up journey which is after the Sandbox we will try out either managed OpenShift or OpenShift itself managed on public or private cloud and then that leads to sales opportunities and closure of maybe even existing opportunities. So we can see the developer Sandbox is influencing new trials of our platform and also influencing single year bookings for Red Hat. Next slide please. So what's coming in the next few months is we're going to be adding more and more into the developer Sandbox. We're onboarding the OpenShift Pipelines operator we're onboarding the database of the SAS operator especially with the launch of the Rota service coming up pretty soon. We'll be merging the Rota Sandbox now that we've added out into one Uber Sandbox which is going to be the current Sandbox that we have but now it's going to have a lot more in it so now we can imagine the customers can not only create data science models they can also create applications that consume those models and even run the pipelines to run a few builds and sample tasks that they want to automate the end to end part of what it takes to deliver a data science model into an application. So very exciting. It's going to be a much broader reach across our Red Hat customer base. Continuing on the free-to-feed journey as Serena mentioned about the ability to export an application and then import it into a cluster we're going to be onboarding those capabilities into the Sandbox and then tying it back into our console RedHat.com so that you could actually come into the Sandbox, create an application, export it, create a new cluster let's say it's a Rota cluster on AWS and then kind of import the application directly into there so providing a free-to-feed journey there. To increase customer acquisitions we are going to be working on a few things on the product side more on the marketing side. One of the things that we are targeting on the product side is having an activation code-based application. So that you could have a special event where you run, you can have a code that you can share with everybody, you could say code can support up to 250 new sign-ups keep it valid for the next 24 hours and in that way we can now find who came in for a particular event make sure they all come into the same developer Sandbox environment in terms of the cluster and then you can run promotions and the subscribers can avoid having to do phone verifications and things like that. They can just come in directly and share the activation code. So we are kind of working on that capability. Next slide please. So App Studio, I don't know how many of you have heard of it. It's a code name so please don't go by the title but it is targeting a managed developer experience that is going to be focused on delivering a lot more of our app cloud strategy but this is the first step into it so I would like to share some details about it. We are working through the flows that as a developer when you are creating a new application there is a flow that takes to go from an application to a scaled out deployment of the application across a multi-cloud platform starts from wanting to create an application all the way to packaging, connecting into services and can affordably continuously delivering it onto the cloud platform that is suitable for that application. Next slide please. And for that as we all know there's quite a few steps that developers have to go through and some of these steps are very often and some of the steps are highly complex and may not have to be done as often but it starts by how can I create a secure container from the source code that I have all the way down to how do I deploy it to all the cloud platforms, how can I access the data that I need to fix issues when it comes up, when the application is running across the different cloud platforms and so there's a lot of steps that need to happen and for developers there's a lot of technology complexity and a lot of know-how that has to be kind of learned and built in before they can go from 0 to 60 miles an hour so currently the 0 to 60 honestly just takes a long time, it is not the 5.9 seconds that you're used to in the public cloud world. Next slide please. So what we are announcing App Studio at Red Hat Summit is it hosted fully managed experience to solve some of these problems. Basically enable developers to build full stack applications including Java, easily connect to all the leading cloud services and tools that they are used to, especially in the cloud world, adopt certain DevSecOps practices without really becoming an expert in DevSecOps and deploy to any cloud platform of choice. That's the mission that App Studio is working towards and to make it easy what we do is things like let's make it zero friction of packaging the software, we have secure run time so let's not let the developers kind of fumble around figuring out how do I create a container that is going to be secure, provide seamless integrations kind of hide the abstract out the technology and make it easy for them to do the work that they need to do without having to become an expert in the underlying pipeline products, GitOps products the platform of OpenShift itself we are just basically creating a developer experience which is managed by us and then in the end give them a single pane of glass for all your applications across the software the development life cycle and multi-cloud environments and that is something which is very unique in the industry, like everybody has specific ones nobody has that kind of a layer where you could do all of this from one place and just run applications across a cloud platform that suits you next slide please so in the beginning we are going to target certain kind of applications which are suitable for App Studio full blown front and back distributed microservices, applications that span across cloud platforms and geos, applications that are basically going to be scaled up with demand that comes in next slide please at the high level when you look at the market texture what this means is customers can bring in the services and the tools that they are used to that they want and they could be tools and services given to them by Red Hat, by the cloud vendors themselves by other even ISVs like GitLab and HashiCorp and GitHub and then you bring in the experience that is on console.redhat.com and you can have a layer in the middle that this makes it very easy to tie these applications that you are creating with these services and the tools that you want to consume have a iterative environment so you don't have to worry about creating a Kubernetes or an OpenShift environment just to try out your application it comes bundled with it, you just come in you start running your application you can then commit to basically buying OpenShift environments when you are ready and so it's not like you had to go buy one on day one just so you can iterate over the application it will give you that, it may take you months it may take you days, it's up to the customer and then once you are ready to deploy your applications you can basically pick and choose the cloud platforms, you can pick and choose the OpenShift environment that you want on top of it and then we are working towards a hybrid app cloud, the compute part of it where we abstract out all these things and we basically are just the customer can literally pick and choose certain placement rules and requirements and we just go deploy irrespective of the underlying cluster Next slide please So to get there, ambitious project and we are going to be doing it in a very measured way, iterative way, it's managed it's hosted, so the good news is we don't have to follow product release cycles, we want it to make it really fast and iterative take customer feedback, bring it in deliver the next capability at the end of every sprint, so we are going to start by launching a private preview around summit timelines and we want to provide certain capabilities in that, the key one being you should be able to create an app, iterate over it in the bundle sandbox, create a Rosa cluster and just deploy it to Rosa, so now you have a multi cluster, multi cloud environment experience right on day one of private preview and then we go past it right now we start bringing in some of the key managed services we want to connect in with enabling some team level capabilities because you know that you are not going to be working on this alone so we will start expanding it introducing some paid tiers for cost recovery and also for SLAs and just kind of give a very highly qualitative experience to the developers and for Red Hat to find to kind of interact with these developers who are coming in from organizations and you know who want to really go into the cloud and are looking at how can we go cloud first but in a agnostic and a fast way and as minimal effort as possible so as you can tell there is a pretty good roadmap ahead of it a lot of it is going to be reacting to what customers want us to do and yeah it's pretty exciting time with that turn it over to Steve. Thanks Brog yeah we come to the end here some additional resources we've done the 4.9 what's new developer edition so we're looking at doing a 4.10 one coming up we're going to look out for that we'll update some links here as we have them but if you do want to reach out there's the depthful PM mailing list which covers everyone on this call and yeah thanks to Kasturi Moet Parag, Rob, Serena, Savan and Siamic for pulling this together and if you do want the gory details of all the different things that are happening you can look in the back of the slides and we have the detailed roadmap for all the different areas we covered that cover basically the quarters or more or less the rest of this year as I mentioned continues to be a growing focus things may change, things expand a lot of great stuff here so please reach out if you have any questions if you have any feedback we'd love to hear it and thanks for listening and watching


So, today of course I am not going to do anything new, I think I have more or less finished except for a review and just telling qualitatively what are the other theories that are possible. We have mainly described the many electron problems, so in particular Hartree-Fock which is of course the best uncorrelated theory. So this is the reference point from where all the electron correlations start, so then we discuss the electron correlation as the important topic and in particular we developed perturbation, the algebraic as well as diagrammatic of course CI, the configuration interaction as the two major methods of electron correlation. Of course there are several things to do, so our interest has been mostly on the energies, but I must tell you that as you go forward we also need to learn how to get not only energies but also energy derivatives and this is something that we have not covered in this course. How do you get energy derivatives with respect to some external field or perturbation? This is a very important topic and this is often called the response, this is something we have not covered that means how does the energy change if I give an additional field like electric field, magnetic field, this is very important because electric field change gives you dipole moment, if you have second order change it is called polarizability and so on. So these are also very important to calculate analytically, so I must mention the numerical calculation is very easy because you just put an external electric field, your one particle potential changes, you keep doing whatever you want to do and take a numerical derivative. What is of importance is of course analytical derivative, analytic derivative and this is something that is a very important part of quantum chemistry, not only external field equally important or even more important are the nuclear coordinates and this is a very part that we discussed and if I change the nuclear coordinates then of course my Hamiltonian will change because the external potential changes, how does the energy change and these are basically known as, these derivatives will be known as the gradients and the Haitian. Many of these are used for geometry optimization, why I am saying because in quantum chemistry a very important part is to optimize the geometry of a molecule. So what do you mean by optimization of geometry, if you calculate the potential energy surface like a diatomic molecule we have to find out where it is minimum, the simple hydrogen molecule if I do it correctly, so this is the point which is 1.4 atomic unit or whatever for H2 molecule it is a minimum. So for a complex polyatomic molecule we have to find out where the equilibrium geometry is, so what we need to do is to calculate this energy which I call potential energy, I hope all of you remember what is the difference between V and E electronic, what we have done the calculation is E electronic because in the Hamiltonian we have not added the nuclear nuclear repulsion term, so if you add the nuclear nuclear repulsion term which is a constant so it will not change anything you get the potential energy. So for gradient it is very important because this part is also a function of nuclear coordinates. So when I do the gradient I have to calculate del V del R, all R let us say there are n number of R's for nuclear coordinates which are basically degrees of freedom, vibrational degrees of freedom like 3n minus 5, 3n minus 6, then you know that for a minimum each of them has to be 0, so this is a very important equation, so what we mean by analytic derivatives is to calculate these analytically and then set an equation that this is equal to 0 okay and then we have to see whether it is maximum or minimum by looking at the second derivatives and checking the second derivative matrix which is basically called Hessian, so this is gradient and this is Hessian, second derivative matrix I take with respect to one R and another R, so R i, R j this is a matrix as you can see as a function of ij, this is called Hessian matrix and the trick is that if you diagonalize this matrix you get the eigenvalues, if those eigenvalues are all positive then it is called minimum. These eigenvalues are essentially the frequencies, you know many of you might have heard IR frequencies, this is another way to calculate, this is infrared because I am changing potential energy with respect to coordinates, I calculate those frequencies if they are all positive then if they are all positive then it is called the equilibrium geometry and of course there may be negative frequencies, one of them is negative, two of them negative, you will get different states which are actually called transition states, you know many of you will be using the transition states, so we are not done in great details but I thought today I will just tell what are the other things that we have to actually do apart from calculation of energies, so what we have focused in this entire exercise is to calculate the energies okay but the gradient and Hessians are very important part along with other external field response and this in general is called response approach, so this is a very important part how do you calculate this apart from the energy calculator, whichever method you pick up, in the same method you have to do consistently this, we have of course discussed within the energy important problem of size consistency in great details when is a theory size consistent, when is theory not size consistent and in particular we discussed the Hartree-Fock that Hartree-Fock itself may not be size consistent, when a even restricted Hartree-Fock or Hartree-Fock when a closed shell molecule fragments into open plus open it is not size consistent, however if they goes into close plus close it is size consistent but then even if it is size consistent if I do approximate CI the size consistency can go down, so in particular we have taken a system of H4 into H2 plus H2, so with an example we showed that H4 can go to H2 plus H2 correctly in the case of the restricted Hartree-Fock but here this correction breaks down if I do an approximate CI and in particular we discussed DCI, I hope you remember this particular model problem, this model problem was essentially a Hartree-Fock 1, 1 bar note that whenever 1 bar will be used, please remember it is a spin orbital with 1 as the special orbital, beta as the spin orbital, spin, so that is something that you should have no confusion, so this is just called chi 1, chi 2 in our nomenclature where chi 1 is 1 alpha, chi 2 is 1 beta, so that is a spin orbital, so please be careful even whenever we ask be careful of the symbols so if I am saying chi 1, chi 2 then of course this will be chi 1, chi 2, if I am writing in terms of special orbitals this can be written 1, 1 bar and then 2, 2 bar becomes chi 3, chi 4, so a very simple minimal basis problem where this is special orbital 2, this is special orbital 1, we have done in great detail and in particular we discussed the DCI wave function which is 1, 1 bar plus C 2, 2 bar, remember this is a DCI wave function and this is actually full CI for this problem if we restrict ourselves to a symmetry adopted state, so let me just quickly tell you why as you know that this symmetry is sigma G, all of you know for hydrogen molecule when I do this it is a sigma G, one S A and one S B symmetry combination and this is called the sigma U which is anti-symmetric combination, so if I do a one electron excitation from G to U which can be a part of the CI, S D CI, full CI, the one electron excitation will lead to a symmetry which will be G into U, one of the electrons will be in sigma G, one will be in sigma U, so that will become a small U symmetry, remember that this is sigma G square, so sigma G square has a group theoretic symmetry which is singlet sigma G, capital sigma G, I hope all of you are more or less familiar that the capital sigma is for the molecular term symbol, small sigma is for the orbitals, so this you have done in MSA itself, so if I restrict only this wave function to singlet sigma G then you can imagine I cannot have any function which is singly excited because it will involve one G and one U, this will then become U state, I am interested only in G state, further of course I am interested in capital sigma state which will be always generated if I have two sigma so no issue, further I am interested only in a singlet state, so the only state that is possible is 2 2 bar which is doubly excited because if I have put both the electrons in sigma U then sigma U square also is a singlet sigma G state with higher energy normally, if you have look at these two determinants they are higher energy but your actual ground state energy is a combination of these, so this will have a larger dominance, this will have a lower dominance for this kind of states okay but of course as I discussed for the hydrogen molecule if you stretch this apart then both these orbitals come very close and then of course that is the reason RHF breaks down because they become nearly degenerate, so if I go around this part when R tends to infinity for hydrogen molecule these two almost come together and both sigma G square and sigma U square become almost equally important, so that is a failure of the RHF and eventually all the theories have to be geared to take this, so we have discussed the DCI problem, we also have discussed how to solve the DCI equations iteratively, so solution of particularly DCI equations iteratively, of course DCI or any CI can be solved as an eigenvalue equation, so let us not forget but we iteratively essentially mean that we do not want to solve the entire eigenvalue problem, we want to look at only the ground state or the lowest root in an iterative manner and very often we have started with the a correlation expression in terms of e correlation and set e correlation equal to 0 as the first guess and then you continue, so this also we have discussed very elaborately, so I just wanted to mention this, I should now mention few of the other theories for energy calculation which I mentioned, so perturbation I have already told you that we have discussed yesterday also in great detail diagrammatic and connection in the algebraic except that we have not proved, we have not proved the link cluster theorem, we have simply used the link cluster expansion of Goldstone and yesterday we gave you a model problem, I hope you remember practice problem of MP4, so please try to do, I have given a fourth order diagram, so do not say that the fourth order is outside the syllabus, I have given the diagram yesterday, if I give a diagram you should be able to write the algebra with all the Hugen-Hulls rule, there only Hugen-Hulls diagrams is what we have done, so you should be able to write the algebra with this sign and everything correctly, all right, so apart from perturbation and CI we said that we are going to cover at least mention the names of a few more methods, so one of the important methods is what is called the MCSCF, I think the name itself is clear, it is multi-configuration self-consistent field theory, so this is known as the multi-configuration self-consistent field theory, so let me just explain what it is, so this is the full form of this, self-consistent field already you know that is a Hartree-Fock where for a single determinant you try to get the best spin orbitals, okay, you also know what is multi-configuration theories in CI, CI is a multi-configuration, expansion, so this is as the name suggests is a mixture of CI and Hartree-Fock, the spirit, Hartree-Fock is optimizing the orbitals, right, that is self-consistent field, CI is optimizing the coefficients of an expansion, if I have a linear expansion how do I optimize the coefficient, so in MCSCF you do both, so you have a web function which is a combination of determinant, first linear combination of determinants and these determinants have to be chosen carefully, then you optimize the energy with respect to both the linear expansion coefficient and the orbitals involved in the determinants, not just one determinant, there are many determinants, all the orbitals involved in the determinant, you can clearly see that this goes much beyond CI, this of course is beyond Hartree-Fock because I have a multi-configuration function and it can be a very, very accurate method because depending on number of determinants there are many orbitals, all the orbitals I am optimizing, just like in Hartree-Fock you remember I wrote energy as a, optimized with respect to orbitals, right, orbitals essentially could mean LCAO coefficients, orbital expanded in a basis, so then coefficients are optimized but essentially orbitals and in CI it was a reverse problem, orbitals are fixed, if you remember the standard CI that we did, we always went with a basis of orbitals which was Hartree-Fock orbitals, with those Hartree-Fock orbitals we constructed Hartree-Fock determinant singly excited, doubly excited and we only changed the coefficients, so the equation was only to get the coefficient which is an eigenvalue equation, we have again done this, you construct the H effective matrix for the E correlation where the first term is 0 and then all matrix elements of H minus E Hartree-Fock, you with respect to all the determinants but determinants are fixed because orbitals are fixed in CI, only the coefficients you change, in this case we are doing both, so for example, so obviously in such a case we have a restriction that we cannot take such a large CI because there are too many determinants, if I have to do this it's really a no go from the beginning because it's too complex a problem, so what we do is to actually take problems where it is required, so one of the problems is precisely what I have discussed just now, that I have a situation where hydrogen molecule, I mean hydrogen is just an example stretched, so if I stretch it the configuration sigma g square and sigma u square will be nearly same in energy, they may not be degenerate, they may be degenerate only at the separation point but if I stretch they will come closer and closer, so basically this is the equilibrium sigma g and sigma u, as you go forward this will go down, this will go up and something like this, so this kind of system is not degenerate but they have a name in quantum chemistry which is called quasi degenerate, the quasi essentially means that it is nearly degenerate, not exactly degenerate, now in all systems and including degenerate systems I need to construct the wave function not as I discussed the Hartree-Fock does fails but I must need to construct the wave function phi 0 as some C0 sigma g square plus C1 sigma u square, in a small model this is exactly full CI, 1, 1 bar, 2, 2 bar except the C0 is 1, I mean normally we have said C0 is 1 for intermediate normalization but that's unimportant, so if I have only 1, 1 bar and a minimal basis this will be then 2, 2 bar it's of course full CI but if there are many other basis it is a part of the double CI and there may be many other double CI coefficients but knowing the physics here that only these two configurations are important that is two electrons here and two electrons here I can do a much better job than just doing a CI, note again in a minimal basis this is exact, I can repeat for hydrogen molecule but if there are many other orbitals, so there are many other orbitals then it is not exact, so to do exactly even DCI I need to take many, many configurations, correct, I may have to take even singles for full CI because there may be another orbital with g symmetry where I should be able to excite because g into g remains g, right, here it was only g and u minimal basis so I can't do so in principle the problem may be very large even for hydrogen molecule if there are many number of orbitals but I know that only these two configurations are important the rest are not important, in such a case I should be able to write only as a combination of these two determinants and then not only vary these coefficients just like in CI but also vary these orbitals themselves 1 and 2, so I would vary C0 and C1 as well as 1 and 2 remember the sigma g and sigma u normally when I do CI I have taken from a Hartree-Fock calculation and fix it but now what we are suggesting is that anyway this is an approximate calculation let's not just take Hartree-Fock 1 and 2 let's also try to re-optimize 1 and 2, so this the reason it will change is that now that we are optimizing the orbital 1 it is being optimized not just for sigma g square that was the Hartree-Fock but in the presence of another determinant so there will be a coupling term and because of that the orbital 1 will change similarly orbital 2 will change the coefficients will change of course when I vary so it's a very complex problem and this is exactly what is MC SCF multi configurations SCF multi is here 2 that 2 can be 3, 4, 5 but in general you don't do a multi configuration SCF with 1000 configurations because then there are so many orbitals the orbital optimization itself is a non-linear optimization as you know because orbitals are the exponential something quadratic even Gaussian or whatever exponential term so they are extremely difficult to optimize Hartree-Fock we could do because there is only single determinant so obviously if there are 1000 determinants you can't optimize the coefficient and orbital they are very very expensive so MC SCF has to be used judicially those will do MC SCF remember should be done for a particular problem where a few configurations are important so don't do a real CI because CI you are taking everything even in CI of course you do selection I told you by looking at the energy denominator you can select determinants amplitudes but at least here I know that a few configurations are important in such a case you can actually do MC SCF it gives a very very accurate results many times this configurations are chosen by looking at active orbitals and I will tell you what is an active orbital so let's take a problem of more than 2 electrons so where it will be relevant so let us say that these are my occupied orbitals and this is the line these are my virtual orbit this is this is not an orbital they just a line separating the occupied and virtual orbitals so this is my lumo this is the homo and of course I have many other orbitals here so I have let's say 10 electron system okay so up down up down whatever now and then there are lumos so I have to I can generate many configurations by exciting electrons from here to here okay question is I want to do an MC SCF because this gap between homo and lumo has become very very small so it is exactly the similar problem that the gap between homo and lumo has become small so there may be other configurations which are important so you may decide then to choose what are called active orbitals which have to be mixed so if you ask me what are the active orbitals in this problem the active orbitals which were mixed with sigma g and sigma u in this case there are two active orbitals so let us say that I choose similarly one active orbital from here one active orbital from here and then I construct all possible determinants where the electrons active electrons are put within these orbitals within these two special orbital so let's say I choose active orbitals as homo and lumo so two orbitals how many spin orbitals four spin orbitals correct I don't want to change this so all my configurations will have this frozen this eight electron so these are not my active so active electrons are also only two now without looking at the symmetry how many determinants I can form between these active orbitals so that means I will I am free to excite one of the electrons here two electrons here whatever but everything that I do is just between these two special orbitals and involving these two electrons these eight electrons are fixed so how many how many determinants I can make as everybody agree you have four spin orbitals two electrons so you have four c2 without looking at the symmetry right now because you don't know the symmetry of the orbitals they may have the same symmetry so you should be able to excite okay so in general I have six electrons so if I six determinants if I make a wave function which is now a linear combination of these six determinants okay how did I how did I choose these six determinants by first choosing the active orbital remember if I if I say this lumo plus one is also very close to lumo then I can expand my active orbitals as homo lumo lumo plus one so active orbitals are essentially orbitals which are near degenerate or quasi degenerate so look at the degeneracy of within the homo within the lumo and between homo and lumo and choose the active orbitals okay of course if it is only within the homo there is there is nothing to choose because that is already filled so it has to involve lumo of course the unoccupied orbital not only lumo lumo plus one so if I have one more orbital this would become six this this and this and then my number of the six active so it will become six C2 I can also say that homo minus one is also very close then what will happen I will have this this this and maybe one more this is all these four are very very close in energy then what I have to do I have to choose these four orbitals which means eight spin orbitals and I have to choose four electrons as active because this will be also lifted these six will then be frozen so you have to decide the problem looking at the orbital energies how many active orbitals you have to choose but having chosen an active orbital if you make a wave function which is a linear combination of all determinants all determinant that can be constructed out of the active orbitals all then it is complete okay then such a method is called CAS SCF if I make the determinants and then do exactly like MC SCF which means I change the coefficients of this determinant six determinants as well as their orbitals so in this case the orbitals are let's say homo and lumo two active orbitals in this particular example then you change this and these orbitals okay and their coefficients of the six determinant in general and of course this is g and u then you have only one determinant okay g square and a two determinant g square and u square just like this example so in this example it is a CAS SCF actually because I have chosen only sigma u I have two electrons in terms of symmetry this is the only possibility okay so in a way this is a CAS SCF so CAS SCF is like MC SCF but the MC the MC's part is chosen like this that you first look at the active orbitals distribute the active electrons in all the active orbitals possible within the symmetric considerations and then do an MC SCF so that becomes CAS SCF it is called complete active space and then you know self consistent field field so basically just the MC space becomes a CAS complete active space after you do CAS SCF there are many people who do within this multi-reference multi-configuration function another perturbation theory that is very very powerful and that is usually called CAS PT perturbation theory so on so do a perturbation on CAS so these are all methods that are available in fact many of you will see this so you have a CAS and then do a perturbation theory so you get CAS PT so you can have CAS PT 2 PT 3 etc depending on which order you do usually CAS PT 2 itself is extremely time demanding and people do CAS PT 2 and you can see that first of all I have chosen the important determinants I am doing a CAS SCF which means not just CI changing the orbitals and then top of it I am doing second order perturbation where other orbitals will come because right now other orbitals are left out I have taken only homo lumo all these orbitals are left out in CAS okay so when I do CAS SCF remember the dynamic correlation from all these orbitals are left out only these two correlations are taken care and this is usually called the non-dynamic correlation where very few configurations are important and I do not want to introduce these terms late in the course but I just thought I will tell you so MC SCF or CAS SCF does the non-dynamic or static correlation very well but you need these dynamic correlations all the other basis then you have to do a perturbation theory on that and that is where CAS PT 2 gives very good results in fact if you do second order perturbation that is good enough but in many case the dynamic correlation is not important only static correlation is important then you do CAS SCF or MC SCF so these two kinds of correlations are very important static and dynamic so usually static comes from a few configurations few important configurations so in that case you can do just a CAS SCF dynamic comes from a large number of configurations each of which is not very important but their sum is so sum is important or some cannot be neglected so I have to sum them also so this is what we have done so far so today what I am discussing right now MC SCF is really to take the static correlation how do you take small number of correlation and there you have a choice not to optimize the orbitals or to optimize the orbitals but MC SCF does both okay orbitals as well as then coefficients so it is very good for static correlation so MC SCF or CAS SCF MC or CAS whatever SCF is very good for static correlation this you have to do dynamic correlation the perturbation theory or normal CI CI involving all other determinants basically I have to involve the rest of the orbitals not just those few configurations for dynamic correlation so this is something that is today understood that the correlation also has two different parts and different theories can handle each of these very well so I think this is something that I thought I would tell you among the other important theories and there used to be also a theory which is almost now dead today but it is a very important theory which is called the electron pair theory which actually started from Synanoglu's work and then was eventually taken up by Wilfred Meyer as electron pair approximation and there were several approximation independent electron pair approximation and different versions of coupled electron pair approximations from SEPA 0 to SEPA 7 you know there are so many small small modifications this is called independent electron pair approximation coupled electron pair approximation so take electron pairs how do you couple them the way you couple but today the electron pair theory is almost extinct you know most people don't do it


Now I'm in the situation where they come back and they say, Hey, I have a problem. I want you to reverse this transaction. Well, you've already paid us. So what can we do at this point? We could issue a check or an expense form, but we'd rather do something in the customer field. So if we're going to actually issue them a refund at that point, we might use the refund receipt, which we talked about before.


MSA Transformer is a powerful tool for generating new proteins with desired properties. It can be used to create sequences with similar or better properties than those found in natural data sets, even for small protein families. This makes it a promising candidate for protein sequence generation and protein design. This article was authored by Domino Scarbosa, Ambuto Lupo and Anne Florence Bitball.