feature/update main model for automatic tap changer

[Jerry-Jinfeng-Guo]

• [ ] Update main_core/output → function skeletons are already in place (main_core.hpp and output.hpp). User will need to be able to extract certain data (tap positions, etc.).
• [ ] Attribute input should be checked (should have been in place)
• [ ] attr output (optimizer >all the way back> output structure) needs to be done
• [x] add check to ensure that there can at most be one regulator for each transformer
• [ ] include unit tests for the input/update/output functions of automatic tap changer.

[Jerry-Jinfeng-Guo]

At the moment the tap_position_optimizer still writes everything to a SolverOutput. The addition of MathOutput to include both SolverOutput and OptimizerOutput seems ignored. @mgovers Could the automatic tap changer adapt before I continue?

[mgovers]

At the moment the tap_position_optimizer still writes everything to a SolverOutput. The addition of MathOutput to include both SolverOutput and OptimizerOutput seems ignored. @mgovers Could the automatic tap changer adapt before I continue?

Yes the optimizer needs to output a MathSolver that includes both the SolverOutput and the OptimizerOutput if that is waht you mean

[sonarqubecloud[bot]]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
98.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud