Showing posts with label Corey Anderson. Show all posts
Showing posts with label Corey Anderson. Show all posts

Sunday, 13 September 2015

Anderson or Neesham

An email dropped in my inbox on Friday from New Zealand cricket naming the squads for the test series with Australia and the NZA squads to play Sri Lanka A. There was a lot to talk about, with new players being named in the A squad and the prospect of a day-night test coming up. But over 1/4 of the press release focused on two players: Jimmy Neesham and Corey Anderson. When I got in the car to come home from work, I listened to a debate between Darcy Waldegrave and Goran Paladin about who should be picked, Anderson or Neesham.

A quick scroll through the different websites I check for cricket news found that this was the story that most writers picked up on:
Cricbuzz put down their Indiacentric blinkers to lead (briefly) with "James Neesham, Corey Anderson named in Test squad for Australia Tour".
Andrew Alderson's piece in the New Zealand Herald was Anderson v Neesham: Let the contest begin.
David Leggatt wrote a piece for the Otago Daily Times titled Cricket: Black Cap selectors face all-rounder quandry.
Mark Geenty went for the slightly more negative Concerns remain over Anderson, Neesham as recovery race heats up for Brisbane on stuff.co.nz.
Wisden India went for Anderson, Neesham return for Australia Tests.

It was clear that this was the key talking point for most people.

And that's fair enough too. It's not often that a team has a genuine all rounder. To have two players who have the potential to develop into such players is remarkable. Given that neither are quite there as being both first choice batsmen and bowlers, to pick them both is unlikely, so a show down is likely.

Neesham is probably less aggressive than Anderson with the bat, which has led to him having more success in the few tests that he's played in. Anderson has really made his name in ODI cricket. Neesham, on the other hand, didn't make New Zealand's 15 man squad for the World Cup. With the ball, Anderson has been very effective in ODI cricket, but has not really performed as well in tests. Neesham has not taken a lot of test wickets, but has been quite effective at holding down an end. Anderson tends to rely on bounce and his left-arm angle, while Neesham has a good cutter, and tends to attack the batsman's body more.

There is quite a bit of debate about who is the better player, and so the prospect of them both being fit, and us seeing who Hesson opts for is tantalizing.

In the conversation on the radio, Waldegrave and Paladin both said that it was clear that Neesham had better statistics, and so he should be picked. My ears immediately pricked up.

The basic statistics do bear that out.

BattingAndersonNeesham
Innings1815
Runs533606
Average31.3543.28
100s12

BowlingAndersonNeesham
Overs174109.5
Runs500361
Wickets1311
Average38.4632.81

Neesham has the better batting and bowling average. He's scored more runs in less innings, and has taken roughly the same number of wickets in roughly half the innings.

Here's a graphical representation of their batting scores so far:

A quarter of Anderson's innings have been scores of 2 or less, which is certainly not ideal. Neesham, on the other hand, has a quarter of his at 78 or higher.

Bowling innings are not so easy to show in a graph, but I felt that it was useful to see the difference. I've graphed their average vs the number of overs bowled.


We can see the trends in the numbers - Anderson's average is increasing, while Neesham's is decreasing. When Anderson had bowled the same number of overs as Neesham has now, their averages were similar, but Anderson's averages have risen fairly steadily since then.

However, straight summary stats can be misleading. I was interested to see if Neesham truly did have better statistics to the point where we could be confident that he would perform better.

I'm finding that more and more I distrust cricket basic statistics to tell me about players. That is an odd thing for a stats blog to say, but please hear me out.

Firstly a batsman's previous innings is not actually the full list of what he was capable of doing. It is effectively a sample. Of all the times that he could have played, he only actually played a few of them. (They have both batted on about 40 days, over the space of 3 years). Treating their previous results as population data, where we can compare summary statistics directly is dangerous, because these are effectively actually a sample of what their careers will eventually be. (Assuming here that they will play more). They are also only a sample of the scores that they were capable of throughout their careers. Perhaps they would have scored more if the last series they played in had been longer, or if there was an extra tests added into the last tour that they were on.

When we compare samples, we need to use statistical techniques in order to be able to account for sampling variation. Sampling variation is basically caused by not having enough information. There are a range of techniques to do this. If we have reason to believe that our population is normally distributed, we can create confidence intervals using descriptive statistics. However, we know that cricket scores are not normally distributed. Scores tend to be skewed to the right - ie the majority of scores are below the average. (Some examples Graham Dowling scored less than his average in 68% of his innings, Graham Smith scored below his average in 73% of innings, Gordon Greenidge scored less than his average in 68% of his innings and Don Bradman scored less than his average in 64% of his innings - if scores were normally distributed, then most players would score their average in roughly half their innings).

Another technique that can be used is a technique called bootstrapping. This is where a confidence interval is created by resampling with replacement. This is almost black magic, in that it uses just the variation in the sample to describe the variation in the population, and, despite it seeming illogical at first, it actually tends to work remarkably well. (For example, the bootstrap confidence intervals for the first 25 innings for Graham Smith, Sir Don Bradman and Gordon Greenidge all include their final career average. It even worked for Sir Frank Worrell, who had an amazing start to his career followed by a poor end)

The easy interval to construct was the batting scores. Here I randomly selected their batting innings, and calculated the average of each batsman. Then I subtracted Anderson's resampled average from Neesham's resampled average. If a number came out positive, then it meant that Neesham's average was higher, if it was negative, it meant Anderson's was higher. After taking 1000 resamples, I then looked at the central 95%. If it is all positive or all negative, it implies that there is a true statistical difference.

Here's the graph of the results


The red line in this graph indicates the confidence interval. Here we can see that the interval includes both positive and negative numbers. This means that we cannot make a call based on the start of their careers as to who is statistically the best. They are too close to call.

Bowling is harder to compare. There are so many things to compare that it can be really difficult. The way that I chose to compare the bowling was to think about what the job is that they are going to be asked to do. in the media conference Mike Hesson was actually quite clear about what role he expected Neesham or Anderson to do. They were to be an additional support bowler, in the same way that they have been used throughout the recent games. I looked at all the matches since McCullum has been captain, and the median overs bowled by the 4th seamer (or 3rd seamer when 2 spinners were picked) was 11. (For this I ignored a few innings where McCullum bowled himself for an over or 2, but I included the innings where he actually bowled 2 full spells)

As a result I normalised each bowling innings by Neesham or Anderson to 11 overs. To do this I added on a percentage to the run rates for situations where a bowler had only bowled a few overs. This meant that 0/25 off 5 became 0/65 off 11 and 2/12 off 6.1 became 3/25 off 11. There are obviously issues with this, but I felt that it was fairer than any other method that I could think of.


After normalizing we can see that the runs distribution is similar, but Neesham took more wickets more often.

The bootstrap results looked like this:


Again there is not enough evidence to actually say who is statistically better.

A third way to look at it is to compare the contribution in individual matches. For this I selected batting innings and bowling innings randomly from each player. I added Neesham's batting to Anderson's bowling, then subtracted Neesham's bolwing and Anderson's batting. If the result was positive then Neesham had made the bigger impact, if it was negative, then it was Anderson.

The result of this was as follows:


Again, there is not enough evidence to make a call.

However, all this data is from some very small samples. This is why the confidence intervals are so wide. To try and make any sort of call from such a small sample is really sketchy. To be able to make a valid comparison, I needed more data. Accordingly, I decided to look at their first class records. This time they both had more than 50 innings, and so the data was a little more useful.

However, the results were similar, despite the intervals being smaller. In every case the outcome included both positive and negative numbers, meaning that we could not make a call statistically who was the better player.

What does this mean in the context of selection?

Quite simply it means that the selectors need to rely on what they notice, rather than on the statistics. Who do they think will be successful, given their experience in the game, and their intuition for knowing which players are likely to do well.

Selection is not an exact science. In this case there is not a compelling statistical argument for either Neesham or Anderson, and so it really should come down to who the selectors feel would be most effective on the pitches that they are playing on.

Statistics can tell you a lot of things. But it cannot tell you everything. It is a tool for finding patterns, rather than a crystal ball for divining the future perfectly.

Thursday, 6 March 2014

Who should win the NZ cricket awards

I was asked by Tony Veitch to put together some stats for the different awards on offer for the New Zealand Cricket Awards tonight.

I could have just brought up a list of averages, but that's really not the CricketGeek style, so I decided to delve into things a little more closely.

One of the difficult things in cricket statistics is to compare bowling success with batting success. For example, which is better taking 5/84 or scoring 172? We need a device to compare the two disciplines.

I decided to compare each player's year with the historical averages for their position. For example, for batting I compared the batting average with year end batting averages throughout history. I had a cut off of 10 innings, as making a cut off much higher than that excludes too many players, as most teams play less than 10 tests per year. I then compared a player's average to the historical average of averages, and the standard deviation of averages to generate a z-score. (For more on Z-scores, see This NFL blog post)

