Skip to content

Mention workflow tools (i.e., made for automatization) #159

Open

Description

@GuilloteauQ

It might be interesting to mention tools made for automatization to the authors.

As reviewers we are too often seeing the "single run.sh" approach to automatization.
But this is often not robust, not configuration by the reviewers, not parallelizable by the reviewers, and not idempotent (when possible).

Tools such as workflow managers might be worth a mention in the packaging-guide.md.

I am thinking of tools such as Make, Snakemake, CWL, NextFlow, etc

If you are interested, I can try to write a small description and list a few tools.

- **Automate as much as possible**, you will save a lot of time in the end from not having to re-run experiments that suffered from human error.
This is feasible even for artifacts that need multiple nodes or to replicate configuration in multiple places.
See [this repository](https://github.com/SolalPirelli/docker-artifact-eval) for an example of artifact automation with Docker.

Activity

  1. SolalPirelli commented on Mar 2, 2026

    @SolalPirelli
    Collaborator

    Sounds good, especially if you know good tutorials for these tools -- the average Make file isn't that far from a shell script ^^' (and to be fair, making a proper Makefile with incremental build etc is not trivial)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions