|
1 | 1 | For units such as departments, schools, or flagship projects |
2 | 2 | ============================================================ |
3 | 3 |
|
4 | | -Our service is funded by departments and schools, and members of these |
5 | | -units can receive our services free of charge for a short period of |
6 | | -time (in accordance to the shares of funding). In addition to the |
7 | | -basic service, researchers and group leaders can request long-term |
8 | | -support which they pay for themselves. |
9 | | - |
10 | | -**By joining the Research Software Engineering service, you provide |
11 | | -the highest-quality computational tools to your researchers, enabling |
12 | | -the best possible research and attracting the best possible |
13 | | -candidates. You fund a certain amount of time, and actual cost |
14 | | -decreases when groups pay for long-term service themselves. For both |
15 | | -short and long-term projects, our surveys indicate a significant |
16 | | -efficiency: (researcher time saved) ≥ 5 × (time we spend).** |
17 | | - |
18 | | -.. admonition:: Case study: Systematic improvements |
19 | | - |
20 | | - Your department has a lot of people doing little bits of |
21 | | - programming everywhere, but everyone is doing things alone. What |
22 | | - if they could work together better? By joining the RSE program as |
23 | | - a unit, your staff can get rapid help to understand |
24 | | - tools to make their programming/data work better. After a few |
25 | | - years, you notice a dramatic cultural shift: there is more |
26 | | - collaboration and higher-quality work. Perhaps you already see a |
27 | | - change in your KPIs. |
28 | | - |
29 | | - |
30 | | - |
31 | | -Benefits |
32 | | --------- |
33 | | - |
34 | | -Benefits to schools/departments: |
35 | | - |
36 | | -* Increase the quality and efficiency of your research by providing |
37 | | - the best possible tools and support. |
38 | | -* Provide hands-on technical research services to your community at a |
39 | | - higher level than basic IT (see :doc:`/help/garage`). |
40 | | -* More societal impact, for example ChatGPT-type preview interfaces. |
41 | | -* Help with data management, open science, FAIR data - be more |
42 | | - competitive for funding and help get value out of your unit's data. |
43 | | -* You will be able to set priorities for your funding, for example do |
44 | | - you focus on a certain strategy, wide variety of projects, |
45 | | - high-impact project, etc. |
46 | | - |
47 | | -Benefits to groups: |
48 | | - |
49 | | -* Receive staff/on-call software development expertise within your |
50 | | - group, without having to make a separate hire, and at less than a |
51 | | - full time equivalent. We don't disappear right after your project. |
52 | | -* Instead of just one person, you have the resources of our whole team |
53 | | - available to you. |
54 | | -* Your researchers focus on their science while improving their |
55 | | - computational skills by co-working with us. |
56 | | - |
57 | | - |
58 | | - |
59 | | -How to join |
60 | | ------------ |
61 | | - |
62 | | -The RSE program is a part of Aalto Science-IT (Aalto Scientific |
63 | | -Computing), so is integrated to our computing and data management |
64 | | -infrastructure and training programs. You don't just get a service, |
65 | | -but a whole community of experts. We can seamlessly work with |
66 | | -existing technical services within your department for even more |
67 | | -knowledge transfer - if it matches their mission, your existing |
68 | | -technical services can even join us directly. |
69 | | - |
70 | | -In practice, joining us means that you contribute a certain amount of |
71 | | -funding, which allows us to hire more staff (combined with the other |
72 | | -departments), to provide a certain amount of time to research groups |
73 | | -in your unit. This is easy with basic funding, but we can also use |
74 | | -Halli to work with project funding. |
75 | | - |
76 | | -If you would like to join contact Richard Darst or rse-group at |
77 | | -aalto.fi. |
78 | | - |
79 | | - |
80 | | -Current sponsoring units |
81 | | ------------------------- |
| 4 | +Computing is everywhere: in almost every unit of every field of |
| 5 | +research. But computing is often hard, and not everyone can do what |
| 6 | +they need to alone. Advanced computing needs to be a team effort, and |
| 7 | +we can help with that. |
| 8 | + |
| 9 | +Aalto Research Software Engineers (RSE) is part of Science-IT, the |
| 10 | +Aalto University infrastructure for scientific and high-performance |
| 11 | +computing. Science-IT is a virtual organization in Aalto, and your |
| 12 | +unit can join by hiring staff to serve with us. |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +Proposal in brief |
| 17 | +----------------- |
| 18 | + |
| 19 | +Aalto Science-IT is a research infrastructure, and part of it is Aalto |
| 20 | +Research Software Engineers. Our job is to make computing possible |
| 21 | +for everyone. We have some ability to serve all Aalto, but this is |
| 22 | +limited. |
| 23 | + |
| 24 | +Your unit can reach the next level of computing and AI based research |
| 25 | +by supporting its staff with Research Software Engineers. This will |
| 26 | +allow your research community to do better science, faster, and more |
| 27 | +reproducible. You'll waste less time on solved problems. |
| 28 | + |
| 29 | +You can fully join the RSE team by hiring (or finding |
| 30 | +internally) some staff interested in research software and scientific |
| 31 | +computing. They'll join our team, taking full advantage of our |
| 32 | +knowledge and resources, while focusing on your own unit's problems. |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +What do research software engineers do? |
| 37 | +--------------------------------------- |
| 38 | + |
| 39 | +See also: `ASC blog post: What is a Research Software Engineer? <https://aaltoscicomp.github.io/blog/2024/what-is-a-rse/>`__ |
| 40 | + |
| 41 | +What do you need to do with computing, but your staff currently |
| 42 | +struggle with? It depends on your unit's needs, but in general |
| 43 | +activities include: |
| 44 | + |
| 45 | +- Consulting with project's small problems (solve problems faster and |
| 46 | + save time) |
| 47 | +- Writing and supporting software, when the software isn't the main |
| 48 | + goal of the research |
| 49 | +- Keeping data organized |
| 50 | +- Port code and manage workflows on supercomputers |
| 51 | +- Finalizing projects and making nice interfaces for the public to |
| 52 | + view. |
| 53 | +- Manage automation and workflows: reach a larger scale. |
| 54 | +- Assist in planning for research ethics evaluations and data |
| 55 | + management. |
| 56 | +- See our :doc:`portfolio <portfolio>` for more examples of real |
| 57 | + projects. |
| 58 | + |
| 59 | +**Previous measurements have shown that RSEs are a good investment: an |
| 60 | +hour of our time usually saves 5 hours of researcher's time or more**. |
| 61 | +We also make new projects possible, which couldn't be done otherwise. |
| 62 | +Aalto RSE's biggest impact is speeding up and improving lots of small |
| 63 | +projects, but we usually have some longer projects going on, too. |
| 64 | + |
| 65 | +.. figure:: https://github.com/AaltoSciComp/aaltoscicomp-graphics/blob/master/figures/rse-alignment.png |
| 66 | + |
| 67 | + One way of looking at the types of projects a RSE can do. Note we |
| 68 | + do anything from providing advice to speed up other projects to |
| 69 | + doing projects ourselves, where an academic can't. |
| 70 | + |
| 71 | + |
| 72 | + |
| 73 | +How it can work |
| 74 | +--------------- |
| 75 | + |
| 76 | +**Aalto Science-IT (and thus Aalto RSE) is a university-level research |
| 77 | +infrastructure. It operates as a virtual team: in principle, it's |
| 78 | +easy for your staff to join.** Here's how we would go about it: |
| 79 | + |
| 80 | +First, think of where such a person can be situated. Are they hired |
| 81 | +at the school level? Department? Service staff or academic staff? |
| 82 | +Job title? All of these can be adapted to what makes the most sense |
| 83 | +for your school. |
| 84 | + |
| 85 | +.. admonition:: School of Science practices |
| 86 | + :classes: dropdown |
| 87 | + |
| 88 | + At the School of Science our arrangement is: |
| 89 | + |
| 90 | + - Have hired at the school level as Technical Services |
| 91 | + - Full time and permanent |
| 92 | + - Job title "Research Engineer", business title "Research Software |
| 93 | + Engineer". |
| 94 | + - Service staff with regular working hours. |
| 95 | + - Funded from school and department budgets. Research projects |
| 96 | + also directly contribute funding via Halli for their share of the |
| 97 | + work. |
| 98 | + |
| 99 | +As for the actual hiring, you might already have someone internal who |
| 100 | +is interested in a focus shift. For new hires Aalto Research Software |
| 101 | +Engineers can help with recruitment. We can suggest good candidates |
| 102 | +from our recruitment calls - we get many good candidates from various |
| 103 | +schools. |
| 104 | + |
| 105 | +Your new hire would begin in your school, but initially spend time |
| 106 | +working with Aalto RSE. They can join our support and training |
| 107 | +sessions and learn the tools of our trade, while focusing on your own |
| 108 | +unit's problems. This is the way we onboard people to computational |
| 109 | +support. See the `RSE work rotations |
| 110 | +<https://aaltoscicomp.github.io/blog/2024/rse-work-rotations/>`__ blog |
| 111 | +post for more info. |
| 112 | + |
| 113 | +After some time, your staff may split off into its own team, or they |
| 114 | +might continue operating as part of the Aalto-wide team. We'll discuss |
| 115 | +and see what is best for you. Some continued collaboration is best, |
| 116 | +because a large team has the most knowledge to draw on. |
| 117 | + |
| 118 | + |
| 119 | + |
| 120 | + |
| 121 | +How to get in touch |
| 122 | +------------------- |
| 123 | + |
| 124 | +If the above sounds like something that would benefit your unit, Aalto |
| 125 | +RSE is ready to help you (2024). Gen in touch with Richard Darst or |
| 126 | + |
| 127 | + |
| 128 | + |
| 129 | + |
| 130 | +Current member units |
| 131 | +-------------------- |
82 | 132 |
|
83 | 133 | See :doc:`procedures/units-info` |
0 commit comments