Embedded CSE (eCSE) support
The 11th eCSE call
The 11th eCSE call opened on 28th March, 2017 and closes at 4pm on Tuesday 9th May, 2017.
A provisional timetable of future eCSE calls can be found here.
Through a series of regular calls, Embedded CSE (eCSE) support provides funding to the ARCHER user community to develop software in a sustainable manner for running on ARCHER where ARCHER includes both the Cray XC30 and XC40 Xeon Phi systems. Funding will enable the employment of a researcher or code developer to work specifically on the relevant software to enable new features or improve the performance of the code. Examples of this could be
- Implementation of algorithmic improvements within an existing code
- Improving the scalability of software on higher core counts
- Improvements to code which allows new science to be carried out
- Porting and optimising a code to run efficiently on ARCHER
- Adding new functionalities to existing codes
- Code development to take a code from a Tier-2 (Regional) or local university cluster to Tier-1 (National) level bringing New Communities onto ARCHER
Funding can be requested for existing ARCHER users or from those planning to become ARCHER users and who's research is within the remit of EPSRC or NERC. This can fund staff located at the institution of the PI, third parties, or can include staff from the centralised ARCHER support team or a mixture of the above.
Please note that the eCSE Calls are distinct from the EPSRC's Computational Science and Engineering: Software Flagship Project Call. We refer you to the EPSRC's website for further details: https://www.epsrc.ac.uk/funding/calls/compsciengsoftwareflagship/.
New Scientific Communities
Funding is available for established ARCHER communities and proposals from these communities are encouraged. However, proposals from new scientific communities are also encouraged.
New scientific communities are communities from scientific areas not currently exploiting the ARCHER system. These communities are likely to have a scientific need for ARCHER and a need for greater computational power than available at a regional level. Examples include:
- A science community not currently exploiting the ARCHER service, that wishes to develop a code to be able to exploit ARCHER to do new science;
- A science community currently exploiting a regional service, but not ARCHER, and that requires greater computational power.
- A science community that wishes to exploit existing algorithms or code on ARCHER to carry out significantly different science from that currently being carried out on ARCHER;
- A science community wishing to add additional functionality to an existing ARCHER code, to carry out significantly different science from that currently being carried out on ARCHER.
This does not include a science community wishing to extend an existing ARCHER code for only moderate diversification of the scientific area.
The review process recognises that applicants from new communities may not have had access to ARCHER previously and may not have existing performance data from the ARCHER service. In addition, the application process recognises that establishing a user community on ARCHER may be a longer-term, multi-staged process that may go beyond the end of an eCSE.
Funding can be requested for staff located at the institution of the PI, third parties, or can include staff from the centralised CSE support team or a mixture of the above. Staff employed on an eCSE are expected to play a full part in ARCHER related activities such as the technical forum. We would expect projects to last from around 3 months to up to a maximum of 1 year. Projects will not be awarded more than 12 months of staff effort.
Reasonable travel will be funded for travel within the UK to meetings with other partners. Travel cost will be funded for the technical staff only.
Funding is awarded to institutions after a contract has been agreed. The process of setting up a contract should not be onerous and most institutions have a legal/research management department which deals with such matters. In addition we have template contracts we use so contracts do not have to be created from scratch and are usually accepted by most institutions with only minor changes. This also ensures parity across all eCSE projects. If you would like to see an example of such a document then please get in touch and we will send you a template - we may already have one tailored for your institution anyway.
ARCHER computing resources will be made available at a level of 50 kAUs per staff month awarded.
Regular training will be provided via the CSE team. Details of upcoming training course can be found here.
Application and Review Process
Information and guidelines fon how to apply for eCSE funding can be found here. Proposals undergo a two-stage process. A technical review is performed first. During this stage the forms will be checked to ensure there is no obligatory information missing and applicants will be given the opportunity to provide such information. All proposal forms and completed technical evaluation forms will then be passed to the review panel who will make decisions on ranking and any award of funding.
ARCHER embedded CSE support is only available for projects within EPSRC or NERC remit (the Research Councils funding ARCHER).
Reports and eCSE staff requirements
Regular reports are a requirement of the award and failure to submit them may lead to funding being withdrawn. A detailed technical report is required at the end of the project as well as quarterly reports as the project progresses (for projects longer than 3 months). Templates will be provided for these reports. Upon conclusion of the project, in addition to the detailed technical report, a report aimed at the non-specialist is required explaining the aims and successes of the project together with the scientific and any other impacts of the work. PIs are expected to give a least one webinar of the work achieved and expected to be fully active in the ARCHER technical forum and relevant mailing lists.
Calls for proposals will be published at regular points during the lifetime of ARCHER. A provisional timetable of future eCSE calls can be found here.
IPR will belong to the project, although the expectation is that any EPSRC-funded code development will be made available to the wider community via a new release of the software.
You should use the following phrase to acknowledge ARCHER in all research outputs that have used the facility and the eCSE Program:
This work was funded under the embedded CSE programme of the ARCHER UK National Supercomputing Service (http://www.archer.ac.uk).
you should also tag outputs with the keyword ARCHER whenever possible.
The ARCHER CSE team can be contacted via the ARCHER helpdesk.