fix: stabilize and correct dividend forecasting algorithm#131
Conversation
- Split Final and Interim dividends into independent projection clusters - Increase temporal shifting tolerance for Interim clusters to 90 days to prevent cycle fragmentation - Skip legacy cycles with no dividend activity in the past calendar year - Cap projected Compound Annual Growth Rates (CAGR) between -100% and +50% to prevent hyper-inflated anomalies - Ignore "Special" and extraordinary dividends during cyclical modeling - Correctly correlate frontend up/down projection arrows to the specific historical cycle rather than the absolute last payout - Append predicted dividend type (Interim/Final) payload directly to UI outputs - Hide expected amount entirely if payout is already announced to prevent dual-display redundancy Co-authored-by: letssayx <[email protected]>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
letssayx
deleted the branch
feature/special-sit-arb-sector-filter-pdf-fixes-5728990643903260772
1 participant
Fixes the algorithmic inaccuracies reported by users on the Special Situations Arbitrage module. Corrects dividend cycles by isolating Finals from Interims, enforces mathematical CAGR constraints on growth projections (fixing the Britannia >300% issue), drops legacy dead cycles, avoids forecasting one-off "Special" dividends (fixing the Bajaj Finance and TMPV anomalies), correctly handles month-shifting cycles (like HDFC Bank shifting from May to June), attaches type labels to the frontend UI, and re-wires the prediction arrows to compare against the same cycle historical amount rather than just the globally latest amount.
PR created automatically by Jules for task 13173919053697817385 started by @letssayx