 OK, everybody, if we could grab your seats. We're live, Chris. OK, thank you, everyone. We're now going to do a quick wrap-up of day one of the NF Core Hackathon, October 2023 in Barcelona. Thank you, everyone, here today in person. It's been an amazing day seeing everyone talking, kind of socializing, and getting a lot of stuff done. By the number of people who have come and asked me, can we do this new thing? I feel like it's been a productive day, so it's good signs. Hopefully, everyone's had a really good time. We are going to quickly have a few wrap-up slides for me, group leaders, just to summarize some of the work we've done. Now, I know there's a lot of you here today in person and online, and it's kind of impossible to represent everything that everyone's done. So apologies in advance to those of you who may feel underrepresented on the slides. We're going to try and strike the balance of it not being boring and too thorough, but give it a flavor of the kind of things that people have been working on today. So without further ado, who wants to go first? Yeah? Sure, like this. OK, hey, everyone. First of all, thank you to everyone and the modules and sub-workflows group for adding a bunch of new modules. I have the feeling the numbers are a bit low if I look at the GitHub repository. But in any case, we had about, I think, 13 new modules or more today for a bunch of different things. Then several people worked on adding NF tests for some modules. And we had multiple bugs fixed, bugs fixed, and Adam added this new, oh, sorry, better. OK, we had 13 new modules for anyone who didn't hear me. NF tests added for several modules, several bugs fixed, and sub-workflows. As I mentioned, I think the numbers are a bit low, so I kind of just checked a bit on the projects board. But we had 13 new modules, 13 PR open and 11 of closed, and 11 PRs reviewed. So don't forget to add your PRs for today still or also for tomorrow then. Yes, it has not been updated. Can I? Oops. How do I do full screen? How do I do full screen with that? Sorry. A slideshow. Hello, everyone. Yes, sorry, I'm so bad with the Mac. You should never let me get close to a Mac. So yes, pipeline team, we've been like, not we. Everyone else but me has been working amazingly well, so that's good. Like, congratulations to all of you. I'm proud to be part of this team. So I think one of the biggest stuff was the consensus that we started this world discussion about refactoring the pipeline to accommodate NF tests, so that was good. We added first NF tests for some everyday SICK module. There was adding some NF test module in some NF tests in the NFCore fund scan, adding some new crack and sub workflow to the demultiplex pipeline as well, updating some of the pipeline as well as we said, so Metal SICK, adding some new profiler in the tax profiler pipeline, adding some new stuff in the differential abundance pipeline, adding new module to Sarek, better docs in differential abundance as well, a metromap as well in... Oh, good job. No, no, that's nice. And now, like, fetch SDS metadata that can use FFQ. So, oh, that's amazing. Congrats Rob on that. And yes, next slide, sorry. That's already... So, good job everyone. And I will do better tomorrow. Yes, hello everybody from the infrastructure group. We were this smallish group here, but also one online, Marius. And we worked on, as usual with infrastructure on everything. So first in the morning, we got the AWS CLR runners running for the modules. So we... You got these starting models through because we had free runners. So, and similar with the pipelines, this will also then in the future, hopefully run on AWS. So we don't run into the issues with the GitHub runner limits. We still run into issues with the GitHub API limits, but that's a different story. Then, Niklas was working on general bug fixes in the NF validation. And also, I think, especially for Sarek, added support for sample sheets with no headers. Alfred picked up three stale PRs, which were all dealing with type checking in NFCore tools. So we will now get types in tools, which is very exciting. And Sofia worked on the website to add an accordion effect on the parameter pages so you don't need to see the whole group, but you can close them down and scroll faster to certain sections. And Marius, who's online, did many things. Specifically, he added some more documentation about using profile debug, which I actually didn't know about. So you never stop learning when reviewing PRs. In total, we reviewed around nine PRs. We opened one issue in closed five, so win. We opened three PRs, merged 11, again, win. And I closed one because Jose was faster than me with a PR, so yeah, that's what we have one person. Thank you very much. Howdy, folks. My name is Ben Sherman, and I'm in charge of this new Nextflow Plugins Group. If you're wondering who I am, I wasn't here this morning because I was stuck in passport control. Not because I'm a sketchy individual, but because there was just a really long line. I got through just fine once I made it to the front of the line. So now we're here, and we got all kinds of stuff going on now in the Nextflow Codebase and a growing ecosystem of plugins. First of all, in the Nextflow Codebase, we got Jordy, my colleague. He's working on this issue that has been around for a little while. Some people have requested basically being able to specify a checksum whenever you download a remote file, say like from an HTTP URL, being able to provide that checksum so that it'll verify it for you. He told me that he just finished it before he left, and he's gonna test it tomorrow. We got Mahesh working on the join operator and some other operators to make them work better with the typical structure that you guys like to use where you have like a metamap and you wanna be able to say like join items based on certain keys within the metamap. By the way, if you wanna join on just the whole metamap, you can just do that, but if you wanna do certain kinds of keys, that's gonna require some extra plumbing. So he's working on that. We got Francesco, who wants to expand the Nextflow training to include some sections about, I believe by application-specific, he means some trainings that where you work through specific enough core pipelines just to show you how to use them for whatever analysis they're designed for. And then we've got this new plugin called the NFCO Tube Footprint that'll basically show you how fast you're burning the world with every analysis you run. And so it looks like Sabrina is leading that and she's adding some stuff from Green Algorithms. I don't actually know what that is, but I assume it's achieving her goals. So go Sabrina. We got enough proof. So this was actually started last year by Bruno Grande. He's since moved on to better places and he handed the plugin over to me. And so now I'm working on it. You may have seen some releases on Slack recently. We added support for bio-computed objects. I'm now working on AutoCrate. Specifically, this is called the Work for a Run AutoCrate, which is, I would say, a more detailed provenance report for your pipeline runs that'll include stuff like input files, output files, even like the specific tools and scripts you ran, which apparently you guys like this format out here in Europe, so we're gonna make that for you. And then Rob Newman is just working on a tiny little improvement where whenever you have input files that came from, say, like a GitHub repo or GitLab repo, that the provenance report actually shows that URL, so you can just click on it instead of whatever local path it gets staged to. So that'll be nice. And then we also got our friends from Quilt Data, Ernie and Kevin. So they've been spinning today trying to set up a, I believe, an S3 bucket that they'd like you guys to use that you'll be able to upload on Quilt packages too. If you're not familiar with this Quilt plugin, basically it's the plugin itself, if you do a pipeline run with it, at the end of the run, it will create a Quilt package, which you could think of it as sort of like a provenance report, but it contains a lot. You can really put whatever you want in it and uploads it to a bucket, like a S3 bucket, and then Quilt has a browser where you can go and view all that stuff kind of like GitHub, but for data results. And so what they'd like to do for this hackathon is collect, maybe make a few example packages for all the different NF Core pipelines. So if you guys are interested in that at all, please go talk to them or message them on Slack because they probably need your help to figure out how to create those packages and they can help you get started with that too. I forgot to add a funny GIF. I'm sorry. I'll try to do better next time. That's all I got. Thank you folks. Brilliant. So just to wrap up, thank you very much everyone. Thank you to our project leaders there for giving us an overview of everything. And thank you to all of you, both here in person and also online for hacking with us. Some really exciting start to a day. Hopefully everyone feels like they're really kind of got sunk into it now. Know what they're doing and we'll kick off again 10 a.m. tomorrow morning. Can be back here and sort of just crack straight back on again basically. Quick reminder, tomorrow we have the hackathon social in the evening. Remember there's not very long to get there. So we're gonna be doing the same wrap up, six to six thirty tomorrow evening. And then we've got to get to the venue to be there ready to start at seven. So basically you're probably gonna have to come straight from here. So just bear that in mind, bring anything you need with you. And we'll all sort of probably track over in a big group. Otherwise, thanks very much. And we'll see you bright and early tomorrow morning. Have a good evening.