In Cylc7 the title configuration was moved into a [meta] section. When we move a configuration we deprecate the old one, when you validate a suite using Cylc7 you should see a message like this:
WARNING - * (7.5.0) [runtime][A][title] -> [runtime][A][meta][title] - value unchanged
Deprecated settings will continue to be supported for the life of the major release (so Cylc7 in this case) after which they will be dropped.
The fixed suite should look something like this:
[meta]
title = “A/B suite”
description = “A/B suite”
[cylc]
UTC mode = True
[scheduling]
initial cycle point = 20191007T1200
final cycle point = 20191008T0300
[[special tasks]]
clock-trigger = A(PT0M)
[[dependencies]]
[[[PT30M]]]
graph = A[-PT30M] => A => B
[runtime]
[[root]]
env-script = """
export JOB_DIR=$HOME
"""
[[A]]
script = """
$JOB_DIR/A.pl
"""
[[[meta]]]
title = "A"
description = "A"
[[B]]
script = """
$JOB_DIR/B.s
"""
[[[meta]]]
title = "B"
description = "B"
Sorry for your trouble! As you might infer from what @oliver.sanders wrote, we sometimes need to deprecate aspects of the workflow configuration as we continually improve the system (in this case title and description were originally the only metadata items allowed; now you can have arbitrary metadata under the [meta] section).
To deal with this, I suggest in future you:
take notice of deprecation warnings and upgrade your configurations before the items become obsolete
at cylc-7, validation tells you that title title is deprecated and should be [meta]title
if you do hit an obsolete item - which is essentially just an error/illegal-item - the error message should tell you exactly what is wrong:
(then, search for title in the user guide and you’ll find that it should be under [meta]).
@oliver.sanders forgot to upgrade some syntax deprecated (but not obsoleted) at cylc-8. As the validation warning says, the workflow graph should now be written more simply like this:
[scheduling]
...
[[graph]]
PT30M = "A[-PT30M] => A => B"
Yes, I’m sure the Cylc 8 User Guide would have helped you there (coming soon…)
Note sure what you mean here? The quotes around graph strings - as for any single line config item values - are optional, but I like to use them as it helps to make clear that the entire thing is a single string value (whose meaning is determined internally by Cylc, not by the basic config file parser).