Embedded CSE (eCSE) support

The 12th eCSE call

The eCSE12 call opened on the 15th August, 2017 and closed at 4pm UK time on Tuesday 19th September, 2017.

Please note that the ARCHER CSE contract is presently due to finish on the 31st October 2018. This means that:

  • The maximum number of staff project months that may be requested is 9 months. The minimum is 3 months.
  • All final reports for funded projects must be received one month after the 31st October 2018 deadline (i.e. 30th November 2018).
  • To allow the standard 2 months for final reports to be completed after the end of an eCSE project, a project will need to be completed by 30th September 2018.
  • In exceptional circumstances (e.g. staffing issues), projects can run until the 31st October 2018 as long as final reports are completed by the 30th November 2018. If this is the case please explain this in your proposal.
  • eCSE projects are expected to start between 3-6 months after the call closing date giving a start date for eCSE12 projects of between mid-December 2017 and mid-March 2018.

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.

Scope

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 the current ARCHER service. We continue to welcome proposals targeting the current ARCHER service. In addition, we also encourage proposals that also consider running on any current or future UK Tier1 services. We also welcome proposals from current Tier-2 users who have an aspiration to move towards current or future Tier-1 systems.

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

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
  • Porting and optimising a code to run efficiently on ARCHER and on a (Tier-2) Regional service
  • 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

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 technical staff of the project only.

When submitting your proposal, all costs must be included in your submission. As this is the final eCSE call, the panel will award as many projects as possible, until the remaining 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.

Funding is awarded to institutions after an agreement has been signed. The process of setting up an agreement should not be onerous and most institutions have a legal/research management department which deals with such matters. In addition we have template agreements we use so agreements do not have to be created from scratch and are usually accepted by most institutions with only minor changes. If you would like to see an example of such a document then please get in touch and we will send you a template.

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 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.

Computing Resources

ARCHER computing resources will be made available at a level of 50 kAUs on the current ARCHER system per staff month awarded.

Training

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. 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.

Eligibility

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. A template is provided for the report. 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 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.

Contact

The ARCHER CSE team can be contacted via the ARCHER helpdesk.

Useful Links