TEAPAC by Strong Concepts, TRANSYT-7F Watch

TRANSYT-7F Watch...

This page identifies specific issues we are aware of regarding the TRANSYT-7F software published by the McTrans Center. Please be aware that this information is the best available at the time it is published, and may not be accurate for recently released versions. You might also check our User Discussion Forum for questions and discussions which may also be helpful.

This page is relevant to TEAPAC software users because the PRETRANSYT function of TEAPAC creates data files for the TRANSYT program from an easy-to-use interface which allows data entry in easy-to-understand traffic terms on graphical screens. This data can also be used by other TEAPAC functions, such as PRENETSIM which prepares input files for CORSIM, PREPASSR which prepares input files for PASSER-II, PRETSPPD which prepares input files for TS/PP-DRAFT, PRESYNCHRO which prepares input files for SYNCHRO/SIMTRAFFIC, and SIGNAL which optimizes signal timings and phasings for HCM capacity analyses.

10/9/03 - Offset-Only Hillclimb Optimization Doesn't Work As Documented

TRANSYT-7F Rel 9 does not handle an offset-only hillclimb optimization as documented. Release 9.5 offered a new feature to define the parameters to be optimized in field 8 of record type 5X, but when TRANSYT encounters an offset-only hillclimb optimization, it actually performs a split+offset optimization. This alternate action is performed without any notice to the user that the result is different than the requested action. The net result is that the user will have no knowledge that the splits have been altered unless he/she carefully reviews the optimization results.

At this time, the only practical way to achieve an offset-only optimization is to perform an offset-only genetic optimization, then simulate the resulting offsets (or to use record types 4 and 6 to define an offset-only optimization). This turn of events is particularly troubling for PRETRANSYT users because it would not be uncommon to do a 'blind' offset-only optimization (never viewing the TRANSYT results) where it is never apparent that the splits have been altered and that the optimum offsets returned by the process relate to these altered splits, not the original splits. Look for a free Ver 3.01 update to PRETRANSYT Ver 3.00 licensees to address this new problem sometime soon. In the meantime, the appropriate workaround is to define a genetic offset-only optimization with the Edit-System-Optimize dialog (select Offsets and set the optimization list to all zeros), then Export to TRANSYT, then Import the optimized offsets, then define a simulation with the Edit-System-Optimize dialog (select None), then Export to TRANSYT for the simulation of the optimized offsets.

7/23/02 - Long Phase Times Don't Display in Output

TRANSYT-7F Rel 9.5 (and probably earlier versions) does not display phase times greater than 99.9 seconds in the output. When the actual phase time is greater than 99.9 seconds the output field displays as ****. The time displays correctly in a related error message. For TEAPAC users, the significance is that the Import function of PRETRANSYT reads the output file when importing phase timings, so the Import function will not work correctly when optimized phase times exceed 99.9 seconds. This problem is normally solved by letting SIGNAL2000 optimize the phase times based on the 2000 Highway Capacity Manual, thus eliminating the need to import phase times from TRANSYT. SIGNAL2000 can establish the worst allowed level of service for all of the critical movements and assign any time available after this is accomplished to designated priority movements. Then when PRETRANSYT reads the SIGNAL2000 files with these timings it merely instructs TRANSYT to optimize offsets-only so the SIGNAL2000 phase times remain unchanged.

6/21/00 - Certain Valid Input Files will Crash Running Under Windows NT

Certain input files which run fine under Rel 8.2 of TRANSYT-7F running under Windows 95/98 will cause TRANSYT to crash when the same file is run under the same verion of TRANSYT running under Windows NT. The problem is typically (but not always) triggered by specifying left-turn sneakers on record type 29. The next release (8.2a?) due in about four weeks should contain a fix.

2/18/00 - Folder Name Length Limits (all DOS versions)

DOS versions of TRANSYT-7F require that names of folders and sub-folders do not exceed eight characters in length, otherwise the files and/or sub-folders within that folder cannot be seen by TRANSYT. This applies if you are using McT7F or the Export AUTO feature of PRETRANSYT. In the case of Export AUTO from PRETRANSYT, you will see the TRANSYT screen flash briefly, but will not get any results or messages from TRANSYT for this condition.

2/1/00 - PPD.PAR Configuration File Limitations (all versions thru 8.2)

It is not uncommon to have a comma appear in an agency name, such as Your Company, Inc. When entering your agency name in the PPD program configuration screen, however, do not enter any commas, or the PPD program will not function properly. For example, one symptom which has been observed is that difficulty is had producing multiple PPD's from a single PPD file with a related need to delete the PPD.PAR file each time a PPD is printed.

this page last updated April 15, 2019