Date   

Next TSC meeting

TILLOY Anne
 

Hi everybody,

 

Our next TSC meeting will be on September the 15th, 13h30, on Teams: Cliquez ici pour participer à la réunion

 

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

 

Next release is for today. This release of powsybl-core 4.10.0 contains:

 

-          [IIDM] limit getters return optionals. It is a breaking change.

-          [IIDM] the SLD extensions are moved to powsybl-core.

-          [IIDM] parameters are moved to commons.

-          [IIDM] allow to serialize false as redundancy.

-          [Modification] create bay feeder and create branch feeders. Add utility methods to retrieve the connectable order positions.

-          [Modification] transform a tee point into a switching voltage level.

-          [Modification] renaming attach to createLineOnLine and connectVoltageLevelOnLine.

-          [Conversion] importer and exporter refactoring.

-          [CGMES] many improvements, see release notes Releases · powsybl/powsybl-core (github.com)

-          [PowerFactory] improvements, see release notes Releases · powsybl/powsybl-core (github.com)

-          [Short-circuit] clean and refactoring.

-          [Security analysis] a first beta version of the security analysis API with remedial action + switch action + line connection action and phase tap changer tap position action.

-          [Sensitivity analysis] add contingency status in the result.

-          [Sensitivity analysis] support of three windings transformer as functions and variable.

-          + quality

 

Release train 1.3.0, based on powsybl-core 4.10.0

 

-          OLF, SLD, NAD, Dynawo, balances ajustement and entsoe expected next week, release train expected next week too.

 

Other repositories:

-          Florian: single line diagram and network area diagram.

-          Sylvain: pypowsybl.

-          OLF:

Support of shunt compensator G

Introduce plausible target voltage parameters

New GraphConnectivity API

Support of dangling line as function reference in sensitivity analysis

[Excepted] Support of switch contingency in sensitivity analysis.

[WIP] Work on generators connected to the same bus but controlling two different buses -> change the exception by a warning first.

-          powsybl/powsybl-starter (github.com)

-          powsybl/powsybl-benchmark (github.com)

-          IIDM C++, no release for the moment, still supporting until IIDM 1.5.0, WIP.

-          WIP: non regression testing

-          ENTSOE: flow decomposition following ACER methodology.

-          Dynawo: redesign.

 

Roadmap:

-          IIDM: Sets of operational limits. We found limitations in using private extension currentLimitsPerSeason and properties.

-          IIDM: modeling of protections.

-          Time series : benchmarks on time scale DB ;

-          Network modifications: creation of voltage level from scratch.

-          Increasing the shortcircuits API: REX after models integration and work around parameters

-          TODO: fusion of balances-ajustement and powsybl-enstoe?

-          TODO: we are late about documentation.

-          Multi component results for security analysis API.

-          The support of EMF in pypowsybl

-          Other subjects?

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

powsybl-tsc@... | Calendar

 

See you soon !

 

Anne

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


TSC meeting

TILLOY Anne
 

Hi everybody,
 
I have decided to switch to Teams for this regular meeting.
Thanks for understanding.
 
++
 
Anne
 
________________________________________________________________________________
Réunion Microsoft Teams
Rejoindre sur votre ordinateur ou application mobile
Rejoindre avec un appareil de vidéoconférence
ID de vidéoconférence : 126 318 204 3
________________________________________________________________________________
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Now: TSC meeting - 08/25/2022 #cal-notice

Group Notification <noreply@...>
 

TSC meeting

When:
08/25/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Event: TSC meeting - 08/25/2022 #cal-reminder

Group Notification <noreply@...>
 

Reminder: TSC meeting

When:
08/25/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Annulé: TSC meeting

TILLOY Anne
 

Hi everybody,
 
I have decided to switch to Teams for this regular meeting.
Thanks for understanding.
 
++
 
Anne
 
________________________________________________________________________________
Réunion Microsoft Teams
Rejoindre sur votre ordinateur ou application mobile
Rejoindre avec un appareil de vidéoconférence
ID de vidéoconférence : 126 318 204 3
________________________________________________________________________________
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Next release

TILLOY Anne
 

Hi everybody,

 

