Support and User Policies
Not sure where to go for help?
Send an email message to mscf-consulting@emsl.pnl.gov.
Forgot Your Password?
- If you have forgotten your password, send an email message to support@emsl.pnl.gov.
Trouble Getting an Account?
- If you have difficulties or questions about obtaining your account, your first action should be to contact your host or his/her secretary. (If you are a PNNL employee, ask your secretary). If you still have questions, see "Get Help" or support@emsl.pnl.gov.
Need an Allocation Refund?
- If your job failed on the MSCF computer, it may be possible for you to receive a refund of the allocation time lost. Please see the guidelines for allocation refunds.
Support at MSCF
- For assistance in getting refunds or for general guidance in running jobs, send a message to mscf-consulting@emsl.pnl.gov
- Questions about the configuration and status of the computers can be addressed by the high-performance computing support staff. For further details, see "Get Help" or mscf-support@emsl.pnl.gov.
Policies for Using Computer Resources
- Any use of the computing resources of the MSCF must be properly acknowledged.
- The /home directory is a shared resource without enforced quotas. When excessive amounts of disk space is used, those who are using the most space will be asked to reduce their use to some value. Repeated excessive use of disk space can lead to loss of system privileges. This directory is not a permanent storage system. Files to be saved should be stored on your local machine or on the NWfs file storage system.
- Jobs running from the /home file system causing system degradation either because too many files are being accessed or there is a likelihood of exceeding disk capacity, will be terminated by the system administrator and the user will be sent an e-mail message. Such jobs should be run from /dtemp or the local /scratch files.
- The /dtemp file system should not be used to store important data. It is a temporary file system and is not backed up. Files may be removed after 60 days to maintain optimal performance.
- When a production run is found running on a login node instead of in the batch queue, the job will be terminated by the system administrator and the user will be sent an e-mail message. Such jobs cause unnecessary degradation of login node performance.
- Jobs in the batch queue that have been suspended for more than 12 hours will be deleted.
- The longest time a single job can run is 48 hours. For further details, see http://mscf.emsl.pnl.gov/hardware/summary_mpp2.shtml#policies
