Pierre Martinon

Small update: in the latest version only the adjoints are retrieved, other multipliers are skipped. Putting them back is easy since the previous code is still there. While we're at...

By the way we probably want to retrieve the different constraints as well (parsing is the same so there is no extra effort). So maybe something like this, to keep...

Ok, in the solution parsing I can sort the different kinds of constraints and their associated multipliers, then interpolate the functions as we already do for the state and control...

@jbcaillau Do you still have the error with option `adnlp_backend=:default` added to the solve call ?

@ocots @jbcaillau More related maybe to the GPU case, but we can use different test sets by passing arguments to the runtest action in the workflow yaml file (here `Moonshot.yml`):...

We can import to OptimalControl the tests in https://github.com/control-toolbox/CTDirect.jl/blob/main/test/suite/test_exa.jl These are CPU, not GPU, and can run normally with the other tests, provided the correct dependencies are added. There are...

Many solvers can handle a callback function called at each iteration, we may try to use this to plot the current iterate ?