[DO NOT MERGE] Experimental Design for new v2 API - #2398
Conversation
|
I still need to add forecaster etc. I have already added what i think will be added to this PR in the description. I willl update the desc if something changes |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
Thanks for the review @CloseChoice!
The current branch is just a Proof of concept, and if you all like it then we can create complete workstreams and implement each feature step - by - step |
| "outputs": [], | ||
| "execution_count": null, | ||
| "source": [ | ||
| "!pip install git+https://github.com/phoeenniixx/pytorch-forecasting.git@ptf-new-design" |
There was a problem hiding this comment.
general best practice suggestion: jupyter notebooks should not modify the runtime environment...
There was a problem hiding this comment.
yes, this was intentionally added so that people can run this notebook direclty in colab as well if they want to. As we are not going to merge this, I thought it provides the reviewer some flexibility (not setting up ptf in their env) and then pulling the branch.
fkiraly
left a comment
There was a problem hiding this comment.
Very nice! I think this is great!
I have one question though:
- why is
TimeSeriesno longer aDataset? Is there anything that forces us to move away from standard APIs resp classes? I do not see anything that we could not do with adataset
I think I also think in future, we can refactor this datatype to be more "generic" (removing Also, we already have a Private dataset class for each Datamodules, and if we loose anything on not having What do you think? should we move back to it being |

This PR tries a new prototype for new design.
Created
_prototo have the files with major changes and some minor changes (like toEncoderDecoderDM) has been made in place.NOTE
This is a prototype - not to be merged as here the idea is just to get a minimal working state of the design to test out how it feels. I have done somethings which will not happen in ACTUAL implementation. Like
BaseForecasteris inheriting fromBasePkgwhich will not happen in actuality asBaseFroecasterwill REPLACEBasePkg._protofolder withForecaster,TimeSeries_datatypeetc files. which will be present in their designated folders and not in this folderTimeSeries_datatypewill be renamed toTimeSeriesif we decide to move on with this planWhat should a reviewer concentrate their feedback on?
Just the notebook and try out the vignettes and play around with it. This PR is not meant for the "code review" but just for the review of the vignettes and design
Try the notebook on colab (i have added a cell to install the branch as well)
AI Generated, so it SHOULD NOT BE MERGED
Only raised to try out the new interface and get feedback. If approved, will be implemented over a stack of PRs :)