2022 ICC Men's T20 World Cup - Australia

[Sherlock Holmes]

 

[Skankhunt_42]

Will be bad for South Africa if that's a washout. India won't mind I guess. But we have Ashes 2.0 in perth

 

[SMMODS]

Unveiling new logo of worldcup T20 2022

 

[Bevab]

I doubt it. It's still not a dead rubber as yet.

Netherlands will be wearing orange jerseys... KL Rahul upon seeing that shall go ballistic on them.

 

[icyman]

Not sure if you noticed the swearing contained in the tweet.

Apparently the other two mods @CerealKiller @wasteyouryouth didnt notice it either. Perhaps my eyed are deceiving me?

Lol, someone's made a strong showing here. Pretty sure we have a new nod in the making

 

[Fenil]

1) Any delivery, above waist height is deemed to be unfair, regardless of speed. It used to be that slower bowlers could get away with it up to the shoulder.
2) Batter can only be out run out on a free hit, so the ball isn't dead if it hits the stumps because he's not out. Similar happened just two days before in the WBBL.

3) I believe it hit DK, so Rizwan was allowed to take the ball in front of the stumps

Thank you so much for the detailed reply.

1) Yes, thats what I thought. Spinners used to get away with shoulder high full tosses earlier.
2) Got you!
3) Yes, it did. So I guess if its the batsman, then the keeper is free to gather the ball in front of the stumps.

Thanks again for clearing my doubts.

 

[Fenil]

Jeez just read the 25 page of analysis.
Trying to take the easy way by asking.

Why go through a 25 pager analysis when I have experts to share their opinion? Utilizing expats' knowledge to learn something new is a win-win.

 

[Khan Sahab54]

View attachment 271985

Tomorrow, Babar and Rizwan

 

[Satan666]

Why go through a 25 pager analysis when I have experts to share their opinion? Utilizing expats' knowledge to learn something new is a win-win.

Yup the web always been lacking.

 

[Umair7]

Mr Bean Derby LETS GOOOOOO @Umair7

Babar to score another duck

 

[Aislabie]

DLS takes into account the amount of wickets left, but would there be a way for it to take into account the quality of the batters left to bat?

It could be done, but the beauty of DLS is that it can theoretically be used at all levels of the game so long as you have the required information to hand.

Any attempt to create a DLS-N (Duckworth-Lewis-Stern-Nerds) system would require complex algorithms and complete statistics to adequately calculate the value of each individual batter within the broader scope of the team's resources, rather than the present system of each of the ten partnerships being allotted a set percentage of the team's batting resources. Those kinds of details would absolutely not be usable all the way down the cricketing ladder, and would not even be any fairer than the present system. There would be the chance that it would be more advantageous for a team to send in a statistically weaker batter (for the sake of argument, a Temba Bavuma rather than a David Miller) if there is imminent heavy rain, as the amount you would "gain" in unused resources would outweigh the amount you would "lose" by having a slower batter. The DLS system is better than this because there is no real way to game the system - you simply have to make sure that if you've used 30% of your resources then you have 30% of the runs.

And that's without looking at the utter mess the DLS-N hypothetical would make of games with multiple rain interruptions. Not only in being an absolute mess of numbers, but in taking so long to calculate that by the time it's sorted, the rain has started again.

DLS is also not in the hands of the umpires or match referee, but with the scorers. Although there has been a move towards computer-based scoring, which usually calculates a DLS par score automatically, this would be blown out of the water if there were to be all this added depth to it. Not only would every scorer's computer have to have access to a comprehensive statistical database, but they would also have to be able to keep this system easy enough to use that the scorers are not distracted from the match as it unfolds: in a T20 game, there is a lot going on - loads of things to record, and very little time to do it in. Cricket scorers are generally not a young or tech-savvy bunch, either. I believe that the Hampshire II scorer - the next cab off the rank when the first team scorer is no longer able to keep the role - is well into his eighties. That is the youth policy of cricket scoring.

This is a very long way of me saying "yes, but perhaps stop to ask if we should"

 

[CerealKiller]

It could be done, but the beauty of DLS is that it can theoretically be used at all levels of the game so long as you have the required information to hand.

Any attempt to create a DLS-N (Duckworth-Lewis-Stern-Nerds) system would require complex algorithms and complete statistics to adequately calculate the value of each individual batter within the broader scope of the team's resources, rather than the present system of each of the ten partnerships being allotted a set percentage of the team's batting resources. Those kinds of details would absolutely not be usable all the way down the cricketing ladder, and would not even be any fairer than the present system. There would be the chance that it would be more advantageous for a team to send in a statistically weaker batter (for the sake of argument, a Temba Bavuma rather than a David Miller) if there is imminent heavy rain, as the amount you would "gain" in unused resources would outweigh the amount you would "lose" by having a slower batter. The DLS system is better than this because there is no real way to game the system - you simply have to make sure that if you've used 30% of your resources then you have 30% of the runs.

And that's without looking at the utter mess the DLS-N hypothetical would make of games with multiple rain interruptions. Not only in being an absolute mess of numbers, but in taking so long to calculate that by the time it's sorted, the rain has started again.

DLS is also not in the hands of the umpires or match referee, but with the scorers. Although there has been a move towards computer-based scoring, which usually calculates a DLS par score automatically, this would be blown out of the water if there were to be all this added depth to it. Not only would every scorer's computer have to have access to a comprehensive statistical database, but they would also have to be able to keep this system easy enough to use that the scorers are not distracted from the match as it unfolds: in a T20 game, there is a lot going on - loads of things to record, and very little time to do it in. Cricket scorers are generally not a young or tech-savvy bunch, either. I believe that the Hampshire II scorer - the next cab off the rank when the first team scorer is no longer able to keep the role - is well into his eighties. That is the youth policy of cricket scoring.

This is a very long way of me saying "yes, but perhaps stop to ask if we should"

Makes sense. Just look at the forecast and play accordingly.

 

[Sherlock Holmes]

Makes sense. Just look at the forecast and play accordingly.

If it rains, just smash

 

[wasteyouryouth]

Rossouw is so good

 

[wasteyouryouth]

Hoping Pak Bean has been flown out to intimidate the Zimbabweans.