ENTSO-E filename convention

[mathbagu]

The UcteFileName class must be renamed in EntsoeFileName class and missing features must be added:

• missing file types (2-days ahead and intra-day at least, LT and RE)
• missing UC geographical code
• long clock change support

For long clock change, ENTSO-E NM&FT (SOC/RGCE) chose the following name convention:

• YYYYMMDD_0230_TyW_UCV.uct (CEST)
• YYYYMMDD_B230_TyW_UCV.uct (CET)

More informations are available in file in attachment
File name convention operational data exchanges.pdf

[nomont]

Forecast distance checks / optimization can be done based on the following assumptions:
The specifications says that: "TY: File type (FO = Day Ahead Forecast, SN = Snapshot, RE = Reference, LR = Long Term Reference, 2D = two days ahead forecast, ‘hh’ = Intraday Forecasts where ‘hh’ is for example ‘02’ for two hours ahead intraday forecast)". Therefore, when:

• TY = 2D, it was generated between 00:00 and 23:59 in D-2.
• TY = FO, it was generated between 00:00 and 23:59 in D-1.
• TY = hh, it was generated between 00:00 and 23:59 in D and “hh” hour before the realization.