Sherlock changelog

Sherlock changelog

www.sherlock.stanford.edu

Introducing Boltz-1 on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC
Software
We're pleased to announce the availability of Boltz-1, a new open-source molecular interactions AI model recently released by MIT.
Introducing Boltz-1 on Sherlock

Sherlock 4.0: a new cluster generation

by Kilian Cavalotti, Technical Lead & Architect, HPC
New
Announce
Hardware
We are thrilled to announce that Sherlock 4.0, the fourth generation of Stanford's High-Performance Computing cluster, is now live! This major upgrade represents a significant leap forward in our computing capabilities, offering researchers
Sherlock 4.0: a new cluster generation

Sherlock 4.0 is coming!

by Kilian Cavalotti, Technical Lead & Architect, HPC
New
Hardware
We are thrilled to announce that the next generation of Stanford's High-Performance Computing cluster is just around the corner. Mark your calendars for August 29, as we prepare to unveil Sherlock 4.0! Building on the success of previous
Sherlock 4.0 is coming!

Instant lightweight GPU instances are now available

by Kilian Cavalotti, Technical Lead & Architect, HPC
New
Hardware
We know that getting access to GPUs on Sherlock can be difficult and feel a little frustrating at times. Which is why we are excited to announce the immediate availability of our new instant lightweight GPU instances!
Instant lightweight GPU instances are now available

A new tool to help optimize job resource requirements

by Kilian Cavalotti, Technical Lead & Architect, HPC
It’s not always easy to determine the right amount of resources to request for a computing job. Making sure that the application will have enough resources to run properly, but avoiding over-requests that would make the jobs spend too much
Documentation
Scheduler
Improvement

ClusterShell on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC
Software
New
Ever wondered how your jobs were doing while they were running? Keeping a eye on a log file is nice, but what if you could quickly gather process lists, usage metrics and other data points from all the nodes your multi-node jobs are running
ClusterShell on Sherlock