Embedded CSE (eCSE) support

The 13th eCSE call

The eCSE13 call opened on the 5th June 2018 and closes at 4pm UK time on the 17th July 2018.

Please note that the ARCHER CSE contract is presently due to finish on the 17th November 2019. This means that:

  • The maximum number of staff project months that may be requested per project is 12 months, this is inclusive all the technical staff.
  • All projects must be completed by the 17th November 2019, the current date for the end of the ARCHER service.
  • All successful projects will be expected to produce a final report. These must be received within 6 weeks after the project end date and no later than 31st December 2019. Please note that the ARCHER service is currently due to be decommissioned on the 17th November 2019 and projects may not have access to the service after this date.
  • Successful projects may start on or after the 1st October 2018, subject to contract and/or agreement.

Please note that the guidance for this call has been updated to reflect the anticipated closure of the ARCHER service and is different in a number of places from previous calls. Please ensure you read the guidance carefully - both on this web page and in the Application Guidance.


Through a series of regular calls, Embedded CSE (eCSE) support provides funding to the ARCHER user community to develop software in a sustainable manner, to run on current (ARCHER) and future UK Tier-1 systems. As the current ARCHER service is nearing the end of its lifetime, proposals should focus on preparing codes for future Tier-1 systems, including improving maintainability and sustainability. Applicants should not propose developments that only target the current ARCHER service.

For the purpose of this call, the term ARCHER includes the existing ARCHER systems - the Cray XC30 and XC40 Xeon Phi systems - and the term ARCHER 2 includes any potential UK National HPC replacement to the ARCHER service.

While the focus of the call is on maintainability and sustainability, all proposals should utilise the current ARCHER service to deliver the work and to demonstrate that the Objectives of the proposal have been met. Proposals may, in addition to ARCHER, utilise other systems and resources if it helps demonstrate maintainability and sustainability.

Funding will enable the employment of a Research Software Engineer (RSE) to work specifically on the relevant software to enable new features or improve the performance of the code, with an emphasis on preparing the code for new Tier-1 services. Examples of this could be

  • Implementation of algorithmic improvements within an existing code in a portable manner
  • Improving the scalability of software on higher core counts in a portable manner
  • Improving a code to enhance sustainability and maintainability
  • Improvements to code that allow new science to be carried out on ARCHER and on future Tier-1 services
  • Porting and optimising a code to run efficiently on future Tier-1 resources
  • 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 and ARCHER 2


Funding can be requested for existing ARCHER users or from those planning to become ARCHER users and whose research is within the remit of EPSRC or NERC. 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 project are expected to play a full part in ARCHER related activities.

Reasonable travel will be funded for travel within the UK to meetings with other project partners. Travel costs will be funded for the named RSE of the project only.

When submitting your proposal, all costs must be included in your submission. As this is a standalone eCSE call, the panel will award as many projects as possible, until the full budget is spent. It will not be possible to modify your costs after the panel meeting. Hence please ensure your budget is accurate and inclusive of all costs before submission. Please see the guidance document for details of allowable costs.

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 ARCHER. These communities are likely to have a scientific need for ARCHER / ARCHER 2 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 and ARCHER 2 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 project.

Computing Resources

ARCHER computing resources will be made available at a level of 100 kAUs on the current ARCHER system 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 on how to apply for eCSE funding can be found here. Proposals undergo a two-stage process. After submission, 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.

The eCSE applications should be submitted via SAFE. The eCSE proposal template can be found here.


ARCHER embedded CSE support is only available for projects within EPSRC or NERC remit (the Research Councils funding ARCHER).

Reports and eCSE staff requirements

A detailed technical report is required at the end of the project. A template is provided for the report here. Upon conclusion of the project, in addition to the detailed technical section, a section 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 and/or project technical staff 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.

Intellectual Property

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.

Acknowledging ARCHER

You should use the following phrase to acknowledge ARCHER in all research outputs that have used the facility and the eCSE Programme:

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.

Useful Links