Part of the preprocessing that's done for the crossborder model involves rearranging an old CT-RAMP input file into something that ActivitySim can understand. However, the tour scheduling component of the crossborder model is set to read a different file. Pull request #339 removed this inconsistency, but there were changes in the results so pull request #357 undid this change. Some things to consider:
- Is the crossborder preprocessing correctly rearranging the CT-RAMP input file?
- If the answer to question 1 is yes, should we update that file?
- Should we just get rid of the reformatting of the file and save the file in the ActivitySim format?
Part of the preprocessing that's done for the crossborder model involves rearranging an old CT-RAMP input file into something that ActivitySim can understand. However, the tour scheduling component of the crossborder model is set to read a different file. Pull request #339 removed this inconsistency, but there were changes in the results so pull request #357 undid this change. Some things to consider: