Beep, Beep - I am your friendly #Snakemake release announcement bot.

There is a new release of the Snakemake executor for #SLURM on #HPC systems. Its version now is 2.0.2!

Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi.

If you want to discuss the release, you will find the maintainers here on Mastodon!
@rupdecat and @johanneskoester

If you discover any issues, please report them on https://github.com/snakemake/snakemake-executor-plugin-slurm/issues.

See https://github.com/snakemake/snakemake-executor-plugin-slurm/releases/tag/v2.0.2 for details. Here is the header of the changelog:
𝑅𝑒𝑙𝑒𝑎𝑠𝑒 𝑁𝑜𝑡𝑒𝑠 (𝑝𝑜𝑠𝑠𝑖𝑏𝑙𝑦 𝑎𝑏𝑏𝑟𝑖𝑔𝑒𝑑):
𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬

* partition cluster selection: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/385

Beep, Beep - I am your friendly #Snakemake release announcement bot.

There is a new release of the Snakemake executor for #SLURM on #HPC systems. Its version now is 2.0.2!

Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi.

If you want to discuss the release, you will find the maintainers here on Mastodon!
@rupdecat and @johanneskoester

If you discover any issues, please report them on https://github.com/snakemake/snakemake-executor-plugin-slurm/issues.

See https://github.com/snakemake/snakemake-executor-plugin-slurm/releases/tag/v2.0.2 for details. Here is the header of the changelog:
𝑅𝑒𝑙𝑒𝑎𝑠𝑒 𝑁𝑜𝑡𝑒𝑠 (𝑝𝑜𝑠𝑠𝑖𝑏𝑙𝑦 𝑎𝑏𝑏𝑟𝑖𝑔𝑒𝑑):
𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬

* partition cluster selection: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/385

Beep, Beep - I am your friendly #Snakemake release announcement bot.

There is a new release of the Snakemake executor for #SLURM on #HPC systems. Its version now is 2.0.1!

Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi.

If you want to discuss the release, you will find the maintainers here on Mastodon!
@rupdecat and @johanneskoester

If you discover any issues, please report them on https://github.com/snakemake/snakemake-executor-plugin-slurm/issues.

See https://github.com/snakemake/snakemake-executor-plugin-slurm/releases/tag/v2.0.1 for details. Here is the header of the changelog:
𝑅𝑒𝑙𝑒𝑎𝑠𝑒 𝑁𝑜𝑡𝑒𝑠 (𝑝𝑜𝑠𝑠𝑖𝑏𝑙𝑦 𝑎𝑏𝑏𝑟𝑖𝑔𝑒𝑑):
𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬

* validator check for integers was broken.: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/381

Beep, Beep - I am your friendly #Snakemake release announcement bot.

There is a new release of the Snakemake executor for #SLURM on #HPC systems. Its version now is 2.0.1!

Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi.

If you want to discuss the release, you will find the maintainers here on Mastodon!
@rupdecat and @johanneskoester

If you discover any issues, please report them on https://github.com/snakemake/snakemake-executor-plugin-slurm/issues.

See https://github.com/snakemake/snakemake-executor-plugin-slurm/releases/tag/v2.0.1 for details. Here is the header of the changelog:
𝑅𝑒𝑙𝑒𝑎𝑠𝑒 𝑁𝑜𝑡𝑒𝑠 (𝑝𝑜𝑠𝑠𝑖𝑏𝑙𝑦 𝑎𝑏𝑏𝑟𝑖𝑔𝑒𝑑):
𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬

* validator check for integers was broken.: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/381

@rupdecat @jannem The #HPC community lost a lot when Slurm failed to implement the DRMAA standard. The API and the code that underpins it are messy as a result. But it was popular and free, so it gained a strong foothold. (Grid Engine was the definitive implementation, and for a while all schedulers supported DRMAA and were interoperable for codes that used it.)

There is support for multiple clusters within a given Slurm instance, but they have to be set up to use these features in advance.

Why? Why are so many admins tinkering with their SLURM setup?

I say tinkering because there are understandable amendments and breaking changes.

A breaking change is when you require developments made on "your" cluster really, really hard to port onto another. When admins do that, they were tinkering with the SLURM source code.

😱😱😱😱😱😱😱😱😱😱😱😱😱😱

#HPC #academicchatter #reproducibleComputing

RE: https://fediscience.org/@snakemake/115611862667755622

Now, this is huge!

Thanks to a contribution from Cade Mirchandani (Santa Cruz, CA), whom I met at this year's #SnakemakeHackathon users can now supply a partition profile. So, instead of wrangling #SLURM partition information into a workflow profile (indicated with --workflow-profile), we can now have a global file to contain this information.

I added a time conversion function, such that the SLURM time format is obeyed, too.

There are several other development needs, before we continue in this direction (e.g. parsing SLURM partition information directly). But a task to be done is summing this up for non-users, e.g. administrators, is due too.

In any case, I think this merits a new major version.

#Snakemake #HPC #ReproducibleComputing

Beep, Beep - I am your friendly #Snakemake release announcement bot.

There is a new release of the Snakemake executor for #SLURM on #HPC systems. Its version now is 2.0.0!

Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi.

If you want to discuss the release, you will find the maintainers here on Mastodon!
@rupdecat and @johanneskoester

If you discover any issues, please report them on https://github.com/snakemake/snakemake-executor-plugin-slurm/issues.

See https://github.com/snakemake/snakemake-executor-plugin-slurm/releases/tag/v2.0.0 for details. Here is the header of the changelog:

𝑅𝑒𝑙𝑒𝑎𝑠𝑒 𝑁𝑜𝑡𝑒𝑠 (𝑝𝑜𝑠𝑠𝑖𝑏𝑙𝑦 𝑎𝑏𝑏𝑟𝑖𝑔𝑒𝑑):
⚠ 𝐁𝐑𝐄𝐀𝐊𝐈𝐍𝐆 𝐂𝐇𝐀𝐍𝐆𝐄𝐒

* proposal for dynamic partition selection: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/321

𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐬

* partition time handling: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/378
* proposal for dynamic partition selection: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/321

𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬

* naming SLURM logs, SLURM logs not just "log files": https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/372

𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧

* Replace incorrect Markdown with a blockquote: https://github.com/snakemake/snakemake-executor-plugin-slurm/issues/377

Virtual SLURM HPC cluster in a Docker Compose

https://github.com/exactlab/vhpc

#HackerNews #Virtual #SLURM #HPC #cluster #Docker #Compose #HPC #Cloud #Computing #OpenSource

Tik tok, the clock is ticking…
Only 10 more days left to submit your talk proposal for the #HPC, Big Data, and Data Science devroom at #FOSDEM’26 !

https://hpc-bigdata-fosdem26.github.io

Same goes for pretty much all of the other devrooms BTW…
See https://fosdem.org/2026/schedule/tracks/

Tik tok, the clock is ticking…
Only 10 more days left to submit your talk proposal for the #HPC, Big Data, and Data Science devroom at #FOSDEM’26 !

https://hpc-bigdata-fosdem26.github.io

Same goes for pretty much all of the other devrooms BTW…
See https://fosdem.org/2026/schedule/tracks/

This sounds horrifying: https://www.hpcwire.com/2025/11/19/new-world-order-coming-with-new-doe-supercomputers/

Apparently Oracle will be operating the next big DOE systems. I don't have words...

#hpc #doe #oracle #insanity

This sounds horrifying: https://www.hpcwire.com/2025/11/19/new-world-order-coming-with-new-doe-supercomputers/

Apparently Oracle will be operating the next big DOE systems. I don't have words...

#hpc #doe #oracle #insanity

Made my day when @geerlingguy stopped by the Texas Tech #SC25 booth to take a look at our x86 mini-clusters that run Warewulf, Ansible, Spack, and complete scientific #HPC applications with the same software stack as on our main clusters.

@guix may be a good alternative or even a companion for

European Environment for Scientific Software Installations

https://www.eessi.io/

Quote: "What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance?"

I faced it while preparing #guixastroupdate 2025/11

#Guix #EESSI
#HPC #OpenScience

Made my day when @geerlingguy stopped by the Texas Tech #SC25 booth to take a look at our x86 mini-clusters that run Warewulf, Ansible, Spack, and complete scientific #HPC applications with the same software stack as on our main clusters.

@guix may be a good alternative or even a companion for

European Environment for Scientific Software Installations

https://www.eessi.io/

Quote: "What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance?"

I faced it while preparing #guixastroupdate 2025/11

#Guix #EESSI
#HPC #OpenScience

Deadline for submissions for the 11th #HPC, #BigData, and #DataScience devroom at #FOSDEM26 (Brussels, Sat-Sun 31 Jan + 1 Feb 2026) is Mon 1 Dec 2025. Please see details at the link below. Looking forward to another dynamic, exciting, packed session! https://hpc-bigdata-fosdem26.github.io/

Deadline for submissions for the 11th #HPC, #BigData, and #DataScience devroom at #FOSDEM26 (Brussels, Sat-Sun 31 Jan + 1 Feb 2026) is Mon 1 Dec 2025. Please see details at the link below. Looking forward to another dynamic, exciting, packed session! https://hpc-bigdata-fosdem26.github.io/

This took a while. After the new version of the Snakemake paper (a rolling paper on F1000) came out, the DOI now is "working" 🥳 :

https://doi.org/10.12688/f1000research.29032.3

From my point of view, it particularly describes the working with various #HPC batch systems. And: Development did not cease. If you want to follow our announcement bot for updates: @snakemake

#Snakemake #ReproducibleComputing #DataAnalysis #OpenScience #WorkflowManagement