Acknowledgements and Code of Conduct - nthu-ioa/cluster GitHub Wiki

Acknowledgements

Last updated: 15th Jan 2020

Please add the following to any papers for which any author has made use of the cluster, however minor. These acknowledgements help with future funding requests.

This work used high-performance computing facilities operated by the
Center for Informatics and Computation in Astronomy (CICA) at National
Tsing Hua University. This equipment was funded by the Ministry of
Education of Taiwan, the Ministry of Science and Technology of Taiwan,
and National Tsing Hua University.

Where authors have used the cluster and other CICA funding, they can add

XX is supported by CICA through a grant from the Ministry of Education of Taiwan.

Code of Conduct [DRAFT]

Last updated: 1st June 2020

By opening an account on the cluster, you agree to the following basic code of conduct. This applies to all users, regardless of their seniority or affiliation, including the administrators and collaborators. Violations of this code will lead to restriction of your account. The code of conduct for an NTHU computing account also applies.

Users must never:

  • Use the cluster for illegal or unethical purposes (including but not limited to unauthorized access, hacking or denial-of-service attacks, cryptocurrency mining, illegal downloads);
  • Use the cluster for resource-intensive personal activities, especially those involving the network (including but not limited to gaming, digital rendering, audio/video encoding, legal downloads unrelated to work, hosting websites).
  • Use the cluster for resource-intensive research projects not related to their work at IoA, unless given permission (for example, stock market analysis, or running physics computations for your friends in other universities without being a named collaborator on their papers -- consult a member of faculty if you are unsure about a specific case).
  • Use the cluster for any other purposes not compatible with the regulations of the University;
  • Exploit security vulnerabilities or knowingly install malicious software on the cluster;
  • Share their account password, SSH keys or other login credentials with anyone.

Users must contact an administrator as soon as possible if they know of:

  • a violation of this code of conduct or other misuse of the cluster resources;
  • a security flaw or other vulnerability on the cluster.

Users must:

Policies [DRAFT]

Job awareness

We expect that, if asked, users can explain to the system administrators what their jobs are doing, how they work, why they need the resources they have requested, and when they are expected to finish. Jobs will to be removed from the queue if requests for this information are not answered in full and in good time, especially if a job is blocking access to the queue.

Privacy

As a general principle, users can expect privacy on the cluster. However, this is a shared system. Be aware that, unless you set file and directory permissions to prevent it, other users may be able to read your files. Administrators can always do so, whatever permissions are set (but with the exception below, will not, as a matter of course). For this reason, users are strongly advised not to store sensitive or personal files on the cluster.

When a job is causing a problem or behaving suspiciously, the system administrators reserve the right to inspect running processes, source code, I/O files and directories, and submission scripts, without notice.

Academic work

With the agreement of their supervisor, IoA students are welcome to do their NTHU academic work on the cluster. The rules and standards are the same as for all other users. Research work (and system maintenance) will always have priority. Do not assume the cluster will be available to meet your deadlines.

Urgent jobs

Users are advised to discuss urgent, time-sensitive jobs with the administrators. The uptime of the cluster and the availability of the queues can never be guaranteed. Problematic jobs can be killed without notice.

Backup

:warning: There is no automatic backup system on the cluster, for either /home or /data. Users are responsible for making their own copies of important data. Students should ask their supervisors for advice on where to store backups of data critical to their thesis projects.