Hello everyone, this is the Circuit Python Weekly for August 14th, 2023. This is the time of the week where we get together to talk about all things Circuit Python. I'm Liz and I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support Adafruit and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it-slash-discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. This meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with the U.S. holiday. In the Note Stock, there's a link to a calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you would like to receive those notifications, we ask us to add you to the Circuit Python Nistas Discord role. There's a notes document to accompany the meeting and recording. The final notes document includes timestamps go along with the video so you can use the doc to skip around and view parts of the video that interest you most. The meeting tends to run 45-60 minutes. After each meeting, we post a link for the next meeting notes document to the Circuit Python Dev Channel on the Adafruit Discord. The meeting is held in five parts. The first is community news. This will look at all things Circuit Python and Python on hardware in the community. It's a chosen set of items from our Python on microcontrollers newsletter. The second part is the state of Circuit Python, libraries and Blinka. This is a quantitative overview of the entire document. The second part is the state of Circuit Python, libraries and Blinka. This is a quantitative overview of the entire document. This is a quantitative overview of the entire project. It's a chance to look at the project by numbers separate from our status updates. The third part is hug reports. Hug reports is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. Fourth part is status updates. Status updates is an opportunity to report on what we've been up to. Take a couple minutes and talk about what you've been doing in the last week since the last meeting and what you'll be up to over the next week. The fifth part is in the weeds. In the weeds is an opportunity for more long form discussions. These discussions can come out of status updates or be something you've identified ahead of time as too long for status updates. And that covers how the meeting will go. With that, we'll get started with community news. And I think the biggest news is Circuit Python Day 2023 is nearly here on August 18th. That is this Friday. The day highlights all things Circuit Python and Python on hardware. And there is a big list of events. It's going to be going from 10 a.m. till probably 9 p.m. Eastern. There's going to be special streams, special panels. Show and tell will be happening at 7.30 p.m. that night, followed by Ask an Engineer. And programming note that if you normally tune into 3D Hangouts or John Park's workshop, those are also happening on Friday as well. There will be a special stream from Maker Melissa, a special Circuit Python Day game stream with FOMI guy. It's going to be action packed. So stay tuned to the Adafruit blog and Adafruit social media for links including YouTube. Interaction with shows and progress will be held on the Adafruit Discord server where this meeting is taking place right now. And if you're working with Circuit Python, tag your projects with hashtag Circuit Python Day 2023 on social media and Adafruit will look to highlight them. Next, Nicholas Tolarvy and Fabio Pliger give an update on PyScript. One of the most exciting initiatives in the Python space these days is PyScript, which enables Python running natively in a browser with consistent support from the folks at Anaconda. This project has been making solid strides since its initial release. On the latest episode of Talk Python, host Michael Kennedy catches up with Fabio Pliger and Nicholas Tolarvy to see where they are with the PyScript progress. And then Project of the Week was the ADA. The AI display assistant is a beginner-friendly project for using chatGPT on an ESP32. This project uses chatGPT and an Afruit MAGTAG and ESP32 with an eInk display to display interesting facts and inspirational quotes. You can adjust the refresh frequency to whatever frequency you want or need, and this was seen on Haxter.io. This and more is available in our weekly Python for Microcontrollers newsletter, which goes out via email on Monday mornings. That was this morning. Visit AdaFruitDaily.com to subscribe to the newsletter. Thanks to Ann for putting the newsletter together. If you have any Python on hardware projects to share or find content you'd like to see included, please consider contributing to the newsletter. You can open a PR on GitHub, tag AnnEngineer on Twitter with hashtag CircaPython, or email cpnews at AdaFruit.com with a link. And that is the community news. Next up is State of Circuit Python, Libraries, and Blinka. This is a quantitative overview of the entire project. It gives us a chance to look at the health of the project separate from our status updates. We'll talk about the project overall, then separately discuss the core, Libraries, and Blinka. So first up overall, there were 17 pull requests merged by 16 authors. There were eight reviewers and seven closed issues by six people, ten opened by ten people. And now we will go to Dan for the core. Okay, thanks. Okay, in the last week or so, we have eight pull requests merged from nine authors. Jeanne Zoiburg is a new name, maybe. Thank you, everybody. Three reviewers. There are now 24 open pull requests. Some of them are really old and some of them are drafts that are blocked on other things, but we try to keep it under 25. 25 are under. There were five closed issues by four people and four opened by four people. So we're sort of almost even. There are now 683 open issues. We've got six acts of milestones. 8.2.x has zero open issues. 9.0.0 has 48 open issues. A lot of those are just being deferred until there are changes that we made in 9.00 as we need to. 22 open issues labeled as libraries. 593 open as long term. 15 labeled as support. We're not sure if they're actually bugs. Eight issues are dependent on third party things, so we're blocked on those. And two issues need to be triaged. They haven't yet been assigned a milestone. So that's it for the core. Thank you, Dan. Next we'll go to Katny for the libraries. Thanks, Liz. So the section applies to all of the Adafruit Circuit Python libraries, as well as all of our Circuit Python libraries in the community bundle. So that we had across all those repositories, nine pull requests merged from eight different authors, a few of the new names mentioned earlier, and six reviewers. The oldest one that was... There were two older ones at 293 days and 235 days that were closed, which were great. The rest were much younger. And it leaves us with 47 open pull requests, which is also down at least eight from the last time that I recall it being a little bit higher. So that's excellent to see. And we had two issues closed by two people and four open by four people, leaving us with 631 open issues. 19 of those are labeled good first issue. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more, including a list of open pull requests and a list of the open issues. If you're interested in reviewing, check out the open issues, leave a comment, let us know, and once you're comfortable with that, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation, check out the open issues. See if anything interests you, leave a comment and let us know you're working on it. If you're new to contributing to open source, we do have a guide on contributing to Circuit Python using Git and GitHub. So don't let the process intimidate you. We want to make sure that you can contribute in a way that works for you. We're always available on Discord as well to help. In terms of library PyPI Weekly download stats, we had over 312 libraries, 138,266 PyPI downloads, and the top 10 are listed in the notes if you're interested. We had one new library in the last week, USB host descriptors, and a couple of updated libraries that I will not read off, but they are in the notes. That's what I have. Excellent. Thanks, Katni. Next we'll hear from Melissa about Blinka. Hello. Nice here. Okay. Blinka is our Circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. This week, we had no pull requests merged. There are currently five open pull requests amongst the repositories. There were zero closed issues and two open by two people. There are currently 102 open issues amongst all the repositories, and there was 11,694 PyPI downloads in last week, 10,248 PyWheels downloads in last month, and we are at 119 ports. And that's it. Thank you, Melissa. And that is the state of Circuit Python, the libraries, and Blinka. Next up is Huggerports. Huggerports is a chance to highlight folks in the Circuit Python community and beyond for doing awesome things. I'll start and then we'll go down the list alphabetically to give everyone a chance to participate. Next only or are missing the meeting, I'll read your notes when I get to them in the list. So I will start. I would like to give a hug report to Carter for many rapid PR reviews last week as I was working on a product guide and a group hug. And then next we'll hear from Dan. Okay, thanks. Thanks to Scott for last Tuesday we had a detailed discussion about the MicroPython merge from MicroPython V1.19.1 into Circuit Python to catch up, and that was extremely helpful and sort of set me on a good path to getting toward the end of the merge.  I knew that it would break, but I wasn't sure what the fixes would be and he had already fixed up a bunch of things by the time I got up. So thank you. And that's it. Thanks. Next I'll read for David Glauze, text only. A hug report to TAC, who's a tiny USB author for the great contribution to Circuit Python, ease of use, and now USB host things, to Vladimir Smitka for the PicoPad support in Circuit Python, and educational content he is working on, and a group hug to the Community and Learn Guide writer-reviewer. I have been and am still learning a lot about software development, get usage, automation, thanks to you all. And then we'll hear from DJ Devin. I have a hug for Jepler for help with a syntax, translating a syntax snippet about shifting and truncating binary and hex values. It was a really neat little snippet of code that just blew my mind. And I'll echo a big hug to Scott for his deep dive this week. It was an excellent deep dive. Thank you. And a group hug. That's it. Great. Thank you. And now we'll hear from Fome Guy. All right. Hi, guys. Hi, reports for me this week. Thanks to Katny, who's been doing lots of great work organizing Circuit Python Day. Hi, report for Michael Melissa, who added some more new functionality and image load to support even more types of RGB images, which is really cool and a group hug for everybody. Thanks. Thank you. And now we'll hear from Jepler, who I see is adding even more hugs. I am. You know, as people acknowledge things, I'm like, oh, yeah, that's kind of important. So I just want to echo their words. Yeah. So first up, Dan, thank you for the merge. I know it was a long time that you were working on it. And I'm glad that it's reached this milestone of being there for GitHub to chew on until some of the remaining problems. To Katny for a wonderful chat last Friday, just hanging out some friend time. I'm really pleased to have made some friends within this community who are really dear to me. Todd Bot, thank you for sending me one of your PCB designs. It is a synth, naturally, and that's going to come later this week. I'm excited. Katny, thank you for organizing Circuit Python Day. And David, thank you for back porting that board definition to Circuit Python 8. As you identified that could be really helpful for folks who have the board, for instance. And that's what I've got. I'll think of more. But yeah, that's for now. Excellent. Thank you. And now we'll hear from Katny. Hello. So back at you, Jeff, for a wonderful chat. I have a hug report to Todd Bot for a synth hardware care package with one thing that I was expecting and three surprises. There was all sorts of fun going on there. To Paul Cutler for hosting a synth IO panel on Circuit Python Day.  To Meagher Melissa for hosting a stream. Foamy Guy for hosting a stream. To Jeff and Dan for joining me in a chat. To John Park, Noah, and Pedro for hosting their weekly streams. And to John Park for taking on doing the introduction. And to Scott for hosting a stream as well. And a group hug. Great. Thank you. Looking forward to all that Circuit Python Day content. And now I'll read for Kmatch, who is text only. To Jepler for taking on the challenge of the ESP32S3 dot clock displays. Can't see what's possible for these big touch screen displays. And hugs to all. And now we'll hear from Meagher Melissa. Let's see. I wanted to give a hug to Jepler and Pinker Dragon for laying the groundwork for the Matrix Portal S3 and Bitmap Tools. And a group hug to everyone else. Great. Thank you. And now I will read for Mark. Hug report to Katni for the Circuit Python Day organization. Hope to attend some of it. And a group hug. And then we'll hear from Scott. Hello. First, a hug report to Microdev, who did a ton of work to do an ESP IDF 5 update for Circuit Python. I'm dusting that off and it's been awesome. It's a huge boost. So thanks to them. Thank you to Katni, like other folks have said, for organizing Circuit Python Day on Friday. Hug to Dan again for the 119 merge PR. And lastly, also to David for some board back ports. Great. Thank you. And that was hug reports. Next up is status updates. Status updates is our time to tell folks what we're up to individually. I will start and we'll go through the list alphabetically. What I call on you take a couple of minutes to talk about what you've been doing since the last meeting and what you'll be doing until the next meeting. I'm going to provide some tips and tricks relevant to what people are working on. If a discussion becomes too long for status updates, we can move on to in the weeks. With that, I'll get started. So I've been working on a few product guides, PC Joystick seesaw breakout and the Arduino pages for the Metro RP2040. I had never actually used a PC joystick before, so I had to procure one on eBay for testing, but luckily it worked really well and I'm hoping I maybe will do a project with it. I've also been putting together some code for upcoming project collab with Noi. We are redoing our MX MIDI guitar project to be a synth guitar. We're using the prop maker feathers since it has the onboard I2S amp and the LIS 3D H accelerometer, which we'll use for some effects controls. And then we'll hear from Dan. Okay, so on Friday I released circuit byte on 8.2.3. This is just a bug fix release. The only changes were a protomatter update for RGB matrix. If you're using like matrix portal M4 this release is helpful for certain RGB panels. It's not needed for matrix portal S3, the new board. And there was also a fix because of some changes in the read-the-doc site. We had to change how we generate that documentation. Thanks to Jeff for that. As I mentioned, I discussed the MicroPython merge with Scott. And we actually talked about backing out some of the changes that we made over the years in upstream. Mostly having to do with something called long-lived storage. Which was increasingly in conflict with stuff upstream. So the result of that is that after working on it for several more days I finished most of the merge and it was at a point where most of the builds worked. I admitted a draft PR and wrote it up. You can find that if you want in the PRs. And so there's a long discussion of a brain dump of what I worked on during the merge. Jeff looked at this this morning and suggested a bunch of changes and I incorporated those or equivalent changes and a lot more things are working now. There's the things that are the tests are still breaking but I think we can figure that out. There are a very large number of file changes a large number of them of recent changes just have to do with formatting but there are also a bunch of really significant changes further back. And as I mentioned we're going to see about taking out this long-lived storage thing which we've had for many years it reduces fragmentation which is especially needed on small words like Circuit Playground Express and we want to see how badly taking turning this off whether it breaks too many things on Circuit Playground Express there are ways to put it back in that are less in conflict with the way storage management now works in MicroPython. So we'll look at that when and if the time comes. Okay, that's it. Thanks Dan. Now I'll read for David Glau's text only so CircuitPython, PicoPad and GitWeek contacted Vladimir Smitka see if he could do a back port PR for PicoPad support into the 8.2.x branch decided to do it myself and learn about Git Cherry Pick for back porting and the proper way to take PRs from one branch and apply it to another branch keeping the original author accredited. Checked the 20 to 25 layers boards in CircuitPython.org downloads and that together with PicoPad the Metro ESP32-S3 was the only other board about a stable release download option. Made a blind, I don't have the hardware to test back port PR of Metro ESP32-S3 to 8.2.x branch so that if there is an 8.2.4 it could contain both boards. Also found out that what I did the previous week for the DS10-X20 and photo cell sensor was not needed since Vladimir has a lot of educational content in CircuitPython with code covering these sensors. And then in non CircuitPython Feather-RP2040-USB host week. Tested the latest release and feature of J. Fedor-2's HID Remapper project that is a really cool project. Finally tested my IntelliQ key membrane with Feather-RP2040-USB host and firmware from TAC. Found an uppercase lowercase bug in one of the overlays and made a PR, now approved without installing Arduino but tested the result with the resulting artifact. And now we'll hear from DJ Devin. Thank you. This week I started working on a matrix portal S3 project with two matrix panels and I want to stack them vertically. Quickly found out that the included IDC cable isn't long enough to reach if you vertically stack them. Had to jump on Digi-Key, try to find the right ribbon cable out of the tens of thousands of IDC ribbon cables. I think I got the right one and ordered 10 feet so I could just cut and splice into the existing connectors because they just kind of crimp on. And then Jebler just told me that I've been doing it wrong and there's actually a way to easily use the included IDC cable with the way that I want to do it. You just have to invert the second row and that should work. I didn't realize that would work but thank you very much Jebler. I will definitely be working on that now. I'm working on a jewelry box birthday gift for my sister that incorporates a graph display of Fitbit heart rate data. The TFT will be mounted inside the lid and when opened will play a song and display the last 15 minutes of heart rate data on the display TFT display. My sister will have a dedicated display to see my mom's heart rate data anytime she wants. All she has to do is input her wifi details into settings.tomo and there you go. Nice birthday grid. That's all I got. Cool. I've been enjoying seeing what you've been doing with the Fitbit stuff. Next we'll hear from Fome Guy. Thanks Liz. I just messed up my stuff. There we go. Over the past week or so I knocked out a few more of the older library PRs and I've got another couple lined up to look at this week. I probably think I spent the most time over the last week was wrote some scripts to compare a full list of the PIDs that are in the different store against all of the data that is inside the Oshawa database to try to find the ones that are not in there yet. And then once I had that list of all the ones that are not in there yet to go through it and find the ones that are kind of like quote unquote real that actually need to be submitted because lots of them are like variations of different hardware that's already there or other third party stuff. So I've been working through that list and just wrapped it up actually before that's nice. And then the other stuff that I got into over this past weekend on the stream is started prepping a little bit for the game that I'm going to make on stream on circuit python day. So far I've built out a test map and started working on some helper classes that will get used inside of that game. And so I will be continuing on with mostly the same things this week. Thanks. Cool. Thank you and thank you for working on Oshawa stuff and looking forward to your stream. Next we'll hear from Jepler. Hi again. So my main activity over the last week was to continue to work on the dot clock displays. It's still not actually doing anything yet, but I'm getting really close. Most of the register setting code is implemented. Most of the pinboxing code is implemented. The main thing that's left is code to do the actual DMA of the data to the display, which is always a big bug bear for me, but I'm getting close, I think. And like Dan discussed, I've been helping out with problems in the MicroPython merge. We solved several items together already this morning. Sadly, I seem to be coming down with a cold. My spouse is like a day or 36 hours ahead of me and it may be minor or it may knock me out for part of the week. So we'll just see how it goes and yeah, that's what I'll be up to. Alright, I hope you're able to rest up, Jeff. Next, we'll hear from Katny. Alright, so last week and earlier today, published the MetroRP 2040 guide, took care of some guide feedback on the PropMaker Feathering Guide, which reported some code that wasn't working among some other things and also related a GitHub issue where someone is reporting the same thing. Also wrapped up a few other GitHub issues that I had been assigned that have been sitting around for, you know, years. They're gone. So this week, Friday I'll be on Paul's panel chat and then also chatting with Jeff and Dan. Jeff's cold willing as well as coordinating folks throughout the day and during the week. I need to write up the CircuitPython day intro. It is going to be streamed by John Park but I promise to write it up. So I have to do that and then in between all of this, I will be writing the MetroESP32 S3 guide, which is in the shop coming soon. So hopefully that guide I actually don't know the ETA and what it's supposed to be in, but the guide will be done within a week. So within this week, I guess. So if it goes into the shop sooner, you might have to wait, but it will be available very soon. That's what I've got. Cool. Thank you. Next we'll hear from maker Melissa. Hello. Let's see. Last week, I worked on, I finished the alpha button changes for the CircuitPython core board. And I submitted a PR for that. I added the field compression support to the image load library so you can now load images created with GIF or GIMP, I mean. I updated the matrix portal M4 and S3 simple test. In fact, we reset images and put them in the respective guides. Worked on finalizing code for the message board project. And I started a guide for the message board. This week, I'm going to get the message board finalized in PR and I'll just get it PRed, I guess. I'll work on the guide for the message board and I'll do my CircuitPython live stream on Friday. And that's it. Looking forward to that project and your live stream. Thanks. And last we will hear from Scott. Hello. Thanks Liz. I'm going to be kind of bug hunting for USB host back and forth with TAC this week. He's out last week because he got sick. I'm doing a demo thanks to some code from ToddBot that is a USB host MIDI keyboard plus a synth IO. And I've got a little bit of initialization code to write for the 1060 EVK but I'm kind of excited to get that working end to end. And I'll be testing some fixes from TAC through that. And then on top of that, I'm also doing an IDF-5 merge. So I'm updating MicroDev's PR and starting with that. And that's been super helpful, like I said. So we'll be updating the IDF-5 and then I'll follow up once that is in with an update to 5.1. I have a PR out to the Black Magic project which is a debugger sort of thing. And they gave me feedback and I haven't got back to them on that. So I need to do that as well. So I'm updating for Circuit Python Day, DeepDive starts a half hour later than normal and then next week, Monday through Wednesday, I'm out. So it'll be a short, super short week for me next week. But having vacation with family. So that'll be good. Great. Looking forward to USB MIDI host and enjoy your vacation. And that was Stass Updates. Next up is in the weeds. We're here for long form discussions that either come as Stass Updates or the folks have identified ahead of time. If you have any in the weeds topics, please make sure they get added while we're discussing other things. So we're not waiting around to see if anyone has topics. It looks like today there aren't any topics. So, I think with that we're going to wrap things up. This has been the Circuit Python Weekly for Monday, August 14th, 2023. Thank you to everyone who participated. If you want to support AidaFruit and Circuit Python and those of us that work on Circuit Python, consider purchasing from the AidaFruit shop at AidaFruit.com. The video of this meeting will be released on YouTube at youtube.com slash AidaFruit and the podcast will be available on major podcast services. It will also be featured in the Python for Microcontrollers newsletter. Visit AidaFruitDaily.com to subscribe. The next meeting will be held next Monday as usual at 2pm Eastern, 11am Pacific. The meeting is held on the AidaFruit Discord which you can join by going to AidaFruit.it slash Discord. To be notified about the meeting and any changes to the time or day, you can ask to be added to the Circuit Python NISAs role on Discord. We hope to see you all next week. Thank you everyone.


Well, morning everyone. We made it to the final day of the formal large meeting. Good to see you all. I hope you have enjoyed your time here in Brisbane at QUT. So bear with me. I had a double espresso just like 10 minutes ago so hopefully that's working for me. So, but yeah, really keen to share with you a collaboration that we had with the Department of Agriculture here in Australia and really thanks Galaxy because has been one of the platforms that has enabled this conversation to make an impact for horticulture industries. So horticulture crops in Australia certainly play a role in our economy. It has been estimated that the value of the sector is around $14 billion in the last calendar year and it's anticipated that that value will increase by another $4 billion by next year. So, as you can see, Australia exports to different regions around the world and these are high value markets. And from the point of view of our economy, we're really keen to protect access to those markets. So how we can do this certainly you have experience of a few and thank you for coming all the way down to Australia. It can be a bit of a journey to come down here but that journey also is applicable to exotic pests. So we do not have many of these pests in Australia and we're really keen to keep it that way and with the more trade that is happening more movement of people and resources we're really keen to continue to make sure that we safeguard the industries. So, some of you may have experienced some coming in that yes, you need to be across quarantine regulations, which is perhaps for some of you may have been a culture shock. But yes, we are really keen to have those processes in place and if someone tells you sorry mate we misplaced your luggage. But actually turn out that your luggage needs to be screened for three years and we'll get back to you in three years. So probably you may not be very pleased with that. So, and that is actually what is happening with our industries currently. So, any new germplasm that they bring to Australia, they spend a really long time in quarantine testing and eventually they, they get tested and release once it's safe. And then they can start the businesses so as you can see as a business owner that's not really something that is of appetite because you can keep your, your, your market share, either domestically or internationally. So we really need to make our industries more flexible are more agile to respond to market opportunities. So, but why this is happening is because we, we, when we started this project, the main driving force for diagnostics is relying on molecular assays and surgical assays and biological indicators that can take really a long time to be performed. So, in that sense, yes, we need to have an alternative that can be more scalable to also improving new regulations. So we have 217 viruses which are of by security concern in Australia, and we need to make sure that we look at all of these. There's also the challenges of, if we continue to rely on existing processes and technologies, there is less and less appetite for new students to go and acquire those skills. There's a decline in expertise, for example, in biological indexing, shoot if grafting so if we want to be future proof, we really need to start to rely on alternative solutions so we engage with the Department of Agriculture will listen to their pain points and how challenging is for them to cope with new updates on what is being regulated throughout the year and they need to respond to these regulations. So, as you can see quite quickly, it wasn't just something that they can maintain and sustain to be able to address. So, we decided we need an easier strategy so can we tap into this into a solution that can be sustainable. So we didn't realize quickly that we can leverage from the host planning immune system. So plants have done all the work for us. So essentially, we did not need to do anything ourselves because throughout evolution. So plants have evolved to respond to infecting viruses and they rely in these small RNA pathway which is called RNA interference, and there are specific enzymes that responds to viruses and one of the really nice features of these enzymes is that they can recognize these viral molecules and fragment these molecules into quite specific sizes so when we're building that analysis strategies we can rely on these specific products that we expect to be coming from the response to viruses. So, briefly, I would like to share with you what we've been working with the Department of Agriculture over the last four years or so, certainly COVID has been part of this journey so we share with you as well that, and we were really keen to look at, yes, what are the various STS technologies, there are many flavors of STS technologies that are being used. We had initially identified in the proof of concept that N is referred to that small RNA pathways might be the way to go for us. It gave us the opportunity in this partnership to step back and look at the bigger picture and see is this the best way forward because different agencies around the world they use different approaches so we're really keen to look at the technology and then look at running large scale trials to make sure the processes work and then I would like to share with you a couple of technical lessons that we learned in the journey and then finish up with the policy adoption. So, smaller than ACS, I don't really need to dive too much into it. I think it's a fantastic proxy when we are really keen to know whether a virus is actively replicating within the host. It gives us that possibility for us to assess that and measure that activity. But one of the drawbacks of potentially relying on this strategy is some viruses have evolved strategies to suppress the RNA interference in the host. And we don't see that is 100% effective in removing that activity, but there is a consideration, but also there can be some of the viruses can be dormant and not really replicating. So, relying in alternative approaches and technologies can provide us that that possibility to assess whether yes we should rely on the smaller days or perhaps we should go and look at an alternative strategy which is in this case, rather some of the police in RNA, I think it's a sensible approach. We started with that initial question. We wanted to address which technology we should take forward. We rely on positive control set of plants that we knew what viruses and something that is called baroids. They are really small circular RNAs that are present in plants, they can range between 200 or so nuclear pipes to 600 basis, and they can also cause a disease phenotypes in plants so we're really keen to to look at these plants that are not only infected with viruses but also with these smaller viral molecules. So, as we started this journey. We wanted to continue to work with the initial partner, and that was an overseas partner that we initially work to develop the proof of concept strategy, but looking at implementation and adoption in Australia. It was not really sensible for us to think we can move information overseas so we needed to have a local solution that can be utilized if we were to adopt this technology. So we're really keen to start that conversation and we started to work with a local provider. So, we start this journey of looking at the detection of these viruses using these two approaches with the small RNAs and Robosomal STS, and soon we started to see that we observe some differences of what is known from the positive quarantine testing and legacy information on the selection of these positive control plans. So, on the site of the small RNAs we were missing a virus which is called citrus tracessa virus this is a very interesting virus in Australia. In the world about nine genotypes of CTV are present and we do have some of these genotypes in Australia which are endemic but some of the genotypes of CTV are exotic so we do test for CTV so that we prevent entry of new strains of CTV but the smaller RNA was clearly not detecting any signal there. And when we look at the alternative Robosomal depletion, we did observe a minimum signal, but it wasn't a strong signal to suggest that it is present so when we did compare with the molecular plant, we did observe from positive quarantine, the sample that we sent for sequencing the first one on the link wonder, it was certainly missing, we could not detect a signal in CTV, and also additional extracts from that particular plant also means that so yes, it was certainly missing in that in that plant. And then, when we look at the Robosomal depletion. We did miss Hopistan Varoit, which is also another pest of interest, but when we look at the molecular assay data, we could detect the so we were not detecting in this particular strategy that we utilize with the service provider that particular pest. The lesson that we quickly claim to realize and when we work with these technologies is that when we utilize public data, we don't necessarily keep the metadata information when the data is being generated so sometimes when we generate data we try to go and aim for low cost data generation options, but that could potentially impact what you are detecting in your samples. And that is something that we've learned that there can be a phenomenon called index hopping events or cross sample contamination, but that essentially means is when you have some signal that is strong in one of your samples, you could detect that strong signal in other multiplex samples that you have in that particular experiment, and you can have a false positive so we really need to be mindful on that. And certainly, we did detect these two signals with a smaller stick in these control plans, but yes I suspect that we could not really validate them. So we look at the rubber some of the pollution. Yes, the initial strategy that we use. It was a bit of daunting picture because we could see that a large fraction of the samples that we were testing were reporting these false positive contamination so from the point of view of quite agencies. When we report to them, we found these, they need to go on and inspect and assess and validate these so as you can envisage that can be quite a daunting overhead on resource allocation to follow up this erroneous reporting. So, we were really keen to improve this so we started to partner with a local service provider and gave us the opportunity to test on a strategy called well indexing that can minimize these false positive reporting, and this was roughly three years ago, or so. And we started with that option. The good news for us is that yes we can detect all the past that we expected to test with a smaller seek a strategy. We also detect everything that was expected to be detected with rubber somal depletion are a secret strategy which would include in the hop stand baroid that we were initially missing. And when we look at the cross sample contamination. Yeah, we saw less down team picture we could see less cross sample contamination with rubber somal depletion, we did not observe this with smaller and a sake, but we then realized that it was because of the instrument that we were using back then so next, next sick instrument at less prone to this cross sample contamination, but if you use Nova sick instruments, you will start to see this effect so you need to be mindful on the instruments that you utilize. So, at that point, we thought it's sensible for us to go ahead and utilize a smaller nice as the strategy going forward to start to use larger scale testing, and for enabling this conversation on this testing. We implemented to analytical workflows. Initially we implemented a prototype workflow using next flow. And as we learn more lessons throughout the processing of the samples. We optimize the workflow. And now this is published and accessible to anyone. This is called the report. And that has been our initial prototyping of optimization, but simultaneously. We also utilize galaxy, and that has been really fantastic resource to work with galaxy Australia, because most of the plan molecular biology is a post entry quarantine they don't have these data analytics expertise. For them, it was really fantastic that we provide them this galaxy experience and interface so that they can see how the data gets process, and they have visibility to all the intermediate information that it would be required by them to analyze and make a sense of what has been detected. The resource that we found quite rapidly important to develop is a curated database for viruses and this has been highlighted a couple of days ago that we need to have a uniform approach to dealing with public information. It's the same for us. When we work with public resources of our information. We defined our strategy that we needed to harmonize taxonomic information of the viruses as a way for us to make sense of this and make a uniform approach to harmonizing descriptors. So we utilize an adopted data strategy. Additionally, we go and look at the taxonomic information that is assigned through the international committee for taxonomy of viruses. So we make sure that whatever is harmonized is compatible with the experts. Additionally, we do what is called we define representative sequence for highly related genomes. So when we're looking at public data as you can anticipate there might be some minor differences in terms of genomic data. So it can be a little bit of a challenge to make sense of what is detected and consistently so what we decided is to remove that ambiguity in terms of what we are detecting and what we are reporting. So we decided to define what is a sensible representative sequence for highly related genetic sequences. So we use those as references for diagnostics. And the benefit of doing that is that it can result in a very light database that can be used within Galaxy, and it's very effective in running these processes. And we, with those resources in place at different stages of development, we started the first season of testing, and we secure access to 188 samples across different commodities. We started the first set of of processing. We essentially was starting to be part of in our life and initially we didn't feel the impact of it, but then soon after, yes, it was starting to impact the supply chain, or as to continue to do this work as resources when being directed more to hobby testing. So we decided we need to build resilience. If we want to adopt this technology, we need to define a strategies that can build a more sustainable approach in Australia so we'll get back to that in a moment. So we needed to go back to some of our partnerships that we have overseas to continue to progress with this activity. And we learned a few lessons along the way. So the more valuable lessons were where we were not detecting a pest that were detected through authentic quarantine protocols. So we were able to have that firsthand knowledge access so that we can optimize our analytical pipeline so that we can get to this 100% agreement with the post entry grant protocols and that was really valuable experience for us. Another challenge that you can to realize when you are dealing with these biological samples is that we have viral sequences that can be integrated in host plant genomes. And one of those cases studies for us was working with raspberries, and this particular virus which is called rubus yellow net virus, and we reach out to Driscoll us because they have been working, and they provide germplasm for raspberries, and they were trying to create a sense of how these viruses are being integrated into their germplasm they are providing to industries across the globe. So we got access to some of their early insight knowledge for us we of interest for us is the one at the top. It's an episomal strain of which is of by security concern. And so far, we were not able to see any positive detections for this alone that journal. We also were able to detect new to science viruses, and we identified a new pot of ours. And so we were able to recognize by having a very long polyprotein, and this is a bit more than 3000 amino acids polyprotein that encodes a range of, of operating frames that sustain the function of this particular virus. And so this was closely related to sarcoma suck virus, and also sugar came as a virus, and we tentatively name it miscanthus in nc's most like bars for review by the ICTV. And we mentioned that, yes, COVID was impacting our delivery of milestones within this project activities so we're really keen for us to, to partner with more service providers in Australia and we invite them to undertake at least two different strategies, where they can use, and perhaps they might be already within their R&D pipelines to use and deploy as new services to the community, so that we can test and assess which one might be suitable which ones might be suitable. Ideally, we have some redundancy there. So what we learned is a long story short is that Cajun micro elaborate keyed having with a unique molecule or indexing and unique dual indexes was the strategy that was preventing this cross sample contamination that we did observe when we moved from instruments to a higher throughput. So we do recommend to utilize this strategy, having said that there are still opportunities for us to improve and we'll get back to that in a moment. So, we continue our testing on our second season of testing. And as we expect with most of these germplasm that it gets imported to Australia. And to be quite clean, we only detected in just around 8.7% of the imported plants, regulated viruses of by security concern to Australia. So, it is important that we have those detections, and in addition, depending on these industries, they are interested to know which other endemic viruses that we already have in Australia, my view of interest. So at that time, we were looking at reporting some of these viruses of interest for a specific industries so that we can provide that information so that they can make an informed decision, whether they would like to build a business portfolio around that new germplasm that may have an endemic bars. As part of this we also detected another new designs virus and I think there is opportunities to continue to build and have these resource available to the community. It looked like a potty virus but it turned out to be a pot-ex virus instead. And this is now the moment under review for publication. So, a couple of lessons that I would like to share with you in terms of looking under the hood. First, it was really informative to optimize when we're working and deploying and implementing end to end analytical workflows. We're really it was really informative for us to understand the source of the genetic information that we were collecting. So, because that allow us to improve the standard operating procedures from sampling, collection of RNA, but also library preparation, and we partnered with Cajun, our team to implement strategies to try to minimize the collection of primitive data. We use a representable depletion strategy for a small RNA-seq data which is not typically used, typically use this representable depletion for longer RNA-seq experiments. And it has been working well for us to deplete long RNA, representable RNA fragments that we can see in these libraries, but it still is not very effective at removing smaller fragments of ribosomal RNAs that, as you can see, is still present in these libraries. So, we're really keen to continue to work with them to define strategies that we can remove these non-informative information being ribosomal RNAs, chloroplasts RNAs, mitochondrial RNAs, which are not really informative from the point of view of technostics. And if we are, and we are in this currently looking at implementing some new R&D strategies to try to specifically pull a smaller RNAs that are derived from viruses. Another aspect that we were initially thinking what are our controls that we can use as part of these experiments is how we can assess cross-sample contamination. And for addressing that question, we use an alien control and we use the Miscanto sample that I just mentioned earlier. That is a virus which is highly expressed. So it's a really good candidate because the signal from the virus is quite strong and can be detected in other samples if there is a virus hoping event. But then we are also interested to look at when we have negative detection of viruses, water strategies we can use, and we decided to tap into a synthetic microRNA, in this case we use the CLEG and microRNA39, which has no sequence similarity to any sequencing plans. So, and we use these as our work control to also measure the sensitivity of detection in these plans where we have negative signal of detection from viruses. So, policy, it's been a bit of a journey for us to work and has been fantastic, the partnership with the Department of Agriculture. One of the blessings that we have when we work with the department is that they are really keen to have relationships and the initial trigger of this activity was when Mark Washam, back in 2012, said this is our pain point, viruses, we need better approaches to detect these viruses. And then we were involved in that process and we received these plan-based securities, CRC funding to develop the plan-based, the initial proof-of-concept approach, and we deployed the solution in something called YABI, which stands for another bioinformatics interface, and back then we thought it was sensible to use that platform because, yeah, that was part of the platform support in our host institution, but then we realized that we need to provide and build resources that are more accessible to the community, so hence we use now other platforms to provide these solutions and access. And the journey that I'm sharing with you is the journey that we had recently, we received funding from horticultural industries to look into implementing this technology for routine testing at quarantine agencies, and also how we can potentially upskill the team, the molecular biologists, plant pathologists within the quarantine agency in the Department of Agriculture to have the expertise to adopt and utilize the technology for routine work. And I'm glad to report that December last year we have formally adopted this technology for the first year of commodities, and these are prunes, rubus, and strawberries, and this is in addition to ornamental grasses that we adopted during the proof-of-concept facing. So, and we are starting to roll out now these as a routine service at the Department this year, and the plan is to eventually expand these to other commodities. So, but all this is just possible because the partnership and the relationship, the regular engagement, so we had monthly meetings throughout the last four years with the Department of Horticulture, and that has been fantastic to have some of the champions, Mark Gwatham, Julie Pattermore, Akandis, Elliot, and also Greg Murphy there in the picture, Adrian DiCel, all of them have played a major role to engage different teams within the department, policy regulator teams, operations team, IT teams, so that we can all come to the table and work towards adopting this technology. Without them, I don't think this is possible. And then certainly, Galaxy, Galei has been a really instrumental interface and platform, and I would like to acknowledge all of you that contribute to having this resource available, because that has been a platform for us to engage and communicate with the, this stuff within the current agency so that they can get visibility on how the data is generated, how to adopt strategies and technologies, and we implemented some of the material user guides, videos that allow them to use this technology. And now we're working with the IT team to implement a portal, and this is an in house portal is not available to external stakeholders, but this is internally to enable them to implement operations and brand these diagnostics for these commodities that are currently adopted for HCS testing. So, from the point of view of what they need to do, at the Department of Agriculture, we wanted really to streamline and minimize their hands on involvement. We weren't excited and passionate to learn new skills, but we know how busy they are. So we wanted to really minimize their hands on involvement in the whole process so all they need to do now is just basically collect the samples, and everything is automated. So, the samples are sent to a service provider and the service provider, provide us an email with a JSON file within metadata information of the samples and that triggers an automatic ingestion of the data. And that will trigger automatically the processing of the samples we send automatically the data to Galaxy Australia for processing. We fetch back some information from Galaxy Australia for further processing in the cloud. And once that is processed we go back to a galaxy Australia and run a second set of processing to then generate this final report. And in addition to that we have also this next flow option. It's important to build redundancy. And we have these possibilities. So I think he's sensible to have this. The hobby is yes you need to build as much resilience and redundancy so that you can ensure operations are not impacted so that's why we decided to use and provide this to our partners. So what are the benefits for positive quarantine and for horticulture industries. We have reduced certainly a number of essays and now they need to run for the adopted commodities. Currently hts as a first pass screening so that informs what molecular sites they need to be run on which individual samples so it is more efficient in terms of resource allocation to clear those plans in terms of quarantine testing. And also provides them quality metrics to inform their decision making on these plans that are important and the other benefit I think which was really important is when we have this partnership with academic institutions. It's not only a research collaboration, but also we can transfer that knowledge and expertise. So that they have that capability in house capability. And for industries. Yeah, we see the benefits is cost savings in terms of this it can be quite an overhead to import this germplasm and credit test for. We do see that is one of the initial benefits for them but more importantly, those cost savings can be used to bring in more diverse genetic germplasm that can be used to test how they adapt to the Australian environments and they can build a more resilient business portfolio. Another aspect that I touch upon is, yes. We can look certainly at what are the profiles of of viruses that can be in these commodities. And there is now the particular and the visibility for the industries, whether they would like to build a new business portfolio on a particular commodity that doesn't have an exotic products, but it may have something else that could be of a concern for them to have a sustainable return in their investment. And now we're thinking on implementing some new strategies of how we could potentially implement a strategy is now that we know which viruses are present in this material, how we can assist in cleaning those plants from those viruses. And that is something that we are currently interested to implement. And the biggest benefit in terms of profitability and ability of industries to remain competitive is having access more faster to this important material so and that is something that we're that is part of the journey. So we think we are in the process of using HTS and in operations routine testing, but we still need to rely on on existing standard protocols they have been using over the last two decades. It will take a bit of a time to have full advantage of this technology, but we see once they are using this technology and this other available assays, eventually they will move to adopting this technology as we know it can be more can be rapid in terms of transactions. And also, as we build these analysis pipelines that are robust, reliable, they can have the confidence that they can build the business portfolio, and have this material release earlier. So, in terms of future perspective, I still there is a gap for data generation. There is a lot of data that gets generated and deposit in public databases but a lot of this data is non informative so we need to really develop strategies in which we can generate data that is more sensible and bespoke and can be used for addressing specific needs and initiatives. And we are implementing and we're testing will be testing with over the next couple of years, some strategies in a partnership with a new collaboration looking at seed testing over the next four years or so to assess whether we can make these more specific. The other global initiative, which is important. It's good to have these operations in a in a in a domestic setting, but the biggest impact is when we have this understanding and harmonization of of using these technologies across countries across jurisdictions. So, we are working in a you fresco collaboration. This you fresco initiative is engages 23 countries around the world at the moment we have 10 countries that are interested to look at how it is utilized for plant diagnostics, and that is an initiative that will be rolling out over the next couple of years and we are committed to have an understanding of the best practices and processes across jurisdictions, so that we have a harmonization at the technical level, and then eventually we can move on to a policy agreement that can facilitate trade so the long And from one of my colleagues mark wasm is can we have a plan passport so that can remove these barriers of trade so and that is something that potentially that will come in a few years I think there's still a few building blocks that need to be put in place so from our lesson on implemented this technology in Australia, it took us a bit of an engagement with policy to get to this stage and when we are now looking at global adoption of these technologies I think we need to have that early engagement and champions within the individual organizations to have that engagement that can facilitate this adoption. So, with that, I would like to acknowledge. QG, and the team of QG, Maria Emily, and the work will be report really walla in the galaxy implementation of the report, such a real leblanc and that work on the miscantus work and also in the implementation of the custom database. So, with the implementation of the next flow solution. For this activity, certainly. Professor Matthew bell guard for hosting this activity here QT Chris Williams and Hamish on providing infrastructure that enable this to be our colleagues from the Department of Agriculture. I'm really keen. I have not all the names here but some of our champions, the list is much longer than this and we are really blessed that they have been involved in this activity. Our culture Victoria Galaxy, Garrett Igor. Thank you for that support and throughout the journey and our partners from horticulture innovation. Thank you to CRC and our colleagues from New Zealand that have been also part of this activity. And with that, yes, I would like to thank all the people involved in this journey. And happy to take any questions. Thank you. Excellent. Any other questions from the audience. Yeah, I mean, that was a really cool talk and really cool to see like. Yeah, where you taking the analysis I mean, I think it's a really interesting approach. And I actually I have a bunch of questions but maybe just the one that I'm most interested in. So how do you decide which viruses are problematic. So when you do this type of analysis you also mentioned that you find some novel or unexpected viruses in these samples. And then that you couldn't detect these viruses in endemic species is like I imagine a lot of it is like barely studied and then following from that do you keep the raw data that you collected for retrospective analysis in a couple of years. Good question. Yes, what we do is we have a decision free in terms of based on the HTS evidence that we collect for any of the detections, depending on the quality metrics that we have defined we can assign when we have enough evidence, we can assign to a specific viruses. But then there would be cases where we have a low express also called low tighter viruses that could be present. And when you are collecting this type of data is very reasonable to think we can get a very strong signal so we classify them into a different category which is a potential detection of those viruses so what that would trigger in terms of the decision making is we need a follow up molecular assays to verify those cases that are matching, for example, viruses or by security concern specifically those are the ones of interest. So they can go ahead and run those assays on those. And another category, which is, as you pointed potential this new to science viruses those viruses that are divergent, and they can be more of a challenge because we rely on a small RNA technology. So what we can resolve when working with this type of cases is relatively a small fragments of their potential genome. So what we are now considering is implementing Oxford nanopore approach for those cases where we have those signals and we can use that to determine that we have to resolve larger portions of their genome. So we are working currently into a developing a follow up long as technology that can provide us more visibility on that angle. So both of the data is, yes, it's certainly quite important that we keep the raw data, and this raw data is kept. I just alluded that automatic is an automated process that bring in the data to the cloud. And what we have is an automatic archival of the data from the point of view of the policy regulation. We have confidence that any raw data that has been generated has not been touched by no one. So that is part of their couple process. No, no one touches that data that is archive and at the moment we're considering to keep that data forever. Typically, depending on initiatives, dealing with this kind of data, they can keep the data for seven to 10 years, typically. And for now we've put in place strategies that can allow to have much longer retention cycles for those data sets, but yes, it is important to have this, this backup data. And how you say that, yes, we do have an alternative copy that we use for the processing of the pipeline but yes. Thanks. Great talk very important research. I'm curious about your slide on the workflows, where you have next flow and galaxy and we talked a little bit about this but I'd be curious to know whether elements or features in next flow that you found easier to do and perform in and then vice versa, where the elements of galaxy which you found were easier than doing in next flow. Awesome. Thank you. Fantastic question. Yes, what we one of the strategies where we decided to have these two flavors of deployments of the pipelines were for two different purposes initially. So we decided to have the next one implementation because it's a very portable solution that can run on multiple. So it could be the cloud could be on Prem HPC could be a local server. And we were really keen to use that solution because you can upscale quite easily, you can run thousands of samples without any changes to the code and can really upscale to any demand that maybe require. So, one of the, the process of using next flow is that we can automate the whole process from end to end from the initial use of the road out all the way to the generation of the reporting. And when we look at galaxy, we use galaxy for a different purpose, not really initially, not really for processing all this data, but for training, we're really keen to provide this training element to to personnel of the funding agency, so that they have that accessibility, because as you as you might be familiar with next flow, you need some digital expertise to go on and deal and make sense of that and access to those resources. So which are not readily available in the team. So we're really keen to use galaxy for that. One of the bottlenecks we found is that not every tool or not every option might be yet available in galaxies so that's why we run an initial process in galaxy, we go back to the, to the cloud and the footed process and then go back again to galaxy to complete that process. Perhaps that may be one of the, the, the initial bottlenecks that we have experienced, I mean said that, I think it has been really informative for us to use galaxy to provide that accessibility to the end user and I think it's important to have that engagement with the users because at the end of the day they will be making decisions on the evidence. So, and what we work towards is to have the same information coming through galaxy, but also this next flow, and having access to these two, it provides them redundancy in terms of, as we know, as users of galaxies, sometimes we have some maintenance, for example, that we may not be available to use some of the servers. And if we are pressed for time, we can rely on next law, but next law can be potentially a bit more cost demanding on using the resources cloud services so in that sense yes, it's really good to have galaxy as well available. So, a follow up question. How, I mean, would it make a difference in the development of pipelines to you, if you were able to more easily just add in a command line and run it as a tool. So, like, you take a script, maybe have an interactive way to like see if the script works. And you can just use that as a tool is that something that would be interesting. Yes, absolutely. I think that will be really will provide a lot of facility for the community, because we implement this in house scripts for processing of the data, whatever that process it might be. And you have an easy way to incorporate that into galaxy I think that will be very useful. And one of the things that was initially chatting is having these histories. So we process about 400 samples in this project and looking at 400 histories can be a bit of an experience for someone to go and look and make sense of that information so having the possibility to have an script to go and pitch reliable. And that is needed to make sense across all those histories and merge that and combine that in the single history. That will be also very useful for us so we can go and fetch these outputs from all these individual runs and go back into having a single site where we need to go and look at that will be also of interest. Thank you. You mentioned at the beginning but just briefly that you know this is sort of big business and if there's delays in this or probably you know areas in this this costs some people a lot of money. I noted that you know I know that a lot of the sequencing providers you use to diagnostic services and they're accredited. Can you just comment on the need for accreditation of the computational environments that you're doing the analysis on as well and how do you you know how do you ensure that they're doing what they're meant to be doing. Thank you a fantastic question again. As part of I haven't alluded to this but as part of the implement adoption of this technology we need to implement the standard operating procedures and to end along the journey of how the data is dealt. And also, that the generation of the data, because we can say, small RNA is the way to go. And, and with you and unique molecular identifiers or unique unique dual indexes. We find that combination to be the most sensible. But as you go and rely on different service providers utilizing that it may not necessarily get you to the same outcome, in principle it should but not necessarily there is warranty that that can happen. So as part of this process, we have a set of positive control plans. So, and that is at this stage, we work with this particular service provider, working with this positive control set of plans that we've optimized and we know we can detect. So there is that evidence, but if you were to go and work with a different service provider, then we'll need to go through that process where we yes we need to make sure we are still getting the same information. Yes, and that is part of part of the process for us. So that can be certainly a challenge initially when we started to use different providers we thought we should get similar results but not necessarily. And also this can be impacted because you could be using for example, a novastic X, and that is a much higher throughput instrument where you may be processing your samples along X number of people. And also impact what you are detecting. So yes, we need to have that visibility of what else has been added to the multiplex experiment in that particular run. So we would recommend yes not really. I mean yes it's separate point of view of cost effectiveness. This is good to use this larger high throughput instruments, but from the point of view of ensuring that making sense of what signals we observe we need to have that visibility of the metadata of the samples that were used in that particular experiment so and that needs to be considered when looking at making sense of these and also having this accreditation, although that is not a formal conversation yet. That needs to, we need to engage that accreditation, but I think it's really sensible that we have that. I think I'm glad that I typically I talk too much so I tried to cut a lot of things, a lot of things from here it goes last time I talk I went a bit without any time for questions and so yeah. With this, I would like to thank the, this is my first galaxy conference. So really thank you. I would like also to thank you all for developing this resource. I'm making it available to the community. As you can see this is just one little case study where it has been valuable for us to adopt a particular technology to hopefully make a difference to businesses and our ability to be competitive profitability. I mean, there are more impacts on these because as we reduce the inversion of this past, we can also protect our nature, our environments as well. So thank you all.


