-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CGMES export bugs #2707
Comments
I will fix the rest of the issues in separated PRs. I will start with the |
About preserving We plan to store (in a property) only the |
About preserving We plan to store (in a property) only the storage type of hydro power plant (run of river, pumped storage, storage). |
Using property is very weak, we should think about enriching the generator to have something better than just energy source with just a few values |
Both For the use-case that we want to support, is this valid ? |
We defaulted to properties because this information is not required for the kind of analysis that PowSyBl is performing now, but we are not aware of the specific use-case where it is needed. Are there more details on this ? Why is relevant to keep this information through PowSyBl ? |
Also, before deciding how to store this data in IIDM, we have to know if we need to keep track of the CGMES identifiers involved: a generating unit may have multiple fossil fuel type associations, and an hydro generating unit has its kind defined through an association to a hydro power plant object. Maybe instead of augmenting the model for generators we should consider an extension. |
Let's look at |
Is it needed? |
I agree with @geofjamg, we have to increase enum
Can we put in this reflexion what is called generator enstoe category? |
It is needed if we want to preserve the original CGMES information in IIDM. It also contains "hints" about the behaviour of the plant ( |
Hello, In general, if we want to keep the information for round trip import-export, it can be modeled as a named property, if it's not going to be used in powsybl, or as extension of IIDM model. Regarding graph LR;
SynchronousMachine-->HydroGeneratingUnit-->HydroPowerPlant;
HydroPump-->SynchronousMachine;
HydroPump-->HydroPowerPlant;
|
Describe the current behavior
minQ
andmaxQ
.AcLineSegment
gch: maybe because there are equal to zero (we have this condition in the code).FossilFuel
andHydroPowerPlant
.TapChangerControl
missing (phase control and voltage control).operatingMode
in SSH even though the injection is 0. This is not that relevant unless the machine has control enabled.To be continued.
Describe the expected behavior
No response
Describe the steps
No response
Environment
No response
Relevant Log Output
No response
Extra Information
No response
The text was updated successfully, but these errors were encountered: