Diagramming "Or" Constraints using the Tree Method

[lsataddict]

How are "or" clauses diagrammed using the tree method for relative ordering games?

For example, what would the tree look like for the following scenario:

C is taller than D.
E is shorter than D.
C is shorter than A or B.*
F is taller than E.

It’s the third rule that concerns me. If the "or" was replaced with an "and," I know exactly what to do. I have the same problem with "either" as I do with "or."

Thanks!

[shehadehr]

Hey, so what I usually do is right away when I notice the game is relative ordering (usually done by quickly glancing at the rules), I immediately begin the tree. Sometimes the tree isnt smooth, like in one of the games I did in PT 56 today. "Or" constraints, to me, are considered not smooth for sure, so what i do is the following:

say you have your first constraint down, H -- G, so you mark that off then skim down to contraint 4 that says G -- L. Then, you hit that "OR" constraint, because of the last two, the "OR" constraint is the only one that includes either H G or L, what I do here is, for example, if it says "M goes better H or after after L, but not both," I then quickly lay out a replica of my already made "H -- G -- L" tree, so that I have two exact ones (this should take 5 seconds) laid out side by side, and then, for the left one I put "M -- H -- G -- L" and for the right one I put "H -- G -- L -- M."

In short, anytime I see an "OR" contraint, I immediately know I'm going to have to draw the same tree I have set up to that point, again quickly, and then immediately move to bang out that "OR" constraint and keep moving to the next constraint, last constraint, etc.

btw, after you have two tree side by side, following your "OR" constraint, do not forget to, when continuing to diagram the constraints (if there are any left), draw that next constraint on BOTH trees! Don't forget that. Crucial. Remember these are money in the bank games, so never let the "OR" factor turn you off--instead attack it

-Ray

[shehadehr]

How are "or" clauses diagrammed using the tree method for relative ordering games?

For example, what would the tree look like for the following scenario:

C is taller than D.
E is shorter than D.
C is shorter than A or B.*
F is taller than E.

It’s the third rule that concerns me. If the "or" was replaced with an "and," I know exactly what to do. I have the same problem with "either" as I do with "or."

Thanks!

wow instantly realize you have something up, so for that I would do it like this:

1. D -- C
2. E -- D -- C
3. E -- D -- (with A hanging down left of C) -- C -- B
or
E -- D -- (with B hanging down left of C) -- C -- A

4. Now with both trees (see 3) side by side, simply have F hanging to the right of E, and you're ready to hit the questions.

-Ray