-
Notifications
You must be signed in to change notification settings - Fork 99
Project Meeting 2023.04.06
Michelle Bina edited this page Apr 5, 2023
·
5 revisions
- Ending the activitysim_resources git monorepo.
- One giant repo with 10's of GB of files from multiple agencies is inconvenient to manage.
- Tracking data changes in Git (even with LFS) is mostly unnecessary
- When our monthly bandwidth is exhausted, users (including the CI testing) are locked out of the data until the next month
- Maybe replace with per-agency repos and/or S3 buckets or similar, possibly independently managed? e.g. activitysim-prototype-mtc
-
Do we want to continue to develop/maintain 3-zone model code?
If no participating agency is planning on using this formulation, we should consider ending support for it ASAP to allow that time to be spent supporting other more useful things.
-
Is validation testing against TM2 results at scale a thing we want to do?
The BayDAG PR included a number of component level tests that are backed by comparisons against TM2 results at scale. The datasets for these tests are large and it is unclear whether they can be supported in the CI package.