Seems unprofessional to me, you already started dunking on this release but added little to no arguments as to why or what is wrong here.
Honestly this might be very good for feature selection to refine a much more specialized model.
Edit : working with GLM5.3 now, it's also slow. Maybe Mistral's under heavy load.
Disclaimer : Not Cofounder of The Forecasting Company here
> Known-future covariates. Some drivers of sensor behaviour are known in advance, such as production schedules, planned shutdowns, weather forecasts. Timestral can condition on them to improve forecast quality, so a scheduled load increase is expected rather than flagged as a surprise.
To me this should be the entire basis of the system, not a condition to improve forecast quality? Like if you're modelling electricity consumption, if all you have is a window of N previous samples, you're going to get completely beaten by a comparatively simple system that knows the time of day, that there's holidays coming up, the weather forecast, etc.
I would also think that these time-series forecasting models would gain from a sophisticated understanding at least the labels of the covariates? A 5M model has no idea what a "bank holiday" is, it just sees an arbitrary class go from 0 to 1, and won't have any useful inductive biases as to what it means or how to link them to other pieces of information.
Or perhaps I misunderstand the use-case and this is more for extremely short term movements?
edot•51m ago
Speed looks nice too. I want an open weight model with this performance now.
GeoffNN•40m ago
dfdydx•32m ago
OKRainbowKid•36m ago