collapse

* '23-'24 SOTG Tally


2023-24 Season SoG Tally
Kolek11
Ighodaro6
Jones, K.6
Mitchell2
Jones, S.1
Joplin1

'22-23
'21-22 * '20-21 * '19-20
'18-19 * '17-18 * '16-17
'15-16 * '14-15 * '13-14
'12-13 * '11-12 * '10-11

* Big East Standings

Please Register - It's FREE!

The absolute only thing required for this FREE registration is a valid e-mail address.  We keep all your information confidential and will NEVER give or sell it to anyone else.
Login to get rid of this box (and ads) , or register NOW!

* Next up: The long cold summer

Marquette
Marquette

Open Practice

Date/Time: Oct 11, 2024 ???
TV: NA
Schedule for 2023-24
27-10

Author Topic: ND/G-town postgame  (Read 7891 times)

Warriors10

  • All American
  • *****
  • Posts: 571
Re: ND/G-town postgame
« Reply #25 on: January 22, 2013, 10:04:15 AM »
And the blow out loss to Florida would increase that point spread standard deviation.  You could argue that the sample size isn't big enough as a whole to take much from statistics like point spread std. deviation, but calling out 3 data points and saying that shows context and lessens Warrior's Path's point shows misunderstanding of the statistics he generated. 

A better way to attack the stat is to question if a lower std. deviation is actually a good thing.  Sure, it means you are generally losing/winning by the same general numbers, but there needs to be some sort of weighting applied to factor in the quality of opponent.  A close win against a superior opponent and a close loss against an inferior opponent would show small point spread std. deviation, but you could make the valid point that the team was inconsistent.

Well the three data points is approx. 17 percent of data because, as you said, it is a small sample size; I get your point though and I get Warrior's analysis.  I was just pointing out that some data points are different than others because of the time played, but I would agree that this team isn't as inconsistent as people make it out to be. 

TJ

  • Registered User
  • All American
  • *****
  • Posts: 1764
Re: ND/G-town postgame
« Reply #26 on: January 22, 2013, 10:11:30 AM »
Well the three data points is approx. 17 percent of data because, as you said, it is a small sample size; I get your point though and I get Warrior's analysis.  I was just pointing out that some data points are different than others because of the time played, but I would agree that this team isn't as inconsistent as people make it out to be. 
Ok, they're consistently mediocre?  Pitt, GU, and Cincy have good defenses - but we looked REALLY bad on offense those games.  Seton Hall doesn't and we still looked pretty bad.  I'm glad they keep winning, but the goal this year is a tourney birth - not competing for first in the Big East.

Henry Sugar

  • Registered User
  • All American
  • *****
  • Posts: 2007
  • There are no shortcuts
    • Cracked Sidewalks
Re: ND/G-town postgame
« Reply #27 on: January 22, 2013, 10:40:06 AM »
The consistency of our point spread standard deviation is the consistency of both our offense and our defense and the gap between those two. It's not just the point spread itself.

My basic argument is that MU has been consistent lately. For example, we have the #7 offense and the #7 defense in conference. Note that I said "consistent" and not "pretty".

Considering we are 4-1 in conference, being consistent is a good thing, right?
A warrior is an empowered and compassionate protector of others.

Aughnanure

  • All American
  • *****
  • Posts: 2860
Re: ND/G-town postgame
« Reply #28 on: January 22, 2013, 11:31:04 AM »
Counterpoint - An average team in college basketball has a point spread standard deviation of 15. An inconsistent team has a point spread standard deviation of 22. Marquette's point spread standard deviation is 8.

/math

What is this? Did you just make up a standard point spread for inconsistent" teams? If you can't see this team is wildly inconsistent on offense, I don't know what to tell you - but you should look at the scoring differences between halves and the long scoring droughts we run into instead.

We're getting better at it - but trying to say we're not inconsistent because some other teams have been playing worse overall doesn't make sense.  Being inconsistent is not defined by your "point spread."  
« Last Edit: January 22, 2013, 12:31:35 PM by Aughnanure »
“All men dream; but not equally. Those who dream by night in the dusty recesses of their minds wake in the day to find that it was vanity; but the dreamers of the day are dangerous men, for they may act out their dreams with open eyes, to make it possible.” - T.E. Lawrence

g0lden3agle

  • All American
  • *****
  • Posts: 1046
Re: ND/G-town postgame
« Reply #29 on: January 22, 2013, 12:03:45 PM »
The consistency of our point spread standard deviation is the consistency of both our offense and our defense and the gap between those two. It's not just the point spread itself.

My basic argument is that MU has been consistent lately. For example, we have the #7 offense and the #7 defense in conference. Note that I said "consistent" and not "pretty".

Considering we are 4-1 in conference, being consistent is a good thing, right?

Could you go a little more in depth with how you are calculating your numbers?  I thought I understood what you were doing until I read this post.  Thanks in advanced!

Henry Sugar

  • Registered User
  • All American
  • *****
  • Posts: 2007
  • There are no shortcuts
    • Cracked Sidewalks
Re: ND/G-town postgame
« Reply #30 on: January 22, 2013, 12:35:05 PM »
What is this? Did you just make up what a standard point spread for inconsistent" teams? If you can't see this team is wildly inconsistent on offense, I don't know what to tell you - but you should look at the scoring differences between halves and the long scoring droughts we run into instead.

We're getting better at it - but trying to say we're not inconsistent because some other teams have been playing worse overall doesn't make sense.  Being inconsistent is not defined by your "point spread." 

I pulled the numbers from "Basketball on Paper" by Dean Oliver. It's not just some made up standard point spread for inconsistent teams.

I've paid attention to this stat since the Crean years, because many of Crean's teams were really inconsistent. And I've been particularly tracking it this year because I felt the team would struggle early and then improve as the year went on.

Could you go a little more in depth with how you are calculating your numbers?  I thought I understood what you were doing until I read this post.  Thanks in advanced!

It's a moving five game average of the efficiency margin standard deviation. The actual calculation is:

[VAR(Ortg) + VAR(Drtg) - 2*COVAR(Ortg, Drtg)]^0.5

but it's run over five games at a time. I should also clarify that our current five game Point Spread STDEV is 8 and that has been the average for the past nine games. We were very inconsistent for everything around the Florida game (>22), but since the Wisconsin game we've been more and more consistent.

Again, I view this all as a good thing. But hey, if people want to discount the data because it conflicts with their pre-existing notions, go ahead.
A warrior is an empowered and compassionate protector of others.

Aughnanure

  • All American
  • *****
  • Posts: 2860
Re: ND/G-town postgame
« Reply #31 on: January 22, 2013, 12:58:05 PM »
I pulled the numbers from "Basketball on Paper" by Dean Oliver. It's not just some made up standard point spread for inconsistent teams.

I've paid attention to this stat since the Crean years, because many of Crean's teams were really inconsistent. And I've been particularly tracking it this year because I felt the team would struggle early and then improve as the year went on.

It's a moving five game average of the efficiency margin standard deviation. The actual calculation is:

[VAR(Ortg) + VAR(Drtg) - 2*COVAR(Ortg, Drtg)]^0.5

but it's run over five games at a time. I should also clarify that our current five game Point Spread STDEV is 8 and that has been the average for the past nine games. We were very inconsistent for everything around the Florida game (>22), but since the Wisconsin game we've been more and more consistent.

Again, I view this all as a good thing. But hey, if people want to discount the data because it conflicts with their pre-existing notions, go ahead.

Or you can manipulate data to support preconceived notions. There is no standard data on inconsistent teams because, for one, they're inconsistent.

This isn't baseball where the structure of the sport makes it is easy to take data absent from the context of the game and create conclusions. You can be inconsistent in a game and still win, but the only data you are looking at is the end score -  not what happened to get there. It's like saying the game was called fair because the number of fouls were even without taking into account when the calls were given, if the calls changed the game's momentum, how many calls changed the game's possession, etc.  (i.e., crap you can't make data create conclusions for).

Inconsistent is not a synonym for "bad" and pointing out that our most "inconsistent" time came around our statistically worst game of the year really doesn't mean anything.
“All men dream; but not equally. Those who dream by night in the dusty recesses of their minds wake in the day to find that it was vanity; but the dreamers of the day are dangerous men, for they may act out their dreams with open eyes, to make it possible.” - T.E. Lawrence

Henry Sugar

  • Registered User
  • All American
  • *****
  • Posts: 2007
  • There are no shortcuts
    • Cracked Sidewalks
Re: ND/G-town postgame
« Reply #32 on: January 22, 2013, 01:04:31 PM »
Or you can manipulate data to support preconceived notions. There is no standard data on inconsistent teams because, for one, they're inconsistent.

This isn't baseball where the structure of the sport makes it is easy to take data absent from the context of the game and create conclusions. You can be inconsistent in a game and still win, but the only data you are looking at is the end score -  not what happened to get there. It's like saying the game was called fair because the number of fouls were even without taking into account when the calls were given, if the calls changed the game's momentum, how many calls changed the game's possession, etc.  (i.e., crap you can't make data create conclusions for).

Inconsistent is not a synonym for "bad" and pointing out that our most "inconsistent" time came around our statistically worst game of the year really doesn't mean anything.

Whatever you want to believe. I'm not going to discuss this with you any further.
A warrior is an empowered and compassionate protector of others.

akmarq

  • Starter
  • ***
  • Posts: 241
Re: ND/G-town postgame
« Reply #33 on: January 22, 2013, 01:35:04 PM »
Or you can manipulate data to support preconceived notions. There is no standard data on inconsistent teams because, for one, they're inconsistent.


Show me where his methodology is manipulated and how so. Then show me that the manipulation is specifically targeted at producing a certain analytical conclusion.

Please use math or at least terminology relavent to dicussing his method.

boyonthedock

  • Guest
Re: ND/G-town postgame
« Reply #34 on: January 22, 2013, 02:41:25 PM »
I pulled the numbers from "Basketball on Paper" by Dean Oliver. It's not just some made up standard point spread for inconsistent teams.

I've paid attention to this stat since the Crean years, because many of Crean's teams were really inconsistent. And I've been particularly tracking it this year because I felt the team would struggle early and then improve as the year went on.

It's a moving five game average of the efficiency margin standard deviation. The actual calculation is:

[VAR(Ortg) + VAR(Drtg) - 2*COVAR(Ortg, Drtg)]^0.5

but it's run over five games at a time. I should also clarify that our current five game Point Spread STDEV is 8 and that has been the average for the past nine games. We were very inconsistent for everything around the Florida game (>22), but since the Wisconsin game we've been more and more consistent.

Again, I view this all as a good thing. But hey, if people want to discount the data because it conflicts with their pre-existing notions, go ahead.

Does this account for quality of opponent? Because if not, going from Maryland Baltimore County to Florida to Wisconsin to Savannah State is going to make every team look inconsistent in a rolling 5 game average.

Golden Avalanche

  • All American
  • *****
  • Posts: 3164
Re: ND/G-town postgame
« Reply #35 on: January 22, 2013, 03:11:30 PM »
In this context, consistency is being used in reference to on-the-court play, not results.  Otherwise, I would inquire as to why you conveniently left Stephen F. Austin off your list of examples.

If you're only talking about on-the-court play then no team in the history of any game has been consistent.

Henry Sugar

  • Registered User
  • All American
  • *****
  • Posts: 2007
  • There are no shortcuts
    • Cracked Sidewalks
Re: ND/G-town postgame
« Reply #36 on: January 22, 2013, 03:41:47 PM »
Does this account for quality of opponent? Because if not, going from Maryland Baltimore County to Florida to Wisconsin to Savannah State is going to make every team look inconsistent in a rolling 5 game average.

Yes, I agree. We went from crushing UMBC to getting crushed by UF.

This is why I prefer to really only start looking at numbers during conference play.
A warrior is an empowered and compassionate protector of others.

Aughnanure

  • All American
  • *****
  • Posts: 2860
Re: ND/G-town postgame
« Reply #37 on: January 22, 2013, 04:24:29 PM »
Show me where his methodology is manipulated and how so. Then show me that the manipulation is specifically targeted at producing a certain analytical conclusion.

Please use math or at least terminology relavent to dicussing his method.

You don't have to manipulate methodology or data to manipulate an outcome, but your decisions on what data to include or not include can. His findings are based on the end of game point spread - eliminating the ability to judge the inconsistency of our play inside one game, something I think was the focus and meaning of TJ's point.

You want me to mathematically analyze a fancy metric so I can more confusedly come to a conclusion I can clearly see with my eyes? Tough s**t. If you can't clearly see that we play like a bag of hammers sometimes without an overly complex mathematical equation to support it, I don't know what to tell you...but maybe you should start by looking at the only two numbers that matter from our last game:

1st Half: 13 points
2nd Half: 50 points
« Last Edit: January 22, 2013, 05:03:54 PM by Aughnanure »
“All men dream; but not equally. Those who dream by night in the dusty recesses of their minds wake in the day to find that it was vanity; but the dreamers of the day are dangerous men, for they may act out their dreams with open eyes, to make it possible.” - T.E. Lawrence

Benny B

  • All American
  • *****
  • Posts: 5969
Re: ND/G-town postgame
« Reply #38 on: January 22, 2013, 10:17:24 PM »
If you're only talking about on-the-court play then no team in the history of any game has been consistent.

I wasn't actually going to take it that far, but yes, that was pretty much the point.
Wow, I'm very concerned for Benny.  Being able to mimic Myron Medcalf's writing so closely implies an oncoming case of dementia.

akmarq

  • Starter
  • ***
  • Posts: 241
Re: ND/G-town postgame
« Reply #39 on: January 23, 2013, 09:02:13 AM »
You don't have to manipulate methodology or data to manipulate an outcome, but your decisions on what data to include or not include can. His findings are based on the end of game point spread - eliminating the ability to judge the inconsistency of our play inside one game, something I think was the focus and meaning of TJ's point.

You want me to mathematically analyze a fancy metric so I can more confusedly come to a conclusion I can clearly see with my eyes? Tough s**t. If you can't clearly see that we play like a bag of hammers sometimes without an overly complex mathematical equation to support it, I don't know what to tell you...but maybe you should start by looking at the only two numbers that matter from our last game:

1st Half: 13 points
2nd Half: 50 points

I wasn't trying to sound confrontational in my post to you, I was merely wondering what your issue with his metric was and was hoping you could show me. Apologies if the tone came off otherwiese.

You seem interested in looking at MU's offensive point spread between the two halves as a measure of consistency. I'm not sure this is the best way to go about things as it neglects things like fatigue, in-game adjustment, and foul trouble, but here is the difference between our offensive production in each half of our BE games:

MU - CIN: 13/50: differnence of 37
MU - SH: 26/43: differnence of 17
MU - PITT: 33/24 : differnence of 9
MU - GT: 20/29: differnence of 9
MU - UCONN - 30/39: differnence of 9

Average differnence inc. CIN game : 16.2
Average differnence w/o CIN game : 11

I figured the average difference b/t halfs w/o the CIN game because I think there is a compelling case that the CIN game was an outlier (worst half ever played by MU under Buzz perhaps). You will see that we bounced back and played our best half of offensive BE basketball to date in that game as well (they were certaintly inconsistant in that game).

If I have more time I'll try to do this for some other BE teams to get something to compare us to. I'll be the first to acknowledge that there are several flaws with the above, but I also think your method has its flaws as well (in that it's your subjective, observational opinion that you backed up with splits from one game).

akmarq

  • Starter
  • ***
  • Posts: 241
Re: ND/G-town postgame
« Reply #40 on: January 23, 2013, 09:22:49 AM »
Three more schools for points of comparison:

Georgetown
GU - Marq: 19/29: difference of 10 (L)
GU - PITT: 22/23: difference 1 (L)
GU - SJU: 36/31 : difference 5 (W)
GU - Prov: 38/36: difference 2 (L)
GU - USF - 31/27: difference 4 (L)
GU - ND - 34/29: difference 5 (W)

Average difference: 4.5 

Louisville
LU - PROV: 37/43: difference of 6 (W)
LU - SH: 36/37: difference 1 (W)
LU - USF: 38/26 : difference 12 (W)
LU - UCONN: 28/45: difference 17 (W)
LU - SYR - 38/30: difference 8 (L)
LU - VIL - 28/36: difference 8 (L)

Average difference: 8.66 

Syracuse
SYR - RU: 39/39: difference of 0 (W)
SYR - USF: 30/25: difference 5 (W)
SYR - PROV: 30/42 : difference 12 (W)
SYR - VIL: 27/45: difference 18 (W)
SYR - LOU - 38/32: difference 6 (W)
SYR - CIN - 22/35: difference 13  (W)

Average difference: 9

I'd be interested to see what the bottom of the conference looks like. I'll take our record and offensive inconsistency over Georgetowns consistency and record.

TJ

  • Registered User
  • All American
  • *****
  • Posts: 1764
Re: ND/G-town postgame
« Reply #41 on: January 23, 2013, 10:59:21 AM »
I am sorry I used the word consistency, it has derailed this thread.  What I meant was that while we can be good at times, we can also be very, very bad (see the first half against Cincy).  I could easily see the bad coming back to haunt us a few more times before this season ends.

akmarq

  • Starter
  • ***
  • Posts: 241
Re: ND/G-town postgame
« Reply #42 on: January 23, 2013, 11:02:05 AM »
I am sorry I used the word consistency, it has derailed this thread.  What I meant was that while we can be good at times, we can also be very, very bad (see the first half against Cincy).  I could easily see the bad coming back to haunt us a few more times before this season ends.

+1

I think the whole thing got derailed b/c posters were using 'inconsistency' in very different ways and some were equating it with 'bad' and others were not. We do tend to score in spurts, but we usually do so in the second half which, to me, is indicative of good coaching, good player adjustments, and a commitment to drawing fouls. Our bad first half cost us the game at CIN, but I think that second half play has been a strength of this team.

Aughnanure

  • All American
  • *****
  • Posts: 2860
Re: ND/G-town postgame
« Reply #43 on: January 23, 2013, 11:51:08 AM »
I wasn't trying to sound confrontational in my post to you, I was merely wondering what your issue with his metric was and was hoping you could show me. Apologies if the tone came off otherwiese.

You seem interested in looking at MU's offensive point spread between the two halves as a measure of consistency. I'm not sure this is the best way to go about things as it neglects things like fatigue, in-game adjustment, and foul trouble, but here is the difference between our offensive production in each half of our BE games:

MU - CIN: 13/50: differnence of 37
MU - SH: 26/43: differnence of 17
MU - PITT: 33/24 : differnence of 9
MU - GT: 20/29: differnence of 9
MU - UCONN - 30/39: differnence of 9

Average differnence inc. CIN game : 16.2
Average differnence w/o CIN game : 11

I figured the average difference b/t halfs w/o the CIN game because I think there is a compelling case that the CIN game was an outlier (worst half ever played by MU under Buzz perhaps). You will see that we bounced back and played our best half of offensive BE basketball to date in that game as well (they were certaintly inconsistant in that game).

If I have more time I'll try to do this for some other BE teams to get something to compare us to. I'll be the first to acknowledge that there are several flaws with the above, but I also think your method has its flaws as well (in that it's your subjective, observational opinion that you backed up with splits from one game).

Sorry about being confrontational as well. Your post was after Warrior Path's "I'm not going to bother discussing this with you further" cop-out, so I was riled up. Also, manipulate was too strong of a word.

I just don't like bringing in overly complex calculations to discuss something that is very hard to define such as "consistency" and very much based on the eye test. I'm a big fan of stats...in baseball. But I just don't think they apply the same way inside a more constant flow/running sport such as basketball beyond efficiency ratings. There's no clearer point I can show than the blatant discrepancy between home and road play. No stat or calculation can explain, or justify, why an above avg team like Wisconsin is freaking unbeatable at a certain venue or how it makes competitive sense that Kansas can win some 63 games in a row at home. In fact, its down right silly that it works out in that way.

Can we say that we were inconsistent or was it the other team that was? Is it simply missing your shots or is it poor offensive motion and getting up poor shots? I think stats answer a lot, but consistency against different teams and players in different situations is an exceedingly difficult calculation (especially as someone wisely pointed out, basketball is a game where all teams play inconsistently - so where's your base start from?). I think people were drawing WAY too big of conclusions on whether this team plays inconsistent or not from the end of games scores.
“All men dream; but not equally. Those who dream by night in the dusty recesses of their minds wake in the day to find that it was vanity; but the dreamers of the day are dangerous men, for they may act out their dreams with open eyes, to make it possible.” - T.E. Lawrence

Niv Berkowitz

  • All American
  • *****
  • Posts: 1302
Re: ND/G-town postgame
« Reply #44 on: January 23, 2013, 12:31:53 PM »
"Inconsistent" is the word that nay-saying fans of every top 25 team use to describe their team.  The only D-I teams that have been consistent this year are those that are consistently bad.

It doesn't matter how well you play the game or how good you look... the only thing that matters is what the scoreboard says when the clock hits 0:00.  Just ask Gonzaga.

Then let me add-on to the previous statement.

We are wildly inconsistent and we lack a go-to scorer. Many a team remains inconsistent, but they at least have one or two go-two guys to get the biscuit in the basket. We don't have that. We also have a downlow scorer that can only play 25 effective minutes at most. So put all three of those things together and you have cause for concern this year.

 

feedback