Skip to content

Have ensureNonNegative() error instead of warn #365

Description

@Alomir

Currently, ensureNonNegative() throws a warning when the input variable is below zero (or, really, below -eps). When we have sufficient confidence in the model (which may be now, or at least once #359 goes in), we should convert this to an error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    on holdThis issue is not ready to be implemented

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions