WGC Bridgestone Invitational

[QUOTE=TheDude;24863]Very nice comeback by Big Brendon DeJonge.[/QUOTE] [QUOTE=Alf M;24863]Comeback? Brendon de Jonge was never behind in that match. jajaja...[/QUOTE] PMJI, I think TheDude was speaking about DeJonge coming back from being behind DURING the first and second rounds. Especially important was being down a stroke to Taylor and potentially missing the cut around the 11th hole of the second round. DeJonge then went from EV to finish the 2nd round at -3. From then on, he was never behind.

[QUOTE=ComptrBob;24910]PMJI, I think TheDude was speaking about DeJonge coming back from being behind DURING the first and second rounds. [/QUOTE] Correct Bob. Just glad it all worked out.

Hello Bob, didn't know you were so versed and exact in following our golf matchups, you must have bet them your self? yes?

[QUOTE=Alf M;24927]Hello Bob, didn't know you were so versed and exact in following our golf matchups, you must have bet them your self? yes?[/QUOTE] Certainly not as versed as you and TheDude, I appreciate following the logic behind betting these tournament matchups. These days, its easy to have the leaderboards visible during the day to follow the tournaments. One question I have is do you and/or TheDude explicitly model the probability of missing the cut into your handicapping (either getting an early win or suffering an early loss) or is it just part of the overall probability of the total win? Obviously, in many cases of really elite golfers, missing the cut is a pretty small probability, but with middle of the road guys, its a very real possibility.

Well, I always want my opponents to miss the cut, and yes, this is a major part of my strategy, especially going against struggling players. If we can't win at the cut then we are positive that the cream rises to the top over 4 rounds if necessary. Over the years of the matchups that I win, 62% are determined before the cut, which is key and really helps your overall percentage.

Alf when do you plan to post PGA selections?

wrong thread...oops