Before we end, I wanted to acknowledge and announce some native plant awards to two couples that have done some fantastic work in Kentucky. So let me share my screen real quick. Okay, so this is the first year that we're going to give out awards. There are so many folks that are doing some great work in the state. But I really wanted to highlight two groups of folks that have done some fantastic work. So first the native plant stewardship award. So this award this year is going out to Jeff Nelson and Liz Nehoff. This is an award that actually is going to be given out by the Office of Kentucky Nature Preserves, but the native plant society is now also going to adopt, giving out native plant awards as well. So this award is being given to Jeff and Liz from both organizations. So just a background on Jeff and Liz. Jeff Nelson was born in San Francisco, California, and grew up in Sunnyvale, California, he received a BS in chemistry from the University of California at San Barbara. And Liz Nehoff was born at home in rural McCracken County, Kentucky. She received a BA in sociology from San Jose State University in San Jose, California. Jeff Liz and their son Aaron moved from California to McCracken County, Kentucky in 1987. So after building their house on their 10 acres, the family has spent the last 30 plus years restoring the property from farmland to native woodland. Jeff was employed as an IT director at of the of the Paduca Independent School District for 15 years retiring in 2008. So hence Jeff is our webmaster he is an IT guru. Liz was self employed for many years as a gardener and landscape designer and has spent much of the past 30 years removing exotic invasive species from their 10 acre restoration. He has been a member of the Kentucky Native Plant Society since the early 1990s and Jeff has been on the board of KMPS since 2017. Since 2019 they have shared responsibilities as nature preserve monitors at Metropolis Lake State Nature Preserve in McCracken County. And as lifelong amateur naturalist Jeff and Liz love exploring Kentucky and learning about the rich diversity of the Commonwealth's many ecosystems. I can't say enough about Jeff and Liz I absolutely love, love them so much. You know from their work on invasive species. Jeff's work and now using iNaturalist and mapping different interesting plants that he finds. Rare species updates, general preserve monitoring. Of course, Jeff is also our webmaster and esteemed board member. The restoration of their their property is just fantastic. They also do native work at restoration on their property and work with partners to increase increase native orchids. And they've volunteered for our roadside native plant project. So just just some amazing people. Not only that they're amazing nature photographers. They also manage the Native Plant Society social media pages and their content is regularly shared and loved by thousands of nature enthusiasts. And I also wanted to just to just mention, you know, often when Jeff posts different photos Liz is always hiding in the background so I'm always trying to find where Liz is in the photos. And she's here and she's also an amazing poet. So, here's a poem by Liz Red Fox sits beneath the black cherry tree, knowing only Gray Fox perched above could climate with patients of Job eyes ears on point Red Fox six and weights for rain of Gray Fox's feast. So, thank you Jeff and Liz for all of your work from, and this is from the Native Plant Society and the office Kentucky nature reserves. So, Jeff and Liz I don't know if you want to say a few words. Where are you guys can can you. Yeah, yeah. Can we highlight everybody. Let's see. Make sure that you guys are spotlighted so that we can see you. Okay, yep, we are. Okay. Let me tilt the thing. Yeah, just thank you for that that's that's really nice and thank you for everything and Liz said when we started, we're now 30 years into a 200 year restoration project. And so, we just love native plants and all the critters that depend on the native plants so indeed. Thank you all very much. Awesome. This will go on. Never give up. Thank you so much. And look to our newsletter for more information about Liz and Jeff, we're going to be creating an article about this. All right, so I will just want to mention one other award. So I'm going to give you an article that will be giving out and highlights the work of and Milligan and Steven Brown with the native plant diversity award. So some of you folks may know and Milligan from social media posts on Facebook from the Louisville seed swaps. I'm going to put more background on and Steven so they currently reside in semi rural southeast Jefferson County, and as an oil painter and Steven Brown is the author and historian. So over the past 12 years they have transformed their yard into a native plant sanctuary. We all know the work of Doug to Lammy's work bringing nature home promoting native plants and gardening. Among other things, well and and Steven are just as inspirational and our Kentucky heroes in that regard. This show us how the power of just a few individuals can start a movement and inspire others to join them. So over the past 12 years they've transformed their yard and realizing the amount of native seed that they were producing. They decided to share their love of native seeds and start seed swaps and that has been just wildly popular throughout Jefferson County. And they just wrote a book. I have it here called you can't see it because of my background but let the earth breathe and I encourage you to find that and get yourself a copy just to learn more about the details of and and Steven's work with their native plant restoration in their yard. So this is a and also just recently started a nonprofit let the earth breathe to about this restoration process and the seed swaps and there's also some really great Facebook groups for the seed swaps to join particularly if in your if you're in that region. And and just wrote an article for the native plant society on this process and encourages everybody to start their own seed swaps across the state. So those are just photos of the recent seed swaps. But I just I've just loved watching over the past couple of years, this develop and so excited that and and Steven have published a book so and I don't know if you are on here. Yeah, but I don't know how to make myself. Okay, Jeff will spot Jeff will spotlight you. Okay, thank you Jeff. Okay, so do you want to say a few words. There we are. Hey, all right. First of all just want to say really quickly because we're almost at the end how much I've enjoyed this. This symposium I've been here since the beginning today and I'm absolutely amazed at the amount of work that's being done. But this are amazing people in the world.  I'm really, really impressed. Right. So what we are in Kentucky is we're serving we are suburban nights we, we love the well but we live in suburbia and our job is to make sure that suburbia plants native species in our yards and we want it to start with our neighborhood and we want it to spread out to our city through regions and then we want it to spread from our regions around the state. And just want to say that Margaret Shay at drop seed nursery is sort of the core she sort of the native plants guru of our area and we started our project she's who we went to and in the end she'll be the one we go to. And it's such a resource here and we're so so honored to be a part of extending what they're doing at drop seed nursery out to suburbia so thanks so much for asking us and if you wanted the book you'll you can learn everything about where we're at and where we're going we hope we're going at lettheearthbreathe.org you can buy the book there you can read up on what we're doing you can keep up with what we're doing on lettheearthbreathe.org and also you can buy the book let the earth breathe on Amazon. By just clicking in let the earth breathe book and also on our website lettheearthbreathe.org thank you. Thank you so much. All right, let's see. So I was going to open this up for any questions or comments. Originally I was going to do a native plant stakeholders updates for folks that are doing some really great work across the state on on other native plant projects, we don't have too much time but I encourage folks. You know, if you're whether an organization or an individual if you're working on a really awesome native plant project, you know, write an article for the native plant society and we can and highlight your work. Let us know what you're doing. And just just communication. And yeah, Heidi do we have any questions or comments. There was one question for you. If we find a population of an unusual or rare wildfire what is the best way to contact you with info or photos. Yeah, so I can provide my email. If you wanted to email me directly I know what Vanessa had talked about with a naturalist and in our, you know, rare plant volunteer programs that we're trying to start on i naturalist that's also a good way. And with rare plants of course we obscure our data. But you know if you put a rare plant on i naturalist, you will get contacted by me or Vanessa or other folks at at nature preserves and we'll get that but yeah I can put my email down as well. If anyone want to contact me. Jeff you got something. Yes, I did. I have a question. When are y'all coming down here.


Britain has denounced France's seizure of a British boat in French waters. It has also warned Paris against further retaliation in a rapidly deteriorating row over post-Brexit fishing rights. There is more in this next report. France seized a British trawler fishing in its territorial waters without a licence on Thursday. It also issued a warning to a second vessel as a dispute over access to fishing grounds after Brexit escalated. France is furious that Britain has refused to grant its fishermen the full number of licences to operate inside British waters that France says is warranted. And so, from November, it's over. Clermont-Bone is France's Europe minister. It's time for us to get respect. It's done by the fact we issue threats and pursue dialogue till now. It allowed our fishermen to have just over half the fishing licences today. We have to also see the glass half full, but that's not enough. Not acceptable at all. Now we need to speak the language of strength, as that seems to be the only thing this British government understands. The French government said it would from November 2 impose extra customs checks on British goods entering France. That raises the prospect of more economic pain before Christmas for Britain, which is facing labour shortages and rising energy prices. It's also reviewing a second round of sanctions and does not exclude a review of its exports of electricity to Britain. France's seas minister on Thursday told French Radio, It's not war, but it is a fight. Britain condemned France's seizure of the fishing boat as disproportionate. It says it's fully in compliance with the rules of its post-Brexit trade deal and the European Union, and wants further talks with French and EU officials. Let's talk about fresh news updates.


Thank you for joining. One more call. So this call today is dedicated to, let's say, a focus on data repositories, on research data. How do we manage to aggregate content providers that are providing research data records and how do we have this research data in our research graph, in our infrastructure. Let's say that this is a community call to clarify some issues regarding the content acquisition policy and what we need to change in our guidelines to address some challenges regarding the research data. Because OpenAir is just starting a campaign to have more data archives that the repository is registered in OpenAir infrastructure. So this is one, let's say that this is a way to start this campaign involving the community, involving those that are, in fact, providers of OpenAir. So let's start with, usually, as you know, we always have a topic on some updates. We like to share some news or to some highlights regarding the provide service. Then our focus will be the research graph and data repositories, the content acquisition policy, and the changes and the updates that we are doing to the guidelines for data archives. And how can you also contribute and provide the feedback for this public consultation period that we are doing, that we are running right now. So let's say, first we start with this news and updates, then we have Paolo Manghi, the OpenAir technical director, to discuss with you about, to present you the research, the OpenAir research graph and discuss with you about the role of Natalupuzitri and the expansion that we are doing within our content acquisition policy. And then we discuss about the updates, okay, together. Okay, thank you for joining this call. Let's start with some news. The first one, you know, so but it's always important to highlight that we have, we did a redesign of the provide service. So it's available in production since April. We are doing slightly slight changes. We did, in May and in June, several tests with 10 repository managers. From those tests, user tests, we are selecting those issues that in fact we need to change or to improve a bit in the layout of our provide service. The user tests are always important for any service, but it was quite important for us. We did all the redesign of the service, based on input from workshops and from service that we did last year and yes, last year and early this year. But we realized that we need to change and to update some things in our layout in order to address some difficulties that during the tests we realized that the repository managers and the users of the services have. But I think we are quite happy with the service that we have now running. So the changes are big. If those that those things that are really, let's say, a big change in the layout, we will postpone it to a second version of this layout, but so other changes we are doing. So broker events, we have already highlighted that in the, not in this last newsletter, but in the previous, but as we didn't have a call, a community call in June due to the open repositories conference. So just want to highlight that in May, we have generated updates in the broker events. They are available. Also in provide, you can check it. And it's important to say that we start receiving some and also as a result of some user tests and some complaints about the notifications via email. In fact, we had some issues sending notifications via email, putting available the information from the broker events in the notification area of our dashboard. The technical team have already realized and solved those issues. And we will put it available as soon as possible. So what are we going to do is that we are going to clean the notifications from all the users and generate and ask you to generate new subscriptions. And we will start to generate properly these notifications and sending via mail properly the notifications for those that have asked to receive the notifications via email. So this is important. Your feedback was important. So I think problems are more or less solved. We will put it in production as soon as possible. I also need to check some with some colleagues. If they are here, they can also provide information later. But so when are we able to do this? But we can already say that I think it's important for you. Some of those that are participating in this call in fact have reported this error. I will ask my colleague Andrea to share the link for this other new. The Canadian Association of Research Libraries together with OpenAir, with the participation of the company for science have developed plugins for this base version 5 and version 6 to comply with the OpenAir guidelines version 4, the literature guidelines version 4, which is good. OpenAir is quite well aligned with the release of new versions. The version 7 will be much aligned with our last version of the guidelines, but we are aware of some limitations because the previous versions are not compatible by default. So we are all together in this work to promote this global interoperability and it was great to have this contribution from the Canadian Association of Research Libraries to support, to sponsor and support these developments specifically for this space only. So when we want to highlight these developments in this call and to share with you, so if you are not aware we also published yesterday in the newsletter, but Andrea will also share here in the link for the news item for you to be aware of. This and the last novelty before we have Paolo Manguidas, it's about the user statistics. You are aware of some issues with the user statistics service and the availability of proper figures from the user statistics in provide service. It's important to highlight two things. Statistics real members are already available in Explorer. In the repository page, in Explorer, in the providers page, you can see the numbers there. They are correct and in the different places of explore when it comes, when it relies with the information that is related with each repository provider. The numbers are not in the statistic information, it's not fixed in provide service. We also have some colleagues here responsible for the user statistics service. If you have questions, please ask. We can reply these questions in the chat or later here in this call. So feel free to ask questions about this. So I will not reply now. I will maybe buy a shot, but later we can answer. So we can make comments or if you find any issue just share with us. So for the user statistics specifically, we are gradually performing all these corrections repository by repositories for those repositories that have enabled already the user statistics service. For the new, it's not the problem. It's only a problem for those that have already enabled this year, last year, two years ago, the service. So we will fix this, but for the new, we don't have any issue. Okay, these are the highlights. There are other things that are also interesting. So in the previous, in June, in June, we have invited you all to participate in the session during the open repository, the open repository conference session where Paulo Mangui, in fact, was also Paulo Mangui, have presented the COVID gateway, open science gateway that we have in open air. So it's another interesting novelty. It's a different service, not the provide service, but I think you need to be aware because the content that you provide to open air is also available in that gateway. So it's another novelty. So there are other things that are also new, which is important to my life, but I just want to highlight this for specific information. So let's move to the next topic and we'll invite Paulo, the technical director of open air to join me and to do this presentation in order for us to be aware of research that the data repository is in our infrastructure and what we want to change, what is new and what we want to promote in the coming months. Thank you Paulo for your availability. Thank you all. Let me try to show my slides first. Can you see them now? Yes, but not the right one. Okay, wait a second. It's always an issue with selecting the proper again. Okay, so let me go through quickly about this presentation. So you know a little bit already of open air, but what we're trying to do at the technical and networking level is in fact to facilitate this process. So bridging the work done by scientists and the world where the results are published. So making these two worlds as connected as possible, possibly transparently. So what we would like to happen ideally is that the scientists perform science and all these results or her results are being published automatically on his behalf and of course prior authorization by the machinery he's using. Exceptions made for the of course the narrative part of which the scientist is in charge, but we can surely dream of a world where this process, especially facing the needs of open science would be dealt with mainly by machines, right? So open science requires us to publish the whole process and this requires a lot of manual effort if we compare it to the traditional procedures unbearable. It's one of the barriers we know. So open area is working in that direction. So aligning globally and all these activities which are necessary for this paradigm of open science to be implemented. So for that technically speaking, so I'm skipping the networking part, we're providing a number of services. The layer at the bottom as you can see shows the number of services in support of publishing science from data management plans with Argos, Amnesia for anonymization of data, Zenodo for storage and say persistence of data, long-term preservation of data and as well as other services that are allowing us to bridge again to automatically publish from thematic services to data sources, scholarly communication data sources, our scientific results. On top of that, we build another set of services which are there basically to monitor the quality and track how science is doing overall. For example, in School Explorer we build a collection of links between publications and data sets and we develop the interoperability guidelines which you've heard of several times. Together with the communities this is the most important thing I think so these are not top down but the results of the bottom-up process which involves the communities as Pedro stressed before. We provide usage analytics and brokering. And on top of that of course we build the added value services that we can obtain by working on this content that we're collecting and coming from the services below but coming also from the institutional repositories and coming from the data repositories which are the subjects of today's talk. So what we are building at the core is what we call the Open Air Research Graph. We call it a graph because it's a metadata collection of entities of different types so in the same data collections you have objects which belong to different and describe different kinds of objects for example publications, data, software, projects, authors, organizations, all these are of different kinds they have different properties but at the same time they're connected by semantic entities relationships sorry so semantic links which somehow determine the kind of relationships between the two objects. For example this object is hosted by this repository or this object was funded by this project or this publication was supplemented by this dataset so this is why we call it a graph. In order to build this graph we have to collect metadata from several sources data sources which we stress should be as aligned as possible in terms of the metadata they expose and how they describe the entities they host. As you can see we are collecting from a variety of sources as well so we don't focus on one kind but we try to collect from all sources which we believe are trusted by scientists. Trusted we mean sources that scientists typically use in their daily activities community specific ranging from community specific to cross community ones or to scholarly communication services like ORTID or as you can see on the left side or data side crossref from the thematic publishers and thematic repositories but also to the aggregations of those which in several cases provide us with a lot of added value for example ampewo Microsoft academics is one of these samples also from open citations and we range out to other kinds of products like github for software and research software etc. We include funders and as a specific case also research infrastructures so we are trying to open up and reveal give the dignity of research results to products research outcomes which are typically hidden by the the services that we know only recently we made a step towards data research data we were used only to publications in open air we're trying to go beyond that so we include other kind of products in the research life cycle and for the evaluation and assessment so how we build the graph we collect from 12,000 data sources roughly we build the raw graph then we deduplicate the content of the graph because the same records can be collected from different sources and we enrich the graph after this this step by full text mining we have about 15 million PDFs on top of which we perform mining in order to infer links between entities typically this publication has been funded by this project or this publication is linked to these datasets or to this piece of software and we create the corresponding entities in the graph so we build the graph that is enormously and much more richer than the one that you can build but just by collecting the metadata. On top of this we propagate this content so that's a nice activity because we thanks to the relationships we can propagate the contextual information of one object to another object that is related with it for example if I know that a project has funded the publication and the publication is supplemented by a dataset I can easily state that the dataset is also being concerned with the project and it is related with it so on top of the graph we provide the number of services we expose the graph through APIs, dumps, etc and we build the number of services for discovery and monitoring mainly but also for example the added value that we provide we provide so from the graph we can of course redistribute the information to the original sources when we are able to enrich their metadata records so let's keep going here I'm not going through this it's not so interesting of course we include registries so we rely on existing registries we are not reinventing PIDs we're not reinventing the wheel and these are just the least of the ones that we have we count today 30 funders roughly with 300 and dot sorry 3.5 millions projects and the inference we perform we do it at the level of the project so we can tell exactly with a 99 98.8 approximation rate that a publication is related with the project provide provide was just mentioned several times here so one activity that you can perform if you're a data source or content provider is to register your service to provide this means that you you have you need to have your source data repository for example register to with the data in this case if it's a data repository we push for this because we want these services to become the way the way we normalize and we align the information about data sources worldwide once is in you can point to it from open air and start your activity of data collection metadata collection the first step is of course to make your repository compliant to the guidelines you can validate this process through provide so get feedback on how your metadata complies to the guidelines to different versions of the guidelines and get a report on how to improve it and of course you can have other added values like the measure like user statistics and also the enrichment of the metadata through the broker which you've heard about before now let's go through these you register etc data content acquisition policy this is an important thing so if you go today to the production portal of open air you will notice that the majority of the objects inside are open access and that's because in the previous era of open air we were mainly focusing on open access publications so we kept this rule because the commission wanted that was part of the tender so we had to measure the ratio between open access and non-open access publications funded by ec projects and that was the deal in the beginning so we needed to somehow measure the taking the take up of the mandates of the commission the open access mandates then things changed so what we are currently doing today is to build a broader graph that contains all possible objects out there independently of the license so that we are able to measure the trends in europe and worldwide in fact we respect two different funders not only to the commission we respect the resource communities and measure research impacts and monitor their attitude so we changed the content acquisition policy for this so we collect everything as long as it complies to guidelines first of all this is the most important thing and as long as it is material that is related with research okay so if you take a look at the guidelines as they are you will have a deeper pick in the next presentations you will notice they're based on standards so we are not reinventing the wheel building application profiles on top of that thanks to again agreements with the communities so you should consider the guideline an evolving product with which you can play you can give feedback and together improve and make evolved in the future now the important thing is that when we collect metadata records ideally we are talking about data repositories later to repositories but we don't really believe it so apart from we see we see repositories that let's say they are pure from this sense they only provide data not as exceptions but like specific to specific to two disciplines mainly most of the time we tend to consider data sources as hybrid so for this reason every time we collect the metadata records from from a source we inspect the specific type or resource type of the object and we try to map it into a meta category of the graph publication data software or others okay so data repository like to know they may contain for example research soft or it's the same for fig share it's the same for publication for institutional repositories which in several cases contain data and software so we try to remap the objects where they belong so in the classifications in the neater classifications that we have in open air so this is a general process you have to take into account so if your repository is not purely data we don't mind okay we also include other stuff and you should make sure this stuff is properly described in your resource type so that we can map it to the proper place in the proper classes uh added value services i'll be uh quick here but i wanted to touch on this it's very important what you get out of this so once your data source is open air what do you get out of this well of course more visibility and discovery etc but there are other things that are very interesting the first one is the broker when we collect one record from a data repository for example we throw it into the graph with the duplicated so we put it together with other similar records if the data set has been deposited somewhere else for example and we build links around it right so we can we may find a link between the data set and the project with data set uh and an orchid id you didn't have for example we bring them in and the good news is that we can send this data this metadata back to you so you can in principle enrich your collection make it more complete than it is uh thanks to the broker this is the first benefit of course discovery as i mentioned before once your data set is in it reaches out different communities which we're serving today so through the graph uh you may provide your content to specific disciplines or to cross uh discipline search or to funders uh research impact is another important aspect so we provide research impact for example for egi for the main research infrastructures for rda itself but also for the commission so as a result of that your data sets will be exposed for monitoring uh to all scientists who want to report them to the commission and this is where i want to show you the integration with third party services the ec sigma which is the portal for example the from the commission the participant portal will show all the data sets potentially related with the project to the uh project coordinator or to the person on behalf of which the coordinator is uh uh reporting the collect the the research outcomes so you will be provided with the list of data sets related with the project and be able to select them scopus is the same thing so if you expose your links through uh your data site uh uh metadata links from your say your uh research data set to publication these links will be exposed to scopus they point to us they point to our apis in order to resolve the links and we'll be soon fully integrated with orchid so orchid users will be able to access the open air integrated access with open air and therefore select all the products which go well beyond the publications and then can include the data sets that are provided by your repository all content is available through open apis and dumps so you can in any case um be sure that your metadata will be made available for science for research for innovation for anybody who wants to build added value on top of that i'm done so uh if you have any questions i'll be happy to try to answer i mean if many thanks paul yes please feel free to um so you don't need to use the in the chat if you want to just use your microphone just ask questions feel free to to to join and i think this is the what what paulo have elated now in one of the last slides regarding the integration with the the third parties i think it's a it maybe it's a novelty for some of you and it's quite important because when paulo mentions that um so scoppers or sigma or orchid uh will use or are using open air so in fact they are using open air open air content open air edis and they are um linking to your um to your um content so the content that the open air gather from from from you and we have we we collected in in open air infrastructure so feel free to ask a question so i will or i will continue it with the two or three more slides that i have just to highlight the changes in the in the guidelines and how can you participate to align with this new content acquisition policy but um you have any question i know that we have we have one question in the in the document that we usually let me check if there are but it's not related with this presentation i will i will reply to this question uh at the end but it's it's not related with paulo presentation it is a a technical issue regarding the place repositories but i will answer okay so if you don't have any questions uh is fine don't worry uh i'm always available for that so uh yes just just just to stay with us because uh so yes you finish the calling in in 30 in 23 minutes we will we will for sure there will be questions let's see let's see okay thank you paolo just uh we'll just share the screen just the white light um okay just um okay uh i will skip this you can you can check in the slides that we have already shared things about the content acquisition policy so specifically for for that archive managers for the our data repositories uh for several of you that i know that are participating in this call that have this hybrid repositories in in your institutions for example that paolo mentioned some some of you in fact are um have a repository that is providing publications and also have registered the same repository the different collection to provide also data but there are other participants here that have um the specific data repository to be part or that is already part of open air so um regarding the the specific guidelines that we have for that archive managers for that repositories uh we so we we are preparing a new version of these guidelines to align basically to fully align with our content acquisition policy that is much more open regarding research data and to align also with the data set schema so we have already um our colleagues from Billerfeld University have already prepared a draft that is available that is publicly available in order to make the process of feedback easier and you can comment so it's really a draft that is in this link available for you to to to make comments uh what is important to say is that uh okay uh this version three of the guidelines for that archive managers um are so uh aligned with the data set the the last the the schema version for that three of that a seed and also use additional vocabularies for example from co-art vocabularies instead of the the old info or repo that in the literature guidelines we don't have it so we need also to update the this version of the guidelines in order to avoid this um this alignment between the different versions of the of the different types of guidelines so this is important to there are some also alignments with with the the vocabularies that the the confederation of open access representatives have available regarding the access rights for example um and so we also uh want to to update the the guidelines uh to align with the fair data fair data principles and also with with plan s so you can check the draft that we are already available in this in the following link so um let me put also here uh so you you can check this information and also um how to contribute to the with with comments so for sure we will have another call where we we can dedicate some time to to some details of the of of of this new version of the guidelines but feel free to visit this this page uh to comment we also have a google document where we where we want to receive your feedback uh so this document was already available we also share this document in previous in previous calls or in some workshops that we have organized already but feel free to to contribute to make your contributions there and provide your feedback but you can also use directly the the open air guidelines github repository to uh to to create to to create an issue and the and the and the suggest changes um so basically this is what we want to to highlight to say that we have this version that is aligned with the new content acquisition policy uh and it's something important in order to facilitate the registration um you can also check this google document where you can contribute so maybe andre is also sharing these all these links in the community call just to highlight you you all are aware of the registration process um and paolo also shared a slide i just want to i put just here an arrow to just to say that um it's important to to say that if if uh so let let me just because i forget here it's important also to to say that these new guidelines so we don't have any more this concept of of a specific set for data okay um if you have your data your and if you can expose the content from your repository um uh based on the on the specifications that we you have but you don't have a specific set uh uh to comply with the the previous version so just just register your repository this is what i want to highlight so um just register then we will provide your feedback if we we have any issue but in this process that we don't have the new version of the guidelines but we also want your content your data repository to be registered in open air feel free to register to and then we will check uh if there is if you need to change something in in your interface um but but feel free to do that because there is now it's um in terms of support and the way that we disseminate properly the information is a strange period because there is a disalignment between the last public version the final version of the guidelines and the content of position policy and what we want to proceed so in between in this process i hope that after summer we have already the final version of the guidelines and there is a full alignment and also our validator is aligned with the last version of the guidelines in between because we have this this alignment guidelines validator and content the position policy feel free to check the draft to to register uh and then if it's not possible for us we will provide the feedback but uh you don't need to have a successful registration against the version two of the guidelines to be available to be registered in open air so we will we will do that for you and we will provide your feedback somewhere in september october i hope that we will have the conditions to have the all our services aligned from the guidelines to the validator in order to provide appropriate support for you okay i just want to i like you this information so you already so you are aware that you need to be registered in the in our alternative data opposite redirectory with redata to then to to to request for registration in in in open air okay so this is the information that i want to to give after paul's presentation is there any question so we have one question here in the chat in the chat now in the google document regarding the the space values okay so the the do the dc type values in this space have to be the same values as required in driver to be compatible with open air so i will reply but so we have other colleagues from open air that are also here available if if they want to jump in and to answer but so we have in the inversion in the previous versions of open air so the dc types were fully aligned with the driver now the dc types that we are suggesting are aligned with the coir vocabularies types okay um so please check that so there is there are the those that are in driver in previous version of open air guidelines and now there is a new let's say list of types that we use that it's global is a result from the confederation of open access vocabularies a working group so we are aligned with that specific and one of the vocabularies that we are using in our guidelines is the types resource types from coir but maybe in this question there is another explanation if i well understood so so you can you can map you can use the type of type that you want to use in your repository you can align with something internal or you can align with the the driver or the coir resource types but what we open air ask is that you need to map your types to those that we have in our guidelines so whatever you use what we want from you is that you can expose the types aligned with our types so um you can use different types in your repository for internal reasons to comply with the internal procedures uh of course there are types that are a bit universally like article book etc but you can use your types your list of types that from my perspective should be aligned with the with standards but then what you need to expose is those that are aligned with us so you can transform you can map and expose your your types compliant with our compliant with our guidelines we have another question for me because if you want to to to put your questions in on using the audio you can do it we are installing an institutional repository within venue rdm and there is a link to open air as far as we know is there an only is that only a technical link or is there a need to fill inform or to apply for the connection to open air just as okay okay so you if you are if you are installing the venue rdm solution uh you need to to register your repository so first registering with redate and then resisting in open air I would like to have contributions from from from our colleagues from from CERN that are managing the venue to understand this question of the link because the link the direct link that we have is from Zenodo it's not from a standalone installation but maybe there is something new that is also new for me which is good no problem that they they know so if we have any additional comment we will put it here in this document but the first answer is yes that you need to register but I will I will clarify this direct link from this new venue rdm software platform if there is anyone in this call that can help me to just jump in and help me with this answer but um Brianna is there any improvement in procedure or workflow for clean the data for organizations okay paulo this is a great questions from our colleague Brianna that you may want to to answer I think in one of the previous calls I have already a little bit open the the this new service that we want to to have in open air to to create organizations but maybe you can you can present because this is something critical that the repository managers it is critical it is critical so the good news is that we have developed it so it's there the the the bad news is that we haven't tested it yet and I think this was something that nashla uh wanted to bring in so we need testers so we need testers from the nodes this would be uh the best scenario for us uh because we believe the nodes will be the ones that at the national level can do this job and uh the the the idea of the tool is simple is to curate a collection where the first collection so the the starting collection is the one that we obtain by doing what we can in terms of uh technical efforts for the duplication and curators can at the national level so we we have for the moment uh this assignment of users to countries at the national level they can curate the result which means uh dismiss the results so say no you're wrong or instead group different collections etc this uh this is say you want to share a bit with our community the service should I share do you want to share this again just seven or eight more if you want to do it I uh no no no just go ahead I mean probably you are more familiar with it than I am so uh I used it when we were designing the the service so we have a sample uh data set in there um so a better service just here really a sample so Paulo you you can you can introduce what is this concept and as we have for a five minutes maybe we can share this so yes so what you have is the service suggesting you which are the new duplicates that have been found that require your validation and which are the ones that may raise conflicts and that you need to resolve you can undo everything decision you make but just keeping mind that whatever you do uh in from time to time is taken and used uh as the course the core organization set into the into the open air so you can see you can see here to the right for example you may say yes this belongs to this group or no that doesn't belong to this group this is a choice that you can undo in the subsequent phases or you can search and select another entry that is not been identified automatically and include it into this group you can edit the name of the group the name of the university so you you have a lot of curation power right the core is taken from grid but we will include Roar because Roar is the next step of the grid uh and again just here the the the different types just for you too yes you see you have different identifiers we collect organizations from so many different places every funder has its own categorization uh in some cases they don't even have identifiers right so you will have the PIC for the commission you will have is me you will have grid identifiers and at the national level you may have also identifiers um you can group them so saying this organization is equivalent to this ID this ID this ID this ID and this will help us in producing records that are uniform in that perspective now we need uh the knowledge to become very familiar with these two and to tell us what's wrong what is not intuitive and so on but this is the way to go so collaborative approach because the machine we cannot do it by itself the information available is really too little to make decisions just opening different different examples yeah just for universal maribor university of maribor universal maribor this looks good so this was a good guess from the from the duplication but in some cases as you will see this is not easy at all so we translated from seven or eight I don't remember different languages all the naming of institutions like university department etc and all the cities and country names and also the subjects engineering etc so when we can we translate and we replace the word with the code and we just compare the code and then we leave the rest as as the rest of the text the remaining text as the equivalence relationship that may say yes or no but again it's very complicated because the information is sometimes blurry little and not uniformly specified so the language is just one of the many barriers so we need humans in the loop yes please may I say something okay I think that this summer is a perfect time to do this for sure and I think that there are some volunteers in some of our country who would really like to help you and I think that the knowers in their countries knows all these variations in their institution and especially they are speaking the language in their country so it will be good to speed up this process and just to give us to work on this let's say for my point of view I really want to be part of this and to volunteer to help you with this even I will so and I think that there are some other notes that they are here and they would like to do on this thank you this is very good and we'll make sure the two to of course exploit your into the asm as much as possible because we need it now the thing is we need to make this progress incremental so the first version of the tool that we will provide you with is just there for the only purpose of checking if you can use it if it's intuitive enough if there are questions that you may have and then we'll move it to production so in the first phase there is no need that you're going to resolve all possible things but that you you know how to do it you learn how to do it and if you have any hints that may help us improve in the tool they're welcome then at some point we'll switch it to production and this is where you will start doing the effective work right and your work will be precious we don't want to waste your time in the first phase and we need like three four nodes who will take the role of train the trainers as usual right so the ones who will give us feedback make the tool good enough and then we'll explain others how to use it using the language of the nodes rather than our uselessly complex technical language okay so it's very important that we do this and we need somebody to take the lead on this process as technically the technical team is quite busy with so many things so we'd really appreciate if some of you would take this forward yeah thank you um Rian and thank you Paolo so I think this is this is in organizations are critical for all the scholarly communication services and it's quite important for the the provider so if open air can okay fix this for the benefit of open air it will be a benefit for the community so this is something important yeah not so we are coming to an end I'm not sure if you have any other questions here one last thing very important this set will be made open of course in public so for the whole world to use so it will be very important to have it so it's not just an internal product of open air so the whole collection will be published normalized so for every organization will say which are the corresponding equivalent identifiers we give it back to Roar we give it back to Grid we publish it to the world okay so we can we can promise that we that we will say something as soon as possible I think what is important Paolo is that we establish a process how to what to do technically and how to involve people and then we we have two or three from us coordinating the process and I think in terms of involvement of the community as Breanna said I think it's easy relying on on on on no ads on the national open access test for open air and some other contributions from the community that are also closed to our no ads in fact at the national level they are collaborating with our no ads in different bodies in formal or formal so for sure it will be easier to I think I think from those that I know that are participating in this call there are different people even if they are not part of open air that can also they can contribute to this good okay so I don't know when and how but for sure if not before via a different channel so I have my so I put as a promise from my side I will provide something information about this in the next community call so we put a topic there and to provide some information about this if you are already if we are already doing something or if it's expected and when okay so I was checking the shot we don't know no questions in the shot no questions in the I think I have already replied to the question so feel free to put comments and the and questions in the in the in the community calls google document that we have we will answer during the coming days or during the month so sometimes people use it to other comments so feel free to do it use and access the provide service feel free to use we are open for all the feedback as you know via our travel dashboard available now please record this this google document and the draft of the guidelines it's quite important and be available for this the campaign that we want to run to have more data repositories in us so some of the no ads from open air that are here we are counting with you to to for this campaign and all the rest and all the others so be be available to register your data sources or to or if you have any issue I know that some of you have already registered if you have any issue just ask also feel free always to ask questions because the people that usually answer the tickets in the help desk they are here in this call so you have a direct link sometimes in the community calls we have specific requests and that are answered so today we didn't have any but feel free to ask questions so and thank you for joining this call I'm not sure Andrea I'm not sure if you have put it the already the dates for the upcoming calls in the second semester not yet but we will put it as you so you have this link in our website where we have all the the the agenda for the different calls the the plan for the calls we will put if not today tomorrow the the dates for the all the calls from the second semester and all the recordings in the web in the slides are there okay available so many thanks for joining and Paulo many thanks for your support I think it's always great when we have your presence in this and participation in these calls I think so all our content providers realize the power that they open air have to to to produce some useful services not only for them specifically but for for the for Europe and for the world so many thanks for your presence okay in this call and stay safe everyone for those that will have holidays so good holidays see you in the next call maybe in the first Wednesday of September I don't think we will have in August so for sure our next call will be on the first Wednesday of September bye bye


Thank you. Thanks for giving me the opportunity to give this presentation at the beginning of the conference. So my talk will be about, well, I dropped from the title the much view because to say the truth, this is more also about my view, but what I'm understanding about the evolution of architectures. And there is a funny thing that, so several years ago, I was involved in making projection and suggestion for, let's say, planning the evolution of infrastructure. And all the time I was asking and planning for having a factor 10 improvement in the storage or in the compute capacity. The sponsor institution always said, but they really need such amount of... Then it started to become the age of buzzword, like big data that immediately my sponsor institution came to me and said, we are going to need petabytes of data. We know we need exabyte, exaflop of computing. And I said, yes, really? So it's a sort of game changing, so this, let's say, little bit strange to me. So in Macs, let's say, one of the goal is to enable exascale and exascale transition. I don't want to spend too much, but just to give you a lot. So we have a strategy and the strategy inside the first period of implementation of Macs, it was that we start from, let's say, open up and brainstorm and do, let's say, evaluation of different technologies. So we choose a pragmatic approach. So building knowledge about exascale, first of all. And I'm quite happy at the end that we know and learn a lot. And now we have a better view and better understanding of what we should do in terms of evolution of codes in terms to be prepared for what next, exascale but whatever other bus were. And in the meanwhile, in the roadmap to exascale, quite recently, there was an important announcement. So the announcement was, so there was a change in the roadmap. So this kind of guy that we, that was taken into consideration, somehow in our, let's say, thinking has been dropped. Has been dropped and canceled. So it has canceled the evolution of this processor from its architecture roadmap. I have to say that I think, I'm really convinced that, let's say, night landing or night hill, they were good processors. So if you were involved in the previous generation experiment that was night ferry, night coordinate, night landing, you can see a quite quick take up of this technology tower, a really efficient architecture for, for application. But apparently this was dropped not because it was not good and the plan was not aligned with the goal of the exascale, but because simply Intel was not able to find a market for this guy. So HPC is not enough. You need some other market. So, and we will discuss a little bit more in the talk. So at the beginning of the history of Max, we were, let's say, sort of, for those of you in Max, they may, you may remember our talk, our discussion, say we don't know what an exascale machine will look like, but for sure, if we use the math, since the exaflop means 10 to the 18 flops and let's say floating point units are not going to be any faster, at least based on the current architecture than one flop, one gigaflop. So I'm not sure how this architecture will look like, but it will integrate 10 to the 9 FPUs. So the challenge was how these FPUs will be integrated in the system. So there were two working hypotheses at the beginning of Max. So either in a dense system or in a light system. So the system will 10 to the 5 FPU in a server, light system, 10 to the 4 FPU in a server. But as I said, since the Intel drop, the F4 tower light, quote, unquote, server along the KNL line, we now are almost, sorry, we are almost sure that the architecture for exascale, at least my view is that I'm 85% sure that will be a tenor genius. So in the same system, we will have different chips to deliver different functionality. And even Intel, I discovered two years ago, sorry, four days ago, I look at the HPC wire and there was an article speaking about of Algarra view of exascale. Algarra is a well-known architect that now it is Intel, but it was formerly at IBM designing the blue gene computer line. And it was speaking about this kind of, let's say, node. So they already give for sure that you will have an heterogeneous system. So general consideration in the exascale is not only about scalability and the flop performance. In an exascale machine there will be 10 to the 9 FPU, but now we know that 10 to the 5, so 5 order out of 9 order of magnitude, German floating point unit will be inside a node. So probably we have, as I said, since the beginning we have to do probably more inside the node rather than across different nodes because we know that how to scale out to codes using message passing, but probably we don't know enough to scale up codes inside the nodes. So we need to, let's say, keep much more attention, pay much more attention rather than in the past to what happened in the node evolution rather than in architecture evolution. So, but from the market point of view, this is my own analysis, but that other may have different opinion or different view, but what is also happening that if we analyze from a market point of view, the value is moving up. So here we have a hardware infrastructure. Then we have this pillar that are verticalizations, so let's say a specialization of architecture tower, a given application, and then we have application. As you move up along this line, you are, let's say, bringing in more and more value, generating more and more value. And you know better than me probably that now there have been, well, a lot of success and a lot of value that have been generated, let's say verticalizing some architecture tower artificial intelligence or cloud service or in the past accelerated computing. So this means that the market is pushing to generate more values toward, let's say, specialization of architecture in a way because here is the value. And in fact Intel last year, that was Intel somehow find, find himself stuck somehow in this low value kind of part of the market. So Intel breakups, now Intel is two companies in one, one that is still dealing with that and another that is calling Intel data center group. That last year for the first time after many years, had the opportunity to increase the revenue. So now there is an announcement that in the last quarter of 2017 Intel do a lot of, but this was because data center group was able to move out from this layer and start to generate value here. So this I think will have an important impact of the architecture we are going to integrate. And in fact, again, let's say out of this Algarra interview, you can recover, let's say the same, so the view is, so the same architecture for the access care will be probably covering different aspect and different needs, vertical needs, so HPC, AI, data analytics and hopefully true configuration. This is, let's say, I'm not sure about that. It will be possible to configure easily a system to deliver different verticals, different verticalization, but I'm pretty sure that now if I'm going to, let's say, build up pre access case supercomputer right now, I probably need to integrate GPUs that already contains specialized core, so tensor core, which let's say are there regardless of the fact that you plan to have it or not. So tomorrow there will be the chance and the challenge to exploit different vertical and specialized hardware. So I can go quickly. This is just, but we already talk about the size of our next scale system. So my guess is that for the, well, again, take access scale just what's next, then it can be anything, but I see a trend of moving away from, let's say, having general purpose architecture to have some specialization in the hardware, because the market recognizes and takes value out of it. So since there is value, the designer of the architecture will try to maximize the return and so there is a strong push. There will be a strong push in having specialized core and specialized memory module. So I, I, I bandwidth memory module and specialized non volatile memory to integrate in future storage server. So in order to, let's say, this is a big challenge that we have in order to leverage this kind of new hardware that will probably be designed not for HPC, but for the degenerating value in different domains or for a single or few application. Then for HPC is up to us to, I think, try to cope and maximize our own return of the value. So in order to do that, we need, and you, you will, along this conference, there will be a talk about performance modeling. We need, in order to figure out how to leverage all that, we need to be better in modeling the performance and understanding how to refactor the code to fit architecture for architecture with specialized hardware. Just to make an example, if we look at the, the most well-known first, let's say, heterogeneous system. So the combination, the combination of an OST processor and an accelerator, let's say, a GPUs. So in order to, we start with codes that were running in this way, code being a sequence of, let's say, latency part. So part that were what come for performance, where the speed, the speed to solve and the speed to execute the operation on a single, on a single thread. Then in part where the code is essentially throughput, so where you can break up your computation in many smaller pieces and you can, let's say, with throughput, in a throughput part, you can leverage having multiple execution units. Then we have communication and so on so forth. So the code is a sequence of these sort of components. And then what we learn and what we are learning to do is to refactor, refactor the applications such that to have, let's say, break up and identify latency code and throughput code. And then we need to map this latency code and throughput code to the architecture overlapping, overlapping the two guys in order to keep them and fully exploiting without having to pay latency on the architecture. And when we look at the trace of one of the codes, you can, well, you can fairly understand what are these parts. And so we can identify fairly well what the code is doing. And so then it's more a problem of how we can really, let's say, restructure code to have this component being able to be placed where it's best for the execution. There is another problem that is one size does not fit all. So as I said, we have 10 to the 9 FPU to leverage. And probably the best algorithm for one FPU is different from the best algorithm to 10 to the 9 FPU. So the idea is, and then we discover it just working on the codes, that the best, to just make an example, the best FFT algorithm for the scalability is not the best algorithm to be executed on a single FPU. So in the code you have, let's say, there will be many modules. And that's what we will see next. There will be many components that can do similar stuff or the same stuff, but adapted or written for specialized hardware. And then the challenge is how we can choose runtime possibly the best algorithm or compile time for the given architectures in order to deliver the maximum value for the user and not to get stuck with the performance. We still don't know exactly what is the target architecture, but we start to learn, but as I said, probably there will be GPUs, many cores, FPGAs, others, specialized core, but heterogeneity. So we like in the past homogeneous architecture. But now we know that for sure heterogeneity is here to stay, and so we should care about. So heterogeneity is here to stay, and so we need to separate concern, as I said before. And so our idea is to sort of break up application in components at different levels. So there is an ongoing discussion, but I think that we have to, let's say, we should give the possibility to break up application and reassemble them. Reassemble them probably to some extent also at runtime to be possible to cope with and adapt with the hardware and the system in which the code is being ported or is being executed. So there is a full stack of possibilities starting from kernel libraries, so very low level to very high level. And let's say we are working to, let's say, better define these components and models, and better, let's say, give the opportunity to these modules to be adapted to the underlying hardware much faster and probably with the help of specialists to the underlying hardware rather than having monolithic codes. But just to say that along the first implementation of MAX, for what concerns quantum express, I was particularly involved in breaking up the core modules of quantum express. So now the core modules, we have at least three, but now soon we come four or five core libraries. So the code is becoming a collection of libraries and those collection of library may change, maybe interchange with other code that we can give the opportunity to, well, either for those that would like to rewrite or adapt the code to new architecture to either concentrate on a specific library or, let's say, not to, let's say, to have the challenge to consider a monolithic application with alpha million lines of code, but really concentrating deliver the best working on a limited set of lines of codes. Well, I don't have just to conclude another, so planning for access scale. We already now, we are able to, let's say, having applications that can exploit, let's say, a fairly large part of our current tier zero system in Europe. So we can scale out and exploit up to, let's say, a partition of a system that is in the order of several petaflops. So what is the path we are imagining toward access scaling? So probably there is some breakthrough in the middle, but we would try from an eye level point of view to try to be, let's say, inside a continuous kind of integration model where at the low level, oh, sorry, no, I would like to say that with separation concern, the idea is to live back through at the level of components, but at the level of application and user to be, to offer a sort of continuous path toward access scale. So today we are able to run on several petaflop partition. The idea is for the pre access scale system where we are imagining a factor of three to five improvement in the socket performance with respect to today. We can have the same user being possible to exploit partition of the system that is in the order of tens of petaflops, and, well, at the access scale probably when the architecture will be there, it's more that, well, beside the hero run that demonstrate the full scalability or the full exploitation of the system, probably the same user that today is running on a significant partition of the system of the order of several petaflops. In the access scale machine system, those users every day, they for sure need to run on partition which will be in the order of 100 of petaflops. So our challenge is to give the user the perspective of being able to, let's say, exploit the same fraction of the infrastructure. And with separation of concern, leaving the breakthrough managed at the level of the components, not to make the user, let's say, cope with that, as it was probably also in the past.


