Hello and welcome back to the craft box. My name is Brennan today. We are doing a full Tour of Wizard City or at least all of the updated areas We're on my myth because I don't actually know where my death is currently. He's um He's somewhere that I can't get to at the moment because I haven't actually Unlocked him quite yet. I'm still loading a whole bunch of stuff So I hadn't actually got him ready yet, but currently we're just on the myth because he was already in the commons So yeah, this is the this is this is the commons like holy moly Chicken pox. This is crazy. I don't know what I said there, but sure um This is ridiculous like really really really ridiculously cool. I was a bit skeptical that it's not gonna look cool Especially the library um I was really concerned about the library Not really fitting in because of all like the bright goldy sort of stuff But now that I see it with the rest of the stuff. I'm really really happy about it like this looks so cool I'm not gonna go in the library yet But this is the shutterbug lady any shutterbug who is here. I haven't loaded her in yet video coming soon Hopefully later today Haven't been over into nightside yet either But um the first time I logged in I was here in Unicorn Way. I'm not in Unicorn Way In the commons.  I don't know if maps are gonna be loading or not But I've already been here so I've loaded basically everything already This looks so dope. This looks so dope This is the nice wee life symbol in the middle fantastic looks really cool better than the before the past is just so light Here's Daddy Unicorn Really chilling out here Really really chilling out here. I tell there was a whole part of loading and just unicorn statues They've gone all out with the unicorn statues. Um, there's also the bone cages Now I don't really like these As you can see right here, they're not quite connected, right? They're also really low as well I'm not really a fan. They've moved a whole bunch of them as well. Here's a pink unicorn They've moved like a lot of them. There's not as many around anymore So a bit weird a bit strange. They're so much lower, which I don't particularly like but you know, it's cool It's cool. Whatever. There's two there The keep in mind. We've just gone through all of them. There's two here. We haven't seen many haven't seen many already Yeah, I don't think they've updated many of the they've updated the skeletal pirates look at how cool they look look at the skeletal pirates They look like actual pirates now. I don't think the lost souls got much of an update Not that I saw I'd kind of left before I could really see them It looks like we haven't really done the dark fairies yet either But we still haven't seen many bone cages. There's another couple here right at the end here And that's about it. I haven't actually gone into the hedge maze. So let's go do that as well Yeah, but overall this looks freaking cool freaking fantastic. I'm I'm impressed I'm really really really impressed like this looks really cool. I don't think much is gonna load But this is the new this is a new battle circle So, yeah, it looks really really cool super crisp and you I really love how the red just pops in the ruby It's lost a whole bunch of detail though, which is I'm not really a fan of but I mean it looks good There's also a bit of like cracking around it, which I mean interesting interesting choice But yeah, I mean it looks good looks good. Don't you agree? There's also no music in here, which is bad I've found a lot of places with no music Hedge maze is apparently one of them. I've already reported one as a bug. I might have to do the hedge maze as well Yikes But yeah, we'll go over in two the Let's go back to the commons been around here We head over to I haven't seen Ravenwood yet I'm saving that for the end because Ravenwood apparently looks really really dope Let's go to go on court because that was what was spoiled and plays life hammers teaser with the whole tutorial being updated Also, another weird thing is Before the music just stopped when you weren't here, but now it's just the carnival music You can ride the carousel which is here. I haven't loaded There's a lot of things I haven't loaded in because this is actually the first time I've kind of like loaded Most of the stuff in test drum His last time test drum came out. I didn't actually go on it much So yeah, but look at this this is golem court. Obviously the NPCs aren't gonna load unfortunately But look at how cool this looks look at the trees Like seriously, this is probably like the best place to see the trees So much better than before. There's also dragon mouth cave, which I don't know if that'll be updated But we're not gonna go in there now Not gonna go in there because we need to keep this kind of short Apparently the pet hatching kiosk has moved I've found out from tacos who's one of my viewers That the pet hatching kiosk has moved again. This is like the third time in its existence that it's moved So let's quickly go and check that out Real quick. We still need him. I'm not gonna hit them to the library.  Okay, that's not ready for us. That's unfortunate.  That's good Haven't been tonight side yet, so I don't know how daddy dwarven's doing But let's go over to the shopping district kind of just going where I can at the moment So bear with me Haven't loaded Ravenwood. I don't think I'm not sure but I don't think I have But yeah, this is this is the shopping district. It looks so freakin cool really really really cool fountain pretty dope Alex edge Amazing. This is one of the spoilers here or teasers here with the whole root of buttlebee Who is like somewhere over that way? Coming out looks really dope really really dope, but then we go into old town which I wasn't thinking would be updated because Apparently Colossus Boulevard and all of the avenues apart from Unicorn Way haven't been updated apparently so that'll be coming soon hopefully But yeah, I wasn't expecting Old town to be updated, but it has been obviously as you can see Really freaking cool. I think they've made this a lot wider and if not, they've kind of made it a lot It's definitely different. I don't know what is different about it, but it's different They've moved some of these guys over here to down here Baldur's moved he's moved closer to a ship now. He used to be over this side Those two are the same We've got private Gilda scene who is who was up here now down here Then we've also haven't actually been down here. So I don't know what's down here Oh private Rosen Crange is here He was he also used to be up there as well, but he's down here now, which is cool And then this the big elephant in the room is why are people standing around this random hole here? Like seriously, what are you doing? What are you doing? What is this? What are this? What is this? Looks like there's a wee little cave down there. So that could be something interesting Renee's cooking up something real good here. She's just looking at it like hey, huh? Look at this hole. Yeah Who knows what that is I don't What was that? That was weird. Did you I'm gonna have to replay that day when I'm thinking doing Editing this like what that was weird. I'm also the wisps have a new shadow underneath Which is pretty cool. I think I'm actually on high detail high graphics, which is kind of good I haven't actually my computer isn't the best So It's kind of kind of bad. Yeah, I'm on high textures, which is kind of interesting How many do they go low and high? Okay? You can only have to what does low look like then because I'll probably have to Play on low when I'm streaming Nothing different really. Okay. Well, let's just go to high for now Yeah, sure why not so this is apparently low, okay Interesting why are they loading the graduation? I don't know. We're going to Ravenwood now Ravenwood the last place.  Thank goodness. I have that open. Thank goodness. I have that loaded I am excited for this. I am really really really excited Ravenwood is one of those areas that I've always remembered Always remembered so it'll be really interesting to see What we got in here nice loading screen The loading screens look really really good with the new graphics as well. So I'm impressed I'm really really impressed with this. Okay. Can we load that would be great chop chop chop load load Please please please that'd be great. Please load. Thank you. Okay. That was weird. Oh bottle. He's gone Rip bottle bees missing Team bottle bees gone. That's not cool Okay, so things haven't really loaded yet. That's unfortunate Torrance hasn't loaded unlucky Yeah, okay, so things aren't really loading that's funny. I think there's a lot of people on at the moment So there's um, you know a lot of things that aren't loading But um, basically you can you can get the idea I'll probably do another video just going over this because Ravenwood is one of my favorite areas That music though that music sounds so good Yeah, this is obviously him without his eye because I'm on my myth character I'll probably go through Ravenwood again and go more into detail With my death so you can see his eye as well But even without the eye that looks so much better than before so so good so good Super duper dope Yeah, hopefully the trees can load that'll be kind of cool Otherwise we'll probably just wrap up here. Here's Kelvin Sneezing away being a bit of a frosty boy. Look at that. He's really frosty. He's got a lot of frost Bernie looks pretty dope. He's apparently really on fire. He's like pretty lit apparently Um, he came up to me when we start when people start talking and I had it open and stuff so His icon looks really good. Most of the icons of the characters have all changed. There's misfit here They haven't really I don't think they've updated the reagents, which is a thing that they'll probably do in the future This is this music reminds me of the Arcanum, but five times better Five times better than the Arcanum blossom looks pretty cool Um, not not a hundred percent a fan. It looks more The face definitely to me looks more masculine than feminine and from memory blossom is female female Blossom is girl I don't think chat balloons are loading Maybe I have them off. I don't even know because that's the second time it has done that chat balloon show Yeah, that's probably yeah, I don't know. That's weird. Um, there's Torrance. He's a bit stormy. He's a stormy boy That looks pretty dope that looks pretty dope indeed That's pretty cool Bernie's finally loaded here we go with Bernie Here's Bernie. Look at how lit he is. He's like really lit Really really lit and then Ivan No, we'll go and see Ivan go and see Ivan then we have to go and see daddy to organ I haven't been a night side yet. So we'll go and see that real quick after this Here's Ivan. He's got we little wispy things flying around him, which is pretty cool He I think Ivan is probably one of my favorites Ivan is probably my favorite tree. Nice. We it's just so Nice like it's clean Really really clean. It's definitely different to blossom. I don't really like because of the face. It looks a bit too masculine But and Bernie the elemental schools are a bit I'm crazy apparently Niles has been updated as well I'm not gonna go over to Cronkotopia. Probably don't have that downloaded. So it'd be like forever for me Did a go get it an upgrade? No, I don't think a go and got an upgrade. Did these guys get an upgrade though Is he Simeon? Are you upgraded boy? Oh Simeon's a bit upgraded Simeon looks cool now. He's um, yep He looks really cool. Don't know about alpha all of the teachers got upgraded again. I'll go over Probably the Ravenwood later Later in the deed later in time Let's quickly head over to night side or sunken. No not sunken city. Just night-sided. That's what it's called Good job Go and see how things look there Hopefully look good So, yeah, there's as I said earlier in the update notes video if you haven't seen that you should go and check that out So, you know exactly what has happened. Holy moly. It's so blue. I love it get inside.  Oh They're spooky faces. That's so cool. Oh my gosh. That's so cool It's like debris everywhere. This looks lit. This honestly looks so good Let's see how the death school looks. I know all of the schools got updated And I did watch plays left him his video just earlier So he didn't go into night side. Holy frick. This looks cool The music The music the music in this game is so good already and now it's just like super good Dworkin's icon got a bit changed. It's a bit more old now. Oh Gosh, this looks so cool Okay, we're gonna leave seeing Dworkin for later We're gonna quickly just see if mortis is loaded in has he hopefully can he after After the Sunken City, can you please load that would be great. Nope. Okay, learn try them So, yeah, we won't see Dworkin I'll go through all of the schools in detail in another video. That was kind of just a quick overview of everything that's changed Colossus Triton firecat haven't changed apparently Darkmore hasn't either obviously it's a bit new so yeah, but otherwise Thank you for watching more videos coming later today. I'll be streaming from 10 a.m. New Zealand time Which is 5 p.m. Central remember craft outside the box


