Closed zakwatts closed 7 months ago
We might want it to be set to the same as PVNet repo, which is currently 3.0.23?
I see, but the current version of PVNet in production isn't that? I'm thinking instead to then just do version control based off that version in the PVNet repo now.
Yeah, so have this update be this, and this will update to 2.1 when #minor is added to a commit. The name of the model in the app should change, but that is something different, I'll open an issue on that.
Update version.
Once the pvnet model has been updated to represent the forecast sent in backtest, this should be changed to 2.1.
Forecast sent in backtest was UK national probabilistic with ensembles and ECMWF.