Living-with-machines
apply for GPU RSE support
Funding opportunity:
GPU eCSE support provides funding to the UKRI research community to develop software in a sustainable manner to run on GPU-based architectures. We invite proposals to develop software that facilitates research targeted at UKRI’s digital research infrastructure e.g. future Exascale supercomputing services, UK national AI services, national Tier-2 HPC services. The call is open to research across all of UKRI’s remit.
The 2nd GPU eCSE call (GPU-eCSE02) opened on the 2 July 2024. The final deadline for proposal submission is 16:00 on 17 September 2024 via the ARCHER2 SAFE. Please note that for this call there is no separate technical evaluation stage or separate technical evaluation form. Funding will enable the employment of an RSE (a Research Software Engineer, PDRA or equivalent) to work specifically on the relevant software to enable new features or improve the performance of the software to be run on GPU-based architectures. Funding can be requested for up to 24 person months of effort per project for a duration of up to 2 calendar years. There is flexibility in the way the effort is requested. For example, a project may have more than one person working on it or the effort could be spread over a greater number of calendar months, i.e. a staff member could work on the project at less than 100% alongside other commitments or it could be worked on by a staff member who doesn’t work full time. Please just get in contact with the ARCHER2 Service Desk ([email protected]) if you wish to discuss possible scenarios. Projects are expected to start between 1 January and 1 July 2025, and be completed by 31 March 2027. Funding can be requested for staff located at the institution of the PI, third parties, or can include staff from the ARCHER2 centralised CSE support team at EPCC or a mixture of the above.
Projects may utilise the GPU component of ARCHER2 or other suitable GPU resources to complete the technical work. If the proposal plans to use the GPU component of ARCHER2, successful projects will be given access to these resources. If projects plan to utilise other systems, you should ensure you have suitable resources available to complete the project successfully. Please contact and arrange this access with the relevant service provider before submission.
More details of how to apply are available by following the link to the eCSE calls page from here: https://www.archer2.ac.uk/ecse/calls/
Deadline for final GPU-eCSE02 submission: 16:00 on 17 Sep 2024 (via the ARCHER2 SAFE: https://safe.epcc.ed.ac.uk/)
This deadline is quickly approaching. We need to prioritise this if we are going to submit a proposal.
I have read the guidance for this more closely now. The funding is for an RSE to work on GPU-oriented development, but this RSE should ideally be a named person in the proposal - it is their salary and travel being funded. IF this proposal were to be about development for MapReader & T-Res, is there someone we would have in mind for this? I am assuming it doesn't make sense to name, for ex, @rwood-97, as that is unnecessary? But maybe that is an interesting opportunity for you Rosie, e.g. we can name you as a Co-I on this. @kallewesterling could be same for you too. Happy to brainstorm this with you, but we should request costings from either Turing or Lancaster before the end of the week if we want to go ahead.
FYI:
Allowed roles are: • PI (leader of the project) • Co-I (other members of the team who will help to lead or advise on the project) • Technical Staff (the person or people who will be funded to work on the project) • Contact (someone working on behalf of the PI who should receive any correspondence – note PIs, Co-Is and technical staff will all receive correspondence automatically so there is no need to give them the Contact role) • Member (no specific role in the project but can see and edit the proposal) It is possible to select more than one role for a person and roles can be changed at any time up to the final submission. The eCSE programme funds staff costs for the technical members of staff. Details of how to cost this are provided later in this document. The programme does not fund PI and Co-I staffing time.
- I have emailed Pieter about handling naming Turing peopl
- I have not heard back from ARCHER team about naming one of them centrally
- I will let the Bristol person know we are applying, maybe they would be interested?
- I have shared the proposal draft google doc on slack
- If we go ahead, and people are named as members or Co-Is I will need a CV from anyone fulfilling a technical role. And I will need a 250 word statement about your contribution from everyone. Details in the doc.