Hello in turn.
Personally my reason (not a problem) was to design "threads" in timetable for freight trains, with unknown timings, as well as for passenger trains, the information about which is unavailable. Instead of long-time consuming experiments, I tried to use a graphical method to calculate crossing times. You can read about it at the first post of this thread above.
Sure, the dispatcher will not allow trains to collide, but we need an optimal timetable instead of too long waiting of opposite train somewhere, aren't we?
Using a traffic-graph's gird in timetable design process The pretty idea
#12
Posted 07 August 2021 - 01:57 PM
nounours1952, the graphics makes it easier and quicker to find the meetings between trains and have the train designation at hand.
There wouldnt be any problems unless the original timetables were wrong...
I have massivly introduced all of my contry's timetables into jgraph and guess what? There were a lot of errors. most of the times with the times meeting on stations in single track routes, but sometimes in overtakings done where that would not be possible, meaning, there were errors in printing :)
There wouldnt be any problems unless the original timetables were wrong...
I have massivly introduced all of my contry's timetables into jgraph and guess what? There were a lot of errors. most of the times with the times meeting on stations in single track routes, but sometimes in overtakings done where that would not be possible, meaning, there were errors in printing :)