Hi everybody !

We have a planned TSC meeting on the 19^th of August. I know that many of you are in holiday, so I think that I am going to cancel this event. The next one will be in September, the 16^th.

Powsybl project has its TAC annual review on the 31^st of August. I am going to follow these requirements: Technical Project Lifecycle - LF Energy - LF Energy

All the other projects of the LFE will be present and could give advices, so maybe it will be interested to have one of you with me for more technical questions. Just let me know about it !

Thanks a lot and see you soon.

Best regards,

Anne

Hi everybody,

Our next TSC meeting will be on June 24^th.

For this public meeting, it would be great if we follow these items:

Release of powsybl-core (4.3.0-alpha-1) since May 25^th, please refer to the release notes to know what the release contains: Release v4.3.0-alpha-1 · powsybl/powsybl-core (github.com)

This intermediate release contains the new security analysis API, including the new feature that monitors the buses and branches results (voltage, angle, active and reactive powers) for pre-contingency state and for post-contingency states. We also support contingency on three windings transformers with this new version, and new limit violation types. OpenLoadFlow has been released too.

To be compliant with the European Merging Function, we can now maintain the power factor constant when loads are scaled. A tutorial is in progress to show how to implement the EMF with Powsybl.

And as usual, some bus fixes and other quality evolutions.

Next release of powsybl-core (4.3.0) expected on July 7^th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

New extension to model remote reactive power control for generators (breaking change) ;

A first version of the CGMES importer from a unique EQ file : it is a beta feature mainly used just after SCADA system ;

The possibility to export flows at switches in SV file ;

Still WIP:

- The new sensitivity API ;

- PSSE updated export ;

- Extensions for measurements compliant ;

- Support of CGMES 3.0 ;

- UCTE: use double instead of float. The extension MergedXNode will change too.

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR every month. Having a clear, detailed and updated roadmap is key for external contributions.

Technical discussion

Sylvain, Florian and Mathilde are working on a schematic vision of the network to provide SVGs. The SVGs could be integrated in an interface such GridStudy (gridsuite.org) or created from a python script by pypowsybl users (PyPowSyBl’s user documentation — pypowsybl documentation). They imagine that there is a JavaScript component that can be shared between these two applications. Sylvain is going to share some slides before our meeting.

Thanks for joining the TSC. Remember that meetings are scheduled here:

powsybl-tsc@... | Calendar

See you soon !

Anne

Some of you don’t have any invitation for tomorrow (yes, indeed it is on the 27^th of May). All our meetings are publicly in this calendar:

powsybl-tsc@... | Calendar

I have updated the meetings, so you have been notified. In the notification, you have an “invite.ics” that you can add to your outlook calendar or add it to all TSC members as I did minutes ago.

Sorry for that… but our calendar must remain public.

Anne

Hi everybody,

Our next TSC meeting will be on May 28^th.

For this public meeting, it would be great if we follow these items:

Release of powsybl-core (4.2.0) since May 25^th, please refer to the release notes to know what the release will contain: Release v4.2.0 · powsybl/powsybl-core (github.com)

Main features or bug fixes:

- CGMES import: consider transformer at boundary ;

- CGMES export: export flows for branches and three windings transformers ;

- CGMES: support of TYNDP CGM files with workarounds ;

- Make import of control areas optional ;

- CGMES: import of Xnode HVDC type for balances adjustment ;

- IIDM: improve network notification performance ;

- IIDM: fix connect bug ;

- IIDM: allow bPerSection to be negative ;

- PSSE: start of support DC conversion ;

- Scalable: add new DanglingLine scalable with both convention supported ;

- LoadFlow: add synchronous and connected numbers to results ;

- LoadFlow: add new parameters dcUseTransformerRatio, countriesToBalance and connectedComponentMode ;

- Triplestore: Blazegraph has been removed ;

Next release of powsybl-core (4.3.0) expected on July 7^th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

The new API of security analysis is ready, the implementations should adapt. WIP on OpenLoadFlow side. What about Dynawo? We plan to do an intermediate release for that breaking change.

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR before tomorrow. Having a clear, detailed and updated roadmap is key for external contributions.

Technical discussion

Free for the moment.

If you have subjects, do not hesitate to send it to me.

Thanks for joining the TSC.

Anne

Hi everybody,

Our next TSC meeting will be on May 28^th.

For this public meeting, it would be great if we follow these items:

Release of powsybl-core (4.2.0) since May 25^th, please refer to the release notes to know what the release will contain: Release v4.2.0 · powsybl/powsybl-core (github.com)

Main features or bug fixes:

- CGMES import: consider transformer at boundary ;

- CGMES export: export flows for branches and three windings transformers ;

- CGMES: support of TYNDP CGM files with workarounds ;

- Make import of control areas optional ;