I hope you are all fine and that you envoy your vacation. I have to cancel the TSC meeting because many committers are out of the office today.

 

In order to prepare the back-to-work, just some relevant information :

 

-          Next release of powsybl-core will be on September the 14th. The release train should follow. We already have an alpha-1 release, but a release candidate will be published one week before.

-          In order to be ready, there are some pending PRs. If I miss some important features or bug fixes, just tell me.

 

In the Pull requests · powsybl/powsybl-core (github.com) of powsybl-core, the next-release PRs to be finished, reviewed and merged are :

 

-          There is an issue with the CGMES import because SequenceNumber is optional but strongly recommended in Europe. So we have decided to rely on it, but it leads to issues for American CGMES files. Miora has started to try to find a solution that preserves performance : [WIP] SequenceNumber can be optional in CGMES import by miovd · Pull Request #2241 · powsybl/powsybl-core (github.com) @Luma if you can help Miora finding a solution, it could be nice.

-          I have opened a PR to fix the BUS_VOLTAGE sensitivity factor in order to stay in bus/breaker view Fix sensitivity factor model reader for BUS_VOLTAGE factor by annetill · Pull Request #2240 · powsybl/powsybl-core (github.com) @Sylvain if you have time to review this before your vacation, it could be helpful.

-          Add convenient methods to retrieve bus-breaker buses from bus-branch bus ID by miovd · Pull Request #2239 · powsybl/powsybl-core (github.com) I think it is a very useful feature, I hope it will be ready for next release. Unit testing is low for the moment.

