SCENARIO has been superseded by and incorporated into the new TEAPAC Complete product which is described in detail at the main page of www.StrongConcepts.com. Upgrades from SCENARIO to TEAPAC Complete are available. Contact Strong Concepts for details.
:SCENARIO Ver 1.81 27MAY08
Build 11 - 27MAY08
>Include SCENARIO_000.tpc in distribution for CreateFromTemplate.
The SCENARIO_000.tpc file which is used by the CreateFromTemplate process was
missing from some distribution packages which included the SCENARIO program.
This file is now included in all distribution packages, and the corresponding
old-format SCENARIO_000.for file has been removed.
>Look for SCENARIO_000.tpc in installed folder, not in data file folder.
The prior requirement that the SCENARIO_000 file (for CreateFromTemplate) be
located in the same folder as the user's data files has been eliminated. The
file is now always used from the installed folder where it is placed by the
setup installation process.
>NOTE shows 'Issue X Not Selected' when case selection does not select an
Issue.
When a scenario case is selected from a file using the File-GetScenarioCase
menu, the various Conditions which are selected are described in the NOTE entry
which is displayed on-screen and in each output report. When a Condition for a
specific Issue is not selected, this 'unselected' status is now included in the
NOTE so that it is apparent that there may be certain data that has not been
populated by the GetScenarioCase process.
>File-SaveAs to an existing file name with Scenario conditions doesn't hang.
In prior versions, if File-SaveAs was used to save data using a file name that
already existed with scenario condition files, the potential for a hung system
occurred in the program's attempt to reconcile the conflicts between the
condition files of the old file and the new file. This potential has been
rectified.
>Generic changes made to all Ver 7.81 TEAPAC programs.
Allow negative percentage on ASSIGNMENT for Passbys and Diverted trips.
Use Shift while dragging mouse to define development area on network display.
Dialogs identify need for consistency between Yellowtimes & ReqClearances.
Display dummy node dot and node number if it is current node or in Subsystem.
Note in CrdSysMgmt dialog that NewLinkDist button assumes coords are in feet.
Able to save from OpenIntoEdit if it was first file opened into program.
NOTE shows 'Issue X Not Selected' when case selection does not select an Issue.
File-OpenMerge does not allow existing Network data to be overwritten by zeros.
File-SaveAs to an existing file name with Scenario conditions doesn't hang.
File-SaveAs shows file type of current file & better file type descriptions.
:SCENARIO Ver 1.80 25APR07
Build 00 - 08JUN07
>Long File Names and Longer Path Names Implemented, Plus New File Format.
All aspects of TEAPAC data file storage, including SCENARIO condition files,
have been extended so that file names can have as many as 70 characters in their
names, and file path names can have as many as 180 characters, both including
upper or lower case characters and spaces. Since SCENARIO condition files and
certain file switch options can add as many as 6 characters to file names, it is
best if user-entered names are no more than 64 characters.
A new, higher capacity data file format with a new file extension (.tpc) has
been introduced which will be used by default for all new files created by all
TEAPAC programs. This format is text-based like the old .for format so it is
still easy to see what is in a file, as well as write such files from other
programs, but with a look to the future this format has line length maximums of
256 characters per line (254 useable) instead of the more limiting maximums of
the .for format which had maximums of 128 characters per line (80 useable). The
old format can still be read and written simply by continuing to use the .for
extension, but users are encouraged to convert files to the new format simply by
saving .for file with the new .tpc extension (then archive the .for files so
they are not used by mistake). The long file names and paths mentioned above are
valid for either extension.
>New User Discussion Forum Is Accessible Directly from the Help Menu.
The new User Discussion Forum which has been implemented for TEAPAC users and is
available 24/7 for posting questions and searching through answers to previous
questions can now be accessed directly from the Help menu of the program. The
Forum can also be accessed directly using any internet browser at
www.StrongConcepts.com/Forum.
:SCENARIO Ver 1.71 08SEP06
Build 07 - 25JAN07
>SCENARIO Program Makes its Debut.
SCENARIO is a new Visual TEAPAC program that can create multi-scenario data
files either from scratch or from data files of earlier versions of TEAPAC.
Users can 1) select from pre-defined typical scenario structures like multiple
volume conditions or multiple timing plans, 2) create completely unique scenario
conditions for their analyses, or 3) customize a pre-defined scenario structure
to meet their specific needs. The primary advantage of using SCENARIO is that
all the scenario data is saved without dangers of duplicated data which often
occur when scenarios are managed by the typical use of File-SaveAs.
The SCENARIO program also functions as an automatic plugin for all other Visual
TEAPAC programs so that each program automatically understands the SCENARIO file
structure which has been created, and at no additional cost (see below).
SCENARIO can easily define both single-issue and multi-issue conditions, and any
data dialog can be assigned or re-assigned to any defined issue for as many as
five independent, mutually-exclusive Issues. 25 Conditions can be defined for
each Issue. For example, a very common and simple single-issue scenario would be
having multiple volume conditions for one or more intersections for which
capacity analysis, intersection design and/or signal timing optimization would
be needed. Other examples of a single-issue analysis could be multiple years of
traffic count data for TURNS or WARRANTS, or multiple years or zones of land use
for SITE's projected traffic estimation.
Multi-issue scenarios could be combinations of any of these, where the variation
of one variable is independent of the others. Another example of a multi-issue
scenario could be where one Issue is changing volumes based on the time-of-day
and/or day-of-week while the other Issue is independently changing intersection
geometrics which depend on differing funding possibilities.
>SCENARIO Support in All Visual TEAPAC Programs.
All Visual TEAPAC programs have been updated so that support for multi-issue
data files created by SCENARIO is automatic and seamless. The SCENARIO program
serves as a plugin to the other Visual TEAPAC programs so that they
automatically support the SCENARIO-structured files for both File-Open and
File-Save. A new File menu option labeled Get-Scenario-Case allows the user to
select any of the Conditions for all of the Issues which have been created, and
any subsequent changes to data which are made are automatically saved in the
correct Condition files which have been defined. SCENARIO has also been added to
all LinkTo menus so that SCENARIO is immediately available to modify the defined
scenario structure, as necessitated by changing project assumptions.
>Generic Enhancements Made to All Visual TEAPAC Programs.
A number of additional generic enhancements and fixes have been made to the
original Ver 7.00 releases of Visual TEAPAC and are collectively included as Ver
7.01 Build 07. These are documented below. Ver 7.01 Build 07 changes are free
updates for Ver 7.00 licenses.
Data entry dialogs that don't apply to dummy nodes have been modified so that if
they are inadvertently displayed while pointing to a dummy node they will not
display unpredictable values or cause the program to crash.
The LinkTo menu has been adjusted so that if no data file path has been defined
it will attempt to use the program's file path, but will not crash if neither of
these is defined. The file menu options for Open, SaveAs and IntoEdit have been
adjusted similarly for the condition when no data path has been defined.
A bug has been fixed that could cause a crash when clicking within an output
being displayed at a zoomed-out scale on some low-resolution monitors.
this page last updated September 07, 2008