Page 1 of 1
| Detecting conflicting movements in TT Analyzer 20/12/2020 at 09:06 #134940 | |
9pN1SEAp
1102 posts |
Hi, With a new timetable I'm testing which has a lot of shunts at RPLANEX/RPLLWSS, it would be good if the Analyzer could highlight where two trains are trying to occupy the same location. In its simplest form, one could apply the algorithm per 'platform' thus: * if passing time is ticked, AND the previous activity on that platform is not (depart or start), the movements conflict. Obviously once you consider things such as detached portions, or overlapped Arr/Dep, then the above isn't going to be perfect but I think it could be relatively easy to add. Thanks Jamie Jamie S (JAMS) Log in to reply |
| Detecting conflicting movements in TT Analyzer 20/12/2020 at 13:03 #134949 | |
bill_gensheet
1314 posts |
As you say portions etc are meant to occupy the same platform but the pattern of --E and B-- entries is consistent. I generally find that a quick scan of the analysis output works quite well if you are expecting E-- --B E-- --B A>> >>D The pattern --E --E B-- B-- is worth a look if you are doing a unit timetable, but is what you would expect for a loco hauled one or a regular double docking. Parsing the text file and running it through a spreadsheet would be pretty simple, "if B25=B26 text = red" would find all platform share / double dock examples Log in to reply |