Release the Source Code for Duckworth and Lewis Already

So here’s the Cricinfo commentary while the Australia-India match was being washed out by rain:

18.30 Tony Lewis, of Duckworth and Lewis, has emailed giving us the correct permutation. A newer version of the software was implemented for this tournament, which Tony has. Per the new WinCODA2 software being used by Tony and the scorers in South Africa, India’s target will be 266 in 42 overs, and 166 for 20 overs. Thanks for that Tony. Appreciated. And no, this system apparently does not take into consideration Powerplays.

It is amazing (incredible, astonishing, STUPID) that the rules for determining the outcome of a match are hidden inside proprietary software that even the No. 1 cricket website in the world doesn’t possess. It is even worse that no one, outside the makers of that proprietary software, can explain what those rules are.

So release the application source code already. Maybe Duckworth and Lewis can sign a contract with the ICC for being the sole vendors for the software, and they can license the technology to resellers who can service the local tournaments. That way, they don’t lose out when open-sourcing the software.

By releasing the code, every cricket enthusiast can look at the rules and suggest improvements that can be rolled back into the main product. Not to mention bugs that can be fixed.

A Simple Solution for Stupid Duckworth-Lewis Mistakes

There are mistakes and then there are MISTAKES. If you throw away your wicket while batting, that is a mistake because you can always argue that if the shot went right, you would be praised instead of being criticized. Same can be said for bowling mistakes. You take risks, which, by definition, have downsides. But there are other mistakes that leave you with, “What in the world is wrong with you? Are you illiterate? Can you not read a piece of paper that simply has a list of numbers on it?

John Dyson committed a MISTAKE. Even as the West Indies have won their first series against a major Test nation after a long time, Dyson, at least for the short-term, will be remembered for this amazing piece of incompetence. The only thing that may perhaps comfort him is that he is not alone. The South Africans famously messed up their 2003 World Cup campaign by hitting a drawing score instead a winning one, and then crashing out. Dyson went one better, by choosing a losing score, though the ramifications are not as severe as exiting a World Cup. This mistake is now immortalized in his Wikipedia entry.

Which leads me to my conclusion: The Duckworth-Lewis calculations may be lucid to statisticians and those inclined towards math and numbers, but apparently they are heavy going for sports persons and coaches. One option may be to make the charts much easier. But another option is to provide the details right there on the giant scorecard in the stadium itself. Here is the simplest form:

WI behind by 1 run

This information would be updated at all times by a certified Duckworth-Lewis computer program after every ball. In addition, every player on and off the field would have a pager-like device that would provide this information and also allow captains and coaches to explore scenarios such as what happens if one or more wickets are lost. All the information would be streamed from a single source so that there can be no point of confusion.