What was the score of the Duke vs Purdue game in the Sweet Sixteen?”
HOUSTON — An NCAA tournament that has defied convention now has one of the sport’s blue bloods back in a familiar place. This Story * South Region: It’s like old times for Blue Devils * Box score: Duke 70, Purdue 57 Top-seeded Duke outlasted fourth-seeded Purdue, 70-57, on Friday night to earn its first region final appearance since 2004, the last time the Blue Devils reached the Final Four. They will play third-seeded Baylor in Sunday’s South Region final. The loss ended an impressive tournament run by the Boilermakers (29-6), who were counted out by most of the country after losing standout Robbie Hummel to a season-ending knee injury Feb. 24. Defense helped Purdue reach the Sweet 16, but the Boilermakers could not shut down Duke’s Big Three — Kyle Singler, Jon Scheyer and Nolan Smith — each of whom had his offensive moments down the stretch Friday. The Duke-Purdue matchup was not a favorite of those who prefer free-wheeling, full-court action. Every pass was contested, every poss
Top-seeded Duke outlasted fourth-seeded Purdue, 70-57, on Friday night to earn its first region final appearance since 2004, the last time the Blue Devils reached the Final Four. They will play third-seeded Baylor in Sunday’s South Region final. The loss ended an impressive tournament run by the Boilermakers (29-6), who were counted out by most of the country after losing standout Robbie Hummel to a season-ending knee injury Feb. 24. Defense helped Purdue reach the Sweet 16, but the Boilermakers could not shut down Duke’s Big Three — Kyle Singler, Jon Scheyer and Nolan Smith — each of whom had his offensive moments down the stretch Friday. The Duke-Purdue matchup was not a favorite of those who prefer free-wheeling, full-court action. Every pass was contested, every possession proved a struggle for two teams whose calling card is defense. At one point, Purdue’s Chris Kramer, the Big Ten’s defensive player of the year, remained on the floor for a few minutes during a timeout after run