SOME RULES FOR SIMULATIONS

 

In order to run simulations in the right way, the following rules should be followed.

 

ROUTES

SIMULATION CONTEXTS

CHRONOLOGICAL SUMMARY

MODIFICATIONS

SUPPORT

 

ROUTES
==============

  • The layout must have been validated, with a correct signaling, before attempting to simulate ...
    ...(Tag "Edit/Module" >> "Build and check module ").

  • The routes must be created with blocks (or sections) long enough to host the longest consists targetted
    to travel on them. Whenever this condition is not met, the simulation will stop with an error message, as
    soon as a train will straddle both on the start and end of a block.
    The block (or section) length is displayed at bottom of the route section capture menu.

  • For a route to be useable in simulation, it must be looped on itself, so that a train will periodically go
    through any point of this route. During route capture, the software detects that the currently captured
    section loops on the starting point, and prompts for looping the route, and hence end up the route capture.
    NOTE: it is also possible to defined NON looped routes, dynamically (that is while simulation is running)
    so as to move a train from one location to another. This alternate route type (named "on-the-fly" route)
    will be detailled in antoher note.

  • On any block (or section) of a route, a maximum speed may be defined .
    This maximum speed should be lowered, if some trains cannot stop before block end, in case of scheduled
    halt, or in case of wait for next block.

  • In the initial train positioning phase (Tag "Trains" >> "Place"), required before any simulation launch,
    any train can be attached to a route.

    • There may be several trains attached to the same route.

    • A train may be placed without any route, in order to drive it "manually".
      But in that case, the recommended approach is to use "on-the-fly" routes while simulation is running.
      (see specific nore on this topic).

    • In order to be able to reuse multi-train positioning for another simulation, it is recommended to save this initial
      "context" into a simulation context (see next section).

BACK TO TOP OF PAGE

|

|

|

|

 

 

SIMULATION CONTEXTS
========================

  • In order to be able to reuse an initial set of trains, located on proper blocks, for later use in another
    simulation or another "RUN", it has to be saved into a simulation context:
    Tag "Consists >> "Save a Simu/Run context"

  • Since the "RUN" is driven by the simulation, a simulation context may be used both for simulation and
    for RUN.

  • Another important benefit of these simulation contexts is that, in case of problem during simulation or
    RUN, the "support team" (on the forum) has all assets in hand to reproduce the problem.

  • There is no specific limit on the number of simulation contexts. Any context has a specific name allocated
    upon creation.

  • Two specific contexts are automatically created by CDM-Rail. These contexts are intended for straightforward
    restart     from the last known train locations, either for simulation or for RUN.
    In general, they are useless for support in case of problem.

    • _SIMU_CTXT, created on end of simulation,

    • _RUN_CTXT, created on end of RUN.

BACK TO TOP OF PAGE

|

|

|

|

 

CHRONOLOGICAL SUMMARY
=============================

  • Create one or several looped routes.

  • Place trains on the layout, and specify the proper route for any of them...
    ... Or restore a previously saved simulation context ("Consists" >> "Restore a Simu/RUN context ").

  • Once all trains are in place , save into a new simulation context, different from
    _SIMU_CTXT et _RUN_CTXT.

  • After any important step (for instance a simulation context which runs fluently), save your project (.lay)
    under a different name (for example with the date), so as to be able to restore the data, in case of problem
    with the project file (quite rare, but it may happen).
    In other words, after an important step, use
    "File/Layout" >> "Save layout as " rather than "File/Layout" >> "Save layout "

  • Start simulation by clicking on button "SIMU" in window "SIMU/RUN" which pops up at place time.

  • The simulation (or RUN) may be frozen/restarted thanks to key STOP/GO in window SIMU/RUN,
    or by pressing the keyboard spacebar .

  • Whenever the simulation or RUN has been stopped by clicking button SIMU ou RUN with red "X":

    • either the CDM-Rail session has not been ended, and trains are still in place on screen: in that case restart will
      occur by just clicking button SIMU or RUN,

    • or context _SIMU_CTXT ou _RUN_CTXT must be restored (according to whether SIMU or RUN is to be launched).

BACK TO TOP OF PAGE

|

|

|

|

 

LAYOUT OR SIGNALING MODIFICATIONS
=======================================

Unfortunately, CDM-Rail is still not very tolerant as far as layout and signaling modifications are concerned.
once, routes have been created.

If a track segment, or a signal, is used in a route, then it will not be possible to modify or move this segment or
signal.
This only solution, in that case, is:

  • delete all routes using this segment or signal,....

  • ... and delete all simulation contexts using those routes,
    (including automatic contexts: _SIMU_CTXT et _RUN_CTXT).

 

BACK TO TOP OF PAGE

|

|

|

|

 

 

SUPPORT (VIA FORUM CDM-RAIL)
=================================

To get support on the forum (free of charge, of course), in case of problem on a simulation, please make sure
to provide the following information and data:

  • project file (".lay"),

  • initial simulation context leading to the problem,

  • simulation time at which the problem occurs (the simulation time is continuously displayed on bottom of
    screen).

  • precise description of the problem at hand.

 

BACK TO TOP OF PAGE