Idea was formulated by @jbwexler in
- specification @jbwexler suggested there to have smth like
[datalad "containers.bids-fmriprep]
cmdexec = {img_dspath}/scripts/singularity_cmd run {img} {cmd}
image = images/bids/bids-fmriprep--{version}.sing
default_version = 20.2.0
or even just
[datalad "containers.bids-fmriprep]
cmdexec = {img_dspath}/scripts/singularity_cmd run {img} {cmd}
image = images/bids/bids-fmriprep--{version}.sing
version = 20.2.0
hence version specifying the default one but us allowing to overload it while naming which container to run:
- making it possible to specify version while running e.g. as
-n {NAME}={version} or adding explicit --version to overload that version in the specification.
Idea was formulated by @jbwexler in
and does have good meaning there given that the dataset has a good number of versions for many containers. Overall it could boil down to
or even just
hence
versionspecifying the default one but us allowing to overload it while naming which container to run:-n {NAME}={version}or adding explicit--versionto overload thatversionin the specification.