Skip to main content

Usage Guidelines

1. Network Security Standards​

To implement the requirements of the Cybersecurity Law of the People's Republic of China, the Personal Information Protection Law of the People's Republic of China, the Data Security Law of the People's Republic of China, the Regulations on the Security Protection of Critical Information Infrastructure, and cybersecurity classification protection requirements, and to further strengthen and optimize network security protection in the Supercomputing Technology Park and Software Park, the Shandong Supercomputing Center (National Supercomputing Center in Jinan) (hereinafter referred to as the "Center") has formulated a Network Security Responsibility Commitment Letter based on the principle of "who uses, who is responsible." This aims to enhance network security awareness, advance the rectification of security issues, and strengthen the security of business application operating environments.

The entities responsible for network security commitments regarding HPC resource usage are: resource applicants and resource trial/usage teams.

1) Data processing and storage on the platform must comply with relevant laws, regulations, and confidentiality requirements; users must not disseminate or store illegal or infringing information.​
2) Cluster login requires prior VPN login. Users must not transfer their accounts or usage rights, whether for compensation or not, nor use others' accounts to access computing resources. Otherwise, the account applicant is responsible for all issues arising from the account (e.g., network security issues and computing cost issues).​

2. Do not run case programs on the login node​

After logging into the cluster, the node used is the login node. The login node is only for editing and compilation work; please do not directly execute computing programs on the login node. Please use job submission scripts to schedule programs to run case programs on compute nodes. Refer to the job submission section.​
If programs are run directly on the login node, administrators have the right to kill the program processes. Frequent violations will result in account bans and login restrictions. Please comply with the regulations! Users with compilation needs should limit compilation processes to no more than 2 to avoid high load on the login node affecting everyone's experience. Thank you for your cooperation!​

3. VPN Password Lockout Issue​

If the account is locked due to multiple incorrect password entries during VPN usage, please wait patiently for 15 minutes. The account will automatically unlock after 15 minutes.​

4. Logging in using the MobaXterm tool​

When logging into the cluster using the MobaXterm tool, it is normal for characters not to be displayed when entering the password. Proceed with normal password entry.​

5. Linux Data Deletion​

Since Linux data deletion is an irreversible operation and data cannot be recovered, please exercise caution before performing deletion operations.​

6. Cluster Network Connectivity Issue​

To ensure customer data security, the cluster is not connected to the internet. Network download commands such as git and wget cannot be used. Software installation packages must be downloaded from a local computer with internet access and then uploaded to the cluster.​

7. Yum Usage Issue​

Cluster users do not have root privileges. If you need to install specific libraries using yum, please contact technical support to apply for the process, after which technical support will assist with installation, or you can perform source package installation yourself.​

8. Computing Resource Waste​

If jobs are not running on full cores, please contact technical support in advance to modify the scripts accordingly to avoid wasting resource nodes by submitting a large number of jobs.​
In cases of non-full-core computation with low memory requirements, add the parameter #SBATCH --mem-per-cpu= to the job submission script to improve node resource utilization and avoid resource waste.​
Example: #SBATCH --mem-per-cpu=10g indicates that this job only occupies 10GB of memory resources on the node. Other jobs can be submitted to the same node based on the remaining cores and memory.​

9. Graphical User Interface​

In the cluster environment, all operations are performed via the command line. The cluster does not have a graphical user interface.​

10. Software​

When using commercial software, such as VASP, MATLAB, ANSYS, and other copyrighted software, corresponding installation packages and licenses must be provided. Contact technical support for assistance with installation.​

11. Using Windows-version Cases​

When using Windows-version cases, check if the case content contains Chinese characters or Windows absolute paths like C:/Users/ to prevent case execution failure.​
For example: Submission failure caused by DOS/UNIX format issues.​
sbatch: error: Batch script contains Dos line breaks​
sbatch: error: instead ofexpected UNIX line breaks​
For handling this issue, please refer to the Common Login Questions.​

12. Slow Data Transfer with Tools like WinSCP​

The SSL VPN + SSH transfer process involves two layers of encryption. This is related to the priority settings of the internet service provider. VPN only ensures normal operation after logging in and cannot guarantee file transfer speeds.

China Mobile:https://112.6.51.12:443​
China Telecom:https://58.59.15.67:443​
China Unicom:https://124.128.14.54:443​
When logging in via VPN, use the corresponding ISP address (China Mobile, China Telecom, China Unicom) or switch network environments.​

13. Data Transfer​

For large volumes of computational data requiring upload or download, we recommend transferring data via physical hard drives to avoid interruptions caused by slow network speeds or instability.​
External hard drive transfer speeds depend on USB 2.0/3.0 interfaces, hard drive type, and the number of small files.​
For single large files, server transfer speeds are approximately 100–150 MB/s; for multiple small files, speeds are approximately 10–20 MB/s.​

14. Cancel Job​

To cancel a job, use the following command. Deleting the folder directly will not stop the job; it will continue running and consuming compute time.​
squeue
  
JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)
9446   intel01     bash    shizs  R 4-19:20:08      1 n03521
scancel 9446