Update Hycon hybrid supervisory controller architecture to handle general components

[misi9170]

This PR adds a new controller, HybridSupervisoryControllerGeneric (name possibly to change), that supersedes both HybridSupervisoryControllerBaseline and HybridSupervisoryControllerMultiRef. This supervisor can have arbitrary component controllers assigned to it, and curtails them in a user-specified order when satisfying a grid interconnection limit or power reference tracking target. The control of the individual components (e.g. profit maximizing, power tracking) is handled by the individual component controllers.

This PR is a work in progress. Once complete, this should supersede #99 , and address the following issues: #98 , #60, and possibly #62.

This PR does include breaking changes. I intend to release a new version of Hycon (v0.8) once it has been merged (and has been on develop for some time to identify any issues).

To do:

• Update controller and ensure existing examples run as expected
• Tests pass
• Include desired behavior from Port over hyconx controllers #99
• Remove deprecated HybridSupervisoryControllerBaseline and HybridSupervisoryControllerMultiRef controllers
• Add test for new controller (reference tracking)
• Add test for new controller (individual controls sharing interconnection)
• Address Establish unified way of passing controller parameters from either input file or as dictionary #60 , create approach for checking and setting controller parameters, remove controller_parameters from interface (?)
• Remove input_dict
• Update documentation
• Generate new example output figures for docs
• Check and update docstrings across all controllers.
• Consider addressing Feature request: Forced outage override #101 (or work on this in a separate PR) Decided to leave this for a later PR

[misi9170]

@paulf81 I've marked this ready for review. I'm not expecting an actual review here, since this is such a major overhaul that I think the best approach will be to merge it and let it sit on develop a while to iron out any bugs. However, I know you are going to use this a bit today, so I'll let you do that before I merge it just in case there are some obvious bugs that come up.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 39 out of 42 changed files in this pull request and generated 9 comments.

Comments suppressed due to low confidence (3)

hycon/interfaces/hercules_v1_interface.py:1

• The nested controls schema elsewhere uses controls_dict[\"battery\"][\"power_setpoint\"], but this code looks up battery_power_setpoint, so battery commands will silently default to 0.0. Change this to read power_setpoint (and keep naming consistent with the rest of the interfaces/controllers).
  tests/battery_controllers_test.py:1
• These np.isclose(...) checks are missing assert, so the test will pass even if the computed setpoints are wrong. Change these to assert np.isclose(...) to actually validate the behavior.
  hycon/interfaces/hercules_v1_interface.py:1
• The v1 check_controls() no longer validates that turbine-indexed controls (e.g., yaw_angles / power_setpoint) have length n_turbines. Since send_controls() assumes correct lengths, restoring length validation would prevent hard-to-debug runtime shape issues and aligns with the previous safety checks.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.