Skip to content

tspan argument should be checked to be a proper time interval #732

@schillic

Description

@schillic

Passing tspan=(1., 0.) to solve should throw an error instead of computing a normal-looking but invalid result.

EDIT: According to the documentation, this is actually allowed. But I think at least the TMJets algorithm does not support this properly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions