openclimatefix / PVNet

PVnet main repo
MIT License
15 stars 3 forks source link

Training questions #107

Open peterdudfield opened 7 months ago

peterdudfield commented 7 months ago

Hi @dfulu , here are some questions from a Energy Forecasting company. They asked

  1. How many images are used for the training process?

  2. I've noticed that on the Eumetsat platform, cloud mask images appear to be delayed relative to the satellite images. How are these used in the forecasting process?

  3. What is the frequency of updates? Is it every 15 minutes?

  4. How many hours ahead do you forecast and with which granularity?

  5. Do you possess any performance data specific to a concrete PV plant that you could share? There is some open source data here, but they are all quite small PV plants.

@dfulu do you mind answering these? We could even add them to the Readme.md if we want

jacobbieker commented 7 months ago

For 2. cloud masks are not currently used at all. We just give the satellite imagery.

  1. I believe its every half an hour? As the satellite data is delayed in production?
  2. 8 hours at half-hourly resolution, being extended soon.
  3. I don't think we have any specific PV plant data to share, since its all regional at the moment, even India is regional data instead.
dfulu commented 7 months ago

To add to what Jacob has said

  1. We use 1.6 million training examples across the 317 GSPs. Thats selected over about 5 years (so ~500,000 different 5-minutely source satellite images). Each training example uses a history of 7 satellite images.
  2. I thought the satellite data was only actually refreshed by the consumer once an hour. Hence we would get alternating 30-minute and 60-minute delays. Although I haven't looked at those delays since before summer.
peterdudfield commented 7 months ago

Could we make a PR and add this to the Readme.md please?

peterdudfield commented 7 months ago

@dfulu your probably the best person to update the Readme.md with these?

peterdudfield commented 7 months ago

Lets reflect on current Readme, and see what needs adding

Rough idea is to keep the expereiment document, could be one expeirement doc for each UK, India, e.t.c

Try to keep the Readme.md generic. Have a high end overview of what the UK production is using, at most 1 paragraph. This means it wont change much so is easy to maintain, but providers useful information for people