Thanks for the various comments etc.
Some answers :
Quote
Do you own a copy of the SWB route? if so I can attach the timetable and paths for your perusal.
I haven't got that route as yet - but there's always room for one more.
What and where is it?
Quote
You state that start and end points of the different paths used must match one another. What do you mean by match (be located within the same platform / signal block, or be simply close together)? If the latter, how exactly must they match?
Begin and end need to be in the same signal block, or section between switch nodes if there are no signals.
When placing multiple trains on a single siding which may be split by signals or switches, it is best to run all paths through to the end (both ending and starting paths) - if the train is set behind other trains the system can work out the required actual start and stop position.
The same goes for 'runround' path - no need to carefully start or end this in front of the train, starting and ending anywhere on that section will do nicely.
Quote
PS: I know exact station names can more or less easily be retrieved from a route´s TDB file, anyway, on large routes, this might be a little bit complicated. Are you planning to once write a timetable editor to cope with that and various other more difficult aspects of the timetables? (I know this will be way in the future, if at all. It is just that while imagining a few things while reading the documentation, one or the other idea came to my mind how timetable creation could be facilitated).
Presently, only stations (platforms) can be set as timing points.
However, the idea is to generate a new 'path' tool which can create 'locations' anywhere in a route. A 'location' can be a station, siding, yard etc., but also just a signal or a stretch of track.
An additional function of that tool might be the generation of a full 'location' list.
A full timetable editor is not on the cards, really - that would come close to building one's own spreadsheet tool.
Quote
As time permits, I will be using Amtrak timetables to generate an Excel spreadsheet that I would like to use with the NEC4 route that runs from Philadelphia to Wsahington, DC. One of the fascinating aspects of this section of the Northeast Corridor is the presence of NS and CSX freight trains. Though these trains are generally restricted to night runs to avoid the daytime passenger traffic, occasional problems on the freight lines will result in daylight appearances of various types freight traffic in competition with passenger trains.
Sounds a good idea. Let me know if you have any questions or need a bit of help to get going.
Quote
As I understand it, the Excel timetable would include the passenger trains (based on arrival times at the various stations along the line). Perhaps I am wrong, but I would imagine that freight trains, although not generally scheduled, would have to be included in the Excel timetable (?).
Yes, freight trains would go in there as well. They would have a starttime, but do not need any intermediate timings.
At present, all trains must be defined in a single spreadsheet. The intention is, however, to make it possible to use multiple files. In that situation, you could put the freight trains in a separate file.
Quote
However, if one wanted to alter the freight train times, this could be accomplished simply by modufying the Excel timetable. Perhaps I am wrong here.
Yes, just change the starttime, consist or path and you have a different freight.
Quote
Also, the freight train(s) would also require a path with passing paths. Regarding the latter, it seems that all trains (passenger and freight) would require passing paths (?) though, obviously, the passenger trains would need to have access to station platforms.
Passing paths only work for trains in opposite directions (it is part of the 'deadlock' processing). It does not work to allow trains to overtake. As most of this route is double track, there is no need for passing paths. But you may have to set up some paths of the freight trains through loops or 'slow' lines if passenger trains must be allowed to overtake them.
Quote
One of the issues that I am not certain about concerns the nature of starting and ending points for the freight train. There are a few locations where NS freight trains could enter the NEC (e.g., the connection of the Port Road Branch from Harrisburg, PA, with the NEC at CP Perry).
That's just all in the paths for the freight trains - no real difference there between timetables and activities.
Start and end points of paths need not be any of the stations. Trains - both freight and passenger - can start and anywhere on the route; the station times are only used to ensure trains run to their booked times.
Quote
Perhaps a more significant issue (perhaps something to be addressed in the future) is a system of priotizing trains. Freights are lowest of the food chain. In fact, they may wait hours to move during rush hour (we want to try to aovid this in an activity). You certainly wouldn't want to hold a Boston - Washington DC passenger train for a 120-car empty coal train.
Real priority selection would require a major rework of the 'section reservation' logic, and is not on the list for a fair time to come.
However, if you have some idea of the timing of the freight trains with relation to the passenger trains running in the same direction, you can use the 'follow' command to make sure the freight trains give priority to those passenger trains.
Because the freight trains have no stops and might not pass through platforms, you would need to define that at the 'top' of the column (in the 'note' row).
Another option you might consider is to 'split' freight trains, making them run parts of the route between yards or sidings. Using the 'form' command, you can still set this up as a single through freight working. It would, however, allow freight trains to shift from following one passenger train to following the next one. Perhaps not waiting for hours (even though that would be quite possible, specifically if split in 'portions' as suggested), but it would allow the freight trains to be overtaken.
Another option, but more difficult to arrange, is using the 'waitany' command, using a fairly long path backward from a yard or siding exit, which would force the freight train to wait for any approaching passenger train.
Finally a bit of help for those who want to get started.
Attached is the most 'basic' timetable : just one train, no stops defined.
Choose any route, select a train you now run in an activity, set its consist and path in the appropriate fields, add a name and starttime - and you have a timetable.
From that on you can build it up slowly : add another train or trains, e.g. in opposite direction. Then add stations and stops etc.
EmptyBasicTimetable.zip (3.76K)
Number of downloads: 867
Another bit of advice : it can be very useful to include an 'observer' in the timetable. This is a train which just has a very short path in a siding somewhere where no other train will ever come. You can use this 'observer' to check on everything that goes on. Just select the observer as player train, and use camera 8, the F5 dispatcher Hud or the dispatch window to check on what happens and, for instance, which trains are causing a blockage. In contrast to an activity, you do not need to create a complete new timetable to use such an observer. And you can simply change the starttime if you want to check trains at other times in the day, or set a different path if the problem is in another location. The ultimate test is to start the observer at 23:59 - and check all trains have reached their destination.
I've sorted all problems for the Surfliner timetable (and there were plenty!) not by running any trains but by using such an observer until everything ran to the end of the day. Only then could I really start to run trains.
And, admittedly, 'virtual train spotting' at LA Union Station during the rush hour was actually quite interesting.
Regards,
Rob Roeterdink
Log In
Register Now!
Help
roeter, on 25 May 2014 - 04:37 PM, said:
TT_example.png
