Welcome, everybody, to this small demo about the useGalaxy.startSARSCOV2 bot scripts that we are running and operating to do automated SARSCOV2 genome surveillance based on the COVID-19 GalaxyProject.org workflows that you've seen already. So there are three workflows for variant calling, consensus building and reporting that have been introduced earlier today. My name is Wolfgang Mayer. I'm working for the Galaxy Europe team and I'm going to guide you through the system we've built and that we use to orchestrate the action of these three types of workflows to build a really scalable system for high throughput SARSCOV2 genome surveillance. So the system you'll see in action in a minute is composed of three main components. So of course a Galaxy server that is capable of running the three types of IWC workflows that you've seen in action already.  And then a controlling machine on which you can run scripts powered by Planimo and BioBlend, so those two packages libraries to interact with the Galaxy API that you've learned about before in Simon's hands on. And these scripts we provide through GitHub repo. The link for it is shown down here. And so by running the scripts provided through this repo on this controlling machine, the controlling machine can instruct Galaxy to upload data from that file server, build collections automatically out of them, run the IWC workflows in an order. In an orchestrated way to do a complete SARSCOV2 genome analysis from raw data through variant calling ending in these batch wise reports ending consensus sequences as you've seen. And then the machine would also use the API to query the analysis states of these different runs on the Galaxy server and see whether new runs can be launched and whether like a variation workflow has finished on one of the datasets and can you can now start the reporting and consensus workflows on that batch of data. What's important here to notice that this controlling machine only has to deal with metadata and small pieces of code. There is never any sort of sequencing data transferred to this controlling machine, but the controlling machine only needs the information about those newly available files on that file server. But the whole transfer of big data of the sequencing data is happening between the file server and the Galaxy server. And all the heavy compute is also taking place on that Galaxy server, of course. So in fact, this controlling machine can be as low powered as a Raspberry Pi. So actually, our very first run of these scripts and of this whole system was actually using my Raspberry Pi at home to control everything. Now, of course, we found more professional solutions, but this was nice for development. So just illustrating that really, if you have a Galaxy server, if you have a file server, then setting up the controlling machine is really kind of trivial. And all you need is found in this repo down here. And just to stress this again, you can use this code to connect any Galaxy server that you have access to to any file server with sequencing data that that Galaxy can communicate with. So really giving you lots of options. It's still a young project. So if you find the following demo interesting, we would really love to have you try it out. For your own sequencing data and give us feedback also contribute to this repo. We would love to hear from you what you think about all of this. So let's explore how all this would work in practice. Then how you can use these GitHub repo and the bot scripts therein to actually analyze your own SARS-CoV-2 sequencing data using using any load. The local machine as the control machine from that previous abstract slide. So here I am on a Linux machine armed with just three things. My terminal and account on usegalaxy.eu for which I noted down the API key to access it from the command line. And a couple of links to sequencing data sets that I would like to have processed. So these links I have in the form of files on my local machine. So in here I have two files, two text files. Each of these holds a couple of links to data sets that I would like to retrieve from a server and analyze. So let's just look at one of them. So first one is this content. So it has one header line and then followed by many links to public data sets in that case from the EBI server, FTP server. And so how can I use our scripts and Galaxy to analyze those in an automated fashion? So I have two of these files. How can I process all this data? So first step is I git clone. So I use cloning functionality of git to get the code from this repo of the bot scripts onto my machine. And so I'm just going to clone this now into demo repo for now. So cloning it, it got pulled down from GitHub. Now I'm stepping into that newly created folder bot demo repo and take a look around to see what we got. So there are three directories in this downloaded repo. One with biobland scripts, which are lower level scripts that we for now do not need to access directly. Some documentation apparently, which is always good to have. And then of most interest for us right now, this job YAML templates folder. So this job YAML templates folder we can also explore. And then we see that there are sample files in there. And so these sample files are configuration sample files for scripts that would launch different workflows on different public servers. So you see that you have some .eu sample files and some .org sample files. So the .eu sample files would be scripts that are already partially preconfigured to work on usegalaxy.eu and the .org files on usegalaxy.org. You see that you have scripts for running the variation bot, scripts for running the reporting bot and scripts running the consensus bot. So those are bots that would launch these workflows that we've seen already used in the graphical user interface. Now just that we can launch these workflows from the command line. And so how exactly they are launched with which PLANIMO RUN parameters is determined by these variation job YAML files. And right now these are sample files. So depending on what we want to analyze, we now copy one of these sample files and start modifying it to become the real thing to execute. So the data I just showed you, which I would like to download from the ENA repository, is Oxford Nanopore Technology Sequenced Arctic data. So a reasonable thing to copy seems to be that variation job YAML.ont.eu sample file because we're working on the EU server with Oxford Nanopore Technology data. And so I'm copying this into that same folder but with the name shortened to just variation job YAML file. So this will be the job YAML file that the variation RUN script will pick up later and uses the job YAML file for its PLANIMO call. So we copy it there and now we can edit it in the new place. So I use Win for that, but of course you can use any text editor of your choice. And then this file. And now this is what's inside the file. So it configures the server to be used as HTTPS use Galaxy.eu. So that's fine. And then it lists a single end workflow ID. And this is supposed to be the ID of a variation ONT workflow that's accessible to my user account on usegalaxy.eu. So since I cannot be sure this is the correct ID and that I have access to this workflow, we will better get our own workflow on usegalaxy.eu and write down and use its ID in this file. So this is the first thing you would like to edit. So in general, these IDs are usually what you would be interested in changing. So let's go over to usegalaxy.eu and get a workflow. And you've seen this in the Graphical User Interface Workflows hands-on tutorial already. I just repeat these steps now to be sure we are using the right kind of workflow for this. So I'm going to the search form that lets me search on these GA4GH tool registry servers. I would like to get the workflow from Dockstore. And as you should all know by now is I'm using organization IWC workflow here as my search term. And then I can see all these intergalactic workflow commission maintained workflows that are available through Dockstore. And I find this one Oxford Nanopore Technology Arctic variant calling workflow. Three versions of it I download the latest one 0.2.1 into my user account. And now that I have that, I can record its ID. So I can, for example, view the workflow and then just copy this ID part here from the navigation bar from the address of this page. And then I insert that same ID over here instead of the one that's filled in here. And then the space is important here actually. So this is the new ID of my workflow that I would like to have launched by the bot. And then yeah, it lists a collection name which sounds reasonable. So we keep that for now. And another thing is that it lists a history for downloads here. So what these botscripts do is they will download those links in my two files with download links to so-called staging history. So they will first make sure they get all the data into a staging history on my usegalaxy.eu account. And once they got all the data, they will then build the collection in a new history and launch with Planimo Run the ONT workflow that this other ID here is referring to. So this history that will actually hold the analysis will be created automatically. But the data staging, I need an existing history ID for that to take place. So I need to create a new history in this account that will surface the download staging history. So I do this the usual way with that plus sign here.  The name doesn't matter really. And now I just need to get at that history ID of that history I just created. So this is easiest to get by going to user histories, which will list all the histories that you have in your account.  And then you can just right click that view for example and copy the link address of that history. And now this is supposed to go here instead of the ID of the template. So I'm pasting that in. Now I pasted more than just the ID, so just the numbers are the actual ID. So this is the ID of that new history I just set up on usegalaxy.eu where the downloads are supposed to end up in. Okay, so now this file lists an existing workflow ID pointing to an Oxford Nanopore variation workflow downloaded from Docstore. And it lists the ID of such a staging history. Okay, so with that we're already quite good. Now we need to let Galaxy know about these links files. So we need to upload them and we don't want to upload them into the staging area, but we want to upload them to a new history, a different one. So I create yet another one. And I call this history data links, for example. Again, the name doesn't matter much. You just should be able to find it again later on. And now into this history, I'm going to upload those two files with the links I've just shown you from the terminal before. So I'm going to upload data. I choose local files here and then select the ones I want. Okay, here they are. And I know these are simple text files listing URLs, one in each line. So I already said I declare these as text files and then I just upload them. So they appear here in the history, get uploaded now.  It expects this history to hold a collection of datasets, each listing the links to a batch of sequencing data. So it will only work if these files are part of a collection, but we know already how to do this. So I go to operations on multiple datasets, select those two and say for all selected, I want to build a dataset list. So this is the list. And now I can say I actually don't want to have the dot text suffix in here. So I delete it, but this is just cosmetic. It wouldn't affect the bot much. And then I'm saying I want to have these two datasets become part of a new collection with a new name. And now that name is actually not free for you to choose, but it must match the one that's listed in this file. So the bot will discover things only if they are in a collection and if that collection has the name listed here on line 10 of this template file. So metadata collection name should be ONT article links for the ONT bot. So we copy that name and put it over here. And now we will create a collection with the right name. And we can confirm that the links actually made it there. So yeah, this looks good. And this one also looks good. One of the today's sets has a few links more than the other. And now we have one more thing to set up. And this is this line here in the configuration file metadata history tag. This is a tag that must be present on such a metadata history to mark it as one. So the default is GX meta for Galaxy meta. And I mean, for me, it's fine. You can change that if you want to. But the important thing is that now you have to put such a tag onto this history. So here we go. We put that tag on the history. And now we are ready with our setup. So that's all we needed to do. We have created the variation job YAML file on our local system. We have added the correct IDs pointing to the workflow to use an O&T Oxford Nanopore Technology variation workflow, a staging history ID that exists in our account on usegalaxy.eu. And on the galaxy.eu site, we have created a collection with the right name in a history with the right history tag that has two batches of links to analyze. So all that's left to do at this point is to save our changed variation job YAML file to disk. And then if we inspect this repo again, we see that there are four of these run underscore something.sh shell scripts for you to be executed. And of course, the one interesting right now is this run variation.sh script, which will trigger a run of the variation workflow that's now configured in this variation job YAML file. So it will trigger a run of this O&T Oxford Nanopore Technology workflow because that's the ID of a workflow that we wrote into this variation job YAML file. And of course, in order to execute this workflow on my user account on usegalaxy.eu, this script will need my API key. So I already stored this API key in a shell variable API key. And I'm just now going to export this to make it accessible to the script. And that's all that's left to do. So now what we can do is we can just execute in the current directory this run variation script. And it will use plenty more run to launch the right workflow. Once it's downloaded the data into the data download staging history that we configured. So here we go. This script is now searching my account on usegalaxy.eu for suitable history and data set. And it just found one. So it's this data set ID in this history. So presumably this one with 28 lines or 27 lines of links to download. So let's look what happens. There are already 27 data sets queued for downloading in this staging area. So this part worked. Download is initiating. And now it depends on the ENA FTP server how fast this will go and whether it will go smoothly. Looks good so far. Just wait and see. An interesting case. So some of these downloads failed because of problems on the ENA FTP server side. And this is actually very good to illustrate the flexibility of the script. So the script will now make sure that all the data gets retrieved. And if some data sets fail, it will just retry those. So currently we have one, two, three, four failed data sets. And after short pause, those four will be retried within that same history. So that problem gets auto detected and by default one minute intervals. So they should soon appear back here. And in the meantime, what I can show you is that the bot now, here they are already queued again. The bot now did a tagging of this first batch of data. So if I look at the data set tags here, it has put a tag there bot downloading so that it marks this batch of data as currently being processed that another run of the same bot script wouldn't try to download the same data again. Now all the data in two attempts has finished downloading. And now what should happen is that script here in the terminal should notice this pretty soon. So there will soon be a message that the download completed. Yes, here it is. Data upload complete. What happened now is that the actual analysis history should be created and here it is for sure. So we now have this GX surveillance with that identifier of that batch of data. So that's taken over here from this data set in here. So that same name is now used as the name of this analysis history. The bot has put a GX variation tag on that history so that we know what it is. And it built a data set collection with these 27 items with the sample identifiers as their names. And now it will launch the Oxford Nanopore variation workflow on those. And the script here will terminate when the workflow is complete and it will then mark this data set as bot processed instead of bot downloading. So in fact, so you always need to refresh Galaxy to see changes in these tags. So that's a bit annoying, but that's how it is. So right here in the data set links history, if we go there again, you will see that now that this is running successfully downloaded, this tag has changed from bot downloading to bot processing. So that's the status of this data set at the moment. When it's finished, it will change again to bot processed. So just a couple of minutes later, that workflow run on usegalaxy.eu has succeeded. It has analyzed those 27 data sets up to final SNPF annotated variants as we've seen the hands-on tutorial for the workflow. So in here are my 27 VCF files with the variant calls for those 27 samples. And the script in the terminal has completed. So I'm back at my command line prompt. And now what I want to show you is that this setup that we had to do is really a one-time effort. So we have the second batch of data in the data links history inside this collection. So this one is processed now. It's still marked as processing because as I said, I would have to refresh Galaxy to refresh the tag display. So apart from this minor issue, so here's the bot processed tag that's now on this data set. The other one is still untagged. So if I run now this very same command again, the dot run variation dot SH, the script will automatically note that this first data set has been processed already. It will also see that there is a previous history which is completed. And actually if it wasn't, this script would not run in order not to overwhelm the server with too many variation jobs. But that's a configurable parameter in the jobYAML file. Now it found a new data set to work on. And this is supposedly this. So it should now upload 45 new data sets. And if we go here back to the history list, we see that 31 are the ones that we used before, including the four retries. And now that amounts to 45 new data sets that are currently staged for download. And these are the new ones. Again, any download failures will be automatically reattempted by that script just like before. Though it looks quite good so far. Let's refresh to see how the progress is. 18 are still downloading. And once they are downloaded, this will automatically create a new GX surveillance history with the name of this new batch and do just the same as for this batch. And what you can see now actually for the one that's already completed is that the bot has put two additional tags on that history. And that is a bot go consensus tag and a bot go report tag. And so if we now used one of the other scripts run consensus.sh or run reporting.sh. Of course, we would need to configure the corresponding job yaml files first to use the correct workflow on my user account. But if we did so, then either one of these two scripts would detect this tag on the finished GX variation history and would pick up this history as input for the next workflow run. So all this is completely automated and all it takes you is to run these run.something.sh scripts. So of course, if you're working in a place with a real high throughput of sequencing datasets, then even this manual execution of these four different run.something.sh scripts will be quite amount to quite a bit of effort. You do not want to always open a terminal, find that repo, run the script, wait until it finishes, run the next one and so on. So this should be further automated and it's quite easy to do so. These are just shell scripts. So you can just configure any scheduling system on your platform of your choice to do so. You could, for example, set up simple cron jobs to trigger automated runs of these scripts in regular time intervals. What we decided to do on usegalaxy.eu for our genome surveillance projects of different European countries is actually we're using a Jenkins server that we're also using for other regular tasks on usegalaxy.eu. And we just configured lots of scheduled projects on that server for running the different workflows through these run.sh scripts. So we have one for variation. For example, let's go in there and then if you look at how that's configured, it's actually nothing special. It just automatically does what we've seen on the command line in the terminal now. So this project will run every two hours on usegalaxy.eu. And anytime it runs, it will simply clone with git clone this scripts repo, just like we did in the terminal now. It will install the scripts requirements here with Python's package manager pip. So that will pull in planimo and biobland as the requirements. And then it will modify using a simple set command the IDs of the workflows that are found in the, in this case, onteeu.sample file on the fly and write them out to the final variation job YAML file. So again, what we did manually in the text editor will happen automated in the script. And then we'll simply export the API key and run the variation.sh script just as we did in the terminal now. And this will happen every two hours and analyze a new batch of input data on usegalaxy.eu in a special bot processing account that we created for this purpose. There are other similar configured projects then for example for reporting. And the only difference there is will clone the same repository will also run every two hours. But the difference is that it will simply run the reporting.sh script. And for any finished variation history in that bot account that carries a corresponding bot go report tag on the history, the script will pick it up and just run the reporting workflow on it. Same for consensus building. And then we even have an automated workflow for exporting that data onto an FTP server. So this is how this is set up. And then if you look into the bot account you see what it does. It just creates many of those histories or tagged correspondingly. Now we can use search by tags here to look for example just for gx variation histories. And we can see that there are a lot of them. So there's like here completely processed one that has now a consensus bot OK tag on it, a report bot OK tag on it. So this automated run of these shell scripts further simplifies the whole task of analyzing lots of data reliably with your Galaxy server or with usegalaxy.eu. And the only thing that's now left to do to get your data analyzed is to put it in some discoverable gx meta tagged history as we've seen. So on the spot account we have a couple of them. So I can actually just search for gx meta to show you what kind of things we have there. We have for example one current meta history for Greek data and one for Irish data. If you go inside there then you can see that I'm simply uploading not these small two batches things like I showed you on the terminal. But we actually occasionally upload a whole new chunk of in a deposited data. So these are now 74 batches of FTP links each with those links inside. And then as before the bot will just every two hours when it runs automatically through Jenkins. It will take the next one of the 74 batches analyze it and only when all 74 batches are processed. We simply get new data from the DNA uploaded into a new collection of new FTP links and then continue processing. So this was my demo of how we deployed the system. You see schematically again here on usegalaxy.eu and kind of look behind the scenes if you will. But we are not only using the system on usegalaxy.eu but on several used galaxy.star instances at the moment. So this system has currently been deployed on usegalaxy.eu but also on usegalaxy.org. And it's used also on the Spanish COVID-19 platform COVID-19 usegalaxy.es. On all three platforms for the analysis of national genome surveillance data from across Europe. So we are processing data from the UK. So from the CogUK initiative from Estonia from Greece and also from Ireland. The source of this data is mostly Illumina patent sequenced Arctic amplified data. But we also have used it to analyze Oxford Nanopore Arctic amplified data as you've seen today. And in total we've processed so far more than 150,000 samples. So for this national genome surveillance effort with Galaxy we picked data from these four countries. The UK, Estonia, Greece and Ireland because they are doing a good job at depositing the data in public databases. So not just result files, but they're all sequencing data and they're uploading those to the European Neucleotide Archive. Providing metadata about the samples like collection dates of these samples and which lab sequenced the samples at which time. And so we are exclusively for this national level surveillance. We are exclusively taking data from the European Neucleotide Archive's FTP server at the moment. And then analyzing it on the Galaxy platforms and depositing all key results files that come out of these three Galaxy workflow types. On to an FTP server that's provided to us by the Barcelona Supercomputing Center and the CRG, the institution that runs also the viral beacon project that you hear more about tomorrow. And in general tomorrow we'll spend on looking at that ecosystem of projects we're collaborating with to then bring that data that Galaxy produces to people, so that big data analysts and virologists, policy makers can actually explore the data, look at it, do further analysis with it or just create telling statistical figures out of it. If you're thinking a bit smaller scale, so if you're not running a national genome surveillance project, but you just have occasionally interesting data sets that you would like us to process with our compute and our standardized pipelines. We have an interesting additional project, so a dedicated GitHub repo to which you can make pull requests with files with your URLs to your data sets. So as long as these files live somewhere that our public Galaxy instances have access to, we can merge these pull requests and then this data will end up in the same processing pipeline as these big national genome surveillance projects. And you can later have access to the resulting Galaxy histories on one of our servers. So this is currently this request based analysis available only on use Galaxy EU, but can also in principle be deployed to any other public Galaxy instance. So just illustrating again the flexibility of this whole system. And yeah, the key message is you can use this right now on usegalaxy.eu, usegalaxy.org and presumably other Galaxy instances in the future, but it's also ready to be deployed and you saw how easy that can be on your local instance too. So really think about this possibility. You're getting a fully functional, very scalable system for free and we are happy to answer questions if you're interested in that.


What's up everybody Jason here for jazzy's caseworks comm this fills up old sake Pikachu number eight We're guaranteed at least one team Hornets plus more. So again, we have a 11 spots So we're gonna sell 11 spots We sold them we'll take the 11 customer names and randomize them only and then we'll match them up with this list below number one gets the Hornets alone and then two through 11 get two teams and again all of them actually are pretty well tiered you have the Mavericks and Nets Nuggets Cavs, Spurs Nicks, Sun Sixers, Pacers Raptors, Thunder Wizards, Celtics Blazers, Bulls Pistons All of even down here Hawks and Kings with the Tyrese Halliburton opportunity down there and Heat and Jazz so pretty strong guys Again will did buy the three spots straight up Nico is the only one that got in from the pack filler that wasn't will So there you go. Good luck to both of you guys of course.  So that's the cool thing So let's roll the dice and we got ourselves a two and a six eight times. Good luck one two three four five six seven eight Wow, no way stop Congratulations, Nico. I can't believe this even happened. I cannot believe it two and a six eight times Wow You're at the top all the way down to will Jesus. That is ridiculous Go go get a lottery ticket or something All right Well, you have the Hornets no Mac congratulations And then will you got the rest of the teams here including the Mavericks including the Cavs the Nicks the Sixers the Wizards The Kings Pistons Bulls Heat all of those teams there So this one locks Pikachu number eight and coming up next of course is Pikachu number eight Jasper's case race calm


Welcome to the session. In this session, we will discuss a question which says that with time in r's h, the distance travelled d in miles by two cars a and b are given in the form of linear functions. Distance travelled by car a is given by d is equal to 18 h and distance travelled by car b is given graphically determine which car is moving fast. Now, let us start with the solution of the given question. Now, in this question, we are given relation between time in r's and distance travelled in miles of the two cars that in different representation. For car a, the relation is represented as graphically and for car b, the relation is given graphically and we have to determine that which car is moving fast. Now, we know that speed is equal to distance travelled upon time taken or you can say speed is distance travelled per hour. So, unit height is given by slope of two linear functions. Here we will compare the two given linear functions with respect to their slopes. Now, in function 1, we are given a linear function showing a relation between m distance travelled d, the equation d is equal to 18 h is of the form y is equal to mx whose graph is a straight line passing through a region is equal to 18. It means travelling one unit is equal to one hour. Now, let us take c dash which lie on the slide. Now, we know that slope is equal to rise. Now, we know that on horizontal axis, one unit is equal to one hour run is equal to a vertical axis. One unit is equal to 10 h is equal to 1, 2 and 3 minutes. It should be equal to, so slope is equal to 30 which is equal to that car b is travelling at the rate is travelling at the rate of 80. And the rate of 50 is moving. The slope using coordinates of c and c dash has coordinates of c are 30 and coordinates slope is equal to upon change in m 30. This is equal to 30 upon 2 which is equal to equation of the given question. That's all for this session. Hope you like and enjoy the session.


