Download here
It's the same as last week except that it works this time - and the scorecards now load in about 3-6 seconds, rather than 10-20 seconds. That's all I've had time for this week.
There are a few little things not quite right with the scorecards that need to be fixed. The yellow squares are supposed to indicate who was on strike each ball. But it doesn't seem to be picking up on balls where one player was on strike, but the other player got out (eg run-out). That's very minor - plus I want to think of a better way to show it than bright yellow squares anyway!
It also doesn't add additional balls to overs where extras get rebowled. The "!" symbol indicates that a ball was rebowled, but at the moment it's not adding those extra balls in to the card for you to see. Again, that's a minor thing (except in matches where Andy bowled the final over of course).
And so that inspired me to post "Most Extras Bowled" as the Stat-Of-The-Week. And in fact, it shows that it is not Andy who is king of the wides...
Tuesday, 2 March 2010
Tuesday, 23 February 2010
Version 0.0.05
(Edit: it doesn't work... I forgot to change one of my lines of code from the testing version to the for-everyone-else version... so it only works on my home computer... Get the next version instead)
As the 2009/10 season draws to a close, you can now go back and re-live every game
New in this version:
Scorecards! The complete scorecard for every game in the database can now be viewed. The only problem is that it's really REALLY SLOW... don't know why yet. But just be patient for now. It takes about 15 seconds to put together a scorecard on my computer. I'll get around to fixing it up later. It shouldn't take anywhere near that long.
Behind the scenes:
I'm finally able to mark batters and bowlers as "subs" when they are chosen to bat or bowl additional times in a game (when the team is short of players or someone is injured). Before this it was a pain in the neck having to go in and manually enter a bunch of data into the database by hand.
Coming soon:
As the 2009/10 season draws to a close, you can now go back and re-live every game
New in this version:
Scorecards! The complete scorecard for every game in the database can now be viewed. The only problem is that it's really REALLY SLOW... don't know why yet. But just be patient for now. It takes about 15 seconds to put together a scorecard on my computer. I'll get around to fixing it up later. It shouldn't take anywhere near that long.
Behind the scenes:
I'm finally able to mark batters and bowlers as "subs" when they are chosen to bat or bowl additional times in a game (when the team is short of players or someone is injured). Before this it was a pain in the neck having to go in and manually enter a bunch of data into the database by hand.
Coming soon:
- More player stats - there's so many little things in the player profiles that I'll be slowly adding whenever I can't be bothered adding large chunks of new functionality.
- Partnership stats - I've been thinking about the best way to implement this - and now the time has come to put it in. Will probably be the next addition to the program.
- Stats by season - for anyone who doesn't like how they've performed so far, a chance to start over. Once we get into the season, I'll be putting in a way to view only stats from only a certain sub-set of matches - starting with "matches from a certain season".
- Records per time-period - following on from the above idea, you should also be able to view records along the lines of "Most runs in a season", "Most wickets in a calendar year", etc.
And finally - yes, I skipped version 0.0.04, but who cares... I missed a week as well. The numbers don't mean much yet anyway.
And double finally, the scores from Monday's game are not in there. Just because I haven't got around to it with all the other things I'm trying to do. So I'm 1 game behind. But that's still 1 game more than there was last time I gave you stats!
Tuesday, 9 February 2010
Previous Highlights
I'm now expanding the blog to include a bit of a write-up of some classic moments from the indoor cricket matches of Popped Collars.
For example, last night we saw some great umpiring when Sanjit was given out LBW despite playing a shot. Sure, it wasn't much of a shot - just a wristy little leg glance - but there was definite movement of the bat in a clear attempt to make contact with the ball. I didn't actually see it, but I'm assured it was a terrible decision.
As well as an LBW, we also saw a Hit Wicket. Throw in the Interference wicket from a few weeks ago, and it leaves Mankad as the only type of dismissal now not seen in our current set of stats. Even "angry dude" from last week was unable to pull off a Mankad, despite trying twice. The first time the umpire "didn't see" if X was out of his crease or not (he was, by the way) - and the second time, Rian was sitting down in his crease at the non-strikers end to ensure that no run was taken off the final ball, to ensure Popped Collars held on to win.
Special mention also goes to Jules' catch. With the batters on third-ball, and a bit of a gumby on strike, Jules raced up from back-net-leg-side to the half-way line on the off-side (while the bowler was running in!), and the ball was popped up beautifully to him to take an absolute sitter.
However, the most talked about incident last night was the 2nd "LBW" in the match. Final ball of the game, A.Ragg on strike. He played a... well, I'm not really sure what the shot was, but he managed to hit it kind of into the groud(?) into himself(?)... yeah it was a bit unorthodox and not very effective - but somehow the umpire decided he should be given out. "Bat Before Wicket" Andy called it. Now there's a rule that'll make it tough for batsmen!
For example, last night we saw some great umpiring when Sanjit was given out LBW despite playing a shot. Sure, it wasn't much of a shot - just a wristy little leg glance - but there was definite movement of the bat in a clear attempt to make contact with the ball. I didn't actually see it, but I'm assured it was a terrible decision.
As well as an LBW, we also saw a Hit Wicket. Throw in the Interference wicket from a few weeks ago, and it leaves Mankad as the only type of dismissal now not seen in our current set of stats. Even "angry dude" from last week was unable to pull off a Mankad, despite trying twice. The first time the umpire "didn't see" if X was out of his crease or not (he was, by the way) - and the second time, Rian was sitting down in his crease at the non-strikers end to ensure that no run was taken off the final ball, to ensure Popped Collars held on to win.
Special mention also goes to Jules' catch. With the batters on third-ball, and a bit of a gumby on strike, Jules raced up from back-net-leg-side to the half-way line on the off-side (while the bowler was running in!), and the ball was popped up beautifully to him to take an absolute sitter.
However, the most talked about incident last night was the 2nd "LBW" in the match. Final ball of the game, A.Ragg on strike. He played a... well, I'm not really sure what the shot was, but he managed to hit it kind of into the groud(?) into himself(?)... yeah it was a bit unorthodox and not very effective - but somehow the umpire decided he should be given out. "Bat Before Wicket" Andy called it. Now there's a rule that'll make it tough for batsmen!
Version 0.0.03
Download here
New in this version:
More player stats are now available. You can see how players are dismissed and how they take their wickets, as well as what kinds of scoring shots people play, and have played off their bowling.
You can see, for example, that Rian is the King Of The 7s, being the only player to average more than 1 per innings. Meanwhile, Gareth holds the same title for being run-out (fortunately for him, he rarely gets out any other way).
Most importantly, Rian is no longer known as 'Brian' - I finally decided to change it.
Behind the scenes:
I've been tinkering with the database, and so it now is able to easily track when people are batting or bowling additional times in a match. This means that I'll be able to change the MVP calculator to ensure that someone who bats twice in a game doesn't get incorrectly given an MVP just because they scored twice as many runs as everyone else. Similarly for people who bowl additional overs and may end up with figures of 4 overs 3/50... or something.
Coming next:
Scorecards. This is almost ready to go - next update should have the ability to choose a match and view the full scorecard.
New in this version:
More player stats are now available. You can see how players are dismissed and how they take their wickets, as well as what kinds of scoring shots people play, and have played off their bowling.
You can see, for example, that Rian is the King Of The 7s, being the only player to average more than 1 per innings. Meanwhile, Gareth holds the same title for being run-out (fortunately for him, he rarely gets out any other way).
Most importantly, Rian is no longer known as 'Brian' - I finally decided to change it.
Behind the scenes:
I've been tinkering with the database, and so it now is able to easily track when people are batting or bowling additional times in a match. This means that I'll be able to change the MVP calculator to ensure that someone who bats twice in a game doesn't get incorrectly given an MVP just because they scored twice as many runs as everyone else. Similarly for people who bowl additional overs and may end up with figures of 4 overs 3/50... or something.
Coming next:
Scorecards. This is almost ready to go - next update should have the ability to choose a match and view the full scorecard.
Tuesday, 2 February 2010
Version 0.0.02
Two more matches worth of scores have been added to the stats. Despite Rian's best attempts to give us all the same name, the umpire gave out enough info to easily put in the stats for this week.
I was going to change his name back to Rian this week, but as punishment for that little name-antics last night, he gets to remain as Brian for another week. When you're good, I'll change it back :)
New in this version:
There's not actually any extra functionality that you'll see in this build. I haven't finished anything new to put in yet. You will notice, however, that the data file is now 1.5MB in size - rather than 8.5MB as last week. I realised that all my data I was using for testing was still sitting in there... so I got rid of it all... makes quite a difference!
There's also a now three files making up the program rather than two. The extra file is just a security file for the database... nothing very exciting.
Planned upcoming additions:
- Partnership stats
- Full scorecards
- The rest of the stats in the player profiles
GO THE STATS!
Subscribe to:
Posts (Atom)