You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Just needed to ask for help debugging a cisd(change in state of delivery) code am working on. For the most part it is delivering the cisd upon sweep but it does miss lots of post sweep series of defending candles. Do you have any idea on how to overcome this. The core logic is detection crt ranges on either of the 2 HTFs which then project c1 levels on the current ltf and then a cisd scan starts once a block is broken. The code is somehow producing good cisd but mostly it fails to capture post sweep blocks which can be very valid. Also sometimes once a sweep is detected, and there happens to be an old broken block within c1 which took place before the sweep, it gets marked and that is not structurally correct. We only need to mark post sweep bar breaks. The candle breaking the blocks either pre sweep or post sweep should be after the sweep ltf time itself. I'd really appreciate any help in solving those. issues
CISD Detection – Structural Refactor NeededThe current CISD engine produces valid signals but suffers from structural inconsistencies around sweep anchoring, block detection, and breakout prioritization.
Main problems:
Daily and weekly and monthly cisd are not properly drawing despite the crt and Ltf projections printing on the charts.
Post-sweep defending blocks are sometimes ignored in favor of older pre-sweep blocks, causing delayed or structurally incorrect CISD signals.
Pre-sweep blocks can override post-sweep structure even when the post-sweep breakout occurs first.
Block detection occasionally splits contiguous defending clusters or anchors mid-block instead of using the true oldest candle.
Breakout logic is not fully standardized (mix of open/close/high/low checks), leading to inconsistent trigger behavior.
Goal:
Rework the CISD engine so that the sweep is the strict structural anchor, blocks are clean contiguous defending sequences, and the first valid breakout after the sweep triggers CISD — with no implicit priority conflicts and a clearly defined breakout rule.
In the photo usually if i have a cisd for htf2 it tends to skip the most obvioous and nearest block near the sweep and marks the oldest block if there is any. That is why i introduced the reuse logic from htf1 cisd calculation. So the fl