Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to add id and label fields to all CWL's and tools #114

Open
stevekm opened this issue Aug 25, 2022 · 0 comments
Open

Need to add id and label fields to all CWL's and tools #114

stevekm opened this issue Aug 25, 2022 · 0 comments
Labels
revisit this later non-critical, non-breaking change to consider

Comments

@stevekm
Copy link
Member

stevekm commented Aug 25, 2022

All workflows, subworkflows, and CommandLineTool's (and other tools and workflow processes) should be tagged with labels like this;

vcf_to_maf:
    run:
        class: CommandLineTool
        id: vcf_to_maf
        label: vcf_to_maf

This will make the logs easier to parse in order to track the status of workflow tasks. Otherwise workflow tasks seem to be represent in logs with uninterpretable hash ID's that are largely impossible to trace back to any discernible CWL component. For some reason, both id and label fields are required, having only one of them does not propagate them into the logs.

These fields can be seen with the toil_track_utils.py script (https://github.com/mskcc/pluto/blob/master/toil_track_utils.py)

@svural svural added the revisit this later non-critical, non-breaking change to consider label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
revisit this later non-critical, non-breaking change to consider
Projects
None yet
Development

No branches or pull requests

2 participants