> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/deep-learning/deep-neural-time-series.md).

# Deep Neural Time Series

Forecasting a series with a deep network does not have to mean building an LSTM from scratch. This page follows one library, NeuralProphet, from its documentation to a quick guide and then to tuning it.

The same notes are in [LTSM for time series](https://www.mlcompendium.com/predictive-ml/forecasting.md#ltsm-for-time-series).

The reference for NeuralProphet is [NP Docs](https://neuralprophet.com/code/forecaster.html), the NeuralProphet class documentation. With the API known, [Optimizing Time Series Forecasting with NeuralProphet: A Quick Guide](https://medium.com/@miritrope/optimizing-time-series-forecasting-with-neuralprophet-a-quick-guide-a08afe8216ac) is Miri Trope's quick guide to using it well. The last step is the settings: [Hyper Param Tuning](https://medium.com/eni-digitalks/unlock-the-neuralprophet-potential-hyperparameter-tuning-1905ccb87537) is Lavinia Guadagnolo on finding the optimal hyperparameters for a NeuralProphet forecast, which means knowing what each parameter does, where to set its values, and how they interact.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.mlcompendium.com/deep-learning/deep-neural-time-series.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