Attention West Colfax residents. This is a community notification of a new sexually violent predator in your area. Please stay tuned to the following short program for more information. Hi I'm technician Ron Hackett with the Denver Police Department. The sex offender registration and compliance unit at DPD is responsible for the registration monitoring and tracking of all registered sex offenders and sexually violent predators who live in the city and county of Denver. Here's a brief history of sex offender legislation in Colorado. Our state laws trickle down from federal government mandates. In 1994 we had the Jacob Wetterling Act which mandated that states would establish a sex offender list. Megan's law of 1996 said that the public would have access to those sex offender registration lists. The Pam Litchner Act of 1996 stated that some offenders might have to have lifetime registrations and the Adam Walsh Act of 2006 unified sex offender laws across the country. In Colorado the legislature has determined that sexually violent predators by definition pose a higher risk to the community at large and therefore mandated that upon their release from the Department of Corrections the community must be notified. Sex offender notification in Colorado happens in two ways. The first is passive and ongoing through the sex offender registration process which is a list maintained by local police departments. The second way is active via community notification for those offenders determined to be sexually violent predators by the courts or by the parole board. Most sex offenders in Colorado are supervised by the criminal justice system in our communities. Most sex offenders engage in crossover behavior which means they may have been arrested for one type of crime but be apt to commit another.  There is no typical sex offender but all tend to be deceptive, manipulative, and secretive. 80 to 93 percent of sex offenses are committed by someone known to the victim. Sexual deviancy begins in mid to late adolescence. Sex offenses are not impulsive.  The community has a vested interest in helping offenders to be successfully managed in the community. Sex offenders have the same need for housing and employment as any other citizen. Any citizen who uses sex offender information to harass, threaten, or intimidate an offender will be subject to criminal prosecution. There are approximately 16,500 registered sex offenders in the state of Colorado. About 65 percent of convicted sex offenders are placed in the community on probation. The remainder are in the Department of Corrections or Community Corrections. Offenders may be caught for one type of offense but be at a high risk to commit another type. Crime of conviction is only one indicator of risk.  The offender's residence must be verified quarterly by the Denver Police Department. The full sex offender registration list is available by calling the Denver Police Department Identification Bureau at<PHONE_NUMBER>. Convicted felons and those with multiple convictions are posted online at denvergov.org slash police.   Now, here's a look at the newest sexually violent predator living in Denver. Here's an overview of the registered sex offenders currently living in Denver. There are 2,400 total living within city limits. In Denver Police District 1, there are 295. Precinct 122 has 73 registered sex offenders. Of those, 38 have felony convictions and 35 have misdemeanor convictions. Raymond Warren Scott is a sexually violent predator currently living in Denver. He's 57 years old and was born on March 5th, 1960.  He's currently living at 1362 Wolf Street in the West Colfax neighborhood of Denver. Schools located within one mile of this offender include Yeshiva Torres Hyam at 1555 North Stewart Street, Beth Jacob High School at 5100 West 14th Avenue, Colfax Elementary at 1526 North Tennyson Street, Stripe Prep Lake Middle School at 1820 North Lowell Boulevard, Cowell Elementary at 4540 West 10th Avenue, Cheltenham Elementary at 1580 North Julian Street. Parks located within one mile of this offender include Sloan's Lake Park, Martinez Park, Sanchez Park, Lakewood Dry Gulch Park. Bus routes located within one mile of this offender include Route 6 West Colfax Avenue, routes 50 and 51 West Colfax Sheridan Boulevard, Route 16 and 16L West Colfax Sheridan Boulevard. A brief history of charges against this offender attempted second-degree sexual assault. He's currently on parole and registered with the Denver Police Department on November 13, 2017 to 1362 Wolf Street in the West Colfax neighborhood of Denver. Past charges against this offender include first-degree sexual assault, disorderly conduct, traffic offenses, trespassing. Raymond Warren Scott has been determined a sexually violent predator after meeting the following criteria. Criteria 1 age 18 or older on the date of the offense or under 18 and tried as an adult. The offender was age 40 at the time of the offense. Criteria 2 the crime must have been committed on or after July 1, 1997 and convicted on or after July 1, 1999.  The offender was convicted on March 13, 2000 for attempted second-degree sexual assault. Criteria 3 the relationship to the victim was one of the following. Victim was a stranger to the offender or the offender established or promoted a relationship with the victim primarily for the purpose of sexual victimization. The victim was a 32 year old female. The offender was known to the victim. Criteria 4 positive results are the passing of a risk assessment instrument administered by probation parole staff and a qualified treatment evaluator. Positive results include an assessment for the presence of a mental abnormality, a level of denial regarding the offense, treatment appropriateness and motivation, presence of sexual deviant interests. The offender was evaluated by the Colorado State Board of Parole with positive results, determining him to be a sexually violent predator.


That's a gain of 3 tenths of 1% in the Dow Industries as well as the composite and 4 tenths of 1% in the S&P 500. The whole contract down at $21 trading $12.95, now Gold got hit hard, 400,000 contracts down there will come into a Friday so that swing low is kind of sticking out here folks, we'll see whether that's going to get whacked tomorrow morning or in fact they break right through it because you're right next to it right now. We didn't hit it out here today but we basically laid right next to it. We got down to $13.93, $12.93 rather, $12.87 is the number and I suspect we're going to at least try to get into that number tomorrow. Now what has happened is that if you take a look at the volume characteristic, it's a big volume that being said what you are going into is the large volume from March 1st. Also if you take a look at the GLD that characteristic looks pretty good actually. We came down to $11.4 million, that last low was established out there at $16.4. We're right into it though so and into it coming on a Thursday into a Friday is basically saying your probability gets much higher that you're going to get down and test that level. Silver, Silver's a problem, Silver broke a B point today, has the volume on the break and Silver looks like okay you're going to $14.35, right now you're at $14.98. If that's the case, what we're going to see out here tomorrow inside the currency markets inside the Euro as well as the pound as we'll see those continue into lower price and what that is all about and will be all about is that Theresa May is going to try to gamble one last ditch vote. That one last ditch vote is going to be tomorrow and if she can't get this through, bottom line is that they're going to do a hard Brexit on April 12th or they're going to come in for a huge extension and we're talking about like an extension they're talking about like between the year, year and a half and they're going to be a lot of very disappointed people in the UK, that's for sure. Recap out here, Dow Industries finished up $91, Nasdaq up $25, S&Ps up $9.5, stay right there folks, come right back.


What comes in nursing school explained in this video on how to insert a nasogastric tube into a patient. After checking the orders and making sure that we confirm everything that we need in order to make sure that the procedure can be performed safely, we need to also make sure that we educate and inform our patient about the procedures and the details. Now this is an uncomfortable procedure and sometimes patients they vomit during the procedure so the better you prepare a patient for all the eventualities and what to expect the better and the smoother the insertion will go. I'll tell you that as a new nurse I had a lot of trouble inserting nasogastric tubes into patients when I worked in the emergency department but a senior experienced nurse told me that the key to this is to have the patient put their chin to their chest once the tube is in the posterior fairings because then you close off the epiglottis and then the tube just slides down when you have them swallow the water. But first things first, so first of all we need to make sure that we have all the equipment that we need to do this. So first of all we need our nasogastric tube. We also will need a stethoscope to confirm placement after it's been inserted. We need a cup of water with a straw that's very important the straw because the patient won't be able to tilt the head back to drink water in an attempt to swallow the tube and then a piece of tape as well as a piston or catheter tip syringe, an MSS basin and an extra towel just in case the patient throws up so that we are prepared for all the eventualities. And the way that I usually explain the procedure to the patient is this is then can be an uncomfortable procedure but the most important part is that you don't swap my hand away because that's a reaction that some patients will have and they will attempt to to move your hand away when it becomes uncomfortable when you when the tube hits the back of their throat. So I'll just tell them right away in case it becomes too uncomfortable or unbearable or you need a moment to breathe just raise your hand and I'll stop right there but I'm not going to let the go of the tube because I don't want to jeopardize any progress that I've made with the tube because if the patient coughs or starts to vomit or gags they can push that tube right out and any progress that we've made will be not happening anymore. So once I've told the patient about this then I get my equipment then we can start the procedure and then depending for the reason of the reason for the anti-tube insertion if this is for example for a bowel obstruction and the patient will need suctioning then we certainly need to also make sure that we have the wall suction set up at the correct setting and have that tubing ready to go so that we can hook it up once the ng-tube is inserted. Okay so this is a clean procedure not a sterile procedure so I'm going to wash my hands and don my gloves and in this case I've already explained the procedure to my patient so after I don my gloves I will assess their nears first because it is important to know the anatomy and if there are any abnormalities that I could expect so questions to ask would be have you ever had a nasal fracture or a deviated septum or any kind of nasal surgery and if they say yes then you have to be extra careful and notified of physician and then maybe they want to have an ENT or somebody else insert the ng-tube for safety reasons but if that is not the case then we want to make sure we have a patent there one of them might be more patent than the other the simplest way to do this is to include one of the patient's nostrils and ask them to exhale and then you can see or you can actually hear if there's a patency and airflow and then we do the same thing on the other side exhale okay and then we can know that the other thing you could do is use a sterile q-tip and then sort it gently into the patient's nostril kind of like you would do when you correct a nasopharyngeal swab for for a respiratory secretion panel or swab for any kind of testing and to see how patent the nostril is once you've determined the patency of the nostril we can go ahead and start with the procedure so I always place a towel right here on the patient's chest you want to make sure that you sit them up as much as possible but depending on why they need it and what's going on with their abdomen they might only be able to tolerate a certain degree of elevation of the head of the bed but the minimum you should aim for would be 45 degrees otherwise it's going to be more difficult to insert this ng-tube the other thing that I need to do once I have inserted the ng-tube I'm going to have to secure it and some facilities use some newer devices that that have like a little plastic clip that can go around the tube and the sticker that goes to the patient's nose but the good old-fashioned way is to just use some tape and in this case you would use transport tape and you would get about I guess this is about four inches or so strip and then you want to tear the strip for a small portion and eventually the strip that's still intact that's not torn will go on the patient's nose and then these two ends will twirl around the tube to keep it in place so I'll just make sure that I have this strip of paper ready to go here and then I will explain the procedure and I will say once you're going to fill the tube in the back of your throat then I'm going to ask you to put your chin to your chest and at the same time drink the water with the straw of course one more thing that's important to check is the patient able to swallow and is that okay or are they completely in PO but for the most part once we get the tube down there any water that the patient has swallowed we can suction that back out if that is the purpose of the tube so so we'll instruct the patient chin to the chest and at the same time drink the water and then as the patient is drinking the water the epiglottis will open and then we can we can pass the tube as the patient swallows so with every swallow we'll be able to pass the tube okay I'll be ready here with my stethoscope around my neck I have my emesis space in here that I'll tell the patient to hold with their left hand preferably that's also the hand that I'll instruct them to hold up in case they need me to stop for whatever reason if they need to catch their breath and then I will open up to many times many times you can just use the wrapper the inside wrapper as the source for your lubrication so you can just I'm just going to squirt my lubricating jelly on here and actually before they come to come in different sizes also this particular one is a protein fridge sealant some to depending on why the patient needs it is it for suctioning is it for feeding how long is the tube expected to stay in will depend on the size of to that you that you select and then the tube has these centimeter markings on here which will allow us to know the depth of the tube once it is in there but of course first we'll have to measure it another thing that I always like to go over are these two parts so we have this blue part and then we have this other part at the end of the tube here with this adapter and so many times what this adapter is needed for if you would hope this up to suction the suction tubing connects right here so this is basically an adapter otherwise the suction tubing won't fit on this end of the tube another thing here blue just think blue equals air and that is the airport or the air vent of the ng-tube and the purpose of it is once the tube is in the patient stomach and we put it to suction it's going to move and so it will it there's a possibility that the tube might suction itself against the wall of the stomach but because we have the air vent there is not really a vacuum in the stomach otherwise there would be but because we have that vacuum there it allows the air to get in there not a vacuum to occur and so if we had if even if we had a continuous or intermittent suction even if the tube suction itself against the wall of the stomach we would it would still eventually become free again because of the air vent and the concern here is that if the tube suction itself against the wall of the stomach and it does that for a prolonged period of time it could create an ulcer a pressure ulcer in this case a more of a suction ulcer and it could cause a GI bleed so we want to be extra careful with that and so now that I have got the tube ready I have a lubricating jelly here I will put the cup in my patient's left hand and one more thing I am right-handed so I'm going to be standing on the patient's right side because I'm going to use my right hand for the insertion of the tube so next I need to make sure that I know the how much length of the tube I need and so I'm going to measure from the patient's the tip of the nose through the earlobe and then down to the xiphoid process and remember the xiphoid process is the last piece of a bono cartilage in your chest so in this case in my case this comes out to be 48 centimeters you can either mark it with a sharpie which is what I prefer or you can put a piece of tape there the reason I don't like the piece of tape is because sometimes it's hard to take it off after the fact and I like to use a different sharpie a different color because it's easier to see on the black markings so now we are ready to go so now that I know the length of my tube I'm going to lubricate it and I want to make sure I lubricate at least the first 10 centimeters or so of the tube to make this easier for the patient okay sir I'm going to start the insertion of your tube now once I hit the back of the throat we're going to take a quick break and then once you feel the tube in the back of the throat and I instruct you to do so please drink the water and put your chin all the way to the chest so here we go so I'm going to start inserting the tube by aiming more back rather than up some people think you go up but it really the the nasal bearings opens up more to worse like a straight line rather than out so now I'm hitting resistance okay sir now I'm hitting resistance what I need you to do now please pick up the cup of the straw and put your chin all the way to the chest so I'm going to have him do that and then while he drinks the water I'm going to continue inserting that tube and he might call for gag and if he raises his hand I'll just stop right here but I will keep my hand on the tube because I let go if I let go it might slide back out so I'm going to the patient is coughing I'm going to give him a some time to breathe and then once he's okay again now that I'm past the epic goddess I can actually have him bring the chin back up and I just continue inserting the tube until I get to my blue marker right there at the tip of the nose which is where I started where I marked it now that that's been done I'm going to take the tape that I will be going to use for securement and the bigger part of the tape that's still together I'm going to take on his nose and then I'm going to use the two ends that I have here to twirl around the tube to secure it make sure that the marking that I have the depth of the tube is still where it needs to go now that I've secured that up definitely make sure my patient is okay and then depending on the order I'm either going to hook the end up to suctioning the other thing that I can do is I can hook up my catheter tip syringe to the end of the tube but I have to take this adapter out and then aspirate the fluid and this is one of the verification methods that could be used to measure to see if we're in the right spot and then the fluid that I have aspirated goes on a pH card where it reads the stomach acid and I know then I'm in the right spot by the pH of the stomach the other two verification methods are either an air bolus which is where I fill my syringe with air and typically about 30 mls are okay I put the end of the syringe on the tube and then I take my catheter scope and I listen right over the patient's stomach and as I am inserting the air bolus so pushing that air in I'm going to hear that gurgling in the patient's stomach if the tube were in the lungs or had gone through down to the trachea then I wouldn't hear the gurgling because the lungs are supposed to have air and it's just gonna sound like a deeper breath but in this case the gurgling is very very distinct and once you've heard it you will know that that's what it is the third verification method is a chest x-ray which is the most reliable method but also make sure that you know at your facility what are the method well what is the policy to do a verification of the NG2 placement after the insertion so if this NG2 was just let's say for feeding then I would put the cap on here and then hook it or use a safety pin to secure it to the patient's gown but this can be a little bit iffy because you know the patient might pull on it or somebody might change the gown what I like to do is take a washcloth that's different from this towel or a small towel and just kind of wrap it up because sometimes gastric juices come up as the patient coughs or sneezes and that way the end is contained and we won't have a big mess with stomach contents and that will take care of the NG2 insertion of course will take care of our patient and document all the findings that we had particularly how deep or how far the tube went in the length of it how the patient tolerated the procedure as always and then any kind of verification method that we use such as the gastric acid aspiration or a chest x-ray and then we can just refer to the chest x-ray or the air bolus depending on actually again the facility that you're working at so thank you for watching this video on nursing school explain on the insertion of a nasogastric tube please also watch my other videos in the skills playlist that go over other important basic nursing skills give me a thumbs up if you've enjoyed the video subscribe to my channel see you soon right here on nursing school explained


