PERFORM-Forecasts / documentation

ARPA-E PERFORM Forecasts Documentation
18 stars 8 forks source link

ECMWF in MW #17

Open helenehanyu opened 2 years ago

helenehanyu commented 2 years ago

Hi I am looking at the ECMWF v.s. Actuals. And I have noticed that the ECMWF is the unit of MW. To my best knowledge, ECMWF only generates weather forecasts. I am wondering what is the post-process procedure. Is this the output of SAM?

I have also noticed that some files in the ECMWF are named in a different fashion. For example, the ECMWF file Site_Adams_Wind_Generations,_LLC_wind_2day-ahead_2019.h5 . the file's corresponding actuals are Site_Adams_Wind_Generations_LLC_wind_actuals_2019.h5 . The , is dropped in the naming of the actuals. Is it possible to name every wind farm in the same way?

Thank you

bsergi commented 2 years ago

On the question of the units, your intuition is correct in that we are using the ECMWF forecasts to generate solar and wind output profiles using SAM.

The Site_Adams_Wind_Generations,_LLC_wind_2day-ahead_2019.h5 may be an old file as the file size looks off and there is another file Site_Adams_wind_2day-ahead_2019.h5 which matches the expected format. @fzhang-WZ can you take a look at this an confirm?

fzhang-WZ commented 2 years ago

Adams and Adams Wind Generations, LLC are completely two different sites. Adams Wind Generations, LLC is a much smaller site with capacity around 20 comparing to Adams with capacity 154. I will update the name with , deleted.

bsergi commented 2 years ago

Thanks @fzhang-WZ, let me know when you've updated and we can re-sync. @helenehanyu we'll post here when the naming issue is resolved

bsergi commented 2 years ago

FYI we've updated the name to remove the comma and that data is synced to AWS. Am closing this issue for now, but please reach out again if you have additional questions.

helenehanyu commented 1 year ago

Hello @fzhang-WZ and @bsergi , the file names in MISO's site-level forecasts are still inconsistent with Actuals. The intra-hour forecasts are correct. But intra-day, day-ahead, 2day-ahead are still having extra symbols.

bsergi commented 1 year ago

@helenehanyu can you point us to a few examples of discrepancies that you are seeing?

helenehanyu commented 1 year ago

Here are a few examples,

There is MISO/2019/Wind/Actuals/Site_Adams_Wind_Generations_LLC_wind_actuals_2019.h5 v.s. /MISO/2019/Wind/Forecasts/2Day-ahead/Site_level/Site_Adams_Wind_Generations,_LLC_wind_2day-ahead_fcst_2019.h5

MISO/2019/Wind/Actuals/Site_level/Site_G_McNeilus_Wind_Farm_wind_actuals_2019.h5 v.s. Site_G._McNeilus_Wind_Farm_wind_2day-ahead_fcst_2019.h5

/MISO/2019/Wind/Actuals/Site_level/Site_Glen_Ullin_Energy_Center_Clean_Energy_1_wind_actuals_2019.h5 v.s. /MISO/2019/Wind/Forecasts/2Day-ahead/Site_level/Site_Glen_Ullin_Energy_Center_(Clean_Energy_1)_wind_2day-ahead_fcst_2019.h5

bsergi commented 1 year ago

@fzhang-WZ are you able to take a look at this?