madtoinou

Hi @SaltedfishLZX, This feature is not yet implemented, I added it to the roadmap. If you have time and would like to contribute to Darts, feel free to tackle it...

Hi @AndrewJGroves, I think that including this information as covariates is the most appropriate and straight-forward approach.

Hi @gitbooo, The error message seems to indicate that `test_targets` does not contain the same number of static covariates as the series used during training. In order to use your...

Hi @zhoujs93, This feature is already tracked by issue #1175, where some workarounds are also shared. I started working on it but the end of the year is quite busy...

Hi @ETTAN93, Thank you for raising this issue. `gridsearch()` does not support the optimization of the parameters of the wrapped model at the moment, I added it to the roadmap.

Hi @adahan, Thanks you for this feature request, I think it's a partial duplicate of #2004. I really like the approach you are describing and would like to know your...

@dennisbader Yup, no problem, should be trivial to implement a progress bar when there are several series. @ETTAN93 `verbose` is only supported by `TorchForecastingModel.fit()`, `RegressionModel` verbosity is usually defined in...

Hi @hberande, As explained in the table summarizing the models available in darts [here](https://github.com/unit8co/darts#forecasting-models), NBEATS and NHiTs do not support future covariates at the moment. I don't think that modifying...

It should be, but you might diverge from the initial architecture and there is no guarantee of performance gain. Be careful about data leakage. #1943 links to a paper presenting...

Hi @Tristanjmeyers, This features is already implemented in `TimeSeries.slice_intersect()` ([doc](https://unit8co.github.io/darts/generated_api/darts.timeseries.html?highlight=timeseries#darts.timeseries.TimeSeries.slice_intersect)), you'll have to call it several times if you have more than two series. I like the idea of offering...