Snakemake storage plugin: apd
Warning
No repository URL found in Pypi metadata. The plugin should specify a repository URL in its pyproject.toml (key 'repository'). It is unclear whether the plugin is maintained and reviewed by the official Snakemake organization (https://github.com/snakemake).
Installation
Install this plugin by installing it with pip or mamba, e.g.:
pip install snakemake-storage-plugin-apd
Usage
Queries
Queries to this storage should have the following format:
Query type |
Query |
Description |
|---|---|---|
any |
|
An example apd query |
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 apd --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 apd --default-storage-prefix ... \
--storage-apd-max-requests-per-second ... \
--storage-apd-working-group ... \
--storage-apd-analysis ... \
--storage-apd-readonly ...
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="apd",
# optionally add custom settings here if needed
# alternatively they can be passed via command line arguments
# starting with --storage-apd-..., 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=...,
# Working group of the analysis e.g. bnoc
working_group=...,
# Name of the analysis e.g. bds2kstkstb
analysis=...,
# Whether access is read-only (True by default). Set to False toallow write access
readonly=...,
rule example:
input:
storage.apd(
# 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="apd",
# optionally add custom settings here if needed
# alternatively they can be passed via command line arguments
# starting with --storage-apd-..., 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=...,
# Working group of the analysis e.g. bnoc
working_group=...,
# Name of the analysis e.g. bds2kstkstb
analysis=...,
# Whether access is read-only (True by default). Set to False toallow write access
readonly=...,
# register multiple tagged entities
storage foo:
provider="apd",
# optionally add custom settings here if needed
# alternatively they can be passed via command line arguments
# starting with --storage-apd-..., 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=...,
# Working group of the analysis e.g. bnoc
working_group=...,
# Name of the analysis e.g. bds2kstkstb
analysis=...,
# Whether access is read-only (True by default). Set to False toallow write access
readonly=...,
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):