-
Notifications
You must be signed in to change notification settings - Fork 12
Committing to Daysim
Ben Stabler edited this page May 12, 2017
·
19 revisions
- Create an issue describing the problem/issue/bug
- If you don't have write access to the repo, then first fork the repo and work in the fork.
- Commit all changes for the issue to a new branch, named something related to the problem/issue/bug, for example trip-mode-fix
- When ready to add these into Daysim proper, commit the changes to the develop branch. If working in a fork, then issue a pull request for us to review.
- A commit to the develop branch automatically runs the test system
- If pass, then the test system merges develop into master. Close the issue if applicable.
- If fail, then correct and re-commit to develop.
Note that the master branch is write protected and can only be written to by the DaySim-Jenkins-user by Jenkins after the tests pass.
- Input Data
- Developer's Guide
- Standard Technical Documentation
- 2.1 Users Guide
- 2.0 Users Guide
- 1.8 Users Guide
- Model Variable Descriptions
- Changes to handle AVs and paid ride share mode
- KNR and TNC to transit implementation
- Telecommute Model
- Estimation Mode
- Distributed Setup
- CI Test System TRB Poster