I used batting average and bowling average for test cricket, as really what we care about is scoring runs and taking wickets. I wasn't totally happy with the results, as there was no advantage for the players who had maintained a high standard over a number of games, rather than just one. (James Neesham, for example, averaged 171 this season, but only over one match).  I first filtered out anyone who hadn't either batted in 10 matches or who had bowled less than 100 overs. Then I multiplied the z-score by the square root of the number of innings that they had applied their skill in, in order to get a fairer list. It only caused a couple of positional changes, but the new lists looked more appropriate.

Here's the test lists.

Player - SkillAverageRanking
LRPL Taylor - batting81.6012.3
BB McCullum - batting52.735.0
TG Southee - bowling20.073.8
TA Boult - bowling22.363.6
KS Williamson - batting47.213.4
BJ Watling - batting42.272.0
N Wagner - bowling30.421.1
CJ Anderson - bowling30.541.0
CJ Anderson - batting32.70-0.3
TA Boult - batting32.25-0.4

I would give the award to Ross Taylor. He scored 816 runs at an average of 81.60. He past 50 in half of his innings. McCullum, Southee, Boult and Williamson all had great years, but Taylor's average really makes his numbers stand out.

Next I looked at the ODI lists.

Here I decided to use the batting and bowling index developed by S Rajesh from Cricinfo (and me separately). Again I compared the players index to the historical data.

Here's the list:

Player - SkillIndexRanking
CJ Anderson - batting 84.4816.1
LRPL Taylor - batting 43.776.9
MJ Guptill - batting 44.226.4
KS Williamson - batting 39.044.7
MJ McClenaghan - bowling 23.871.1
NL McCullum - batting 26.230.9
JDS Neesham - bowling 23.690.8
CJ Anderson - bowling 24.850.7
KD Mills - bowling 25.970.7
L Ronchi - batting 22.93-0.1

Again a batsman takes the title. This, however was not particularly surprising. Anderson was immense with the bat, and generally the games were played on high-scoring pitches, which don't really flatter bowling statistics.

For the T20 award I used batting index, but my own metric for bowling. In a previous post I showed how each wicket worked out to roughly 5 runs in a t20. Accordingly we can take 5 runs off a bowler's total for every wicket they have taken. They then get a modified run rate. I used this to compare the NZ players' years to the historical data. This is a little less relevant, as there is not a lot of historical data (about 1/10 the quantity of test and ODI information) and also New Zealand only played 6 matches, so the sample size is very small.

Here is the list:

Player - SkillIndex/Modified run rateRanking
L Ronchi - batting221.1114.7
BB McCullum - batting101.084.1
AF Milne - bowling2.752.9
AP Devcich - batting73.341.7
C Munro - batting60.041.5
JDS Neesham - bowling5.000.5
JD Ryder - batting44.020.0
NL McCullum - batting42.25-0.1
NL McCullum - bowling5.64-0.3
HD Rutherford - batting40.02-0.3

Luke Ronchi is a bit of a surprise here, but I remember looking up his stats and being surprised as to how effective he has been in t20s recently. During the course of the year he averaged 133 at a strike rate of 166. Those are quite ridiculous numbers.

The last major prize left is the Sir Richard Hadlee Medal, for the best overall. For me that goes to Brendon McCullum. He managed to attract the attention of the whole nation with his 300, and he also captained the side particularly well across all the formats. There would be a fair argument for Taylor and Anderson, but for me, McCullum needs to be acknowledged some how, and that award seems appropriate.

Who would you give the overall award to?

Monday, 6 January 2014

Don't steal Corey Anderson's moment

Michael Jeh is a fantastic writer. When I see that he has written an article, I often read it.

Recently he wrote an article about the New Zealand - West Indies match in Queenstown, in it he suggested that Corey Anderson's innings was more a case of bad bowling than good batting. He even suggested that the game contained "possibly an unofficial record for the most full tosses bowled (including junior cricket!)"

I hadn't had a chance to see the innings before reading the article, and so I naturally assumed that Anderson's innings had involved him hitting a number of full tosses for 6. I was quite surprised, therefore, when I watched the highlights that I didn't notice a single full toss before he got to 100.

A few days later, I had a chance to sit down and watch the game closely, and actually see if Jeh's criticism was valid. Not every ball is shown on the highlights, so I wanted to be careful to not judge his article based on the work of the Sky editors.

After watching it I noticed a few things.

