Tellurian.Trains.Schedules.Model 3.2.1

Tellurian.Trains.Schedules.Model

Core domain model for railway timetable planning and scheduling.

Installation

dotnet add package Tellurian.Trains.Schedules.Model

Key Types

Layout (Physical Infrastructure)

Timetable (Train Operations)

Schedule (Resource Assignments)

Remark The concept with VehicleSchedules containing TrainParts is to make it possible to change locomotives and wagonsets at a station between the train's first and last station call.

Usage

using Tellurian.Trains.Schedules.Model;

// Create a layout with stations
var layout = new Layout { Name = "MyLayout" };
var station = new Station(1, "Central", "C");
station.Add(new StationTrack("1") { IsMain = true });
layout.Add(station);

// Create a timetable with trains
var timetable = new Timetable("Morning", layout);
var train = new Train(101, "P101") { Category = passengerCategory };
train.Add(new StationCall(station.Tracks.First(),
    arrival: new Time(8, 0),
    departure: new Time(8, 5)));
timetable.Add(train);

// Create a complete schedule
var schedule = Schedule.Create("Schedule2024", timetable);

// Add vehicles and assignments
var loco = new Vehicle(1, VehicleType.Locomotive, 1234);
schedule.AddVehicle(loco);

var vehicleSchedule = new VehicleSchedule(1);
schedule.AddVehicleSchedule(vehicleSchedule);
vehicleSchedule.Add(train.AsTrainPart(0, 1)); // First to last call

var assignment = new VehicleScheduleAssignment(1, loco, vehicleSchedule);
loco.ScheduleAssignments.Add(assignment);

Validation

The model includes comprehensive validation to detect scheduling conflicts and data inconsistencies. Validation is performed after data has been successfully imported with referential integrity intact.

For detailed validation documentation, see VALIDATION.md.

Validation Options

Validation can be configured using ValidationSettings:

var options = new ValidationSettings
{
    ValidateStationCalls = true,       // Check arrival/departure times
    ValidateStationTracks = true,      // Check track occupation conflicts
    ValidateStretches = true,          // Check single-track conflicts
    ValidateTrainSpeed = true,         // Check speed limits
    ValidateVehicleSchedules = true,   // Check vehicle schedule overlaps
    ValidateLocomotiveCoverage = true, // Check locomotive assignments cover entire train
    MinTrainSpeedMetersPerClockMinute = 0.3,
    MaxTrainSpeedMetersPerClockMinute = 10
};

var errors = schedule.GetValidationErrors(options);

ValidationError

Validation returns ValidationError objects containing location and time information for highlighting conflicts in a graphical timetable:

foreach (var error in errors)
{
    Console.WriteLine(error.Message);           // Localized message
    Console.WriteLine(error.ErrorType);         // Error category
    Console.WriteLine(error.Trains);            // Trains involved
    Console.WriteLine(error.FromTrack);         // Conflict start location
    Console.WriteLine(error.ToTrack);           // Conflict end location
    Console.WriteLine(error.FromTime.HHMM());   // Conflict start time
    Console.WriteLine(error.ToTime.HHMM());     // Conflict end time
}

// Check conflict type
if (error.IsStationConflict)  // FromTrack == ToTrack
    // Conflict is at a single station track
if (error.IsStretchConflict)  // FromTrack != ToTrack
    // Conflict spans a track stretch between stations

Validation Error Types

Validation Checks by Option

Note: MissingTrackReference, TrainTimeSequence, and TrainTooFewCalls are always checked.

Localization

Validation messages are available in:

• English (default)
• German (de)
• Danish (da)
• Norwegian (nb)
• Swedish (sv)