I'm Byron Abraham Daniel. I'm in the Mellon College of Science in the Physics Department. I'm from Atlanta, Georgia, the good old ATL. My preparation process took two months, so I started back in December and if you're wondering why this took two months, there are a lot of things I did, so I scripted this, I made examples, I ran through examples of my family, there are times like I have so many drafts of my presentation just kind of like on the cutting room floor essentially. There's one funny story that like during Christmas I just walked up to my dad said, hey dad, can I practice something with you? And he's like, sure, and I just went through my entire spill and was just getting feedback from him about it. So, I was mostly just, it was a pretty long process. Okay, I will tell you the fact that got me into Nutrino Research to begin with. So, I was talking with ATA in my undergrad about neutrinos and she said, oh wait, let me show you something really cool, then she just did this.  And she said, yes, a hundred billion, isn't that crazy? And I just said, yes, yes it is, like, where do I learn about more? And he said, oh, why don't you come to our department, we'd be department talks when we learn more about neutrinos. Great hook. What I really like doing research at Carnegie Mellon is it's like how much, like, I really like it with this, how much emphasis they put on just understanding just all the physics and, like, rotations. So, for example, although I focus on neutrino physics, as part of my graduate process, they actually had me learn other labs too, so I could learn about other particles with size neutrinos. It's just important to make sure that we as graduate students have a great grasp of physics as a whole in addition to just our own specific subfields.


