0% found this document useful (0 votes)
15 views3 pages

Understanding Duckworth-Lewis Method

The Duckworth/Lewis system was created to provide a fair target in limited over cricket matches affected by rain by taking into account the number of overs remaining and wickets lost. It calculates the 'resources' remaining for each team based on these factors and uses that to adjust targets if a team batting second has fewer overs than the side batting first. The system provides modified targets that account for the changing circumstances of interrupted limited overs matches.

Uploaded by

dip_mon77
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views3 pages

Understanding Duckworth-Lewis Method

The Duckworth/Lewis system was created to provide a fair target in limited over cricket matches affected by rain by taking into account the number of overs remaining and wickets lost. It calculates the 'resources' remaining for each team based on these factors and uses that to adjust targets if a team batting second has fewer overs than the side batting first. The system provides modified targets that account for the changing circumstances of interrupted limited overs matches.

Uploaded by

dip_mon77
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Duckworth/Lewis made Easy? [Link]

htm

The Duckworth/Lewis system was invented by two statisticians, Frank Duckworth and Tony Lewis in an
attempt to solve the perennial problem of creating a fair target for the side batting second in a limited-overs
match shortened by the weather.

At its simplest, the problem is this. If the side batting first in a 50-over match makes 250 runs, the target for
the side batting second is 250 to tie, 251 to win. Their average run-rate must therefore exceed 5 per over if
they are to win in a full 50 overs. But if rain or bad light stops further play after only 20 overs, during which
the second side score 101 runs, then comparing average run-rates would make the second side the winner.
But if they had lost nine wickets in gaining those 101 runs, then few would give much for their chances in an
uninterrupted 50 overs. So the old average-run rate system gave an unfair advantage to the side batting
second if the number of overs was reduced. They could blaze away without worrying too much about losing
wickets. Other variants were tried, such as basing the target on the best overs of the side batting first, but this
was unfair to the side batting second.

Enter Messrs Duckworth and Lewis, who studied the performances in a great number of limited overs
matches, and concluded that the factor to take into account was what they called the "resources" available to
each side. The resources depend on the number of wickets lost and the number of balls remaining to be
bowled.

So at the start of a 50-over innings, the batting side have 100% of their resources available. With 40 overs
remaining, the resources would be 90.3% if no wickets had been lost, down to 7.6% if 9 wickets had fallen, as
shown in the table below. The full Duckworth/Lewis tables go down to the resources available after each
individual ball has been bowled, but for purposes of explanation we will stick to units of 10 complete overs
here.

With 30 overs remaining, the table gives 77.1% of resources remaining if no wickets have been lost (in other
words, on average the team would be expected to make 77.1% of their total score in the remaing overs),
down to 7.6% again if nine wickets have fallen. So our team chasing 250, having scored 101 after 20 overs
when rain stops play would lose 77.1% of their potential resources to rain if no wickets had fallen, leaving
them with 100% - 77.1% = 22.9% resources [Link] they should be expected to have scored 22.9% of the
first innings score, and their target to tie the match would be 22.9% of 250, which is 57.25 rounded down to
57 to tie, and hence 58 to win. So 101 for no wicket after 20 overs would be a winning score. But if they had
lost 4 wickets then their resources lost would be 54.9%, and their resources used would be 45.1%. So the
target to tie the match would be 45.1% of 250 = 112.75, rounded down to 112. So 101 for four wickets or
more down would be a losing score.

If only things, and the weather were that simple. Either innings could be interrupted, possibly several times, or
cut [Link] the Duckworth/Lewis system can cope with anything the weather can throw at a game.

If the game starts late and is reduced in overs, or if it was only scheduled to be of less than 50 overs in the
first place, then each side has their resources available reduced by the appropriate amount. So a 40-over
match starts with each side being reduced to 90.3% resources, so having lost 9.7%. If there is an interruption
with 30 overs remaining, as a result of which the match is reduced by ten overs, then if four wickets had been
lost, the resources available would drop from 54.9% to 46.1%, a loss of 8.8%. All the losses in an innings are
totalled and then subtracted from 100% to find the resources available for that innings.

If the resources are the same for both sides, then no calculations are necessary, and the side with the highest
score wins.

1 of 3 21-04-2010 02:48 AM
Duckworth/Lewis made Easy? [Link]

If the side batting first had more resources (R1) available than the side batting second (R2), the the target to
tie the match is calculated as the first innings score multiplied by (R1/R2) rounded down.

If the side batting first had less resources (R1) available than the side batting second (R2) then the target is
the first innings score plus the difference between the resources divided by 100 and multiplied by the typical
score in a 50 over match (normally 235, but could be different - it was 190 in the 1997 ICC Trophy). So if the
first side scored 150, and had resources available of 60%, and the second team had resources available of
70% when the innings finished, then the target to tie would be 150 plus (10/100)*235 = 173.5, rounded down
to 173.

So the apparently unfair position can arise where if the first innings is truncated by rain after 40 overs with six
wickets lost, then resources lost would be 24.6, resources available would be 75.4. The second side might
start with 40 overs to play, no wickets lost, and so have 90.3% resources remaining, more than 75.4% so their
target to tie would be 235*14.9/100 rounded down = 35 more than the first innings total, even though both
sides would have to face 40 overs. The discrepancy would be because the first side would have been pacing
themselves for 50 overs, and the second would have known from the beginning of their innings that they
would only have to face 40 overs.

One final detail is that if the side bowling first take more than their allotted time to bowl their quota of overs,
then they may be penalised by having overs deducted when their turn to bat arrives. The Duckworth/Lewis
system compensates for this this by treating it as a reduction in the resources available for the first side as if
they had been deprived of that many overs.

To avoid the spectacle of the batsmen meeting in mid-wicket and consulting Duckworth/Lewis tables and
pocket calculators between every over, the scorers generally do the calculations at the end of each over and
display the difference between the runs achieved and the score needed to tie if the match were to be finished
at the end of the over as a plus or minus figure on the scoreboard (or sometimes just the target), so all can see
whether they are ahead of or behind the target.

From October 2003, there have actually been two alternative tables, with the "Standard Edition" being
replaced by the "Professional Edition" in the professional game to account for different scoring patterns that
have been observed.

The whole procedure is explained in the pamphlet "Your Comprehensive Guide to the Duckworth/Lewis
method" published by the University of the West of England BS16 1QY ISBN 1-86043-189-5
[Link]
and a PC computer program called CODA is available from
ASQM Consultancy Unit (D/L)
Faculty of Computer Studies & Mathematics
University of the West of England
Frenchay
Bristol
BS16 1QY
United Kingdom
Price £29.95 (plus £1.50 P&P or £2.50 overseas)

Wickets
lost
Overs
0 1 2 3 4 5 6 7 8 9
left
50 100.0 92.4 83.8 73.8 62.4 49.5 37.6 26.5 16.4 7.6

2 of 3 21-04-2010 02:48 AM
Duckworth/Lewis made Easy? [Link]

40 90.3 84.5 77.6 69.4 59.8 48.3 37.3 26.4 16.4 7.6
30 77.1 73.1 68.2 62.3 54.9 45.7 36.2 26.2 16.4 7.6
20 58.9 56.7 54.0 50.6 46.1 40.0 33.2 25.2 16.3 7.6
10 34.1 33.4 32.5 31.4 29.8 27.5 24.6 20.6 14.9 7.5
0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Overs
0 1 2 3 4 5 6 7 8 9
left
Wickets
lost

