tsfeatures VS statsforecast

GluonTS Differences: -GluonTS is written in mxnet, which reduces its adoption. In contrast, NeuralForecast is written in PyTorch. -Including new models in GluonTS tends to be challenging because mxnet 's and the library structure's learning curve are steep. PyTorch-Forecasting Differences: -NeuralForecast hosts some models from our research, including N-HiTS and Transformer-based (Autoformer, Informer, Transformer, etc.) methods specialized in long-horizon forecasting (https://arxiv.org/abs/2201.12886). -And the exogenous variables extension of N-BEATS, the NBEATSx (https://arxiv.org/abs/2104.05522). Extra Features: -NeuralForecast has a wide range of curated datasets used in research to develop and test new models, such as Tourism, M3, M4, M5, EPF, ILI, Traffic, Weather, etc. -NeuralForecast models include reasonable hyperparameter spaces to speed up hyperparameter search, based on our experience. -We include an experiment module that makes it easy to put the entire time series forecasting pipeline into production. -Finally, NeuralForecast is part of a larger ecosystem of time-series analysis and forecasting that includes feature creation (tsfeatures, https://github.com/Nixtla/tsfeatures), machine learning models (mlforecast, https://github.com/Nixtla/mlforecast) and statistical models (statsforecast, https://github.com/Nixtla/statsforecast).

Thanks for your comments.

We agree that in most cases prophet is not a good benchmark; however, we wanted to use it because it is one of the most used libraries in forecasting. For that reason, we also tested the solution against AWS Forecast obtaining better results.

Besides the better performance and scalability, the pipeline we created considering all the stages of time series forecasting: preprocessing (e.g. missing value imputation), creation of static and dynamic features, forecast generation, and finally evaluation using data sets of important competencies. (https://github.com/Nixtla/tsfeatures)

On the deployment side, the entire pipeline can be quickly deployed in the user's cloud using terraform. This allows for less development time. (https://github.com/Nixtla/nixtla)

I can't find the TimeGPT-1 model.

LICENSE Apache-2

https://github.com/Nixtla/statsforecast/blob/main/LICENSE

Mentions ARIMA, ETS, CES, and Theta modeling

If you only have historical data: StatsForecast

I also recommend you check Nixtla's libraries, in particular StatsForecast and HierarchicalForecast. They offer a wide selection of forecasting models, and can work with multiple time series. Given that you're working with many products in a warehouse, I think the hierarchical forecast can be very useful, especially for the short time series (the ones that don't seem to have enough time stamps).

If you are mostly worried about time and use python you could try out Nixtla's statsforecast as it is very snappy. https://github.com/Nixtla/statsforecast

I was researching about using deep learning for time series forecasting applications when I came across two experiments by the Nixtla team. They showed that their traditional statistical ensemble (comprised of AutoARIMA, ETS, CES, and DynamicOptimizedTheta) beat a bunch of deep learning models (link) and also the AWS forecast API (link).

- https://nixtla.github.io/statsforecast/

Leaving these two repos here for anyone interested in trying decision tree regression or statistical forecasting baselines: - https://nixtla.github.io/mlforecast/ - https://github.com/Nixtla/statsforecast

In this reproducible experiment, we compare Amazon Forecast and StatsForecast a python open-source library for statistical methods.