Number Posted March 31, 2012 Posted March 31, 2012 Goddy deserved to complete his double hundred on that day as further play for additional one or two overs wouldnt have made a significant difference anyways . Declaring your team mate when hes only 6 runs short of a double ton in Land of Rivals was a stupid decision and not selfless as some fans of the Wall claim , otherwise all the captains around the world would start declaring the batsmen on scores of 99* , 199* to prove their selflessnes . Wright wrote that after 150th over he told Sachin and Yuvi (during tea) that you can have 15 overs more. Then declared it after 12 overs. :cantstop: Sachin last 26-28 runs came in around 30 balls. That's more than good run-rate. It wouldn't have taken Sachin more than 2-3 overs which Dravid already gave him. Though It doesn't bother me much as in the end we won. What baffles me is his fans who think only Dravid was a saviour of Indian Cricket and only Dravid cared for India , only Dravid could do this and that.. rest are all selfish record chasers.
The Outsider Posted March 31, 2012 Posted March 31, 2012 If I get the time I'll post the chapter from Indian Summers over the next few days to help you guys decide on a 7 year old murda.
velu Posted March 31, 2012 Posted March 31, 2012 Not only sachin but most of the batsmen will be disappointed if the innings are to be declared when they are nearing 200. :mad: But IMO dravid/dada might not have declared if UV was not out. We might have lost additional 2 overs if new batsmen goes to support sachin and we never know how many balls or overs sachin might need to score additional 6 runs.:giggle::giggle: Anyway this is overblown by media out of proportion , sachin's highest is 241* , 9 run short of 250. :secret:
velu Posted March 31, 2012 Posted March 31, 2012 lets bust this myth (once again ! ) that Tendulkar was crawling his way to a 200 in Multan . Here is how his last 100 runs were scored and the teams score at that point. Figures in brackets are the no.of balls he faced. 430 - 93(203) 543 -144(290) 675 -194(348) So from those numbers we find that his last 50 runs were scored in 58 balls and this includes the supposed slow down for the "landmark" of 150. That amounts to a strike rate of 86.2% - exactly the same as his ODI S/R. So turns out that this crawling BS is a result of shouting long and hard. Our runrate vs pak in multan test. :two_thumbs_up: Full chart not available
CSK Fan Posted March 31, 2012 Posted March 31, 2012 Our runrate vs pak in multan test. :two_thumbs_up: Full chart not available So Sachin's run-rate between 80 and 100 is consistant with the rest of his innings except when it peaked between 60 and 80 and after 100. What does that prove? Even between 80 and 100, the run-rate hasnt dropped much compared to hthe over-all innings, its just low compared to his 60 to 80. BTE hoe do we know if Sachin was even on strike in those overs? He might have been taking the first run of every ball like he does Plus none of this has any relevance to what happened near 194 which was about his second 100, not first Plus source please, before I trust your graph
CSK Fan Posted March 31, 2012 Posted March 31, 2012 The article just confirms that this was a tiff between two very different kind of men.A mature man who was acting like the captain of a team wanting to make sure of a win and an immature star wanting his glory more than anything else. A mature man also avoids any kind of miscommunication within the team. a mature man also doesnt promise someone 15 overs and declare after 12. A mature man is not someone who keeps things so much within himself than no one else is aware of what his plans are and springs it on un-suspecting team-mates to take them by surprise. In the end there was no way 2-3 overs required to get those runs was going to make any difference so Dravid was proven wrong and Sachin was proven right As Wright rightly said, you either declare when the guy is on 150 or let him complete that extra 6 runs so Dravid made a mistake on both counts. Dravid as usual was caught in two minds, not able to make a forceful decision and ended up playing for the gallery as a 'mature' captain. a mature captain would never have let that situation arise in the first place
beetle Posted March 31, 2012 Posted March 31, 2012 The mature man made sure the team won the match and that is what is most important.
akshayxyz Posted March 31, 2012 Posted March 31, 2012 People fooling themselves who think that individuality can be taken away in game of cricket. Even in chase of 330' date= Kohli found time to consume 16 balls to move from 90 ton 100, was that selfish? I don't know. World over batsmen celebrate their hundred's. Have you ever seen any batsmen celebrating when team reaches 100 or 200? Why? Shouldn't they be more happy about team reaching 100 then they themselves reaching 100? What happens to theory of team's runs being more important than individual runs? When Sehwag tries to get to his century with a six, I think that is even more selfish. 194* was a clear case of miscommunication. 2 overs more or two overs less could make an impact and could not. It's all how captain is planning things. It's not that it was absolutely essential for Dravid to declare at that point. There have been test matches where teams batted in third day before declaring and there may have been cases where team declared at 2nd day tea. I am not saying that what Dravid did was wrong, but communication wasn't very clear, either delivery or reception. Waiting for a century before declaring is not something that only Indians do. Captain waving batsmen back from balcony, immediately after one of the batsmen's century, is very common scene in test cricket, across the world. lets bust this myth (once again ! ) that Tendulkar was crawling his way to a 200 in Multan . Here is how his last 100 runs were scored and the teams score at that point. Figures in brackets are the no.of balls he faced. 430 - 93(203) 543 -144(290) 675 -194(348) So from those numbers we find that his last 50 runs were scored in 58 balls and this includes the supposed slow down for the "landmark" of 150. That amounts to a strike rate of 86.2% - exactly the same as his ODI S/R. So turns out that this crawling BS is a result of shouting long and hard. Wright wrote that after 150th over he told Sachin and Yuvi (during tea) that you can have 15 overs more. Then declared it after 12 overs. :cantstop: Sachin last 26-28 runs came in around 30 balls. That's more than good run-rate. It wouldn't have taken Sachin more than 2-3 overs which Dravid already gave him. Though It doesn't bother me much as in the end we won. What baffles me is his fans who think only Dravid was a saviour of Indian Cricket and only Dravid cared for India , only Dravid could do this and that.. rest are all selfish record chasers. All these facts dont mattter. Its amusing to see that stats filter experts are adept at selective filtering through text also. Wright clearly mentioned all aspects of 194* event - but all it got noticed was that a certain selfish player 'felt let down' - when asked. And that equates to b1tching and moaning about selfish milestone. Wright could have stayed away and did not bother to talk about it ( assuming that members are supposed to be mature enough). But he was smart and experienced enough to understand/realize the mis-communication there, and hence he took the initiative to diffuse the spark, before it can grow at all- which most likely would not have happened - knowing Sachin and Dravid.
akshayxyz Posted March 31, 2012 Posted March 31, 2012 The mature man made sure the team won the match and that is what is most important. No one is taking away credit for that. But as a captain of the team, he is responsible for the issue also.
velu Posted March 31, 2012 Posted March 31, 2012 So Sachin's run-rate between 80 and 100 is consistant with the rest of his innings except when it peaked between 60 and 80 and after 100. What does that prove? Even between 80 and 100, the run-rate hasnt dropped much compared to hthe over-all innings, its just low compared to his 60 to 80. BTE hoe do we know if Sachin was even on strike in those overs? He might have been taking the first run of every ball like he does Plus none of this has any relevance to what happened near 194 which was about his second 100, not first Plus source please, before I trust your graph nah.. it clearly shows Sachin dragged the runrate down between 40-50 and then again from 80-100 ( or sachin accelerated after crossing 50 or 100 ) :winky: and for heavens sake i dont want to argue how much the runrate has dropped ( bcoz we already had enough of it in other forum , but if u wish i canthelp ).. and FYKI on the other side sehwag was there till sachin scored 130 , snf please dont go overdefensive :nervous: source of the chart is given in the chart itself :giggle::giggle: you can manually check the runrate there at http://www.espncricinfo.com/ci/engine/match/64081.html?innings=1;page=3;view=commentary
akshayxyz Posted March 31, 2012 Posted March 31, 2012 nah.. it clearly shows Sachin dragged the runrate down between 40-50 and then again from 80-100 ( or sachin accelerated after crossing 50 or 100 ) :winky: and for heavens sake i dont want to argue how much the runrate has dropped ( bcoz we already had enough of it in other forum , but if u wish i canthelp ).. and FYKI on the other side sehwag was there till sachin scored 130 , snf please dont go overdefensive :nervous: source of the chart is given in the chart itself :giggle::giggle: you can manually check the runrate there at http://www.espncricinfo.com/ci/engine/match/64081.html?innings=1;page=3;view=commentary Hi lafandar babu.. Thanks for the link, and allowing us to make a fool of your highness. from Sachin's 79 to 100... Sachin SR - 80 Sehwag SR 57 Guess who was responsible for drop in team's run rate..and what was the milestone Sehwag chasing.. 275??? :hmmm: :hysterical::hysterical::hysterical:
Number Posted March 31, 2012 Posted March 31, 2012 Hi lafandar babu.. Thanks for the link, and allowing to make a fool of yourself. from Sachin's 79 to 100... Sachin SR - 80 Sehwag SR 57 Guess who was responsible for drop in team's run rate.. :hysterical::hysterical::hysterical: :cantstop:
The Outsider Posted March 31, 2012 Posted March 31, 2012 Too bad Tendulkar did not get the opportunity to slow down near a 300 due to his incompetency to make big scores. :hysterical:
velu Posted March 31, 2012 Posted March 31, 2012 Wright wrote that after 150th over he told Sachin and Yuvi (during tea) that you can have 15 overs more. Then declared it after 12 overs. :cantstop: Sachin last 26-28 runs came in around 30 balls. That's more than good run-rate. It wouldn't have taken Sachin more than 2-3 overs which Dravid already gave him. Though It doesn't bother me much as in the end we won. What baffles me is his fans who think only Dravid was a saviour of Indian Cricket and only Dravid cared for India , only Dravid could do this and that.. rest are all selfish record chasers. let me throw my two cents in :--D Pakistan faced 16 overs on Day 2 after our declaration, and most probably dravid/wright wanted to bowl 15-20 overs in the end.. but when UV got out , if another batsmen goes out to bat it might reduce another 2 overs ( + few more for sachin to score his 200 ), so in the heat of the moment we night have declared.. incase if we had let sachin to complete his 200 , we might ended up bowling 10-12 overs.. anyway its done and dusted, will be good for discussion only in forums :hysterical:
velu Posted March 31, 2012 Posted March 31, 2012 Hi lafandar babu.. Thanks for the link, and allowing us to make a fool of your highness. from Sachin's 79 to 100... Sachin SR - 80 Sehwag SR 57 Guess who was responsible for drop in team's run rate..and what was the milestone Sehwag chasing.. 275??? :hmmm: :hysterical::hysterical::hysterical: Thanks for correcting me.. but can you check two or three posts b4 that :two_thumbs_up: Not only sachin but most of the batsmen will be disappointed if the innings are to be declared when they are nearing 200. :mad: But IMO dravid/dada might not have declared if UV was not out. We might have lost additional 2 overs if new batsmen goes to support sachin and we never know how many balls or overs sachin might need to score additional 6 runs.:giggle::giggle: Anyway this is overblown by media out of proportion , sachin's highest is 241* , 9 run short of 250. :secret:
akshayxyz Posted March 31, 2012 Posted March 31, 2012 let me throw my two cents in :--D Pakistan faced 16 overs on Day 2 after our declaration, and most probably dravid/wright wanted to bowl 15-20 overs in the end.. but when UV got out , if another batsmen goes out to bat it might reduce another 2 overs ( + few more for sachin to score his 200 ), so in the heat of the moment we night have declared.. incase if we had let sachin to complete his 200 , we might ended up bowling 10-12 overs.. anyway its done and dusted, will be good for discussion only in forums :hysterical: How? As per the laws - new batsman must be ready to receive the next ball within 3 minutes, which usually happens within a minute or two. Decisions like declarations are not done "in the heat of the moment". They are well thought out in advance.
akshayxyz Posted March 31, 2012 Posted March 31, 2012 Thanks for correcting me.. but can you check two or three posts b4 that :two_thumbs_up: For how many years have you been carrying the burden of that graph? :hmmm: Yes I saw the other post, which is what Wright also wrote - it is one thing to declare when batsman is at 170, and completely another when batsman is 5-6 runs short - especially when earlier plans were something else. btw, check the post above, sending new batsman does not lose 2 overs... 3-4 balls at max (that too when batsmen would have been defensive).
Number Posted March 31, 2012 Posted March 31, 2012 How? As per the laws - new batsman must be ready to receive the next ball within 3 minutes, which usually happens within a minute or two. Decisions like declarations are not done "in the heat of the moment". They are well thought out in advance. Might be , When Fielding team goes in to bat in, it reduces 1-2 overs from days play. Even that taken into consideration Dravid should have given 2 overs more. But in all honesty this issue never bothers me. We won, both of them sorted out their issues. What bothers me is saying only Dravid cared for team , Sachin was selfish and slowed down for personal record , when he hardly did.
velu Posted March 31, 2012 Posted March 31, 2012 How? As per the laws - new batsman must be ready to receive the next ball within 3 minutes, which usually happens within a minute or two. Decisions like declarations are not done "in the heat of the moment". They are well thought out in advance. nope.. "Timed Out" as a specific method of dismissal was added to the Laws in the 1980 code.[4] It provided two minutes for the incoming batsman to "step on to the field of play". so we will miss atleast 1 over for the new batsmen for getting in to face the ball and he also needs to rotate the strike.. what i meant was we were already at the borderline area of declaration , once uv got out we declared :bow: and about the chart , its not mine , i quite remember abt it bcoz we had few had arguments abt it..
Recommended Posts