1. Getting ConnectedAnchor id2 id2
2. The User $HOME DirectoryAnchor id3 id3
3. GroupsAnchor id4 id4
4. QueuesAnchor id5 id5
5. Starting Your First JobAnchor id6 id6
6. Here Are a Few Next StepsAnchor id7 id7
Info | ||||
---|---|---|---|---|
| ||||
|
1. Getting Connected
If you are off campus, you will need to use a VPN to access compute1.
Instructions for accessing the WashU VPNs can be found here: https://it.wustl.edu/items/connect/
If you run into issues using the VPN, you will need to follow the directions in the previous link to contact WashU IT proper.
...
We assume the vast majority of our users are using Linux or Mac working environments and will be able to utilize the terminal within those environments. However, there is SSh software for Windows to be able to connect as well.
2. The User $HOME Directory
Users are represented by Wash U WUSTL Key IDs. Upon first login to a compute1-client host, the system will create a new home directory for you. From the command line, you can run the following command to confirm your home directory.
...
Info |
---|
RIS has observed that some users’ home directory is not /home/wustlkey but rather has a pattern like /home/IDC-ID-12345. We are working to correct this. |
3. Groups
Before launching a job, you must ensure you are a member of a compute- group.
RIS mediates access to services by groups and you will be unable to submit a job if you are not part of one.
Usually a user will be part of only 1 group.
You can find out what groups you’re in by running the group command.
Code Block | ||||
---|---|---|---|---|
| ||||
groups |
...
4. Queues
The compute cluster offers a number of queues. This is how the scheduler organizes jobs.
You can use the bqueues command to see a list of queues available.
...
-
- We have learned over time that the proliferation of queues to support special projects and features becomes unwieldy, so we strive to keep the minimum number of queues possible.
general : This is the default queue where non-interactive jobs land. Most of your high performance work should land here.
general-interactive : This is the queue where the interactive feature is supported. There is a job run time limit of 24 hours here.
If you have large numbers of jobs or intensive jobs you should use the general queue.
If you have ad hoc type or similar type of work to perform, you should use the general-interactive queue.
5. Starting Your First Job
This example shows how to run a simple job that will demonstrate how to use the system and runs the date command using an alpine docker image to do so.
After you connect to the compute1 environment as shown above, launch the job with the following command.
...
Info |
---|
Congratulations! You have now run your first job within the RIS Compute environment. The rest of the documentation found within The User Manual can help you get working on your data. Compute Recipes has documentation on common use cases within the service. |
6. Here Are a Few Next Steps
Connecting to My Research Storage Space
...