Badgers CC cap badge
Badgers Cricket Club
Affiliated to the CCC

The Statistical Sett – Scorecard Queries

Home
Clubhouse
News
Fixtures
Results
Averages
Club Officers
Hall Of Fame
 
Links
 
Cricket Teamwear, Cricket Clothing from Kalibazar, Custom Clubwear from Cricket Kit Suppliers
SafeSurf Rated All Ages

Historically (certainly between my taking over the creation of the end of season report in 1988 and the addition of scorecards to this web site back in June 2002) the information in the scorebooks was processed annually, between the completion of the season and the end of season awards presentation. This tended to mean that we had to take the scoring record as gospel unless there were obvious errors in tallying. Once the scorecards started to be displayed on the web site then things changed and the scorebook data was entered as the season progressed, often weekly, which meant that mistakes were more likely to be spotted immediately.

There were often anomalies in the scorebooks that had to be dealt with ‘by hand’, a process that would either be performed on paper or using a spreadsheet of some kind, but back in June 2012 I got fed up with that approach and started work on a scorecard checking program that took a ball-by-ball input (from the bowling analysis) and recreated the whole scorecard. In recent times (starting at some point fairly early in 2014) it has been my habit to use this program to process every match, not just those with issues, and thus to fill in all of the details that Play-Cricket caters for.

Sometimes the processing of the scorebook data goes without a hitch but often there are queries thrown up that need to be resolved, some of which require a bit of detective work amongst the various elements of the scorebook whilst others have necessitated picking the brains of those who were present. Most of those deliberations and decisions are lost in the mists of time but I have started trying to record them here, partly for our own history and partly so that I have something I can point our opposition at in order to explain why what I’ve entered into Play-Cricket differs from what they have in their book.

For the time being this is a single page, with each of the links above taking you to the area of the page with information for the season concerned, each of which have their own links to individual games from that season. Since I only created the program to check the scorecards back in the middle of 2012 there won’t be any information prior to that point (and prior to the 2016 season I had only taken the time to record a few egregious examples from the last few weeks of 2015) and obviously not all games have queries. Whether this page goes the way of the clubhouse, table keys or photo gallery and falls back into disuse, who knows, but for now I intend to document all of the queries and compromises from the 2016 season onwards as I process the scorebook data each week.

The rest of the Statistical Sett resides elsewhere, and the links below will take you back to the other top level categories:


Scorebook queries from the 2017 season

The following matches in 2017 threw up queries that needed to be resolved, either by my taking unilateral decisions or by consultation with others involved.


28th May 2017 – Old Whitgiftians

Hardest situation of all this week in that I was away and thus have only the photographs to go on. Sadly, things are not straightforward (not helped by the fact that both books were completed in pen) and I have found the following problems in the opposition scorebook for the first innings:

  1. things go awry almost from the get-go and the only way I can have the number two and three batters make the individual scores they’ve been credited with is to swap them over at the end of the fourth over of the innings, Bill’s second, so that Ayuub scores both the final four in that over and the single at the start of the next. This implies that either something very strange happened or the scorer missed a run of some description off the final ball of that over
  2. barring that, hardly minor, hiccough things proceed swimmingly through to the 31st over where the end of over total suddenly goes out of sync. The bowling analysis shows Greggy’s final over as containing a single and a bye, which the fielding extras dictate should be four byes. However, the running total only increases by four and the tally only shows the four runs not the single
  3. the next two overs contain the right number of runs and seem to tie up with the running tally but Mark’s final over makes no sense as it appears to have been written, consisting of a four, two byes (a two inside a triangle), a no ball (a circle which might contain a dot), a single, a dot, a two and a final dot. There was obviously a change of scorer for the last couple of overs, the extras box shows no no balls and no two byes whilst the running tally shows a four, a three, a two, a one and another two so I’ve decided to interpret the triangle as a wide with two extra runs and the circle as two byes – which is something of a stretch but matches the running tally, almost gets the batsmen their recorded scores and ties up with the extras totals recorded
  4. all in all the final total might be 203 or 204, but no matter because 203 was the score that was recorded on the day, and thus what we were chasing

Our book for the second innings looks almost as much of a mess, but proved to be slightly easier to interpret:

  1. I can only make sense of things if the first scorer works across then down in each box, although a second scorer takes over later in the innings who goes down then across
  2. in Mehran’s first over, the fourteenth of the innings, there is a no ball with a number one inside it. If I accept that then Rob ends up with an extra run and no balls one less so I’ve chosen to accept the totals and record it as an extra not off the bat
  3. the sixteenth over, Mehran’s second, is the one potential source of confusion, assuming we are still working across then down, since Amy starts on strike but cannot score the six. I have chosen to interpret the box exactly as written, with a single before the six off a no ball, even though it would be highly unlikely for it to have been recorded like that, so that Amy and Mark receive the correct additions to their individual scores

All of which does not detract in any way from a superb innings from Mark backed up by Bill in a record breaking ninth wicket partnership. Finally, when I came to update Play-Cricket with the derived details I found the following differences with what had been entered by Jonathan Higgins on behalf of Whitgiftians:

  1. Drury was credited with three fours, but I see four – both in the derived scores and in their book, and thus would give him an extra one
  2. Higgins himself had been given 43 runs, which is what their book adds up to, but my derived data gives him an extra boundary four (so he scored four fours between the single to get off the mark and the first double) and thus 47, which would also affect the number of fours hit which would increase from 6 to 7
  3. as mentioned above, in order to get things to make sense as recorded I would have to deprive James Schad of a run, so he would be 7 rather than 8
  4. also based on the above confusion over the total score during the closing overs, I would adjust the fall of wicket scores up by one
  5. Matt Smith was shown in the book as conceding 41 runs but that looks like a tallying error, or poor writing, and it should be 40
  6. Mark was recorded as having conceded 19 runs, but his actual total depends entirely on the interpretation of the final over he bowled. On the basis of the decisions I made in resolving that over, and the fact that I have had no response from the oppo about the situation, he ends up with 21 runs against.


    21st May 2017 – Dormansland

    I was left to score on my own this week – flattering in one respect but more difficult in others – and did so for the first time using my scorecard checker program at the same time as the paper scorebook. This presented one major difficulty, in that the screen of my HP408 tablet was really difficult to see in bright sunlight, plus several expected minor issues because I am still developing the live scoring capabilities and had some fun with not knowing the batter order of the team batting second at the start of the game.

    All of this, and the need to attempt a battery top up during tea, meant that the book was not quite as well curated as it would have been if I’d concentrated on just that record, but it did mean that I was able to upload to Play-Cricket first thing Monday morning. The only blemish that I will need to go back and correct is that first innings wides show only six whereas nine were bowled (both according to the bowling analysis and my program) and Mark’s individual wides bowled tally was missed.


    7th May 2017 – Hampton Wick

    Not really sure where on earth to start this week because the opposition scorebook for the first innings was, to put it as politely as I can, something of a mess. The following problems were identified whilst trying to get my scorecard checker to make sense of things:

    1. over number ten, Jake’s fifth, shows only two runs in the bowler box and added to the bowler’s total but three were added to the over by over total. Checking the running tally I see an extra single run between the four at the end of the previous over, which took the total to 25, and the two runs that are all that shows in the bowling analysis. I’ve no idea what to make of this because giving an extra run to either batter messes up their individual scores, and which ends they were at, and Jake swore blind when I talked to him during our innings (whilst I was trying to make sense of our bowling analysis but before I had discovered that different symbol meanings were in play) that he did not recall bowling any wides
    2. no end of over total was recorded for the nineteenth over, and for some reason, thereafter nothing other than the runs were entered
    3. the nineteenth and twentieth overs, Darrell’s second and Mark’s fourth, show just two runs between them, but the end of over total increases by three in that span to 87, a score that is impossible according to the running tally, where the 87th run is shown as the first of a four, which agrees with the game situation as the scorecard checker sees it
    4. ignoring for now the extra run in over ten, things get back into sync in over 21 with the score recorded as 100, an increase of 13, when the over features 14 runs but from that point onwards the end of over scores are all possible in the running tally until we get to the last couple of overs
    5. the thirtieth over, Rod’s first, demonstrates the folly of scoring in pen, since it started with a simple single being turned into a two by some sloppy throwing and wicket keeping (much to the annoyance of the bowler) which resulted in something of a mess in the top left hand corner of the bowling analysis box. It isn’t easy to interpret what is crammed into the rest of the box, but discussions after the game and my analysis of the running tally suggest that the scoring sequence was a two, two singles, a wide (the home team scorers used a triangle to represent wides), a four, another single and a final two
    6. incomprehensibly, over 36 has an end of over total of 222, which is less than the score at the end of the over before. By my estimate it ought to be 228 with the 230 after the following over being correct
    7. the final score is recorded in the book as 234, which is also what is ticked off in the running tally, and yet we somehow ended up chasing 232 to win. Adding up the batting runs in the scorebook results in a score between 226 and 228 (depending on whether we take four or five wides and whether Sadiq is credited with 27 or 28) so perhaps someone decided to split the difference? Darrell tells me that the first innings score of 231 was already entered into the scoreboard at the point our innings started so that might be a reasonable explanation

    All of which leaves me with the interesting job of trying to map the runs entered against the batsmen with the information derived from the bowling analyses.

    1. Sadiq is shown in the book as having started his innings with a single – although whoever added his score up seems to have missed out a run – but I see no way that that can be possible from the bowling, so we credit him with 27
    2. taking the bowling analysis as gospel leaves us with the biggest discrepancy of all, which is that the calculated scores for the two main men – Yasir and Fawad – bear no resemblance to what is recorded in the batting. The only way I can get things to line up to a greater or lesser extent is to swap the batsmen over at some point between Darrell taking the wicket, in his second over (the nineteenth of the innings), that brought Fawad to the wicket and the start of his next over. During that time the only runs scored are shown as a two in Mark’s fourth over, which is not shown against either batter. I have chosen to effect this switch at the end of the nineteenth over, and thus to give Fawad the two runs, for no better reason than that he is shown in the batting as having scored three runs before his first four and yet otherwise I only see a single in that span. This gives individual scores of 86 for Yasir and 62 for Fawad (as against the 82 and 59 respectively the scorebook shows), although it also casts some doubt on their balls faced
    3. once the pair retired I have another impossible situation to deal with, in that I am fairly certain that batters 7 and 8 came out to the wrong ends (which ties up with the book in that Haseeb faced a leg bye before Will Taylor was clean bowled from his second delivery) but the leg bye off the final ball of that same over – Matt’s first and the 36th of the innings – and the three singles thereafter, then puts the wrong batsman on strike to be dismissed by the second ball of Matt’s second over (I am absolutely certain that Zubair faced the first ball of Billy’s last over but thereafter I don't recall well enough to be sure). Again I’ve cheated to get the right batting scores as I’ve already wasted far more of my leisure time than is reasonable given that none of this matters to our statistics

    After all of that fun and games our book was slightly easier to deal with, which is to say that there was only one discrepancy (which I had spotted whilst I was scoring late in the innings) in that Mark was not credited with four runs that he should have been (I will try to blame Ricky for signalling the boundary late, after some confusion over two or four but really it has to be my fault – poor concentration).


    30th Apr 2017 – Beechwood

    Two scorers this week but one minor disagreement to resolve (no scorebook images for this one though, as they were taken in the pub in fairly poor light and simply aren’t clear enough to warrant posting):

    1. Jacqueline had recorded Ricky with 55 and Greggy with 24 but the opposition scorer had 56 and 23 respectively. Once I’d processed the scorebook it proved to be that Ron was right and my daughter had given one of Ricky’s singles to Ian.

    Scorebook queries from the 2016 season

    The following matches in 2016 threw up queries that needed to be resolved, either by my taking unilateral decisions or by consultation with others involved.


    25th Sep 2016 – Westcott

    No scorers again this week and another handful of mysteries to resolve in the scorebook for the second innings:

    1. The first element of possible confusion is that all those who scored for Westcott, and I only detect two lots of handwriting, filled the bowling analysis as three across and two down – something encouraged by the shape of the boxes in their scorebook – and it is not necessarily obvious whether or not they worked across then down or not. I cannot get a perfect match to the batting details either way but have chosen to go with down then across to start with, as that gives a closer match to the early batting entries, changing to across then down from the ninth over onwards because otherwise things go awry in terms of who scores which runs and is at which end to be dismissed (and there is an obvious change of handwriting in the eleventh over). Whilst this sounds like a trivial thing, once we have the batters at the right ends for all significant events, it can also have an effect on the balls faced.
    2. There is an anomaly in the second over of the innings in that the third ball is shown as a W in the book, but from memory the non-striker was run out by a direct hit from Amy at long off, trying to stretch a single into a two. Therefore Harman should be given that first run, which increases all of his total, Mark’s runs against, the team total and the fall of wicket. Isted is shown as having faced three balls but it can only be two (which also helps to confirm the down then across scoring method at this juncture).
    3. Bill’s seventh over, the first of his second spell and 29th of the innings, is recorded as just a maiden, with no obvious symbols underneath, but the end of over total goes up by one and Andrews, who is on strike at the start of that over, has a bye symbol in the batting just before the dot and two prior to his dismissal in the next over, Jake’s first. So, there must have been a change of ends and since I did not let through other than the four in Westy’s first over and a one in Jake’s last. and there is a leg bye shown in the Extras section of the book, I have made the final ball in the over a leg bye.
    4. Finally, Jake’s third over, the 34th of the innings has conflicting information, with seven marks in the bowling analysis box – four singles and a six plus two dots, making ten runs in all – but only nine is added to the bowler’s total underneath and to the end of over total. I tried ignoring the final single, but that did not play out right in relation to the batting, and removing the fourth symbol from the top row did not work out either. In order to get the best possible match I have had to assume that the fourth symbol from the top row was actually the seventh ball of the over!! This has the effect of increasing Hart’s score, the Westcott total and Jake’s runs against by that additional run.

    18th Sep 2016 – Cuddington Casuals

    Jacqueline having return to Uni we had no scorers this week and although I was able to score our innings I have ended up with some interesting anomalies to pick over in the scorebook for the second innings:

    1. I can find no way for Julian Radford to score a four in the first few balls of his innings and then score a long run of dot balls whilst Patel scores the figures that he has been given. Radford came in at the fall of the first wicket and must have been at the non-striker’s end whilst Mark Smith scored the four, four dots and a single that put him back on strike to be caught from the first ball of Vinny’s fifth over. The batters may well have crossed on that wicket, a running catch by Mark off a skier at deep mid off, which means that Radford may well have faced the rest of that over, which would match the first few entries in his individual record. However, for the rest of his and Patel’s entries to be correct, Radford must then have faced the maidens in Westy’s sixth and seventh overs whilst Patel scored the runs in Vinny’s sixth and seventh overs, but he is at the wrong end to do so. To stop this getting even more complicated, to have the batters at the right ends for the next fall of a wicket (which memory and the scorebook tells me was Patel not Radford) and to have them on the scores they’ve been given, I have chosen to cheat and swap the batters around at the end of the tenth over. That is quite palpably a fudge, but is the best I can do in order to match up everything else recorded.
    2. By my reckoning there must have been a wicket somewhere in Ben’s third over, the 22nd of the innings even though the end of over scores show a wicket falling in the 23rd over. There are no fall of wickets recorded from the fifth onwards, but Knight must stay in to score the three in Loll’s fifth over so Emond being dismissed in amongst the wides somewhere makes sense. Memory tells me that there were several wickets from that end that fell from the final ball of the over, so I have chosen to guess at that one, but it could have been earlier in the over (although J Sattaur’s individual entries concur).
    3. The exact point at which Mike Stockbridge was run out by a fluky ricochet off Bill’s boot is not recorded, but it must have come in the first over that Bill bowled – the 31st of the innings – and the only difference made by which ball I pick, given that Claude was on strike for the whole of the over regardless, is on the score at the fall of wicket. I have chosen the fourth ball of the over for no real reason other than that I am fairly sure that it wasn’t the first ball and thereafter it really makes no difference.

    4th Sep 2016 – Addington 1743

    One significant issue this week, albeit that it makes no difference whatsoever to the result – we still lost. However, our innings has a flaw in the bowling analysis, which means that it is illogical and could not have occurred as recorded, and a couple of possibly related issues with the individual scores for Jake and Matt. The scorebook for our innings has the 34th over (Ali’s third) as containing two singles, and the end of over totals show the score moving from 115 to 117. However, if I process the over as scored then Jake ends up on strike for the following over (Shafi’s first) and thus is not in the right place to be dismissed by the second ball since the first was a leg bye that would take him off strike. We know that Matt Smith was on strike for the two no balls in the 33rd over (Baig’s fourth and last) since he was castled by the second of them and the batting details have Jake scoring the four and two that ended that over. Therefore two singles in that following over are not sufficient to match what actually happened in the game.

    To further complicate matters, Jake appears to have been given one too many runs and Matt one too few. We (Jacqueline and I) don’t believe that the two facts are related, since the extra single given to Jake falls after the 4, 2, 4 sequence in Baig’s third over and was followed by a bye that she believes she only belatedly picked up on, and may have given Jake the one for. Matt scored a run of singles between his two fours, and whilst the book only has four of them, I see five (and no way to move that run between the two batters, since if we were to add an extra run to the 34th it would go to Matt as well as being in the wrong place to make sense of Jake’s individual runs in the book).

    The one additional piece of information I have is that I recorded the 34th over as containing three runs. Since all I keep is a running tally I have no more detail than that, but all of the evidence leads me to believe that there were actually three singles scored in the 34th over, with the extra one coming from the bat (it seems unlikely that Jacqueline would have acknowledged a signal for an extra of some sort without actually recording it somewhere in the book).

    Having said all of that I have decided not to record an extra run, because I don’t like guessing about such things, and instead have just swapped the batsmen around at the end of the 34th over, leaving Jake a final score of 33 and Matt 19. Given that switch their respective balls faced may be wrong too.


    21st Aug 2016 – Deando Ruxley

    Only one really minor nit this week, in that there was a ball that went through the wicket keeper in the penultimate over, Geoff Bowyer’s third. Matt Mann originally did not signal anything, was then prompted and incorrectly signalled leg byes (which is what Jacqueline recorded) and then belatedly changed it to byes. I have recorded it as byes. No images this week as the poor lighting in which I took the photos meant that they were very blurry.


    31st Jul 2016 – Smallfield Manor

    Another interesting exercise for yours truly as a mixture of scorers, handwriting and approaches make the scorebook for the first innings tricky to make sense of, but we will try:

    1. The first problem is that the first ten overs or so seem to have been scored by at least two scorers, interchanging regularly, making it difficult to be certain whether each box has been filled in down and then across or across and then down. After a bit of experiment I chose to stick with down and across even for those boxes (overs 2, 4, 5, 6, 9, 10 and 11) where it looks like there are three symbols across
    2. The first over contains a symbol of which I can make no sense but, given that only one run is shown against both the bowler and the end of over total, I have chosen to interpret it as a wide and two dot balls (there was a bit of grumbling at the time about leg side wides, hence I am fairly certain that there was a wide in that first over)
    3. Matt Smith’s fifth over, the ninth of the innings, looks like it contains a right pointing arrow, but the only interpretation that fits all of the other elements would be a 3
    4. Matt Smith’s sixth over, the eleventh of the innings, needs to contain six runs in order for the bowler’s total and the end of over total to make sense. However, the figure underneath has obviously been altered (possibly from nineteen) and my suspicion is that the scorer missed a wide signal and was then taken by surprise when a seventh ball was bowled and hit for four. We also recall more grumbling about a leg side wide later in Matt’s spell so I have chosen to see the content of this box as a leg bye, a wide, four dots and a four
    5. During Jake’s second over, the sixteenth of the innings, things go from irritating to aggravating since Dom Glossop needs to score the three at the start of the next over (for his individual scoring entries to come close to making sense and for him not to be on strike when the next wickets falls), and is not shown as scoring any fours between his two threes (something that already isn’t true) and yet the nine runs added to the bowling and to the end of over totals mean that different batters need to score each of the fours, whichever way the box was completed. Therefore I have to resort to cheating and just swapping the batters over so that Vikash scores both fours and the single
    6. Darrell’s first over, the 24th of the innings, quite clearly shows eight runs but the end of over total advances by only seven runs.
    7. Rob’s seventh over looks like it has a wide and a two in it, but given the batter’s scores, the extras recorded and our recollection of the game I am certain it was actually three wides (which should be indicated by extra dots around the cross)
    8. In Darrell’s second over, the 26th of the innings, the end of over total goes awry by another run, with ten quite clearly being scored in it but the total only advancing from 68 to 77. Perhaps the confusion arose around the four off a no ball (although quite how a chest high full toss from a bowler of my son’s pace is called a no ball is beyond me – law 42.6(b) quite clearly stating otherwise)

    So the end result of all that is that the home side probably scored 129 runs rather than the 127 they credited themselves with; Dom Glossop probably scored 52 rather than 51 (and thus reached his half century before his teammates clapped him for it); Chris Glossop probably scored 15 rather than 16; Vikash probably scored 20 rather than 18; there was only one no ball in the innings, not the four marked in the Extras box, and thus there were only ten total extras; Matt Smith went for 23 runs not 24; and Darrell for 35 not 33 (the latter being a simple tallying error).


    24th Jul 2016 – Ripley

    This was a bit of an oddity despite the fact that Ripley had a scorer for the whole of the game, who obviously knew his cricket. However, he did not mark byes or leg byes in the bowling analysis and did not include wides and no balls in the totals for each bowler so the scorebook for the first innings required a fair bit of interpretation:

    1. the first element of confusion comes in the running total at the end of the seventh over which is shown as 17 despite the fact that at least 10 runs were scored from Bill’s fourth over and the tally would indicate that 17 was never the score. It also looks as if the second three in that over was originally missed from the tally and added back after the end of the eighth over. The total number of runs added to the end of over scores and the entries in the tally lead me to add a leg bye from the fourth ball of Bill’s fourth over and another at some point in the first four balls of Rob’s fourth over, which are also necessary for the batters to end up with the same individual scores shown in the batting section
    2. there must also have been two extras during Bill’s fifth over, after the wicket, and thus I’ve added a bye and a leg bye between the single and the wide
    3. everything then chugs along smoothly until the end of over 27, Vinny’s last, when it looks as if the end of over total was not correctly recorded and the book is showing the score at the end of the 28th instead. This error does not get rectified and the end of over totals are an over or two out until skipping a couple to over 34.
    4. the totals shown for overs 27-29 are actually those for 28-30 and another over is then skipped with the total entered for over 30 actually being the score at the end of over 32, and that for over 31 being correct for over 33.
    5. Things then get confused because the 34th over, Mark’s second is shown as containing three twos and a single, but the tally has a four after the second of those twos and thus the end of over score is recorded as 118 rather than 114. However, the batsman (Russell) is only shown as scoring two twos at that point, with no sign of the four or the third two, although an extra two has been added to the end of his score that cannot possibly have been there from the bowling analyses. It doesn’t seem fair to resolve this by giving the batsmen four extra runs and thus damaging the bowler’s figures yet further, so I have chosen to resolve this by adding four leg byes, even though I am certain that that is wrong.
    6. The next over, Greggy’s fourth, starts with a no ball that was hit for four. This is correctly recorded and totalled in the bowling analysis and the four is credited to the batter Russell, but for some reason four no balls have been entered in the Bowling Extras box, which is quite palpably incorrect
    7. Given the end of over scores for overs 36 and 37, and the three single runs recorded in the tally between 128 and 131, there must have been an extra in each of those overs. In order for the batsmen to score the right runs I have added a leg bye from the second ball of Bill’s seventh over and a bye from the second ball of Greggy’s fifth over.
    8. Russell was run out at some point in the 38th over, Bill’s eighth, but no entry was made in the scoring record to indicate when. Bill’s recollection ties up with mine, in that he thinks he bowled one ball at the incoming batsman and thus the run out has been recorded as from the fifth ball.
    9. Over and above all of the issues mentioned above, once everything else had been sorted out we are left with Mulvi(hi)ll’s score being one less than he is shown with in the scorebook. I can see no way that he can have scored two singles between his first four and the three, so 16 runs is what he ends up with.

    17th Jul 2016 – Oxted & Limpsfield

    Just a couple of simple ones this week, both related to our scorebook for the second innings since Jacqueline was scoring on her todd. The first concerns a leg bye in the fourth over which was called back by yours truly because Rod did not attempt to hit or evade the ball before Ricky got over-excited and called for a run. Vinny had already signalled the leg bye before my attempts to be heard above the ‘dance tent’ pumping out drum and bass at maximum volume were successful and the batsmen returned to their original ends. Vinny did then signal dead ball but his attempts to communicate with Jacqueline were also drowned out and she assumed that the dead ball signal was for something that had happened afterwards. The leg bye has been expunged from the score, resulting in no leg byes for the innings, one fewer total extras, a lower team total and a reduction of one run to the score at the fall of wickets two and three.

    I have also been unable to get the events in the bowling analysis to result in the individual scores given to Ricky and Rod and have had to conclude that a single was given to Rod that was scored by Ricky and thus they scored 13 and 19 rather than the 12 and 20 in the book.


    10th Jul 2016 – Malpas

    It is very difficult to write politely about the first innings scorecards for this game, but I will do my utmost. The home side very kindly scored the first innings in our book as well as theirs – multiple different people rather than one person doing both books, best as I can tell – but neither book has a complete and useful running tally, neither book shows fall of wickets and neither book (barring a handful of overs in the middle of the innings) has end of over details recorded.

    Differences between the bowling analyses:

    1. Rob Knew’s sixth over shows five balls in our book but six in theirs, although the same number of runs so no material effect
    2. Jake’s fifth over shows seven balls in their book but five in ours, but again the same number of runs
    3. Ben Valentine’s first over shows three singles and a four in our book but only two singles and a four in theirs. I have gone with our book because otherwise the individual batter’s scores get out of sync
    4. Paul Reeve’s second over shows three singles in our book but only two in theirs and again I have gone with our book in order to keep things in sync
    5. Ben’s third over is a mess in both books, which is probably the result of runs from a wide, since I remember missing consecutive wides, but an extra run being scored from just one of them. In the end I have made a fairly liberal interpretation of the two scorebooks in order to keep the individual batsmen’s scores roughly correct but without changing Ben’s total runs against in our book
    6. Neither of Matt Mann’s overs look the same in each book and it is difficult to know what to make of those differences, especially given the need for Lewis Neil to score two of the three fours in the first over (including the one from the no ball) and not be on strike at the start of the next one, since Dave Hunt must have been in order to be dismissed in it. In the end I've juggled the sequence such that it might not match either book but gives the desired result in terms of the individual scores, which results in Matt being charged an extra run allowed in comparison with our book, but matching theirs
    7. Mark’s first over is shown as including a single in our book but as a maiden in theirs. Unlike most other instances I’ve chosen to ignore the run because if I include it then the wrong batter is on strike for the wicket. This increases Mark’s maidens to 2 but leaves his runs allowed unchanged from our book due to a tallying/interpretation error
    8. Darrell’s second over has a single and a wicket in both books, but not from the same balls, and his fourth over is missing a single from their book but has one from the fifth ball in ours, which is how I’ve interpreted it. Due to tallying/interpretation differences this leaves him with 25 runs against rather than the 27 I came up with on the day (neither book had the bowling analysis totals filled in)
    9. I remember Adrian complaining after the game that he reckoned he’d scored 13 not the 11 he’d been credited with and that must be the case, which also removes a run from Hodgkinson
    10. neither book has complete information in the Extras boxes but the result of the various guesses etc. above is that there were four wides (one off Matt Mann and two, plus a run from one of them, against Ben) and the no ball that Matt bowled

    Remarkably, and thankfully given what happened in our innings, the end result of all of that toing and froing is a total of 208, exactly matching what was posted as the score on the day, despite neither book having either a tally that showed that figure or a final total recorded


    8th Jul 2016 – Iscoyd & Fenns Bank

    One oversight in the scoring of the second innings – serves me right for trying to use CricHQ and the paper scorebook at the same time – in that I failed to give my son his first run in the batting section and therefore his score should have been 16 not 15 (there was a run missing at the time, so I knew that I had made a mistake somewhere).


    26th Jun 2016 – Horley

    Just one item of note from this one, where we had two full-time scorers who were able to help each other out. There are no scorebook photos to accompany this entry as the quality of the images I took is so bad that I have no desire to share them. Absent the home scorer swapping around the fall of the fourth and fifth wickets in their innings, in terms of which batsmen were dismissed, the only significant difference between the two books was that Jacqueline had recorded two runs off the last ball of Matt Smith’s fifth over whereas the Horley scorer had two leg byes. The most likely explanation is that Jacqueline missed a signal, since she chose not to sit in the scorebox, and thus I’ve gone with the leg byes and taken two runs from Westwood’s batting, two from Matt’s bowling and added a maiden.


    19th Jun 2016 – Tadworth

    I did not participate in this game but from what I’ve been sent it would seem that Tadworth had a scorer but we (unsurprisingly) did not and thus I only have their book to process for each innings. There turned out to be a number of discrepancies in both innings, including a couple in the second innings that mean that the scoring record was illogical.

    The opposition scorebook for the first innings was obviously the work of a single scorer who cared about their work, but (as I know all too well) it is easy to make mistakes when you are scoring on your own. Whilst running the bowling analysis through my scorecard checker I found the following minor errors:

    1. The extras in the scorebook show 10 wides and 3 no balls, but I see nine wide symbols, two of them with an extra run, and only two no ball symbols, so there is a mistake either in the extras boxes or the symbols in the bowling. I have chosen to assume that the bowling analysis is correct (not in the least because I have no way of knowing which of the wides to turn into a no ball) and the extras totals should therefore be 11 wides and 2 no balls.
    2. The scorebook shows the third wicket as falling at 34, but the end of over totals show the score as 32 at the start of the seventeenth over, Seb Sander’s first, and 37 after and the bowling analysis has three runs scored before the wicket and two after, so the wicket must have fallen at 35. The explanation might be found in the running tally which has two twos and a one marked off and perhaps therefore things were adjusted at the end of over.
    3. The sixth and seventh wickets are shown as having fallen at 124 and 125, but it looks like a mistake was made in recording the first ball of Karia’s first over, the 31st of the innings, which was corrected after the end of the over, and that correction was not copied back to the fall of wickets, which should have been 125 and 126. The first ball, from the running tally and Jake’s batting entry, was a six off a no ball but the running tally only records six not seven runs for it, with the extra being added as run 130, after the two wides, single and two that followed amongst the wickets taken.
    4. The eighth wicket is recorded as 133 but again the end of over totals and the run scoring in the over (Karia’s second) indicate that it should be 134, with the sequence of scores in the running tally suggesting that a correction was made at the end of the over and not reflected back in the fall of wicket score.

    NOTE that once I eventually reviewed the above, in conjunction with our scorebook whilst doing the end of season checking, I was able to confirm the fall of wickets details matched my expectation and to track down which delivery had been incorrectly entered as a wide and thus change the no ball and wides totals back to the three and ten that they were in both books. This also affects the number of balls faced by Vinny (since a no ball counts as a ball faced whilst a wide does not) and the number of wides and no balls delivered by Karia.

    There are also discrepancies amongst the balls faced and the not out batters and their scores at the fall of wickets, in both innings, but that is a level of nit-picking to which I’m not going to stoop (on this occasion).

    The opposition scorebook for the second innings looks to still be the work of the same scorer, but the coloured pens have been dispensed with. Sadly there are two major anomalies and a number of minor issues in this innings:

    1. The first problem occurs in the fourth over the innings, Greggy’s second, where my interpretation has an over consisting of a wide, a dot ball, two runs, three more dot balls, two runs to the batter from a no ball and a four. However, if we look at the batting we see the wide, dot ball and two against Karia, with some or all of the subsequent dot balls but Baldwin is shown as scoring the subsequent two and four. The end of over scores and the running tally all tie up with the number of runs and the sequence in which they are scored, so something must have happened to cause the batsmen to switch ends (and one dot ball has been lost from the batting somewhere along the way). Absent any reasonable explanation (a short run, for example) I have chosen to swap the batters around after the fifth legal delivery of the over, thus attributing all of the dot balls in the over to Karia. This is almost certainly wrong, but is the best I can do.
    2. The second problem crops up in Bill’s first over, the eighteenth of the innings, which the bowling analysis shows as a two, one, one, dot, two and dot. The batting details for Seb Sander and Matthew Perrins, the batters at the time, make it apparent that Sander must have been on strike at the start of the over, since he scored the two and three at the end of Greggy’s last over and the four and one in Paul Reeve’s second over. However, he also needs to be on strike for the first ball of the next over, Paul’s third, in order to be dismissed from it. The only way I can make that happen, and have the individual batting entries make sense, is to swap the batsmen around immediately after Perrin scores the second single (as if there’d been a short run), so that is what I have had to do.
    3. The scorebook shows the fourth wicket as falling at 23, but the end of over totals make it apparent that the scorer missed a run in the ninth over and adjusted the score after the tenth over to correct it, obviously without correcting the fall of wicket which should have been at 24.
    4. Charlie Young has been given a total of two in the book, but the individual analysis quite clearly shows three runs for him and that ties up with the bowling.
    5. The wides total has obviously been changed after the fact, with the final wide being altered to a two bringing the total to four. However, I can find no evidence to support this since if I change either of the wides in Greggy’s sixth over to a two then the batters end up at the wrong ends (and the running tally only shows single wides). Wides have therefore been changed back to three.
    6. Possibly related to the previous point, Greggy’s running total for the sixth over has been changed to add ten but the end of over totals only show nine runs in the twelfth over (and the running tally corroborates the ball by ball scores) and his runs against have thus been reduced to 40.
    7. The totals do not credit Jake with the maiden that he quite clearly bowled.

    For the record all of the above changes have been made to the result details entered into Play-Cricket, along with recording the calculated balls faced and not out batsmen and their scores at the fall of wickets.


    8th May 2016 – Ham & Petersham

    Just one minor error this week – I scored on my todd and everyone was getting terribly excited towards the close with the usual demands on the scorer for status updates, so I guess that is not too bad – with Bill being shown as having scored 17 when in fact he scored 19 because he was only given credit for a four off the final ball of the 24th over when the signal was changed to a six, which I had corrected in the bowling and running tally but missed in the batting.


    1st May 2016 – Beddingtom

    Players did all of the scoring this week so no surprises that there were a few problems. With regard to their scorebook for the first innings I am fairly sure that a) their total should have been 225 rather than 221 and b) something else is missing from their innings as it could not have taken place as recorded (at one point Down and White end up at the wrong ends to score the runs recorded against them). In the end I got things to line up reasonably well by simply swapping the batsmen over after the runs have been scored in the 19th over, Vinny’s fourth.

    As far as our second innings scorebook was concerned there were a handful of problems most of which stemmed from one unusual incident, which is where I will start:

    1. At the end of the 32nd over Cooper-Stewart went to continue his second spell by starting to bowl what would have been his ninth over. Despite my shouting out (since Jake, who was scoring, wasn’t quick enough to do so) before he had delivered the ball those on the field decided that the delivery should count and that the over should be completed by another bowler. Mark scored a single off the original ball, although only only a maiden for Horkan was recorded in the scorebook. I have since changed this so that Cooper-Stewart is shown as bowling 8.1 overs and conceding 34 runs, whilst Horkan only delivers 7.5 overs.
    2. This has a knock-on effect on the fall of wickets for the eighth wicket, which is increased by the extra run to 143 and the ninth (which is shown as 145, despite the end of over score for the previous over being 146) which should be 147.
    3. Mark should get credit for that extra single, and another has also been missed from his individual score and thus he made 54 rather than 52.
    4. The correct extras are recorded in the batting and bowling but are missing from the Extras boxes in the scorebook, with the no ball in the last over not recorded, the leg bye in the penultimate over missing and the two byes in the final over not written in either. The end result is one no ball, six leg byes and eleven byes.
    5. In addition to the run missed because of the ninth over shenanigans another has been lost from the last over of the innings, which the book shows as two byes, two runs scored from a no ball, two singles and a four, for eleven total runs but the penalty for the no ball was missed from the tally and only ten were added to the end of over total.

    The end result of all that is that we scored 159 for 9 from our 40 overs and still lost by more than 60 runs!!


    24th Apr 2016 – Beechwood

    Two scorers this week but still a handful of minor errors to correct (no scorebook images for this one though, as they were taken in the pub in fairly poor light and simply aren’t clear enough to warrant posting):

    1. Our book had Matt Smith conceding 27 runs, as did the Beechwood one. However, Jacqueline had recorded the first ball of Matt’s fourth over as a leg bye whilst their scorer had it as runs. As ever I am inclined to believe that one scorer missed a signal rather than the other imagined one, so those two runs should not have gone against Matt and thus his runs allowed are reduced to 25.
    2. Our book shows 10 runs allowed by Mark but their book has 12 and Jacqueline has made a simple tallying error so 12 is what it should be.
    3. Our book had Morris as bowling 7.4 overs and the innings total as 38.4 but both of those are light by one and correctly recorded in the Beechwood book.
    4. Jacqueline recorded our sixth wicket as falling at 100 but their book has 104 and the latter is correct given that Steve Cooksley’s fourth over, the 30th of our innings, shows a four before the wicket and the end of over total for the previous over was 100.

    Scorebook queries from the 2015 season

    Whilst we occasionally have the luxury of a scorer from one side or the other (and even more rarely, both) it is more common for the scoring of Badgers’ matches to fall to those playing in the games. Inevitably that means that the state of the scoring record often leaves something to be desired and the more hands that are co-opted into the job the greater is likely to be the mess…


    27th Sep 2015 – Westcott

    My heart sank when I saw the opposition scorebook for this game – it looked a mess and the batting, bowling and running total were all different. However, when I came to process the bowling analysis it turned out to be simple enough to interpret but we were left with one anomaly that I could find no way of catering for without the need for adjustments…

    Over 16 was bowled by Bill Jenkins and was his second. The book shows a wicket from the fourth ball and four byes from the fifth, which is no problem at all. It also shows a dot for the sixth ball, but that does not gel with Tom Hopkins’ individual score, nor with the need for him to be at the other end in order to hit the six and the single in the next over, Amy Gordon’s fourth, which gets him back on strike to be bowled by a jaffa in Bill’s next over. However, the end of over scores and the running total tick off does not show a single after the four, so I’ve either got to take one off Tom’s score and ‘cheat’ him down the other end or I’ve got to go against everything other than his individual score (and which end the batsmen were at) and add a single to that sixth ball. Of course, that has the disadvantage of increasing Westcott’s team total by one, but this wouldn’t be the first time that the batting and bowling scores don’t up to the designated total score.


    6th Sep 2015 – Addington 1743

    This may be one of the worst ever scorebook pairs, and the opposition scorebook contained a number of anomalies:

    1. no indication of where byes and leg byes were scored, so I’ve had to make a guess at when they happened
    2. all three no balls have been written in as a circle with a dot in the middle, which should indicate that the batsman took an extra run from each of those no balls, but I don’t remember that being the case so I’ve assumed that they were all just no balls
    3. the fourth over contains only ten runs but twelve were added to the running tally for both the team score and the bowler – this obviously affects both the bowler’s final analysis and Amjad’s total score
    4. the run out off the first ball of the ninth over is just shown as a W in the book, but to my recollection Amjad sliced the ball down to third man and was run out trying to stretch it into a two, and thus should have been given the first run – this affects his score, the total score, and the bowler’s analysis
    5. the 13th over, Rob Knew’s seventh, shows two runs against the bowler but only a wide is recorded. I have presumed that there was a bye after the wicket, because otherwise the batters are at the wrong ends for what happens next, and that only one run should have been recorded against the bowler
    6. finally, I see no way that Asif Ali can have scored a single and a four. He came in in the sixth over and the only single between then and his dismissal at the end of the eighth over is immediately before the only four, and thus he cannot have scored both. I would give the single to Amjad and reduce Ali’s score to four
    Clubhouse:  [Notice Board] [Photo Gallery] [Statistical Sett]

    Copyright 2000-2017 Steve Pitts/Badgers Cricket Club – All rights reserved
    Last updated 16 Jun 2017
    Last built 16 Jun 2017 from base file 'statistical_sett_scorecard_queries' and 'badgers_menu' template