NETKRH is a cluster randomized control trial with a step-twitch design involving 33 outpatient general practitioner, GP, offices in a rural area in northeast Germany. The aim of this study is to evaluate the effectiveness of providing teleneurologic consultations to patients with neurologic symptoms through a face-to-face video conferencing system with a neurologic expert at a university hospital. The primary outcome measure is the proportion of neurologic problems being solved at the GPS office. Secondary outcomes include hospital stays and days, time until neurologic specialist appointments and diagnostics, patient health status and quality of life, outpatient and inpatient referrals, and cost-effectiveness. Additionally, a concurrent observational study, together with a process, implementation, and health economic evaluation, will be conducted. This study has the potential to provide valuable insights into the feasibility and effectiveness of teleneurologic consultations in rural areas. This article was authored by Kerstin Wainwright, Imkmaier, Anna S. Oliveira Goncalves, and others. We are article.tv, links in the description below.


The Speaker House of Representatives Honourable Femig Bajabiamila has assured Nigerians that the Parliament will address the issues of Electoral Act Amendment Bill upon resumption in 2022. Bajabiamila gave the assurance on Tuesday in his 2021 End of Year speech at Plenary. It was shortly after he read President Bohari's communication to the House on Electoral Act. President Bohari and his communication cited insecurity, manipulation of election and molestation among others, as a reasons for withholding assent to the Electoral Bill. The cost of direct primaries across the 8,809 words across the length and breadth of the country will lead to a significant spike in the cost of conducting primary elections by parties, as well as increase in the cost of monitoring such elections by INEC. Who has to deploy monitors across these words each time a party is to conduct direct primaries for the presidential, the territorial and legislative posts? The addition of these costs with the already huge cost of conducting general elections will inevitably lead to huge financial burden on both the political parties, INEC and the economy in general at the time of dwindling revenues. He however showed that the reasons for declining assent to the bill will be addressed and Nigerians will be given a credible electoral law when the House reconvins after the Christmas break. This year, despite the differences of opinions, all of us in the House of Representatives and indeed the entire National Assembly works to pass the Electoral Act Amendment Bill. We included in that bill provisions we hoped will significantly enhance the conduct of our national elections and improve public confidence in our electoral outcomes. As it is now, that bill has not received presidential assent and it falls to parliament to decide the best way forward. When we return in the new year, we will resume our efforts to reform the electoral system in our country and we will do it together. That is what the Nigerian people expect of us and we will do our duty for God and country.


