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

[Moco] Create interface for user-defined InputControllers #3698

Closed
nickbianco opened this issue Feb 6, 2024 · 0 comments
Closed

[Moco] Create interface for user-defined InputControllers #3698

nickbianco opened this issue Feb 6, 2024 · 0 comments
Assignees
Labels
Moco This label identifies bugs or desired features to aid Moco development

Comments

@nickbianco
Copy link
Member

nickbianco commented Feb 6, 2024

Addressing issue #3605 will introduce the notion of an InputController, which will enable controllers driven by inputs from OCP controls. This new functionality will introduce new complexities in defining, solving, and returning solutions for MocoStudys. The following considerations will need to be addressed:

  • How will bounds from setControlInfo() be obeyed when the model control is no longer an OCP control?
  • How will users set bounds on Input controls (e.g., setInputInfo())?
  • Should we allow users to add OCP controls on top of model controls produced by controllers?
  • What do we return in a MocoSolution? Both the Input values and the model control values?

Link to planning doc.

@nickbianco nickbianco added the Moco This label identifies bugs or desired features to aid Moco development label Feb 6, 2024
@nickbianco nickbianco self-assigned this Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Moco This label identifies bugs or desired features to aid Moco development
Projects
None yet
Development

No branches or pull requests

1 participant