{Grounds Index] [Back to John's Homepage]

3 of 3 21-04-2010 02:48 AM

Common questions

Powered by AI

Yes, the Duckworth/Lewis system can potentially disadvantage the side batting second if the first innings is reduced. If the first innings is truncated due to interruptions but the second innings is not adjusted similarly, the second side may face a disproportionate target. This is because the first team might have had fewer resources due to a shortened number of overs, but if the second team starts their innings knowing it will be a fixed, albeit shorter, number of overs, they can pace their innings more aggressively. The system attempts to correct for this by adjusting targets based on the revised resources left for both innings, but balance adjustments can sometimes still appear skewed due to the inherent pacing differences for known versus unknown overs reductions .

Scorers play a crucial role in applying the Duckworth/Lewis system during a match by calculating the necessary adjustments after every over and updating the teams and audience about the current game situation. They use tables or software to determine resources lost and calculate target scores, ensuring the updated required run rate or target score is clearly displayed on scoreboards. This helps teams strategize their innings to either maintain or chase the target effectively. Their prompt calculations and communications ensure that everyone is aware of the real-time changes in required runs due to any interruptions or changes in match conditions .

The Duckworth/Lewis system ensures fairness by calculating the target score for the side batting second based on the concept of 'resources' available. These resources take into account the number of wickets lost and the number of balls remaining to be bowled. This system addresses the unfair advantage that traditional methods could give to the side batting second by simply comparing average run rates. By using detailed tables and calculations of resources lost, Duckworth/Lewis provide a structured way to adjust targets in line with the match conditions as they change due to interruptions, ensuring both teams have an equitable chance regardless of disruptions .

In the Duckworth/Lewis method, resources are calculated based on the number of wickets lost and the overs remaining. At the commencement of a 50-over innings, a team has 100% of their resources. As overs are completed and wickets are lost, these resources decrease according to standardized tables. The impact on the target score is significant because it adjusts the target based on the percentage of resources available when the innings is curtailed due to weather or other interruptions. This ensures that the batting team does not unfairly benefit from knowing a reduced target because their target is adjusted to reflect the circumstances under which the second innings started or was interrupted .

The Duckworth/Lewis system relies on the mathematical principle of resource percentage to set targets reflecting the changes in match conditions. This principle involves calculating the available resources based on the overs remaining and wickets lost, which represent the potential scoring capability of a batting team. The calculations use empirical data from past games to create tables that indicate the expected percentage of total score a team can achieve given specific game conditions. This mathematical framework ensures that target scores reflect the scoring potential under constraints imposed by disruptions .

The Duckworth/Lewis Professional Edition tables were introduced to account for varying scoring patterns observed in professional cricket games. As professional players tend to score more aggressively and consistently under different conditions compared to amateur or semi-professional levels, the Standard Edition tables were replaced to better reflect the outcomes in professional contexts. These modifications ensure that the resources calculated and the resulting targets are more aligned with the performance characteristics observed at higher levels of the game, thus providing more accurate match scenarios in professional settings .

Differences in percentage resource loss can significantly affect the final target in the event of a reduced number of overs. The system uses these differences to determine how much of a match's scoring potential has been lost due to reduced playing time. If the percentage resource loss is greater for the team batting first, the side batting second might have a reduced target if the resource allocation is more favorable, and vice versa. This influences whether the match is closely contested or skewed towards one team. Calculating precise targets based on percentage impacts ensures that both teams have equal chances adapted to the games' actual circumstances after disruptions .

The Duckworth/Lewis target might appear unfair when both teams face a reduced number of overs because it accounts for the pace anticipated by each team within their understanding of the match duration. The first team might have paced their innings for a full 50 overs but had to stop due to rain, resulting in a lower score than if they had known it would be a shorter game. Conversely, the second team knows their innings will be shortened and can plan accordingly, which may give them an advantage in runs scored per over. The Duckworth/Lewis system tries to address this by adding extra runs to the first team's total based on the difference in resources, but it can sometimes lead to a counter-intuitive higher target for the second team even if the overs faced are equal .

The Duckworth/Lewis system manages multiple interruptions effectively by continuously recalculating the resources available to each team after each interruption based on the overs left and wickets in hand. After each interruption, the current resources are calculated by subtracting the resources lost from 100%. If a match is interrupted multiple times, each interruption's impact on resources is cumulative. By recalculating the resources after every interruption, the system ensures that the target is always aligned with the current game situation, accounting for all stoppages and changes in match conditions up until resumption or conclusion of the innings .

The Duckworth/Lewis system requires an adjustment for time penalties when the side bowling first takes longer than their allotted time to complete its quota of overs. This penalty is incorporated by reducing the number of overs the penalized team can bat when their turn comes. This reduction is treated as a reduction in the resources available to the batting side, thus adjusting the Duckworth/Lewis calculations accordingly. This approach maintains fairness by penalizing teams for slow over rates with a direct impact on their potential innings performance .

You might also like