There are a few reasons I can think of why a bowler will deliver a full toss. Here is a list of some possible reasons:

  • Perhaps they decided that a particular batsman has trouble with full tosses. 
  • Perhaps they want to bowl a slower ball, and they know that slower balls are much more effective if the batsmen are attacking them. As a result a wide half-volley or a full toss often pick up wickets. 
  • A good tactic for spin bowler who sees a batsman charging down the wicket is to throw in a flat full toss. The batsman often ends up just hitting the ball straight back to the bowler.
  • Perhaps they just executed a yorker/full ball badly.
  • A bowler who has been hit a number of times sometimes just wants to get through their over, and doesn't focus as much on where the ball lands.
Some of these are a result of poor skills, but some of them are actually caused in reaction to the batsmen. It is important that we identify which is which before we criticize too harshly.

Jesse Ryder has a history of getting out to full tosses. It is not a good idea to bowl one every ball to him, but it is a valid tactic to occasionally bowl one to him, especially outside off stump, where he has a tendency to mistime them and hit them at catching height to cover. This is a risky tactic, and not one you would try every delivery, but it is a valid option occasionally.

Corey Anderson, however, doesn't have a reputation as a bowler who is likely to get out to a full toss. He is possible only behind James Franklin and Colin de Grandhomme in his ruthlessness at dealing with full tosses.

The first 5 full tosses were all bowled to Ryder. The first one was in the 9th over. There was not a single full toss in the first 53 balls. The first one was mistimed for a single. In the next over the West Indians bowled another. It was also mistimed for a single. A couple of overs later Ryder received two in a row. He hit the first for 4, but failed to score off the next one.

About 3 overs later Ryder received another full toss, and again managed only a single off it.

The first full toss that Anderson received was the ball immediately following him bringing up his hundred. There was not a single full toss in the 36 balls that he took to get to 101.

Ryder got 2 more full tosses. The first he managed to score 2 off and the second one dismissed him. Ryder scored 9 runs and was dismissed off the 7 full tosses that he faced. Off the other 44 balls he scored 95 runs. Overall Ryder scored at a higher rate off the balls that bounced than off the ones that didn't.

Anderson received 4 full tosses. He hit two of them for 6 and two of them for 2.

Overall the "unofficial record for the most full tosses bowled" is apparently 11. Only 2 of those 11 were in the first half of the innings. They were a result of good batting, putting the bowlers under pressure and getting them to go searching. 

They also didn't actually contribute that significantly to the overall score. Anderson and Ryder scored 25 runs off the 11 full tosses. This equates to 2.27 per ball. Off their other 87 balls they scored 210 runs, or 2.41 per ball.

The bowling performance by the West Indies may not have been the best ever, but the real story was the extraordinary batting. To focus on the bowlers bowing too many full tosses is to steal the glory that Corey Anderson and Jesse Ryder richly deserve. It is a disappointing angle for such a high quality writer to take, and makes me wonder if it would have been taken if it had been Warner or Dilshan scoring the runs.

Wednesday, 1 January 2014

A quick look at the Anderson innings

Corey Anderson has been talked of as the big hope for New Zealand cricket for about 7 years.

He was signed to a national contract when he was still at school to make sure he didn't chose to play rugby, a sport in which he also excelled.

He was one of only a few New Zealand players to play first class cricket while still at school since the Second World War.

And yet so far in his international career he has failed to make a splash. Until today.

Today he broke Shahid Afridi's record for the fastest ODI hundred by smiting the West Indies for 131* off 47 balls. The first 101 of which came up off only 36 balls. I honestly thought Afridi's record would never be broken, but I guess you should never say never.

Here's the full 47 balls, for those of you who are interested:

1 . 4 1 . 1 6 1 . 2 1 4 6 1 6 6 . 6 . 6 1 . . 6 6 6 6 6 1 . 1 4 4 1 1 6 6 4 1 2 4 1 6 1 2 2 1

The first question that came to my mind was how does this innings compare to other great innings of the past.

I came up with a formula that I've used a number of times before to quantify how good a limited overs innings is. Basically the score is either squared if they are out or multiplied by 5 more than itself if they are not out, then divided by the balls faced. It rewards both big scores and quick scoring. It isn't perfect, as it doesn't take into account the state of the match, the quality of the opposition the importance of the game or the conditions that the match is played in. However, it is the best simple system that I know of, so it's the one that I use.

I put Anderson's innings into the formula and then compared it to all other big innings that were scored quickly. For this comparison I looked at every innings where a batsman scored more than 75 at a strike rate of more than 110.

Here are the top 20:

