Guidance for Completing the Project Application form on MySCW

  1. Project Title:
    A descriptive title that aims to cover the aims and objectives of the project and the work that will be undertaken as part of the project.
  2. Project Description:
    A meaningful description of the scientific goals and objectives of the project, and the methods and objectives to be pursued.
  3. Legacy HPC Wales ID (Project legacy ID from HPC Wales)
    Although now unlikely after two years of the operational service of Hawk and Sunbird, if you are migrating a project from the HPC Wales legacy HPC system, please enter the project’s ID code e.g. HPCW0337, SAM0012.
  4. Legacy ARCCA ID (Project legacy ID ARCCA):
    Although unlikely some 10 months after closure of ARCCA’s legacy “Raven” HPC system, if you are migrating a project from Raven, please enter the project’s ID code e.g. PR340.
  5. Owning institution project reference:
    If your project is externally funded (see below), please enter the reference number provided  by the sponsors, e.g.,  EPSRC (EP/S016376/1), BBSRC (BB/T006188/1)
  6. Department:
    Your School, Institute and/or Department. If the project is under the auspices of an Institute, please also specify your School.
  7. Principal Investigator’s name, position and email:
    By default, we request that Principal Investigators for Projects on the system be permanent staff members who are ultimately responsible for the research being undertaken. If you are a PhD student, Research Associate or Research Assistant, this would naturally be your supervisor or line manager.
    As the person requesting the project, you will be listed as Technical Lead, the person we will contact in first instance on all matters related with this project and who will receive project membership requests and can approve/deny them.
  8. Funding source:
    If the research study, of which this project is part, has received funding (internal or external), please let us know by selecting the appropriate category.
    Current options:
BBSRCEPSRCMRCNERC
AHRCSTFCLeverhulme 
EU / H2020Ser Cymru IIWEFOInternally Funded
Other (please specify)NoneN/AConfidential
  1. Start date:
    Project start date. If there is likely to be a delay in starting the project, please let us know here.
  2. End date:
    Project end date. Just ahead of this date you will be contacted to determine whether you wish to renew the project.
  3. Software Requirements:
    Enter details of any software you require to be installed on the system to be able to use it for your research. Examples include compilers (Intel and GNU C, C++, and Fortran compilers are available already), interpreters (Python and R are available already), open-source libraries, and commercial software (e.g. Stata, Matlab, Molpro). In addition, if you require a specific version of the software then please specify this.
  4. Gateway Requirements:
    If you have any special requirements on accessing or transferring data to Hawk from an external network, please let us know in this field.
  5. Training Requirements:
    Do you require training in order to make use of the system (e.g. Linux, Bash, General HPC, containers)? If so, write details of this here.
  6. On-boarding Requirements:
    Do you require any assistance in adapting your software to be able to make use of the system? Would a virtual session explaining the use of the Scheduler be helpful, If so, write details of these here.
  7. CPU time allocation in hours:
    How many “core-hours” do you anticipate this project needing? For example, if you have a program that only uses one CPU on your laptop, and runs for 48 hours, and you need to run it 1,000 times, then this number would be 48,000; if instead it used four cores on your laptop for the same amount of time, it would be 192,000.
    Thus one useful way to quantify the overall project requirements is to first define the requirements of a typical job, then have a stab at estimating the likely number of jobs to be run over the lifetime of the project. We realise this can be tough providing even a ballpark estimate given the dynamics of any research project, but it doesn’t have to be too quantitative, just a qualitative estimate will be fine.
  8. RAM allocation in GBytes:
    How much memory will your program need at once per node? If you don’t know this number, but know that the program runs on your computer, then enter the amount of RAM on your computer.
  9. Home storage in GBytes:
    Home storage is long-term (although not backed up) file storage used for data you need to keep on the system for months at a time. This is subject to a quota. Enter the amount of storage you need for the longer term; 50 GBytes is the default allocation on Hawk and 100 GBytes on Sunbird.
  10. Scratch storage in GBytes:
    Scratch storage is short-term, high-performance parallel file storage used for intermediary data you need temporarily but will either delete or move off the system once it is no longer needed. There is a 5 TBytes quota on Hawk and 20 TBytes on Sunbird, and when it full, then old unused files will be deleted.
  11. Upload Supporting Documents:
    Any other documentation relevant for the project application. This could include relevant publications from previous work, a case for greater allocations than the defaults (storage etc), detailed software requirements etc.