|
|
TSIS-CORSIM
Version 6.0 Known Issues Please contact McTrans with any new problems found that may be added to this list. Some of these errors may be corrected in the next release, subject to priorities (suggestions welcome). This list does not include brand-new features that have been added. 1. When actuated timing plans are transitioned between time periods, the CORSIM 6.0 transition logic sometimes may not function properly for certain offsets.* 2. When coordinated-actuated timing plans have lead-lag phasing, TRAFED 6.0 may not properly load or save the data. CORSIM can still simulate lead-lag actuated coordination properly if the TRF file is coded correctly. To code coordinated-actuated timing plans with lead-lag phasing, try one of the following four options instead of TRAFED: a) HCS pre-processing, b) TRANSYT-7F pre-processing, c) TSIS Next, d) TSIS TextEditor. 3. If the input file
requests FRESIM conflict data, but only contains
NETSIM data,
CORSIM 6.0 will crash after simulation has been completed.* 4. When using the
output processor, turning
off all checkboxes (Generate OUT, Generate CSV, etc.) on the Multiple
Run Properties tab is sometimes necessary for the output processor to
compute results normally. 5. CORSIM computes Bus Travel
Time Per Vehicle in minutes per vehicle, but the Output Processor
labels FRESIM Link Bus Travel Time Per Vehicle in seconds per vehicle. 6. CORSIM build 507 can now explicitly simulate triple
turn pockets, but sometimes vehicles will move into the wrong
downstream lane. This problem can be avoided by coding lane
alignments, which force vehicles to enter specific downstream lanes.** * indicates
that the problem is fixed in build 507, which can now be downloaded |