How does TRANSYT time-segment length affect the results? - TRL Software
01344 379777software@trl.co.uk
TwitterYouTubeLinkedin
  • TRL Main Site
  • Careers
  • Publications
Top Menu
Search
Cart0
  • No products in the cart.

Subtotal: £0

View Cart Checkout

TRL SoftwareTRL Software
TRL Software
World Class Traffic & Transportation Software Solutions
  • Products
    • Junction & Signal Design
      • Junctions
        • ARCADY
        • PICADY
        • OSCADY
      • PCMOVA
      • TRANSYT
    • Traffic Control
      • MOVA
      • SCOOT®
      • Urban Traffic Control (UTC)
      • MotorGraph
    • Road Safety
      • iMAAP
      • Street Auditing
    • Economic Appraisal
      • HDM-4
    • Digital Asset Management
      • iROADS™
  • Services
    • Junction Analysis
    • Microsimulation Services
    • Signal Control
    • Road Danger Reduction
    • Software Development
    • Strategic Modelling
  • About
    • TRL Software
    • Quality Standards
    • Careers
  • News
  • Support
    • Training
    • Knowledge Base
    • Webinars
    • Videos
    • Support Options
    • Maintenance Agreement
    • Licensing
    • Online Store Help
    • Ideas Portal
    • FAQ
  • Contact
Menu back  
TRL Software > Support & Training > Articles > How does TRANSYT time-segment length affect the results?

How does TRANSYT time-segment length affect the results?

Question: How does the time-segment length affect the TRANSYT 13 (or later) results? Does it have the same effect as the “simulated time period” in TRANSYT 12?

Answer:  In TRANSYT 15 (and 14 and 13), the “simulated time period” is now called “modelled time period”.  As you will probably know these vwersions of TRANSYT allow varying traffic conditions over time (segments) to be modelled.  This means that the “modelled time period” is no longer entered directly by the user, but is simply calculated by TRANSYT as “Number of Time Segments” x “Time Segment Length”, which ARE both user-specified.  The “modelled time period” works in the same way as the original “simulated time”.  E.g. most of the TRANSYT outputs reflect the average (e.g. Mean Max Queue”) value over the modelled time period.

 

N.B. A previous TSN article (see Issue 41 – March 2007) explained how you could use the simulated time to give an estimate of the MMQs at the END of the time period rather than the average.  This process is no longer necessary for this particular item, as the TRANSYT results now include an output value (see excerpt from the Link Results table: Queue and Blocking below) called “Mean Max Queue EoTS”.  EoTS stands for “End of Time Segment”.  Obviously when you have just one segment, this value is also the MMQ at the end of the modelled time period.  When using multiple segments there will be one for each segment.

 

Link Results: Queues And Blocking

Link Major Link Mean Max Queue (PCU) Mean Max Queue EoTS (PCU)
213   1 6
214   9 17

 

 

Furthermore, please remember that most TRANSYT outputs are shown as ‘rates’ – usually per hour – and as such need to be scaled by the time-period if you wish to know absolute values for the time period being modelled. E.g. If the segment length is 30 minutes the total flows and saturation flows are entered by the user, and output by TRANSYT as hourly values.  To work out the total flow over a stopline during a 30 min segment, you will need to divide the results by two.  However, even when segment lengths are fractions of an hour, it is normally easiest to continue to work with rates throughout rather than absolutevalues.

Categories
  • ARCADY Modelling
  • ARCADY/PICADY/OSCADY Technical
  • Other products
  • PICADY Modelling
  • TRANSYT Modelling
  • TRANSYT Network Diagrams
  • TRANSYT Technical
Recent Articles

  • TRANSYT 16 Simulation Model

  • Automatically calculating future traffic flows using growth factors

  • Graphs showing sensitivity of geometric parameters

  • How can I transfer traffic data between Junctions and Excel?

  • Pedestrian crossing and blocking on the same road

Stay up to date with news from TRL Software

Sign up
Products
  • Junction & Signal Design
  • Traffic Control
  • Road Safety
  • Economic Appraisal
  • Digital Asset Management
Services
  • Junction Analysis
  • Microsimulation Services
  • Signal Control
  • Road Danger Reduction
  • Software Development
  • Strategic Modelling
Contact Us

01344 379777
software@trl.co.uk

TRL Limited
Crowthorne House
Nine Mile Ride
Wokingham
Berkshire
RG40 3GA

TRL Software
TRL Registered Office: Crowthorne House, Nine Mile Ride, Wokingham, Berks, UK, RG40 3GA. Registered in England, No. 3142272, VAT Registration 664 625 321.
© Copyright 2021 TRL. All rights reserved.
  • Sitemap
  • Terms & Conditions
  • Privacy Notice
  • Accessibility
Footer Menu