Document expected output of dummy workflows

[SJaffa]

matflow-user-documentation/README.md

Lines 17 to 19 in efda0e5

	matflow go hello.yaml
	matflow go groups.yaml
	matflow go advanced_workflow.yaml

We can verify if all tasks ran successfully using matflow show --no-update --full (add --legend to see explanation of status symbols), but what output files should be produced and what should they contain? For the beginners tutorial, where should we direct people to see the results and confirm that they match that tasks specified?

I get an output fiolder called groups_YYY-MM-DD_timestamp containing:

.
├── artifacts
│   ├── groups.yaml
│   ├── submissions
│   │   └── 0
│   │       ├── app_std
│   │       ├── commands
│   │       │   ├── 0.sh
│   │       │   ├── 1.sh
│   │       │   └── 2.sh
│   │       ├── jobscripts
│   │       │   └── js_0.sh
│   │       ├── js_funcs
│   │       │   └── js_funcs_0.sh
│   │       ├── js_run_ids
│   │       │   └── js_0_EAR_IDs.txt
│   │       ├── js_std
│   │       │   └── 0
│   │       │       └── js_0_std.log
│   │       ├── scripts
│   │       └── tmp
│   └── tasks
├── execute
├── metadata
│   ├── elements
│   │   └── 0
│   ├── iters
│   │   └── 0
│   ├── run_dirs
│   ├── runs
│   │   └── 0
│   │       ├── 0
│   │       ├── 1
│   │       └── 2
│   ├── submissions
│   │   └── 0
│   │       ├── js_at_submit_md
│   │       │   └── 0
│   │       ├── js_deps
│   │       │   └── 0
│   │       ├── js_run_IDs
│   │       │   └── 0
│   │       │       └── 0
│   │       │           └── 0
│   │       ├── js_task_acts
│   │       │   └── 0
│   │       │       └── 0
│   │       └── js_task_elems
│   │           └── 0
│   │               └── 0
│   │                   └── 0
│   └── tasks
│       ├── 0
│       └── 1
└── parameters
    ├── arrays
    ├── base
    │   ├── 0
    │   ├── 1
    │   ├── 2
    │   ├── 3
    │   ├── 4
    │   ├── 5
    │   ├── 6
    │   └── 7
    └── sources
        └── 0

[gcapes]

The output from the groups example all goes to stdout, which is now at artifacts/submissions/0/js_std/0/js_0_std.log. It would probably help to update the output text to be slightly more verbose. I'll do that now.

[gcapes]

Scratch that - turns out I don't know how to do that 😆

[SJaffa]

PR in the shared docs repo: hpcflow/hpcflow-shared-docs#11
Explained the folders produced and where to look for results, logs & errors.

Waiting for Adam to review.

[SJaffa]

Closed by hpcflow/hpcflow-shared-docs#11