The Seven Bridges Knowledge Center

The Seven Bridges Platform is a simple solution for doing bioinformatics at industrial scale. But sometimes, everyone needs a little help.

Get Started

Dynamic expressions in tool descriptions

📘

This page provides more details on how to use dynamics expressions in version 1.0 of the Common Workflow Language. If you are describing a tool using the sbg:draft-2 version of CWL, please see this page for details.

The tool editor allows you to describe the features and behavior of your command line tool. The resulting description is used to create an interface between your tool and other tools that can be run on the Platform.

If your tool has a certain behavior, controlled by a command line option argument, that you don't want to ever vary with executions, you can 'hard code' this into the tool description. On the other hand, if you want to chose the argument every time you run the tool, you can manually input it with each execution. But, in many cases, a middle way is more appropriate: although the required argument will vary with executions, it should do so in a deterministic way, dependent on other features of the tool execution.

To achieve this behavior, you can hard code the argument using a dynamic expression in your tool description, rather than a literal. It can be expressed in terms of the inputs, outputs, or other aspects of a tool execution; the object that the expression refers to will then be determined at runtime on the basis of the values of these other objects.

Using dynamic expressions

Dynamic expressions are given in Javascript. You can enter a dynamic expression anywhere in the tool editor where you find the symbol </>. For example, you could enter the Javascript expression 1+2, or a function body such as ${return 1+2}.

Places where you might want to use dynamic expressions include:

  • Specifying the command options for your tool. Options related to tool inputs are set in the Input ports section, and others are set in the Arguments section.
  • Specifying stdin and stdout.
  • Setting the resources allocated to your tool (memory and CPU number).
  • Setting up the glob pattern to catch outputs, in the Output ports section.
  • Specifying secondary files for inputs and outputs.
  • Specifying files available in the working directory prior to command execution.

Predefined Javascript objects

Some Javascript objects have been defined in the scope of the tool execution, and are available for you to use in dynamic expressions to increase their expressivity. The inputs, self and runtime objects denote properties of the ongoing tool execution (the job), and the tool's inputs or outputs in a given execution. They are described below.


The inputs object

This is an object that denotes the inputs for the tool. Remember that tool inputs include files and parameters. The inputs object has the properties <input_id> and <input_value>.

<input_id> is the ID that you have labeled each input port with in the tool editor.

<input_value> refers to the object that is entered into the port named <input_id>. It is set according to the following rule, illustrated in the table below: If the object entered into the port named <input_id> is any data type other than a file, then <input_value> is the object itself. If the object entered into the port <input_id> is a file, then <input_value> is four objects that describe, and uniquely determine, the file.

Data type input to the port named <input_id>

<input_value>

File

The following four objects are the input_value:

  • class: this is always 'File'
  • secondaryFiles: this is a list of secondary files (index files) attached to the file. It may be empty.
  • path: this is the file path.
  • basename: this is the file name (e.g. filename.bam).
  • nameroot: this is part of the file name before the last '.' character in the name (e.g. filename).
  • nameext: this is the extension of the file (e.g. .bam).
  • size: this is the file size.

String

The string entered to the input port.

Enum

The enumerator of the enumerated type that is entered to the input port labeled by <input_id>

Int

The integer entered to this input port.

Float

The float entered to this input port.

Boolean

The boolean value entered to this input port.

Array

The array entered to this input port.

Inspecting the inputs object

The objects in <input_value> are defined at runtime, depending on which strings, ints, files, and so on are inputted to the tool.

To see the inputs object for your tool description and test values:

  1. Click the ... icon in the top right hand corner
  2. Select Export (YAML format).

A file in YAML format will be downloaded. The file contains the entire CWL code of the app, including the defined input ports within the inputs object.

In order to get a better understanding of what input_id and input_value denote, let's create a tool description in the editor that has input ports for different selected data types, and then view the inputs.

Examples of inputs usage

Earlier, we listed fields in which you may want to use the inputs object in dynamic expressions. Here are a few examples:

  • You may need to set the tool's required memory to be a function of the size of the inputted file. In this case, you can use the object inputs.<input_id>.size to pick out the size of the file inputted to the port <input_id>.
  • You can use inputs to perform linking input files to the current working directory of the job. To do that, you will need to specify: (a) the file name and (b) the file to be copied/linked.
    • (a) The file name for the file input to the tool is obtained from the basename property of the <input_id> object for the input port that takes files. The name of the input file is $(inputs.<input_id>.basename).
    • (b) The file itself is obtained from <input_id>, for the input port that takes files. Use: inputs.<input_id>.

The self object

The self object is used to modify the value of the input or output that gets passed to the command line.

  • In the command line bindings for the tool inputs, self is set to the value of the input. In other words, in this context self is just inputs.<input_id>.
  • In the command line bindings for the tool outputs, self is an object with the properties path and size that match the globbed file (see here for more information on globbing).

Examples of self usage

Here are a few examples of how you can use the self object:

self in the Input ports section:

  • Use self for string manipulation. Suppose that your tool takes input files that are entered on the command line, but expects these to be given as filenames, not as file paths. Since self refers to the tool input, in the case that files are the input type, self will refer to a full file path. By performing string manipulation on this file path, using self.basename, you can extract the filename. Then, enter this as the input value to the tool.
  • Another use case for self is to manipulate an integer input. Suppose that your tool expects integer inputs in exponent notation, but inputs are given as integers. In this case, self will refer to the integer inputted, and you can use an expression in terms of self in the Inputs value field to give the integer in its exponent representation.

self in the Outputs ports section

  • In addition to using self to refer to a tool's inputs, you can use self.path in the Output Ports section to specify to the path of the file matching the glob pattern. You might want to annotate output files with the metadata field 'file type', whose value depends on the particular extension of the file being output by the tool. In this case, set the metadata key to file_type and set the value to the Javascript expression self.path.split('.').slice(-1)[0] to refer to the part of the file path after the dot, i.e. the extension.

The runtime object

It is an object with properties related to the running environment. More details are explained in the Common Workflow Language specification.

Updated 10 months ago

Dynamic expressions in tool descriptions


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.