home.social

#snakemakehackathon2026 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #snakemakehackathon2026, aggregated by home.social.

  1. RE: fediscience.org/@snakemake/116

    This little bit "performance improvements" lowered the number of file system access events for considerably! #Snakemake triggers many such events for keeping track of metadata. Which is important, but may cause some delays due to file system overhead - particularly on parallel and/or network file systems. The feature to outsource parts of this to sqlite was implemented during the #SnakemakeHackathon2026 . I hope, I can test the improvements next Monday!

    #HPC #ReproducibleComputing

  2. RE: fediscience.org/@snakemake/116

    This little bit "performance improvements" lowered the number of file system access events for considerably! #Snakemake triggers many such events for keeping track of metadata. Which is important, but may cause some delays due to file system overhead - particularly on parallel and/or network file systems. The feature to outsource parts of this to sqlite was implemented during the #SnakemakeHackathon2026 . I hope, I can test the improvements next Monday!

    #HPC #ReproducibleComputing

  3. RE: fediscience.org/@snakemake/116

    This little bit "performance improvements" lowered the number of file system access events for considerably! #Snakemake triggers many such events for keeping track of metadata. Which is important, but may cause some delays due to file system overhead - particularly on parallel and/or network file systems. The feature to outsource parts of this to sqlite was implemented during the #SnakemakeHackathon2026 . I hope, I can test the improvements next Monday!

    #HPC #ReproducibleComputing

  4. RE: fediscience.org/@snakemake/116

    This little bit "performance improvements" lowered the number of file system access events for considerably! #Snakemake triggers many such events for keeping track of metadata. Which is important, but may cause some delays due to file system overhead - particularly on parallel and/or network file systems. The feature to outsource parts of this to sqlite was implemented during the #SnakemakeHackathon2026 . I hope, I can test the improvements next Monday!

    #HPC #ReproducibleComputing

  5. RE: fediscience.org/@snakemake/116

    This little bit "performance improvements" lowered the number of file system access events for considerably! #Snakemake triggers many such events for keeping track of metadata. Which is important, but may cause some delays due to file system overhead - particularly on parallel and/or network file systems. The feature to outsource parts of this to sqlite was implemented during the #SnakemakeHackathon2026 . I hope, I can test the improvements next Monday!

    #HPC #ReproducibleComputing

  6. RE: fediscience.org/@biohackrxiv/1

    Today, we published the summary (as a #BioHackrXiv preprint) of the #SnakemakeHackathon2026 . All the accomplishments which contribute once more to improve the #Snakemake "ecosystem" for #reproducibleResearch & #Dataanalysis .

    Many thanks to @egonw from BioHackrXiv for helping us!

  7. RE: fediscience.org/@biohackrxiv/1

    Today, we published the summary (as a #BioHackrXiv preprint) of the #SnakemakeHackathon2026 . All the accomplishments which contribute once more to improve the #Snakemake "ecosystem" for #reproducibleResearch & #Dataanalysis .

    Many thanks to @egonw from BioHackrXiv for helping us!

  8. RE: fediscience.org/@biohackrxiv/1

    Today, we published the summary (as a #BioHackrXiv preprint) of the #SnakemakeHackathon2026 . All the accomplishments which contribute once more to improve the #Snakemake "ecosystem" for #reproducibleResearch & #Dataanalysis .

    Many thanks to @egonw from BioHackrXiv for helping us!

  9. RE: fediscience.org/@biohackrxiv/1

    Today, we published the summary (as a #BioHackrXiv preprint) of the #SnakemakeHackathon2026 . All the accomplishments which contribute once more to improve the #Snakemake "ecosystem" for #reproducibleResearch & #Dataanalysis .

    Many thanks to @egonw from BioHackrXiv for helping us!

  10. RE: fediscience.org/@biohackrxiv/1

    Today, we published the summary (as a #BioHackrXiv preprint) of the #SnakemakeHackathon2026 . All the accomplishments which contribute once more to improve the #Snakemake "ecosystem" for #reproducibleResearch & #Dataanalysis .

    Many thanks to @egonw from BioHackrXiv for helping us!

  11. "Snakemake Hackathon 2026" doi.org/10.37044/osf.io/h6zqj_

    "Nonetheless, the platform’s continued evolution faces several open challenges: improving core performance on heterogeneous high-performance-computing (HPC) resources, extending the plugin architecture for domain-specific extensions, and lowering the entry barrier for novice users while preserving full reproducibility. Here we report on the Snakemake Hackathon 2026, convened in Munich, Germany (9–13 March 2026) with more than 40 participants representing academia, industry, and national-level research infrastructure." index.biohackrxiv.org/2026/04/

    #SnakemakeHackathon2026 #biohackathon #snakemake

  12. "Snakemake Hackathon 2026" doi.org/10.37044/osf.io/h6zqj_

    "Nonetheless, the platform’s continued evolution faces several open challenges: improving core performance on heterogeneous high-performance-computing (HPC) resources, extending the plugin architecture for domain-specific extensions, and lowering the entry barrier for novice users while preserving full reproducibility. Here we report on the Snakemake Hackathon 2026, convened in Munich, Germany (9–13 March 2026) with more than 40 participants representing academia, industry, and national-level research infrastructure." index.biohackrxiv.org/2026/04/

    #SnakemakeHackathon2026 #biohackathon #snakemake

  13. "Snakemake Hackathon 2026" doi.org/10.37044/osf.io/h6zqj_

    "Nonetheless, the platform’s continued evolution faces several open challenges: improving core performance on heterogeneous high-performance-computing (HPC) resources, extending the plugin architecture for domain-specific extensions, and lowering the entry barrier for novice users while preserving full reproducibility. Here we report on the Snakemake Hackathon 2026, convened in Munich, Germany (9–13 March 2026) with more than 40 participants representing academia, industry, and national-level research infrastructure." index.biohackrxiv.org/2026/04/

    #SnakemakeHackathon2026 #biohackathon #snakemake

  14. "Snakemake Hackathon 2026" doi.org/10.37044/osf.io/h6zqj_

    "Nonetheless, the platform’s continued evolution faces several open challenges: improving core performance on heterogeneous high-performance-computing (HPC) resources, extending the plugin architecture for domain-specific extensions, and lowering the entry barrier for novice users while preserving full reproducibility. Here we report on the Snakemake Hackathon 2026, convened in Munich, Germany (9–13 March 2026) with more than 40 participants representing academia, industry, and national-level research infrastructure." index.biohackrxiv.org/2026/04/

    #SnakemakeHackathon2026 #biohackathon #snakemake

  15. "Snakemake Hackathon 2026" doi.org/10.37044/osf.io/h6zqj_

    "Nonetheless, the platform’s continued evolution faces several open challenges: improving core performance on heterogeneous high-performance-computing (HPC) resources, extending the plugin architecture for domain-specific extensions, and lowering the entry barrier for novice users while preserving full reproducibility. Here we report on the Snakemake Hackathon 2026, convened in Munich, Germany (9–13 March 2026) with more than 40 participants representing academia, industry, and national-level research infrastructure." index.biohackrxiv.org/2026/04/

    #SnakemakeHackathon2026 #biohackathon #snakemake

  16. The #SnakemakeHackathon2026 has ended, we are still preparing our preprint release. But, our host has prepared a note on their homepage: go.tum.de/946236 🥳

    #Snakemake #ReproducibleComputing

  17. The #SnakemakeHackathon2026 has ended, we are still preparing our preprint release. But, our host has prepared a note on their homepage: go.tum.de/946236 🥳

    #Snakemake #ReproducibleComputing

  18. The #SnakemakeHackathon2026 has ended, we are still preparing our preprint release. But, our host has prepared a note on their homepage: go.tum.de/946236 🥳

    #Snakemake #ReproducibleComputing

  19. The #SnakemakeHackathon2026 has ended, we are still preparing our preprint release. But, our host has prepared a note on their homepage: go.tum.de/946236 🥳

    #Snakemake #ReproducibleComputing

  20. The #SnakemakeHackathon2026 has ended, we are still preparing our preprint release. But, our host has prepared a note on their homepage: go.tum.de/946236 🥳

    #Snakemake #ReproducibleComputing

  21. RE: fediscience.org/@snakemake/116

    This is a big step forward: The SLURM plugin for Snakemake now supports so-called job arrays. These are cluster jobs, with ~ equal resource requirements in terms of memory and compute resources.

    The change in itself was big: The purpose of a workflow system is to make use of the vast resources of an HPC cluster. Hence, jobs are submitted to run concurrently. However, for a job array, we have to "wait" for all eligible jobs to be ready. And then we submit.

    To preserve concurrent execution of other jobs which are ready to be executed, a thread pool has been introduced. In itself, I do not see job arrays as such a big feature: The LSF system profited much more from arrays than the rather lean SLURM implementation does.

    BUT: the new code base will ease further development to pooling many shared memory tasks (applications which support no parallel execution or are confined to one computer by "only" supporting threading). Until then, there is more work to do.

    #HPC #SLURM #Snakemake #SnakemakeHackathon2026 #ReproducibleComputing #OpenScience

  22. RE: fediscience.org/@snakemake/116

    This is a big step forward: The SLURM plugin for Snakemake now supports so-called job arrays. These are cluster jobs, with ~ equal resource requirements in terms of memory and compute resources.

    The change in itself was big: The purpose of a workflow system is to make use of the vast resources of an HPC cluster. Hence, jobs are submitted to run concurrently. However, for a job array, we have to "wait" for all eligible jobs to be ready. And then we submit.

    To preserve concurrent execution of other jobs which are ready to be executed, a thread pool has been introduced. In itself, I do not see job arrays as such a big feature: The LSF system profited much more from arrays than the rather lean SLURM implementation does.

    BUT: the new code base will ease further development to pooling many shared memory tasks (applications which support no parallel execution or are confined to one computer by "only" supporting threading). Until then, there is more work to do.

    #HPC #SLURM #Snakemake #SnakemakeHackathon2026 #ReproducibleComputing #OpenScience

  23. RE: fediscience.org/@snakemake/116

    This is a big step forward: The SLURM plugin for Snakemake now supports so-called job arrays. These are cluster jobs, with ~ equal resource requirements in terms of memory and compute resources.

    The change in itself was big: The purpose of a workflow system is to make use of the vast resources of an HPC cluster. Hence, jobs are submitted to run concurrently. However, for a job array, we have to "wait" for all eligible jobs to be ready. And then we submit.

    To preserve concurrent execution of other jobs which are ready to be executed, a thread pool has been introduced. In itself, I do not see job arrays as such a big feature: The LSF system profited much more from arrays than the rather lean SLURM implementation does.

    BUT: the new code base will ease further development to pooling many shared memory tasks (applications which support no parallel execution or are confined to one computer by "only" supporting threading). Until then, there is more work to do.

    #HPC #SLURM #Snakemake #SnakemakeHackathon2026 #ReproducibleComputing #OpenScience

  24. RE: fediscience.org/@snakemake/116

    This is a big step forward: The SLURM plugin for Snakemake now supports so-called job arrays. These are cluster jobs, with ~ equal resource requirements in terms of memory and compute resources.

    The change in itself was big: The purpose of a workflow system is to make use of the vast resources of an HPC cluster. Hence, jobs are submitted to run concurrently. However, for a job array, we have to "wait" for all eligible jobs to be ready. And then we submit.

    To preserve concurrent execution of other jobs which are ready to be executed, a thread pool has been introduced. In itself, I do not see job arrays as such a big feature: The LSF system profited much more from arrays than the rather lean SLURM implementation does.

    BUT: the new code base will ease further development to pooling many shared memory tasks (applications which support no parallel execution or are confined to one computer by "only" supporting threading). Until then, there is more work to do.

    #HPC #SLURM #Snakemake #SnakemakeHackathon2026 #ReproducibleComputing #OpenScience

  25. RE: fediscience.org/@snakemake/116

    This is a big step forward: The SLURM plugin for Snakemake now supports so-called job arrays. These are cluster jobs, with ~ equal resource requirements in terms of memory and compute resources.

    The change in itself was big: The purpose of a workflow system is to make use of the vast resources of an HPC cluster. Hence, jobs are submitted to run concurrently. However, for a job array, we have to "wait" for all eligible jobs to be ready. And then we submit.

    To preserve concurrent execution of other jobs which are ready to be executed, a thread pool has been introduced. In itself, I do not see job arrays as such a big feature: The LSF system profited much more from arrays than the rather lean SLURM implementation does.

    BUT: the new code base will ease further development to pooling many shared memory tasks (applications which support no parallel execution or are confined to one computer by "only" supporting threading). Until then, there is more work to do.

    #HPC #SLURM #Snakemake #SnakemakeHackathon2026 #ReproducibleComputing #OpenScience

  26. 2/3 accomplished ✅

    Now, for a release a dependency has to be released with my two fixes, which have already been merged. Then, the world will see a new #nanopub application.

    A #SnakemakeHackathon2026 result.

  27. 2/3 accomplished ✅

    Now, for a release a dependency has to be released with my two fixes, which have already been merged. Then, the world will see a new #nanopub application.

    A #SnakemakeHackathon2026 result.

  28. 2/3 accomplished ✅

    Now, for a release a dependency has to be released with my two fixes, which have already been merged. Then, the world will see a new #nanopub application.

    A #SnakemakeHackathon2026 result.

  29. 2/3 accomplished ✅

    Now, for a release a dependency has to be released with my two fixes, which have already been merged. Then, the world will see a new #nanopub application.

    A #SnakemakeHackathon2026 result.

  30. 2/3 accomplished ✅

    Now, for a release a dependency has to be released with my two fixes, which have already been merged. Then, the world will see a new #nanopub application.

    A #SnakemakeHackathon2026 result.

  31. RE: fediscience.org/@snakemake/116

    Hm, I thought(!) that I fixed some issues with this bot. Appears not to be the case. Moreover, the `**docs** should be bold, not ignored. 🤦

    Any way, this release is yet another leftover from the #SnakemakeHackathon2026 !

  32. RE: fediscience.org/@snakemake/116

    Hm, I thought(!) that I fixed some issues with this bot. Appears not to be the case. Moreover, the `**docs** should be bold, not ignored. 🤦

    Any way, this release is yet another leftover from the #SnakemakeHackathon2026 !

  33. RE: fediscience.org/@snakemake/116

    Hm, I thought(!) that I fixed some issues with this bot. Appears not to be the case. Moreover, the `**docs** should be bold, not ignored. 🤦

    Any way, this release is yet another leftover from the #SnakemakeHackathon2026 !

  34. RE: fediscience.org/@snakemake/116

    Hm, I thought(!) that I fixed some issues with this bot. Appears not to be the case. Moreover, the `**docs** should be bold, not ignored. 🤦

    Any way, this release is yet another leftover from the #SnakemakeHackathon2026 !

  35. RE: fediscience.org/@snakemake/116

    Hm, I thought(!) that I fixed some issues with this bot. Appears not to be the case. Moreover, the `**docs** should be bold, not ignored. 🤦

    Any way, this release is yet another leftover from the #SnakemakeHackathon2026 !

  36. Personally, the week in Munich at the #SnakemakeHackathon2026 was really neat. I met friends and acquaintances, took the time to meet an old friend of mine not working in academia any more and the wonderful @FrankSonntag from our #FediScience association.

    And now, tired, on my way back. Thanks to the railway service in Germany, I enjoy some boredom and the opportunity to do something else. Even reading a disc world novel (which is not "novel" any more) does not help.

    #lifeis2short

  37. Personally, the week in Munich at the #SnakemakeHackathon2026 was really neat. I met friends and acquaintances, took the time to meet an old friend of mine not working in academia any more and the wonderful @FrankSonntag from our #FediScience association.

    And now, tired, on my way back. Thanks to the railway service in Germany, I enjoy some boredom and the opportunity to do something else. Even reading a disc world novel (which is not "novel" any more) does not help.

    #lifeis2short

  38. Personally, the week in Munich at the #SnakemakeHackathon2026 was really neat. I met friends and acquaintances, took the time to meet an old friend of mine not working in academia any more and the wonderful @FrankSonntag from our #FediScience association.

    And now, tired, on my way back. Thanks to the railway service in Germany, I enjoy some boredom and the opportunity to do something else. Even reading a disc world novel (which is not "novel" any more) does not help.

    #lifeis2short

  39. Personally, the week in Munich at the #SnakemakeHackathon2026 was really neat. I met friends and acquaintances, took the time to meet an old friend of mine not working in academia any more and the wonderful @FrankSonntag from our #FediScience association.

    And now, tired, on my way back. Thanks to the railway service in Germany, I enjoy some boredom and the opportunity to do something else. Even reading a disc world novel (which is not "novel" any more) does not help.

    #lifeis2short

  40. Personally, the week in Munich at the #SnakemakeHackathon2026 was really neat. I met friends and acquaintances, took the time to meet an old friend of mine not working in academia any more and the wonderful @FrankSonntag from our #FediScience association.

    And now, tired, on my way back. Thanks to the railway service in Germany, I enjoy some boredom and the opportunity to do something else. Even reading a disc world novel (which is not "novel" any more) does not help.

    #lifeis2short

  41. I learned, that I am the first to write a reporter plugin, which is part of the #Snakemake organization.

    That will change. @fbartusch is working on an #ROCrate plugin. Yours truly is working on a #nanopub plugin. Both will ease publishing workflow analysis metadata and making our computing a bit more transparent. Our motivation? Well, did you ever read a data analysis paper (e.g. from an #Bioinformatis group) recently? See?

    #SnakemakeHackathon2026

  42. I learned, that I am the first to write a reporter plugin, which is part of the #Snakemake organization.

    That will change. @fbartusch is working on an #ROCrate plugin. Yours truly is working on a #nanopub plugin. Both will ease publishing workflow analysis metadata and making our computing a bit more transparent. Our motivation? Well, did you ever read a data analysis paper (e.g. from an #Bioinformatis group) recently? See?

    #SnakemakeHackathon2026

  43. I learned, that I am the first to write a reporter plugin, which is part of the #Snakemake organization.

    That will change. @fbartusch is working on an #ROCrate plugin. Yours truly is working on a #nanopub plugin. Both will ease publishing workflow analysis metadata and making our computing a bit more transparent. Our motivation? Well, did you ever read a data analysis paper (e.g. from an #Bioinformatis group) recently? See?

    #SnakemakeHackathon2026

  44. I learned, that I am the first to write a reporter plugin, which is part of the #Snakemake organization.

    That will change. @fbartusch is working on an #ROCrate plugin. Yours truly is working on a #nanopub plugin. Both will ease publishing workflow analysis metadata and making our computing a bit more transparent. Our motivation? Well, did you ever read a data analysis paper (e.g. from an #Bioinformatis group) recently? See?

    #SnakemakeHackathon2026

  45. I learned, that I am the first to write a reporter plugin, which is part of the #Snakemake organization.

    That will change. @fbartusch is working on an #ROCrate plugin. Yours truly is working on a #nanopub plugin. Both will ease publishing workflow analysis metadata and making our computing a bit more transparent. Our motivation? Well, did you ever read a data analysis paper (e.g. from an #Bioinformatis group) recently? See?

    #SnakemakeHackathon2026