JUSTUS2/Policy Agreement: Difference between revisions
< JUSTUS2
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== JUSTUS 2 Policy - Agreement - V3 == |
== JUSTUS 2 Policy - Agreement - V3 == |
||
For all users of bwForCluster JUSTUS 2 for Computational Chemistry and Quantum Sciences the [https://www.uni-ulm.de/fileadmin/website_uni_ulm/kiz/wir_ueber_uns/kiz-bo.pdf |
For all users of bwForCluster JUSTUS 2 for Computational Chemistry and Quantum Sciences the [https://www.uni-ulm.de/fileadmin/website_uni_ulm/kiz/wir_ueber_uns/kiz-bo.pdf terms of use for services of the Communication- and Information Center (kiz) of Ulm University] apply. |
||
When registering for the service, you comply with above mentioned terms of use. Additionally you ... |
When registering for the service, you comply with above mentioned terms of use. Additionally you ... |
||
| Line 14: | Line 15: | ||
* agree to contribute to reports for the DFG |
* agree to contribute to reports for the DFG |
||
* acknowledge that your home directory and work spaces will be deleted after expiration of your account (thus you are responsible to backup your files before your account expires) |
* acknowledge that your home directory and work spaces will be deleted after expiration of your account (thus you are responsible to backup your files before your account expires) |
||
* will |
* will avoid swap file I/O operations or any other intense I/O to HOME - swap files of single-node jobs must use the node local disk space |
||
* |
* will not run long cpu/memory intense calculations on login/vis nodes - those nodes are for interactive use, compiling and short tests only |
||
* |
* will not store important results in workspaces, since they are not included in any backup |
||
* |
* will not mass-submit very short (minutes) jobs to the batch system |
||
* plan/submit calculations |
* will plan/submit calculations in such a way that those jobs fill entire nodes - since nodes are user-exclusive on JUSTUS 2 |
||
Also see |
Also see |
||
Latest revision as of 17:37, 16 February 2026
JUSTUS 2 Policy - Agreement - V3
For all users of bwForCluster JUSTUS 2 for Computational Chemistry and Quantum Sciences the terms of use for services of the Communication- and Information Center (kiz) of Ulm University apply.
When registering for the service, you comply with above mentioned terms of use. Additionally you ...
- agree to use the cluster only for research in accordance with DFG funding conditions
- agree to acknowledge the bwForCluster JUSTUS 2 in your publications
- agree to send us references to all publications with contributions by JUSTUS 2
- comply with the terms of use of the software manufacturers
- agree to report any problem that might endanger the cluster operations
- agree to use the resources carefully (without wasting cores, memory or disk space)
- accept that the system is monitored to prevent misuse
- accept that job and software usage statistics are collected for improving the service and reporting to the DFG
- assure that your compute activities comply with the German Foreign Trade Act (Außenwirtschaftsgesetz - AWG) und German Foreign Trade Regulations (Außenwirtschaftsverordnung - AWV), see https://www.bafa.de/DE/Aussenwirtschaft/Ausfuhrkontrolle/Academia/academia_node.html
- agree to contribute to reports for the DFG
- acknowledge that your home directory and work spaces will be deleted after expiration of your account (thus you are responsible to backup your files before your account expires)
- will avoid swap file I/O operations or any other intense I/O to HOME - swap files of single-node jobs must use the node local disk space
- will not run long cpu/memory intense calculations on login/vis nodes - those nodes are for interactive use, compiling and short tests only
- will not store important results in workspaces, since they are not included in any backup
- will not mass-submit very short (minutes) jobs to the batch system
- will plan/submit calculations in such a way that those jobs fill entire nodes - since nodes are user-exclusive on JUSTUS 2
Also see