-
Notifications
You must be signed in to change notification settings - Fork 12
Distributed Setup
Ben Stabler edited this page Apr 11, 2017
·
1 revision
DaySim can be run across multiple Windows machines by using the DaySimController. It uses Windows RPC to call DaySim on each remote machine using DaySim's s=, e=, and i= command line arguments. Each remote machine gets a batch of households. The DaySimController first reads the inputs to determine the batch sizes for the remote machines. Then it uses WMI and RPC to run Daysim remotely. Then it reads the remote machine output files and merging them back into output files on the master machine.
Instructions on how to run it are in the command line '-h' menu.
C:\projects\chattanooga_daysim_test>DaySimController.exe -h
-c, --configuration=VALUE Path to configuration file
-p, --printfile=VALUE Path to print file
-h, -?, --help Show help and syntax summary
DaySimController requires these additional properties:
RemoteUsername=your_username
RemotePassword=your_password
RemoteMachines=pormdlppw01|E:\test\Daysim.exe|/c=config.properties|/p=dclog.txt,sdmdlppw01|E:\test\Daysim.exe|/c=config.properties|/p=dclog.txt
RemoteCopySPFilesToRemoteMachines=false
All machines, including master, need the exact same folder and file setup
This includes inputs since inputs are not copied from the master to the slaves
Each machine's folder needs to be shared so DaySim can access it remotely
Exceptions, or hanging, is probably due to configuration/path issues
It is best to setup with the simplest possible file/folder setup
Windows RPC server must be enabled on the remote machines
- 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