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

Improve flow.cylc reference docs #4846

Merged
merged 4 commits into from
May 3, 2022
Merged

Improve flow.cylc reference docs #4846

merged 4 commits into from
May 3, 2022

Conversation

MetRonnie
Copy link
Member

This is a small change with no associated Issue.

Requirements check-list

  • I have read CONTRIBUTING.md and added my name as a Code Contributor.
  • Contains logically grouped changes (else tidy your branch by rebase).
  • Does not contain off-topic changes (use other PRs for other changes).
  • Applied any dependency changes to both setup.cfg and conda-environment.yml.
  • Does not need tests
  • No change log entry required (docs/invisible to users).
  • No cylc-doc PR needed.

@MetRonnie MetRonnie added the doc Documentation label May 3, 2022
@MetRonnie MetRonnie added this to the cylc-8.0rc4 milestone May 3, 2022
@MetRonnie MetRonnie requested a review from wxtim May 3, 2022 11:15
@MetRonnie MetRonnie self-assigned this May 3, 2022
Copy link
Member

@wxtim wxtim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Jotted some thoughts down.
  • Built docs locally.

Comment on lines 179 to 180
If ``True``, the workflow will use UTC as the time zone for
cycle points and timestamps in the logs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possible alt, take or leave.

Suggested change
If ``True``, the workflow will use UTC as the time zone for
cycle points and timestamps in the logs.
If ``True``, the workflow logs will use UTC as the time zone for
cycle points and timestamps.
If ``False`` System time will be used.

Copy link
Member Author

@MetRonnie MetRonnie May 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually when I think about it, UTC mode only affects the log timestamps ever since #4457. Updated this description accordingly


If instead you only want to set a time zone for cycle points,
leaving log timestamps to use the local/system time zone,
see :cylc:conf:`flow.cylc[scheduler]cycle point time zone`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
see :cylc:conf:`flow.cylc[scheduler]cycle point time zone`.
see :cylc:conf:`flow.cylc[scheduler]cycle point time zone`.
(`cycle point time zone` defaults to UTC.)

this to ``False``.
.. admonition:: Cylc 7 compatibility mode

In :ref:`Cylc_7_compat_mode`, implicit tasks are still
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have I missed a discussion about this?
There's a slight inconsistency in that I thought that we were going to allow implicit tasks in compatibility mode, unless a rose-suite.conf is present (since Rose 2019 had behaviour equivalent to implicit tasks = False).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, that was never updated in the docs

@hjoliver hjoliver merged commit ccdfc19 into cylc:master May 3, 2022
@MetRonnie MetRonnie modified the milestones: cylc-8.0rc4, cylc-8.0rc3 May 4, 2022
@MetRonnie MetRonnie deleted the doc branch May 4, 2022 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants