www.cricketstatz.comAdded the Batting Order Optimiser | Cricket Statz
Some of you may remember the batting order optimiser from the old PC software. Well... it's back! It will calculate the optimal batting order of your top 7 batters, based on their success in each batting position, for any given team.
How it works
You run it from the admin panel/reports function.
Unfortunately no - we had won 17 games in a row but couldn't win the 18th to cap the season off - we didn't make enough runs batting first, we were 3/84 and then all out for 106 !!!
@Joel Norman By the way, did they win the GF?
thanks that would be more in line with my thoughts for that team based on this seasons stats.
So with just a "current season" filter on it, it comes out as:
Yes Steve has had quite the career at our club and holds most records, the only thing now is he is getting a bit long in the tooth and generally bats down low in the order which is reflective of his age and mobility!
Yes, Steve has quite the career with good scores in lots of positions:
So it is no surprise it is putting him up the order when you have no date filter applied.
You are correct with the team you slected for our club.
I think my initial issue was with Steve Lockwood batting so high, which as you mention below is around using the correct date ranges. So i'd need to check this a bit more before i report back to you.
@Joel Norman Actually, I went and had a look at your database and I assume that the team was the SSCC 3rd.
I looked at the semi final batting order https://www2.cricketstatz.com/ss/w.aspx?club=17697&mode=100&match=618790 and then compared it to the optimiser output.
I could see that there were a couple of players that had only played in that position once and had got a pretty good score, so it was putting them in that position in the optimiser. It may have looked odd to you, but I can assure you they had batted there and they had indeed got some good runs when they did.
But I also understand that a single time batting there could be a fluke so I have just introduced an internal filter to make sure they had batted in that position at least twice.
I re-ran it and got:
Now, this is pretty close to the semi final batting order:
Although it seems to suggest that Hendrik be dropped down and Steve be given a go up the order.
It is all based on numbers - so don't shoot the messenger. 😁
You made the comment about "putting blokes in batting positions that they hadn't batted in all year" - note that you can limit the date range to just pull data from the past 12 months if you like. This will fix that aspect.
Just one last thing - before you start comparing averages in the "by batting position" report on the player page with those that are listed in the batting order optimiser report - they will be a little different! The optimiser just uses a simple average score at that position, not a traditional batting average. It does this on purpose.
@Joel Norman Thanks for having a look.
Yes, if you can provide me with specifics (a copy of the output) and if you can highlight which players look very much out of place then I can look into it some more.
Mark our club had a team in the Grand Final yesterday and they have pretty much been using the same line up and a similar batting order for quite a few weeks. So when i ran the Batting optimiser report i noted it didn't really provide a very good batting order for that team in my opinion. It was putting blokes in batting positions that they hadn't batted in all year or had a poor ave in that batting position. i haven't got much time this week