Our ridiculously unrealistic path to #9

[WACB]

Based on various computer ranking systems:


Jeff Sagarin PREDICTOR
----------------------
(16) 64 Saint Mary's-Cal.
(8) 32 Purdue
(4) 16 Notre Dame
(2) 8 Utah
(1) 4 Arizona
(1) 2 Wisconsin


kenpom.com
----------------------
(16) 64 South Carolina
(8) 32 Maryland
(4) 16 Notre Dame
(2) 8 Utah
(1) 4 Wisconsin
(1) 2 Arizona


Massey Ratings
----------------------
(16) 64 Kansas St
(8) 32 LSU
(4) 16 UNC***
(2) 8 Kansas
(1) 4 Duke
(1) 2 Virginia


RPI
----------------------
(16) 64 Harvard
(8) 32 Buffalo
(4) 16 Louisville
(2) 8 Gonzaga
(1) 4 Villanova
(1) 2 Kansas


BPI
----------------------
(16) 64 Illinois State
(8) 32 Iowa
(4) 16 Ohio State
(2) 8 Kansas
(1) 4 Arizona
(1) 2 Wisconsin


Which one would you want?

 

[BigBlueFanGA]

I'd take RPI, what a joke, just hand us the trophy and history.

 

[*dezyDECO*]

I'll take the RPI:



RPI
----------------------
(16) 64 Harvard
(8) 32 Buffalo
(4) 16 Louisville
(2) 8 Gonzaga
(1) 4 Villanova
(1) 2 Kansas

KU in the Title Game, without Alexander... seems like easy pickin's!

 

[LowCountryCat]

Kenpom and Massey are wrong, at large teams don't get 16 seeds.

 

[WACB]

Originally posted by Prime MF:

Kenpom and Massey are wrong, at large teams don't get 16 seeds.

That's what makes it ridiculously unrealistic. I just looked at the top 64 teams.

 

[FiveStarCat]

This is roughly the way it should be. "Geography" (in quotes because what the NCAA really means when they say that is "money") is skewing the bracket balance in a way that is unfair to the Midwest.

 

[jwheat]

RPI by a landslide. How is it possible to have that many byes?

 

[sonnyg333]

RPI

 

[CatPhight_rivals65113]

South Carolina? Pomeroy has been smoking rock again.

 

[Big_Blue79]

^ ah yes, the old "algorithm doing drugs." Mmm... computer code drugs.

 

[CatPhight_rivals65113]

Originally posted by Big_Blue79:
^ ah yes, the old "algorithm doing drugs." Mmm... computer code drugs.

To suggest South Carolina will win the SEC Tournament as the 11th seed and grab the automatic berth...yeah I would like to see the size of the rock those coders burnt before they input those variables.