Handle stop changes
Open
enhancement
- Dominant language
- CSS
- Stars
- 22
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We need to handle stop changes so we can use the fit from past data to predict for the future. Right now we are using route 6 as we develop and only one stop has changed from our training set (currently using picks N-21 and N-22) to test (N-25 and N-26). This stop goes from tageoid 5316 to 17705 and we are just recoding it. We need to perform a matching for all stops that will be used in the simulation.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.