Hello friends and welcome back to another DGC 2020 balance series. My name is Leo Sunon as Osiris and we're gonna be Continuing on with the Lapras the G max Lapras team that we started off with earlier in the week So I'm just literally continuing on from where we left off in that last match against the G max Charizard Wolves team that he had for series 2 if you want to check that episode out go up here and click through and And check that out before coming into this one if not, then we're gonna get straight into it with our first opponent up as a Good old mate over here playing a team of a lot of nine tails Tita ex-gadrill Rotom wash Togekiss and the ferrathons So we're running that team that we ran earlier in the week Which was the ex-gadrill the Rotom heat the Togekiss comes a cot the hitman top and the Lapras so hmm Can we just go for the Lapras hitman top here? Probably can we've got to be a little bit careful around the Rotom Yeah, the Rotom is a little bit of an issue Because it can just max lightning us, but I was so bulky we can we can pretty much I think I'd be I'd be quite happy just taking that so we'll go with this lead up top What do we want in the back? probably ex-gadrill Rotom heat Yeah, I think we're on heat Yeah, we'll go with that so And we'll just wait for a good old mate over here just to lock in I would imagine they probably may want to go with their nine tails so they can get their own roar available and Other leads I kind of expect would be the Rotom and the Togekiss. I feel like that probably is pretty decent against us and There's always an argument there for us to lead maybe Lapras ex-gadrill in that situation, so we've got a nice option against both Motogokiss and the Rotom if it does come out It's not a bad option against Haranita and things like that. It just slows down and momentum with Lapras I feel one thing with how we're running these Lapras is we kind of want to get going very quickly with it We do see the nine tails and the Rotom come out from my opponent So I'd imagine the Rotom to go for To Dynamax and go for max lightning and so it means we don't need to proc our own weakness policy at least I'm gonna fake out Nine tails I think and go I don't want damage Probably more damage. I want on to the Rotom to be honest We could go for max lightning. It's worth getting out our resonance up though Just to get the Aurora Villa and I think just to cover their role they'll going up this turn just so we get a little bit more damage I'll go for the nine tails fake out there I don't want to regret not going for it and then get there They're over there and that damage in the end game kind of costing us Which you could do so you've got to kind of think of the end game even at the start of the game I feel like it's always good to like think about these things There's you've got a certain amount of damage you need to do to your opponent team if you can stop getting that damage off sooner It does make the game a bit easier as you get a bit deeper into it if that makes sense So there's the Rotom going for it to max Dynamax I should say Max lightning into Lapras but in the process of doing this it will proc our weakness policy. We should take it I Want to say pretty comfortably Like I would imagine probably does about 40 like if it does 40% I'll be happy there's more than that Worrying a little bit. We may need to adjust Him on top to maybe ex-good rail next to Max guards. We've got something in to at least deal with the Rotom a little bit better But we'll see we'll see what this damage. I put is it's Max geyser ah into him on top It doesn't want to activate our weakness pretty obvious. It doesn't want to do that. Okay They know what we're gonna do with that break break That's why they're going for the top Maybe maybe Maybe maybe maybe who knows a and I think you probably want to get rid of like the Rotom isn't a massive concern of mine because I do have the extra girl in the back I want to stop them getting there They're all about Permanently, so I'm gonna break break and I'm gonna go for Max lightning just get the terrain up as well We don't need to worry about the Rotom. It's not on the ground. So it's not getting the terrain boost So we're not like being counterintuitive counterintuitive here and I Could go for the geyser, but I don't feel like we're gonna need that much damage to get the nine tails And if something like Rotom switches in on that slot, then at least we're getting some nice damage there as well and It should be enough. I think we'll see if they're these dry. Well, there's a weakness policy proct No, of course, it's not. No, it's not too perfect. There's a weakness I still think my problem would have been better going for the mass lightning at the first time It's interesting that they haven't even went while they can't go for that or all down now that the Rain's up course Okay Maybe T-Tar ex-cadrill Maybe the toggle kiss though, that's the T-Tar. Okay, just to disrupt the weather Hmm, I Think hitman tops in a really nice position here to actually We could potentially get the T-Tar T-Tar could protect though. That's the only issue And We might be better off going for the lightning into now, I don't really I'd rather concentrate down on the Yeah, the T-Tar like honestly the T-Tar is probably gonna protect and it's probably gonna go to weakness policy up, but I Still don't feel too bad about doing this because we do have ex-cadrill in the back Like that's what I'm just thinking like we get ex-cadrill in we've got the earthquake You can take advantage of before I do the rental team I'm probably gonna change the earthquake to high horse power. So there's max lightning coming out again We don't see the protect from the T-Tar. We do take that. Hopefully we had With him on top. Maybe we do maybe don't know and we do So close What we do out to be yeah, okay, it's got the pass your barrier looks like so the pass your bearing Yeah But we do out to be the T-Tar so that's fine I would get rid of that which helps out a toga kiss a bunch Because toga kiss doesn't really worry about rocks and especially when it's not dynamics, but she when you've got ex-cadrill sitting next to you So that's kind of the end the board game that we want to try and get ourselves into ex-cadrill toga kiss And we should be able to close things out with that Okay, we've got ex-cadrill my opponents I think the thing that we want to do here is just get it a mack punch off onto the ex-cadrill and probably Try and get a parish song up Because there's a chance that my opponent tries to get rid of the the hitmontop now with a hydro pump And I think I don't know if we'll take a hydro pump, but they do do that and protect the ex-cadrill to maintain their sash then we You get a parish song up You get the mack punch off break the stash in you so that's nice looks like gonna take down lapras and I'd imagine We kind of want the rotten to take down hitmontop here because we want that board position It would talk about a little bit toga kiss ex-cadrill. Here we go.  All right, oh, we haven't got the toga kiss. Okay, but it still doesn't really matter too much because yeah We just we just said quick now mack punch it quick and that's that's game Okay, talk is would have been better better than the Rotom, but did they have ferrathorn? Is that why we bought? It literally doesn't matter what we do now. Honestly, it really doesn't love the mack punch into me into the Rotom And the battle is cancelled. So good game to my opponent nice win for us to kick off with today Good old matey boy over there. Um, and hopefully we can Get a couple of wins today. That'd be nice. That'd be nice to get us off to Couple of wins and then we've gone because we we were one-on-one on Tuesday So it'd be nice to just kind of pick back up and finish at least Nicely positive for the week with this team before we end up with it and Of course, we'll be back with a new team next week to test out If you've got any suggestions that you'd like to see played next week, do leave them down in the comment section below I'd love to hear what your thoughts are and I'll definitely take them into consideration when picking a team to play next week So we've got our next opponent you in playing a team of Daryl Adon Incineroar Raichu Windsor cut a lot of nightels and Garados Okay Auroraville gonna come out again. The Daryl Adon's a little bit of an issue Kind of makes me want to lead more ex-cadrill Because it does so well against like the Incineroar the Daryl Adon the Raichu the wimmy the nightels to a certain extent and But This is all about G max lapis. So we're gonna go that way I will bring ex-cadrill in the back, but what's our fourth Pokemon gonna be probably them probably the Rotom I think they do have tailwind, but I feel confident You can get ourselves around the tailwind stall it out and get a Rotom in the position I think that's gonna be in the back of our mind the whole time The tailwind does go up from the Windsor cut and the Garados is out in the field You just got to make sure that we are kind of planning ahead So we can stall it out and get Rotom in And It's maybe the scrappin's the other team like the way I'm looking at it like maybe we need to use utilize Windsor cut a little bit more on our side and would definitely help us match speed control on my opponent's side of the field And one of the issues obviously is gonna be the fake tears Windsor cut could come out Do a bunch of just annoying things especially with that Daryl Adon next to it But the fake out does help with that for sure they got definitely helps with that So let's see what my point is gonna do here right you and Garados Have to be a bit careful with the Garados of course because then It does have access to power And be a bit of a pain Right you I think probably The thing is if I don't max with Lapras, I could potentially just go for a freeze-dry into the Garados But I probably want to just actually not even bother with that and go for my punch And go for the G max resonance into the Raichu if I can get rid of the Raichu It means that we open the door to utilize our And the bolt against the opposing Garados. I Think top probably gets baked out here could see an ice cream as well into us potentially But if we get Lapras set up with the resonance and Then it'll be alright, so okay, let's see what happens There's a pickup on the right that's into the Lapras. Okay, we get they get the mic punch off That's huge for us. Even if we lose him on top now, that's not too bad because We're gonna be potentially able to get rid of the Raichu now, which is pretty big There's the airstream and top take this No, okay, I didn't think it would be able to not even minus one. There's a speed boost for the Garados though It's all about getting rid of this Raichu. That's the thing. We need to get rid of it. The problem is that it probably has a sash It's moxie Garados and that's not what we want to see and it's life-alived as well. Wow, okay Okay, so right we'll get the resonance off Into the Raichu, get rid of it. There's no sash there So it does open the door for us to actually start getting some damage off onto this Garados It's gonna be a bit tricky though because the Garados Of course, it has the air balloons. You did see that in the start Huh extra girls probably the better option for us just because it's got the sash There's no weather up at the minute like hail to kind of Make it awkward for us. So Okay That's fine. That's fine I Yeah, we're gonna be able to we definitely gonna be able to get a thunderbolt off 100% so there's the intimidate. That's fine Probably have to protect X could roll here I don't really want to just give it up for free and there's no point of switching wrong. I'm in on potentially a Max Geyser that's coming out from the Garados either Unless the only thing that I can think the Garados maybe wants to try and do is go for a The max grass move into Lapras here still don't think it's gonna be enough to take us down though Because it's only it's a neutral attack at a minute even with the life warm And you're all they'll support up. I don't think it's enough and Yeah, there's a max over gross. We could have got away with going for an attack Take that saw comfortably and thunderbolts gonna be more than enough to take down the Garados There's no way Garados takes this attack and then Potentially with our last turn with Lapras, we could maybe take them in Sonora, but it all depends on my point It's the last one If we're in a position to do that, that'd be nice and so no one generally don't carry protect So we should have a kind of a free shot into there might say a parting shot Are you turn into Lapras now? It would be a nice idea to do that So you've got the fake out active the next turn as well makes it a bit easier We're just seeing the flablets into the Lapras and just tanking it tanking it because Lapras is just a tank So strong so strong. Okay, right nine tails coming in It's kind of fine now isn't it really really is fine gets the hail up, but I mean an iron head Into the nine tails and a max geyser into incidental I don't really feel like there's much my opponent can do they can go for their Aurora Ville here Yeah, but is incidental going to be able to take a plus two Max geyser, I don't know. I don't know maybe Ninetales no sash just straight down and back in like 2017 Ninetales was last really popular within the format It was the run sash quite a lot and then got both years format went on and had one of the fifty percent berries So they were the kind of two common items as well as likely But no sash there and the incidental Unfortunately cannot take the Aurora Ville and we do take it down and that is a nice quick game for us to Finish up with them. We do finish with two and zero. So that's perfect for us But good game to you and and really showcasing the power of the Lapras in that last one So that was a really nice game for us to end with today and like I promised my friends Now we don't we don't need to see that do me. So we'll come out like I did promise I would do the rental code for you for this team now if you do try it out Please give me a shout out on Twitter. Just let me know how you've been getting on with it What you found about the team or comment down below Just let me know if you want to follow me over on Twitter though I am at all Cyrus VGC and some manage Teams to share that's what we want to do. We want to manage some teams to share while we need to get rid of some teams Okay, which one I think we'll get rid of This one because oh, but don't make it public. Okay. Yes. We'll take it away We've got two team fives. That makes sense How's that even working? Okay, so that's empty now. We'll select the team And I'll pop in this one So there we go my friends How can I why is it not? Yes, make it public. There we go. Okay. I was just checking it check it just to make sure and Yeah, the only thing I would maybe do is change the earthquake to high-horse power Although the earthquake is super handy in some situations and it can really Kind of clinch out winds Certain situations it's it's tricky probably high-horse power is a bit more consistent But there is the rental team my friends have a lot of fun with it I hope you enjoyed Gmax Lapras on the channel this week. We will be playing it on stream as well or week So there might be some extra episodes Later on this week with the team from the stream highlights and things like that and but we'll be playing something brand new next week And so do tune in for that leave a like do subscribe to the channel for more Pokemon content And I will see you all for the next one central in ticket and bye-bye


