pytorch-forecasting VS pytorch-lightning

Source: Conversation with Bing, 4/5/2023 (1) jdb78/pytorch-forecasting: Time series forecasting with PyTorch - GitHub. https://github.com/jdb78/pytorch-forecasting. (2) Time Series Prediction with LSTM Using PyTorch - Colaboratory. https://colab.research.google.com/github/dlmacedo/starter-academic/blob/master/content/courses/deeplearning/notebooks/pytorch/Time_Series_Prediction_with_LSTM_Using_PyTorch.ipynb. (3) time-series-classification · GitHub Topics · GitHub. https://github.com/topics/time-series-classification. (4) PyTorch: Dataloader for time series task - Stack Overflow. https://stackoverflow.com/questions/57893415/pytorch-dataloader-for-time-series-task.

Temporal fusion transformer https://github.com/jdb78/pytorch-forecasting

Pytorch-forecasting

To name a few: https://github.com/jdb78/pytorch-forecasting, https://github.com/unit8co/darts, https://github.com/Nixtla/neuralforecast

I'm a data trainee at this organisation. I wrote my master thesis about using an event clustering mechanism to enrich an existing dataset to improve short-term demand predictions, using Pytorch Forecasting using the temporal fusion transformer component, and LightGBM (and compare the models with and w/o the event feature, so 4 runs in total).

Darts is a pretty nice one. I've recently been using pytorch-forecasting for larger models like the Temporal Fusion Transformer. https://github.com/jdb78/pytorch-forecasting

def on_validation_end(self, trainer: Trainer, pl_module: LightningModule) -> None: # Trainer calls `on_validation_end` for sanity check. Therefore, it is necessary to avoid # calling `trial.report` multiple times at epoch 0. For more details, see # https://github.com/PyTorchLightning/pytorch-lightning/issues/1391. if trainer.sanity_checking: return

Under the hood, the ModelWrapper object will create a ML model based on the config (so far, an XGBoost model and a PyTorch Lightning model). Each of those will have a wrapper that conducts training and evaluation (since from my understanding of Lightning, Trainers are required to be outside of the class). In lack of a better name, I call these wrappers Fitters. For uniformity, I thought about adding a common interface IFitter, which is inherited by all model wrappers as outlined below.

Join their Slack to ask the community questions and check out the GitHub here.

Pytorch lightning benchmarks against pytorch on every PR (benchmarks to make sure that it is mot slower.

There is already a ton of momentum around automating ML workflows. I would suggest you contribute to a preexisting project like, for instance, PyTorch Lightning or fast.ai.

Is the problem the sheer number of options, or the fact that they are all together in one place? Would it be better if they were organized into the different trainer entrypoints (fit, validate, ...)? If that is the case, there was an RFC proposing this which you might find interesting, feel free to drop by and comment on the issue: https://github.com/PyTorchLightning/pytorch-lightning/issues/10444

I wanted to make a quick performance comparison between the GPU (Tesla K80) and TPU (v2-8) available in Google Colab with PyTorch. To do so quickly, I used an MNIST example from pytorch-lightning that trains a simple CNN.

We've noticed GPU 0 on our 3 GPU system is sometimes idle (which would explain performance differences). However its unclear to us why that may be. Similar to this issue

If you want a good example for reference, take a look at Pytorch Lightning's readme (https://github.com/PyTorchLightning/pytorch-lightning) It answers the 3 questions of "what is this", "why should I care", and "how do i use it" almost instantly