Page 1 of 1
| Mutually Exclusive 16/12/2011 at 21:43 #25664 | |
Gwasanaethau
509 posts |
Hi All, Whilst I use examples from the Trent default timetable, the question applies to all timetables so I thought it best to post here. There are two trains that start in different locations at different times but end up at the same place at the same time (and even change to an identical next working). There are no rules to stop them from both appearing. Is it sufficient to declare a rule making them mutually exclusive or do I need to fiddle around with the probability settings for one or both of them too? If you need examples, 5M041 and 5M042 in the Trent default timetable (2007 v3.9) are ones that illustrate this. Thanks again! Mark. Log in to reply |
| Re: Mutually Exclusive 16/12/2011 at 21:50 #25665 | |
Steamer
3985 posts |
One train should have a probability set, and then the trains set to be mutually exclusive. Otherwise, one train (probably 5M041, since it is first alphabetically) will always appear unless the Sim has randomly delayed it.
"Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q) Log in to reply The following user said thank you: Gwasanaethau |
| Re: Mutually Exclusive 16/12/2011 at 21:51 #25666 | |
AndyG
1842 posts |
easiest way at present is to make one run a percentage of the time, the other to run 100% but with a rule "not run if train one runs"
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either. Log in to reply The following user said thank you: Gwasanaethau |
| Re: Mutually Exclusive 16/12/2011 at 21:54 #25669 | |
|
Gwasanaethau
509 posts |
Coolio, thought it might be something like that. Thanks guys!
Log in to reply |
| Re: Mutually Exclusive 16/12/2011 at 22:49 #25675 | |
Peter Bennet
5402 posts |
Depending on the core code the Sim was built on you may need to experiment till you get the desired result as problems have been identified on some Sims and not on others. Mutually Exclusive works slightly differently from A must not run if B (don't ask me- I don't know). In some instances you may find A Mut Ex B plus B Mut Ex A is necessary but in others neither train will enter with that pair of rules and one will suffice. If you use the A must not run if B runs you should also have B must not run if A runs (the XOR key can be used to create the pair). The explanation on the Wiki worked on the Sim I used as the test bed but, as I say, difficulties have been experienced on some Sims (hopefully fixed going forward). Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Re: Mutually Exclusive 03/01/2012 at 13:40 #26720 | |
|
bill_gensheet
1414 posts |
With two different trains, the probability must be set for the first one that appears, timewise. It gets a little complex if they are entering around the same time, as you have to consider if the one with probability gets a delay greater than the 100% one, then to 100% one will turn up more often than you expect. So 6K22 entering 05:30 at 50%, and 6P90 entering 05:40 (notif 6K22) will *not* produce equal numbers of 6K22 and 6P90, you get about 60% of 6P90's. I'm a bit confused at Peters's comment on MutEx differing from a set of NOTIF rules, using the timetable editor all that 'are mutually exclusive' does is to write a full set of NOTIF rules, unless that is a recent change regards Bill Log in to reply |
| Re: Mutually Exclusive 03/01/2012 at 14:21 #26729 | |
|
Peter Bennet
5402 posts |
" said:With two different trains, the probability must be set for the first one that appears, timewise. It gets a little complex if they are entering around the same time, as you have to consider if the one with probability gets a delay greater than the 100% one, then to 100% one will turn up more often than you expect.I had the same understanding which Clive disabused me of. The tool to create a set of NotIf rules is not the same as the Mutually Exclusive rule itself which is accessable via the rule list. The distinction escapes me at this time but it works differently internally and in some old core-code not at all. Peter I identify as half man half biscuit - crumbs! Log in to reply |