gitea-pages/pages/merlin6/01-Quick-Start-Guide/code-of-conduct.md

title, keywords, last_updated, sidebar, permalink

title	keywords	last_updated	sidebar	permalink
Code Of Conduct	code of conduct, rules, principle, policy, policies, administrator, backup	07 September 2022	merlin6_sidebar	/merlin6/code-of-conduct.html

The Basic principle

The basic principle is courtesy and consideration for other users.

• Merlin6 is a system shared by many users, therefore you are kindly requested to apply common courtesy in using its resources. Please follow our guidelines which aim at providing and maintaining an efficient compute environment for all our users.
• Basic shell programming skills are an essential requirement in a Linux/UNIX HPC cluster environment; a proficiency in shell programming is greatly beneficial.

Interactive nodes

• The interactive nodes (also known as login nodes) are for development and quick testing:
  • It is strictly forbidden to run production jobs on the login nodes. All production jobs must be submitted to the batch system.
  • It is forbidden to run long processes occupying big parts of a login node's resources.
  • According to the previous rules, misbehaving running processes will have to be killed. in order to keep the system responsive for other users.

Batch system

• Make sure that no broken or run-away processes are left when your job is done. Keep the process space clean on all nodes.
• During the runtime of a job, it is mandatory to use the /scratch and /shared-scratch partitions for temporary data:
  • It is forbidden to use the /data/user, /data/project or /psi/home/ for that purpose.
  • Always remove files you do not need any more (e.g. core dumps, temporary files) as early as possible. Keep the disk space clean on all nodes.
  • Prefer /scratch over /shared-scratch and use the latter only when you require the temporary files to be visible from multiple nodes.
• Read the description in Merlin6 directory structure for learning about the correct usage of each partition type.

User and project data

• Users are responsible for backing up their own data. Is recommended to backup the data on third party independent systems (i.e. LTS, Archive, AFS, SwitchDrive, Windows Shares, etc.).
  • /psi/home, as this contains a small amount of data, is the only directory where we can provide daily snapshots for one week. This can be found in the following directory /psi/home/.snapshot/
• When a user leaves PSI, she or her supervisor/team are responsible to backup and move the data out from the cluster: every few months, the storage space will be recycled for those old users who do not have an existing and valid PSI account.

{{site.data.alerts.warning}}When a user leaves PSI and his account has been removed, her storage space in Merlin may be recycled. Hence, when a user leaves PSI, she, her supervisor or team must ensure that the data is backed up to an external storage {{site.data.alerts.end}}

System Administrator Rights

• The system administrator has the right to temporarily block the access to Merlin6 for an account violating the Code of Conduct in order to maintain the efficiency and stability of the system.
  • Repetitive violations by the same user will be escalated to the user's supervisor.
• The system administrator has the right to delete files in the scratch directories
  • after a job, if the job failed to clean up its files.
  • during the job in order to prevent a job from destabilizing a node or multiple nodes.
• The system administrator has the right to kill any misbehaving running processes.