Skip to content
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

specification class #2

Open
ivalab opened this issue Aug 13, 2016 · 0 comments
Open

specification class #2

ivalab opened this issue Aug 13, 2016 · 0 comments

Comments

@ivalab
Copy link
Collaborator

ivalab commented Aug 13, 2016

There are some commonalities with the cost and constraint classes, so it might be a good idea to incorporate some kind of specification class.

  • One problem is that the way the specifications work regarding computation of the gradient.
    • To compute the gradient, the system implicitly uses the variable names as gleaned from concatenated constraints.
    • Need to find where this happens and how to see if can modify.
    • In this search process, somehow only the variables actually used in the specification factor into the Tnames field and, consequently, into the gradient. How done?
  • Solution is most likely to encapsulate this within an optimal control problem class that is variable aware. It then provides the necessary info to the specifications as they are given.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants