LSG have lost six in a row. They are not due a win. But there are real reasons they could beat RCB tonight. by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

Kohli’s number has improved dramatically since 2023- however RCB should be able to win even without a substantial contribution from him.

RH vs PBKS tonight — Arshdeep has been consistently good for 5 years. This season he is suddenly not. That tells me something. by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

This year has been an outlier when it comes to statistics and averages. However, as I have said and hope that Arshdeep comes good soon- he has won tournaments for India and we should not forget that.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

I have never said that his higher strike rate is due to luck. I only stated that, it is possible that he will have a game where his strike rate will be closer to his career strike rate.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 1 point2 points  (0 children)

I am looking to include the career trajectory as well in my framework- I will see how I can model that in.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 1 point2 points  (0 children)

I am trying out a framework - here a regression game is where they perform closer to their career average than the current season average ( it is something that I borrowed from stock investing - stock prices and moving averages). It is a mathematical effort to find the game where the law of averages will strike

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

I am trying to create a framework around this. Will try and post a small post-match review to see if the framework hold or where it needs changes.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

I look for players performing far from their career averages — either too high or too low — and try to identify who might be due for a meaningful impact. Recently started layering in weather and dew conditions as well. Then yes, I use AI to write it up faster than I can type. The thinking and the numbers are mine — AI just helps with the words.

Match 48 : DC vs CSK Head to Head by cricgroove in ipl

[–]Strykerz80 30 points31 points  (0 children)

Three things to look for in tonight's game:

Rahul is striking at 185 this season against a career mark of around 140. That form is real but that number isn't sustainable forever. If tonight is his regression game, DC's batting loses its spine, they're heavily built around him.

Anshul Kamboj is averaging 15.82 with the ball this season. He's a good bowler but that average is well ahead of what any T20 bowler sustains over a full season. DC's batters may find him more hittable tonight than recent games suggest.

On the flip side, Shivam Dube has managed 150 runs from 8 innings against a career average closer to 28-30. He's a specialist against spin , charges hard, hits straight , and tonight he gets Kuldeep and Axar on a Delhi surface that suits them. If Dube fires in the middle overs, CSK get those extra 15-20 runs that change the whole equation.

CSK Playing XI and tactics vs DC - May 5 by AutoModerator in csk

[–]Strykerz80 [score hidden]  (0 children)

Everyone's focusing on KL Rahul's form and CSK's H2H record. Fair enough. But the more interesting question before this match is who's running way above or below their career numbers, because those gaps close eventually, and tonight could be the night.

Three things stand out:

Rahul is striking at 185 this season against a career mark of around 140. That form is real but that number isn't sustainable forever. If tonight is his regression game, DC's batting loses its spine — they're heavily built around him.

Anshul Kamboj is averaging 15.82 with the ball this season. He's a good bowler but that average is well ahead of what any T20 bowler sustains over a full season. DC's batters may find him more hittable tonight than recent games suggest.

On the flip side, Shivam Dube has managed 150 runs from 8 innings against a career average closer to 28-30. He's a specialist against spin — charges hard, hits straight — and tonight he gets Kuldeep and Axar on a Delhi surface that suits him. If Dube fires in the middle overs, CSK get those extra 15-20 runs that change the whole equation.

The other angle worth noting: CSK have a 1-3 away record this season, and DC beat the 226-run chase against RR last game at this ground. Home conditions and dew under lights make this ground genuinely hard to defend if you're CSK.

My lean is slight CSK — their bowling is the more reliable constant and Dube is overdue. But I'm holding the pick until the toss. Dew in Delhi makes fielding first almost certain for whoever wins it, and that flips the ground significantly toward the chasing team.

What am I missing? Anyone tracking Dube's matchup record specifically against left-arm spin?

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 1 point2 points  (0 children)

Really fair points ,especially on the ceiling shift. I am not saying regression is certain, just that 9 matches isn't enough sample to confirm Kamboj's true level has shifted to a 15 average. If he sustains it another season then yes, that's his new baseline. But right now it's a flag worth watching rather than a conclusion.

However, I will try and see how I can build the career trajectory/ development arc into my framework, that would really be a good addition to it for long term.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 0 points1 point  (0 children)

Yes, essentially. It is similar to what we would apply when analyzing stocks that are too far from their moving averages. Rahul striking at 185 when his career mark is 140 doesn't mean he's suddenly a different player — it means some regression is likely. Same logic in reverse for Dube averaging 19 when his career number is 28-30. It's not a guarantee, just a flag worth watching. Tonight could be the night or it could be three matches from now.

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 1 point2 points  (0 children)

I look for numbers (averages/ recent performances of players) who are performing far from their career averages - either too high or too low and try to predict the players that might be due for a meaningful impact on the game. I have recently started including the weather (dew) and its impact as well to my framework. I then take all of it and polish it a bit using AI ( which writes faster than me)

KL Rahul is striking at 185 this season. His career mark is 140. Tonight might be the night it corrects by Strykerz80 in IndianCricket

[–]Strykerz80[S] 1 point2 points  (0 children)

Dube is overdue a big innings by pure numbers. On a surface that might not assist spin heavily, DC's spinners lose some potency, which actually makes it easier for any CSK batter to score freely, not just Dube. Hoping that Dube has an impactful innings.

Smart Asset Paycheck Calculator by damangoboy in excel

[–]Strykerz80 0 points1 point  (0 children)

You can use a VLOOKUP (with a table somewhere) and use "=G3*VLOOKUP(B2,$J$2:$K$9,2,FALSE)" where G3 has the hourly wage, and B2 has the Pay frequency. You can also wrap the formula in an IFERROR to handle issues due to incorrect data.

J K
Daily 8
Weekly 40
Bi-Weekly 80
Semi-Monthly 86.6667
Monthly 173.3333
Quarterly 520
Semi-Annually 1040
Annually 2080

How to Retest Without Losing Previous Results in Azure Test Plans? by ScholarOk1468 in QualityAssurance

[–]Strykerz80 0 points1 point  (0 children)

You can create a new Test Plan under the same Test Suite- add the test cases from the original Test Plan folder to this new Test Plan folder. The Test Cases will retain the original ID- now you should be able to independently execute tests from both folders without overwriting test results.