## Conditional Logic in LR

Prepare for the LSAT or discuss it with others in this forum.
scalawag Posts: 172
Joined: Sat Apr 18, 2015 4:50 pm

### Conditional Logic in LR

So this post is concerned with conditional logic in instances where the average test taker needs to be aware of it to answer the question correctly.

What question types does it appear the most frequently in?

What is your strategy for answering the question? Do you start diagramming as soon as you see that it is conditional logic (it seems like this could eat up some time) or do you wait until you get to the answer choices and determine that you need to diagram to answer the question?

Thanks

Alexandros Posts: 6478
Joined: Thu Jun 09, 2016 4:46 am

### Re: Conditional Logic in LR

I think the most common ones are Parallel flaw/reasoning, must be true, and some ID the flaw and assumption questions.
I only diagram conditional logic on parallel flaw/reasoning and the most challenging of the MBT, ID the flaw, and assumption questions. I find a lot of questions with conditional logic are pretty intuitive so diagramming isn't necessary.
My theory with diagramming is - if you can answer it intuitively, then do so. If it's got conditional logic and your eyes glaze over reading it, diagram immediately, because trying to think it out will be more of a time sink than diagramming on the most challenging ones.

eta: I usually diagram immediately on parallel questions when they have conditional logic, with the other questions I'll diagram if I see the stim is very complex or if none of the answers jump out as correct with one or two careful read-throughs.

scalawag Posts: 172
Joined: Sat Apr 18, 2015 4:50 pm

### Re: Conditional Logic in LR

Alexandros wrote:I think the most common ones are Parallel flaw/reasoning, must be true, and some ID the flaw and assumption questions.
I only diagram conditional logic on parallel flaw/reasoning and the most challenging of the MBT, ID the flaw, and assumption questions. I find a lot of questions with conditional logic are pretty intuitive so diagramming isn't necessary.
My theory with diagramming is - if you can answer it intuitively, then do so. If it's got conditional logic and your eyes glaze over reading it, diagram immediately, because trying to think it out will be more of a time sink than diagramming on the most challenging ones.

eta: I usually diagram immediately on parallel questions when they have conditional logic, with the other questions I'll diagram if I see the stim is very complex or if none of the answers jump out as correct with one or two careful read-throughs.

Thank you sir

SunDevil14 Posts: 478
Joined: Wed Apr 27, 2016 7:35 pm

### Re: Conditional Logic in LR

I'd diagram parallel reasoning questions with conditional logic. You are looking at 6 different arguments in a very short amount of time. The slightest lapse in memory can lead to an incorrect answer and or spending much more time on the question.

Blueprint Mithun Posts: 456
Joined: Mon Sep 14, 2015 1:54 pm

### Re: Conditional Logic in LR

scalawag wrote:So this post is concerned with conditional logic in instances where the average test taker needs to be aware of it to answer the question correctly.

What question types does it appear the most frequently in?

What is your strategy for answering the question? Do you start diagramming as soon as you see that it is conditional logic (it seems like this could eat up some time) or do you wait until you get to the answer choices and determine that you need to diagram to answer the question?

Thanks

The three most common question types to feature conditional logic are:

Must Be True (Inference) questions. This is especially true of the ones that explicitly ask for something that must be true, rather than the "most strongly supported." With MBTs, you'll want to diagram all the conditionals and see if you can make any inferences using contrapositives and the transitive property. Do this even before you look at the answer choices - if one of your inferences shows up in there, it's the correct answer.

Parallel/Parallel Flaw questions. If the stimulus features conditionals, then you can be sure that the correct answer will have the exact same conditional logic, just with different terms. So diagram the stimulus, try and eliminate any answers that obviously don't match up (not enough conditionals, not the same logical strength, etc.), and diagram out any answers that you think are viable in order to test them. This can be time-consuming, so once you've moved on to timed practice, be wary of the clock.

Sufficient Assumption questions. In this case, you're looking for something that bridges the gap. Diagram out the stimulus, but be sure to put the premises and conclusion in the correct place. Afterwards, try and come up with at least one conditional statement that would link the premises to the conclusion. So if your premise was "A --> C" and your conclusion was "A --> F," some valid answers would be "C--> F" and "Not F --> Not C." As with MBTs, you may have to play around with contrapositives to find the correct answer.

With each of these three question types, if I see conditional statements, I immediately begin diagramming the stimulus. With Parallel questions, I rarely diagram every answer because that's so time consuming, but I'd recommend doing that for practice, just not in a real testing situation.

scalawag Posts: 172
Joined: Sat Apr 18, 2015 4:50 pm

### Re: Conditional Logic in LR

Blueprint Mithun wrote:
scalawag wrote:So this post is concerned with conditional logic in instances where the average test taker needs to be aware of it to answer the question correctly.

What question types does it appear the most frequently in?

What is your strategy for answering the question? Do you start diagramming as soon as you see that it is conditional logic (it seems like this could eat up some time) or do you wait until you get to the answer choices and determine that you need to diagram to answer the question?

Thanks

The three most common question types to feature conditional logic are:

Must Be True (Inference) questions. This is especially true of the ones that explicitly ask for something that must be true, rather than the "most strongly supported." With MBTs, you'll want to diagram all the conditionals and see if you can make any inferences using contrapositives and the transitive property. Do this even before you look at the answer choices - if one of your inferences shows up in there, it's the correct answer.

Parallel/Parallel Flaw questions. If the stimulus features conditionals, then you can be sure that the correct answer will have the exact same conditional logic, just with different terms. So diagram the stimulus, try and eliminate any answers that obviously don't match up (not enough conditionals, not the same logical strength, etc.), and diagram out any answers that you think are viable in order to test them. This can be time-consuming, so once you've moved on to timed practice, be wary of the clock.

Sufficient Assumption questions. In this case, you're looking for something that bridges the gap. Diagram out the stimulus, but be sure to put the premises and conclusion in the correct place. Afterwards, try and come up with at least one conditional statement that would link the premises to the conclusion. So if your premise was "A --> C" and your conclusion was "A --> F," some valid answers would be "C--> F" and "Not F --> Not C." As with MBTs, you may have to play around with contrapositives to find the correct answer.

With each of these three question types, if I see conditional statements, I immediately begin diagramming the stimulus. With Parallel questions, I rarely diagram every answer because that's so time consuming, but I'd recommend doing that for practice, just not in a real testing situation.