Welcome to the Jenkins documentation office hours. This is the December 22nd U.S.E.U. edition. Today, we have myself, Mark Waite, and Bruno Verrachton joining us. So quick note, just as a side, next week we will not have Jenkins documentation office hours. We'll be out of office. Most people will be busy with holidays and whatnot. So next week, we won't be anything just as a heads up. Aside from that, we have some action items. Just a quick note on the pipeline Docker plugin and what that means for documentation. And for the most part, just looking at the 2020 to recap newsletter topics and ideas and then a couple of pull requests to take a look at and just make a note of, considering that these sort of things are gonna be really important when we get back into the new year and just get them forward for Jenkins. And Mark's adding a note regarding the Jenkins backboard. So we'll get to that at the end as well. Does everyone have anything else they'd like to add or anything I missed? All right then. So first action item here on the list is right now what I'm doing is going through the Jenkins JIRA and going through all the website certificates specifically. Alex Bright has submitted a ticket to the help desk to make sure that this is taken care of and these issues are cleaned up, closed if we don't need them or migrated if we should talk about them further. So I'm going through that list right now. I've gotten to about 60 to 70. There's about a hundred or so altogether. So a lot of them have been able to get closed out because we've just gotten the documentation now. So yeah, that'll be again, something that gets finished up in the next couple of months probably sooner than that and we'll be discussing those really valid and potential additions as we go. Next thing on the action items is archiving the doc mailing list. This will be something that gets started in January. Mark and I will be discussing what we need to do to get to the starting point and what needs to happen after that. So more information to come, but just say no. And then I wanted to highlight a couple of blog posts that we've published recently. One is John Mark Messon's blog post for the Google Summer of Code mentorship. It just goes really in depth on what mentorship means, what mentorship looks like in Google Summer of Code, the expectations, what opportunities they have, et cetera, et cetera. But Google Summer of Code is super in progress where the Call for Papers is coming up in just about two weeks. I think January 5th is the Call for Papers deadline. So we're in full swing, looking forward to Google Summer of Code right now. So if you have any interest, you wanna chat ideas, topics, how you can mentor, how you can participate, whatever have you. You have plenty of resources and blog post is a great way to start. The other blog post that I wanted to call out and highlight here is the recent post from Basil Crow. He wrote a wonderful and very detailed blog post about the new baseline requirement for a Jenkins plugin development, which is Java 11. This is a more recent update. The Java 11 requirement has been part of Jenkins itself for a few months now, but the POM itself was upgraded to utilize Java 11. So this is something that we wanna make sure is addressed and highlighted. So folks are not getting lost or confused on what needs to happen next. Anything else on the action items or good to go? Cool, all right. Anything for me. All right then. Next small note, just the pipeline Docker plugin. Maybe we're looking at deprecation there. This is gonna have far reaching impacts beyond just Jenkins. So would you need to figure out and really do some research and find out what the impact will be for Jenkins, for other companies, for other usage, platforms, et cetera, et cetera. This is not something that can just be done without anyone noticing. So Mark is gonna work with Darren Pope, Damian, DePortal and myself. We're gonna figure out what needs to happen and then once we know what kind of impacts we'll have, we'll start updating documentation and making the necessary modifications. But again, that's not something that's gonna happen in the next week or anything. So new year. And then again, we have our December, the December newsletter is actually gonna be a 2022 recap newsletter for us. So when we post it in January, most likely in the first week, we're gonna be looking back at all the wonderful accomplishments we've had over the last year. For me, I've only been here part of Jenkins for about eight months or so. And even in my eight months, I know that there's more than I can remember. And obviously Jenkins has existed before that. So tons to list and go over and share and highlight and celebrate. We have been able to create this list previously and we're still continuing to use this as an outline and kind of just a marker for where we should be and what we should be including. So we've got themes like platform modernization, development acceleration, website improvements. So for Jenkins.io, localization and simplification or outreach and advocacy, security, infrastructure and sponsors. And we wanna make sure that we celebrate and highlight as much as we can with this. Bruno and Alyssa are working on the newsletter itself as far as putting that into phone requests and getting that published. And every SIG leader is working on their own updates to include as much as possible. So sorry to interrupt you, Kevin. Go for it. So the source of truth keeps being the same document we've been using for the monthly newsletter. It's not that Jenkins Docs office hours document. Am I right? I'm keeping. Yeah, okay. Thank you. For the Jenkins newsletter, we're still gonna be using the draft template that Alyssa created and set up and has shared with everyone. So that's still the one source of truth for all of this. This is just the list that we've been working on to make sure that if anyone forgets one of the many, many, many, many, many things that have happened this year, we can help fill in the blank a little bit. I'm sure stuff like Java 11 and 17 and a lot of these were very, very large things that I'm sure won't go missing. But we've also had other things happen. Like the development acceleration is a lot of behind the scenes stuff and work that is not necessarily seen but felt. So making sure we call and highlight that stuff out is really important. We have a lot of great developers and maintainers in Jenkins. So these are really things where we wanna make sure everyone gets a chance to be recognized even if their name's not attached to it. Everyone knows what they've been working on. So yeah. And then we might end up moving some of these things like the localization simplification maybe switched over to development acceleration or platform modernization or website improvement. It can be, some of these are not so hard and fast set in stone. I had a few things about the elections and we moved everything into outreach and advocacy because it just makes sense. And then things like the community site which I mean for me now it seems like it's just always been the case but I realized that that's new. So these are all things that we wanna make sure people are aware of. Community site's really nice and has a wonderful area for everyone to discuss Jenkins and any capacity they wish. That's something we should really highlight and celebrate and make people aware of. I'm sure everyone's using it but something so simple is having a large impact and I always love making sure that that sort of scale is called out. When can I consider that the content of the newsletter is frozen, ready to publish? I assume not until January 1. Oh, okay. Yeah, this is all, be still. Yeah, my assumption is it'll be at least January 1. Now I hope to start my writing today on my pieces. The governance board topic and some of the items that are in the early list, the platform modernization things, I'm planning to do most of the writing, a bunch of writing there and development acceleration. And I may in my past role as Docs Officer and as a Google Summer of Code mentor do things on the website improvements because of how personally grateful I am to Veehan Thora for what he did there. So that piece, but that will need at least several days. So if it's okay with you, Bruno, that it waits until January 1, we don't intend to publish until after the first of the year, but if you need more lead time, we could set ourselves an earlier than January 1 date if that's really needed. No, no, that's perfect with me. I'm not in a hurry. So that's fine, thank you. And sorry, I had another thing in mind. I saw earlier today, because you were speaking about GSOC 2023, that two people wanted to become mentors for this year, two more people, so that's a good thing for us. That's awesome. I hadn't seen that, I must admit that. Thank you very much for sharing that, Bruno. That's awesome. The more mentors, the better, obviously. We can reach more, help more people, work with more people, the more resources we actually have. And it's no small commitment. We absolutely appreciate every mentor taking on the time and effort and work that comes along with it, but that's amazing. I'm so happy to hear more and more people are getting interested. Thank you. And as far as my update goes, I'm looking right now, I'm doing a lot. The documentation update is not listed here, but my idea right now is just to highlight and share how much contributions and changes have happened. I'm working right now with the community stats to just kind of recap how any blood posts have been created, how many authors have participated in the blog, the number of pull requests we've gotten merged over the last year, which is almost 900, that stuff like that. So I'm working on making sure that we're highlighting the community and their documentation contributions as well. So yeah, lots of good stuff to come. And yeah, like I said, I'm also writing up little things for a lot of these items, just in case, like I said, the gap is there. So we'll have something, even if I'm not the most well versed on something, I have enough in me to go and figure it out. So yeah. And then Wattic and others will be working on the security stuff. And so we'll just keep checking on that and we'll get that taken care of. And yeah, I'm most likely somewhere around January 3rd to the 5th, I would imagine. So anything else on the December newsletter? Or... Nope. Okay. Okay. No worries. No, thank you so much, Bruno. And then, so just to, as we're reaching the bottom of the agenda here, the second to last item is pull requests of note. These are just a couple of items that are coming up and that have been submitted that we want to bring to everyone's attention. First and foremost, the 2.375.2 LTS release, which is going to be January 11th. I've gotten the change login upgrade guide created that pull request is submitted and open for feedback. So if anyone wants to take a look and review, I appreciate that. And thank you in advance. And then the second item here is the web components for Jenkins.io. This is something that Gavin Mogan has been working on for some time now and has made a lot of headway and we've got the header and footer already kind of working in the plug-in site. And this is just adding more Jenkins.io components in addition, removing a bunch of stuff that we don't need anymore. So making the page load lighter, we get the consistency of looking feel across multiple sites, regardless of whether or not their plugins, plugins, whatever have you, they can all use the web components so that there's unity across. So this is fantastic. We do want to get some more review and testing on this just to see how everything looks and works, but this is a really fantastic effort from Gavin and again, really appreciate all the work he's doing for this. Marcus, is there anything I missed on the components that we should also mention or does that cover everything? No, that covers it. I think the concept of web components is brilliant and I'm so grateful for Gavin to Gavin for being willing to bring it forward. It's even being considered for possible inclusion inside Jenkins Core. So now the exact components Gavin's creating don't belong in Jenkins Core. They don't make sense. They're just for the Jenkins website, but the concept of web components is an interesting and very attractive kind of thing. Nice, definitely. That's fantastic. Great, thank you Mark. And lastly on the agenda here, just the pull requests backlog. So one thing that we want to of course always do is encourage users to participate and contribute to Jenkins. The pull request backlog is right now at 43. We can absolutely get it lower, but we want to make sure that people feel they're being heard and their participation is noticed and is being acted on. So our goal when we get back from break is to make sure that we start getting this cleaned up and closing out. Some tickets are merging things that can be merged and making sure that we're acting on these things. They're not just sitting there waiting. Contributors want to make sure that they're heard, felt and at least talk to if not worked with forever. So this is the absolute easiest way to get started on that and make that impact for them and hopefully empower them to continue contributing. We've had a lot of great additions and improvements this year from the Google Summer of Code projects, ECODE Africa, from all of the different projects we've participated in this year have been immensely fruitful for Jenkins as a whole and we want to keep that going strong to 2023. So more to come on that, but something that we'll be taking care of in due time. Now with that, that takes care of everything on the agenda. Does anyone have anything else they wanna share or add before we stop the recording for today's session and say happy holidays? If not, great. I'll go ahead and stop the recording. It will be available within 24 to 48 hours. And again, thank you to everyone for the past year or 2022 has been amazing. We've had so many Jenkins. It just events in general, whether it's Jenkins.io, actual events or just the projects and participations we've been able to collaborate on. So thank you to everyone, all the contributors and especially for me personally, I wanna thank Mark and Bruno who have been here with me every session being a very nice audience. You're the best. Thanks, Kevin. Happy holidays to both of you. Yeah, happy holidays to everyone and happy new year.


