Jon Harper
Jon Harper
We should highlight the differences/possibilities between a busbreakerview of a nodebreakertopology voltagelevel and an equivalent voltagelevel described directly in busbreaker topology. For example, when an equipment has an open switch...
We should mention that in the busbreakertopology, the busbars from the nodebreakerview are still visible as equipments, it's a bit counterintutive (or maybe a feature ?)
sample code to improve: ```java System.out.println(); System.out.println(s1vl1.getTopologyKind()); if (s1vl1.getTopologyKind() == TopologyKind.NODE_BREAKER) { System.out.println("busbars: " + s1vl1.getNodeBreakerView().getBusbarSectionStream().toList()); } System.out.println("busbreakerviewbuses: " + s1vl1.getBusBreakerView().getBusStream().toList()); System.out.println("busviewbuses: " + s1vl1.getBusView().getBusStream().toList()); System.out.println("busviewbus -> busbreakerviewbus:" + s1vl1.getBusView().getBusStream().map(Bus::getId)...
see https://github.com/powsybl/powsybl-tutorials/blob/main/topology/src/main/java/com/powsybl/tutorials/topology/VoltageLevelTopologyTutorial.java
see https://powsybl.readthedocs.io/projects/powsybl-core/en/latest/grid_model/network_subnetwork.html (previously https://www.powsybl.org/pages/documentation/grid/model/ )
Hi, thanks for the quick reply. if it's not possible to automatically determine which contexts in the hierarchy have which mockbeans, then perhaps adding a parameter to @MockBean to manually...
Simplify handling of Instant and OffsetDateTime and remove incorrect/dubious comments about JDBC 4.2
If you want to proceed with this PR, please let me know how. For example I can create the HH-* jira issue if you want or let you do it...
Simplify handling of Instant and OffsetDateTime and remove incorrect/dubious comments about JDBC 4.2
Hi, I'm sorry if my message came as not humble, that's not what I meant at all. I was just trying to be succinct to make it easier for reviewers...
I would also like to be able to use SMPs on ConfigMapVolumeSource's items (should the bug be fixed upstream instead?)
/remove-lifecycle rotten