Anton Edvinovich Pozharskiy
Anton Edvinovich Pozharskiy
Currently all constraints in `nosnoc.model.base.g_path` are either evaluated on control stage boundaries, finite element boundaries, and/or rk stages uniformly. This can in some cases cause duplicate constraints. As a result...
Rework how we slice the step equilibration options. Particularly with the introduction of relaxation mode support in `vdx` we can perhaps build the step equilibration out of several building blocks.
The current interface for `mpccsol` is designed to be similar to `nlpsol` i.e. `mpccsol(solver_name, plugin, problem, options)`. In its current state we only support `nosnoc.solver.MpccSolver` as a backend for `mpccsol`...
Combine `use_speed_of_time_variables` and `local_speed_of_time_variable` into `SpeedOfTimeMode` with entries `NONE, LOCAL, GLOBAL`
For classes with lots of properties (for example the [`Options` class in nosnoc](https://nosnoc.readthedocs.io/en/latest/options.html#nosnoc.Options)) it would be nice to section the properties for better readability. One approach to doing this would...