Some colleagues and I at QUT are currently working on a couple of related projects simultaneously. One of these is part of our new Bachelor of Education development, which (assuming various approvals go through) will be live next year. There we are looking to refresh the way we and our pre-service teachers look at curriculum, pedagogy and assessment for mathematics as well as the study of the mathematical ideas themselves. The other project is related to continuing professional learning in mathematics and teaching mathematics, directed at teachers already in the field.
As part of both of these pieces of work, I'm looking to make our mathematics classrooms more active and engaging, and to incorporate more inquiry and outdoors activity into the learning. At the moment I've got my head in the junior secondary probability and statistics world, and I'm toying around with some simple activities that will get my students coming up with questions, and then collecting, analysing and visualising their own data.
A few days ago I asked my son if he would help me to try out some ideas and surprisingly he was keen! I suggested that we could do some sporty things such as throwing balls at targets and timing runs of various distances. He improved on my suggestion by turning the ball throwing into a real question for inquiry. More or less, he suggested we look at whether or not there are differences in accuracy when you throw with your left and right hand, and with or without pointing the other arm at the target. The target was another ball some 5 or so metres away, so our activity boiled down to something similar to the situation involved in lawn bowls. That is, he threw a ball, then another, then another, each time trying to get it to stop close to the target ball. After three throws (we had three balls), we would measure and record the distance from the centre of his thrown ball to the centre of the target ball. The screen cap of a tweet I made, shown below, includes a couple of photos of my son throwing (here with his non-dominant hand) and then measuring one of his throws.
Anyway, moving on, we started to do the remaining trials. But before we did, for some reason I copied the autocalculated average across to where it would be needed for right arm with pointing, and the left arm throws. As he started to do his right arm pointing throws, and record his data on my laptop, of course the average down the bottom of the column was changing with each additional data entry. Then a cool thing happened. He did one particularly bad throw, a distance well above what was currently his average, and made a really great observation which I quoted in the tweet below.
That in itself was great - my 9 year old makes an interesting and fairly insightful observation as a result of our activity. Awesome. But then the tweet that followed led to some more interesting conversations online with my friend Rob.
Rob and I are both cricket lovers, so this conversation took a turn towards cricket and cricket averages, and the story of the great mid-20th century cricketer Sir Donald Bradman. For the non-cricket people, "the Don" is probably the greatest cricketer of all time and his stats have even been analysed in various ways that put him as a sportsperson well beyond the likes of Jordan and Gretsky when compared with their respective sporting peers. Anyway, one of the great Bradman stories is that when he batted in his last innings, he needed to score only 4 runs to finish his career with a batting average of 100. Unfortunately, he was dismissed for 0 and his average for ever after has been 99.94. This was the topic of Rob and my discussion (see tweet grab). Also, check out the box for the slightly odd calculation for cricket batting averages.
Aside: The oddity of cricket batting averages In cricket, a player's batting average is calculated according to the formula
where a dismissal means the batter was out. So for example, if I batted 3 times, and scored 50 before getting out, then 20 before getting out and then 30 but did not get out, my average would be 50=(50+20+30)/2. Note that we divide by two because I only got dismissed twice even though I batted three times.
|
I had never thought of this, but had kind of always assumed that Bradman was increasing his average to 100 in that last innings. Rob's question made me think about this and of course, realise that this wasn't the case. Before that final innings Bradman already had an average over 100. The 0 or "duck" in his final stint at the crease dropped him down (similar to my son's observation), and enough so that his average fell below 100.
This got me mucking around of course - I went and downloaded the data for each of Bradman's 70 innings and played a little. One of the plots I put together was that below, showing his average varying over time. At one point he had an average of over 112 runs per dismissal. Phenomenal. And interesting statistics fodder!

No comments:
Post a Comment