nf-core/epitopeprediction
A bioinformatics best-practice analysis pipeline for epitope prediction and annotation
Define where the pipeline should find input data and save output data.
Path to comma-separated file containing information about the samples in the experiment.
stringThe output directory where the results will be saved. You have to use absolute paths to storage on Cloud infrastructure.
stringEmail address for completion summary.
string^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$MultiQC report title. Printed as page header, used for filename if not otherwise specified.
stringOptions for the genome and proteome reference.
Specifies the Ensembl genome reference version that will be used.
stringgrch37Specifies the reference proteome fasta file that is used for self-filtering peptides derived from provided genomic variants.
stringOptions for the peptide prediction step.
Specifies the column name in the input file that contains the peptide sequences.
stringsequenceSpecifies the minimum peptide length.
integer8Specifies the maximum peptide length.
integer12Specifies the minimum peptide length for MHC class II peptides.
integer8Specifies the maximum peptide length for MHC class II peptides.
integer25Specifies the prediction tool(s) to use.
stringmhcnuggetsSpecifies whether wild-type sequences should be predicted.
booleanSpecifies that sequences of proteins, affected by provided variants, will be written to a FASTA file.
booleanSpecifies that the output file will be in wide format.
booleanOptions for optimising the pipeline run execution.
Split VCF file into multiple files by number of variants.
booleanNumber of variants that should be written into one file. Default: number of variants divided by ten
integerNumber of nucleotides between previous and current variant across split.
integer110000Specifies the maximum number of peptide chunks.
integer100Specifies the minimum number of peptides that should be written into one chunk.
integer5000External MHC binding prediction software that is not shipped with the pipeline.
Specifies the path to the JSON file with meta information on external prediction tools.
stringSpecifies the operating system in use (Linux or Darwin). This is only necessary if conda is used.
stringTo use the ‘netmhcpan’ tool, specify the path to the original software tarball for NetMHCpan 4.0 here.
string^\S+\.tar\.gz$To use the ‘netmhciipan’ tool, specify the path to the original software tarball for NetMHCIIpan 3.1 here.
string^\S+\.tar\.gz$Parameters used to describe centralised config profiles. These should not be edited.
Git commit id for Institutional configs.
stringmasterBase directory for Institutional configs.
stringhttps://raw.githubusercontent.com/nf-core/configs/masterInstitutional config name.
stringInstitutional config description.
stringInstitutional config contact information.
stringInstitutional config URL link.
stringLess common options for the pipeline, typically set in a config file.
Display version and exit.
booleanMethod used to save pipeline results to output directory.
stringEmail address for completion summary, only when pipeline fails.
string^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$Send plain-text email instead of HTML.
booleanFile size limit when attaching MultiQC reports to summary emails.
string25.MB^\d+(\.\d+)?\.?\s*(K|M|G|T)?B$Do not use coloured log outputs.
booleanIncoming hook URL for messaging service
stringCustom config file to supply to MultiQC.
stringCustom logo file to supply to MultiQC. File name must also be set in the MultiQC config file
stringCustom MultiQC yaml file containing HTML including a methods description.
stringBoolean whether to validate parameters against the schema at runtime
booleantrueBase URL or local path to location of pipeline test dataset files
stringhttps://raw.githubusercontent.com/nf-core/test-datasets/Suffix to add to the trace report filename. Default is the date and time in the format yyyy-MM-dd_HH-mm-ss.
string