Welcome to this webinar on expert biocuration. You're going to discover Uniprot, and more precisely, the reviewed section of the Uniprot knowledge base, SwissProt, and what we mean by expert biocuration. The second part of this webinar includes a live demo showing the different steps of the expert biocuration process using Uniprot's dedicated biocuration platform on a newly characterized family of proteins. First, what is Uniprot? The mission of Uniprot is to provide the scientific community with a comprehensive, high-quality and freely accessible resource of protein sequence and functional information. Uniprot proposes different resources, but here we will be focusing on Uniprot KB, a reference protein knowledge base which contains protein sequences associated with functional information. Uniprot KB is composed of two sections, Uniprot KB SwissProt, which contains biological information reviewed by expert biocurators, and Uniprot KB tremble, which contains automatically annotated protein sequences. For simplicity, we will use the terms SwissProt and tremble from now on when we speak of these database sections. In the SwissProt section, the biological information is extracted from the scientific literature by the expert biocurators or it comes from curator-evaluated computational analysis. The primary goal of this biocuration process is to provide an accurate and comprehensive representation of biological knowledge on a given protein and to make this data readily accessible to the life science community. We encode biological knowledge in forms that both humans and machines can understand and exploit. What type of information can be found in a SwissProt record? In the next few slides, we'll have a quick look at the elements present in the entry for gene Newt T12 from mouse. This is also the entry on which the demo in the second part of this webinar will be based. A SwissProt record can contain, for example, one or several protein sequences which are the products of a given gene. In this example, the mouse Newt T12 gene produces two different protein sequences as the result of alternative splicing. An entry can also contain information on the family the protein belongs to, on the biological function and if the protein is an enzyme on the catalytic activity, on the different cofactors required for the enzyme's activity, on the subcellular location of the protein and many other aspects that describe the protein, such as post-translational modifications or proteolytic cleavage, involvement in disease, etc. The source of the information is provided whenever possible via evidence tags. Note that the annotation in this entry, before the major update described in the second part of the webinar, was primarily based on similarity to the human orthologue. Once the protein has been fully updated at the end of the webinar, most annotations will be based on the experiments described in the scientific literature. In the SwissProt section of UniProt KB, all information presented in an entry has been curated by expert curators who are usually biologists or biochemists. Let's have a closer look at what this process of expert biocuration actually involves. Expert biocuration in SwissProt consists of a critical review of experimental and predicted data for each protein, as well as expert verification of each protein sequence. This process requires a combination of human intelligence, well-designed software tools and advanced computational methods for literature identification and triage. To give you an idea of the scope of the body of literature on which SwissProt is based, biocurators have gone through almost 240,000 carefully selected publications, which means they have critically extracted and reviewed information from these publications to provide summaries of the knowledge available for every single protein. A well-defined expert curation process is essential to ensure that all entries annotated by expert curators are handled in a consistent manner. SwissProt curation is performed by expert biologists using a wide range of tools that have been iteratively developed in close collaboration with biocurators, integrated in a dedicated biocuration platform. Documentation on our standard operating procedures is available via the help section on the UniProt website. Now let's go ahead and discover the different steps of this biocuration process with an example. We will show the process of updating the SwissProt record from the mammalian enzyme encoded by the gene Newt T12, according to a new publication. This publication shows a new activity that had previously been known in prokaryotes but not yet in eukaryotes. Some biological background. Eukaryotic mRNAs possess a well-known cap at their five prime end called the N7 methyl guanosine cap that prevents mRNA from degradation. Another cap was recently discovered also at the five prime end of mRNA, the nicotinamide adenine dinucleotide NAD cap. NAD-capped RNA can be decapped in a process known as RNA denading. The cleavage can occur at two different sites, as indicated by the blue arrows, depending on the biological context and the enzymes involved. The cleavage at position one is performed by an enzyme called DXO, an enzyme which has been described in eukaryotes. The cleavage at position two is performed by an enzyme called Newt C, which until recently had been characterized only in prokaryotes, in E. coli in particular. Several recent publications report studies of a protein with an activity similar to Newt C in mammals. They found that the enzyme Newt T12 is the mammalian ortholog of the prokaryotic enzyme Newt C. It belongs to the Newt X hydrolyze family, Newt C subfamily. It has denading activity on NAD-capped RNA and can hydrolyze free NAD. Let's start our live demo on the expert biocuration of Newt T12 together with Dr. Sylvan Poo from the Swissprod group of the SIB, Swiss Institute of Bioinformatics. The curation editor is loaded together with the latest version of all controlled vocabularies and other related datasets required for the biocuration process. This is the curation editor homepage. The main window supports curation and it is here that we will see our Swissprod entries once they are loaded. The left side panel provides access to protein or nucleic acid sequences and different supporting documents such as alignment results or nucleotide to protein translation results. The icons at the top provide access to different commands and biocuration tools, some developed in-house, some external, for example, blast for similarity searches, our in-house module for integrated sequence analysis and prediction, various sequence alignment tools, and pubtata, the text mining web tool, which helps us select publications. All together, about 340 different commands are available, which can be executed via their icons or for the experienced curator via keyboard shortcuts. Now we are ready to update the Swissprod record corresponding to the mouse's new T12 protein. According to a carefully selected publication, our aim is to update the relevant biological information in the corresponding existing entries from mouse and other mammalian species, according to the information found in this publication. The curation editor gives access to the latest internal version of the Unipod Knowledge Base. Using the menu, we can search for all entries which contain the term new T12 in Swissprod. We select and load the entries corresponding to the mammalian proteins, which are derived from the gene new T12. Now that we have loaded the entries, we will start to update them, which brings us to the view of the entry. We will focus on the mouse protein encoded by the new T12 gene. As we can see, this representation is slightly different compared to the Unipod website entry view. However, it does look very similar to the text format, which can be downloaded from the website or from the FTP server. Entries are composed of different sections, and the lines in this representation are preceded by a two-letter code defining a section. We can see the section containing protein names and gene names, the section containing publications which were used to annotate the entry, the so-called comments section, where lines are preceded by the letters cc, and which contains paragraphs about the protein's function, catalytic activity, among many other subjects. The section with the cross-references, which give access to relevant information in almost 200 different external databases. Most cross-references are already present in the entry, imported by automated procedures, but others can be added or modified by the curator. We can access cross-reference data directly from the editor with a simple click. There's also the section with the so-called feature table or FT lines that contains annotation related to the protein sequence itself, such as the positions of domains, metal binding sites, substrate binding sites, or post-translational modifications. And last but not least, the section which contains the protein sequence itself, which remains in sight all the time, even as we browse through the rest of the entry. The first important step of the biocuration process is to check and validate the protein sequence, because a lot of annotations are linked to amino acid positions in the sequence. For some model organisms, such as human and mouse, a consortium exists to ensure a consensus sequence corresponding to the genome. The CCDS database for consensus coding sequence is the result of Uniprot's close collaboration with institutes such as EBI, NCBI, UCSC, and Wellcome Trust's Anga Institute to establish a common clean set of human and mouse protein sequences which must match the underlying genomes. In order to validate the mouse's new T12 protein sequence, we therefore have to check that the protein sequence is part of the consensus CDS protein set. A CCDS cross-reference is already present in the cross-reference section of our entry. This means that the mouse sequence matches the CCDS sequence. No additional action is needed in this case. The major added value of expert curators is in literature curation, a process which cannot yet be handled by machines. The first important step is publication triage, where we select the publications relevant for the curation. We do not aim to curate all published papers. Instead, we select a representative subset to provide a complete overview of available information. To do this literature triage, we use a tool developed at the NCBI called Poptator. When launching this tool from within the curation platform, the literature mining results corresponding to the protein and gene names are seamlessly displayed. By using Poptator, we can find 14 publications associated with new T12. Many of these are not relevant because they describe high throughput analysis or experiments performed with artificial substrates, and others are out of scope for uniprot curation. In the end, three publications were relevant for the biocuration of new T12 as a denading enzyme. Numbers 3, 6 and 9 in this list. The publication, which is going to be curated now, is the paper from Nature Chemical Biology. It shows that mouse new T12 has mRNA denading activity. The authors also study the 3D structure of the mouse protein. We will add this paper to the mouse entry in the reference section. We import the paper by using the get pubmet command with the corresponding pubmet identifier. We can now copy-paste the citation in the required format into the mouse entry in the reference section. The new publication is added as reference number 5. We will now update the biological information present in our entry according to this publication and create a short summary of the main findings of the paper in both human and machine readable forms. One of the human readable parts is a short textual summary of the function of the protein, in this case the fact that the protein is an mRNA decapping enzyme. We use so-called evidence tags to indicate the source of the information. In this case the information comes from experiments described in reference 5. We select exp for experimental as evidence tag and add a link to reference 5. A statement about the previously known activity of this protein is already present in the entry, inferred by similarity to the human entry. After having described the function in a human readable form, we now also summarize it in a structured format by using the genontology or GO. Uniprot is a major contributor to the genontology consortium and manual curation of GO terms based on experimental data from the literature is part of the uniprot curation process. In this case, NAD capping of mRNAs was not yet described in GO and we therefore contacted the GO team to request a new term to cover this activity. The term was created and is now part of the official genontology for molecular function and it was inserted in the entry. Now we modified the recommended name of the protein to reflect its activity. We have decided to name it NAD capped RNA hydrolyzed Newt T12. The protein was not explicitly named in the article and the name was attributed by the curator. Therefore, the evidence we associate is curated. We also specify a commonly used short version of this name. The evidence we associate is curated. We also add a partial enzyme classification or EC number 361 to indicate that the protein belongs to the class of enzymes called hydrolysis class 3 acting on phosphorus containing anhydrides subclass 6 1. Note that the previously used name has been kept as an alternative name. The next section to be updated is the catalytic activity section, which is in structured machine readable format. We use RIA, a comprehensive expert curated knowledge base of biochemical reactions to describe our reactions. To refer to reaction participants, RIA uses kebbi, a widely used ontology for chemical compounds of biological interest. According to the paper, Newt T12 is a denading enzyme that hydrolyzes NAD capped transcripts. At the time of this update, the denading activity was not described in any resource and we therefore contacted RIA curators to request the missing reaction. The new reaction was created and we are now able to include it in the mouse entry with the identifier 60876 that was attributed to this reaction. In particular, we can specify the direction of the reaction, which is left to right in this case and we add the experimental evidence tag. The authors have determined the 3D structure of the protein and provide information about the quaternary structure of the protein, which is a homodimer. This type of information is stored in the subunit section. As before, the new quaternary structure information homodimer is tagged with a link to the source and to the fact that there is experimental evidence. The paper provides information about the cofactors. The cofactor section is in structured format. All chemical compounds are mapped to kebbi terms, just like previously in the section on catalytic activity. The previous version of our entry already had cofactor annotation, inferred by similarity from another entry. It had however been unclear if the divalent metal cut iron was manganese or magnesium. Our new paper now shows that magnesium is indeed the cofactor, allowing us to update this information. And we add the experimental evidence tag. We can also add the information that the protein binds three magnesium ions per subunit. The protein is also in complex with zinc, and we can add zinc as a cofactor, selecting it from the list of cofactors imported from kebbi. More precisely, one zinc iron is bound per subunit. And we add the experimental evidence tag. We now proceed to the annotation of sites of interest within the sequence. Which can be done with the help of the crystal structure of new T12 in complex with a substrate analog, with three magnesium ions and one zinc iron, as described in our paper. According to this data, we can annotate the positions of the metal and substrate binding sites. We check that the positions of the binding sites described in the article correspond to the ones present in the structure, and we pay attention to only annotate those binding sites which are biologically relevant. This is done with the help of the PDB sum resource from the EBI. In this 3D structure, we see two zinc ions in blue. There are two, one per subunit of our protein, which we've previously seen to form a dimer. We click on one of the zinc ions and see that it binds to four sustained residues at positions 284, 287, 302, and 307 of the protein sequence. We can annotate these four metal binding sites, again indicating the source as reference 5. We proceed in the same way for magnesium and substrate binding sites. Now that we have added a number of details to the mouse entry, let's have a look at the new entry compared to the original version. We quickly browse through a view that shows these differences, seeing the updated name, the inserted publication, the updated paragraph to document the protein's function, the new catalytic activity, cofactors, the subunit section, describing the quaternary structure, and the metal binding and substrate binding sites. The next step is family-based curation propagation. Annotation content can be propagated to other mammalian species using our propagation tools. Experimental information can be spread among orthologs, because researchers experimentally study different aspects of a protein in different mammalian species. To create a complete and consistent portrait of a protein, we carefully assess which information can be propagated, considering that not all types of information can be propagated to orthologs. We can select our template entry, mouse in this case, and our target entries, and select the topics we would like to propagate. We start with the free text function statement. In Orangutan, Bovine and Makak, we replace the existing comment, which had already been inferred by similarity, by the more up-to-date one we just curated in mouse. The human entry already had an experiment-based statement about protein function, which we don't want to erase, and we therefore decide to add the function from mouse, inferred by similarity, to the existing experimental statement. Once the information has been propagated, we can see in the human entry that the new activity has been added, and the information is inferred by similarity from the mouse entry. The previously annotated function that was backed by experiments has been conserved. We move on and propagate the new and updated catalytic activity, subunit, and cofactor statements accordingly. We can also propagate the updated positional annotations, which are sometimes called features, based on a multiple sequence alignment. On the right-hand side, we have the alignment results, and the features that are eligible for propagation, which are those that are conserved in the sequence. We select the sites that we want to propagate one by one. They are highlighted in the alignment. Once the features have been propagated, we see that the annotation is based on the mouse ortholog, citing the accession number of the mouse entry. When we now look at the human entry as a whole, we can see all the added and modified sections highlighted in color. Most modified sections have been annotated as inferred by similarity from the mouse entry, but as discussed previously, the function section has a mixture of experimental and similarity-based sources. The different entries are now ready and can be submitted to quality assurance curators who will check the annotation before the integration of the updated entries into the internal SwissProt database. Here is what it looks like on the website. Most of the new annotations are in the function section. The free text summary of the function, the new catalytic activity, cofactors, metal binding and substrate binding sites, and the newly created go terms. We'll proceed similarly for the other two publications initially selected for curation. This webinar was a simplification of the process, where we have chosen to illustrate the literature curation for a single publication In a real life case, however, we would simultaneously review all relevant publications, create a summary and synthesis. Then we would spread a combined view of the new findings across the different sections of the entry, before propagating them to entries describing orthologs. We hope you have found this video useful, and will join us again for future webinars, where we plan to address other aspects of the curation process. As always, please don't hesitate to contact our help desk, if you have any questions, updates, comments or bug reports.


Welcome to The Coal Report. I'm Lance Corporal Clayton Phil Poveage. And I'm Lance Corporal Ally Bisonger. Marines who have been using tuition assistance know that this year has been rough. But things are looking better. The Coal has an additional $40.5 million to send Marines to school through Amanda in the fiscal year. The money will break down like this. Just a reminder, Marines can only apply for TA if they have at least two years' time of service. Also, first-time students must establish a good academic track record. So, they'll only be approved one course at a time. To read more, click on the link in the video description. Marine Corps Assistance Command recently tested the Corps' newest flag jacket with Marines from the First Light Armored Reconnaissance Battalion. The new jacket, known as the Modular Scalable Vest, is designed to provide Marines with a single vest system to increase mobility. The new vest looks just like this. Even though it looks larger, the MSV is actually lighter than the two systems currently fielded. You know, it did take you a long time to put that on. Yeah, well, I'm a Pogue and it's my first time. What's this new Cyberg piece here in the back? It's supposed to help distribute weight evenly across the back and the hips. What do you think? Well, I think it feels great, but don't take my word for it. Even though it's still in early development stages, Marines with the first LAR didn't have many complaints. Minor changes like webbing placement and a more comfortable neckline were suggested. For more information, click on the link in the video description. Alright, by Swinger, get me out of this thing. We asked for your help finding the next featured Marine and got some amazing nominations.  With us here today is Captain Brian Jordan. Morning Marines, thank you for having me. Good morning, welcome to the show. Thanks for coming, sir. Thank you. So you were awarded the British Distinguished Flying Cross. What happened out there that day? I was. Well, it was a routine mission that we were doing. JTAR and things kind of went sour towards the end. British soldiers stepped on an IED and we had limited fuel, limited time remaining on station and decided to execute the Kazovac to get the soldier out of there and save his life. So what was your reaction when you were awarded this medal? Extremely humbled. It's a great honor to receive this award, but I'm receiving it on the behalf of my crew as well as the Marines that take care of the aircraft and maintainers. Without them we wouldn't be doing this or being able to do that mission. And the Marines, like Lieutenant Colonel Lightfoot and Captain Jablonski, the section lead putting down some press of fire as we came down and executed the Kazovac, co-pilot Captain Josh Miller and then crew chiefs, gunnery sergeant Vaughn, staff sergeant Sey and Copel Martinez. Those are the guys that made it happen and I'm glad to have had them with me because without them this mission wouldn't have been successful. Do you have any awards of wisdom for our viewers out there? At here in your training there's wonderful instructors out there and great Marines out there, so listen to what they've done, learn from their mistakes and learn from what they have to say. Alright, thank you sir. Appreciate it. Absolutely, thank you. Congratulations. Thank you very much. You're welcome. The heroes of today continue to stand on the shoulders of the legendary Marines of our past. February 19th marks the 69th anniversary of one of the most well-known battles in Marine Corps history, the battle for Iwo Jima. We'll never forget the fierce fighting of our Marines or their iconic feats like the flag raising on Mount Surabachi. Secretary of Navy James Forestel said, the raising of that flag on Surabachi means a Marine Corps for the next 500 years. Remember, if you can catch up on everything else going on around the Corps, then log on to our official social media sites. Those links are in the video description. Thanks for watching. We'll see you next Friday. Right here on The Corps Report.


