开云体育

I have just loaded 4.13.6 in order to get at Timetable - I just couldn't resist it!

I'm sorry, but I have broken the new toy.? I am an oddball in that I want to use it for a real timetable with real distances and speeds - not a model.? If I use feet the numbers are very large and the graph function produces a maximum window size graph with only 4 of the 7 stations on it all equidistantly spaced.? If I use metres it reduces the size of the numbers and the graph comes out with all the stations showing in the right order, in a small window, at reasonable spacing etc. BUT of course it expects my speeds in KPH so the timetable doesn't match with the real thing.? If I change the values to equivalent KPH I need decimal places for accuracy, but I am only allowed integers. UGH!

I doubt that this is of any importance to anybody else, but I'd like miles (or chains or yards) and MPH please?

A bit more information.? After entering the 7 stations in ascending order using feet, it is noticeable that on saving and reloading the order changes.? The numbers shown are still correct(???) but the order is now off.? The graph is "correctly wrong" i.e. the left hand column has the stations in the correct order BUT only 4 of the 7 at equidistances.? HOWEVER the calculated times for the journey ARE CORRECT on the face of the graph.? So the first station shows the correct departure time, as does the next and so on.? The graph Y axis is wrong but the right times for the trains are there.

So there are three lurking problems 1) in the list of stations which incorrectly sorts, but the distance in feet values are correct in the interface and on the TimeTable.py output.
2) the correct timings are being calculated at and between stations in feet and mph, and displayed on the graph 3) the graph Y axis is failing to calculate the distribution of stations properly, and losing 3 of the 7 -? value in feet for the final station displayed is 97152.0 - the stations beyond that point are 170016 and greater.

Sorry I meant to add it looks like 2^16 to me??

Iain,

If you could send me the TimeTableData.xml file (user files location / timetable) or upload it to ProblemsBeingWorkedOn, it would help me figure out what is actually happening.

Dave Sand

How send???

Iain,

The method that I used to sort the station distances breaks down with large numbers.

Due to the release schedule for 4.14, I am not going to be able to get the fix into the next production release. It should be included in the 4.15.1 test release.

In the meantime, if you divide the distance for each station by 10 and set the custom scale to 10, the station sequence and graph look ok.

Dave Sand

Thanks I'll have a look at that.

I have done as you suggest with the Ullapool - Lochinver branch which also didn't work but which is shorter to play around with.? It works fine - thank you.? I can play a bit and will update it when the "fixed" version is put up.

By the way it is spot on with my Google Sheets timetable - so all the calculations are good so far.

Thank again.