Skip to content
This repository was archived by the owner on Feb 27, 2025. It is now read-only.
This repository was archived by the owner on Feb 27, 2025. It is now read-only.

Findability of workflow output #21

@GernotMaier

Description

@GernotMaier

Workflow output consist of

  • derived and validated model parameter (usually one file)
  • associated metadata
  • additional output from the validation or derivation step (e.g., plots and log files)

How do we find these outputs?

The cwltool has a --write-summary options, which lists all derived output files. e.g.

{
    "parameter_derived": {
        "location": "file:///Users/maierg/DESYCloud/CTA/Pipelines/MC-Pipeline/gammasim-tools/workflows/workflows/tt/297d980d-145f-4c6e-90c1-1037b27de129-submit_data_from_external.ecsv",
        "basename": "297d980d-145f-4c6e-90c1-1037b27de129-submit_data_from_external.ecsv",
        "class": "File",
        "checksum": "sha1$5cc99308e90b1b915e35940a1fa4cd9617cf0ba4",
        "size": 2692,
        "path": "/Users/maierg/DESYCloud/CTA/Pipelines/MC-Pipeline/gammasim-tools/workflows/workflows/tt/297d980d-145f-4c6e-90c1-1037b27de129-submit_data_from_external.ecsv"
    },
  "meta_data": {
 ....

Not sure if all CWL implementation provide such options. This issue should remind us of the problem. Above json schema could also be implemented in the ModelDataWriter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions