Skip to content

traceback for invalid initial cycle point #7390

Description

@oliver-sanders

Some invalid initial cycle point values are resulting in tracebacks rather than clean error messages.

(low priority)

Example which triggers a ValueError:

[scheduling]
    initial cycle point = T, T
    [[graph]]
        R1 = foo

[runtime]
    [[foo]]

And another which triggers the same issue:

    initial cycle point = T00, T18

Metadata

Metadata

Assignees

No one assigned

    Labels

    could be betterNot exactly a bug, but not ideal.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions