Skip to main content

Process data

Inputs​

input file naming convention​

The general file naming convention is:

YYYYMMDD-Fzzz-vx-17XTSO-CS------W-to-22XCORESO------S.zip.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • zzz is the file type (see sections below)
  • x is the file version.

CGM (F119)​

The F119 document is a zip containing the 24 networks in UCTE format and an xml header linking the networks to timestamps.

The networks are in UCTE-DEF format, version 02. They follow specific file naming conventions that are used to automatically feed the platform when new files arrive on the FTP server. The process is based on the merged D2CF grid models, to form a Common Grid Model (CGM).

The network files follow the naming convention: YYYYMMDD_hhmm_2Da_UXV_FEXPORTGRIDMODEL_CGM_17XTSO-CS------W.uct.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • hh is the hour of the timestamp
  • mm is the minute the timestamp (usually 30)
  • a is the day of the week (1 for Monday)
  • V is the file version.

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

Reference program (F120)​

The F120 document is an xml file containing the reference program, which is composed by the values of the power exchanges between the different market areas. In OpenRAO, this is used to compute loop-flows.

For a detailed description of the F120 file, you can refer to the documentation: OpenRAO documentation.

DC CGM (F139)​

The F119 document is a zip containing the 24 networks in UCTE format and an xml header linking the networks to timestamps.

This alternative CGM is used to perform the actual NRAO computation, but the chosen remedial actions will be applied on the AC network (F119).

In the naming, the string "FEXPORTGRIDMODEL_CGM" is replaced by "FINIT_EXPORTGRIDMODEL_DC_CGM".

CBCORA (F301)​

The F301 file is an xml containing the critical branches, contingencies and available remedial actions.

Its format, called FlowBasedConstraintDocument, is described in the OpenRAO documentation.

RAO request (F302)​

The F302 document is an xml file containing a list of timestamps to be run and a list of RaoParameters.

GLSK (F319)​

The F319 document is an xml file containing the Generation and Load Shift Keys (GLSK) in UCTE format, detailed in the PowSyBl-ENTSOE documentation.

Virtual hubs (F327)​

The F327 document is an xml file containing the virtual hubs, which are one-node areas which should be considered as market areas when calculating loop-flows.

For a detailed description of the F327 file, you can refer to the documentation: OpenRAO documentation.

Hardcoded data​

RaoParameters​

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

The values of the parameters for Core CC 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.

Outputs​

Output file naming convention​

The generic output file naming convention is: 22XCORESO------S_10V1001C--00236Y_CORE-FB-Fzzz_YYYYMMDD-Fzzz-VV.uuu.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • zzz is the file type (see sections below)
  • VV is the file version
  • uuu is the file extension.

Core CNE (F299)​

The F299 file is a zip file containing the Core CNE file per timestamp. it contains among other the flows, thresholds, PTDFs and loop-flow values. The description of the format is available in the OpenRAO documentation.

ACK file (F302)​

The F302 file is an xml file containing the reply of GridCapa on whether the computation succeefded or not.

It follows the naming convention: 22XCORESO------S_10V1001C--00236Y_CORE-FB-F302-ACK_YYYYMMDD-F302-VV.xml.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • VV is the file version.

FlowBasedConstraintDocument (F303)​

The F303 (FlowBasedConstraintDocument) file is an xml file containing the list of selected remedial actions and CNECs corresponding to curative states.

Networks with PRAs (F304)​

The F304 file is a zip file containing all post-RAO networks corresponding to the initial network with applied PRAs and a CGM header.

Each network follows the naming convention: YYYYMMDD_hhmm_2Da_UXV.uct.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • hh is the hour of the timestamp
  • mm is the minute the timestamp (usually 30)
  • a is the day of the week (1 for Monday)
  • V is the file version.

RaoResponse file (F305)​

The F305 file is an xml file containing the URL of the F299, F303 and F304 files for each timestamp.

Metadata (F341)​

The F341 file is a csv file containing the list of computation durations and hourly computation status. These individual metadata files are used to perform sanity checks and to gather general metadata information: end-to-end computation durations, overall status.

It follows the naming convention: YYYYMMDD_hhmm_METADATA-VV.json.

Where:

  • YYYY is the year of the timestamp
  • MM is the month of the timestamp
  • DD is the day of the timestamp in the month
  • hh is the hour of the timestamp
  • mm is the minute the timestamp (usually 30)
  • VV is the file version.

Logs (F342)​

The F342 file is a zip file containing the logs for each computation.