This guide is a work in progress and is not complete yet. We are actively working on adding more content and information.
Welcome to Sherlock!#
Sherlock is a High-Performance Computing (HPC) cluster, operated by the Stanford Research Computing Center to provide computing resources to the Stanford community at large. You'll find all the documentation, tips, FAQs and information about Sherlock among these pages.
These pages refer to Sherlock 2.0, the new iteration of the Sherlock cluster. For anything specific to Sherlock 1.0, please see the previous wiki.
The older Sherlock system will remain in production until all of its nodes have been merged into Sherlock 2.0. Until then, the two systems will coexist for an extended transition period. The Sherlock 2.0 transition guide includes material intended to help users manage their transition between the two systems: differences, temporary conditions, etc.
Feel free to explore the different sections. If some information is missing, please contact us to suggest additions or modifications.
Searching the docs
If you're looking for information on a specific topic, the Search feature of this site will allow you to quickly find the page you're looking for. Just press S or F to open the Search bar and start typing.
To help users take their first steps on Sherlock, we provide documentation and information through various channels:
You are here
|www.sherlock.stanford.edu/docs||information to help new users start on Sherlock, and more in-depth documentation for users already familiar with the environment.|
|Changelog||news.sherlock.stanford.edu||announces, news and updates about Sherlock.|
|Dashboard||status.sherlock.stanford.edu||status of Sherlock's main components and services, outages, maintenances.|
To get started, you can take a look at the concepts and glossary pages to get familiar with the terminology used throughout the documentation pages. Then, we recommend going through the following sections:
Acknowledgment / citation#
It is important and expected that publications resulting from computations performed on Sherlock acknowledge this. The following wording is suggested:
Some of the computing for this project was performed on the Sherlock cluster. We would like to thank Stanford University and the Stanford Research Computing Center for providing computational resources and support that contributed to these research results.
Research Computing support can be reached by sending an email to firstname.lastname@example.org and mentioning Sherlock.
How to submit effective support requests
To ensure a timely and relevant response, please make sure to include some additional details, such as job ids, commands executed and error messages received, so we can help you better. For more details, see the Troubleshooting page.
As a member of the Sherlock community, you're also automatically subscribed to:
- the sherlock-announce mailing-list, which is only used by the SRCC team to send important announcements about Sherlock,
- the sherlock-users mailing list1, which is used to connect Sherlock users together. If you have a general question about software used on Sherlock, want to reach out to the other Sherlock users to share tips and good practices, tutorials or other info, please feel free to do so through this mailing-list.
We can't accommodate walk-ins
We're unfortunately not staffed to accommodate walk-ins, so please make sure that you're planning to stop by during office hours. We will not be able to help you otherwise.
Sending a question to email@example.com is always the best first option for questions. That way you can include detailed descriptions of the problem or question, valuable output and error messages and any steps you took when you encountered your error. Also, everyone on our team will see your ticket, enabling the most appropriate group member to respond.
Office hours are a good place for more generalized questions about Sherlock, Slurm, Linux usage, data storage, queue structures/scheduling, job optimization and general capabilities of Sherlock. It's also useful for more technically nuanced questions that may not be easily answered with our ticketing system. In office hours some problems can indeed be solved quickly or progress can be made so that you can then work self-sufficiently towards a solution on your own.
What to expect from office hours
We can rarely help with application-specific or algorithm problems.
You should plan your projects sufficiently in advance and not come to office hours at the last minute before a deadline. Sherlock is a busy resource with over 3,500 users and you should not expect your jobs to complete before a given date.
Not all questions and problems can be solved or answered during office hours, especially ones involving hardware, filesystem or network issues. Sherlock features over 1,400 servers, routers and storage pieces of equipment, that are constantly being monitored by our team. You can be sure that when Sherlock has an issue, we are aware of it and working on it.
Office hours are held twice a week, in Polya Hall, room 255 (2nd floor):
- Tuesdays, from 10am to 11am
- Thursdays from 3pm to 4pm
If you're in a rush, here's a 3-step ultra-quick start:
connect to Sherlock
$ ssh login.sherlock.stanford.edu
get an interactive session on a compute node
[kilian@sh-ln01 login! ~]$ sdev
run a command
[kilian@sh-101-58 ~]$ module load python [kilian@sh-101-58 ~]$ python -c "print('Hello Sherlock')" Hello Sherlock
Congrats! You ran your first job on Sherlock!
Here's what it looks like in motion:
This mailing-list is moderated. ↩