Hi everyone, Joe for jaspyscasebreaks.com coming at you with 2016, a blast from the past, Panini National Treasures Football 4 box random team break number 1. 32 spots, everyone gets a team in the NFL randomly. A lot of great stuff here that we can chase. Big thanks to everybody here for getting into the action and congrats again to the winners. And thanks for grinding out all those fillers, I appreciate that. All 32 are in once again, let's do it. Let's roll it, let's randomize names and teams, four and a three, lucky seven times. One, two, three, four, five, six, and seven in final time. After seven, we've got Robert all the way down to Gale. Four and a three, seven times for the teams, one, two, three, four, five, six, and seven in final time. We've got the Jets down to the Eagles. All right, Robert with the Jets, Tom with the Chiefs, Chad with the Bengals and the Bills, Corey with the Browns, Robert with the Buccaneers, Matthew with the Texans and the Saints, Steve with the Dolphins, Matthew with the Falcons, Jer with the Giants, Robert with the Patriots, Jose with the Colts. Michael, you got my Raiders, Tom with the Titans, Chad with the Rams, Terry with the Vikings, Matthew with the Ravens, Matthew also has the Bears, Robert with the Lions, Jonathan with the Boys, Matthew with the Jags, Robert with the Pack, Jose with the Bolts, Tom with the Panthers, Matthew with the Broncos, John with the Seahawks, Freddie, you got the Steelers, Chad with the Niners, Gale with the Cardinals, Matthew with the Washington Football team, and Gale with the Fly Eagles Fly. Let's order these alphabetically by team and we're going to pause the video really quick when we come back. We're going to see if there's any trades and then we'll have the break, stick around. All right, welcome back folks. We had a little bit of a, a little bit of trade chatter, but in the end no deals were done. Thanks everyone for getting in. Is that, we had that big, we had that game on TV, is it really still going on? The Vanderbilt, Arizona, college baseball game? All right, remember they do their stickers really weird, so even the NT was released in 2017, but it's actually 2016. You just can get kind of confusing sometimes. You can see 2016 right there. All right, so there's 2016 NT football. Thanks everyone for making this happen. This was before they changed the, uh, changed the boxes. You get that nice little NT pop right there. All right, first off the top is Alshon Jeffery to 25 for the Bears. That'll be for Matthew. We got a dual relic right here, 17 out of 99 Will Fuller for the Texans, Matthew Shearer with Houston. 94 out of 99, Leveon Bell, Steelers edition. Now these boxes go, the empty boxes go to the, to the, uh, to the kids that come into the shop. It goes to a good place. Steelers, that'll be for Freddie. We got nine out of 25 friends and foes. They were once friends, now they are foes. It's Kevin White and Wendell Smallwood. So that'll be a randomizer between, um, the Bears, Matthew, and the Eagles, Gail. One 30 toddlers wanted to hit the bell. All right, so we'll randomize those two right there. We got tremendous treasures. Uh, Moritz Borenger. If you remember him, he was the first, uh, I believe German born player to be drafted to the NFL, 23 out of 99. I don't know if he worked out, but I think, I think he has that distinction. Vikings, Terry, and we've got Robert Kelly, one of one. Printing plate autograph for Matthew, Shearer, and the Washington football team. Ooh, Ronnie Lott, 32 out of 49, that is, for the Niners. Chad with San Francisco. Rookie gear, dual relic and autograph, black ink auto, 18 out of 49, Malcolm Mitchell. Patriots, Robert Flores with the Pats. Oh yeah, I think there might be a book of box. All right, so a book of box, 31 out of 49, Josh Doxson. It's a nice patch. On book autograph, 31 out of 49, going to Matthew and the Washington football team. Good luck. We've got a redemption down there. Now there's, I'll bet that redemption is going to be expired. I realized this is 2016. A lot of times, Panini is pretty good about doing something for your expired redemptions. They'll try to get you the card itself most of the time. If not, they can try to get you points back in return, something commensurate in value. They'll try their best to do that. So let's keep that in mind. 17 out of 99, Carson Palmer. Cardinals for Gale. Got Jamal Charles to 25. Chiefs, Tom. 91 out of 99, Century Materials, Antonio Gates. That's for Jose, tried to trade, couldn't trade Mojo. Devante Booker, 11 out of 23, Duel Relic, and a piece of the pigskin in there too for my rivals, Matthew Shearer and the Broncos. Another, another randomizer here. We got National Treasures NFL gear, Corey Coleman Browns. Corey Coleman for Corey S. We've got randomized the Browns. Will Fuller, Texans, Matthew, Josh Doxson, watching football team Matthew and the Quantredwell Vikings, Terry. 41 out of 99, nice tremendous treasures. Tyler Boyd. Chad with the Bengals. 58 out of 99, Jalen Marshall. Robert Flores. About the last spot, Mojo. Straight up gets the Jalen Marshall. We got a Kenyan Drake jersey and autograph. 83 out of 99. And now I've ended up with the Raiders. This still goes to the Dolphins of course, Steve Melendez with this one. And it's signatures. Todd Gurley, yeah, it is expired 2018. This would still be Rams edition of Todd Gurley. But when was he drafted? This is second year Todd Gurley, I think. Yeah, he was drafted in 2015. All right, so Rams, that'll be for Chad Coleman. So, like I mentioned, Chad Ricciatopini. In fact, I think they have a system now, I've been told, where if you go through the redemption process, if it's expired, they'll give you some options, I believe. So there you go. Maybe they'll actually have the card that they can still send you. And we got Paxton Lynch, rookie colossal signatures jersey and auto for Denver, Matthew. All right, halfway through this break. 29 out of 99, Frank Ork. Confirmed six, actually saying they actually still redeem expired ones, which is awesome. I've heard both things. I've heard, like, even if it's expired and if they don't have the card for whatever reason, that they'll try to exchange a decent amount of points with you. If it's a top player. 21 out of 49, Brian Erlocker. But yeah, the other companies I feel like just say no, just outright. But Pinini does work with you, which is great. Matthew with the Bears. Another randomizer here, 97 out of 99, friends and foes. Braxton Miller and Michael Thomas, they were once friends and now they are foes. 11 out of 99, Alan Hearns. Three color patch for Matthew and the Jaguars. And we've got a one of one plate, Navarro Bowman. Two color patch. And it looks like it's a little game use, a little bit of dirt right there, too. That's awesome. That'll be for the Niners. That's for Chad. Chad, all aboard the Big Head Express. Woop woop. We've got Joaquin Grant, 51 out of 99, Jersey and Autograph. Steve with the Dolphins. Yeah, Derek, I don't know why the rest of the companies don't do that. 40 out of 99, Farrow Cooper. Chad with that one. And a dual auto. Cardell Jones and Jonathan Williams. Eight out of 10 for the Bills. Buffalo. Chad Coleman with the Buffalo Bills. From Chad Coleman to Corey Coleman for the Browns. And that goes to Corey. Corey S with the Cleveland Browns. Back here is two out of 49, Charles Tapper for Jonathan and the Cowboys. Final box, everybody. 2016 NT. Let's see what's been marinating in this last box since 2016. Nothing ventured, nothing gained. Let's see what we have here. 58 out of 99, Jamal Charles. Tom with the Chiefs. 29 out of 49, Melvin Gordon. Chargers, Jose. 92 out of 99, Rod Woods and Relic. Steelers. That'll be for Freddy. Six out of 19. It's a cool dual Relic right here. I like that texture in the top Relic. Corey Coleman for Corey S and the Cleveland Browns. Another randomizer. We've got Tyrod Taylor, LeSean McCoy, Reggie, but no, these are all Bills. No randomizer. Buffalo. Chad Coleman with the Buffalo Bills. Nice. Tyrod Taylor, LeSean McCoy, Reggie Bush and Sammy Watkins. There's Braxton Miller, 64 out of 99. It's a nice big patch there. Texans, Matthew Shearer. 19 out of 22, Keanu Neal. Matthew Shearer and the Falcons. That's exactly the reference, Vegas Derrick. 48 out of 49, Connor Cook. Vegas Derrick knows the reference. 48 out of 49 for the Raiders. That'll be Michael Robinson, Connor Cook. And AJ Green, four out of 10. Bangles autograph, going to Chad. And wow, last but not least, it's a strong one here. Two color patch and autograph. Rookie, papped auto. Ezekiel Elliott, 82 out of 99. Jonathan Arnaldi won that spot, got randomized the Cowboys and gets a nice big hit. There you go. Nice finish, ladies and gentlemen. Let's do some randomizers. Just three randomizers. We got three cards here. Yeah, Ezekiel Elliott, if that team just clicks, that card can continue going up and up. That is Ezekiel at RPA. So first we got the Bears Eagles, Chicago and Philadelphia randomizer. Then we pulled the Cleveland, Houston, Washington football team and Minnesota randomizer, the quad player jerseys. And then we got the other friends and foes, which was Houston and New Orleans. We'll use one dice roll for all three randomizers. Let's roll it, randomize it eight times for each one. One, two, three, four, five, six, seven, and eight. After eight times goes to the Fly Eagles Fly. So that'll be for Philadelphia. That will be for Gale. There you go, Gale. Next one, eight times. One, two, three, four, five, six, seven, and eighth and final time. After eight, Minnesota. That's going to go to Terry Cahill. Terry, Quad Relic going your way. I don't know if I called your name out too often during the break, but I appreciate you getting in. And the final one, five into three, eight times. Team on top gets it one, two, three, four, five, six, seven, and eighth and final time. Stays with Houston. That's going to go to Matthew Shearer. We'll get this dual relic right here. Thanks, everybody. I'm Joe for jaspyscasebreaks.com. Thanks for knocking out that 2016 NT football. I'll see you next time for the next break.


