tags

When submitting workflows via the run_cloud command, tags are 'labels' that help control which workers are allowed to pick up and run the submitted workflow. Workers should be started with matching tags in order for these scheduled flows to run.

When no tags are set, the following default tags will be used for a Simmate workflow:

• simmate (this is the default worker tag as well)
• the workflow's type name
• the workflow's app name
• the full workflow name

For example, the static-energy.vasp.matproj would have the following tags:

- simmate
- static-energy
- vasp
- static-energy.vasp.matproj

To override these default tags, use the following:

yamltomlpython

tags:
    - my-tag-01
    - my-tag-02

tags = ["my-tag-01", "my-tag-02"]

tags = ["my-tag-01", "my-tag-02"]

Warning

When you have a workflow that is submitting many smaller workflows (such as structure-prediction workflows), make sure you set the tags in the subworkflow_kwargs settings:

subworkflow_kwargs:
    tags:
        - my-tag-01
        - my-tag-02

Bug

Filtering tags does not always work as expected in SQLite3 because a worker with my-tag will incorrectly grab jobs like my-tag-01 and my-tag-02. This issue is known by both Django and SQLite3. Simmate addresses this issue by requiring all tags to be 7 characters long AND fully lowercase when using SQLite3.