Should timechop have a cron-like interface?
Open
needs-discussion
- Dominant language
- Jupyter Notebook
- Stars
- 201
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
If we plan to share `triage` with the partners, the current implementation of timechop recreates all the matrices (because you are moving the last day) everytime that you update the experiment's temporal configuration.
If the partner (or ourselves) want to run the experiment "the 5th of everymonth" timechop should take that information *don't* create new matrices and just train with the new data. Also this interface potentially is more easy to explain that the actual setup.
But what are your ideas?
Contributor guide
Assessment
This issue has not been assessed yet.