BwForCluster RV registration

From bwHPC Wiki
Jump to: navigation, search

This page is describing step 1 of the BwForCluster User Access, if you are registering a new RV. To join an existing RV as a coworker, please refer back to BwForCluster User Access

1 Who should register an "RV"

Typically done only by the leader of a scientific work group or the senior scientist of a research group/collaboration with personnel responsibility.

You will be:

  1. held accountable for the co-workers in the RV
  2. asked to provide information for the two reports required by the DFG for their funding of bwFor clusters
  3. likely asked for a contribution to the grant proposal for a new bwFor cluster of the same research area

2 Registration Procedure

Please login at:

and to fill in all mandatory fields of the given web form. Please note that for your convenience you can also switch to the german version of the web form. The submitter of the rechenvorhaben (RV) will be assigned the role RV responsible.

2.1 Registration Form Details

The web form consists of the following fields to be filled:

Field Explanation
RV Title Define a short title of your planned compute activities, maximum of 255 characters including spaces.
RV Description Write a short abstract about your planned compute activities (maximum of 2048 characters including spaces). Research groups that contributed to the DFG grant proposal (Art. 91b GG) of the corresponding bwForCluster only need to give reference to that particular proposal.
Scientific field Tick one or several scientific fields. Once all bwForClusters are up and running the full list of given scientific fields are supported and hence for rechenvorhaben (RV) applicable. If your RV does not match any given scientific field, please state your scientific field in the given text box. Grayed out scientific fields indicate that the corresponding bwForCluster(s) is/are not operational yet.
Field of activity Define if your RV is primarily for research and/or teaching. If not applicable, use text box.
Parallel paradigm State what parallel paradigm your code or application uses. Multiple ticks are allowed. Further information can be provided via text box. If you are not sure about it, please state the software you are using.
Programming language State the programming language(s) of your code or application.
Numerical methods State the numerical or "calculation" methods your code or application utilises. If you do not know, write "unknown".
Software packages State all software package you will or want to use for your RV. Also include compiler, MPI and numerical packages (e.g. MKL, FFTW).
Estimated requested computing resources Roughly estimate how many CPU hours are required to finish your RV. To calculate "CPU hours" multiply "elapsed parallel computing time" with "number of CPU core" per job.

Example: Your code uses 4 CPU cores and has a wall time of 1h. This makes 4 CPU hours.

Planned maximum number of parallel used CPU cores per job Give an upper limit of how many CPU cores per job are required. Please cross-check with your statement about parallel paradigm.

Obviously, a sequential code can only use 1 CPU core per job.

Estimated maximal memory requirements per CPU core Give an upper limit of how much RAM per CPU core your jobs require. Please give a value in GigaBytes.
Estimated requested persistent disk space for the RV State how much disk space in total you need for your RV. Please give a value in GigaBytes.

Example: If your RV has 4 more coworker and each of you produces until the end of your RV 20 GigaByte of output, your maximum disk space is 100 GigaByte.

Estimated maximal temporary disk space per job State how much space your intermediate files require during a job run. Please give a value in GigaBytes.

Example: Your final output of your job is 0.1 GigaByte, but during your job 10 temporary files, each with a size of 1 GigaByte, are written to disk, hence your correct answer is 10 GigaByte.

Institute State the full name of your Institute.

Note that the fields - name, firstname, organization, mail, und EPPN - are auto-filled and can not be changed. These are your credentials as given by your home organization.

3 Registration Response

Response

  1. After submitting you will get an email from ZAS confirming your submission. With this email you are given an unique
    * acronym
    * password
    Please keep the password enclosed. Only with both, acronym and password, coworkers can be added to your rechenvorhaben.
  2. The cluster assignment team will be notified immediately about your submission.
  3. The cluster assignment team decides based on your submitted data which bwForCluster most fits, and submits its decision to ZAS.
  4. ZAS notifies you in an email about your assigned bwForCluster and provides website details for step 3 .

4 Roles in an RV

The following roles are now available in your RV. You can assign a manager to do most tasks like adding/removing co-workers from the RV.

Role Explanation
RV responsible Registers the rechenvorhaben (RV), i.e. the planned compute activities. Can deactivate but also reactivate RV managers and coworkers. Can promote coworkers to mangers and vice versa.
RV manager RV coworker with elevated rights to deactivate and reactivate other RV coworkers.
RV coworker Typical user who has registered her/himself via RV acronym and password.

5 Registering co-workers

Hand out the acronym and password to your co-workers, they can then register. Anyone can register to your RV with the same with acronym/password. You can change the RV password at any time to prevent mis-use.

  1. You and any managers will be notified about their registration by email
  2. You can set any RV coworker to RV manager and vice versa as well as deactivate/reactivate any RV coworker or RV manager.
  3. An RV manager can deactivate/reactivate any RV coworker.


You and your manager(s) can check the list of RV members at https://www.bwhpc-c5.de/en/ZAS/info_rv.php by clicking on the RV acronym.

6 Duration of an RV

A RV is valid for 1 year. After that, the RV responsible must apply for an extension of the RV for it to be renewed for another year.