- CGMES: import of Xnode HVDC type for balances adjustment ;

- IIDM: improve network notification performance ;

- IIDM: fix connect bug ;

- IIDM: allow bPerSection to be negative ;

- PSSE: start of support DC conversion ;

- Scalable: add new DanglingLine scalable with both convention supported ;

- LoadFlow: add synchronous and connected numbers to results ;

- LoadFlow: add new parameters dcUseTransformerRatio, countriesToBalance and connectedComponentMode ;

- Triplestore: Blazegraph has been removed ;

Next release of powsybl-core (4.3.0) expected on July 7^th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

The new API of security analysis is ready, the implementations should adapt. WIP on OpenLoadFlow side. What about Dynawo? We plan to do an intermediate release for that breaking change.

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR before tomorrow. Having a clear, detailed and updated roadmap is key for external contributions.

Technical discussion

Free for the moment.

If you have subjects, do not hesitate to send it to me.

Thanks for joining the TSC.

Anne

Hi TSC member,

Here are the results of the license scanning performed by the LFE: https://lfscanning.org/reports/lfenergy/powsybl-2021-04-20-ed46eeb7-b4a3-4f66-8266-e757e3fb0c46.xlsx

We miss some license headers and sometimes the author is missing too. I have fixed the powsybl-core java files, using the year of the first commit for the copyright. I am going to fix also the tutorials and the powsybl-open-loadflow repository. It remains the underlying files. Please open a PR on each repository with the changes requested. Note that this email only focus on Java source file.

Note that a preventive strategy could be to use the check REUSE https://github.com/marketplace/actions/reuse-compliance-check Who is volunteer to help on that subject if you all agree?

Thanks a lot.

Anne.

Hi everybody,

Our next TSC meeting will be on April 29^th.

For this public meeting, it would be great if we follow these items:

Release of powsybl-core (4.2.0) expected on May 20^th, please refer to the release notes to know what the release will contain: Release v4.2.0 (expected date: 2021-05-20) · powsybl/powsybl-core (github.com)

Main features or bug fixes: please refer to the draft release notes.

We except a version 4.1.2 for bug fixes tomorrow. The bug concerns the JSON serialization of Line and TwoWindingsTransformer contingencies.

Roadmap

For this TSC, I suggest to focus our roadmap on how growing our community (users + contributors)?

- Vattenfall for grid capacity estimation for DSO and TSO via PTDFs and LFs ; the methodology has to be defined and harmonized ; see slides attached.

- ACER: via pypowsybl, ACER is firstly interested in :

1) Calculation of zone-to-zone PTDFs for AC borders

2) Calculation of zone-to-zone PTDFs for DC borders/DC lines

3) Modification and creation of bidding-zones (e.g. shuffling nodes, e.g. for DK1)

- Control Room of the Future (Control Room of the Future - TenneT) : it is a working group inside the LFE. Powsybl could be used here.

- Other?

Technical discussion

I think that you all know that we pass the CII best Practices badge (BadgeApp (coreinfrastructure.org)) with 185%!

Key points must be underlined after reaching the first 100%:

- Documentation, especially in the web-site is a central subject ;

- Release candidates should be used for major release ;

- We have to focus on vulnerabilities (of the project itself and of its dependencies) ;

- Slack and official mailing lists must be used in priority ;

- Some committers must have a secure development knowledge (Secure Software Development Fundamentals Professional Certificate | edX)  + OWASP Top 10 ;

- Jars must be signed ;

- Dynamic code analysis: using Valgrind for the C++ analysis should become automatic + It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds.

Key points after reaching the last 85%:

- The project MUST document what the user can and cannot expect in terms of security from the software produced by the project ;

- The project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s) ;

- TODO: It is SUGGESTED that in the version control system, each important version tag (a tag that is part of a major release, minor release, or fixes publicly noted vulnerabilities) be cryptographically signed and verifiable as described in signed_releases ;

- Other security issues: the project MUST provide an assurance case that justifies why its security requirements are met. The assurance case MUST include: a description of the threat model, clear identification of trust boundaries, an argument that secure design principles have been applied, and an argument that common implementation security weaknesses have been countered : best-practices-badge/security.md at main · coreinfrastructure/best-practices-badge (github.com)

- Gold: double authentication in Github, not via SMS.

If you have subjects, do not hesitate to send it to me.

Thanks for joining the TSC.

Anne

Hi PowSyBl Community!

LF Energy’s Spring Summit is happening on April 14th.

Although we are not presenting this time, there is a great program including many topics connected to our works. Please take a look at the schedule (see in particular the power system operations and microservices tracks): https://events.linuxfoundation.org/lf-energy-spring-summit/program/schedule/

Here is the registration link: https://events.linuxfoundation.org/lf-energy-spring-summit/register/

I look forward to meeting you there,

Anne