TSIS 5.0

Known Problems

RT 35 Pre-timed Signal Control Timing.  Reference Offset to Signal Interval 1 (entry 2) does not translate from an existing TRF file into TRAFED for time periods subsequent to Time Period one. It will only translate from the value on RT 35 for Time Period one.  Only a single value is editable with TRAFED and that value will be output translated on all RT 35s for the given controller, regardless of which time period they are in.  The only work around for this problem is to edit the TRF file directly with a text editor.

RT 36 Pre-timed Control Codes.  Signal control codes for intervals greater than the number of intervals specified in Time Period one are not imported from existing TRF files into TRAFED in time periods subsequent to Time Period one.  In the TRAFED Pre-timed Controller dialog, and when output translated, they will appear as all-red phases, but with the correct duration.  For example, if Time Period one has 4 intervals and Time Period two has 6 intervals, intervals 5 and 6 in Time Period two will not be shown or written out correctly.  The work around for this problem is to correct the signal control codes for subsequent time periods in the Pre-timed Controller dialog or edit the TRF file directly with a text editor.

RT 186 Mean Dwell Time for Buses.  Mean Dwell Time and Bypass Percentage are not translated from an existing TRF file into TRAFED for any time periods greater than one, nor are they translated out. Only a single set of values are editable in TRAFED, and they are translated out on a RT 186 for Time Period one only.  The only work around for this problem is to edit the TRF file directly with a text editor.

The "CUMULATIVE NETWORK-WIDE BUS STATISTICS" table in the CORSIM output file does not always show the correct number of bus trips. It correctly reports the number of bus trips on routes that terminate in FRESIM, but reports zero trips for all routes that terminate in NETSIM.

Occasionally when running CORSIM, a message box is displayed that reads, "Not enough storage to complete this operation."  If you encounter this message, press the OK button on the message box and re-run the simulation.  If this problem persists, start TSIS with a "-c" command line argument.  This problem may exist when the number of files in a project is large.

Occasionally when running CORSIM on a Windows 95 or 98 platform, a message box is displayed that reads, "Remote procedure call failed."  If you encounter this message, press the OK button on the message box and re-run the simulation.  If this problem persists, start TSIS with a "-c" command line argument.  This problem may exist when the number of files in a project is large.

Popup tool tips for the tool buttons do not appear unless the Welcome page is the top page in the output view or the output view is hidden.  However, tip text is displayed in the status bar, regardless of the state of the output view.

The values for two FRESIM link measures of effectiveness (MOE), Delay Time and M/T, are different between the TRAFVU display and the CORSIM output file.  In most cases the reported values are only slightly different, however, the CORSIM output file values should be used.

User comments embedded in the TRF file will not be translated into TRAFED.

The order that records appear in a translated TRF file may not be the same order as the records in the original TRF file.

Nodes will have a red border in TRAFED until the user opens the node properties and reviews the turn volumes or sets the input volumes for each approach link.  TRAFED does not create a Record Type 21 for a link unless the user has viewed the turn volumes.

TRAFED will generate a warning concerning turn volumes while translating links designated as an interchange.  This warning can be ignored as the file is generated correctly.

The following list contains the CORSIM record types that are not fully implemented in TRAFED at this time:

           -  RT 52 Load Factors for Vehicle Occupancy.  By design, we translate this data into TRAFED and translate it out to a  CORSIM file on RT 58 Vehicle Type Specifications.

          - RT 172 Environmental Tables.  Existing TRF files containing RT 172 information will have that data carried along with the test case in the TRAFED file and exported to the modified TRF file.  There is no way to edit the RT 172 data at this time.  We have provided an interface that allows you to select an external file containing a set of RT 172 records.  The file does not have to be a valid CORSIM file, i.e., it may just contain the RT 172 data and nothing else.

        - RT 173 Maximum Acceleration Tables.  Existing TRF files containing RT 173 information will have that data carried along with the test case in the TRAFED file and exported to the modified TRF file.  There is no way to edit the RT 173 data at this time.  We have provided an interface that allows you to select an external file containing a set of RT 173 records.  The file does not have to be a valid CORSIM file, i.e., it may just contain the RT 173 data and nothing else.