Skip to content

Easy way to determine constraints and/or variables leading to failed solving? #2185

@lfreese

Description

@lfreese

Hi,

I'm solving an optimization over time (1 year by hour, so 8759 runs of the model) by submitting it to a slurm, and during a given number of my timesteps (5001-6000), I get:
Parallel mode: deterministic, using up to 32 threads for concurrent optimization. Row 'c1' infeasible, all entries at implied bounds. Presolve time = 11.16 sec. (3193.35 ticks) ERROR: LoadError: The model was not solved correctly.

I'm wondering if there is a simple way within JuMP to figure out what constraints or variables is causing the inability to solve the model (eg: what timestep, which of my 4 constraints)?

I've looked at the documentation and haven't found something that would specifically work in the context of slurm submissions, but might be mistaken.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions