Sherlock changelog

www.sherlock.stanford.edu

timestamp1734649786948

Introducing Boltz-1 on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC

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

timestamp1724970751957

Sherlock 4.0: a new cluster generation

by Kilian Cavalotti, Technical Lead & Architect, HPC

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

timestamp1700100000000

A brand new Sherlock OnDemand experience

by Kilian Cavalotti, Technical Lead & Architect, HPC

Stanford Research Computing is proud to unveil Sherlock OnDemand 3.0, a cutting-edge enhancement to its computing and data storage resources, revolutionizing user interaction and efficiency.

timestamp1683930644259

Final hours announced for the June 2023 SRCF downtime

by Kilian Cavalotti, Technical Lead & Architect, HPC

As previously announced, the Stanford Research Computing Facility (SRCF), where Sherlock is hosted, will be powered off during the last week of June, in order to safely bring up power to the new SRCF2 datacenter. Sherlock will not be

Final hours announced for the June 2023 SRCF downtime

timestamp1671038838657

More free compute on Sherlock!

by Kilian Cavalotti, Technical Lead & Architect, HPC

We’re thrilled to announce that the free and generally available normal partition on Sherlock is getting an upgrade! With the addition of 24 brand new SH3_CBASE.1 compute nodes, each featuring one AMD EPYC 7543 Milan 32-core CPU and 256 GB

More free compute on Sherlock!

timestamp1670036242756

ClusterShell on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC

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

timestamp1667700685989

Job #1, again!

by Kilian Cavalotti, Technical Lead & Architect, HPC

This is not the first time, we’ve been through this already (not so long ago, actually) but today, the Slurm job id counter was reset and went from job #67043327 back to job #1.

Newer