darts VS tsfeatures

Don't use an LSTM. Get up to date with SoTA methods and read the papers in the field. LSTMs are not the way forward. Read the papers I suggested. It would be very useful to come to grips with both the Time Series Repository (https://github.com/thuml/Time-Series-Library) and Darts (https://github.com/unit8co/darts) as these are widely used for research and in industry.

As others have pointed out, Prophet is not a particularly good model for forecasting, and has been superseded by a multitude of other models. If you want to do time series forecasting, I'd recommend using Darts: https://github.com/unit8co/darts. Darts implements a wide range of models and is fairly easy to use.

The problem with time series forecasting in general is that they make a lot of assumptions on the shape of your data, and you'll find you're spending a lot of time figuring out mutating your data. For example, they expect that your data comes at a very regular interval. This is fine if it's, say, the data from a weather station. This doesn't work well in clinical settings (imagine a patient admitted into the ER -- there is a burst of data, followed by no data).

That said, there's some interesting stuff out there that I've been experimenting with that seems to be more tolerant of irregular time series and can be quite useful. If you're interested in exchanging ideas, drop me a line (email in my profile).

3. darts

Looking forward to checking this out! How does this compare with darts[1]?

[1] https://unit8co.github.io/darts/

Darts is an open-source Python library by Unit8 for easy handling, pre-processing, and forecasting of time series. It contains an array of models, from standard statistical models such as ARIMA to deep neural networks. https://unit8co.github.io/darts/

active support

The new Forecast menu, featuring the open-source Darts Time Series library, offers script-friendly functionality. It's also easy to use. Don't have any data to load yet? Enter through the Stocks or Crypto menus.

I would recommend Darts in Python [1]. It's easy to use (think fit()/predict()) and includes

* Statistical models (ETS, (V)ARIMA(X), etc)

* ML models (sklearn models, LGBM, etc)

* Many recent deep learning models (N-BEATS, TFT, etc)

* Seamlessly works on multi-dimensional series

* Models can be trained on multiple series

* Many models offer rich support for probabilistic forecasts

* Model evaluation is easy: Darts has many metrics, offers backtest etc

* Deep learning scales to large datasets, using GPUs, TPUs, etc

* There's even now an explainability module for some of the models - showing you what matters for computing the forecasts

* (coming soon): an anomaly detection module :)

* (also, it even include FB Prophet if you really want to use it)

Warning: I'm probably biased because I'm Darts creator.

[1] https://github.com/unit8co/darts

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)