Snakemake storage plugin: latch

https://img.shields.io/badge/repository-unknown-blue?color=%23022c22 https://img.shields.io/badge/author-Ayush%20Kamat-purple?color=%23064e3b PyPI - Version PyPI - License

Warning

No repository URL found in Pypi metadata. The plugin should specify a repository URL in its pyproject.toml (key ‘repository’).

Installation

Install this plugin by installing it with pip or mamba, e.g.:

pip install snakemake-storage-plugin-latch

Usage

Queries

Queries to this storage should have the following format:

Query type

Query

Description

any

latch://123.account/hello

basic latch path

As default provider

If you want all your input and output (which is not explicitly marked to come from another storage) to be written to and read from this storage, you can use it as a default provider via:

snakemake --default-storage-provider latch --default-storage-prefix ...

with ... being the prefix of a query under which you want to store all your results. You can also pass custom settings via command line arguments:

snakemake --default-storage-provider latch --default-storage-prefix ... \
    --storage-latch-max-requests-per-second ...

Within the workflow

If you want to use this storage plugin only for specific items, you can register it inside of your workflow:

# register storage provider (not needed if no custom settings are to be defined here)
storage:
    provider="latch",
    # optionally add custom settings here if needed
    # alternatively they can be passed via command line arguments
    # starting with --storage-latch-..., see
    # snakemake --help
    # Maximum number of requests per second for this storage provider. If nothing is specified, the default implemented by the storage plugin is used.
    max_requests_per_second=...,

rule example:
    input:
        storage.latch(
            # define query to the storage backend here
            ...
        ),
    output:
        "example.txt"
    shell:
        "..."

Using multiple entities of the same storage plugin

In case you have to use this storage plugin multiple times, but with different settings (e.g. to connect to different storage servers), you can register it multiple times, each time providing a different tag:

# register shared settings
storage:
    provider="latch",
    # optionally add custom settings here if needed
    # alternatively they can be passed via command line arguments
    # starting with --storage-latch-..., see below
    # Maximum number of requests per second for this storage provider. If nothing is specified, the default implemented by the storage plugin is used.
    max_requests_per_second=...,

# register multiple tagged entities
storage foo:
    provider="latch",
    # optionally add custom settings here if needed
    # alternatively they can be passed via command line arguments
    # starting with --storage-latch-..., see below.
    # To only pass a setting to this tagged entity, prefix the given value with
    # the tag name, i.e. foo:max_requests_per_second=...
    # Maximum number of requests per second for this storage provider. If nothing is specified, the default implemented by the storage plugin is used.
    max_requests_per_second=...,

rule example:
    input:
        storage.foo(
            # define query to the storage backend here
            ...
        ),
    output:
        "example.txt"
    shell:
        "..."

Settings

The storage plugin has the following settings (which can be passed via command line, the workflow or environment variables, if provided in the respective columns):

CLI setting

Workflow setting

Envvar setting

Description

Default

Choices

Required

Type

--storage-latch-max-requests-per-second VALUE

max_requests_per_second

Maximum number of requests per second for this storage provider. If nothing is specified, the default implemented by the storage plugin is used.

None

str