cylc cat-log has been renamed cylc log

I backed off on that PR for reasons I can't quite remember at the moment, should reconsider in the future, but for the mo it's still cat-log

https://github.com/cylc/cylc-flow/blob/76762bbfc1ca83be88ed8b0e0a7224e6af520964/setup.cfg#L152

Open for over a year. Branch in history and can be retrieved later.

...12 minutes later! I see no reason to close this as it's still valid. Just has dropped off people's radar?

I backed off on that PR for reasons I can't quite remember at the moment, should reconsider in the future

I backed off on that PR for reasons I can't quite remember at the moment, should reconsider in the future

That's unrelated, just in response to a resolved comment Hilary made above

Note: There were some offline discussions about how to integrate reload into the tutorial which weren't recorded on this ticket.

Following the training session the other day, I think we should consider bumping the "consolidating configuration" tutorial down the pecking order and develop a larger section about managing workflows, starting, stopping, reloading, vip, vr, etc.

@cylc/core - what's the status of this PR now (not sure if Oliver's last comment suggests not merging this as-is)

We have recently rebooted user training at our end and are developing some ideas about where we might take the main tutorial. Ideas include:

• Introducing clock triggers (this helps to solidify the understanding that the cycle point is just a label, only clock-triggers couple it to the real time).
• Introducing the cylc vip and cylc vr working patterns (by taking users through the process of fixing issues on the fly as part of the main tutorial path).
• Introducing basic runtime interventions (namely trigger, possibly edit runtime too).

In order to add things, we will have to remove things. We can't just pile on the concepts and still cram it into one day, so we may need to rejig things, especially the runtime tutorial. We could potentially merge the first two sections of the runtime tutorial as the first practical doesn't achieve much. We could also thin out the "consolidating configuration" part which is quite lengthy. Perhaps parameters might get bumped to the further topics section? We may need to do something with the date-time cycling section too as this has got quite long and is the hardest part.

We've not dropped this idea, but I think we may need a more coordinated approach to integrating it. We'll come back to it in time and let you know what we're thinking.