[fix] Simulation years can cause a crash

To do

• Rethink the parsing of the daily weather data
  • check lat, lon closeness: warning if latitude, longitude in the Agri4cast weather data does not match the lat, long from the input file
  • check altitude closeness
• check alignment of SimulationStartingYear and SimulationEndingYear
• User documentation
  • where to download data
  • data units
  • Agri4Cast : how to pick a station
  • ...

Summary

(Summarize the bug encountered concisely)

Steps to reproduce

Set start year to 2020 and end year to 2023 in the yaml. configuration file.

Example Project

N/A

What is the current bug behavior?

It crashes when loading the weather data.

What is the expected correct behavior?

It should work.

Relevant logs and/or screenshots

Possible fixes

For a successful simulation :

• the simulation years must be compatible with the PVGIS database called by PASE (i.e. PVGIS-SARAH3 goes from 2005-2023 ; in PVGIS 5.3, it is the default DB for Europe, Central Asia, Africa and South America (partly))
• the simulation years (SimulationStartingYear and SimulationEndingYear) must lie within the data range of the daily weather data file. If the daily weather data file goes from 2005 to 2015, you can simulate any period within 2005-2015, e.g. : 2005-2015, 2005-2005, 2010-2014, etc.

If those conditions are not met, the simulation will crash and return a cryptic error message (see screenshot above).