So, are folks now seeing the first slide? Fantastic, okay. Great. Well, thank you all for coming this afternoon. I know it's been a really long and interesting day and we're so pleased that you're here with us. A little bit of a caveat. We had actually only applied to be in the 20-minute category presentation. And so, while we have attempted to flush out our work a little bit, we may not be going the full 40 minutes, but I suspect that's not gonna be too sad for anyone. So, again, my name is Liz Bedford. Lily and I work for the University of Washington Libraries and we were invited by some faculty at the UW School of Dentistry to create this course that was designed to help some graduates, PhDs, in the fields of dentistry and orthodontia, take their dissertation work and turn it into articles, basically. So, I wanted to start off by sharing the University of Washington land acknowledgments. I'd also like to acknowledge that I'm a White Souther currently living in the traditional territory of the Duwamish tribe. These are the original and ongoing stewards of Seattle and King County. And while they were among the signatories of the 1885 Treaty of Point Elliott, they currently do not have federal recognition. They've been petitioning for this recognition for over 40 years and briefly won it in January 2001, but that ruling was voided in 2002 by the Bush administration because of procedural errors. So, if you're interested in learning more about this, I'd really encourage you to visit the tribes website, which also has a link to a change.org position calling for federal recognition. And I'm going to share that link in the chat. So today, Lonely and I are gonna be talking about the course that we participated in and then also be talking about some of the things that we're thinking about to translate it into the UW context. So, we're gonna both be giving you a little bit of context for the project. Lonely is gonna dig into how the class worked itself. It was called Let's Publish Your Thesis and give you an update on where the students are now. I'm then gonna be talking about the ETD process and student concerns at the UW and talking about sort of the lessons that we learned through this process and how we're hoping to apply it to supporting UW students in the future. So, as I said, this was a class that we were invited to participate with some folks from the Durham School of the Durham Center for Global Moral Health. I also wanted to give a little bit of context for the scholarly publishing landscape because we thought that it was important to also begin by addressing what can sometimes feel like a bit of a paradox in this work. So, our course was aimed at supporting these practitioners in publishing their work because there's really a glaring void in the academic literature, which Linda's going to talk about. However, we also know that the current for-profit scholarly publishing system is both really exclusionary to under-research researchers and often shows a marked reference for research focusing on the best writing topics and populations. We now know that article processing charges or APCs, which are the primary way that for-profit publishers pay for open access can actually cost up to half a year's pay for African researchers. And we also are really aware that the modern tenure system puts way too much emphasis on publications as primary measure of academic worth, far over teaching and service, which are incredibly important contributions, and can lead to really damaging practices like the over reliance on impact factor as a measure of academic work. So, while we were incredibly pleased to take part in this project and help these practitioners take their dissertations and modify them for publication, we really can't forget that there are some systemic issues that also need to be addressed in this area. And I'm going to hand it over to Linda. Oh, thank you, Liz. So, I'm going to give you some context, the dentistry landscape in Kenya. Can you hear me okay? Yeah, okay. As Liz mentioned, University of Washington School of Public Health has had a presence in Kenya for over 30 years, and they've been working with the Daruin Center for Global Oral Health since 2015. There's very little research on oral health, dentistry, orthodontia on people in Kenya, and particularly orthodontic research and the tooth measurements are done with primarily white populations. If you were to go on PubMed or ProQuest Thesis and look for works on oral health, oral dentistry in Africa, you'll see most of the work is done by Westerners. This is a big gap because in 2015, a National Oral Health Survey report in Kenya reported that 34% of adults had untreated dental caries and 98% had gum disease. Oral health impacts so many other parts of our lives. In it, finally, there is a shortage of dentists in Kenya. There's about 680 for a population of 50 million. So this work, having local authors give local context is so important. Next slide, please. So, we were awarded a Global Innovation Fund grant to pilot a project of 10 recent PhDs and help them turn their dissertations into publishable manuscripts. The purpose of the grant was to provide writing skills, knowledge about the publishing ecosystem and how to publish, as well as financial support to allow them to publish in a gold open access journal. The grant included only $10,000 to pay for APCs, and we anticipate that maybe three or four students will get that financial assistance. Next slide, please. So who was involved? Well, here's a class photo from one of our days. We had two faculty members, Dr. Analucia Seminario from UW, Dr. Kamoli from University of Nairobi. There was an orthodontic professor who came in to help the orthodontic students with their dissertations who had a special expertise. We had three University of Washington librarians, Liz and myself and our data visualization librarian, and a grad student who taught Zotero. Who were the students? Dr. Kamoli put an advertising flyer up at the two universities that have dental schools and these 10 students were picked. They had finished their PhDs anywhere from three to seven years ago. Nine are living in Kenya, one in Uganda. Eight of them did their PhDs in Kenya, one in China and one in the Philippines. And they are all currently teaching and seeing patients at University of Nairobi or Muay University in Mombasa. Next slide, please. There was a pre-class assessment and you can see that there was a lot of concern about limited writing skills and not knowing how to submit to a journal. So all centered around the writing process. They had done tons of research, had lots of data, but weren't sure how to move on. Next slide, please. They wanted support in formatting a submission and editing, both critical editing and help with their English. In a follow-up question, 90% said all of these kinds of support wouldn't enable them to increase their submissions to high impact factor journals. Next slide, please. So our class ran for 10 weeks from March to June. We got the grant in February and we worked iteratively with faculty to design the class. What classes should be taught in what order? Next slide, please. These are the classes that we taught. You can see we did started with literature reviews. A lot of the theses were based on data and they were older, so they needed to update their literature reviews, finding a journal, all these topics. Next slide, please. So the subject specialist, the faculty, taught about the writing process, author guidelines, how to submit to a journal. Liz and Nagin and I covered the librarian skills, scholarly publishing and journals, copyright and contracts and different research skills. We had to adapt our course materials, the things we teach at UW to a Kenyan context. We really focused on free materials for both resources and tools. Next slide, please. So Saturdays were the hands-on but fun, fun but hard work days. We started with everyone doing a 20 minute abstract of their dissertations and then worked on teasing out what was the most interesting storyline or research question for a short article using that finer rubric. Each week they drafted a section, abstract, introduction, methodology, results and they did peer review in small teams so that by the end of each session, each student had read their papers to each other. Next slide, please. So the Saturday classes were eight to 10 hour time, six to eight in the evening, their time. Again, we reviewed all the work that happened in the dissertation process. They collected lots and lots of data and so we had to talk about the ethics of data collection, IRBs and in one case getting permission to use the data because it was not what the student had collected. I think one of the best things about this class was the faculty gave individual feedback and worked with the students one-on-one on their papers and I was most impressed. The students gave each other excellent advice and feedback. It was a great situation. So the results of the class are technically still in the works. We do know how the 10 week session went over but their participants are not done yet. Next slide, please. So before the course, participants were given two assessments. One containing questions about basic concepts we would be covering in the class and one asking about their general knowledge, attitude, behavior around scholarly publishing. That's where those charts I showed you earlier came from. After the course concluded, participants were given the skills test again to see whether they had absorbed the didactic content. These were short quizzes that we developed to go along with each day's lecture. We also met with the students in a structured conversation after the class without the faculty present to get feedback on their experience. They'll be given another assessment once they have gone through the whole publishing cycle. Next slide, please. So the current status, it takes a long time for 10 people to share with 10 people and to get feedback and really refine things because sometimes some people weren't pulling the best storyline. I'd say most of the participants finished their methods but they didn't get any further than that. Now the admin for the department is keeping on top of them and three are really far along and should be publishing shortly. Two or three are lagging a bit, but I think they can do it. I've gotten a question asking about certain journals. The grant funds expire in six months in March of 2022. So we're hoping that they do get published. Next slide. The participants told us they were very happy to learn about some free tools, especially Zotero which they can pass on to their students. I'm not sure if I said this explicitly but these 10 people are teaching, they're seeing patients and they have children, we met many small children in the Zoom rooms over the course of 10 weeks. So they're very busy. They particularly appreciated how to do a literature review and what the structure of a paper is since they haven't gotten to the publishing phase we really can't comment on that right now. Next slide please. So the lesson learned, 10 weeks is too short. That wasn't realistic for people who are no longer in school who are teaching, seeing patients having, have families to finish in that time and deadlines are important. I saw the admin's cheat sheet of how she's keeping in touch with everyone and I think some people are more motivated than others to get this done. There's a lot of pressure on people and so maybe if explicit deadlines had been set up from June to November, all of them would be further along. Thank you. Thanks, memory. So yeah, this was a really fantastic course and project and we learned a lot but as I mentioned earlier one of the reasons that I particularly was really interested in doing this project was because I'm the library's liaison to the graduate school for UW's electronic thesis and dissertation program. So I was really interested to see if there were things that I could take into the UW context and help there. So giving a little background as to what that looks like at UW. So within the libraries we offer a lot of different services that sort of address different aspects of the publishing and writing cycle. This takes the form of, or this happens in a number of areas. My department, which is the Scholarly Communications and Publishing Department, offers support for data services, for copyright, the electronic thesis and dissertation program itself. We also have liaisons all over the library offering more sort of traditional research skills like literature reviews, like honing a research topic. And then we also have a dedicated service helping the citation management as well. The way this happens is really only very loosely coordinated. So there are a number of folks who do this work and provide this kind of support. The primary way that this happens is through one-on-one consultations. Many of us are available just to talk to students through their particular concerns. But we also offer courses, standalone courses, and a number of us are also often invited to come speak at individual classes. So forming relationships with instructors to come speak to their class about these issues. And there is a lot that goes into this work that is sort of beyond the expertise of the library. So we have created a number of partnerships throughout the University of Washington that are really helpful in this area. Some of them I wanted to point out. The eScience Institute is the center for data science and working with big data at the university. So they have been incredibly helpful in offering support around data visualization, cloud computing, things like that. As I mentioned earlier, the ETD program is in fact a partnership with our graduate school. So we work really closely with them in supporting students. They focus for the most part on the actual graduation process itself. And the ETD administrator is the platform that we use for students having to upload their work. So they sort of handle those kinds of questions while the library really focuses on publishing and copyright and open access in that aspect of this process. And then there's also the Odegaard Writing and Research Center which is located in our undergraduate library. They offer a yearly dissertation retreat to students that I have talked to a number of times but it's a pretty short session only once a year and really a small number of students that take part in that. So we get a lot of different concerns from students. There are some major themes that come up throughout these questions however, one of which is of course this idea that they want to take the dissertation that they are currently writing and to publish it either as an article or as a monograph afterwards. So there are a number of issues that students face here. Of course, there's the different publisher policies on preprints and students really are unsure about whether their publishers will be okay with having their dissertation out available in the world but we also have an issue in that. As I said, we use the ETD administrator system for students to upload their work. That thesis or dissertation through that platform gets put in two different places both in the ProQuest dissertation database and also research works which is University of Washington's institutional repository which is meant to be an open access repository. So according to the graduate school policy all theses and dissertations must eventually be made openly available but they do get to choose the timing on that. Unfortunately the options for timing and access for research works are different than for ProQuest and so there's just a lot of confusing confusion about how those two symptoms interact and how to actually select the appropriate options so that effectively they get the embargo, the restriction that they want. So thinking about overall learning objectives in this area we really want to be helping students thinking about how to find a publisher evaluating fit and quality and impact but then also particularly looking at their publisher policies or how those publishers feel about preprints and dissertations. And then of course we want to be offering them some more concrete information about how the EDD and administrator system works as well. We also get a lot of questions on the flip side of that. So there are a number of degree programs that offer what's sometimes called the free article thesis option. So this is where students simply write and publish articles and effectively staple them together with some introduction and context. And when they do this, oftentimes students are signing fairly restrictive copyright agreements, author's agreements. So many students aren't aware that they're giving up their copyright which of course has implications for whether they can reuse those works within their thesis or dissertation and has implications for us to whether we can get that license to distribute it. There's also the issue that ProQuest is a for-profit company and even if some publishers are okay with having preprints out in the world, there are a number of them that actually specifically say it must be nonprofit use. So that can be an issue for students as well. So again, thinking about the overall learning objectives that we want in this area, helping students figure out both what the context for their copyrights within University of Washington but then also how that interacts with publisher policies and the contracts that they're going to be signing with those publishers. And then of course, we just get a lot of general copyright and licensing questions. There are two aspects of ETD administrator in particular that students trip up on sometimes. One is around the copyright registration that ProQuest offers. University of Washington has students keep the copyright of their thesis and dissertations but when students are faced with this question, do you want to register your copyright? Oftentimes they think, wait, does that not mean that I have my copyright? If I don't have it registered, does that mean I don't have copyright? So there's a lot of confusion there. And then of course we give the opportunity for students to add Creative Commons licenses as well to their thesis and dissertations. And we get a lot of questions about what does that mean? What's the best one for me? So thinking about again, what we want to be the goals for learning for students, understanding the specific UW context for copyright and how their copyright works for their thesis and dissertation is really important. Again, the ins and outs of that UTD administrator system. And then of course the broader Creative Commons and helping students understand what those licenses mean and how to figure out which one to pick. So as we said, there was a process of putting together a let's publish your thesis course was really fantastic in that it brought together a lot of this information that we already give and that we haven't really figured out how to package well for University of Washington students. So we are currently trying to figure out how to better do that for students. And really what we are focusing on in the next couple of quarters is putting together a Canvas class. So our instructional design and outreach service departments is what there are online learning specialists and they have a number of classes at this point that they offer that are asynchronous classes. So oftentimes it'll be a week long class where that week is scheduled but the work itself students can do on their own time. So you put the content in Canvas and then instructors can interact with students through the discussion feature of Canvas. The online learning folks are also playing with Slack integration as a way of connecting with students rather than that discussion feature. So we have some playing around to do as to what the actual best way of doing that is. So one of the things that in working with the online learning folks, it's been really clear that teaching an online asynchronous class is not the same thing as teaching an in-person synchronous class. And one of the primary issues is being able to really distill what the most important information is in a way that is as direct and to the point as possible. Giving more information means it's actually more likely that students will not absorb it. So really getting to the points and really honing in on what the most important ideas are is we've done a lot of work in thinking about what that actually looks like. So we're thinking that we're gonna be focusing overall on four topics. First, that kind of general idea of how to choose a publisher, which of course, again, we have that thick quality and impact structure that we use, but then also adding on assessing the publisher policies in the context of the fact that your dissertation will be openly available. We know that we also really want to focus on copyright in general, contracts, publishing contracts in particular, the Creative Commons licensing and how that works, and then putting it all together and really focusing on how these issues play out in ETE administrator and how you go and make the correct selections for your particular circumstance. The way to do this, the Canvas class is gonna be organized into modules. The one that I'm showing here is actually a separate data management focused class that I've been involved with, but it really shows the structure that we try to import, which is you give the overall topic, you get some resources around that topic, you give an activity that's, it's not a graded activity, it's basically just designed to have the students play around with the resources that you've just introduced with them and then you give them a discussion prompt and ask them to use the discussion feature, ask questions and have the instructors interact with the students within that discussion feature to help them figure out what's going on for that particular topic. We, so for the let's publish your thesis class, the School of Dentistry, folks really took the lead on the assessment of the libraries where you do things a little bit differently. We have a pretty standard assessment survey that we give to students at the end of the class, but we've also started playing around with some new self-reflection techniques. So UW, it's been really exciting at UW libraries that we've recently opened the Open Scholarship Commons, which is the Center for Open Research and trying to sort of better bring together this kind of support in a way that users can find it. So through the Open Scholarship Commons, we have this practice now of a formal structured self-reflection that we do after events and courses, what went well, what didn't go well, what kinds of things might we want to change, how much time and effort would be necessary in order to make those changes, that sort of thing. And then we also, all the folks who are doing work associated with the Open Scholarship Commons, we meet on a quarterly basis to have a group reflection. So again, sharing best practices, what went well, what didn't go well, so that we can all learn from each other through this work. Now, the one piece of this that I'm personally still kind of struggling with, we, it was so clear through the Let's Publisher thesis process that I guess the didactic information was important, but it was that hands-on information or that hands-on practice and really that very specific interaction with subject matter experts that was so useful for the students. For articles in particular, where the structure of articles can be very different depending on what discipline you're in, it's really important to have folks who know that work and be the ones working with the students there. For monographs, we are really fortunate in that we have a good relationship with the University of Washington Press. So they can give some context about that process but we know that this is a significant need for students and we know that the participants in Let's Publisher thesis really found that aspect of it to be one of the most valuable pieces of course. And so that's an area that we are still trying to figure out how best to address. So that's the end of our formal presentation part. Do you have any questions? Thank you. Thank you very much. I have some questions but let me start with one in the Q&A chat. Jonah McCallister Erika writes, have you found a publisher that isn't willing to grant permission? I've not encountered one that won't eventually. It may take some effort. Often speaking with a real person does the trick. Yeah, I also have not, again, if you can do it on that, on that getting a student to talk with their editor level, you know, it is so common for students to be taking dissociation work and turning it into articles. Like publishers would be really shooting themselves in the foot if they didn't let folks do this. So yeah, on an anecdotal level, I have not experienced that. It would be interesting to see if there are examples though. Thank you. I'm wondering, Liz and Lindley, if you have a sense of how to translate the course that you developed into students from other disciplines. Yeah, and I think that that's really one of the central issues. I think the pieces of it that are consistent, the general framework of finding a publisher, which is, you know, we talk about fit, impact and quality, which really are sort of universal things that people should be thinking about. The general copyright system is of course, universally applicable. It's really that structure piece of the articles themselves and the nitty-gritty of taking, you know, there are 300 pages of work and getting it down into the 30-page article that is the discipline-specific piece of it. And that's where we were so fortunate to be able to work with our subject matter experts. And that's the piece that really, we haven't quite figured out how to translate for the wider audience. I mean, I think it's just gonna need to be partnerships with more subject matter experts. Certainly, certainly. And it seems like the components of your program could be plugged in to another discipline. Exactly. You are at four minutes. I just wanted to let you know that. I have another question. This is really exciting to me. And I'm wondering what advice would you give to your colleagues who were just starting out, just wanted to create an initiative like the one that you've done? Yeah. I mean, I think that it would be important to get a good sense of what the local needs are. If your university does focus on different disciplines, I've been at UW in this position for three years now. And so those patterns of what the questions are that students ask, we feel pretty confident that at least overall, we know where to pinpoint there. So just getting a sense of what the need is to be there with. And then just starting to break down, what does the publishing process look like? What are the steps that everybody has to go through? And can you start, is there information that you have available that you can start plugging in to that overall publishing life cycle to start making something bigger? I'd start unlawfully if you have stuff to add. The only thing I was going to add is, if you're just getting started, and this is something you want to do is to find a champion. You know, we all have certain faculty members who we have close relationships with. And Dr. Seminario is so, she's really dedicated to increasing research capacity, especially in underserved communities. So this, she drove the car at the beginning and then we all jumped on. But having that champion or that having a faculty driver is really important. Yeah, that seems really wise.  And it's this mysterious process that no one teaches you how to bridge that first gap into your, as an early career researcher, how do you begin this? And it's nothing like doing coursework. It's also not a lot like writing a dissertation. It's a different kind of direction with a different skill set and different necessary resources. And I'm just, I think this is a wonderful program.  I also think that just the beginning aspect of getting students to think of themselves and the work that they do as worthy of being shared, just even understanding that publishing is an option is really not on many students' radar. And so getting them used to the idea that the work that they're doing has value and that it could be something that could be published formally is I think can be very transformative for students and how they view their overall coursework and how they view their career progression as well. Wonderful. Well, I don't have any other questions in the chat and I want to really sincerely thank you for presenting on your topic. It was really very interesting and has got wheels turning in my head and I'm sure there are other colleagues who attended. So thank you for your brilliant program and I'm sorry that you have had so many technical difficulties today but it didn't look like it when you did your presentation. So thank you so much for being here and thank you participants. Thanks everyone. Thank you. Bye.


What is regularization? Regularization represents a broad set of techniques to curb overfitting. In the context of linear regression and a generalized linear models, it can involve just adding a penalty term to penalize the coefficients. In the context of decision trees, it involves pruning decision trees, thereby making them less deep. And so, small changes in data won't cause vast changes in the structure of the tree, thus curbing overfitting. In the context of neural networks, regularization can take the form of dropout, which means randomly switching off neurons during the training process so that you force the network to learn along different paths that helps the network generalize better, hence mitigating overfitting.


I just started it. Thank you. All right. Now the floor is yours. Okay. So I am, let's see how this goes. So I am the cloud native architect for resource management, not for all of Intel. I'm not even sure what my org is currently because we just re-orged, but Sasha is my counterpart in SATG. So just to make sure we're all talking about the same subject, when you're talking about resource management, there's two parts. And I know most of you probably already know this, but I run through it anyways just to make sure we're all on the same page as far as what we're discussing. So there's two parts of resource management and clusters. They're scheduling on the clusters where you schedule your workload matters. And so if you don't want to be scheduling your simple workloads to your high-performance AI specific machines with GPUs on them, and you don't want to be scheduling your high-performance workloads to underpowered cores, right? The other, so here's the general picture, which is basically this is just a spread of a heterogeneous system and maybe what you might want scheduled on there, right? So currently with, we'll go through this with the Kublet resource plugin, but currently you ask for a certain number of cores and it does its best in scheduling. So Kubernetes is not great at handling heterogeneous clusters at this time, right? The second part is once you get to the node, what do you do with your resources? So how do you schedule your resources determines both performance of your workload and how long it runs. And this is also getting added attention to the sustainability forums that are starting up and they're all over the place. There's one with NCNCF. Ideally you want to power down all the resources not currently being concerned from a sustainability standpoint. And at the same time, you still want optimal response in this and getting the resources aligned when it's time to use them. This is just a generic example. I know it's new and specific, but you can do this with any sort of resource changing.  Ideally you want these aligned. This gives you more responsiveness. It's faster. It doesn't run as long. It doesn't take as much energy. So my team has a few different projects. We have telemetryware scheduling over an SATG, which I'll also run over is UPIware scheduling, which is part of that. There's power management and then there's the cooblet piece that we would like to get done. So that is a really big piece that I would like to understand community needs for. So telemetryware scheduling, why? We want to avoid scheduling on unhealthy nodes. We want to migrate pods away from unhealthy nodes. When scheduling, we want to consider node property such as temperature, current load, power, and other. And we want to give support to external components like the Kubernetes deschedulers and GPU ware schedulers. I think I did the site. So telemetryware scheduler is currently an extender. So we take telemetry data to aid scheduling and descheduling decisions in Kubernetes. We use policies to enable rule-based decisions on pod placement. And these are powered by metrics collected from the nodes. You can use Prometheus. You can also use other metrics collectors. It knows how to interpret filtering and scoring and utilize node affinity rules and the policy support multi-metric rules. So this is new this year. So we can take any of an olive. So you can combine metrics. So this is the general layout of how this works. There's Prometheus. There's Prometheus adapter. There's custom metrics API. Basically, if it goes into the custom metrics API, we can pull it. Then there's telemetryware scheduler working with the scheduler. And then you can have TAS policies. So we're going to go through these one by one. And there's don't schedule. So pod with this strategy will not be scheduled on a node breaking these metric rules. So if it's with metric name, if it's equal to one, then don't schedule there. And then if it is scheduled here, it prioritizes nodes based on a comparator and an up-to-date metric value. So if the temperature is low, in this case, you schedule there. De-schedule, so if a pod with this policy is running on a node and it violates, can be dis-scheduled with the Kubernetes de-scheduler. So basically, if your temperature is too high or your amount of RAM is less than some amount, then it will de-schedule. And we also allow labeling. This is less than the scheduling, but maybe based on your particular scheduler. So in this case, we basically make labels based on these rules. So you have a card 0 equals true and card 1 equals true. And this is used partially with GPU or worse scheduling. So this is just info on this. You can submit PRs for changes. This is open source. We do have future work for TAS before I want to release this and try to put it into the community, which is specifically to move from an extender because we're currently a Kubernetes extender to the Kubernetes plugin, which plays a little bit better with the current scheduling decisions. So we're currently in that work. But once that's done, we do plan to try to push upstream to the community. And these are more links. I can send this after, but there's white papers on this. We have a power-specific example. And then there is a recent KubeCon talk and demo done by Denicio and Madalina on my team. Do we have any questions on this before I move to GPU or worse scheduling? None for me. OK. So caveat to this is there's GPU or scheduling. So this is a case. I'll go over the use case. The node has two GPUs, and each has a certain amount of memory. And you want to make a replica set to three. And each of these needs five gigabytes of memory. You end up with those nodes being split, or one of those pods being split, because you can put one in each, but then you still have three in three. So this is basically keeping you from scheduling across GPUs. But there's other ways to do this. There are other pieces of this. But with this, we are using the Intel i915. That's a Intel-specific GPU. And we can choose a number of millicores here. And we can choose an amount of memory per each. And choose how many, so this tells you how many GPUs you want, and then what the spread of the memory is for the particular one. So this is cases where you want to divide up the current GPU into slices, and then schedule it across many pods. Or you want some sort of specific number of GPUs on your pod. So this is that particular project. There's NFD with GPU plugin, because you really do need NFD to do the node feature discovery, so you know what's running. Are there any questions on that one? OK. I think one question that I had was on the GPU. So this is for any kind of GPU? Yeah, as long as you can schedule multiple things to it. So how you do the underlying pieces, the device plugins is your own piece. But this will help you do the scheduling. OK, so basically the device plugin would take care of making sure the drivers are up in the node, and then this takes care of the pod scheduling, and they can share it with you. Right, this is the scheduling half. So earlier we had the scheduling half and the resource management half. This is the scheduling half. So to be a bit more specific, the device plugin needs to be specifically crafted to utilize real functionality. So our team who is doing the support for GPU is involved in this scheduling part as well. There's two sides of the same piece. But I guess the question I asked was if I would be using an NVIDIA GPU, for example, with NVIDIA operator orchestrating the driver setup. Then they need a driver to handle it. Yeah, and the NVIDIA plugin needs to be adjusted to utilize the same concepts. All right, OK, thanks. Yeah, so this is scheduling only. And then we have the last project that's Intel specific. Well, GPU aware scheduling and telemetry aware scheduling aren't Intel specific, but we are using them for Intel. Is a power manager, which it provides limited control over the pod. So Kubernetes currently, you don't have really any power over the configuration of CPUs assigned to the pod. So if you want to lower the seat frequencies or raise the frequencies, and you do want that all the time with performance or sustainability environments, you can't do that. And so we've does the Intel Kubernetes power manager is designed to expose and utilize the Intel specific power management technologies. So currently, we have granular control over the configuration cores. We can change the frequency of all the cores in the shared pool. We can lower power consumption by controlling the frequencies of the shared pool cores. And then these are the particular features we have. These are SSTBF, SSTCP, and then frequency tuning. And currently, so I'll advise everyone to wait about a month, maybe less, until we release the new version of power manager. But we're changing from using the library we were using, which was a Python library, to a Golang library that we've also built, which is supporting. It's easier to deploy. And also we have better, it's faster for us to get in functionality. And it's open source. So those are also shared here. So I can share those links also. And we also have a white paper on how to use these. It's, I don't know, we like it. It's currently, it'll remain an operator. In the future, I'd like us to add a GRPC interface to it so you can control cores from outside the power manager through the power manager, basically, so that it doesn't have to be through the pods. But if you have something monitoring things on your system where you want cores spun up or down, you can do that. And you don't have different power managers and governors fighting for control of the cores. Does that make sense? Okay. And I'm happy to work with anyone who wants to work with us. I am requested. We get this out of the door, but we're already going to go. And then this last piece, which I'm extra, this is a community project, more than Intel project, is that we have the current state of Kubelet is we have some restrictions that we can't handle today. So you can't mix PINs with shared cores. You can't choose which pneumozones. So topology manager does a compact packing in pneumozones. Different types of frequencies. So if you have something, we have different types of frequencies within a core, you can't choose them according to frequency. The cores are allocated by container, not by pod. I can't assign them to a pod and then let the pod move from one to the other. I can't handle the affinity of anything below node level. They're cold, so it doesn't support CPU or memory, less nodes. And there's still a max eight pneumozone limitation, which as you start looking at the Thailand, that a lot of cores are doing it these days, plus the fact that there's multiple sockets. That's a pretty big limitation at this point. And part of the challenge to this is Kubelet has a set of resource managers that have to be addressed every time we add a new feature to the Kubelet. So the current solutions, including CRM and CPU puller, they work by turning off the Kubelet functionality entirely, which can have unintended consequences assuming something's working. And we still cannot schedule cores by pods or across specific pneumozones or affinities. We want it out of this model. So I was speaking to Derek Carr and his suggestion was to split the Kubelet into a control data plane and make the control plane a pluggable. So working from that, we would like to do this work so we can release resource managers custom to our hardware to handle our specific use cases, including plugging into solutions we've developed, such as the CPU manager control plane. It's wrong. This is the CPU puller for CRM while still being native to the ecosystem. And if you want info on CRM, Sasha is here so he can give it, he probably has a presentation in his back pocket he can go through. Future is we want to finish getting this RFC through the new and developed, create a cap and start work and get the Kubelet remodeled following the specifications and which I have links to. And we want to plug our resource managers into the new model, which will be more native. Historically, Kubernetes has kept things in pluggable interfaces. So CNI, CSI, device plugins, but we haven't done that with our CPUs and memory and for our devices. And if we have time, we're at the half hour, we can go off over the RFC for the CPU landscape exploration doc where we went through all of the different issues and then customer requests, et cetera, and we put them all in this document so that we knew what we were missing. So that list that we have up there mostly comes from customers or from those issues. Great. Added. Do we want to go through that RFC? Do we want to talk about CRM? I don't, I'm putting it on the spot, Sasha. Sorry about that. No problem. From my point of view, I'm happy to see you continue a little if you feel like we've got time. Okay, we can go through the RFC. Sasha, do you want to, at the end, go through CRM or do you want to do that first? Up to you. I'm fine with that. Okay, let's go through the RFC. It's fairly short. Let me pull that up and share that. You have to find which window I was on. You have to stop sharing and then re-share. Okay. So we'll go through this. So at the beginning, this basically goes through the fact that Kubernetes was initially written with this simple model of node resources and how they would be configured. This has worked well for generic, but now we have a wider range of use cases, which is why a lot of you are in this group is you have your own specialty use cases for HPC or AI or any other specialty case. Telco has worse cases as well. So we wish to move to a kubelet resource plugin model similar to how specialty resources are handled as we have within the device plugin model. I'm currently, here's what the kubelet looks like currently. So you have the kubelet, you have the topology manager, and then you have the hint providers. The hint providers are your CPU manager, your device manager, your memory manager. And everything has to go through the topology manager to go through. So anytime you make changes, you have to make sure all of these places work correctly. So the exploration doc is listed here. There is some commentary on here. I would like more commentary, just to make sure when we start the cup, we know what we're doing as far as who's working on what. So we make sure we're handling everything. The cases I have in there are already in there, so the other one is you can't take advantage of non-uniform, all three cache access configured for CPU course. So we have Intel RGT, but there are others. So that was not listed in the other one. I should probably add it to that. So solutions to any one of these challenges require a related solution to optimize memory. So if we change where the cores are, now we have to check the memory. So if you touch the CPU manager, you'll now have to check the memory manager and you still have to touch the topology manager, right? No matter what you do. So our design proposal is to make a pluggable resource hub, basically, instead of retrofitting functionality to the existing model continually, right? And basically to pull all the resource managers that are currently in there, topology manager, CPU manager, device manager, memory manager, out into a plugin and then work backwards from there. We're still going to need to also handle the runtimes. So there needs, whatever plugin we do has to be both, because we do wanna roll those managers out probably into a GRPC piece. We still also want to make sure that you can also route them through the runtimes because there's projects that route the, including CRM that route the resources through the runtimes. So this particular one will go through the goals. We wanna be able to plug resource managers into Kuglet to allow customizer of resource requirements. We want to be able to export resources to expose them to the scheduler. So that piece may be more complicated because now we have added annotations, right? We want to make it simple to expand resources to those currently not envisioned. So when you're talking about memory less nodes or CPU less nodes, there's other components there, right? You wanna make it simple to expose attributes about resources. Non-goals, we don't wanna break any existing use cases. So whatever solution we add, there should be full support default behavior. And we don't wanna change default behavior. We don't want to create any more latency than there is today for scheduling. And that's, that may be something we do in the future or have a look at after we get this done is there is still quite a bit of latency in scheduling. We wanna be able to support current spot specs. There may be additional expense sensibility, but we still need to support the current spot specs. And the plugin should not be writing to the API themselves. So there needs to be some sort of interface. So the next step is basically to start the cap, but we're still looking for feedback here as to what goals and non-goals are to make sure we have everything encapsulated. Thoughts? No, I mean, it's very, very good, very detailed. On the RFC side of things, is this something you've had to do before or is this the first time you've done this? This is the first time I've done this. Sasha's done this before, I'm sure. I had some questions actually almost right back at the beginning. When you're writing a custom schedule like this, how do you go about testing it? So that's part of the questions. So to start, we're going to be using the default managers, right? So whatever functionality and testing that they use when they put in those with the initial caps is a testing that we'll pull out to make sure it works now. So all of the current ways that we already validated the topology manager, memory manager, CPU manager, all of that seems to work through the plugin model because if it doesn't work through the plugin model, we're missing something, right? We do have some resources to work on this, but we would like community health problem, you know? Does that answer your question as far as testing? Yeah, basically we're looking currently at pulling out all of the current caps that we're already put in for CPU manager and device manager, all of the managers and just pulling them out and then looking at those particular tests. And if someone wants to test a custom resource manager, you're right, we probably need to test harness, so that's a good point to have there. So should I add that to the goals? Yeah, yeah, can't hurt. Are we into general questions now or have you got anything else you want to cover? I think I'm done. Sasha, do you want to go through CIRN or do you want to just go into questions? Well, I can say a few words because there are a few additional things besides with CPU management activities. If you can stop share, so I can reuse. Floor zero, thank you. The recipe, we should be able to see it, right? Yeah, that's good. All right, so I'm going just to reuse a couple of slides from our presentation, what me and one of our team members from my team and Auntie, we did on HPC and BatchWorking Day in last cubecon. So, Maro already mentioned about our project CIRN. The history of that project is such what we tried to create with Kublet resource plugins about three or four years ago. And at that time, community was not ready to. Now it looks like a community a bit more receptive, but meanwhile, to validate all the ideas and to see what we are proposing as actually working, we needed to have some solution. And we come up with some intermediate step. And this intermediate step is CRI resource manager. It works as a normal container runtime. So Kublet sees it as a container, geo cry or whatever. It's absolutely transparent towards the Kublet. It doesn't reinvent with you. So in the backend, it still uses container, geo cry or whatever you prefer to use. But what it does, it allows you to have a dedicated set of policies on how you are managing the resources. So we have both policies related to hardware. So like all the scenarios what Maro just mentioned like limit of NUMA nodes or memory cheating, different setups, all of these things, we tried, we know how to work with it. So like we have tests with huge machines like 32 circuits and so on. We had scenarios with different memory tiers like how you've been with this memory, PMIM, CXL memory, which is upcoming hardware and so on. We also tried to work from a perspective of not only hardware, but also application. So for example, if you have a set of containers which needs to work together, let's say like your application plus service mesh container, you don't want to, like when the data is passed between those two containers, you don't really want them to cross like L3 cache domain zones or even worse like memory domain zones and so forth. We support container affinity and anti-affinity. So for example, like your database should not be affected by like CPU consumption of backup container or something similar. So we provide to the user the set of knobs how to get out of the node. And that's actually like the main difference between like what team or where Marvel is working and my particular team. My team, we are focusing specifically what happening within the node, like all the details, all the deep knowledge of hardware, all combinations of how it's going to work. So as I mentioned, right now it's implemented as a like kind of proxy between where Kublet and actual container runtime. But we are working together with container deep project and cryo project to implement the thing which is called NRAP, node resource interface. It's also plugging interface similar to what Kublet community is now thinking of implementing, but it's a bit more detailed. The reason for it is what we need to understand the border where each layer of the Kubernetes stack contains enough information of doing the proper decision. So right now the communication between the Kublet and runtime is kind of imperative.  The problem with that is what it was okay five years ago when we had only run C as a runtime. The current set of runtimes we have VM-based runtimes like Cata, we have user-leap-based runtimes like device and end hours. So all the assumptions what Kublet has about how the container is run is not necessarily appropriate or not necessarily the true. So some of information available only on the runtime. So with things what my team is trying to do, we are trying to make sure what certain information properly pass in between the Kublet and runtimes and when utilizing how it's done. And beside the CPU, we have several other activities like NRI I already mentioned, but when we have a few things which is related to class-based resources or quality of service kind of resources. So it's cache, it's memory-benders, it's block, well, to some degree, memory teaming can be represented as quality of service scenarios and so on. And another thing is device manager. So like what Marlowe just mentioned about the GPU scheduling it's good, it's a way how to utilize GPU based on current device plugin API. But the problem is what current device plugin APIs contains a lot of, I wouldn't say design mistakes, but inefficiencies if we are looking from the current hardware state of view. So like it worked well if you have single exclusive use of the hardware without any knowledge about internal resources, no shared usage and so on. But as soon as we start to thinking like, okay, let's have one physical GPU or some other accelerator device to be shared. Let's think about the memory on it. Let's think about the internal topology of those accelerators and so on and so forth. Those simply didn't work. Like what are different workarounds and what we implemented with GPU device plugin for Intel accelerators, it's also set of workarounds. Nvidia have way on Google for Nvidia GPUs, we have way on, but it's all not really extendable. So what we are working together with Nvidia and recently we also have people from other projects joining. So like one notable is ACRI, like IoT kind of devices, network-attaching devices, we have those two initiatives. Like one is CDI container device interface. It's a game on the runtime level, how we attach the container to the device. No, sorry, how we attach the device to the container. All the nifty details, how it should be done on a low level. But when the upper part, like the cooblet part is dynamic resource allocation. So this is revisiting how the user can request the device. So going from the previous model of let's use the extended resources and when try to have like all kinds of combination of those resources and when GPU schedule extensions and so on, we are coming to interface similar to persistent volume claims. So you request the device of particular class. You specify a set of parameters to this device. When device driver, like the vendor specific code will be able to understand what those parameters about, how to get it properly allocated and when hint to the scheduler where it will be allocated. So like full flexibility for vendors to provide like vendor logic specific particular device or actually even chain of the devices. So this is like set of puzzles for Intel in overall working across multiple teams in the resource management domain. From scheduler, existing cooblet things, low level runtimes and combinations of it. I think I will stop with that. If for additional questions, I can pull out some of the slides or some of the details. Cool, thank you. I don't know if anyone else has any questions. So I'm curious how the folks in the traditional resource drive management scheduler community would interface with something like this. So if you had somebody from the Altair or the SketchMD community that wanted to pass back to scheduler to make some, to give it information about what components of the node, what resources on the node it should have. Is there something in what you're proposing here that they would be using or that's kind of a entirely separate scope? So there are several things how we can tackle it. So right now the cooblet is discovering resources and when doing my assumptions about how those resources are present on the node. It's not necessarily much as what actually runtime has and can runtime can use. But let's one side of the story, I will come back to it. The second part of the resources is extendable resources. And here we have two variants how it can be announced to the scheduler. Like one is device plugins. So device plugin says I have this amount of instances of particular resource type. Second variant is what you can patch the node object and say what this node object has this amount of this resource allocatable. And one cooblet will do with simple accounting like how many pods are using this particular resource. To help with that, we have NFD. So like our GPU device plugin is working together with NFD to actually automate with announcing of those resources. So like for example, like this middle CPU or middle GPU parts of a GPU or like a GPU memory is handled by NFD plugin. But as I mentioned, it's most of it is like workarounds for current design of device plugins API. So current design of the extendable resources. This things what I mentioned like this dynamic resource allocation, it has similar setup like the storage drivers. So you have a cluster level components which works together with scheduler and you have a node component which is responsible to actually attach the device to container and work together with runtimes to do it. So it will be a part of this cluster level component to talk with the scheduler to make sure what the resources are available and can be consumed for the pod and provide with apology information on which nodes with resources will be available. Regarding the Kublet runtime part, it's long way to actually get there but what we eventually need to do is what we need to remove with discrepancy between the Kublet knowledge and runtime knowledge. So it means what at some point we need to revisit the protocol how the Kublet and runtime are talking about the resources. So right now in this class-based QoS resources what we have, we have a CRI messages where runtime tells to the Kublet which quality of service classes available and what types of QoS classes available and what is the potential values are available. So the node, the Kublet can report it into the node status and then the scheduler can consume it to make a scheduling decision. So it's similar model what we have right now for the native resources on the differences what Kublet not discovering it, Kublet gets it from the runtime. So if we are talking about the resource management plugins like regardless on which level on Kublet or on runtime so now later we will need to have exactly the same interface. So Kublet, sorry, plugin should be able to tell to runtime or to Kublet what kind of additional resources it might be available. So it can be used in the scheduling decision and obviously node status. And that's part of the work is figuring out how to have dynamic resources as part of this, right? So they do need to be advertised to the scheduler but some of that work is figuring out how. Yeah, the biggest problem with all of those how is what we have a lot of legacy code and we have a lot of users who are relying on this legacy. So to change something where we need to be very careful how to not to break the things. Previously it was a huge roadblock in terms of Docker because well, you still needed to take care of like Docker API which was quite simple. Now when Docker is removed, we have a bit more freedom like how we can evolve the CRIP protocol. Awesome, thank you. That is time for one more quick question if there is one. Otherwise, I think that's probably us could time actually five two. So thank you very much Marlow and Sasha for coming along. I think a couple of people has dropped. So sorry about that, but we've got it all recorded and we'll share it. So thank you very much for your time. It's really, really good stuff. Yeah, and I can send out the slides after Sasha if you want to add to mine before I send, I'll send to you. I just sent in the chat, we're linked to a session or what we had much on HPC day. So like the slides what I showed it's attached where and I think recording is also should be available for all the people. Yeah, that's great. And any slides just chuck them into the Slack channel. All right, that sounds great. Thank you. Brilliant. Okay, thanks very much. So yeah, that's probably it for today. Our next session is going to be actually 6th of July. I think it was in the agenda previously. It was down as the 29th of June, but it won't be then because we've already done two sessions in June. So yeah, 6th of July will be the next time and we're gonna do have a session, I think on Cillium and EBPF. So yeah, thank you again, Sasha Marlow and see you all next time. Thank you. Thank you. Bye bye.