Okay, so the syntax is up here. You have the keyword for followed by a variable, the keyword in a container. Okay, this container here is sometimes referred to as an iterable container. Okay, that means something that can be counted or you can loop through that content. So an example of container in this case would be a string. Okay, so strings are containers because you can count each individual character in the string. Right, when we learn lists and dictionaries and so on there, you will also see that those are also containers. But for now, we're going to look at two things, two types of containers. One is a string and the other is what's called a range. Down here is another diagram to show you what that one of those container is. It's called a range. A range is a special function in Python that is very useful as well that you can return a range of numbers and only numbers, okay, integer numbers from a starting point to the stopping point or number. And also it gives you a step value, it's an incremental or decremental value. Okay, so let's take a look at the for loop and I'll show you also the range, what that looks like in the code and what they mean. Okay, so let's go over to the help menu over here and let's type in search for range. You're going to see this help menu here and need to understand what's going on here first. So the range function, inside the range function as you can see, this is the function, this part right here. Inside the function there are three parameters. We have a stopping, the first number or the first argument is the stop, the start, I'm sorry, then the middle is the stop and then you have a third one here is called the step. As you can see it puts a, let's say, score bracket around it. So this is just a syntax, a notation telling you that this is optional and you don't have to include it. And then the start is also kind of optional but you can also change the start value to something else besides zero. If you don't include the start value then it will default to zero. Okay, by default always. And that's what you see up here is a range followed by the stop value only. It ignores the start and the step. Okay, so the step is defaulted to one, a positive one and then the start is defaulted at zero. And then the stop is the stopper, right? If you remember the value, it's like that set no value. I want to stop. Okay, so that is the range. So for example, if I go down to the terminal and I type in the function range, if I pass into this function, let's say five. Okay, so if I only include one number in here, one value, this value here will automatically be set to the stop value. As you can see here, this is a default. If one value, then the stop is the value and then the start number will again is zero. So if I hit enter, you will see that the range is from zero to five. Okay, it does not show the step. The step is, it's done implicitly behind the scene. It's going to be a step of one. So it's a counter. You count from this number zero inclusive all the way to five. And this number here is not inclusive. Okay, it's exclusive in the stopping value. So in this case, if you were to count, the step is one. So it'll be zero, one, two, three, four, and then you're done. Right? Okay, so that is the default range. So if I do again range to a thousand, same thing, zero to a thousand. So to like nine, nine, nine. Okay. If you want to include that starting point, because sometimes maybe you don't want to start from zero, you want to start from 10. So you would do range. I want to start from 10, 10 to what, 10 to 100. So you can see that on the range number is now is overwritten. The start value has been overwritten to 10. So you start from 10 instead of zero. Okay, so sometimes that's important. And so again, it doesn't show the step. If you want to say, okay, I want to increment these count by two, then you have to explicitly include that in the range. So you would do range from 10 to 100 and print every other number. So you're skipping two numbers. In this case, I'm printing 10, 12, 14, 16. And then once I reach, there's a counter that's going on behind the scene, which you don't see. This counter will increment as you use the full loop you'll see in a minute. Once you reach the number of 100, once it exceeds that, or reached that point, it is no longer true, it will stop. To go the other direction, you can also go negative by setting this third variable to a negative value. So if you want to do that, you have to explicitly do that as well. So if you want to count from 10 down to zero and go into negative direction by two. Okay, so you count 10 first because you are starting here. So if you are reversing the direction, just make sure that the starting value is larger than the stopping value. As long as the starting value is greater than zero, because I'm going negative direction, then you will run. Okay, so you can go positive or negative direction, just make sure you swap the two numbers here. So that is pretty much the range. And the range is important because it's a really important part of the full loop. So let's go over here and write our full loop. So the four followed by a variable name. Okay, so if you want to print a number like we did before with the while loop from, you know, a one to 10. So you would do something like from a number, any number in just a variable name, and the range from zero to 10. Right. And the step is again a plus one. So remember that 10 is not inclusive. So in this case, I'm going to print only from zero to nine. If I print the n value, you're going to see that it's going to print zero to nine only, as you see over here. Okay, this is zero to nine, because 10 is not inclusive. If you want to include 10, then you have to put 11 here. So now I print from one to zero to 10. So just remember that this is not inclusive, the stopping value. Even if you go the other direction, if you want to go the negative direction, then the third variable over here has to be a minus one, if I counting one at a time from, right, from what to what, in this case, I'm not going to get anything because it's already false, because the from value is already larger than this. I mean, smaller than the stop values, therefore, it's going to be false. If you see that if I print and run, it's not going to show anything in my console, nothing gets printed. That's why it must be carefully designed. So let's say from 10 down to zero, if you want to include zero, then you want to go to a minus one, all right, because again, it's not inclusive. So now I'm going to go 10, 9, 8, 7, 6, all the way down to zero. Okay, so the negative direction. So this in here, it stores the, in this case, stores the counter from the starting value. So what are these sort of value is initially and it will store the value first. And after that, it runs to one, the body one time. However, statements you have in here runs one time. And then after that, it's going to check this increment. This is the update. It updates the counter by a minus one. So the nation was 10. So now n is now nine. And if it's nine, then it's going to compare that value against the stopping value. Is it greater than one? If it is, then yes, keep going until this is no longer true. Okay, so that's happening behind the scene, which is why you saw earlier that initially when I put a zero here, it didn't work. But something more meaningful is, for example, if you want to print, say that the first three characters of your word and the word is going to be say Python, this three here. So what you do is n starts at zero because we didn't input it, we included zero. So instead of printing zero, I'm going to say, I want the word, then the square bracket of n, right, the position n is zero first. So this is the zero position, it's going to print the letter p, and then I'm going to increment by one, then the y, and then the t, and then at the point we stop. So again, just print three letters. And then and then you see here, we have the letters p, y, t, because notice that I'm using n as the index of this word to get those letters out, right? So use it for this scenario. If you want to get, you know, just the every other character starting with p, how would you do that? You can just go over here and change the range. I'm going to start from zero position, stop at, I can go all the way to, let's say the size of this word, how many characters it has. Well, I don't know, you can know by using the function called lend, right, the length of the word that gives you the total characters in this word, how many there are, it will give you that. So in this case, it's going to be six. And then I'm going to step through two. So you'll print every other characters, right? So p, t, o, and then I'm done, right, p, t, o. So you can see how easy this is in Python.