-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add parameters, fix terminal cost, add bounds on x #12
Conversation
# either provide single parameter vector | ||
p_val = np.concatenate((np.array([1.0, 0.1]), x_ref_val)) | ||
# or matrix (one parameter vector for each control stage) | ||
p_val = np.tile(p_val, (opts.N_stages, 1)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to copy the parameter values over all stages manually?
After some thinking, I would still prefer say p_global_val, p_time_var_val
and p_global
and p_time_var
over p
(and, of course, put them together and copy the values in the solver construction)
The comment above is my only concern. Otherwise, LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing that can definitely be handled later, otherwise LGTM. If Armin's comment is addressed probably good to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love it 🥇
No description provided.