This is due to the diet's ability to restore normal energy metabolism, which can help reduce inflammation and improve cellular functioning. Additionally, this diet may be beneficial in treating neurodegenerative diseases because it reduces oxidative stress and improves mitochondrial function. This article was authored by John Minn Rowe and Carl East Astrum.


Stand by. My fellow Americans, when we got to Washington six years ago, we set out to tackle the tough fundamental challenges to America's future. One of the toughest was drug abuse. Today, I'd like to give you an update, an administrative report, if you will, on this issue. Since 1981, federal spending on drug abuse programs has tripled. It is now nearly $4 billion, and we've included virtually every major federal agency and department in the effort. To consolidate our initiatives and make certain the fight against illegal drugs is a well-managed and effective undertaking, this March I established the National Drug Policy Board. This cabinet-level body, led by Attorney General Ed Meese and Secretary Otis Bowen, has developed a plan which will add new vigor and a more comprehensive approach to our crusade against drug abuse. The strategy is aimed at coordinating the wide range of anti-drug activities going on in our country, education, prevention, treatment, rehabilitation, and research to reduce the demand for drugs as well as investigations, intelligence interdiction, prosecutions, and international programs to reduce the supply of drugs to our citizens are all part of the same battle. The plan would designate a lead agency for each category of anti-drug abuse authority. This means that one federal agency will be the focal point for ensuring that all other federal agencies are doing everything they can to stop illegal drug use. For example, the Department of Health and Human Services will lead on the treatment and rehabilitation issues while the Department of Education will do the same for school programs. This approach is simple, straightforward, and avoids the temptation of adding another layer of bureaucracy. Much of what we do at the federal level is aimed at choking off the supply of illegal drugs. With the assistance of Vice President Bush, we are continuing to make tremendous progress in seizing drugs crossing our borders. With the Custom Service and the Coast Guard working more closely together, we'll seize even more. We arrest drug traffickers and send them to prison. With the Drug Enforcement Administration, FBI, and the U.S. attorneys working more closely together, we'll be even tougher on those who traffic in drugs. But attacking the suppliers is not enough. As long as there is an illegal market for narcotics, the drug lords will find a way to meet the demand. That's why we cannot ignore the other half of our strategy. We need to keep up the pressure to prevent drug use. We want no new users and we want those who are using drugs to stop. We should all be concerned about the competitiveness of our national economy. Last fall I announced a broad anti-drug plan which included the goal of a drug-free workplace. At that time, I signed an executive order requiring drug testing for selected federal workers in critical positions. Many companies, including more than one-third of the Fortune 500, already have a testing program in place. Drug testing, when done properly, can have dramatic results. Ask anyone in the armed forces. Through mandatory drug testing and a well-run anti-drug campaign, we have achieved a 67% reduction in the use of drugs across the board by our military. We need to achieve these kinds of results in our schools as well. Under the National Drug Policy Board Plan, Secretary Bill Bennett will continue to lead the campaign for drug-free campuses. We owe it to our kids to do our very best to protect them against this menace. And that's why part of our plan will also focus on high-risk youth, those young people with serious drug problems. Drugs pervade every part of our society, and the United States isn't the only one confronting this problem. In June, we will be participating in a United Nations conference in Vienna to spur international commitment to battle illegal drugs. Of course, well-organized and coordinated federal action is only part of the solution. State and local governments play an indispensable role through community school boards, hometown treatment, and rehabilitation programs, as well as enforcing of law. Most of all, however, we need the active involvement of the American people in developing a national attitude of intolerance to illegal drugs. Nancy was asked for advice by a young student worried about what to say when approached by drug users and dealers. She told her the answer was simple, just say no. Together we can deal with this threat to our families and country. We can help our loved ones and friends. We all need to speak with one voice. Say no to drugs in the school. Say no to drugs in the workplace. Say no to drugs in the home. Together, say yes to a drug-free America. Until next week, thanks for listening, and God bless you.


All right, D-Led. Yeah, Coach, would you like to turn over and talk to you today? Yeah, that's usually the story of the game, D-Led. Obviously, I was disappointing to turn the ball over three times. All of them were at the start of the drive. Put the defense out there, a lot of bad spots. We battled, but usually when the turnover of Martians like that and hand them things, it's usually the way it goes. But we fought, tried to get everything we could to get back in this football game. Doesn't quit, but obviously, we came up short. Run defense today? Yeah, I mean, they grinded it out. Like I said, when you hand them the ball right back, it's usually advantage of the offense. You got to give Noron's credit. They execute their game plan. And would you, you know, the season's over now, what was your initial statement to the team or just kind of overall defense to the offseason? Yeah, there will be a time and place for that, you know, starting tomorrow. My message to these guys, I was appreciative of everything they've done. Obviously, we came up short of our own goals here. But this team, you know, we learned how to win close games. We went seven and two in one possession games. We scrapped and called. Definitely feel like we've got a good foundation and the better days are ahead. Thank you, D-Led. Yeah, Arthur, there was a report earlier today that there was a report earlier that you and John Kateri and Arthur had told them that you had.  You can find whatever you want on the internet. I mean, Chris Morton's a pretty... Great, I'm not discrediting any through the border. But I can tell you this, for 100% of the fact, there was not a nonsense that came out in the spring. You know, how you want to insinuate things, no different than the Calvin Ridley question from last week. Stay in there. They're not a football decision that's made with the Atlanta Falcons without Terry Fontenot and myself collaborating. That's just absolute nonsense, Michael. Absolute 100% nonsense. It'll never happen. We're not professional politicians. We don't operate that way. I know a lot of the league likes to. Leagues, rumors, that's not how Terry and I operate. So I know there's a lot of respected people. They got a job to do, but that's just not what happens. So again, life's a lot better when you're not on social media. I know you got a job, I understand. Just don't look at your mentions, Michael. I unfortunately have to, let me ask this a little more directly. Do you expect Matt Ryan to be your quarterback next year?  I don't care about it. Everything is evaluated every year, and that's the way it goes in the NFL. To make a grand statement right after a game, we're all on the same page, but do I have to declare that Kyle Pitts will be our tight end for us next year? You want me to declare that? I mean, where do you want me to go? I'm gonna go down the whole roster. I'm not gonna back ourselves into a corner. I know you gotta ask the question, I appreciate it, but we're taking a fair evaluation of everybody, top to bottom, every single year. How do you feel about the way Matt's played this year? Well, I'll say this about Matt, and this is what I appreciate about Matt. From the outside looking in, he's always had a lot invested in the perimeter. There's been a lot of good skilled players on the outside, the first part of his career. Everything, this is what he proved as he can win, and we did it with a lot of different guys contributing. And so that says a lot about him. A lot of quarterbacks look pretty good. When they got first round picks, Hall of Fame guys outside from Gonzalez, Roddy Wright, when they drafted Julio, he was really the third or fourth guys. He got into it, he became obviously a premier player. You had Ridd, you had Austin Hooper. Obviously, Kyle came in here and was forced into a role by circumstance, and we did it with a lot of guys that fought every single damn week. And we found different ways, put Cordero Patterson out there, tried to do everything we could to win football games. And Matt proved that he didn't have to do it with nothing but first rounders out there. I think it says a lot about a quarterback. Mike got a bigger share than Cordero today. We only had 19 plays in the first half. Everybody's going through something, Josh. So there's a lot of packages and this and that. We had guys that, it's week 18. So again, there was only 19 plays. CPS obviously a big part of the game plan. We need more offensive plays. It's been the story of the last five games. Like I said, we found ways to win some games, but we knew a better job of being a little more balanced, which we will. What's the letter that's got with the tournament from the first play of drives? I mean, how costly was that to the overall flow of the game? Well, I mean, it's hard to get into a rhythm, but we took a shot down there, sideline. That got picked. And then we had two fumbles in order to start drives as well. We gave them the ball in plus territory. Those definitely put your defense in a bind. That was the difference in the game. This may be more of a question for when we talked to you on Tuesday, but in what ways have the last couple of games down the stretch shown you and Terry what areas you need to focus mostly on in the offseason? Well, I think you take the whole body of work, and that's why I mean, it's such a long season. And you do find out a lot about players as you go through it, and which guys you can depend on as a season finishes. I mean, everybody dealt with it, but normally you feel this time of year, if you're practicing, you're getting ready for a wild card game. Everybody's doing the same thing, but certainly you go back and look at it. There's something you could do differently. I think everybody should say, hey, how can we improve certain with the roster? Definitely adds up. No one's doing anything specifically with Kyle today, or was that just a fight? He was fighting through stuff, but he gave it everything. I don't think a lot of guys would have played in his circumstance. So we certainly tried, and I'm sure you'll get the hot takes about the target. He was a primary on a lot of play calls. I don't know if they took him away, but I can sit here and look at it and say he wasn't 100%, but I appreciate him going out there and trying to help us. Thank you.


