Build pipeline: viash-hub.demultiplex.main-4xxbp
Source commit: 795abd6868
Source message: Run Falco in parallel for each well (#33)
159 lines
5.8 KiB
JSON
159 lines
5.8 KiB
JSON
{
|
|
"$schema": "http://json-schema.org/draft-07/schema",
|
|
"title": "publish",
|
|
"description": "Publish the processed results of the run",
|
|
"type": "object",
|
|
"definitions": {
|
|
|
|
|
|
|
|
"input arguments" : {
|
|
"title": "Input arguments",
|
|
"type": "object",
|
|
"description": "No description",
|
|
"properties": {
|
|
|
|
|
|
"input": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, required. Directory to write fastq data to",
|
|
"help_text": "Type: `file`, required. Directory to write fastq data to"
|
|
|
|
}
|
|
|
|
|
|
,
|
|
"input_falco": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: List of `file`, required, multiple_sep: `\";\"`. Directory to write falco output to",
|
|
"help_text": "Type: List of `file`, required, multiple_sep: `\";\"`. Directory to write falco output to"
|
|
|
|
}
|
|
|
|
|
|
,
|
|
"input_multiqc": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, required. Location where to write the MultiQC report to",
|
|
"help_text": "Type: `file`, required. Location where to write the MultiQC report to."
|
|
|
|
}
|
|
|
|
|
|
,
|
|
"input_run_information": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, required. Location where to write the run information to",
|
|
"help_text": "Type: `file`, required. Location where to write the run information to."
|
|
|
|
}
|
|
|
|
|
|
}
|
|
},
|
|
|
|
|
|
"output arguments" : {
|
|
"title": "Output arguments",
|
|
"type": "object",
|
|
"description": "No description",
|
|
"properties": {
|
|
|
|
|
|
"output": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.output.output`. ",
|
|
"help_text": "Type: `file`, default: `$id.$key.output.output`. "
|
|
,
|
|
"default":"$id.$key.output.output"
|
|
}
|
|
|
|
|
|
,
|
|
"output_falco": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.output_falco.output_falco`. ",
|
|
"help_text": "Type: `file`, default: `$id.$key.output_falco.output_falco`. "
|
|
,
|
|
"default":"$id.$key.output_falco.output_falco"
|
|
}
|
|
|
|
|
|
,
|
|
"output_multiqc": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.output_multiqc.html`. ",
|
|
"help_text": "Type: `file`, default: `$id.$key.output_multiqc.html`. "
|
|
,
|
|
"default":"$id.$key.output_multiqc.html"
|
|
}
|
|
|
|
|
|
,
|
|
"output_run_information": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.output_run_information.csv`. ",
|
|
"help_text": "Type: `file`, default: `$id.$key.output_run_information.csv`. "
|
|
,
|
|
"default":"$id.$key.output_run_information.csv"
|
|
}
|
|
|
|
|
|
}
|
|
},
|
|
|
|
|
|
"nextflow input-output arguments" : {
|
|
"title": "Nextflow input-output arguments",
|
|
"type": "object",
|
|
"description": "Input/output parameters for Nextflow itself. Please note that both publishDir and publish_dir are supported but at least one has to be configured.",
|
|
"properties": {
|
|
|
|
|
|
"publish_dir": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `string`, required, example: `output/`. Path to an output directory",
|
|
"help_text": "Type: `string`, required, example: `output/`. Path to an output directory."
|
|
|
|
}
|
|
|
|
|
|
,
|
|
"param_list": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `string`, example: `my_params.yaml`. Allows inputting multiple parameter sets to initialise a Nextflow channel",
|
|
"help_text": "Type: `string`, example: `my_params.yaml`. Allows inputting multiple parameter sets to initialise a Nextflow channel. A `param_list` can either be a list of maps, a csv file, a json file, a yaml file, or simply a yaml blob.\n\n* A list of maps (as-is) where the keys of each map corresponds to the arguments of the pipeline. Example: in a `nextflow.config` file: `param_list: [ [\u0027id\u0027: \u0027foo\u0027, \u0027input\u0027: \u0027foo.txt\u0027], [\u0027id\u0027: \u0027bar\u0027, \u0027input\u0027: \u0027bar.txt\u0027] ]`.\n* A csv file should have column names which correspond to the different arguments of this pipeline. Example: `--param_list data.csv` with columns `id,input`.\n* A json or a yaml file should be a list of maps, each of which has keys corresponding to the arguments of the pipeline. Example: `--param_list data.json` with contents `[ {\u0027id\u0027: \u0027foo\u0027, \u0027input\u0027: \u0027foo.txt\u0027}, {\u0027id\u0027: \u0027bar\u0027, \u0027input\u0027: \u0027bar.txt\u0027} ]`.\n* A yaml blob can also be passed directly as a string. Example: `--param_list \"[ {\u0027id\u0027: \u0027foo\u0027, \u0027input\u0027: \u0027foo.txt\u0027}, {\u0027id\u0027: \u0027bar\u0027, \u0027input\u0027: \u0027bar.txt\u0027} ]\"`.\n\nWhen passing a csv, json or yaml file, relative path names are relativized to the location of the parameter file. No relativation is performed when `param_list` is a list of maps (as-is) or a yaml blob.",
|
|
"hidden": true
|
|
|
|
}
|
|
|
|
|
|
}
|
|
}
|
|
},
|
|
"allOf": [
|
|
|
|
{
|
|
"$ref": "#/definitions/input arguments"
|
|
},
|
|
|
|
{
|
|
"$ref": "#/definitions/output arguments"
|
|
},
|
|
|
|
{
|
|
"$ref": "#/definitions/nextflow input-output arguments"
|
|
}
|
|
]
|
|
}
|