Skip to main content

Process data

Inputs​

CGM​

The CGM is in UCTE-DEF format, version 02. It follows specific file naming conventions that are used to automatically feed the platform when new files arrive on the FTP server.

  • The D2CC process is based on D2CF files that follow the file naming convention: YYYYMMDD_hhmm_2Dx_CO_Transit_CSEv.uct
  • The IDCC run 2 process is based on IDCF files that follow the file naming convention: YYYYMMDDhhmmyyx_Transit_CSEv.uct

Where:

  • YYYY is the timestamp year,
  • MM is the timestamp month,
  • DD is the timestamp day in month,
  • hh is the timestamp hour,
  • mm is the timestamp minutes (usually 30),
  • x is the timestamp day of the week number (example: if the day is a Wednesday, x=3; if it's a Sunday, x=7),
  • yy is the forecast hour of the IDCC run 2 process,
  • v is the file version.

For a detailed description of the UCTE-DEF format, you can refer to the format specification.

CRAC​

The CRAC is in a specific format, that follows specific file naming conventions that are used to automatically feed the platform when new files arrive on the FTP server.

  • The D2CC process is based on merged CRACs that follow the file naming convention: YYYYMMDD_hhmm_2Dx_CO_CRAC_Transit_CSEv.xml

  • The IDCC run 2 process is based on IDCF files that follow the file naming convention: YYYYMMDD_hhmm_yyx_CO_CRAC_Transit_CSEv.xml

  • YYYY is the timestamp year,

  • MM is the timestamp month,

  • DD is the timestamp day in month,

  • hh is the timestamp hour,

  • mm is the timestamp minutes (usually 30),

  • x is the timestamp day of the week number (example: if the day is a Wednesday, x=3; if it's a Sunday, x=7),

  • yy is the forecast hour of the IDCC run 2 process,

  • v is the file version.

For more information on the CSE CRAC format, see the OpenRAO documentation.

Hardcoded data​

RaoParameters​

The computations are based on parameters, described in the OpenRAO documentation.

The values of the parameters for the Italy North export process are defined in the gridcapa-deployment configuration. Compared to this list, a few parameters might be modified during the computation, directly in the code. Others, if not defined, are set to the default values listed in the documentation.

CracCreationParameters​

Configmap​

Outputs​

CSE RAO result​

The result of the RAO computation is exported in a file named TTC_Calculation_YYYYMMDD_hhmm_2Dx_CO_RAO_Transit_CSEv.xml.

  • YYYY is the timestamp year,
  • MM is the timestamp month,
  • DD is the timestamp day in month,
  • hh is the timestamp hour,
  • mm is the timestamp minutes (usually 30),
  • x is the timestamp day of the week number (example: if the day is a Wednesday, x=3; if it's a Sunday, x=7),
  • v is the file version.

The file format is in a specific CSE RAO result format in XML.

? To be added: description of the file format

RAO logs​

The logs of the RAO computation are exported in a file named rao_logs.txt.

The detail of the logs is described in the OpenRAO documentation.

Network​

The network file with applied Preventive Remedial Actions (PRAs) is exported in a file named YYYYMMDD_hhmm_2Dx_ce_Transit_RAO_CSEv.uct.

  • YYYY is the timestamp year,
  • MM is the timestamp month,
  • DD is the timestamp day in month,
  • hh is the timestamp hour,
  • mm is the timestamp minutes (usually 30),
  • x is the timestamp day of the week number (example: if the day is a Wednesday, x=3; if it's a Sunday, x=7),
  • v is the file version.