search

Baltic-RCC / EMF

Repository for Open Source EMF implementation
Mozilla Public License 2.0
9 stars 3 forks source link

Identify maximum set of TSO-s for CGM #142

Closed Haigutus closed 1 month ago

Haigutus commented 2 months ago

Identify TSO-s to be included, that results in a stable CGM, to achieve stable daily process

MK1295 commented 2 months ago

EXCLUDE areas : DKE, DKW, FR, D2, D4, D7, D8, AT, if needed also SI Issues with SI IGMs - denied CGMs due to Kirchhoff’s First Law issue – solved and verified on TST environment, waiting deployment on PROD Issues for D2, D8 - CGM divergence, issue with equivalent branches – solved but HF not yet available for testing on TST environment [SCC] RTEFRANCE creates divergence issues for most TSs [SELENECC]

Haigutus commented 1 month ago
  1. Can you also provide currently known good set of IGM-s?
  2. Any ideas how to identify those issues during the IGM validation?
Haigutus commented 1 month ago

On point 2., check sum flow per TP node in IGM validation, after the LF step. To exclude models with Powerflow and Topology issue

MK1295 commented 1 month ago

Include : APG,AST,CEPS,CGES,CREOS,EMS,ESO,HOPS,IPTO,LITGRID,NOSBIH,OST,PSE,REE,REN,SEPS,TRANSELECTICA,ELERING,MAVIR,SWISSGRID,

Exclude: ELES,ELIA,DKE,DKW (Occasional errors) RTEFRANCE,TERNA(Localized errros) 50Hertz,TTG,D7 (propagating erros)

UNDER DISCUSSION: D4,FINGRID https://github.com/Baltic-RCC/EMF/tree/mr-open-nonretained-switches-connecting-tns (Checking problamtic switched and feed it to loadflow, the changed model will not be used in the post-processing, and this solution would be temporary if it will be implemented in validation)