-          We have decided to rename the topology network modifications AttachNewLineOnLine and AttachVoltageLevelOnLine and to increase documentation (Rename Topology network hypotheses with Connect instead of Attach by miovd · Pull Request #2238 · powsybl/powsybl-core (github.com)). There are some impact on a pypowsybl PR that interfaces these methods and impacts on two PRs that codes the reverse changes (PR 2230 and PR 2228). So we have to agree on names and merge it as soon as possible.

-          Geoffroy has open a PR for operations on matrix Improve dense matrix multiplication and addition performance by geofjamg · Pull Request #2236 · powsybl/powsybl-core (github.com) : @Geoffroy : just tell me if you need help and if you need this PR for the next release.

-          Sylvain has found an issue on XML serialization of BranchObservability. @Miora : waiting for your review and merge.

-          There are two PRs for reverse changes of attach new line on line and attach voltage level on line (PR 2230 and PR 2228), review of Geoffroy expected and be careful of the renaming PR explained above. Note that Florian is out of the office until September the 7th.

-          There are two PRs for PowerFactory importer but there are draft PRs. @Luma : do you need these PRs to be merged for next release ?

-          First step towards reproducible itools-packager builds: setTime in the zip by jonenst · Pull Request #2220 · powsybl/powsybl-core (github.com) @Jon : there is no reviewer for your PR on itools. Do you want this PR for next release ?

-          Miora has opened a PR to introduce builders for network modifications (Proposition for network modification builder by miovd · Pull Request #2218 · powsybl/powsybl-core (github.com)) : good idea. Not urgent for the next release and unit tests needed.

-          Luma has opened a PR to be able to import a CGMES file with all profiles in a single XML file (Allow boundaries to be assembled with other network data in the same instance file by zamarrenolm · Pull Request #2216 · powsybl/powsybl-core (github.com)). @Miora : we are waitning for your review and this PR must be in the next release.

-          This PR (Network modification: create feeder bay by colinepiloquet · Pull Request #2214 · powsybl/powsybl-core (github.com)) that creates a bay feeder for any injection must be available for next release. @Coline : the Javadoc is too poor for the moment, especially for utility functions. And Geoffroy has made a comment.

-          Create utility class for compareXml/compareTxt for refactoring purposes by sfid98 · Pull Request #2209 · powsybl/powsybl-core (github.com) is almost ready to be merged. I just have to check the copyright with Lucian before.

-          Reporter new API : what is the status of this work ?

-          Sensitivity analysis: add contingency status in the results by annetill · Pull Request #2186 · powsybl/powsybl-core (github.com) @Geoffroy : I need you review on that PR, whan you find some time… thanks !

 

Anything else ? I have planned to write an e-mail with my feedback on the security analysis with actions after a draft support on the OpenLoadFlow. @Etienne : if my returns are relevant, it must be included for the next release to minimize breaking changes.

 

Thanks everybody, just reach me if you need !

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Re: LF Energy PowSyBl Project License Scan and Findings July 2022

John Mertic
 

Resending due to message issues.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
Academy Software Foundation, LF Energy, and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


On Thu, Aug 4, 2022 at 4:31 AM Jeff Shapiro <jshapiro@...> wrote:
Hi Team,

Here are the results from the July 2022 license scan of the PowSyBl project.  The scan was performed using the Linux Foundation Fossology server.  Licenses and copyrights were examined.

The key findings (if any) and license summary can be found in the HTML report, the list of files in the spreadsheet, and also find the SPDX file listed below:

REPORTS:

lfenergy/powsybl, code pulled 2022-07-28
  - report: https://lfscanning.org/reports/lfenergy/powsybl-2022-07-28-3f2fe59e-8428-48a2-8b09-132962c979f8.html
  - xlsx:   https://lfscanning.org/reports/lfenergy/powsybl-2022-07-28-3f2fe59e-8428-48a2-8b09-132962c979f8.xlsx
  - spdx:   https://github.com/lfscanning/spdx-lfenergy/tree/master/powsybl/2022-07/powsybl-2022-07-28.spdx


NOTE:  The Key Findings in the report are from a previous scan, and the files are still present in your repository.  You should check to see if these have been addressed, remove the affected files, or let me know if there are no isseus.

Please feel free to contact me with any questions about the scan results.  Be sure to reply to me directly as I may not get an email sent directly to the distribution list.

Thanks, Jeff

Jeff Shapiro
408-910-7792
jshapiro@...




Now: TSC meeting - 07/28/2022 #cal-notice

Group Notification <noreply@...>
 

TSC meeting

When:
07/28/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Event: TSC meeting - 07/28/2022 #cal-reminder

Group Notification <noreply@...>
 

Reminder: TSC meeting

When:
07/28/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Annulé: TSC meeting

TILLOY Anne
 

Hi everybody,
 
Too many committers are in vacation, next TSC in September !
 
Have great holidays.
 
++
 
Anne
 
________________________________________________________________________________
Réunion Microsoft Teams
Rejoindre sur votre ordinateur ou application mobile
Rejoindre avec un appareil de vidéoconférence
ID de vidéoconférence : 126 318 204 3
________________________________________________________________________________
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Now: TSC meeting - 06/30/2022 #cal-notice

Group Notification <noreply@...>
 

TSC meeting

When:
06/30/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Next TSC meeting

TILLOY Anne
 

Hi everybody,

 

Our next TSC meeting will be on June the 30th, 13h30, on Teams: Cliquez ici pour participer à la réunion

 

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

 

Next release will be on the end of July or on the beginning of September. This release of powsybl-core already contains:

 

-          IIDM: limit getters return optionals. It is a breaking change.

-          PowerFactory importer improvements.

-          Short-circuit: clean and refactoring.

-          [Expected] In the sensitivity analysis API, the results give a list of contingencies. This is going to change for a list of ContingencyStatus, that gives the status, for each contingency, of the computation (FAILED, CONVERGED, NO_IMPACT).

-          [Expected] A first version of the security analysis API with remedial action: simple and non-exhaustive in order to start the POC on open-loadflow implementation.

-          [WIP] Sets of operational limits: postponed. We are going to find a way to use the private extension currentLimitsPerSeason and properties.

 

Release train 1.2.1 (Release v1.2.1 · powsybl/powsybl-dependencies (github.com)), based on powsybl-core 4.9.1 (Release v4.9.1 · powsybl/powsybl-core (github.com)):

 

-          Note that a patch release of powsybl-core has been published : this release introduces a configuration parameter for CGMES import, which allows the source for IIDM identifiers to be set to rdf:id instead or mRIDs.

-          Please look at the release notes for more details about this release train.

 

Other repositories:

-          Florian: single line diagram and network area diagram.

-          Sylvain: pypowsybl.

-          OLF:

Support of ThreeWindingsTransformer contingency for sensitivity and security analysis.

[WIP] Support of shunt conductance.

[Excepted] New incremental transformer voltage control outer loop.

[WIP] Support of contingency propagation for sensitivity analysis, make it optional.

[WIP] Work on generators connected to the same bus but controlling two different buses -> change the exception by a warning first.

-          powsybl/powsybl-starter (github.com)

-          powsybl/powsybl-benchmark (github.com)

-          IIDM C++, no release for the moment, still supporting until IIDM 1.5.0, WIP.

-          WIP: non regression testing

 

Roadmap:

-          Integration of Dynawo : redesign for next release, then work by Dynawo team ;

-          Time series : benchmarks on time scale DB ;

-          Network modifications improvement -> we need to write issues in order to have a collaborative organization on that topic ;

-          Increasing the shortcircuits API: REX after models integration and work around parameters

-          TODO: fusion of balances-ajustement and powsybl-enstoe?

-          TODO: we are late about documentation.

-          Multi component results for security analysis API.

-          The support of EMF in pypowsybl

-          Discussion about fictitious switch in CGMES

-          Other subjects?

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

powsybl-tsc@... | Calendar

 

See you soon !

 

Anne

 

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Event: TSC meeting - 06/30/2022 #cal-reminder

Group Notification <noreply@...>
 

Reminder: TSC meeting

When:
06/30/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Re: Power Flow Support in CIMSpy/CIMdesk

John Mertic
 

We probably don't need to make this that hard - the case study needs 4 components...

1) Problem statement
2) Why the given project was chosen
3) How the transition has gone
4) Next steps

If we could collect that from them ( maybe a form they fill out ), it should be trivial to write from there.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
Academy Software Foundation, LF Energy, and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


On Wed, Jun 8, 2022 at 6:14 PM Shuli Goodman <sgoodman@...> wrote:
Hi bumping this up again.

Hilary and Chad, could we do a case study?
Thanks!


Shuli



l. shuli rose goodman phd.
executive director, LF Energy
a Linux Foundation project
twitter: @LFE_Foundation
linkedin.com/in/shuligoodman
c: +1.415.722.9688
v: +1.707.874.3231
+++++++++++++++++++++++++++
+++++++++++++++++++++++++++



On May 18, 2022, at 8:08 AM, Shuli Goodman <sgoodman@...> wrote:

I agree. Great news! Let’s loop Hilary and Chad in once back from KubCon. 

We probably will need to find a French speaking writer who can deliver in English. Should not be hard. Maybe RTE can help?

Thanks!


l. shuli rose goodman
+1.415.722.9688
(sent from my tin can)

On May 18, 2022, at 4:45 AM, John Mertic <jmertic@...> wrote:


Great news!

@Shuli Goodman @Carly Akerly - wondering if we should do some sort of case study on this?

Thank you,

John Mertic
Director of Program Management - Linux Foundation
Academy Software Foundation, LF Energy, and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


On Wed, May 18, 2022 at 3:35 AM TILLOY Anne <anne.tilloy@...> wrote:

Hi everybody,

 

I am just received that information today, in French sorry for that. It seems that Power Info is going to use Powsybl in CIMdesk and CIMSpy. What a great news !

 

Best regards.

 

Anne

 


De : Jun Zhu <junzhu@...>
Envoyé : mardi 17 mai 2022 08:44
À : info@...
Objet : Power Flow Support in CIMSpy/CIMdesk

 

EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

 

 

Dear CIMSpy/CIMdesk Users,

 

Just want to share some of the work recently conducted: supporting power flow in CIMSpy/CIMdesk. This is one of the most-requested features, particularly from (European) CIMdesk users. Below is overview of the new feature. For more detailed information, please refer to the attached document.

 

Note: 

 

<image002.gif>     The new feature will be included in CIMdesk 2.8.x to be released to all CIMdesk users sometime this summer, subject to ENTSO-E approval.

<image002.gif>     For CIMSpy users, please check FAQs in the attached document. If you are interested in evaluating this new feature, please contact me. A new version of CIMSpy can be released to interested users at the same time.      

<image002.gif>     Feedbacks are mostly appreciated.  

 

Regards,

Jun

 

 

<image003.jpg>

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction. 

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Re: Power Flow Support in CIMSpy/CIMdesk

Shuli Goodman <sgoodman@...>
 

Hi bumping this up again.

Hilary and Chad, could we do a case study?
Thanks!


Shuli



l. shuli rose goodman phd.
executive director, LF Energy
a Linux Foundation project
twitter: @LFE_Foundation
linkedin.com/in/shuligoodman
c: +1.415.722.9688
v: +1.707.874.3231
+++++++++++++++++++++++++++
+++++++++++++++++++++++++++



On May 18, 2022, at 8:08 AM, Shuli Goodman <sgoodman@...> wrote:

I agree. Great news! Let’s loop Hilary and Chad in once back from KubCon. 

We probably will need to find a French speaking writer who can deliver in English. Should not be hard. Maybe RTE can help?

Thanks!


l. shuli rose goodman
+1.415.722.9688
(sent from my tin can)

On May 18, 2022, at 4:45 AM, John Mertic <jmertic@...> wrote:


Great news!

@Shuli Goodman @Carly Akerly - wondering if we should do some sort of case study on this?

Thank you,

John Mertic
Director of Program Management - Linux Foundation
Academy Software Foundation, LF Energy, and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


On Wed, May 18, 2022 at 3:35 AM TILLOY Anne <anne.tilloy@...> wrote:

Hi everybody,

 

I am just received that information today, in French sorry for that. It seems that Power Info is going to use Powsybl in CIMdesk and CIMSpy. What a great news !

 

Best regards.

 

Anne

 


De : Jun Zhu <junzhu@...>
Envoyé : mardi 17 mai 2022 08:44
À : info@...
Objet : Power Flow Support in CIMSpy/CIMdesk

 

EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

 

 

Dear CIMSpy/CIMdesk Users,

 

Just want to share some of the work recently conducted: supporting power flow in CIMSpy/CIMdesk. This is one of the most-requested features, particularly from (European) CIMdesk users. Below is overview of the new feature. For more detailed information, please refer to the attached document.

 

Note: 

 

<image002.gif>     The new feature will be included in CIMdesk 2.8.x to be released to all CIMdesk users sometime this summer, subject to ENTSO-E approval.

<image002.gif>     For CIMSpy users, please check FAQs in the attached document. If you are interested in evaluating this new feature, please contact me. A new version of CIMSpy can be released to interested users at the same time.      

<image002.gif>     Feedbacks are mostly appreciated.  

 

Regards,

Jun

 

 

<image003.jpg>

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction. 

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Now: TSC meeting - 06/02/2022 #cal-notice

Group Notification <noreply@...>
 

TSC meeting

When:
06/02/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


TSC meeting

TILLOY Anne
 

Hi everybody,
 
I have decided to switch to Teams for this regular meeting.
Thanks for understanding.
 
++
 
Anne
 
________________________________________________________________________________
Réunion Microsoft Teams
Rejoindre sur votre ordinateur ou application mobile
Rejoindre avec un appareil de vidéoconférence
ID de vidéoconférence : 126 318 204 3
________________________________________________________________________________
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Next TSC meeting

TILLOY Anne
 

Hi everybody,

 

Our next TSC meeting will be on June the 2nd, 13h30, on Teams: Cliquez ici pour participer à la réunion

 

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

 

Release candidate of powsybl-core available on Friday Release v4.9.0 (expected: 2022-06-15) · powsybl/powsybl-core (github.com), with as major features:

 

-          CGMES 2.4.15: fixes and improvements after a lot of tests performing for full export validation on real networks.

-          CGMES 3.0: improvements, still a beta feature. Do not hesitate to test this feature and provide feed-back.

-          Configuration: add methods to get the specific parameters of a sensitivity or security analysis.

-          Configuration: add import/export parameter possible values.

-          IIDM: fictitious injections.

-          Modifications: fix add voltage level on a line.

-          Power Factory importer.

-          PSSE importer.

-          Triple store: remove Jena implementation.

-          Many quality commits.

-          Expected: increase of short-circuit API to support elementary computations.

-          Excepted: IIDM converter API merged with IIDM network API.

 

Next release will be on April the 23rd.

-          EMF based on the destructive merge and not on the merging view?

-          Operational limit set support.

-          Support of protections and automatons in IIDM network.

-          On-going work abound a new security analysis with actions (Security analysis with remedial actions · Issue #2015 · powsybl/powsybl-core (github.com)) + a WIP PR [WIP] add remedial actions for security analysis by EtienneLt · Pull Request #2095 · powsybl/powsybl-core (github.com)

 

Other repositories:

-          Florian: single line diagram and network area diagram.

-          Sylvain: pypowsybl.

-          OLF:

Support of all type of contingencies for AC and DC sensitivity analysis and security analysis.

New incremental transformer voltage control outer loop.

-          powsybl/powsybl-starter (github.com)

-          powsybl/powsybl-benchmark (github.com)

-          IIDM C++, no release for the moment, still supporting until IIDM 1.5.0, WIP.

-          WIP: update of powsybl-tutorials

-          WIP: non regression testing

 

Roadmap:

-          Integration of Dynawo : redesign for next release, then work by Dynawo team ;

-          Time series : benchmarks on time scale DB ;

-          Network modifications improvement -> we need to write issues in order to have a collaborative organization on that topic ;

-          New security analysis API with actions (Security analysis with remedial actions · Issue #2015 · powsybl/powsybl-core (github.com)).

-          Increasing the shortcircuits API: REX after models integration and work around parameters

-          TODO: fusion of balances-ajustement and powsybl-enstoe?

-          TODO: we are late about documentation.

-          Multi component results for security analysis API.

-          The support of EMF in pypowsybl

-          Discussion about fictitious switch in CGMES

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

powsybl-tsc@... | Calendar

 

See you soon !

 

Anne

 

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Event: TSC meeting - 06/02/2022 #cal-reminder

Group Notification <noreply@...>
 

Reminder: TSC meeting

When:
06/02/2022
1:30pm to 2:30pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:

Cliquez ici pour participer à la réunion

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Re: Power Flow Support in CIMSpy/CIMdesk

Shuli Goodman <sgoodman@...>
 

I agree. Great news! Let’s loop Hilary and Chad in once back from KubCon. 

We probably will need to find a French speaking writer who can deliver in English. Should not be hard. Maybe RTE can help?

Thanks!


l. shuli rose goodman
+1.415.722.9688
sgoodman@...
(sent from my tin can)

On May 18, 2022, at 4:45 AM, John Mertic <jmertic@...> wrote:


Great news!

@Shuli Goodman @Carly Akerly - wondering if we should do some sort of case study on this?

Thank you,

John Mertic
Director of Program Management - Linux Foundation
Academy Software Foundation, LF Energy, and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


On Wed, May 18, 2022 at 3:35 AM TILLOY Anne <anne.tilloy@...> wrote:

Hi everybody,

 

I am just received that information today, in French sorry for that. It seems that Power Info is going to use Powsybl in CIMdesk and CIMSpy. What a great news !

 

Best regards.

 

Anne

 


De : Jun Zhu <junzhu@...>
Envoyé : mardi 17 mai 2022 08:44
À : info@...
Objet : Power Flow Support in CIMSpy/CIMdesk

 

EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

 

 

Dear CIMSpy/CIMdesk Users,

 

Just want to share some of the work recently conducted: supporting power flow in CIMSpy/CIMdesk. This is one of the most-requested features, particularly from (European) CIMdesk users. Below is overview of the new feature. For more detailed information, please refer to the attached document.

 

Note:

 

image002.gif     The new feature will be included in CIMdesk 2.8.x to be released to all CIMdesk users sometime this summer, subject to ENTSO-E approval.

image002.gif     For CIMSpy users, please check FAQs in the attached document. If you are interested in evaluating this new feature, please contact me. A new version of CIMSpy can be released to interested users at the same time.      

image002.gif     Feedbacks are mostly appreciated.  

 

Regards,

Jun

 

 

image003.jpg

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."

1 - 20 of 149