This annual supply of fertilizer is made possible through the Moroccan Soil Facility Project, a partnership between the Agriculture Ministry and the Kingdom of Morocco, which ensures that the fertilizer is specially formulated to meet local soil health needs as stipulated by the Department of Agriculture Extension and Advisory Services Unit. Councilor of the Embassy of Morocco, Said al-Milaji, says his government stands proud to be associated with its agriculture counterparts here in St. Lucia and will continue to endeavor in creating the best possible environment for the local aquifood economy to thrive. The cooperation relations between Morocco and St. Lucia have experienced in recent years a significant dynamic in various areas. In this regard, I applaud the achievement in agriculture sector in St. Lucia and the fruitful results of practical cooperation between Morocco and St. Lucia and I hope that donation will further strengthen the capacity of St. Lucia for agricultural development and benefit farmers. Juggling a myriad of constraints to food production have proven quite challenging for agriculture leaders. The rising cost of inputs, delayed shipment of supplies, adjusting to ever-changing climatic conditions and managing pests and diseases to ensure soil and plant health are all critical areas to consider when designing the framework for the nation's food security and sovereignty agenda. For the Agriculture Minister Hon. Alfred Prospect, this latest donation from the Kingdom of Morocco is an active illustration of an agricultural partnership which gives an appropriate response to a sector and constituents in need. We know the level of importance and concern with regards to food security.  So it is important that we ensure that we reach out to our farmers because they are the ones responsible for the production of food. And I've always said to my ministry that the Ministry of Agriculture is responsible for food production in St. Lucia. We know of the gluts, sometimes the farmers are disadvantaged by hurricanes and natural disasters impacting them. And as you know, we do not have agricultural insurance in St. Lucia. So our farmers are really struggling now and I am happy that soon from now they will get some level of relief, they will get some bags of fertilizer that will help reduce on the cost of production. The 3,924 bags of fertilizer received from the Kingdom of Morocco are being distributed free of charge to farmers who are pre-selected based on a criteria set by the Regional Extension Offices to assist with soil fertility challenges and post-production. From the Communications Unit of the Ministry of Agriculture, this is Amanda Faye Clark reporting.


Trade it and upgrade it now at Appalachian Wireless and receive up to $700 off when you trade your old eligible device in and upgrade to a new iPhone 14 Pro Max or Samsung S23 Ultra on an unlimited Appalachian advantage plan because we are you. We are Appalachian Wireless. The Mountain Girl experience is currently looking for vendors interested in setting up for their festival. So we're really looking for all different types of vendors and we're mostly interested in artisans and we need food trucks, food vendors, food arts, baked goods that sort of thing. Really interested in basically anything made by your hands. We love handmade but all are welcome and I think it's going to be a really good turnout this year. We're not doing tickets this year so admission will be free so we'll have a lot of foot traffic. Artisans, bakers, crafters and many others are welcome to submit applications to participate in the Mountain Girl experience. And so the mission with Mountain Girl experience is really to support Turning Point Domestic Violence Services and what we're really looking for with our vendors market is to inspire the community. A lot of times folks will be stuck in abusive relationships due to the financial situation and small business can get folks out of bad situations. The deadline for vendors to apply for a spot is May 19th. To apply for a spot you can visit mountaingirlexperience.com or contact the Mountain Girl Experience Facebook page. For Mountain Top News I'm Kelsey Dean.