Rails scheduler adjust for time zone how to#
Rails scheduler adjust for time zone update#
Rails scheduler adjust for time zone manual#
Rails scheduler adjust for time zone full#

Now the timetable is done for train #1.ġ0. Continue clicking Copy, Paste, Bulk shift and change, to create orders for the rest of the week. Click Copy, Paste, Bulk shift and change. Under Bulk edit orders, in Shift field, type 24:00:00. one run too many on AB), edit depot line X order to accelerate it a few minutes.ĩ. If the last run on AB is just before 23:00 (i.e. one run too few), edit the depot line X order to push it back a few minutes. If the last run on AB is before 21:00 (i.e. Check that the first run on line AB starts a few minutes before 6:00, and that the last run on line AB starts a few minutes before 22:00, and also that each run on line AB has the same height in the table (i.e. Scroll up and down through the timetable on the right of the list of orders.

Ensure 'Loop until next order' is NOT checked.

Rails scheduler adjust for time zone full#

The time you enter should be after 22:59 + trip time from A to X, but before 23:59 + trip time from A to X - otherwise train #1 will make another full run). Give it a good cushion and enter say 23:30:00 into the field near At: Monday. Guess at how long it would take for the train to get from A to X - say 5 minutes. To send train #1 to the depot after 22:59, under Append new order, in Run line, select X (depot line). Determine your last desired departure time - to finish line operation around 23:30, I would set the last run for train #1 to be 22:00, so train #1 will complete the run and return to A at 22:59 before heading to the depot (and train #6 will operate until 23:49). Now train #1 will leave station A at 6:00, 7:00, etc.ħ. Ensure 'Loop until next order' is clicked. Type 6:00:00 in the field near At: Monday. Ensure Enter event says Depart exactly at.

Rails scheduler adjust for time zone manual#

For train #1, go to Orders, change Mothballed to Manual orders. Acquire 6 trains (#1-#6) and give them Order 'Mothballed' initially, to prevent wrong orders being given.Ħ. Set service level to Technical maneuvers and Stop behavior to Black hole main, wait secondary.ĥ. Define depot line X with just one station at X. Check now that both Custom loop and Native loop are at 1:00:00.Ĥ. Ensure Custom duration remains black (not red). Add 2 minutes 37 seconds to the already existing time at station A. Determine where you prefer trains to spend this additional time. NIMBY will automatically add 2 minutes 37 seconds to the last station in the line, which may not be convenient. Under Default timings, define Custom duration to be 1:00:00.ģ. For a 10 minute interval, it's convenient to increase the line round trip to 60 minutes. 57 minutes 23 seconds is inconvenient for timetabling. I presume here station A is the first station.Ģ. This line service level should be Passenger service. Define line AB with relevant stations, stops, etc. The full line takes 57 minutes 23 seconds (Native loop) for round trip, including layover times.ġ. At night the trains are stored in depot X near station A. Objective: Create a line that operates on a simple fixed interval schedule with only one train schedule being managed (all others being copies), every 10 minutes from 6:00 to 23:30, from A to B (and back). Let me do an attempt at suggesting a simple way to create a line operating similar to 1.4 (but better, as it would be on a timetable).

It's probably a full time job at a larger transit company. I created one line timetable today, and it took over an hour and probably another hour to fix errors in it. That said, creating a good timetable is one of the more complex tasks in transit planning, with or without software. I am one of those people who do appreciate the complexity of the new system.

I know others may not agree, and others are using the new features fine. This was much more convenient than (what I think is) the current solution of creating a service line and a station with 0m radius? I understand this gives more options, but the complexity is getting a bit out of hand. I'd love to use timetabling to create peak services, stop at night etc, but it's just so much easier to keep everything running in the loop. I'm browsing forums and guides, only picking up pieces, and can't figure it out.

Rails scheduler adjust for time zone how to#

But, combined with already complex signalling, I do think there needs to be a better way to teach players how to use all these systems. Adding a methodology for peak and timetabling makes sense, gives the player options and I understand makes coding PAX more efficient. I understand, appreciate and support the roadmap.

Rails scheduler adjust for time zone update#

Though, the added complexity with each update is dampening, rather than enhancing the experience (IMO).