PlayerScorevsYearModifiedViv Points
Corey J Anderson (NZ) 131* (47)v West Indies 2014379.06144.6
SR Watson (Aus) 185* (96)v Bangladesh 2011366.15139.7
MV Boucher (SA) 147* (68)v Zimbabwe 2006328.59125.4
V Sehwag (India) 219 (149)v West Indies 2011321.89122.8
SR Tendulkar (India) 200* (147)v South Africa 2010278.91106.4
RG Sharma (India) 209 (158)v Australia 2013276.46105.5
ST Jayasuriya (SL) 134 (65)v Pakistan 1996276.25105.4
HH Gibbs (SA) 175 (111)v Australia 2006275.9105.3
IVA Richards (WI) 181 (125)v Sri Lanka 1987262.09100
Shahid Afridi (Pak) 102 (40)v Sri Lanka 1996260.199.2
Saeed Anwar (Pak) 194 (146)v India 1997257.7898.4
Shahid Afridi (Pak) 124 (60)v Bangladesh 2010256.2797.8
RT Ponting (Aus) 164 (105)v South Africa 2006256.1597.7
Yuvraj Singh (India) 138* (78)v England 200825396.5
CK Coventry (Zim) 194* (156)v Bangladesh 2009247.4794.4
L Vincent (NZ) 172 (120)v Zimbabwe 2005246.5394.1
BB McCullum (NZ) 80* (28)v Bangladesh 2007242.8692.7
Ijaz Ahmed (Pak) 139* (84)v India 1997238.2990.9
MS Dhoni (India) 183* (145)v Sri Lanka 2005237.2790.5
ST Jayasuriya (SL) 157 (104)v Netherlands 2006237.0190.4


The first name on the list is Corey Anderson's. This innings overcame Watson's demolition of Bangladesh from 2011.

I've also included "Viv Points." This is a comparison with what many people still consider the greatest innings of all time, Viv Richards vs Sri Lanka in 1987. 100 points means that it was equivalent to Viv's innings.

Incidentally at 43rd on the list was the innings that happened at the other end, Jesse Ryder's 104 off 51 balls. It was also one of the greatest innings in ODI history, but it was completely overshadowed by the outstanding innings from Anderson.

It's still early days in Corey Anderson's career. There have been plenty of players who have had a very good day in an international match (You may notice Charles Coventry and Lou Vincent's name in the above list as evidence of this) but he has now shown that the potential that the selectors saw all those years ago when he was a teenager is closer to being realised.

There are lots of things that can be said about this innings. Poor bowling, small boundaries, big bats etc, but they can't take away from the incredible pace that Anderson managed to score at. It really was a sensational innings.

Friday, 21 December 2012

Land of the long list of lefties

In a few hours New Zealand will take the field against South Africa. There are two players likely to be named in the team who's selection will be quite remarkable.

Corey Anderson is a big all rounder from Canterbury (originally) who hits a big ball and bowls left-arm medium fast. He was a prodigious talent at youth level, making the Canterbury side at age 16, while still at school.

Mitchell McClenaghan is a left-arm fast bowler who is a little erratic and injury prone, but who has a tendency to take wickets. Lots of wickets. Think of him as a New Zealand version of Mitchell Johnson. Not always on target, but capable of occasionally bowling a ball that could get through Rahul Dravid or Brian Lara.

While their selections are not in themselves particularly notable, there is one thing that is: they are both left-arm pace bowlers, adding to a very long list of NZ left-armers.

This year New Zealand has used Trent Boult, Niel Wagner, Andy McKay, James Franklin and Michael Bates at the bowling crease. There is only one other year in history when a team has selected 5 left-arm pace bowlers to play international cricket. In 2007 Sri Lanka actually picked 6 (although Zoysa didn't actually bowl in the one match he was selected for).

And New Zealand are probably against the best team to bowl left-arm pace against. South Africa's batsmen have done well against every type of bowling, but they have done less well against left-arm pace than any other type. In the last 4 years they average about 41 against right arm spin, 39 against left-arm spin or right arm pace but only 35 against left-arm pace. An average of 35 suggest that left-arm pace isn't a silver bullet, but it is a significant difference, and one that New Zealand might be aware of.

So far this year most of the South African batsmen have been dismissed at least once by a left-armer, despite many of them having only faced a couple of innings from a left-armer. Here are the stats for everyone who has faced a left-arm pace bowler at least 5 times:

NameTotal RunsTotal DismissalsAverage
Smith1221122
A Petersen66416.5
Amla162281
Kallis100425
de Villiers1421142
Levi34217
Duminy210-
du Plessis96196

The New Zealand bowlers are likely to be eagerly waiting to bowl to Petersen and Kallis. The battle between the South African batsmen and the New Zealand left-armers is certainly one aspect of the tour that I'm going to be looking forward to watching immensely.