For assistance with our systems, please email: email@example.com
Please note, that firstname.lastname@example.org is the only official way to request support from Research IT.
Other communications channels, e.g. directly emailing staff on their personal email address, phoning the office, calling into the office, Microsoft Teams, etc, are not official support mechanisms and may inadvertently not be responded to. To be sure you will receive support you must email email@example.com. You will receive a ticket number to confirm your support request when you do so. If that is not done we cannot guarantee we will respond to you.
If you have never used our systems before please read our Cluster Usage section. This section is designed to provide new users with enough information to get started using our services.
The “Search docs” box should be used to check our available documentation.
It is also good practice to search the internet for key phrases in your error messages too. That’s probably what the person answering your request is going to do.
Please email us.
When doing so please describe your issue as precisely as you can. It is very helpful for us if you can lay out step by step what you did so we can try to reproduce it. Doing so will speed up our response time.
When contacting us please try to include as much of the following information as you can so we can as speedily as possible help you.
What you did and how you did it. I.e. what exact steps you took:
E.g. I ran
Note: just including a copy and paste of the output from your terminal in your email would probably be enough.
What you had expected to happen but didn’t.
Please include Error Messages and other meaningful output.
When appropriate, include the information we would need to find your artifacts and understand your workflow:
If having a problem with something on a cluster, please specify which cluster. (At the time of writing we run 11 and a number of other systems, it helps to know where to start looking).
The directory containing your build and/or job script.
The modules you were using.
Relevant job numbers.
Any recent changes in your workflow that could affect or explain the behavior you’re observing.
Note on screenshots. A copy and paste of the textual output of an error is preferred over a screenshot where possible. Copy and pasting makes searching with the information easier and it is less prone to transcription problems. Inserting screenshots into emails can also sometimes disrupt the flow of reading an error report, if instead a copy and paste of the error text is used it may be easier to read.