Context
In the current model, you can change weather years through radio buttons, but you can also 'change the weather year' through the backend by uploading solar, wind and temperature profiles.
Current shortcoming
In scenarios where the weather year is effectively changed due to uploaded weather profiles, this doesn't show in the radio button. This still shows as 'Default'. For example, in NBNL 2025 KM.
This is misleading as it suggests in this case that the weather year is still 2019, which is not the case, the description of this scenario states that the weather year is 2012.
Proposed enhancement
Have the radio button reflect it when the 'default' weather year is no longer active.
Success criteria
The tricky thing is that we often don't know what the custom weather year is. It is also possible that someone uploads solar profiles for 2012 but wind profiles for 2006. Finding a good solution to this might be tricky. @noracato / @aaccensi do you have any good ideas?
Context
In the current model, you can change weather years through radio buttons, but you can also 'change the weather year' through the backend by uploading solar, wind and temperature profiles.
Current shortcoming
In scenarios where the weather year is effectively changed due to uploaded weather profiles, this doesn't show in the radio button. This still shows as 'Default'. For example, in NBNL 2025 KM.
This is misleading as it suggests in this case that the weather year is still 2019, which is not the case, the description of this scenario states that the weather year is 2012.
Proposed enhancement
Have the radio button reflect it when the 'default' weather year is no longer active.
Success criteria
The tricky thing is that we often don't know what the custom weather year is. It is also possible that someone uploads solar profiles for 2012 but wind profiles for 2006. Finding a good solution to this might be tricky. @noracato / @aaccensi do you have any good ideas?