Skip to content

Ramp_up_limit / Start_up_limit fails when ramp_up_limit is a timeseries #1322

@DillonJ

Description

@DillonJ

We have a model failing in latest SpineOpt due to Ramp Up limit being a time series so the comparison with start_up_limit fails with

ERROR: LoadError: MethodError: no method matching isless(::SpineInterface.TimeSeries{Float64}, ::SpineInterface.TimeSeries{Float64})
The function `isless` exists, but no method is defined for this combination of argument types.

I think we should revert this commit until it's more robust and downgrade it to a warning.

Ramp_up_limit / Start_up_limit fails when ramp_up_limit is a timeseries

Another option would be to have a run_spineopt() keyword arguments that enables data warnings as errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type: bugSomething isn't working as expected

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions