:TEAPAC Ver 8.61 21JAN14
>Improved Modeling of Shared-Permitted Left Turn Operation.
Continuing improvements initiated at the end of 2012 have been made that affect the results obtained for single-lane and two-lane approaches with shared permitted left-turn operation. The changes were approved by vote of the Highway Capacity and Quality of Service Committee and incorporated by Errata in the 2010 HCM. The result of these changes is that the HCM now provides better corroboration of its results with observed behaviors of these special cases in the field.
Related changes affect the results for exclusive left-turn lanes with permitted or protected-permitted operation AND opposed by a single lane approach, as well as conditions when an approach has no shared lanes and no detection.
:TEAPAC Ver 8.60 04JUL13
>Analyze Dialog Text Expanded to Include Coverage by 2010 HCM.
The capacity analysis dialog (Analyze) has had its text updated to properly reflect the option of the analyst to be able to select either the 2000 or 2010 Highway Capacity Manual (HCM) as the method for the analysis, not just the 2000 method, as previously represented. The desired method can be selected with an Edit-System-Output menu entry.
>Traffic Impact Analysis Example Data File Updated.
The example data file for traffic impact analysis (TrafficImpactAnalysis.tpc) has been updated so that the abbreviations for entries which are used are compatible with the newest command entry data (GreenAverages, in particular) and thus the file works properly with the latest version of TEAPAC Complete. In addition, the main intersection is selected when the file is opened and appropriate phasings and cycles have been provided for all intersections. Lastly, the north and south approaches have been adjusted so that the approach angles better fit the underlying bitmap aerial photo which is used by the example, especially for animation.
>Default Support for Newest TSIS/CORSIM 6.3.
The latest version of TSIS/CORSIM, version 6.3, has been set up as the default supported version by TEAPAC Complete, especially for the new installed folder which is used by the default TSIS installation.
>Network Management Dialog Updated for Clearer File-Save Actions.
Several entries which can be made in the Network Management dialog (accessed from the Setup... button in the main window) are only relevant to the current action of the user, and are not saved in or restored from any data file. This action has been made more clear by the text of the dialog, and the user is no longer prompted to do a File-Save when changes are made to these variables which are not actually saved anywhere.
Build 01 - 08JUL13
>Powerful New Feature Allows Better Export and PlotTSD Modeling for Actuated.
The 2010 HCM method in TEAPAC computes the average phase duration for actuated signals. The default behavior of TEAPAC is now to save those average durations in the new GREENAVERAGES entry and use those average durations for all EXPORT and PLOTTSD actions. This means that the time-space diagram from PLOTTSD will now represent average phase times, not maximums, and modeling or optimization by third-party programs such as TRANSYT, PASSER-II and TruTraffic/TSPPDRAFT will now be able to perform their functions with these HCM averages as opposed to using maximums, which has been the normal use of these programs through the years.
In order to accomplish this, signal timings must be entered By-Movement, and normally the GREENAVERAGES dialog is populated automatically by the ANALYZE or DESIGN commands for a 2010 HCM analysis. For programs which are capable of modeling actuated operation in some fashion from data exported by TEAPAC (such as Synchro, TRANSYT or PASSER), the GREENAVERAGES are exported instead of GREENTIMES (maximum settings) and the actuated operation is disabled by setting recall-to-max, as necessary (ie, Synchro). If the normal actuated model of the third-party program is desired, this should be selected with the <Actuated> setting of the SIMULATION dialog, in which case GREENTIMES will be exported.
If the GREENAVERAGES values are intended to be used for EXPORT per the discussion above, but the GREENAVERAGES all have values of zero, the GREENTIMES values will be used instead, with a warning message to that effect. Normally this situation can be addressed by using the ANALYZE command for 2010 HCM to compute the average green times prior to EXPORT. However, if the EXPORT is specifically intended to represent maximum timings instead of average phase durations, then the GREENAVERAGES can be set to zero intentionally to achieve this effect.
>Export to New HCS2010 File Format Now Supported.
The new data file format which is used by HCS2010 (Ver 6.41) is now supported for direct export of TEAPAC data to HCS2010, both for signalized and unsignalized locations. The default Options-Setup file path has been updated accordingly, as has the support for the new Streets.exe module when using the RunHost button in the HCSExport dialog.
>New RTINFLUENCES Entry Allows Greater Control Over Permitted LT Modeling.
A new data entry dialog has been added to the [Approach] group of entries called RTINFLUENCES in support of a new HCM 2010 feature that has been approved. When an exclusive right-turn lane exists on an approach, the analyst can use this input to indicate whether traffic in the right-turn lane influences the permitted left-turn drivers' gap acceptance on the opposite approach. An entry of 'Yes' indicates this influence exists (this is the default). The determination that the exclusive right-turn lane does not influence gap acceptance should be based on knowledge of local driver behavior, traffic conditions and intersection geometry.
>Other Minor Refinements to HCM2010 Methodology Implemented.
Minor refinements and clarifications to the HCM2010 methodology which have been published to-date (Version 7.11 of the TRB HCM computational engine) have been implemented in order to keep TEAPAC 2010 as precisely compliant as possible. Users may see minor changes to answers as a result of these changes, but significant differences should be limited to very specific cases documented for the engine changes.
>Minor Bug Fixes.
HCM 2010 analyses require timing inputs be made using the By-Movement style, while HCM 2000 analyses permit either By-Movement or By-Phase timing entry. When using an old data file with prior timings entered By-Phase for a HCM 2010 analysis, the user is prompted whether or not the program should be allowed to convert the timings on-the-fly to the required By-Movement style, and circumstances have been discovered where this on-the-fly conversion is not performed correctly. This has been corrected. Also improved is the ability to abort an entire multi-intersection analysis when this conversion is not desired, as well as not checking or reporting intersections which are not included in the current subsystem for the need for such conversion.
When an HCM 2010 capacity analysis is being conducted for a situation which includes a free-flow right turn, the capacity analysis inadvertently included the satflow for the free-flow lane as part of the reported satflow for the adjacent through lane group. This did not affect the validity of the results, as it was only an output representation error, and it has been corrected.
>Default Approach Speed Used for HCM2010 Calculations.
When an approach speed limit is not provided via the Network dialog, rather than using the default speed of 0 mph in HCM2010 calculations, a speed of 35 mph is now used to obtain more sensible results for those elements of the HCM2010 analysis that rely on a speed input. An example of this is how the speed limit is used to modify the calculation of Maximum Allowable Headway in the actuated model of the HCM2010. Using 35 mph produces more appropriate results than using 0 mph.
>Minimum Detector Length Enforced.
User inputs are checked to make sure that a non-zero detector length will be used in a HCM2010 capacity analysis, with a minimum value of 1 foot enforced. This prevents the HCM2010 methodology from delivering nonsensical results.
:TEAPAC Ver 8.55 10APR13
>HCM2010 Logic Change Behaves Better for 1-Way Streets and T-Intersections.
An adjustment has been made to the HCM2010 logic prescribed by the Highway Capacity Manual so that conditions which do not include all movements at an intersection behave better in an HCM capacity analysis. This includes certain situation which can arise at T-intersections and intersections which include at least one 1-way street. Prior HCM2010 logic could produce conditions which cause 0^0 math errors which are likely to crash the program. The prescribed fix corrects this situation and prevents such math errors and/or crashes.
:TEAPAC Ver 8.54 29DEC12
>HCM2010 Signalized Methodology Updates per HCM Committee Changes.
Adjustments to TEAPAC's HCM2010 signalized intersection methodology have been made in accordance with approved changes to the methodology which have been made by the HCM Committee (Signalized Subcommittee) of the Transportation Research Board (TRB) in 2012. Many of these changes are incidental and will not cause noticeable changes to TEAPAC's results, but some may affect a small number of circumstances dramatically and with more appropriate results. Situations which contain permitted lefts opposed by multiple lanes with a shared left-through, permitted left turns in general, shared left-through lanes, movements that terminate a barrier with different clearance times, defacto left turn lanes, or exclusive right turn lanes with adjacent parking or local buses are most likely to reflect these changes with different results than before. The export to the TRB computational engine has also been updated to work with the latest version of the engine, Ver 4.3.
>Fix for Free-Flow Turns.
Situations with free-flow turn lanes have been found to generate inappropriate results under some circumstances. This problem has been corrected with this release of TEAPAC.
>Fix To Detect TruTraffic Ver 10.
Due to a change in the formatting of certain files in TruTraffic Ver 10, TEAPAC was incorrectly detecting that version of TruTraffic on a user's system and exporting the wrong format of data, and thus generating incorrect results. This problem has been corrected with this release of TEAPAC.
:TEAPAC Ver 8.53 19NOV12
>Direct Support for 'CORSIM-for-HCS'.
TEAPAC now links successfully to CORSIM when it is installed as part of HCS2010, making use of all of the functionality which CORSIM-for-HCS provides.
>Default Folders for Third-Party Programs Updated to Match Latest Versions.
The default installation of TEAPAC Complete 2010 now uses updated default folder locations for HCS2010, TRANSYT7F, CORSIM and Tru-Traffic which match those which the most recent versions of these programs use by default. Consistent with installation on the most modern 64-bit Windows installation, these are placed in the C:\Program Files (x86)\ folder, with the following subfolder names - \HCS2010\HCS\, \HCS2010\T7F11\, \FHWA\TSIS6.3\ and \Tru-Traffic 10\. Use of \Tru-Traffic 10\ is consistent with the special instruction in the Tru-Traffic 10 installation notes for installing it for all users on a given computer.
:TEAPAC Ver 8.52 12JAN12
>VISSIM Ver 5.3 and 5.4 Now Supported Directly.
The new default folder name which is used by the latest version of VISSIM (Ver 5.4) is now included as the default in TEAPAC for Export to VISSIM. Also, additional information (VehClasses) which is newly required by both VISSIM 5.3 and 5.4 is automatically included in the data file created by TEAPAC for any version of VISSIM.
>TruTraffic Ver 9 Now Supported Directly.
The new default folder and executable file names which are used by TruTraffic Ver 9 are now included as the defaults in TEAPAC for both Export and Import to/from TruTraffic. New information which is now included in the TruTraffic CSV files which are used for Importing are now also processed correctly.
>TRANSYT Rel 11 Support Improved for Genetic Optimization.
The new format of genetic optimization results which was adopted by TRANSYT in Release 11 has been accommodated in TEAPAC so that genetic optimization results can now be imported into TEAPAC, including optimized offsets as well as split times if they were optimized.
The Import of genetic results has also been enhanced so that results for node numbers which exceed the TRANSYT limit of 99 (and are therefore mapped by TEAPAC into temporary new node numbers for TRANSYT) can now also be imported back into TEAPAC, as above. In order to do this, the AUTOmatic Export and Import options in TEAPAC must be used to circumvent the problem of multiple file names which are employed by TRANSYT for a genetic optimization.
:TEAPAC Ver 8.51 17JUN11
Build 08 -
>Data Files With Old Style Timing Input (ByPhase) Now Read Correctly.
Data files which have been saved previously by any prior TEAPAC version or program and which used the older style of timing input where timings are given for each HCM phase (ByPhase) rather than each Nema movement (ByMovement) were saved in such a way that backwards compatibility with older TEAPAC programs like PRETRANSYT, PRESYNCHRO, etc. was retained. With the change of the default entry mode from ByPhase to ByMovement in Ver 8.51, TEAPAC was not reading the ByPhase timings from these data files correctly, processing the un-designated timings as if they were the new default, ByMovement. This has been corrected so that un-designated (ByPhase) timings are both read and retained as ByPhase timings. Further, since more recent versions of these older TEAPAC programs were able to read the newer formatted data files, all timings which are saved are now fully-designated as either ByPhase or ByMovement, so no ambiguity exists in the future.
Any analyses made by prior Ver 8.51 releases (Builds 01-06) after opening files with ByPhase timings should be checked carefully, although it should be readily apparent that the timings are not correct in the analysis. Further, any files with ByPhase timings that have been opened and re-saved by prior Ver 8.51 releases should be checked to make sure that the proper timings have remained intact in the files.
Under certain circumstances, TEAPAC would adjust the first phasing in the SEQUENCES list (if more than one sequence code was listed for optimization) to better match the input timings, but this adjustment might occur prior to the actual entry of the timings and an inappropriate change would be made where the adjusted sequence code did not match the timings provided. This errant behavior has also been fixed.
>Prevent Rounding to Zero When Computing Analysis Volumes.
Every TEAPAC analysis computes the analysis volumes which can include multiplicative factors (VOLFACTORS) and additional volumes (VOLADDITIONALS) beyond the basic VOLUMES entry which is made. In a case where the computation results in a non-zero result, but one that rounds to zero (such as a VOLUME entry of 1 and a VOLFACTOR entry of 0.4), setting the analysis volume to zero can have unintended consequences, since TEAPAC will make certain decisions based on the existence or non-existence of a volume entry (non-zero vs. zero). With this in mind, a change has been made that prevents non-zero volume computation results from rounding to zero by setting the result to 1 vph in these cases. In a case where the actual computed result is exactly zero, such as with a VOLFACTOR equal to 0.0 or a VOLADDITIONAL equal to exactly the negative value of an entered VOLUME, the zero result will be allowed so that intentional zeroing of analysis volumes is still permitted.
>4-Digit Node Numbers Handled Properly for VISSIM Export.
A fix has been implemented so that use of 4-digit node numbers will be exported properly to VISSIM 5.10. Problems exporting to VISSIM 5.30 are still under investigation.
>Fix Split Phase Export to Synchro After HCM 2010 Change.
A change to the way split phase is handled in TEAPAC that was made for compatibility with the HCM 2010 method has caused problems exporting to Synchro - these problems have been fixed.
Build 04 - 24AUG11
>MinGap Added to Synchro Export.
The minimum gap setting (used for volume-density controllers by Synchro) is now exported for all controller types to avoid an error message in Synchro that suggests this setting must be at least as large as the vehicle extension, even if the controller is not a volume-density controller. The minimum gap is set to the same value as the vehicle extension.
>Chapter 2 Examples in Manual and Help Updated.
The initial example problems which appear in Chapter 2 of the TEAPAC manual and on-screen, context-sensitive help have been updated so they reflect the new default signal timing entry style which is now used. This is a 'by-movement' entry which matches the HCM 2010, rather than the previous 'by-phase' style for the HCM 2000. Both styles are still supported, and user data files of either style can be used with either HCM method in TEAPAC, but the example problems now match the HCM 2010 style. The example outputs in Appendix D have also been updated accordingly.
>Example Data File Modified.
The TEAPAC example data files which are provided with the software installation have been modified to reflect the correct phasing input style, now that the default input style has been changed from 'by-phase' to 'by-movement'. The example files previously used 'by-phase' for several intersections, but were not correctly notated to work properly with the new default.
Build 02 - 21JUN11
>HCM 2000 Method Retained When Older Data Files Opened.
Files saved with earlier versions of TEAPAC Complete (prior to Ver 8.50, or any other prior TEAPAC program) will not have any HCM method designated, since the 2000 method was the only method for these versions and/or programs. When these files are opened into TEAPAC Complete 2010, the HCM 2000 method will now be automatically selected so any subsequent analysis will be consistent with that performed when the files were saved. The method can be manually changed to 2010 with the Edit-System-Output dialog for Signal Analysis, and the method which is currently selected will be saved by any subsequent File-Save action. This change in behavior (in contrast to Build 01 below) will help make for a smoother, controlled transition to the use of the 2010 method on older data files which were started with the 2000 method. New problem data entry which follows File-New will default to the 2010 method, as before.
>Extra Debug Output Removed.
An unnecessary debug output window which was inadvertently left open has now been closed so it is not visible to the analyst.
Build 01 - 17JUN11
>Optimization Now Provided for TEAPAC Complete 2010.
TEAPAC's famous critical movement HCM delay optimization of green splits, cycle length and phasing has now been implemented in TEAPAC Complete 2010 for analyses based on the 2010 HCM methodology. Simply stated, the 2010 optimization method is utilized by the Results-Design function when 2010 method is selected, exactly the way Design has been used previously for the HCM 2000. The user now has the option of selecting either the 2000 or 2010 HCM methods for both capacity analysis and optimization.
A new format for the Results-Timings output in support of the new Design function is also provided so that the optimized 2-ring timings and critical movements are properly depicted, including a graphical timing bar which shows how the design cycle is sub-divided into splits (maximums or force-offs).
A special set of notes has been prepared describing some of the new considerations which have been brought to the table by the 2010 method in regards to both capacity analysis and optimization. These can be found in Appendix C of the Help-Contents menu or the printable pdf User Guide. The section title is Important Considerations for HCM 2010 Calculations, and it can be found as the second topic heading for the Signal Analysis section.
>HCM Method Defaults to 2010.
Now that TEAPAC Complete 2010 can do both an HCM-compliant 2010 capacity analysis and optimization of that capacity analysis (per above), the default methodology for a new problem entry will be the 2010 method. For problems entered and/or saved with the prior 2010 versions (Ver 8.50), the selected method at the time of the file save will be retained. However, files saved with earlier versions of TEAPAC Complete will not have any HCM method designated, so the current default for HCM 2010 will be in force unless the method is manually changed back to 2000 with the Edit-System-Output dialog for Signals. If the prior HCM 2000 methodology is desired to be retained for either capacity analysis or optimization for these older files, they should be opened with Ver 8.51 and changed manually to 2000, then re-saved so this selection is the designated methodology for any subsequent analyses with TEAPAC Complete 2010.
>Gapouts and DallasLefts Included in Phasings Menu.
The GapOuts and DallasLefts entries for TEAPAC Complete 2010 have been added to the Edit-Phasing submenu so that appropriate entries can be made in support of these options as part of the HCM 2010 methodology. These inputs are currently not relevant to any other analyses performed by TEAPAC Complete 2010.
>Better Rounding for Cmin, Covers Fractional Clearance Requirements.
The minimum cycle length (Cmin) determination produced by the Results-Design function for either the 2000 or 2010 methods has been modified slightly so that the rounded cycle length which is displayed will always be large enough to cover any and all fractional green or clearance interval times. For example, if fractional interval timings previously produced an un-rounded Cmin result of 62.2 seconds, it would have had a rounded result reported as 62 seconds - this result will now be reported as 63 seconds.
>New Example Problem Demonstrates 2010 Method Better.
The Signal-Analysis.tpc example data file has been modified slightly so that it better illustrates some of the new features of the HCM 2010 method.
:TEAPAC Ver 8.50 25APR11
Build 04 -
>Official Release of TEAPAC Complete 2010.
Build 04 of TEAPAC Complete 2010 is the first official release of the program, with several minor fixes and enhancements to the 2010 capacity analysis of the initial PreRelease in May.
>2010 Capacity Analysis Improvements.
The 2010 Capacity Analysis output was incorrectly reporting HCM 2000 V/C ratios instead of HCM 2010 V/C's. This has been corrected. Also, timings which are optimized by the HCM 2000 method and subsequently analyzed with the 2010 method now show the 2000 critical movements correctly in the 2010 output, and a vertical bar in the 2010 phasing display which was sometimes missing for T-intersections is now displayed properly.
>Improved Determination of Phase Clearance Times for Shared Phases.
When timings are entered by movement instead of by phase (which is required by the 2010 method, and is an option for the 2000 method) for phases that have shared movements which have different clearance requirements, the most demanding clearance requirements (Y+Rc) are now assigned as the clearance times for the shared phase module. This can be especially apparent at T-intersections and 1-way legs (such as ramp intersections). These differences can also come into play when converting timings between the ByPhase and ByMovement entry modes, as well as after producing the TimingPlan output.
PreRelease 03 - 11MAY11
>First Advertised PreRelease of TEAPAC Complete 2010.
PreRelease 03 marks the first public release of TEAPAC Complete 2010 which follows extensive beta testing by select TEAPAC users. This release has full HCM 2010 capacity analysis capabilities. Optimization of timings and phasing is still temporarily disabled while we put the finishing touches on the new optimization method which the 2010 capacity method requires.
This release allows users to explore the many new aspects of capacity analysis that the 2010 HCM method brings to the table. All that is needed to perform a 2010 capacity analysis is to select the 2010 HCM method from the Edit-System-Output menu for Signal Analysis. Checking default values and/or entering values for the many actuated inputs which are now used by the method is highly recommended.
Users are encouraged to read about suggested techniques and considerations regarding using the new 2010 method which can be found in Appendix C of the Help-Contents menu or the printable pdf User Guide. The section title is Important Considerations for HCM 2010 Calculations, and it can be found as the second topic heading for the Signal Analysis section.
>Several Adjustments to HCM 2010 Implementation Made.
Several adjustments have been made to the implementation of the 2010 HCM method as a result of user testing on a wide range of input conditions. These include better modeling of laggin operations when a coordinated phase is on a north-south leg, better modeling of conditions when an entered minimum exceeds an entered maximum for fixed-time operations, better treatment of default parking conditions, prevention of crashes when satflows can't be calculated, and better column headings for the draft worksheet output which is presently available.
PreRelease 02 - 05MAY11
>Several Temporary Constraints on the Use of the 2010 HCM Method Removed.
The 2010 Capacity Analysis method has been enhanced to handle signals which have coordinated North-South phases, so now any coordinated signal can be analyzed. Also, the ServiceVolumes function has been re-enabled so that a report for 2010 saturation flow rates can be produced. Similarly, when a 2010 capacity analysis is performed, the 2010 saturation flow rates are placed in the SaturationFlows entry for use by other programs such as TRANSYT, PASSER and Synchro in teh same fashion that this is done for a 2000 capacity analysis. Lastly, although no 2010 version of HCS exists at this time, the HCSExport function has been re-enabled when a 2010 analysis has been selected so an Export to the 2000 HCS is still possible.
>Several Enhancements for Export to Synchro Have Been Implemented.
When T-intersections or 1-Way-intersections exist and a nema phase number has not been given to the thru movement on the stem of the T or 1-way leg, then the nema phase number given for the turns on the stem will be used, as expected. This fixes a problem in both Synchro and TruTraffic where the phases for the stem were not being exported properly if the thru movement did not have a nema phase number entered.
FreeFlow right turns are now exported correctly, ignoring the method documented in the Synchro manuals and using an obviously more correct technique.
Exported timings are rounded and corrected for rounding inconsistencies in several additional places, especially for Synchro 7, so that the cycle length deteremined by Synchro is the intended whole-second cycle without any fractional seconds due to rounding.
The cycle length used and exported to Synchro is now determined on an intersection-by-intersection basis so that the Synchro export is independent of the need for a consistent system cycle length, thus allowing multiple sub-systems with differing cycle lengths to be exported all together in a single export rather than separate exports, one for each sub-system.
The controller type is now determined and exported for Synchro Ver 7. This is not an option for a Synchro 5 or 6 export.
When exporting to Synchro with the TEAPAC Optimize option set to None (meaning either for simulation or for no optimization), the actual vehicle MinSplit is sent to Synchro for a possible optimization, even though no optimization is expected.
PreRelease 01 - 27APR11
>Initial PreRelease Version of TEAPAC Complete 2010.
The first PreRelease version of TEAPAC Complete 2010 is now available, incorporating the vastly new capacity analysis methods of the 2010 Highway Capacity Manual. While optimization for this method is not yet included, this version allows users to explore the many new aspects of capacity analysis that the 2010 method brings to the table. All that is needed to perform a 2010 capacity analysis is to select the 2010 HCM method from the Edit-System-Output menu for Signal Analysis. Users are encouraged to discuss their initial use of TEAPAC Complete 2010 with Strong Concepts for insights into using the new method and what the initial PreRelease version is capable of. Feedback is very much desired and appreciated.
>Default PassageTime Changed to 0.
The default value for a PASSAGETIMES entry has been changed from 3 to 0 to indicate the desire to use a default value as defined by the selected HCM method. For HCM 2000, this default is 3.0 seconds, while for HCM 2010 the default is 2.0 seconds. For data files which have already been created, if a self-selecting default value of 0 is desired, it will need to be entered manually since the prior default of 3.0 will be what is found in the file. It is recommended that a non-zero value be entered when the option to include a portion of passage time in the minimums is selected.
>Default Offset Reference Phase Number changed to 0.
The default offset reference phase number has been changed from 1 to 0, since with the 2010 method this input takes on a new and important meaning. A non-zero phase number indicates a coordinated signal, and a zero entry indicates an un-coordinated signal - whether the signal is coordinated or not plays a big role in the way the 2010 HCM method estimates phase durations.
>Enhancements and Fixes Incorporated.
Several enhancements and fixes were implemented in this release to address issues that were observed during the development of this new version. These include the following -
The cycle length used in producing the TimingPlan output for any intersection is now based on the cycle length for that particular intersection, rather than the designated SubSystem cycle length. This makes the results more meaningful for double-cycle locations and relieves the user from making sure that the MasterNode location is properly set when producing the TimingPlan results.
Display of timings in TimingPlan output for T-intersections and diamond interchange ramp intersections are now represented more consistently, regardless of what lane group is used to represent the movements on the stem of the 3-leg intersection.
A very obscure problem with excess allocation of miniscule amounts of excess time in Design optimization has been repaired.
The progress display during Design optimization has been expanded to accommodate 4-digit intersection numbers.
A problem with calculations of very small results for poisson probablility distributions for 64-bit systems has been repaired.
:TEAPAC Ver 8.23 20JUL10
Build 05 - 30SEP10
>4-digit Node Problem Fixed When Modifying Scenario Definition.
A problem has been discovered when modifying scenario definitions with the new 4-digit capability recently added to TEAPAC Complete, resulting in re-written condition files which could no longer be opened. The problem has been fixed, and anyone encountering this problem should contact Strong Concepts to get their condition files repaired.
Build 04 - 24AUG10
>4-digit Node Display Fixed in Network Coordinate System Analyze Output.
The Analyze function of the Network Coordinate System Management dialog (Setup button in main window) has been updated so it correctly displays 4-digit node numbers in its output analysis report.
>Missing Characters Restored in PeakAnalyze Output Report Sub-Title.
The sub-title line in the Peak-Hour Summary report for the PeakAnalyze function has been corrected so it shows the complete sub-title text in the graphics output report. This was a problem for the 15-Minute Flow Rates subtitle which was missing several characters at the beginning and end of the sub-title.
Build 03 - 20JUL10
>Largest TEAPAC Node Number Allowed Has Been Increased from 999 to 9999.
The largest node number which is allowed in TEAPAC has been increased from 999 to 9999 to provide greater compatibility with other traffic software and increased flexibility to be compatible with node number schemes used by agencies in the field. All field widths where node numbers can be entered have been increased to allow 4-digit entries, with error checking limits increased to 9999, and output fields have also been expanded accordingly. Import and Export interfaces to third-party software have been adjusted, as well.
For CORSIM, only the last three digits of external dummy nodes are used when creating their associated entry nodes (which always must be numbered 8xxx). As long as there are less than 1000 dummy nodes in the exported network and none of the external dummy nodes share the same last three digits, this will not be a problem (this is typically the case).
>New Option for Controlling Node Numbering During Network Creation.
A new option has been added to the Network Display and Edit dialog which is used when the Setup button of the main window is pressed. Two entries at the bottom of the dialog provide a place for the starting node number which will be used when new nodes are created, one entry for real nodes and one entry for dummy nodes. Real nodes will use the next available node number counting upwards from the provided value, while dummy nodes will use the next available node number counting downwards from the provided value. The default values are 1 and 6999, respectively. Using 6999 for dummies avoids conflicts with the largest node number allowed by CORSIM, but a number as high as 9999 can be used if CORSIM use is not anticipated.
>Export & Import for TRANSYT Adjusts Node Numbers So Always Less Than 100.
TRANSYT-7F has a limitation that node numbers must be in the range of 1-99 (hence, with a limitation of no more than 99 nodes in any given run of TRANSYT). Exporting to TRANSYT has been enhanced by adjusting the exported node numbers as necessary so that they are always in the range of 1-99. This is particularly useful in light of the enhancement above allowing node numbers in TEAPAC from 1-9999. This allows the full range of TEAPAC node numbers to now be useable, even when TRANSYT will be involved in the TEAPAC analysis (previously TEAPAC node numbers had to be in the range of 1-99 in order to be used with TRANSYT).
This is accomplished by first using any TEAPAC node numbers in an Export that are already in the range 1-99, then using only the last two digits of any other node numbers which do not conflict with the first group, then finally assigning arbitrary node numbers to the remaining nodes which are to be exported. This provides the best possible consistency between the TEAPAC node numbers and the node numbers which are seen in the TRANSYT results. The actual mappings used can be seen in the exported data file (.tin) which is created for TRANSYT.
When Importing optimized results from TRANSYT back into TEAPAC, the mapping of real vs. temporary node numbers used is first read from the .tin data file which corresponds to the the .tof results file which is being imported. This means that when TEAPAC node numbers greater than 99 are being used, the .tin data file created by the TEAPAC Export must be present when performing a subsequent TEAPAC Import.
>Default Installation Support for New CORSIM 6.2.
The default Options-Setup path for CORSIM has been changed to the new default path which is used by a CORSIM 6.2 installation.
>Miscellaneous Minor Issues Addressed.
Descriptive text in several dialog boxes that have migrated from earlier versions of TEAPAC programs have been updated so the dialog/command names referenced in the text agree with the new dialog/command names that were adopted for TEAPAC Complete.
The Synchro Import has been improved to accommodate longer Plan ID descriptions and avoid possible crash problems which involve these longer descriptions. Errors #PSY98 and #PSY99 have been renamed to #EXP98 and EXP99, as shown in the documentation.
The Summarize report for Traffic Impact Analysis data has been improved so that all of the data which appears in the text-only report is now included in the graphical results output. Error #TIA07 has also been expanded so it can accommodate 3-digit distribution types properly, and the Intersection command line which is optionally written to a data file for the ComputePaths function has been modified so it is not an ambiguous command entry (INTE -> INTR).
:TEAPAC Ver 8.22 10MAY10
Build 00 - 10MAY10
>Additional Actuated Inputs Provided to Interface with Synchro.
Five new data entry types are now allowed for each actuated intersection so that these values can be Exported to Synchro to perform actuated analysis. These entries are PassageTimes, Recalls, DualEntrys, FirstDetects and LastDetects. These entries will be stored in the TEAPAC data file so that they will be transfered to Synchro for each Export. The values can also be set when an entire network is Imported from Synchro. Two additional entries have also been added for future use, but not presently used by Synchro. With all of these data entries, it is now possible to create and store a complete actuated set of conditions in TEAPAC which can be Exported to (or Imported from) Synchro on demand, plus several sensitivity-oriented options described below which also exist in support of these new entries. When utilizing the actuated model in Synchro, GreenTimes entries will be interpreted as Maximum green times.
Vehicle extension times which have been previously entered via the Actuations entry in TEAPAC are now stored separately in PassageTimes, allowing the Actuations entry to be temporarily turned off (No) and back on (Yes) without the need to re-enter the actual passage time values. Extensions can still be entered on Actuations where PassageTimes will be entered automatically and Actuations will be set to Yes. The use of the Synchro actuated model can also be defeated for an Export with a single entry on the Simulation dialog (sending a recall-to-max to Synchro for each actuated movement), again without the need to re-enter all the actuated data to re-create the original actuated analysis. The default extension values are 3.0 seconds, consistent with the HCM2000 default, and the default Actuations and Simulation values are ‘No’ (unchanged from earlier) so that specific user input is required to implement the new actuated conditions.
A new option has been added that defines the need to add one or more extension times to the input Minimums entry when optimizing splits in TEAPAC, PASSER or TRANSYT. This provides the ability to assure that the optimum splits will time, for example, the entered Minimums value plus one extension time. A Factor entry on the new PassageTimes dialog allows the definition of anywhere from 0 to 300% of each extension time to be added to each of the specified Minimums entries. This option is only in force when a specific movement has its Actuations condition set to Yes. The default value is 0.0 so that extension times will not be added to Minimums unless specifically requested.
Recalls and DualEntrys parameters allow the entry of these typical actuated timing parameters, while FirstDetects and LastDetects enter the locations upstream of the stop bar where the first and last detections of moving vehicles are made for each movement. Defaults for Recalls and DualEntrys are both ‘No’, while the defaults for FirstDetects and LastDetects are 75’ and 5’ respectively for a typical and reasonable default detector size and location condition
>Updated Import Functions for Synchro and TSPPD/TruTraffic.
The TEAPAC Import function has been updated so it will accept 170 and NEMA-TS2 offset reference styles (in addition to the normal NEMA-TS1 style) from the 1-file UTDF file format used by Synchro Ver 7 and TSPPD/TruTraffic Ver 8. This matches the Import capabilities still supported for the multi-CSV UTDF format used by Synchro Ver 6 and TSPPD Ver 7.
The Import function has also been updated so that it understands the implementation of the 1-file UTDF file format used by TSPPD/TruTraffic Ver 8, especially in the event that all of the movements do not exist at a particular intersection (which previously could cause a crash).
>Abort Button Provided in Output Window.
A button has been added in the upper-right corner of the standard TEAPAC output window which can be used to abort any active analysis function(s) prior to its normal completion. This allows for convenient cancelling of actions which take more than a few seconds (such as certain kinds of optimizations) when it is apparent that the analysis will not produce the desired results. This can be used for routine capacity analyses (ANALYZE) or signal timing optimizations (DESIGN) for a large number of intersections to quickly change a selected option, for quick sensitivity testing that doesn’t require an analysis to fully complete, or in order to abort or re-start batch analyses for a mass of inter-related results which are being produced in sequence directed by a script control file (such as a complete traffic impact analysis consisting of traffic count analysis, warrant analysis, capacity analysis of existing conditions, projection of future volumes, and optimization and progression of. projected conditions).
>Rounding Error Fixed in TimingPlan Results.
A complex algorithm exists in the TimingPlan output for rounding dual-ring phase times so that the rounded phase times (both seconds and percent) for each ring on each side of the barrier 1) add up to the same number on each individual side of the barrier, 2) add up to the correct cycle time across the barrier, and 3) add up to a total of 100 percent across the barrier. Because of these sometimes competing objectives, the final rounded values may not look like they are rounded by normal means, but this process creates rounded results that can be implemented directly on controllers without getting errors from the controllers that the entered numbers 'do not add up'. A minor error which sometimes prevented achieving this balance has been identifed and fixed.
:TEAPAC Ver 8.21 12FEB10
Build 02 - 15MAR10
>MUTCD 2009 Analysis of Warrants for Signals and Signs Now Supported.
A new option has been added to allow signal and sign warrant analyses following the methods of the new 2009 MUTCD which was recently published. This is now the default warrant analysis of TEAPAC, with options still available for selecting 2003, 2000 and 1988 MUTCD methods.
>Launch VISSIM Animation Automatically with New EXPORT Option.
The recently added EXPORT support for VISSIM has been enhanced with an option to automatically start VISSIM with an active animation of the Exported conditions. This option is the Animate option in the Export dialog.
If the new Animate option is selected, control will not return to TEAPAC until the animation in VISSIM is stopped. To stop the animation, one of the Simulation play buttons in VISSIM may need to be pressed in order to enable the Simulation stop button. If returning to TEAPAC during the animation is desired, select the View option in the Export dialog instead of Animate and start the animation manually with the Continuous Simulation play button in VISSIM. Do not attempt to close the Export status message box during the animation or TEAPAC will be closed.
If VISSIM is started by an Export from TEAPAC and then subsequently closed, TEAPAC may need to be re-started so that it can create another instance of VISSIM with its next Export. This condition can be avoided by making sure not to close VISSIM once it has been opened by TEAPAC until the instance of TEAPAC which started VISSIM has itself been closed.
>Problems Fixed Exporting to Synchro Using NemaPhases and Split Phase.
Certain difficulties exporting to Synchro when using NemaPhases different than the defaults have been fixed. Also, certain phasing configurations for split phase that caused problems are now correctly exported. Other special cases of the use of NemaPhases that caused problems have been fixed, including when left turn phase numbers the same as adjacent through movements are used. Lastly, the way the phasing is exported has been modified so the Synchro displays are visually more consistent with the displays in TEAPAC.
>Install Package Modified to Always Install All Files.
The install package for TEAPAC has been adjusted so that all files are always installed, even if there is no change to a file or a currently installed file is a more recent version than that being installed. This will make for easier verification of which files are installed on a given system, and in the future will make installation of an older version over a newer version much easier than at present.
:TEAPAC Ver 8.20 18NOV09
Build 00 - 18NOV09
>VISSIM Simulation and Animation Has Been Added to TEAPAC's Export Function.
The popular VISSIM simulation and animation program (Ver 5.10 distributed by PTV America) has been added as one of the many third-party programs which are supported by the Export function in TEAPAC. A complete signalized network can be exported to a .anm file which can be dragged to the VISSIM main window or imported with VISSIM's File-Import-ANM menu.
When using the AUTO option for VISSIM, VISSIM will be opened and the path to the
TMPVIS.anm file which is created will be selected. Then the user should use the
File-Import-ANM menu to perform the import. In the dialog that opens, the browse
button for the Static Network Data file should be used to select the TMPVIS.anm
file and the Import routing option should be unchecked. Specifying a target
VISSIM input file is not necessary. As an alternative, the TMPVIS.anm file (or
any .anm file created by the Export) can be dragged to the main VISSIM window.
>New Tru-Traffic Program Fully Supported by TEAPAC's Export and Import.
The newest version of TS/PP-Draft which is now called Tru-Traffic (Ver 8.00.40) is now fully supported by the Export and Import functions of TEAPAC. In addition to all of the prior support for TS/PP-Draft, the newest features for managing the background images in Tru-Traffic are also supported by TEAPAC's Export to Tru-Traffic.
>Conditional Turns Are Now Modeled in CORSIM.
CORSIM's feature that allows upstream-downstream assignments between adjacent intersections has been implemented so that the Limited assignment option of TEAPAC's Network entry can be modeled the same way it is optimized in TRANSYT when Limited assignment is selected. This provides an animation of the TRANSYT-optimized results which is more consistent with the traffic flows which were optimized in TRANSYT. Limited assignment can be quite useful for many situations such as closely-spaced intersections, and in particular, to model the upstream-downstream flows which are likely to exist at most diamond interchange situations.
>New Option to Include Warrants Which have Been Analyzed Externally.
A new option has been added to the warrant Conditions dialog to include warrants which have been analyzed externally to TEAPAC. Warrants for pedestrians, schools, coordination and networks are not analyzed directly by TEAPAC since they require data which is not included in TEAPAC. However, if the analyst would like to show that any of these warrants have either been Met or Not Met in the TEAPAC warrant analysis summary, inputs on the Conditions dialog can be made to include any or all of these warrants. The default remains the same as before - these four warrants are not shown in the warrant analysis at all.
>Windows 7 Is Fully Supported.
TEAPAC Complete has been tested and optimized for Windows 7 usage, and takes advantage of many of the nifty interface features offered by Windows 7. No changes will be apparent for usage under any of the other 32-bit Windows platforms such as Windows XP and Vista.
:TEAPAC Ver 8.10 08APR09
Build 14 - 27OCT09
>Synchro Import Prevented from Setting IdealSatflows Equal to 0.
A Synchro Import is now prevented from setting IdealSatflows equal to zero for lane groups that do not exist. These zero values have been seen to be problematic when an analyst alters the geometry after the import and doesn't realize that the ideal satflows are zero. Rather than importing zeros, such values are now set to a more appropriate default of 1900.
>Fixed Synchronization for Edit-TrafficImpact and -CountAnalysis Menus.
Synchronization between the Edit-TrafficImpact menu selection and the dialog displayed has been corrected, where previously the selected menu did not always open the desired dialog. The same has been done for the Edit-CountAnalysis menu.
Build 12 - 15SEP09
>Improved Display of T-Intersections in Network Display.
T-Intersections which have only a shared 'through' lane for turns on the stem of the T will now display correctly as a T-intersection in the network display. Previously, the display could errantly show a fourth leg at the intersection in anticipation of a possible 1-way exiting leg - this display is now used only when through traffic in such a through lane validates the existence of the 1-way exiting leg.
>Scenario Template Function Fixed.
Access to the pre-programmed scenario templates provided with TEAPAC has been restored. The pre-programmed templates found in the Scenario dialog of the Edit menu provide a wide range of typical multi-scenario definitions that can be implemented quickly, and are a quick way to learn and experiment with the powerful scenario function built into TEAPAC.
>PDF User Guide Can Be Displayed from Help Menu.
A new option to open the PDF User Guide has been added to the Help menu. The PDF User Guide has the same content as the context-sensitive, interactive help system, but is formatted like a book for easy reading and is printable, either selectively or in its entirety. The PDF User Guide also provides a more context-friendly search function than the help system. The PDF User Guide is not included with the software download due to its size and redundancy with the Help content, but it can be downloaded at no charge from the Downloads section of StrongConcepts.com. After downloading, it should be saved in the folder where TEAPAC was installed (c:\Program Files\Strong Concepts\TEAPAC by default) so it can be accessed by the Help menu.
Build 09 - 11JUL09
>Synchro Import Enhancements Made.
The new REQYELLOWS input is now set when importing a complete network from SYNCHRO so that the yellow change and red clearance times which are imported will match those found in the Synchro data. The node which is selected in the TEAPAC display prior to a Synchro Import is also retained as the current node after the import is completed. A fix has been made to address difficulties importing certain problematic data situations from Synchro which caused unpredictable TEAPAC behavior after the Import.
>Data Input Checks for NOSTOP Export Modified.
Since volumes are not a real requirement for a TEAPAC Progression ANalysis (NOSTOP), the data check before an Export which requires volumes to be present for every defined lane group is now omitted for a NOSTOP Export. A band ratio which is normally based on directional arterial volumes is set to 1.0 when this is the case.
>Cycle Length Added to Output Display for TIMINGS and QUEUECALCS.
The cycle length which appears in the text-only outputs for the TIMINGS and QUEUECALCS results has been added to the graphical formatted output results for these actions.
>Approach Labels Added to Edit-Movement Menus.
The APPLABELS dialog has been added to the Edit menu for Movement data, primarily to been seen as column headings for entry of the movement data in the Tabular View.
>Approach and Movement Labels Added to TrafficImpact & CountAnalysis Menus.
The APPLABELS and MOVLABELS dialogs have been added to the Edit menus for TrafficImpact and CountAnalysis, primarily to been seen as column headings for entry of movement data (like VehicleCounts) in the Tabular View. This matches the presentation of the Tabular View that appeared in the prior WARRANTS and TURNS programs of TEAPAC.
Build 06 - 20JUN09
>Problem Caused by Deleting Dummy Nodes Resolved.
A problem which appeared in Build 03 has been resolved where deleting dummy nodes could potentially cause unexpected changes to other data values as the references to the deleted node were updated. This Build 06 update is strongly recommended for users of any version of TEAPAC Ver 8.10 starting with Build 03.
>New Lost Time Method Supported for Export/Import to/from Synchro Ver 7.
Synchro Ver 7 uses a new technique for describing lost time for movements, and ignores any attempts to use the prior method of describing lost time. TEAPAC has been adjusted to reflect this change in method so that lost time will be reflected consistently when data is exchanged between TEAPAC and Synchro Ver 7. This Build 06 update is strongly recommended for TEAPAC users exchanging data with Synchro Ver 7 either via Export or Import. Data exchange with earlier versions of Synchro is not affected.
>Default Import Folder Adjusted to Match Export AUTO Folder.
An earlier release of TEAPAC provided a new feature whereby the data folder used by Import functions was maintained separately from the user data folder so that import source files could be retained in a separate folder from other user data files. This feature can cause difficulties when executing Export AUTO functions followed by Import AUTO functions when the user data folder is being changed between each Export function. To resolve this, the default Import folder is now set to match the Export folder each time Export AUTO is used so that Import AUTO will use the same folder as Export AUTO in all cases.
Build 04 - 21MAY09
>Adjustment to License Key Processing Assures Qualified Licenses Self-Update.
A minor adjustment has been made to how license key information is processed to assure that all licenses with paid-up maintenance contracts self-update to allow full usage of all releases issued within the maintenance period, regardless of any change in version number.
Build 03 - 18MAY09
>Red Clearance (All-Red) Time Now Supported Directly by TEAPAC.
A new entry for entering signal timings called REDCLEARTIMES can be used to define red clearance time which follows yellow change time at the end of a phase. For optimizing timings, the previous entry called REQCLEARANCES has been renamed to REQCHANGE+CLEARS because it encompasses all change and clearance time required (yellow + all-red), as before. A new entry called REQYELLOWS is now used to define how much of the REQC+C time is yellow, and the remainder will be red clearance (all-red). Setting REQYELLOWS to zero will prevent any red clearance from being used, making all of the REQC+C time YELLOWTIME, as before. For an HCM2000 capacity analysis, red clearance and yellow change have the same effect, so sub-dividing the change+clearance time into yellow and red clearance has no effect on capacity analysis results. Timings exported to HCS+ will now include red clearance, and timings imported from and exported to Synchro and TS/PP-Draft will now retain the red-clearance times which have been defined. REDCLEARTIMES are included in the Edit-Phasing menu and REQYELLOWS are in the Edit-Movement menu under the new REQCHANGE+CLEARS entry. They are both displayed in the Signalized Summary of Parameter Values report.
>Pedestrian-Specific Signal Timing Parameters Can Now be Entered.
Pedestrian-specific signal timing parameters can now be entered and are maintained separately in the data base, and are used separately as constraints on optimization. Previously, if a ped signal timing requirement was larger than a vehicle minimum, that requirement was entered as the MINIMUM for the associated thru movement. Now new PEDWALKS and PEDFDWS entries can be made for each approach and these values are applied as optimization constraints in addition to the MINIMUMS constraint. Where previously TEAPAC would display an 'm' in the phasing for a phase which was constrained by a MINIMUMS entry, it now displays a 'p' for a phase which was constrained by a ped requirement. Since often it is desirable to test operation of a signal without ped constraints, a PEDWALKS factor can be entered to adjust the ped requirements. Setting it to 0.0 eliminates the peds requirements, while setting it to 1.0 uses the entered values, but other factors can also be used to test the sensitivity of the ped walk and flash don't walk (FDW) requirements. PEDWALKS and PEDFDWS are both found in the Edit-Approach menu under the PEDLEVELS entry. They are both displayed in the Signalized Summary of Parameter Values report and all phasing diagrams show the ped crossing as a dashed line in the appropriate phases.
>TIMINGPLAN Output Report Has Been Significantly Enhanced.
The TIMINGPLAN output report has been significantly enhanced, primarily to accommodate the display of the new timing intervals for red clearance times and ped walk and flash-don't-walk times mentioned above, but other major enhancements have also been provided. These include the display of nema phase times when the phasing is defined 'by-movement' so the times displayed reflect the times which would be implemented on a typical dual-ring controller. Boxes around the various phases and/or nema movement results have been added to make it more clear to which displayed phases these numbers apply, and a proportional display of the actual phase/ring interval timings is provided at the bottom of the report. A related change now shows by-movement timings in the various Summary of Parameter Values reports when the user has selected this entry mode.
>New NEMAPHASES Entry Allows Labeling of Phases.
A new NEMAPHASES entry allows labeling of phases according to what is or will be implemented on a dual-ring controller. If these entries are zeros (the default), no change in the display is made, but entries which define which protected nema phase numbers have been assigned to each of the twelve entry movements will be displayed in any phase diagram, such as TIMINGPLAN above, a capacity analysis, or a SEQUENCES or GREENTIMES dialog. The NEMAPHASES entries are exported to Synchro so that the same phase numbering is used in Synchro, and when a complete network is imported from Synchro, the NEMAPHASES used in Synchro are imported into TEAPAC. NEMAPHASES is included at the bottom of the Edit-Movements menu.
>PLOTTSD Function Expanded for the Possibility of Two Green Bands per Cycle.
This eliminates a previous problem in displaying bands where a short red that disrupts an otherwise wide green band thru a system was not properly represented. Furthermore, if the offset units of the master node in a PLOTTSD result are provided in seconds, the PLOTTSD results will also be displayed in seconds instead of percent of cycle. If the PLOTTSD does not include a master node, the units of the first node in the system are used to define the PLOTTSD units. Other cleanup items have also been performed on this output report, one being the removal of an extra page at the end of the PLOTTSD that sometimes was displayed, and another being problems when all the nodes to be plotted are not properly connected.
>Importing Timings from 3rd-party Programs Expanded for By-Movement Timings.
Importing timings from third-party programs which use by-phase timings can now be performed when the TEAPAC timings are defined by-movement. This includes importing from PASSER, TRANSYT and NOSTOP optimizations. Further, when timings are imported from Synchro (which is always by-movement), the TEAPAC timing entry scheme in use is retained, either by-phase or by-movement; and if a whole network is being imported from Synchro, then the timing entry scheme assigned for all the intersections is now designated as by-movement to match the scheme used in Synchro, rather than by-phase which was used previously.
>ARRIVALTYPE Set to Reasonable Value for Network Import from Synchro.
Previously, this was the responsibility of the user, and still should be considered carefully by the user. Since this is not a direct input for Synchro or a result available in the UTDF file format, the best TEAPAC can do is as follows - if the signalized approach being imported has a real upstream node that is signalized and is no more than 1/3 of a mile away, then the arrival type is set to 4, otherwise the arrival type is set to 3.
>Example Data Files Renamed.
Example data files have been renamed so that the file names reflect the type of Results analysis in TEAPAC that the data has been set up for. On a related note, all prior user data files are upwards-compatible with all the changes described above.
>Internal Flags Reset After COMPUTEPATHS & COUNTANALYZE for New Volumes.
After new volumes are generated by either the COMPUTEPATHS or the COUNTANALYZE function, the volumes and geometrics for the intersection are re-scanned and internal flags are re-set to reflect the new conditions. In particular, when these functions add volumes to movements that otherwise had no volumes, certain flags that indicate the existence of the movements are now re-set for use by subsequent functions of the program, such as capacity analysis and optimization.
>Unconnected Dummy Nodes Ignored By Export.
Dummy nodes which may exist in a network after it has been edited, but are no longer connected to other nodes in the network, are now ignored when EXPORTing to third-party programs to avoid unpredicatable results and crashes due to these extraneous nodes.
>Improved Display of List of Phasing SEQUENCES to be Optimized.
Long lists of phasing SEQUENCES to be optimized are now displayed properly.
>Prevent Crash in PROGRESSION Optimization for 1-Node Arterial.
A PROGRESSION analysis normally cannot be performed unless two or more intersections are entered in the PROGRESSION inputs. However, a one-intersection analysis can be populated by an EXPORT function, resulting in a crash in the PROGRESSION optimization, so checks in the optimization function now prevent this crash and deliver a 'No Solutions found' message which also includes the number of intersections attempted by the optimization.
>EXPORT AUTO Now Checks Data and Host Paths for Invalid Characters.
Certain characters (such as '%') in a file path specification for both data files and host programs that are allowed by Windows can confound the linkage techniques used between TEAPAC and third-party host programs when the AUTO option of EXPORT is used. The data and host file paths are now scanned for such invalid characters with a clear message and clean termination of the EXPORT AUTO function.
>Remove Caution Message About HCS+ Export Using New XML File Format.
A cautionary message about usage of the new XML data file format for HCS+ exports has now been removed in light of the proven functionality of this method of exporting both signalized and unsignalized intersections to HCS+.
>Mouse Sensitivity Reduced for Intersection Selection Clicks.
Slight movement of the mouse during an intersection selection click could be misinterpreted as a drag-and-drop SUBSYSTEM selection, and one that might go un-noticed because of potential minor differences in the colors used to represent selected nodes and SUBSYSTEM nodes in the graphical display. To limit the possibility of this confusion, the size of a drag area which is needed to invoke SUBSYSTEM selection has been increased, making intersection selection less sensitive to slight mouse movement during selection clicks.
:TEAPAC Ver 8.01 08DEC08
Build 04 - 27JAN09
>IMPORT Folder Can Be Independent From the Data Folder.
Previously, the folder from which import activities were performed was presumed (required) to be the same as the user data folder. However, by using the Browse button in the IMPORT and COUNTIMPORT dialogs, this joint-use folder could be changed, and possibly without the user's specific understanding of the specific ramifications. This could create a potential problem when saving the user's data file if it was assumed to be at an unchanged location from where it was opened or previously saved.
To remedy this, specifying a folder where an import file is located (either with the <Data File> specificaton or the Browse button in the dialog) no longer adjusts the folder location where future data file save activities will occur. The location of the last Import (IMPORT/COUNTIMPORT) file is remembered for use as the default folder for the next Import action, and the default folder for the first Import action is the data folder which is current for the first Import action.
>Direct Support for CORSIM Ver 6.1.
TEAPAC now directly supports the newest version of CORSIM (Ver 6.1) for the Export function of TEAPAC. Export support for prior versions of CORSIM remains in TEAPAC.
>CORSIM Export Option Corrected.
The CORSIM Export option was incorrectly displayed as Import instead of Animate in the EXPORT dialog box. This has been corrected. The Animate option allows a direct animate-only result after exporting to CORSIM without the need to view the simulation statistics.
>Node Number Delete and Renumber Prevented from Damaging Multi-Scenario Files.
The methods used to delete and renumber nodes are currently inconsistent with the data file structure used for multi-scenario data files, so these features have been disabled for multi-scenario situations to avoid potential damage to the integrity of the data files. A message to this effect is now displayed and the user is referred to Strong Concepts for a detailed discussion of the issues and potential methods around the problem.
>Help File Improvements.
Help for a number of Results dialogs has been restored for the Help buttons which appear in these dialogs. Also, a large number of pre-indexed search entries which had disappeared from the Help file have been restored.
>More Consistent Use of Enter Key for Dialog Entries.
An improvement has been made in the use of the Enter key in dialog displays for more consistent behavior for effecting a press of the default dialog button with the Enter key.
PreRelease 03 - 02JAN09
>IMPORT Problems from PROGRESSION (NOSTOP) Results Fixed.
Difficulties importing results from a PROGRESSION optimization (NOSTOP) for an arterial which has bend nodes or unsignalized intersections have been corrected.
>Problem Viewing NOSTOP Exported Data Fixed.
A problem scrolling through all of the output when including a view of the exported data for a PROGRESSION (NOSTOP) analysis has been corrected.
PreRelease 02 - 24DEC08
>COUNTIMPORT Dialog Repaired.
The COUNTIMPORT dialog produced from the Results menu to Import traffic count data from electronic counters was discovered to be inadvertantly damaged by a previous (incomplete) modification. This problem has been repaired.
Build 01 - 08DEC08
>Direct Support for TS/PP-Draft Ver 8 Export and Import.
TEAPAC now directly supports the newest version of TS/PP-Draft (Ver 8) for both the Export and Import functions of TEAPAC. TEAPAC automatically detects that Ver 8 is installed and adjusts the Export and Import functions accordingly. Export and Import support for prior versions of TS/PP-Draft remains in TEAPAC.
>Synchro 7 Export Workaround Improved.
Trafficware has not yet fixed the problem with the 1-file UTDF 2006 .csv file format used by Synchro Ver 7, but a simpler workaround has been generated that involves only re-reading the .csv file with Synchro's File-Merge menu after the Exported .csv file is first opened. This simpler method has been added to the warning message that is issued when TEAPAC Exports to Synchro Ver 7.
>More Complete Doc for OUTPUT Options in Dialog, Help and PDF.
All of the options for the OUTPUT dialog are now included in the on-screen help and printable pdf user guide. Previously, only those options relating to the Signal Analysis aspects of the program were included.
>Added Capability to Double-Click Files with Blanks in File Name.
The capability has been added to be able to double-click TEAPAC data files that have spaces in their name as a way to launch TEAPAC and open the clicked file. This capability has existed previously for files without spaces in their name, but was recently noticed as an unintended exception for files with spaces in their names. A related improvement allows such files to be opened directly from attachments in an email program.
>Help System Changes.
A hierarchical table of contents has been added to the on-screen help system for TEAPAC, and is accessible from the Contents button in the main Help window which is displayed when the F1 button is pressed or the Help-Contents menu is selected.
The original Windows Help-On-Help function (F2) has diminished in value over the years, and has been removed completely from Windows Vista, so it has now been removed from TEAPAC. Also, under Windows Vista, the standard Help system used by TEAPAC is available as a free download from Microsoft - go to www.support.microsoft.com and search for 'KB917607' to get the correct download for your system.
>Fixed Synchronization for Edit-Intersection Menu and OUTPUT Dialog.
Synchronization between the Edit-Intersection menu selection and the dialog displayed has been corrected, where previously the selected menu did not always open the desired dialog. A similar adjustment has been made to the OUTPUT dialog which occasionally would display an un-selected program in its drop-down list.
:TEAPAC Ver 8.00 27AUG08
Build 02 - 08SEP08
>First release of TEAPAC Complete, Ver 8.00.
This is the first release of TEAPAC Complete, Ver 8.00, which brings together all of the prior TEAPAC application programs into a single, fully-integrated program. TEAPAC Complete has all the functionality of the prior TEAPAC programs, and is distributed as a single-user, single-computer license. The application functions in the single TEAPAC Complete program now include:
HCM2000-compliant signalized capacity analysis and full HCM optimization of splits, cycle and phasing (previously known as SIGNAL2000).
Estimation of projected volumes for traffic impact studies, including user-adjustable, automated on-screen assignments of site traffic (previously known as SITE).
MUTCD-compliant signal warrant and multi-way stop warrant analyses (previously known as WARRANTS).
Complete traffic count analysis, including peak period determination and import of count data from a multitude of electronic traffic counters (previously known as TURNS).
Simplified bandwidth arterial progression optimization with full-color time-space diagrams (previously known as NOSTOP).
Full Export Capabilities for well-established third-party programs, such as HCS, TRANSYT-7F, PASSER-II, CORSIM, TS/PP-DRAFT and SYNCHRO/SIMTRAFFIC (previously known as SIGNAL2000, PRETRANSYT, PREPASSR, PRENETSIM, PRETSPPD and PRESYNCHRO).
Full Import Capabilities for a complete network created in SYNCHRO Ver 5, 6 or 7 (previously known as PRESYNCHRO).
Revolutionary TEAPAC multi-variable, multi-scenario data management for all applications above (previously known as SCENARIO).
Seamless exchange of inputs and results between all combined applications, such as peak period volumes, projected traffic volumes, optimized signal timings, computed saturation flow rates. etc.
One downloadable manual (and one on-screen help system) covers the entire breadth of TEAPAC applications, with full index and improved graphics and output examples.
Upgrade pricing from prior TEAPAC licenses is available.