There are two steps to gaining access to BlueBEAR; being associated with a registered project and registering a username on the service. These steps are distinct since it is common for a project owner, who has to be a member of staff, not to have an account on BlueBEAR, but for the students or postdocs working on the project to do so.
Registering a Project
Registering a project is described on the help page for project & user registration.
External funding is not a requirement for access to this service; unfunded research projects are also welcome. It is essential for IT Services to gather information about the range of research that benefits from the service and hence make the case to the University for sustained funding in this service, and hence all research projects, funded or unfunded, need to be registered on the service. Projects can only be registered by a member of staff, who may associate other staff members or research students with their project in the People to be associated with this project input box. Projects must not be requested on behalf of another member of the University, be they staff or students; the person submitting the request must be a member of staff and will be the project owner.
Registering a BlueBEAR project does not imply any storage being allocated on the Reseach Data Store or the Research Data Archive for the project, but these can be requested at the same time.
Specifying usernames on a project does not lead to these users being registered on the service; all users, including the project owner, need to register a username if access to BlueBEAR is required once the project code has been received by the requestor. This is described in the following section.
Registering a username for the general BlueBEAR service
Registering for the general BlueBEAR service is described on the help page for project & user registration.
Registration requests are forwarded to IT Services who then approve the request or send a mail asking for further details, especially if a BlueBEAR project code has not been given. Once approved the requests are processed and notification is sent to the requestor's central email address when access to the service is available, usually within 3 days. To enquire about an outstanding user registration please open a Service Desk call.
Please contact the IT Service Desk if you have any questions about, or problems with, your project or user registration.
Registering a username for specialist BEAR services
There are additional specialist services that are available on BlueBEAR. To access these requires a registration for the general BlueBEAR service and then an additional request for the specialist service. At present these specialist services comprise:
These are offered on the "BEAR User Account Options" in IT Service Desk. Such requests should give details of previous work on BlueBEAR which leads to the request for these additional resources; an example would be attempts to run simulations which run out of memory on the standard nodes. Details such as the application(s) that are being used, whether the current work is single-core or using multiple cores (a copy of the job submission script could be included in the request), and the expected amount of resource, for example memory, that will be required should be included in the request. This information should be entered alongside the existing project code(s) in the section "Please give some details as to why this service is needed".
Requests without such information will likely be rejected; requests with such information will be followed up by IT Services, with a discussion between the requestor and a specialist from IT Services. Registration on the general BlueBEAR service, and experience of using the standard resources on the service, are required prior to submitting a request for these specialist services. Requests to register for one of the specialist services without a prior registration for the standard service will be rejected with an explanatory email.
There are User Guidelines describing the service that we offer and also the responsibilities of users of the system. All current and prospective users are urged to read these.
Last modified: 29 May 2018