Good evening. Welcome to the Médend de la Paix and to the Graduate Institute. I'm Hugo Panitz, I'm a professor here at the Graduate Institute and I'm the director of the Center for Finance and Development. I'll be very brief. I just want to thank you and you wider for deciding to have its 23rd annual lecture here at the Graduate Institute. And I'm especially excited because the speaker is Santiago Levy. Santiago has done many things in his career and he will be introduced in a minute. But one of the things that brought me close to Santiago that he was the president for knowledge of the Inter-American Development Bank and among the other things he was directing the research department where I worked for a long time and I always consider res, like we call it, like my second home. So it was great to have Santiago here. So now let me invite Kunal Sen who is the director of UNO Wider will introduce Santiago properly. Thank you Hugo so much for the introduction and also hosting us in this wonderful venue. So let me start by saying welcoming you to the Wider annual lecture 23. The Wider annual lecture is one of our Wider flagship events delivered by an eminent scholar or policymaker who's been a significant contribution in developing economics, social sciences, policy, all of these different areas. And the first lecture was given by Douglas C. North in 1997. Since then the lecture has been delivered by an impressive lineup of scholars such as Santiago and political actors four of whom have received Nobel Prizes in economics. UNO Wider is part of the United Nations University. It's based in Helsinki and we work on informing economic and social policies especially looking at the global south. In this next four years, 2019 to 2023, our research focus will be on transformation in terms of economies, states, and societies and how can we transform economic states and societies to try and achieve the SDGs, the agenda 2030 which is a very important part of the United Nations mission itself. This year's lecture fits perfectly in the research agenda of our research program for the next few years. How would states and economies especially Latin America need to transform the social insurance systems to deliver inclusive economic growth and to reduce informality particularly a very important goal in the SDGs, SDG decent work, SDG8 and this lecture really addresses that in a very central manner. And that's very exciting for us. We know that Latin America and particularly what we see in Chile, they're incredible, they're really significant protests now of social inequality which reminds us the importance of trying to think about the questions that Santiago's going to talk about later today. So we are very pleased to have Santiago here and we're very pleased to have a lecture in Geneva. We've chosen this location for many different reasons. One is that we have a fantastic host here grab the get-in-sit of Geneva but also because we think that arguments we're going to hear from Santiago tonight are really important in the discussion, the conversations happening, the different institutions that are here in Geneva. And we really feel that this particular discussion we'll have tonight is very important, the wider discussion on informality, social protection, inclusive growth, decent work. That's very important to UNIWIRD's own mission itself. We're going to also stream this lecture live and be available to watch online for many months and years to come. And so it's not only going to be having the lecture if you're going to be listening to the lecture here today but many others are going to watch us over in the next couple of hours. I wanted to also thank Lugo Panitza and Jean-Louis Arconne, the gratitude for accepting a suggestion to partner this particular for the annual lecture. It's a very difficult thing for a better partner for this annual lecture, for this topic, for the lecturer and for us. And we're really happy that we could do this together. Now I'm delighted to introduce Santiago Levy who will deliver the 23rd UNIWIRD annual lecture. Santiago is a non-resident senior fellow at the Brookings Institute and the president of the Latin American Caribbean Economic Association. From 2008 to 2018, he was the vice president of the Inter-American Development Bank. In 1994 to 2000, he served as deputy minister at the Ministry of Finance in Mexico. At the Ministry of Finance, Santiago was the main architect of Progressive Office Studies, the iconic conditional cash transfer program that we had in Mexico at that time and since then. But to understand that Santiago was doing in Progressive, you need to go back in time. You don't need to go back to 1995 when Mexico was going through a very difficult time. At that time there was an economic crisis and there was a sharp rise in number of poor that led to almost an increase to a third of the population. In the aftermath of the crisis, the incoming administration of which Santiago was a part was faced with limited capacity to assist the poor. With a sharp economic downturn, there was little room to maneuver to increase social spending. At the same time, most anti-poverty policies in Mexico had considered generalised and targeted food and in-kind subsidies that just reached a fraction of the poor. Santiago became undersecretary of finance in 1995 and President Ernesto Zedillo put him in charge of a team that would draft a plan to address extreme poverty. Santiago launched a pilot project to this team in three cities. It consisted of direct monetary transfers instead of the subsidised milk and tortilla programs that were there in Mexico for a very long time previously. But the project succeeded in improving nutrition and the user health services. It did not involve education, which was seen as a key element in building human capital. And Santiago realized a particular problem in that particular, the pilot project itself. He was also considered with the challenge of reaching the poorest of the poor in Mexico where most are concentrated in rural areas. As a consequence, Progressive was launched in 1997 as a conditional cash transfer program. Progressive was innovative in at least four important respects. First, the program embraced by design a multi-dimensional approach to poverty. It linked transfers, income transfers with some of its interventions in health, education and nutrition, placing a strong emphasis on tackling the intergenerational transmission of poverty through into a human capital investment by education. Second, it was one of the most distinctive features of Progressive was its emphasis on the rural poor. Third, Progressive followed a clear rule-based system of identification, selection beneficiaries. So the program was not hostage to discretionary manipulation, associated with opportunity political behaviour that was often associated with previous anti-poverty programs and policies that was in Mexico previously. Fourth, and perhaps the most important, Progressive included an independent impact evaluation protocol that involved the academic research community right from the beginning, both nationally and internationally, that helped not only improving the program's effectiveness over time, but it also made the program legitimate in the eyes of successive governments whenever there was a change of government. And that's why Progressive survived for such a long time. That's a very important anti-poverty program. And thanks to the rigorous impact evaluation methods and, in fact, recognition that we have now seen this year in the Nobel Prize in economics, the three economists who work in the economics, it's a kind of a reflection of that, in my view. Thanks to this impact evaluation methods that were built into Progressive right from the start, what we have is a very rich evidence base that showed the program had very strong positive effects in reducing multidimensional deprivation and building the human capital of the poor. Progressive's human development approach became a precursor to other conditional cashier programs and country after country, in Latin America and then beyond, became, realized the importance of such programs and particularly providing social protection for the poor. Progressive, along with the other iconic Latin American program, Latin America, was a familiar, were the ones that had huge legacy effects and San Diego was very instrumental in popularizing programs in the developing world. But then, San Diego moved to a different area of research and in more recent writings, San Diego turned its attention to understanding the poor economic performance of Mexico, in spite, and particularly after the press of Christ in 1994, impressive macroeconomic stability and close integration of the world economy through and after. In his recent book, Under Rewarded Efforts, the elusive quest of prosperity in Mexico, San Diego uses very rich data meticulously done empirical analysis to show that different facets of Mexico's policy environment, social insurance mechanisms, tax policies, counter enforcement, led to poor microeconomic implications, incentives, that tax the hyperactivity formal segment of the economy and subsidize the low productivity in forms of the economy, leading to overall economic growth is very slow, particularly because of low productivity growth.  So in his lecture today, San Diego will bring together his earlier interest in social protection and his most recent interest in informality. In his preface to San Diego's book, this most recent book that I mentioned, Danny Roderick Harvard University says, and I quote, when sound economics is combined with a practical pragmatic bent, it can be a potent force for good. There are very few people who are as good and living embodiment of this as San Diego led. We in the United United wider would hardly agree with Doni Roderick. And I'm so pleased to invite Don San Diego to help to provide the 23rd wider annual lecture. San Diego, thank you so much.


Hi everyone. My name is William and I'm going to be talking about putting measurement converters on the web. So why did I make the converters? Some reasons are that a designer asked me about what pixels to M's was how to convert from pixels to M's and I wasn't sure and I'm a web developer so I thought it would be good to find out how to convert pixels to M's. And it's more reliable to build your own converters. For example, kilometers are not yards and that's a website, that's a real website. You say the internet's not entirely reliable? Well, it just came up when I searched. One of the first things I did was to go on Google to find out how to convert pixels to M's. Here's one example of a website I found. I wasn't sure what a base pixel size was so that didn't help me. Here's another example. I wasn't sure what a default pixel size was so this also didn't help me. There were lots of tables as well and complicated converters. In the end I made this. I thought it might be helpful for learning and I wanted to practice front end development. Something I wanted to do was to make the input boxes except only numbers but E appeared. I was testing the numbers type and that happened. So apparently these characters are numbers. The solution was to make an input type equal text. But I thought that my converter didn't look so nice so I added new features. I also realized that the font size in M's for the child element is relative to the font size in pixels of the parent element. And this is how you convert from pixels to M's, I think. I made this just to check all the texts are, they're all 2 Ems. Here's the new user interface. There are SVG buttons, animations and I use Flexbox. One of the most interesting things that I used was SVG clip path. The clip path property. I used Clippy to help with these to get clip paths. There are still many improvements that I want to make to the website. Here's the browser compatibility. You can look at the code and you can view the site. It's online. That's the end. Do you know why E and E are numbers? I think it's to the power of. I think that's why it's like that. And the other thing is why convert pixels into M's? I'm not sure, but I was just It seems to be a problem that many people have with so many converters being around. Obviously. Which is strange. Thank you, strange. Like for me, when I go to websites, the hardest problem that I have is usually when to use M's and when to use pixels. I mean, usually if a form is rather straightforward. But sometimes I find myself using margins in M's and addings in M's too. If I feel like that the amount of space around text, for example, should be relevant to the text size. So you use pixels sometimes and M sometimes? Yeah. That's always the hardest question for me is when to use what? My answer is for everything use M's or M's. But for those small things where you have to use pixels, you use pixels. Like for example, one or two pixel borders, you use pixels because you can't afford to have sub-pixels. When you use M's or M's, you can't go into sub-pixels. Right. And the good thing about Rams and M's is that they can't go into sub-pixels. Can you actually set anything in sub-pixels? You can do quite something in pixels, technically. When older CSS things like pixels were absolute on the screen, around IE7 they changed to sub-pixels and virtual pixels. Because in the old days, increases had a size and nothing else would change. So if you got an image that looks 50 pixels wide, it would stay the same size. So they changed out the pixels in our mode and they've also captivated down to be sub-pixels. A sort of thing that's a question between they actually showing how they encapsulate stuff in browsers. They all basically have a sub-pixel measurement as their base. Gator uses 60 pixels. So one pixel is 60 years. Grom I think uses something else, like 65 or something. Microsoft uses 100. But they all basically have a base measurement. So sub-pixels are ashamed of what they do actually being such. So another question that I was talking to you, why not points? I remember back in the days, everything was points. And it was like you measure the font in points, not in pixels. And like now it's all empty. Yeah, we've kind of gone, because they end up going around originally. And then it's a type of graphic measure just like the point is, and it's relevant in certain circumstances. They're everything going in. Now everything's kind of going back towards pixels to each step. So the question was more, what's the point of using the energy pixels are very relevant. And so before, when you've got something as relevant, so if you go above and the panic around it is going to be in relation to the type size, then you enter exactly what you need to have. If you're measuring like the layout of something on the screen, then pixels are probably what you want. And how about red, when we want red? Red is nice. If you really want red is group M basically. So if you group sliders to 16, then it's exactly 16. If you use it, I can't remember why. Usually if you can't figure out why the hell one M just thought the fault was there. Then you use red. One thing that is very useful for is that you've got a base grid there. If you want that to vary based on the group of sliders, which is something you probably want, then switching it to red could be useful. But since pixels are variable now it's not so important anymore. I think M is useful for visualizing all your measurements in terms of a ratio to a single base size. So it helps you to think of one measurement as, you know, this is twice the usual measurement. I say this 32 pixels doesn't tell you whether it's twice or one half times or one times the usual default size. I think it's actually a rare use case for M in that sense, because when you really want to have, let's say you think of the website as a bunch of different components, when you really want to have like one component inherit the font size from the base component, right, because it would be a use case where you feel like if the base size is 16 pixels then this component needs to be two times that in terms of standard font. But when is that not to be the case? Actually I think RAM should be more useful than M's most of the time. I don't know if that's any clear. Well, for example the button. If you've got a button, then the padding inside the button is relative to the font size. And if that's the case, you can compare the base button styles once. And then if I've got a big button over here, I'll just have the font size and the rest of it takes care of itself. So in that case, using the M's is really relevant. And the RAM is not sorry. But if you want all your buttons to be the same size, and you're somewhere in some piece of text that has been scaled for some reason, then you won't get back to the default size thing. Yes, and that's the general reason for that. It's when you want that reference button to be the same size. You still have to figure out why, but it does come up. It's good to know that it exists. Well, that's the thing. I recommend nautical miles. Here into fractions or something.


Biogiography. Biogiography is the study of the distribution of species and ecosystems in geographic space and through geological time. Organisms and biological communities often vary in a regular fashion along geographic gradients of latitude, elevation, isolation and habitat area. Biogiography is the branch of biogiography that studies the distribution of plants. Zogiography is the branch that studies distribution of animals. Knowledge of spatial variation in the numbers and types of organisms is as vital to us today as it was to our early human ancestors, as we adapt to heterogeneous but geographically predictable environments. Biogiography is an integrative field of inquiry that unites concepts and information from ecology, evolutionary biology, geology, and physical geography. Biogiographic research combines information and ideas from many fields, from the physiological and ecological constraints on organismal dispersal to geological and climatological phenomena operating at global spatial scales and evolutionary timeframes. The short-term interactions within a habitat and species of organisms describe the ecological application of biogiography. Historical biogiography describes the long-term, evolutionary periods of time for broader classifications of organisms. Early scientists, beginning with Carl Linneas, contributed to the development of biogiography as a science. Beginning in the mid-18th century, Europeans explored the world and discovered the biodiversity of life. The scientific theory of biogiography grows out of the work of Alexander von Humboldt 1769-1859 Hewitt Cottrell Watson 1804-1881 Alphonse D. Kondall 1806-1893 Alfred Russel Wallace 1823-1913 Phillip Lee Sclatter 1829-1913 and other biologists and explorers


multiple baseline across subjects. Some people might want to say individuals, but it doesn't really have to be an, it's an ethical thing. I don't know what to say. Ethic individuals or subjects. I like subjects. It's, but we're not talking about math and science. We're talking about organisms, right? So it could be rats and pigeons. Anyway, we got to go fast now because we're running out of time for this one. It's a multiply sign across three people or subjects. Could be rats, could be pigeons, right? So don't forget, start your baselines all at the same time. Interventions are offset by, I don't know, a couple of days. So basically some stable behavior. That's really all you're after. So you offset everything and then find out if your intervention worked by seeing if there was a change in behavior at the phase change across all three subjects. It's that simple, right? It works with pigeons. It works with rats. It works with freaking humans. It's just baselines. There's multiple baselines and they're ABS and they're all stacked together. And how do you stack three non-experimental designs and create an experimental one? You're going to have to watch the other multiple baseline videos to figure out.