Computational Resource Allocation Group (CRAG)
Request for Additional Resources

This form is for Research Computing users who wish to request access to additional resources, or reserve resources, beyond those provided under prevailing CRAG policy.
The completed form should be sent to the Research Computing Platforms Service (rc-support@ucl.ac.uk) for consideration at the next meeting of the CRAG. The CRAG typically meet on a monthly basis. Information about the CRAG and the date of the next meeting can be found here:
http://www.ucl.ac.uk/isd/about/governance/research-it/crag
Users will be informed of the group's decision as soon as possible after their next meeting.
Some example request types and the information needed is provided at: 
https://www.rc.ucl.ac.uk/docs/Additional_Resource_Requests/#examples-of-requests
Section 1 should be completed by all applicants. Students or postdoctoral researchers should additionally ask their supervisor or PI to complete section 2. If you are the PI, you can note this in section 2. Please expand the form cells in the table below, as required.
SECTION 1		
This section should be completed by the User for whom additional resources are requested
	
Name		
UCL userid		
Email		
Department		
Service name (eg Myriad)		
Time period of request (max 12 months – reapplications can be made)	From: 
	To: 
	
Nature of request – please provide full details of the extra resources requested (e.g. number of cores/ nodes, number of jobs, Scratch size etc.)
For increased walltime/priority requests, include what resources a typical job will request and roughly how many of these you expect to need to run, over what time period. This is to gauge the impact of your request on other users.		
Please explain clearly why the proposed work cannot be completed under the prevailing resources allocation policy		
Data management plan: if this is a quota increase request, please explain what you plan to do with the data when the increase expires.	Required for quota increase only

Checkpointing: if this is a longer walltime request, explain why checkpointing is not sufficient. 	Required for walltime increase only. Checkpointing is where a job writes out all the information it needs to continue so the next job can begin at that point and do the next chunk of work.

		
SECTION 2		
This section should be completed by the applicant’s supervisor or the project’s principal investigator
	
Name		
UCL userid		
Email		
Department		
Please explain clearly why you support this request