that's coming from like the nerdy side of me but be that one kid on the first day of class that goes up to the front shakes their hand it goes a long way so my number one thing is this is your time to go get out of your comfort zone do things you would never do before these are your four years to make them what you want and so do with that what you wish. Personally I would just want to tell them to get involved I think that's just kind of the best way to really get plugged into campus feel connected to your time here I came to campus not knowing a soul all the way from Arizona and I'd say within two weeks of being here I couldn't walk across quad in between class about seeing at least one friendly face that's just kind of cuz I plug myself into a lot of different organizations. Say yes to every good opportunity that presents itself whether it be signing up for a new clever organization taking the extra time to meet with those professors just do everything that you can to soak up every experience that you can here in college there's a lot of times you might just want to go sit inside of your residence hall watch some Netflix or Hulu or something like that but I would encourage you go out make some new friends spend that time sitting in the Ferguson Center with Starbucks making a new friend hanging out with your old friends and just soaking up every second that you possibly can. Your experience is what you make it therefore if you want to have a phenomenal time in college make it phenomenal like Annalise said get involved just make sure you know you're happy here that's something I've been doing and it's working out great.


Today's daily debrief focuses on two sides of the political coin in the United States. On the one hand, we have the right-wing Republican Donald Trump, who's facing a host of legal challenges due to his support and role in the storming of the capital into January 2021. On the other hand, we have Joe Biden, who's extremely unpopular due to his failures to deliver on his promises and, equally importantly, for backing to the hilt Israel's genocidal attack on Gaza. In today's episode, we see what lies ahead for the both of them. We begin with Trump, who was disqualified from standing for the primaries in the state of Maine. This is based on a constitutional clause which bans from office those who have indulged in insurrection. The decision by Maine Secretary of State comes shortly after a Colorado court issued a similar ruling. Cases on the same lines have been filed in other states as well, setting the stage probably for a Supreme Court intervention. We go to Anish for the details. Anish, thanks for joining us. So Maine, the second state to come up with a similar prescription, if we can call it, but a very different one from Colorado. So could you maybe first take us through what the decision by, from the state is, what are the terms by, or what are the conditions or what are the reasons mentioned? Well, the reason is quite simple. It's the insurrection lawsuit that has been, it is one of the three lawsuits that has been fielded with the Secretary of State. Now in unlike, you know, most other places, the Secretary of State is essentially the one who handles a lot of domestic matters that includes election qualification and even at times the primaries which are like internal elections for political parties. So what the state secretary of the Maine State has ruled is that Trump is guilty of insurrection because of the January 6th Capitol violence. And because of that, he is disqualified from standing in the ballot for Republican party primary primaries. Now the issue, the thing is this is not necessarily a court judgment and it will definitely be appealed over time. We need to wait and see if it can be done because Maine is one of the first states that go into the whole primary season in the United States. And very often it is one of those states, along with New Hampshire, which is seen as, you know, which gives the, you know, the first lead for most candidates. If they actually can make a significant impact in these electorates of their parties, they can definitely see, they can keep up the momentum for the rest of the primary season, which goes on for months. Now, so if they do not do it within a week, I think, in less than a week, actually, and if there is no appeal happening at that point, then Trump will not be standing in the primaries in Maine. And that is going to be a big issue because obviously it's not the number of representatives that it sent, delegates that it sent the Republican party in Maine from is not that many. So he can probably turn it around later, but definitely it is going to have a significant impact. And, you know, it will be a major roadblock in the Trump's presidential bit. On the other hand, we still have 13 more states where the cases are pending. Some of them actually do have, you know, democratic administrations and also state secretaries even democratic appointed state supreme courts. And in all of them, it is quite, in some of them, it's quite likely that they will follow the same decision. So we need to wait and see how things are going to unfold. On the other hand, the Colorado decision, which is again done by the secretary of state, pretty much is based on the fact that there is an appeals process happening. So we cannot implement the judgment by the Colorado state supreme court, which might seem odd for those of us outside of the United States, because usually you have to get a stay or, you know, a hold on the judgment and nothing of that sort has happened yet. But the fact that it went to the supreme court and has been challenged in the supreme court is being used by again, a Republican secretary of state to just hold the decision and keep Trump on the primary ballot. There is a significant, there is a very clear political divide when it comes to whether or not or what shape these lawsuits are going to take in the coming weeks, even days now, because the primary ballots have to be ready by, you know, the first week of January in many states. So we need to wait and see how that's going to shape up. Right, Anish, it looks like a lot of this will boil down to what the supreme court of the United States decides and that it does seem like the Republicans have an advantage. The Republicans do have an advantage. They probably will. It's quite likely that they will win the Colorado appeal before January 5th, obviously, or but the question is whether or not the Supreme Court is going to intervene and have like a broader judgment or a broader ruling on the matter, you know, take up all those 13 pending lawsuits, you know, and actually give a definitive verdict on the matter of whether or not Trump was guilty of the January 6th and by default, guilty of insurrection, which is the only thing that disqualifies a person from running for the presidency. Now, the that is that is the biggest question because they might if it goes to trial, it becomes a federal trial that is going to have a very different impact and and very significantly different kind of scrutiny than, say, a state secretary or, you know, a state Supreme Court deciding matters. And that is something that the Supreme Court may want to avoid, even though it is it has a conservative supermajority. On the other hand, they could just, you know, go through these cases as they come and just, you know, give individual rulings of whether or not they're valid. And because we are also dealing with primaries and we haven't yet dealt with nominations for the actual federal election, that this is different because in some states, including some democratic states, the administration or the state Supreme Courts have refused to intervene because it is a matter of internal party democracy. And so they did not want to intervene on the matter, whether or not they think Trump was guilty of insurrection. So if the even if, you know, Trump kind of swims through this whole primary season without a disqualification, or at least without a major disqualification, there is there are still, you know, a possibility that Democrats or civil society groups would go after him before the nominations for the federal election happens. So it is still a long way. We are looking at a very long drawn election season next year. And that it is going to be quite interesting. But again, as I said, it is going to be very long drawn and pretty much unlike any of the previous elections we have covered or, you know, we have seen in recent memory. Thanks so much, Anish. You're talking to us moving on to President Joe Biden, whose full-throated support for Israel has earned him the moniker genocide. Now, Biden is facing countrywide protests by hundreds of thousands who are in solidarity with the people of Palestine. Equally worrying for Biden ahead of the 2024 elections is dissatisfaction over many unfulfilled promises. Anish is back with us for more on this. Anish, welcome back. We're now talking about Biden after talking about Trump. First of all, of course, I want to ask you a bit about the other response to Biden's policies in Palestine. We've seen hundreds of thousands taking to the streets, you know, a very number of polls saying that there is a great amount of support for a ceasefire, a lot of disapproval of how the US administration is handling the situation. Could you take us through what's happening there? Well, what we're looking at is how for a very long time in the United States, there was always this sort of smoke screen when it came to Israel, and it was pretty much successful in the propaganda machinery that existed, that supported Israel's wars. We are not talking about one or two, it's like there have been multiple wars on Palestine and there was only a minority, even if though they were like prominent and like they were visible in several places, it was only a minority opinion to actually support self determination of Palestine in the mainstream, you know, public opinion in many cases. But right now, what we're seeing is there is complete, you know, overwhelming support for Palestine this time around. Even the spin doctors who try to make turn it into like Palestine or Palestinian resistance had provoked the whole situation does not work anymore because of the kind of reports, obviously, that are reaching there. And despite how and we have seen that in multiple times in the mainstream media, despite how the headlines are, you know, tinkered a bit to make it seem as if somehow the 21,000 people who died in Gaza just died off their own and not because of a very targeted genocide that is being conducted in Gaza. And this is something that the Democrats, the establishment Democrats have not reckoned with yet because obviously they continue to be beholden by, you know, basically they've beholden by lobbyist money in most cases and considering the fact that the Zionists are the biggest lobbying group. I pack in fact are the biggest lobbying group when it comes to foreign policy issues. It is no surprise and much of their money also goes to the Democrats for that matter. It is no surprise that there is, you know, this complete disconnect from the people's opinions. And this is something that that's something that is definitely coming to bite them. And it is it is not definitely looking good. It has actually brought down Biden's approval ratings, even further that what it should have been, I mean, considering the mismanagement. But it's just tinted the entire image that Biden is somehow significant when it comes to shaping or directing foreign policy issues in the country. Right, Anish, but to go back to somewhat domestic issues now, Biden coming in, promising to reverse a lot of policies as a Donald Trump administration, making a lot of promises to key sections of this voter base. How successful has he been in sort of fulfilling these promises or delivering on them? Well, I mean, if you're talking about success, there has to be some intent to actually achieve some of that success. And what the Biden administration has displayed is that there has been no intent whatsoever to deliver on any of these promises. Very often technicalities have been used as a defense against criticism. Very often, you know, the fact that they do not have an overwhelming majority in the Senate has been used for the last the first two years more of their administration has a defense and, you know, or as a very convenient excuse to actually say that, oh, but because we do not, we can't stop the filibuster. We can't do anything about it. But we forget the fact that filibuster is something that they could have done something about as well before the Congress convened at the start of Biden's administration. So the fact that the establishment Democrats want to continue to keep this very convenient excuse in place so that they can be stonewalled, any kind of progressive legislation can be stonewalled, shows that there has been very complete lack of intent on their part. This comes on major policy issues, including, you know, health care expansion of Medicaid or different kinds of health care programs that the government has expanding the COVID era, welfare policies that actually afforded a lot of people a saving grace in many ways to actually get out of poverty, even if it was for a very brief moment. And even if it was far shorter than what they were required, it actually did help a lot of people. He cut down on those. He pretty much abandoned the entire, you know, $15 per hour minimum wage. That was pretty much one of his, you know, campaign plank. And all of that was completely and you see, like all of these factors, once they fail, they just get abandoned unless there is a massive movement or backlash backlash so huge that they cannot really just sit tight and like ignore. So it is somewhat of that sort that we're seeing the establishment Democrats actually the Democratic Party overall, we can't really differentiate at this point, who's the establishment and who's not is the progressive. But the Democratic Party as a whole, more or less have pretty much abandoned a lot of their policies. And that is, you know, that's showing. And this is despite many of the policies, the campaign promises that they have shown are wildly popular in the United States. And that has we saw with the referendum on abortion in a very considered strongly conservative voting state in previously. And all of that is somehow completely missed the messaging from the people having completely missed by the Democrats and especially the Biden administration. And that pretty much is showing in the manner in which he is losing support. And if he has to completely he has to stand against Trump, there is a good chance that he might not see a second term in, you know, the next next year in the general elections. Thank you so much for the analysis. That's all we have in this episode of Daily Debrief. We'll be back tomorrow. In the meanwhile, do visit our website, peoplesdispatch.org and follow us on all the social media platforms.


The law chamber has asked the federal government to establish a mobile police unit in the Goyuk area of Adamawa state. This is in response to a motion of urgent importance moved by Gibeon Giroki, the member of the House representing Goyuk, Shelling federal constituency. He said the latest was an attack on Dunla community with a huge threat on food security following the destruction of farms. The House also asked the Northeast Development Commission to give relief items to victims. On hearing the only son she had, she collapsed and died, is only through the grace of God. That means the Alban is living. My cry to this House, Mr Speaker, is for these hallo chambers to mandate the Nigerian police to put constant patrol on Savannah, La Mubri, in order for this ugly situation to be stopped.