CI
1ebb61f1e8
Build pipeline: vsh-ci-dev-jsbwk
Source commit: 1e1ffb315f
Source message: Merge pull request #17 from viash-hub/add_biobox_modules
- Migrate a number of components to biobox
- Fix tests
- Reduce size of test resources
- Prepare for Viash Hub
140 lines
5.6 KiB
JSON
140 lines
5.6 KiB
JSON
{
|
|
"$schema": "http://json-schema.org/draft-07/schema",
|
|
"title": "fastqc",
|
|
"description": "Fastqc component, please see https://www.bioinformatics.babraham.ac.uk/projects/fastqc/. This component can take one or more files (by means of shell globbing) or a complete directory.\n",
|
|
"type": "object",
|
|
"definitions": {
|
|
|
|
|
|
|
|
"input" : {
|
|
"title": "Input",
|
|
"type": "object",
|
|
"description": "No description",
|
|
"properties": {
|
|
|
|
|
|
"paired": {
|
|
"type":
|
|
"boolean",
|
|
"description": "Type: `boolean`, default: `false`. Paired fastq files or not?",
|
|
"help_text": "Type: `boolean`, default: `false`. Paired fastq files or not?"
|
|
,
|
|
"default": "False"
|
|
}
|
|
|
|
|
|
,
|
|
"input": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: List of `file`, required, example: `sample.fastq`, multiple_sep: `\",\"`. Input fastq files, either one or two (paired)",
|
|
"help_text": "Type: List of `file`, required, example: `sample.fastq`, multiple_sep: `\",\"`. Input fastq files, either one or two (paired)"
|
|
|
|
}
|
|
|
|
|
|
}
|
|
},
|
|
|
|
|
|
"output" : {
|
|
"title": "Output",
|
|
"type": "object",
|
|
"description": "No description",
|
|
"properties": {
|
|
|
|
|
|
"fastqc_html_1": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.fastqc_html_1.html`. FastQC HTML report for read 1",
|
|
"help_text": "Type: `file`, default: `$id.$key.fastqc_html_1.html`. FastQC HTML report for read 1."
|
|
,
|
|
"default": "$id.$key.fastqc_html_1.html"
|
|
}
|
|
|
|
|
|
,
|
|
"fastqc_html_2": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.fastqc_html_2.html`. FastQC HTML report for read 2",
|
|
"help_text": "Type: `file`, default: `$id.$key.fastqc_html_2.html`. FastQC HTML report for read 2."
|
|
,
|
|
"default": "$id.$key.fastqc_html_2.html"
|
|
}
|
|
|
|
|
|
,
|
|
"fastqc_zip_1": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.fastqc_zip_1.zip`. FastQC report archive for read 1",
|
|
"help_text": "Type: `file`, default: `$id.$key.fastqc_zip_1.zip`. FastQC report archive for read 1."
|
|
,
|
|
"default": "$id.$key.fastqc_zip_1.zip"
|
|
}
|
|
|
|
|
|
,
|
|
"fastqc_zip_2": {
|
|
"type":
|
|
"string",
|
|
"description": "Type: `file`, default: `$id.$key.fastqc_zip_2.zip`. FastQC report archive for read 2",
|
|
"help_text": "Type: `file`, default: `$id.$key.fastqc_zip_2.zip`. FastQC report archive for read 2."
|
|
,
|
|
"default": "$id.$key.fastqc_zip_2.zip"
|
|
}
|
|
|
|
|
|
}
|
|
},
|
|
|
|
|
|
"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"
|
|
},
|
|
|
|
{
|
|
"$ref": "#/definitions/output"
|
|
},
|
|
|
|
{
|
|
"$ref": "#/definitions/nextflow input-output arguments"
|
|
}
|
|
]
|
|
}
|