Yes. Hi everybody. Thanks for joining us today. Welcome. We are here outside of Nancy Pelosi's house in San Francisco and earlier in the week you saw co-founder Jodi Evans knocking on the door trying to connect with Nancy Pelosi. Well we are back and we are here to deliver the petition that you signed. We have over 3,000 signatures. Thank you so much for signing. So we're gonna go to her door and we're gonna knock and see if she'll accept our our petition. Come on over. Come on. Don't be shy. Come on. We're in beautiful San Francisco. It's a little cold right now. Oh my god. Look what we have here. Someone has decorated her door. It says Pelosi. Stop war with Iran. Oh my goodness. Look. Am I in? Wrong with you. You're the one. You can be better than this. Canisters, fishups and fishups and rabbis and papis and bye bye bye bye. Congratulations.


tabilize that? Yes, these are all things that we are evaluating. We are in the process now, and Maureen, I was probably on the line here who's the lead for the channel. We've got several different pilots that we're evaluating. And one of the focus areas, I didn't even have a chance to spend time on is up in the Dudley reach where we've identified as one of the potentially largest sources of particulate lead. So we're right now evaluating several different pilot projects and one of them includes various combinations of capping and dredging in the river. Excellent, thank you. Jim Duff. Jim Duff. Can you hear me now? Yes. Yes, question is, and this would be for Cam, I believe, why have the stream or the river segmentation dynamics changed? And that's the sense I get from a net depositional to now a net erosional regime. So during the mining period, which really extended up through 1968 or so, end of the 60s, there was a lot of, as Ed alluded to, there was a lot of transport and tailings and dumpings of tailings into the stream. It all moved its way down stream into the lower Coeur d'Alene River. There were several episodes where they had built plank dams and these plank dams released during some flood events were released additional tailings. So there was just a gradual buildup of mining material all through that period until mining eventually was ceased in about at the end of the 1960s. And at that point, and Tyler's better to talk about the dynamics of the river, but at that point, the river just naturally starts to re-equilibrate and starts to erode, like I say, it's net erosion. So over time, it starts to cut into the bed. So there are places we found that in the river where it does deposit and the other places where it's more erosive, but in the net it's continued to, it started to cut down starting after the end of the mining period. Yeah, thank you very much for that clarification. I appreciate it. No, Sandy Emerson, Sandy Emerson. Sandy, you hear me now? Yes. Yeah, thank you. I think there's a, you're getting all around my question and that is the toxic waste sink right at the mouth of the Coeur d'Alene River down toward Harrison by the Harrison Dockbetters Association in Springston. I've seen studies there that show 11,000 to 15,000 parts per million lead right there in the concentrated area. And that was actually historically used as kind of a place that they were dumping, intending to dump large amounts of mine waste. It's been discussed how to get rid of that over time rather than just letting it be capped because it's so huge and enormous. How does that factor into some of the things that we're talking about today? I can get my new button there. Those are the concentrations that have been seen. If you recall the slide that I showed you, some of the more concentrated mining material at depth that we've seen from our coring has been up in those concentrations of 20, 30,000 parts per million. And so depending on how much erosion has occurred and whether those legacy deposits are now at the surface, you can see these concentrations. And that is part of what our challenge is and what we're working on now in terms of identifying these sources. We generally want to work upstream to downstream and we know that there's some very high concentrated pockets up and again at the Dudley reach. But that's our goal is to incrementally start to remove or cap or remove them as sources to the lake and to the wetlands. Thank you. It's been said it was somewhere between 400 and 700 million tons just primarily in that particular location or on through that, is that accurate? Yeah, I know there's been some very large numbers. I'm trying to thank Tyler. Do you have the number that we've estimated for the bed itself? I don't have it in the top of my head, but it's- I don't have it on hand to tell. Yeah. But it is a large amount of contaminated sediment that is sitting in the 30 miles and down through. I'm not sure specifically about the location that you're talking about, but. Well, the concern was it would become remobilized as we've been talking about all throughout. So it's a lot to work with it. Thank you. Indeed. Adriana Hummer. Okay, can you hear me? Yes. Okay, thank you. And that previous question and answer partially addressed my question, but I was just curious about other remediation efforts. So we've talked a lot about all the data sets showing that the water is talking about water quality, but are there any other plans in hand right now to do further remediation aside from what was just discussed to improve the quality or are we still in the data collection and analysis phase? Well, I think Ed talked a lot about the, we have a lot about all of the remediation efforts that EPA has been conducting throughout the upper basin. And of course we have focused on the upper basin initially. It's again, it's more of this top-down approach. So in addition to all of the work that has been done up in the tributaries and the groundwater collection system that's been installed in the South Fork and a variety of work done at the mine and mill sites in the upper basin, we are starting to have some efforts down in the lower basin, but there was a definite need to really understand the system and make sure that if we did put something into place, we weren't going to recontaminate it again or just really understand that if we tackled the section of the river that it was gonna move the needle for us that we were really going to have an effect on the suspended sediment, contaminated sediment going into the blood planes and into the lake. So then in terms of the channel itself we are on the cusp of developing some pilot projects I would say in the next three years we'll have some designs in place to work on a section of the Dudley reach and we've also been working on cleaning up some of the wetlands we have the schlept wetland that was done earlier on and then we're currently working on what's known as Grace Meadow now to create more clean feeding habitats. So to remediate those impacted flood plain areas. Fred, I don't have a last name, somebody named Fred. Can you hear me? Oh yes, I can hear you, you can go now. I'm sorry, I'm a property owner on the lake and I own properties probably in four of the areas that you guys have modeled. I was first involved in the site back in the early 80s working for Office of Research and Development, EPA down at EMSL Las Vegas. Later I was director of the mine waste management studies at the University of Idaho where I received my master's and PhD and as part of the director, I put through about the 20 different master's students and PhD students working on the mine and the areas around there. And I did my master's down in the Bunker Hill Mine itself and the PhD I did was out on Smeltabill Flat. So I'm really familiar with the site and I still live in the area and I'm a downstream interest now in my later years. I enjoyed all of the discussions but I had kind of a big question was I missed the opening statements and I was curious what is the purpose and objectives of this group and what is your charge and who issued the charge to you guys to do this? I'm glad to clear all that up in the final statements. Let's finish up the questions here and then I'll summarize restating our charge and the sponsors. That's okay with you. Sure, sure. Now let's see, I think we have a question also from Jamie Sturges, if you can connect. Jamie, are you able to connect? Okay, here you go. Can you hear us? Yes. This is Jamie Sturges by telephone to Jamie Bruner to the internet and I don't have the ability to do audio right now and send because we're not located but I wanted to just, I'm so excited about the moving forward, the moderator, the panelists, the committee and expectations are high. I do have one question which I won't be able to hear the answer to unfortunately but I'm curious with the annual raising and lowering of the high pool and low pool, does that mitigate or aggravate sediment flux into the river in the Chain Lakes area? And I'll just wait for that answer to be able to connect to everybody. You want to take that Tyler? I think you have. It complicates it for sure. And I think Kim mentioned this at the beginning of hers. So during high pool, the sheer stress on the river is less, so there's less erosion. It lasts for longer and because the lake level is higher more water goes to the flood plain. So you have more water and more sediment going to the flood plain but you have less erosion on the channel. During low pool, these sheer stresses on the channel are higher. There's more erosion for a given flow rate but there's less connectivity to the flood plain. And so fortunately more of that sediment during the low pool events goes to the lake. So it's very event dependent. It depends on the dynamics, the flow rate and the length of that event. There are some short duration winter events when there's low pool that cause just as much scour and as much total sediment as long duration spring high pool events. And so it's hard to say that the change in pool helps or hurts the sediment flux to the flood plain or the lake but it certainly complicates and it's an event specific discussion. Thank you. Let's see. I'm waiting to see if there's any more. Do I have any more? Coming up Eric. I think there's one more that's coming over. Okay, thank you. Sorry for the pause here folks. There we go. There now. Let's see. I have the only number I see is Jamie. Let's see. It should be number nine. The name is DDSZ. Okay, would you wanna go ahead, sir or ma'am? Whichever it is. I don't see it on mine, but that's all right. Oh yeah, DDSZ. There we go. Thank you. So DDSZ, whoever that is. DDSZ. I guess we don't have anybody there that's able to connect. And so Eric, do we have any open mic? Anybody in the open mic list that wasn't down here? I don't think so. There we go. I've got a new one. Wait a minute. Oh no, did I get Sky Walden? No, that's fine. I'm just coming in over this way. You guys are talking a lot about future projects being capping, which I've seen up River, but there's also still signs by the creek that say don't touch the water. And I'm wondering when I've done independent research, I've seen like dredging and bioremediation as ways to clean up the existing lead is there any way that we could do something like that? And is there any way to repurpose the lead? Like for MRI doors for hospitals or like, are we just trying to cap it again? We're looking at a number of alternatives. Capping is one, dredging is one. We've looked at various options like putting in weirs and wind fences. There's a variety of options. Wind fences, there's a variety of ways you can tackle this and it would not probably be the same throughout the entire riverbed. They all have their pros and their cons. And we're basically gonna be starting kind of in a stepwise process, probably up at the Dudley reach and testing some of these technologies and it will probably be a combination. In terms of repurposing the lead, EPA has not really, just due to the volume and difficulties of this system, it is not something that is really panned out, not something that we would look at on a grand scale. So a lot of, if we do dredging, there needs to be a place on the site to place that material, which is why we have some well-managed repositories throughout the site. And we'd have to consider that as well for the lower basin. Thank you. Great. I think it's, we're a little, quite a bit over time actually, but that doesn't matter. We're very glad to hear all the questions from the audience and from the public, but I think it's probably time that we wrap up here. Let me, as I promised one of the earlier questioners, I will reiterate that we are specifically, our task is to specifically to focus on future water quality conditions in the lake. And we're collectively looking at available data. We're looking at trends. We're really interested in trends and we're interested in developing a base of understanding or at least discussing and putting together a base of understanding that ties together the things that we heard in these presentations today. It's from that base eventually that some of these more difficult questions hopefully will provide some help in addressing the question of what the future might hold and the other more complicated questions that follow what to do next. So that's what we see as our contribution. The sponsors of the study are the Department of Environmental Quality, Kootenai County, the Coeur d'Alene Tribe and U.S. Environmental Protection Agency, the National Academy's committee comes in at the request of the sponsors and with the charge defined by the sponsors. Our next meeting will be in May. Between now and May, the committee itself will start to drill down on some of these issues and start to put together our report. But let me emphasize that we are in the early information gathering phase. So we don't have much in the way answers right now but we are gonna seriously look at and address these issues. Let me make, let's see. I think that's, yeah, our meeting is in May and recordings of this meeting will be available next week on the National Academy's website for the meeting which I presume you all have access to or we can get to Laura if you need us. If there's anything else that you wanna add Laura, go ahead, otherwise I'll call the meeting to a close. And thank you all very much. Thanks panelists for the questions. Thanks presenters for all these excellent presentations. It's a great start. As Bob said, we're kind of starting, we're just beginning to get a feel for the system. So we appreciate the great start that you've helped us with. Laura, anything else to add? I'll just say that this meeting actually is not over for the committee members. They will be meeting next week in closed session. Those are internal deliberations but after that meeting we will be making information requests to the various study sponsors as well as others who may have submitted comments that we can respond to. So we look forward to everyone's continued participation. Please be looking for communications from myself or from Calar Rosenfeld. And if you need to ask us questions please just feel free to send either one of us emails and we will get back to you as soon as possible. Thanks everyone. That's great. And I should also add one last thing. We expect this process to expect to report in about a year and a half. I know if there's some of you that probably sounds like a long time but that's how much time these things take and the product in the end will provide a base for moving forward. I hope that's our goal. So thanks very much for your participation. Thanks for your questions and for the invitation to be here and we'll see you. We'll see the next public session in May. Thanks a lot.


Master Windu, how pleasant of you to join us, this party's over. Life Lessons in Film. We're continuing our series of Tales of the Jedi Episode 3, Choices. This is another Dooku episode, and do love me my Dooku episodes. Follows Mace Windu and Jedi Dooku as they are doing a mission to find out the happenings around a mysterious death of another Jedi, a luminar-looking mofo. And as they get to the planet they uncover through clever deducing that the Jedi was actually murdered by the people that she was traveling with. There was an attempted coup, yeah the senator was held hostage because the senator started to allow corporations to plunder the natural resources of the planet, and the people living there didn't approve, understandably, so they decided to say enough of that. We're gonna call the shots from now on, we're gonna hold you hostage basically. The Jedi uncover that, there's a little bit of a skirmish, and then they arrest the perpetrators, and then they go back to Coruscant because the Jedi passed away, they have a nice Jedi funeral, and then Mace Windu is promoted, which is why we see him in the Phantom Ennis on the Jedi Council. I really like the line here in the beginning where Dooku and Mace Windu are flying in their ship, which I like too. It was different, so it was creative, but it had a similar color scheme to the ship in the beginning of Phantom Ennis, so just kind of like diplomatic ships that were used by the Republic at that time. As they're talking about the mission, Mace Windu is more about he's a rules guy, he's more about the code, that's kind of how he structures his conduct. Dooku's more of a rebel, Mace Windu, one of the points like, We cannot involve ourselves in local political skirmishes unless requested by the Jedi High Council or Senate. And Dooku responds with, My friend, your devotion to rules is sometimes inspiring and sometimes maddening. I like that there was a nice bowl full of nuance in that statement, right? Because not only do you find parts about everyone that you know, you know, you can disagree with how they go about things, but sometimes you can actually like parts of their character, depending on the situation or depending on their mood or depending on many different things at other times. It doesn't work for you. It doesn't work for them or whatever. Like, seeing that. Some good dialogue. I also liked, again, the political aspect. I was even impressed. The whole thing about offworld corporations coming into a planet with bountiful resources, but doesn't have much in the way of protecting itself from greedy interests, which, you know, reflects our own world, which I think is what sci-fi should do. Good avenue to kind of explore things going on in our world, but doing it through, you know, fiction, basically like neocolonialism, a way of powerful interests just doing whatever they want, exploiting other people's resources, the issues that come with foreign interests influencing local area, local planet, their politics and then people wanting to actually take a stand, defend what they see as their rights, defend their land, defend themselves. And so I liked when Dooku has the talk with the prisoner and now it's starting to build on Dooku's questioning more and more how connected the Jedi are to the Republic, which seems less and less to serve the people. So I like that it adds, again, to Dooku's questioning of things and reasons for leaving the Jedi Order, kind of builds on that idea of the Jedi becoming too closely connected, kind of a facet of the Republic system that kind of have play, start to play more and more but like a paramilitary part of the Republic and less about resolving conflicts and more just kind of allowing the Republic to continue, you know, ignoring issues going on or to perpetuate other issues the Jedi have started to lose sight of their purpose. So Dooku is starting to have more and more cognitive dissonance about the things he's set out to do versus what feels, what he's feeling going on inside. I liked the conversation he has with the prisoner, that relatability to someone who even though you might not necessarily agree with their methods or their ideology generally, you know, but he still I think maybe feels some camaraderie to someone where basically everyone else in the Jedi Council or the Jedi Order at this point thinks of Dooku as kind of a maverick, you know, outlier. Felt good for Dooku to feel some camaraderie with someone else who is trying to take matters into their own hands when they see an injustice happening and he respects that. And there is that kind of feeling of connection to someone that you recognize also is dissatisfied with the way things are, you know, wants to create some meaningful change. Again, you don't necessarily have to agree with them completely on how they go about it or how they even want to shape things, but you just appreciate like I see that you're motivated and kind of want to do something, take action, you know, I respect that and that's something that maybe I aspire to do. So that felt very real and natural for Dooku to kind of have that moment of connection or inspiration validation from the prisoner.  Make sure your people don't lose hearts and evolve so much.  I say that for all of us. People can do things, can be taking things into action, action in their lives, and you can see them doing that. And it can maybe even inspire you to want to be more active in your own life, regardless of if your situation is, maybe if your situation, your life can be very different from theirs, but it can still inspire you to kind of play a more active role, be more present in your life. So I liked all that. And you know, of course I liked Mace Windu and Dooku not only as a pairing because we just never seen that before. Mace Windu's purple lightsaber and Dooku's curved blue lightsaber going at it was fun. Also builds on the stuff that is kind of touched on and attacked the clones, just kind of fills in little tidbits of the prequels that were just kind of there for flavoring. A few times when Mace Windu references Count Dooku and attacked the clones, like says, you know my Lady Count Dooku was once a Jedi. He couldn't assassinate anyone. It's not in his character. Kind of defends Dooku. It's interesting to see why he would do that, to see that they had something of a relationship at one point in school. And also Dooku refers to Mace Windu as an old friend. Master Windu, you are fought gallantly, worthy of recognition in the archives of the Jedi Order. Now it is finished. Surrender and your lives will be spared. We will not be hostages to be barred Dooku. Then I'm sorry old friend. At one point being teammates and being members of the same order. So it's cool to see this episode for me kind of brings up memories of attack the clones where Dooku is talking to Mace Windu and Mace Windu talking about Count Dooku and just adds a little extra, a little extra zestiness, a little extra texture to already existing Star Wars stuff that's out there. I like that. That's about it. But yeah, what did you guys think? Those are some things that I thought I'd have reflected on for the third episode of Tales of the Jedi. Let me know what you guys think down in the comments below. We'll do some chit chat. Let's allow ourselves to leather a little bit in the comments, shall we? Thanks for watching. See you next time. That's a wrap.


