Performance Log - Revision history

Oxalin: /* External Performance Log */

2022-11-05T17:45:45Z

External Performance Log

Oxalin: Fixed category links

2022-08-22T06:53:28Z

Fixed category links

Oxalin: Created page with "The Performance Log is a feature of Railway Operation Simulator. There are two aspects of the log: the internal log, viewable while playing, and the external log, which pr..."

2022-08-22T06:52:45Z

Created page with "The Performance Log is a feature of Railway Operation Simulator. There are two aspects of the log: the internal log, viewable while playing, and the external log, which pr..."

New page

The Performance Log is a feature of [[Railway Operation Simulator]]. There are two aspects of the log: the internal log, viewable while playing, and the external log, which provides a summary after finishing.

== Internal Performance Log ==
This log can be enabled or disabled at will while operating a route, using the “toggle performance log” button. In [[Category:Program Versions|versions 2.12.0]] and earlier the log appears as a box in the bottom left that can be moved around within the ROS window as desired. From [[Category:Program Versions|versions 2.13.0]] onwards, the log opens as a separate window and can therefore be moved outside the boundary of the ROS window - particularly useful for those with multiple monitors.

The log provides a real-time list of all events happening in the simulation, such as arrivals and departures, failures and trains waiting at red signals. The log provides a large amount of detail, with exact time and headcode where relevant, so that any problems can be identified.

== External Performance Log ==
When a session is saved and closed (ie the red X button is pressed), an external performance kog is saved to the “/___/Performance Logs” directory. It can be opened using any text editor.

This log provides all the same detail as the internal log, with an additional summary at the end. The summary uses various statistics including how early and late trains were, how long level crossings were closed, and whether there were any signals passed at danger (SPADs) to determine an overall score.

@@ Line 7: / Line 7: @@
 == External Performance Log ==
-When a session is saved and closed (ie the red X button is pressed), an external performance kog is saved to the “/___/Performance Logs” directory. It can be opened using any text editor.
+When a session is saved and closed (ie the red X button is pressed), an external performance is log saved to the “/___/Performance Logs” directory. It can be opened using any text editor.
 This log provides all the same detail as the internal log, with an additional summary at the end. The summary uses various statistics including how early and late trains were, how long level crossings were closed, and whether there were any signals passed at danger (SPADs) to determine an overall score.

@@ Line 2: / Line 2: @@
 == Internal Performance Log ==
-This log can be enabled or disabled at will while operating a route, using the “toggle performance log” button. In [[Category:Program Versions|versions 2.12.0]] and earlier the log appears as a box in the bottom left that can be moved around within the ROS window as desired. From [[Category:Program Versions|versions 2.13.0]] onwards, the log opens as a separate window and can therefore be moved outside the boundary of the ROS window - particularly useful for those with multiple monitors.
+This log can be enabled or disabled at will while operating a route, using the “toggle performance log” button. In [[:Category:Program Versions|versions 2.12.0]] and earlier the log appears as a box in the bottom left that can be moved around within the ROS window as desired. From [[:Category:Program Versions|versions 2.13.0]] onwards, the log opens as a separate window and can therefore be moved outside the boundary of the ROS window - particularly useful for those with multiple monitors.
 The log provides a real-time list of all events happening in the simulation, such as arrivals and departures, failures and trains waiting at red signals. The log provides a large amount of detail, with exact time and headcode where relevant, so that any problems can be identified.