CTM Server Trace Options

Property	Description
CTMSrv/Auto cache load start time	Sets the number of hours after midnight when you want the cache to automatically reload. If the set value is bigger than 23, the start time is at midnight.
CTMSrv/Auto cache load timeout	Sets the number of minutes after the cache has been automatically loaded that the process can be aborted. Set to 0 to turn off.
CTMSrv/Automatically Reload Signups	If selected, theCTM Server checks for changes on an interval to sign-up periods and reloads the cache if required.
CTMSrv/Exp/APX itineraries	If selected, the system checks for early AM and late PM X-time itineraries from the previous day and next day, respectively
CTMSrv/Exp/Early Requests As Late APX Times:	If selected, the service interprets early AM itinerary requests as late night APX times
CTMSrv/Exp/Extended Max Stop Distance	This option manages the Extended Max Stop Distance Parameter. Set to 0, if there are no initial stops found within the Max Walking Distance. Set to 1, if you want the system to retry a step with the extended max stop distance when there are no itineraries found.
CTMSrv/Exp/Include walkout times in itinerary durations	If selected, the system integrates walkout time estimates into itinerary generation and reporting
CTMSrv/Exp/Report Street Walking Distances	If selected, the detailed MapRoute generated walking distances and instructions for itineraries (origin, destination, and transfers) are shown. Distances are only updated based on theCTM Server switch setting.
CTMSrv/Exp/Search Queue Idle Limit	Number of minutes that searches can be kept in the queue before being removed. The default is 5 minutes.
CTMSrv/Exp/Suppress excess itineraries	If selected, the itineraries that are in excess of the requested number of itineraries are suppressed.
CTMSrv/Exp/Suppress trivial short-distance itineraries	If not selected, itineraries can be generated for stops that are viable as both an Origin stop and a Destination stop (that is, the stop lies within the origin and the destination search circles). This is set to On by default.
CTMSrv/Exp/Threading/Use Thread Pool	This is automatically enabled so this switch is not visible in the Trace Options dialog. For version 13 and earlier, if selected, incoming requests will use a thread pool in order to reduce the number of threads created byCTMSrv.
CTMSrv/Exp/Threading/Initial Max Worker Threads	Number of worker threads is created at start up. We recommend setting to 0 to allow the server to automatically determine the optimum number of worker threads based on the number of processors in the system.
CTMSrv/Exp/Threading/Max Worker Threads	Number of requests that can be simultaneously processed. Minimum is 0, maximum is 16. We recommend setting to 0 to allow the server to automatically determine the optimum number of worker threads based on the number of processors in the system.
CTMSrv/Exp/Threading/Trace Worker Threads	Trace level for worker threads. This is set to Error by default. For Trapeze diagnostic purposes only.
CTMSrv/Exp/Threading/RequestQueue/Trace Interval	Number of seconds between traces of the current contents of the request queue. If set to 0, the trace is off. This takes effect immediately.
CTMSrv/Exp/Threading/RequestQueue/Trace Threshold	Trace is run on the request queue only if the number of items is equal to or greater than this value. This takes effect immediately.
CTMSrv/Exp/Threading/RequestQueue/Trace Max	Number of items from the start of the request queue that is displayed in the trace. This takes effect immediately.
CTMSrv/Exp/Trace Diagnostics Interval	Number of minutes between each summary report of diagnostic information, for example, memory consumption, search queue details. If set to zero (0), the diagnostic tracing is not run; only once when theCTM Server is started. This is set to 0 by default.
CTMSrv/Exp/Trace Diagnostics Level	Trace level ofCTMSrv memory usage and search queue details. If set to Message, the system reports memory consumption and search queue activity. If set to Verbose, the system provides additional details on each search queue entry. This is set to Message by default.
CTMSrv/Exp/Use Info Transfers Table	If selected, the system uses the 'InfoTransfers' table instead of the 'Transfers' table. Reload theCTMSrv cache after you change this setting.
CTMSrv/Exp/Use Lowest Stop Sequence for Transfers	If selected, the system uses the lowest stop sequence number at the origin leg for evaluating transfers (read-only at the Workstation).
CTMSrvExp//Use Proximity Segments	If selected, the system uses StreetRouter proximity segments to compute the walkout distances
CTMSrv/Exp/Use Stop Clusters for Walking Distance	Custom level to enable the use of stop clusters (for example, transit bays) when reporting itinerary walking distances and stop coordinates. Options are: 0 = Off, 1 = Use Cluster Coords Only, 2 = Use Cluster Coords + Name
CTMSrv/Exp/Use Trip Revenue	If selected, the Revenue flag from the Trips table is used to exclude non-revenue trips from being loaded into the cache. TheCTMSrv cache must be reloaded after this switch has been reset.
Linked Lines Signage/UseBlockId	If selected, the signage of connecting trips on routes that have linked lines and are part of the same block is displayed. Being part of the same block means that the From and To lines have the same Block ID.

CTMSrv/Auto cache load start time

Sets the number of hours after midnight when you want the cache to automatically reload. If the set value is bigger than 23, the start time is at midnight.

CTMSrv/Auto cache load timeout

Sets the number of minutes after the cache has been automatically loaded that the process can be aborted. Set to 0 to turn off.

CTMSrv/Automatically Reload Signups

If selected, theCTM Server checks for changes on an interval to sign-up periods and reloads the cache if required.

CTMSrv/Exp/APX itineraries

If selected, the system checks for early AM and late PM X-time itineraries from the previous day and next day, respectively

CTMSrv/Exp/Early Requests As Late APX Times:

If selected, the service interprets early AM itinerary requests as late night APX times

CTMSrv/Exp/Extended Max Stop Distance

This option manages the Extended Max Stop Distance Parameter. Set to 0, if there are no initial stops found within the Max Walking Distance.

Set to 1, if you want the system to retry a step with the extended max stop distance when there are no itineraries found.

CTMSrv/Exp/Include walkout times in itinerary durations

If selected, the system integrates walkout time estimates into itinerary generation and reporting

CTMSrv/Exp/Report Street Walking Distances

If selected, the detailed MapRoute generated walking distances and instructions for itineraries (origin, destination, and transfers) are shown.

Distances are only updated based on theCTM Server switch setting.

CTMSrv/Exp/Search Queue Idle Limit

Number of minutes that searches can be kept in the queue before being removed. The default is 5 minutes.

CTMSrv/Exp/Suppress excess itineraries

If selected, the itineraries that are in excess of the requested number of itineraries are suppressed.

CTMSrv/Exp/Suppress trivial short-distance itineraries

If not selected, itineraries can be generated for stops that are viable as both an Origin stop and a Destination stop (that is, the stop lies within the origin and the destination search circles). This is set to On by default.

CTMSrv/Exp/Threading/Use Thread Pool

This is automatically enabled so this switch is not visible in the Trace Options dialog.

For version 13 and earlier, if selected, incoming requests will use a thread pool in order to reduce the number of threads created byCTMSrv.

CTMSrv/Exp/Threading/Initial Max Worker Threads

Number of worker threads is created at start up. We recommend setting to 0 to allow the server to automatically determine the optimum number of worker threads based on the number of processors in the system.

CTMSrv/Exp/Threading/Max Worker Threads

Number of requests that can be simultaneously processed. Minimum is 0, maximum is 16. We recommend setting to 0 to allow the server to automatically determine the optimum number of worker threads based on the number of processors in the system.

CTMSrv/Exp/Threading/Trace Worker Threads

Trace level for worker threads. This is set to Error by default. For Trapeze diagnostic purposes only.

CTMSrv/Exp/Threading/RequestQueue/Trace Interval

Number of seconds between traces of the current contents of the request queue. If set to 0, the trace is off. This takes effect immediately.

CTMSrv/Exp/Threading/RequestQueue/Trace Threshold

Trace is run on the request queue only if the number of items is equal to or greater than this value. This takes effect immediately.

CTMSrv/Exp/Threading/RequestQueue/Trace Max

Number of items from the start of the request queue that is displayed in the trace. This takes effect immediately.

CTMSrv/Exp/Trace Diagnostics Interval

Number of minutes between each summary report of diagnostic information, for example, memory consumption, search queue details. If set to zero (0), the diagnostic tracing is not run; only once when theCTM Server is started. This is set to 0 by default.

CTMSrv/Exp/Trace Diagnostics Level

Trace level ofCTMSrv memory usage and search queue details. If set to Message, the system reports memory consumption and search queue activity. If set to Verbose, the system provides additional details on each search queue entry. This is set to Message by default.

CTMSrv/Exp/Use Info Transfers Table

If selected, the system uses the 'InfoTransfers' table instead of the 'Transfers' table. Reload theCTMSrv cache after you change this setting.

CTMSrv/Exp/Use Lowest Stop Sequence for Transfers

If selected, the system uses the lowest stop sequence number at the origin leg for evaluating transfers (read-only at the Workstation).

CTMSrvExp//Use Proximity Segments

If selected, the system uses StreetRouter proximity segments to compute the walkout distances

CTMSrv/Exp/Use Stop Clusters for Walking Distance

Custom level to enable the use of stop clusters (for example, transit bays) when reporting itinerary walking distances and stop coordinates. Options are: 0 = Off, 1 = Use Cluster Coords Only, 2 = Use Cluster Coords

+ Name

CTMSrv/Exp/Use Trip Revenue

If selected, the Revenue flag from the Trips table is used to exclude non-revenue trips from being loaded into the cache. TheCTMSrv cache must be reloaded after this switch has been reset.

Linked Lines Signage/UseBlockId

If selected, the signage of connecting trips on routes that have linked lines and are part of the same block is displayed. Being part of the same block means that the From and To lines have the same Block ID.