Within the boundaries of human existence, and as far back as the memories of the most ancient earthlings will stretch, catastrophic space phenomena in the form of Plasmic Energy Discharges occurring in the skies of our planet were documented by the inhabitants of the Earth taking shelter from the phenomena in the most remote locations imaginable. Sometimes these Plasmic Events were a thing of beauty as David Talbot of the Thunderbolts project points out and sometimes they cause scenes of unimaginable terror. In the form of Petroglyphs, the prehistoric inhabitants of this planet carved their documentation of the Plasma Events which is now being deciphered and it shows undoubtedly that the ancient civilization witnessed something that was so outrageous that they sought to document it for all time. Their message has reached us through the ages and thanks to years of painstaking research by Anthony Peratt, it now appears to overwhelmingly show a worldwide documentation of Petroglyph patterns that were actually happening in space and visible here on Earth. Not only that, it also rained down onto our planet affecting life drastically, forcing people to take shelter in caves, the only natural shelter capable ofwithstanding the onslaught happening outside. Now what if we were to tell you that the Petroglyphs and documentation seen around the world of the so-called Squatter Man has been recreated in laboratory conditions? What if we were to tell you that these ancient Petroglyphs match up to Plasma Discharges recreated in a lab with astounding accuracy? Put in the lab as Zenith Pinch, and this was also seen in deep prehistory in the sky of our planet for around a thousand years, an intense inflow of plasma creating an immense aurora that was then shaped by its own magnetic field, a Z-Pinch, and these Petroglyphs are showing exactly what was happening. Petroglyphs have mystified the most curious of our kind for millennia. They are based on every continent with striking similarities and widely regarded as the oldest surviving markings on this planet. They could be thousands or even millions of years old, but definitely dating to prehistory. That is, upward of 7,000 years ago in a very reserved scale of the sense of time with campfire remnants found close to Petroglyphs in Santa Fe, dating to 4,000 years before Christ after Carbon-14 dating. This and perhaps tens of thousands of years ago, there was electrical activity in the sky as Plasma Discharge sequences moved through discreet phases. The explosion of culture documentation seems to have roots directly relating to this and the misinterpretation of these cultural roots all over the world can now be corrected. They were documenting what they were seeing in the sky. But with the YouTube channel Kronos, we intend to help you understand a past that they would rather you wouldn't believe to be real. Wait, do you hear this? In this type of Plasma Discharge occurring in space and as visible from the viewpoint of the observer here on Earth thousands of years ago and also recreating in laboratory conditions by the legendary physicist Anthony Peratt, this shows the edges of the upper disc may appear to point forming arms and those of the lower torso of the apparent humanoid known as a torus may appear to point down forming legs. The underlying hourglass style pattern with many subtle variations not only occurs around the world, it is among the most fundamental forms appearing in highest energy electric discharge in the laboratory. Considered by ancient man this representation of the prehistoric petroglyphs found all over the world in countries including Italy in a region known as Volca Monica one of the largest valleys in eastern Italy. We are again confronted with the squatter man type design which is also seen 3600 miles away in the United Arab Emirates and this is repeated on Hawaii 8800 miles away from the UAE and also appears to be immortalized in the undeciphered rongo rongo inscriptions of Easter Island, the most remote location on the planet and this is continually repeated in Venezuela, Spain, New Mexico, Armenia, Arizona and even in Ghana but to name just a few other locations. That appears to show a worldwide phenomenon taking place in the sky and which appears to have an intense inflow of plasma creating this immense aurora system pinched by its own magnetic field and recorded by the ancients of prehistory as a humanoid figure in the squatting position with arms directed upward. Take for example the Arizona petroglyphs, abstract designs to the would-be observer but according to Anthony Peratt these are in fact very accurate representations of what was seen in the ancient sky in prehistory as he has shown by comparing radiograph imagery to squatter man images repeated across the world by the million count and upward and always located in mountain regions where these ancient earthlings must have sought shelter in the view of the unstable plasma aurora. The conception from Anthony's radiograph matches with shocking accuracy to these worldwide petroglyphic phenomena. They are recorded the same way and sometimes with the two dots at either side representing the Z pinch gravitational influence of the sequence as recorded in the lab, the effects of which are possibly being generated by solar system planets soon to be discussed in this series by the Lost History Channel. Now what if we were to tell you that all these petroglyphs around the world are oriented in the direction of magnetic south all of them as shown at the Arizona site and now realize that all other worldwide locations the artist of all the petroglyphs are in a vantage viewpoint of the magnetic south pole from these locations all across the entire planet. What was happening was the center of the plasma column in space was coming in right at the south magnetic pole generating secretron radiation which was extraordinarily bright and all the petroglyphs around the world seem to have a blinder of some sort that was shielding the observer from the center of the bright radiation and this allowed the documentation in a rock art of these instabilities. It seems these people emerge from the caves they were sheltering in during quiet periods to etch this documentation. It's all oriented magnetic south and this is vital for understanding the direction the aura was coming from and what may have been causing the intense phenomena. The stunning fact is that these artistic designs are only found at locations where the observer can have a clear view of the magnetic south direction but with some kind of blinder protecting the observer from the exposure interestingly they are not found in areas where the south pole is obscured by mountains. Vantageous don't exist unless this vantage is clear and this is a stunning and compelling clue that almost overwhelmingly spells out what was happening. The largest petroglyph site in Europe at Italy's Valca Monica site in the Alpine region also shows that they are in the direction orientation of the magnetic south and they too are putting their rock art in locations that seem to have a limited exposure to the extreme aurora event. The intense cicrotron radiation light if exposed to it which would have disastrous effects if exposed for any length of time and this is again repeated as far away as Australia at the site at Arcary Rock Art Cave depictions. Again, orientated to the south pole with limited exposure in the protection of the mountains but with a clear sight view of the sky. The Babylonians were apparently the first to develop systematic observation of the planets and they recorded the celestial motions with considerable skill but in the laying of the foundation of later astronomy they also preserved a critical link with the past. Again and again they asserted a claim that could only appear preposterous to the modern translator. They declared that the distant planets were the gods of former times. What exactly does it mean the gods of former times? Is it a literal term for these plasmatic aurora events from which the Sumerian and all other civilizations emerged? We are again confronted by the squatter man figure, a literal depiction of events in the heavens in the form of plasmatic aurora and what would later be referred to as the gods of former times by the ancient Sumerians. Sumerian myths say that the rights and standards of kingship descended from the central luminary An. Founder of the Golden Age and in Babylonian myth the Sumerian An appears as Anu. First in the line of gods and kings and according to the best authorities on Babylonian astronomy the god Anu was mysteriously linked to the planet Saturn. Something we will be taking into consideration when addressing the question of what exactly was causing the intense inflow of plasma creating any immense aurora above our ancient sky. But what do you guys think about this anyway? Comments below and as always thank you for watching.


Welcome everyone, this is Jenkins Platform SIG meeting for today, May the 9th. Today we have with us Kenneth Salerno and Damien Duporta, thanks a lot for being here. On the agenda today we have a few open-action items. They are always the same month after month, but one day we'll sort them. We've got some work on Docker agents. Damien will tell us about that. And we have Kenneth with us. We'll talk a little bit about the PPC-64LE progress for the Docker images. And we'll also talk about the latest improvements on the Docker agent images. Hello, Kevin. Let me add you there. Thanks for coming. So for the open-action items, we still have some Docker images. We have to announce the end of support of the deprecation. Let's be precise. So of course the Blue Ocean container, which is not the Blue Ocean plugin. You know, it's a different approach, different effort. I've seen a release a day or two from now about Jenkins Blue Ocean plugin. So it's still maintained, even if we won't have any other new feature added to it. But the Blue Ocean container hasn't been maintained, hasn't evolved for a few years, I think, from now. So yes, it's definitely deprecated, but we have to announce it to the end users. And to do that, we'll have to find a way to announce, to communicate the deprecation to users. And so that's an administrative process. We're still not sure how we will address that. So you will hear from it in the coming months, I'm afraid. Damien, would you like us to switch to your current work about the code factorization on the agents? Yes. The goal is still to target on long-term run having a single repository for all agent images. The reason behind the rationale in that proposal is that all the agents have a common ground. The base image operation, especially when we need to update, let's say, Git package when you have a CVE, for instance, when you need to regularly update base images, et cetera. But also all the free agents have different use cases. So we have the Docker agent, which is the most basic image. And right now, the SS8 agent does not inherit from that image. But both of them need to have default Jenkins user within the ID of 1000. And that kind of, let's say, common ground for whatever kind of agent you run. And then the inbound agents, which needs the Docker agents to be released to pick the change as a base image to only add the shell script and change the entry points. But that adds a lot to the different processes there. So right now, the work that has started, I didn't know where to start. The first step is, before even trying merging the repositories, I'm trying to find code duplication inside these free repositories. Because on the free repositories, we have the same pattern. We have a top-level folder, which is named based on the major GDK version. So you have 11 and 17. And then we have code repetition inside these directories. We have exactly the same Docker file, except for the GDK version. So right now, the goal is to decrease the amount of code on each repository. So when we will merge, we will have exactly the same pattern with twice less code. So I'm currently working here. And this is draft status, but that allows me to get my own dirty with every details on both Windows and Linux. The next step I have in mind, that should not need any complicated discussion on the high level. That will more complicated discussion on the implementation proposed on the draft. But it's more review and testing, more than really high level discussion. That will be to start by merging in bound agent and agent. Because it will solve a problem we currently have today. We had to wait almost one month to be able to deliver a Kenet word about the PPC64. And the reason is not because of Kenet. It's because we had an issue on the inbound agents with the automatic updates that takes the latest base agent updates. We had issues on one of the images that was blocking the whole process. We weren't able to deliver. And now, not only we waste time when we have issues, even when everything goes properly, which is most of the time, we have to wait for a release of the agents and then the automatic update process to kick off, open a PR, pull request, and build again everything for one small change before a new release.  And finally, when we have changes or drifts, the version are different between agents and inbound agents because they all have their own lifecycle. So my proposal targeting merging the code of agent and inbound agents since they already inherit from each other today, the goal will be to have one release lifecycle when there is either one change in the Dockerfile or one change on the inbound version for the remoting component of Jenkins. We create a new tag and both images are released at the same time with the same version. No more confusion for the users. And either it work on a pull request or it doesn't. But we don't have to split the work for both. These are the next steps. For the SSH agent, though, I propose that we wait to see if my proposal is accepted, it's valid and it's working. The reason is I don't want to plan ahead, especially when we'll have an uncomfortable discussion about the lifecycle because the SSH agent use semantic versioning while the inbound and the classical agent are using the default Jenkins plugin versioning system, which is buildnumber.comitid. And we have added a suffix with the package build number when we change something else than the main components. So we will have the decision to make as a community. And that one require discussing before pull requests to see if in the eventuality of we are able to technically merge, do we need one tag each? Do we need to synchronize the same ver? Do we need to synchronize the current version? Do we need to change one or the other? There is no obvious answer that will depend on the community feedback here. And I'm not sure I have an advice right now. Technically, that should be easy. If the inbound agent worked, then adding the SSH agent might have side effects. But globally, the code is almost the same. So that means the side effect will be us surfacing issues that were existing in sometimes, a discrepancy between images. So that will be on the benefit of the user. And if we communicate it well and we do it properly, we should be able to avoid this issue or fix them in the next day or so. So this is the plan. Right now, a preparatory work by merging code duplication and fixing the tooling. Then next major step, merging inbound agent with agent. Only that will be technically complicated. And if everything goes accordingly, then I will come back here and propose the next step with SSH. Is it clear? Does it make sense? And do you agree with this? These are my three questions for you, folks. To me, it's clear. And of course, I do agree. I don't know for you, Kenneth or Kevin. I think it eliminates a lot of redundancy. And I noticed it immediately that in the hierarchy, that it's essentially the same files. But really, we could have used variables to decide what we're going to pull in and what version of what and for which environment. And we actually already are using some control statements with if then for there was a decision that had to be made for one of the architectures. I think it was ARM that we couldn't use J-Link for ARM to compress the size of the JDK. So we already have some kind of control statements in there anyway. Absolutely. For the sake of, let's say, history, there were two reasons why it's as it's today. It's not because the code is bad or bad architectural choices were made. It's because, first, all these images started with the Docker automatic build for official images that require the Docker file to follow some conventions back a few years ago. That is not the case and not required anymore. But that's the reason of why, for instance, we have default version everywhere because each Docker file need to be built without any tooling around. It was the role of the Docker hub to automatically build it. That's not the case in three years now. So we can get rid of that first constraint that doesn't exist. But that explains why we had so much Docker files everywhere because the matrix of Docker file was a list of images on the Docker hub. Now, we have added it since at least one and a half that Docker build is there. And the control statement you mentioned, Kenneth, shows that we can work together the multidimensional matrix tags, architectures, base images, and now custom high-level images. So we know the tooling allows us to use Buildix and we push images directly to the Docker hub. So we don't need the constraint from Docker for official images. And my question to you is, are you going to eliminate the three projects then and just merge them into one project? On the long run, yes, that will be a good idea. That might need a proper way, a blue-green deployment, in that case, that will be creating a new repository, Docker agents, at least on the source code, yes, to your question. So how would you make a decision if you only wanted to build the SSH agent? Would you make that a parameter? Good question. I would delegate that decision to Buildix. The reason is because these images are not idempotent images. We install packages from the base distribution image. So between two builds, you might want to have the latest package that we installed. You don't want to fix the version. It's not a single binary image built with a tool like Bazel or something. Between two builds, I don't expect the exact same content from these Docker images. Because you might have one of the dependencies of the operating system that we installed for the SSH, you need to open SSH as well. So one of the dependencies here, I expect it to be up-to-date each time I rebuild it. So it might change even if I don't change the Docker file. That's why I don't mind rebuilding them all at once. I rely on a highly parallelized process from Buildix, at least for the Linux part, and partial parallelization using Docker Compose on Windows side. However, my proposal is if we see that slowing down the builds for contributors, then we could add a conditional build based on the change files. If the Docker file of SSH is changed on the pull request, you only build the SSH to avoid spending too much time building and change in the pull request. But for the main branch, what do you think to always keep them built? Yeah, I mean, certainly with the inbound agent, you're combining those two make a lot of sense with the base agent. But there's a lot of redundancy in what gets pulled down to build the SSH agent. Yep, absolutely. All the SSH installation should not be part, at least not the server part, should not be in the inbound agent. That's why using the combination of Buildix and multi-stage Docker files would help in that case. You would have only, for instance, let's take Debian for a given version of Remoting and GDK. You will have the base stage that gets the GDK and create the default UID Jenkins with 1,000 or whatever. Then you would have a stage which will be only the inbound agent that takes care of adding the script, setting the default entry point. And another stage in the same Docker file will be the SSH port. The second and the third will be built on top of the common that is the agent today. And the goal then will be to specify different build targets in the Buildix images. So you can say Docker Buildix build SSH targets. That will be described on the Docker bake file to point to say, OK, if you want SSH for Debian, then it's that Docker file with that target so that you'll build the parent image and SSH, but not the inbound in that case. Right. Does that make sense? Yes, because the inbound image becomes its own separate entity after it's built. So just because we refactor, rebuild, we base to, if you were to say, rebuild the SSH agent. While your inbound agent will be based off of an older version of the base, you shouldn't be forced to rebuild it if you just wanted to build the SSH agent. Yeah, that makes sense. So OK, I like it. And also, another compensating measure to fight against the behavior you describe will be to start with a regular schedule for releases. Like, I don't think that will kill or cause problems to release once a week. Every week, let's say Thursday, we have an automatic process like we do for the weekly core Jenkins release. The process will take the latest master branch of the whole set of agent, rebuild everything. And if everything old test pass, then it tags it and release this build version. So then that will be a regular schedule for end user. They know that they will have the latest package once a week. And all your changes will be released on a predefined schedule, unless if it's, let's say, an emergency like security issue. If you as a contributor have something merged, let's say, during the weekend, you know you have to wait until Thursday for the automatic release to deploy your change. That means some change might be slower, but it's deterministic and it's regular. So in terms of packaging, security scanning, and habits from the operators that consume the image, they know it's a regular schedule. Yeah.  I would say worst case is if there is a security issue that can be exploited in the image from last week. But in that case, there is nothing forbidding to manually create a tag and trigger a new release outside of the regular schedule. All right. If it's a security issue, you can trigger a rebuild. Exactly. The weekly cron would be really, really, really simple. In my mind, in my proposal, that would be, OK, if the master branch passes on Thursday when I'm triggered, then I create a tag and no more. And then we will keep the current behavior that say, oh, if you have a new tag, then you will build an image with that tag and push it. What's the current release schedule for the controller image? Because I've noticed the war version and the checksum look to be like 2.3 something. And I know that we have 2.4 being built. And so I always manually specify that. When are we changing that in the? So for the controller, we follow the Jenkins score releases, which means you have two lines. You have the weekly lines, which is rebuilt. Each time we have a new weekly release every Tuesdays. Once it's released in terms of packages and war, then the images are rebuilt. So you can expect a change every Tuesday. So if you want to use the weekly line with Docker image, I recommend you to update every Wednesday. But I have to manually specify the version and the checksum myself. Really? No, you're not supposed to. No, no. If I pull down right now, if I do a git clone on the head of the Docker. Ah, on the source code. You mean, oh, that's different. Sorry. Source code, you have the master branch. How does it work? There is a script that takes care of building the tool, ensuring that the tool last weekly and the tool last LTS. Sorry. We don't have a mapping of the image with the Jenkins versions. The master branch is the latest. And the script takes care of rebuilding every version, specifying manually the version on the build.org like you probably are doing. Yes. You can, yeah, it's an environment variable. And you can specify the path or just the version, actually. And then you have to specify the checksum. Yes. I would not expect any kind of support by default on rebuilding yourself. Because the support which is made by the maintainer is on the build artifact pushed on the Docker hub. The source code is a different matter. Because otherwise, that will be really, really, really complicated to support all of the use cases. If you have to support all of the combinatorial way of building with a given Docker file, every ways to use it, that means then you will have to ensure that the Docker file work with Podman, with the other build container like KaniCo. And that one is already a challenge. Because then we need to validate it against all the building versions with or without the experimental features. Then we need to create, to test all the combinatories, meaning all JDK version of build.org is combined with all the Jenkins version with the checksums. That's an exploding combinatorie. And supporting that is really complicated. Anyway, the main constraint here, that's why you also don't want to go too deep, is for the controller right now, we are tied to using the same tag version for the Docker image and the Jenkins weekly. And if we need, for instance, that's the problem we had, we need to update Git version on the controller image. That's really a challenge because that will need to wait for the next weekly or the next LTS trigger. Right now they are bound, so you need to tag a new Jenkins release in order to release a new Docker image. For the last security issues, when they were exploitable, we added the Docker image suffix, but that was a temporary measure and it's not sustainable. That's a discussion about the lifecycle of the controller image version. The question is, shouldn't we use a package suffix or something like we do for the agents? It sounds to be working with the agent, but there were people that were against that. So the question is, do we consider a one-on-one mapping between Jenkins and the image? That might help on the topic you're on the line because if we change a different topic, then for a given version 1.0.0, I'm saying arbitrarily, or X, I, Z of the image, then you note that version has a fixed version of the Jenkins checksum and version. So you have a deterministic build even with a source code in that case. But that will change the way we build and manage the repository. Thank you, Damien. Sorry, I will have to interrupt you because I'm a timekeeper and it's super interesting, but we won't make it at 30 by the hour. Anyhow, we can always discuss that on community Jenkins.io on GitHub or in the next meeting. Thanks a lot for your questions, Kenneth. So if you don't mind, let's switch to what has been done and we'll also talk about what you've been doing, Kenneth, with the PPC64LE because your Docker agent, SSH agent and inbound agent, PRs have been merged. Congratulate that. And your control PR has not been yet merged. I don't know why it has been reviewed. Do you have any input info, Kenneth, about that? No, I'm not sure. I think we were waiting for a review, right, Damien? No. Sounds like yes. To be quite transparent, I focused on the agent now and then we had some delays, so I'm not sure what are we waiting for here? Yes, you're correct. Based on what team you fixed the issue team pointed. So yes, what you say is true. We need for the maintainer to review it and see if it's okay to merge it or not. At first sight, I don't have any objection, but I'm not the only maintainer that should check on this one. Okay, yeah, I think we're just waiting. I think it was Tim who was looking at it, right? Yep. Okay, so we just have to see when he's freed up. As far as the agent and SSH agent and inbound, I tested all three of those and the ones that were pushed to Docker have been there all working. Cool. Good news. Yeah, I did uncover something interesting about JDK 15 where they changed the V fork to PASX spawn for shell, J and I execution of shell to do an exec to copy the parent process and fork to the child. And under QEMU emulation, PASX spawn seems to be broken, but I could fix that with a JDK parameter, just to specify V fork, but that was my only catch, but that's, you know, nobody's gonna be emulating these images, but me. That makes me think I might bother you, Kenneth, on a plugin, the durable task plugin, because there is a side project named lib durable task that sounds like to be a go long binary. I understand it's that binary is used for persisting pipeline when there is a restart trigger. It's part of the whole pipeline workflow suite. And recently there were a discussion and a per merge. Someone added PPC 64e and arc support for that go long library, but there is no tests. The main reason is because it's a plugin and we don't have a PPC 64 machine on CI Jenkins. But on that area with the age on PPC 64, we could start with QEMU as a first line of testing, but I might need your expertise there, if you don't mind. But I wanted to ask you before, if it's okay, if I ask you directly on the pull request to see if we can help the plugin maintainer, are you okay with that? No, it's okay. Yeah, and I have a test environment where I actually run these containers through the emulation and I also have somebody who has real hardware, so. Cool, sure. And at the same, on our side, on the Jenkins infrastructure, we are still able, I think we should request the OSU OSL for a one or two PPC machine because it looks like they have some. So that could add also real hardware for permanent agent on CI Jenkins. We used to have one, so there is no reason we cannot find another one there. And that might help as well. I will let you know once we have a feedback from them. All right, go ahead, Inia. Those machines are available for us to use. Thanks for your help. Of course. Thanks a lot. Yeah, we won't have time to do all the subject, but there is one which is very important to me. It looks, at least to me, very important. That's a drop support for GDK8 for the SSH agent. At last, Damien, a few words about that, please. So yes, that one, we forgot to take this one back in September. So right now, if you were using this, then you have a problem. The main idea is that your controller should have the same GDK major version as your agent, at least for the GDK use for executing the agent process. If you have, and that's the case on the official Jenkins infrastructure, if you have needs to build a project, a development project on an agent with GDK8, there is nothing restraining you to have a GDK8 installation that you use with your Maven, Gradle and your project or whatever way, but it's still recommended to use another GDK for running the agent. And you can define which GDK is used for the agent process on your controller setup, either a Permanent or FMR agent. We use that since 1.5 and C agent in SIO. So if you have that problem, use the latest GDK11 or 17 depends on your controller, same major version, and you extend the Docker image and add your own GDK8. The change logs shows a draft example of a Docker file for this, if you have that use case. Other than that, there is no reason to keep using GDK8 since Jenkins use this GDK11 by default since September, 2022. Except if you want to get in trouble, I guess. So, oh, the time is finished. I'm afraid we'll have to wrap it up. The agenda will be compiled on the community.genkins.io we'll create about that. And the video should be available on YouTube from 24 to 48 hours. Thanks a lot for being here. Thanks a lot for your time. We'll see maybe each other 14 days from now. Have a good rest of the day. Bye-bye. Thanks. Thank you, bye-bye.