 Hello, and welcome back. So, yeah, now we have upcoming a few short parts. So first will be your future query in scientific computing where we sort of give some like high level information about what you can expect and some other resources available to you. This didn't really fit anywhere else that well. So we did it here. And then after that, we go into connecting to the cluster. So the way this works is that we have a demo session of connecting to the cluster now. And then you can go to zoom and practice connecting, like actually try to do it, ask for help there, whatever. And you should be all ready by tomorrow when we begin the course because we'll assume that it works and we can get started right away. So, and if you already are connected or once you get it working, you can just leave. But please check Hack&D and give us some feedback there. You'll see a new feedback section. So with that said, are we ready to begin the next part? Yeah, I guess this is a short motivational talk. Why do you need to care about scientific computing? Of course, maybe not all of us will be coders or programmers or scientists or whatever we will end up doing our career. But in general, I think that these types of skills are the equivalent of a driving license. And there is no other way of learning than interacting with the people who can already do something and learn from others and try to learn with yourself. Of course, you need to practice. So what we're trying to promote that as it's written, you do not go alone. We try to create an environment that is inclusive. We all come from so different backgrounds, different countries, different interests. But we have this common goal of learning to use these tools and get the best out of these tools to do what we want to do, whether it's science or whatever we will do when we grow up. So here, in this section, in this short page, there's a collection of links that we provide at Alto at least. There is an equivalent for other sites for Elks University with 84 Science and Tampere and Oulu. But the idea is basically that you will find a blocker, you will always find a blocker at some point, and then you can come and ask for help. We provide multiple channels that would allow you for kind of a fast interaction. Often it's much faster to have a quick chat, sit down together, solve the issue, and then we learn from you something that we didn't know and you learn from us. So it's a two-way exchange. What I like to really stress is our daily garage. So it's basically every day at 1 p.m. We have a Zoom room where there's this administrator of the Triton cluster, but not just us. There's also people from our data management services, our VM services, and so many people from all Alto hang around and you can bring any sort of question whether it's with the Triton cluster or with scientific confidence in general. And then we're trying to promote also this chat, which is a Zulip chat. It's basically something like Slack you can think of, but where again everyone from multiple departments or school or wherever they come, they might have an issue. We're trying to promote user groups so that all the users of MATLAB can talk with each other and the Python users and console user and whatever is your tool. Then maybe when it comes to training, well, this course that you find here is part of in our website.com.alto.fi. We have other training courses and in general more broadly, I really like to promote a lot Code Refinery, which is an organization that spans across the Nordics. And the idea here is that it's not really learning how to code or learning some programming language. It's more learning what's around the coding activity. So in the end, you will write whatever code you know, you are the expert for that bit, but you need all these set of tools to, for example, make sure that your code is reproducible, that you can share it with others, that you can reuse it in the future and things like that. Then maybe Richard, maybe you want to say something about the research software because it's your creation. So a year ago, we had this idea that if we're doing stuff online, what else can we do? So I mean, it's not exactly a podcast, but I don't know what the proper term is, but basically, occasionally we go and we have some topic and then we will go in depth into that topic. So for example, there was one on resolving Git conflicts, or there can be something on data management or like other specialized tools. That's a nice one on the cluster etiquette, because the cluster is a shared resource, so you need some etiquette to respect each other. So I really like that. Yeah. So the basic idea is that it's like sitting down with your colleagues and seeing what tips and tricks they have so you can adopt them, and also what we can learn from other people. So right now we do it basically whenever we have an idea, but traditionally it has been Thursday evenings at 9.30 Helsinki time, but well, yeah. And it's also on Twitch. Yeah. And then some other good link, good, or actually it's like a collection of links to get started with scientific computing. It's this hand sound scientific computing. So here you find some sort of a path that would start from the beginning, from the Linux shell, from the blocks up to basically what we will cover tomorrow with so-called parallel jobs and using HPC, HPC resources. And with these you can even get one or two credits if you take it. Yeah. So this is a good way. Well, it's basically sort of the full kickstart for researchers, everything from Linux shell and Git up to the computing stuff. So we made it because we've seen that many times academic courses are, well, more theoretical than applied and we need a way to make sure everyone can start on an equal footing. So that's what we've been working on. Okay. And then here in general, when it comes to professional development, there is a figure that is emerging in academia or at least in the scientific research, which is the idea of research software engineer. It's not really a new label in a sense that some people might say that we all are research software engineer because we are putting together some code and hopefully make some science or meaningful numbers out of it. But the community is growing and universities like Alto are recognizing this as a career, as a profession. Right now, Alto at least is providing this service so that if you're supervised or if you are blocked with your research project and the block list is type of coding, software, pipelines and whatever, this is a service that we can provide. There's the links here. And I don't know if you want to say something more about research software engineer service. Yeah. So I guess you'll notice in the next few days, there's a lot you may need to learn in order to do this computing stuff on the cluster. I mean, it really is. And many people need to do computing, but to be honest, not everyone needs to know everything themselves. I mean, that's why we have division of labor and all that modern economic theory and so on. So if you're from, if you need to do a project and you really don't want to deal with the programming or computing side yourself, the service can do it. So we basically want everyone to be able to do computing, not just those that dedicate all their time to programming. It's available in the Alto School of Science right now. And if you're not in the School of Science, the status is sort of unknown. So we would need to arrange funding somehow. But anyway, contact us and we can work and see what we can do. A good way to contact us is to come to the Alto Daily Garage and we can talk there. Yep. Yeah. All right. I guess this is, I mean, I don't know if we inspire and motivate you in learning more about scientific computing, but, you know, we all need to start from somewhere. And maybe now we can actually, if we should start by testing, then we can connect to HTC clusters.