Add Example Tool Demonstrating Fictitious Platform Extensions about common-workflow-language HOT 5 CLOSED

I'm not sure what you mean by "Runtime modifications to the command-line". Can you give an example?

For UI hints and custom metadata I'd suggest something like this:

class: CommandLineTool
galaxy:toolbox_categories: [NGS, Aligners]
galaxy:process_version_cmd: "mytool --version"
inputs:
  - id: "#text"
    type: "string"
    galaxy:form_element: textbox
# ...

from common-workflow-language.

For UI hints, we are using tag "help". in our case it is a string with Markup language.
What do you mean under Tool-Level metadata?

Also, we are using amount of CPU cores for tool. As an example some tools can use only one core and other any amount of cores. Specifying amount of cores can improve a scheduling and balancing on cluster.

from common-workflow-language.

What do you mean under Tool-Level metadata?

The toolbox_categories and process_version_cmd above - custom key-value pairs added to the tool itself (rather than to e.g. individual inputs).

Also, we are using amount of CPU cores for tool. As an example some tools can use only one core and other any amount of cores. Specifying amount of cores can improve a scheduling and balancing on cluster.

Both drafts already have this (it's the CPURequirement in draft-2).

from common-workflow-language.

@jmchilton Are you suggesting that we add the requested examples to the conformance tests or to the user guide?

If to the user guide then it would be nice if they were actually used by Galaxy/Planemo

from common-workflow-language.

Done: https://github.com/common-workflow-language/common-workflow-language/blob/master/v1.0/v1.0/cat5-tool.cwl#L10

from common-workflow-language.