Today, we're introducing a new high-priority QOS for owner partitions.

In groups which have purchased their own compute nodes on Sherlock, users can now submit jobs to their group partition using the --qos=high_p option: it will give those jobs a priority boost, and will allow for distinguishing between two classes of jobs within the same partition.

This new QOS could be useful to prioritize specific jobs that need to get executed before others, to meet deadlines or differentiate between background and higher-priority jobs.

If your group is not an owner on Sherlock yet, but if you're interested in becoming one, please take a look at the Sherlock website and let us know if you have any question.