How to Calibrate WickFlow Engines With the Stats Panel

How to Calibrate WickFlow Engines With the Stats Panel
WickFlow engines should be tuned against the market you are actually trading.
A setting that makes sense on NQ during the open can be too loose during lunch. A threshold that works on a 40-tick chart can be unreachable on a faster chart. That is why copying another trader's WickFlow settings usually creates either too many signals or no signals at all.
The Stats tab in the WickFlow toolbar window solves this by comparing your current settings against recent completed bars. It shows the market baseline, explains whether each gate is loose or strict, and gives you a simple workflow for calibrating each engine.
This is the updated version of our original guide, Fine-Tuning WickFlow PRO: Using the Stats Window to Calibrate Every Engine. That first post covered the raw stats workflow. This version focuses on the newer Calibration Lab panel, which explains the same math in plain language.
The panel does not grade trade quality. It does not tell you whether a setup is profitable. It tells you whether your thresholds are realistic for the selected market window.
Here is the full panel view. The rest of the guide breaks this into the pieces that matter.

Full WickFlow Stats calibration panel
Start with the right window
Open the WickFlow toolbar window, go to Stats, then choose the completed-bar window you want to analyze.

WickFlow Stats lookback selector
Use Last 200 as the default starting point. It is usually enough data to smooth out random bars without blending together completely different market regimes.
Use the other windows with intent:
- Last 100 when the market just changed and you want the panel to react faster.
- Last 500 or Last 1000 when you want slower, more stable calibration.
- Current Session when you only care about today's behavior.
If Tick Replay is off, or if the chart does not have enough completed order-flow data, the panel will warn you. Fix that first. Calibration is only useful when the stats are based on real completed-bar data.
Read Market Scale before touching settings
The Market scale block tells you what is normal in the selected window.

WickFlow market scale baseline
These values are baselines, not targets:
- Avg Volume tells you the typical total volume per completed bar.
- Avg Range tells you the typical bar height in ticks.
- Avg Duration tells you how fast the chart is moving.
- Avg |delta| tells you normal one-sided pressure.
- p95 |delta| marks rare delta pressure. Most bars are below this.
- Avg vol / level helps calibrate Stacked Imbalance per-level volume.
- Avg wick helps calibrate Absorption Zone Ticks.
This is the first sanity check. If average bar volume is 798 and Trapped Min Vol is 80, your trapped volume gate is only 10% of a typical bar. That can be fine, but now you know exactly what the setting means.
The same logic applies to delta. If Avg |delta| is 80 and Absorption Min Delta is 100, absorption requires 125% of normal directional pressure. That is selective, not impossible. If a delta setting is far above p95 |delta|, the engine may barely fire in the current window.
Use the health cards as the first diagnosis
After Market Scale, read Delta landscape and Volume & size gates.

WickFlow delta landscape and volume gates
These cards translate raw thresholds into useful labels:
- Loose means the gate is easy to pass. Expect more signals and more noise.
- Calibrated means the gate is proportional to the selected window.
- Selective means the engine needs a stronger-than-normal bar.
- Rare means the engine may not trigger often in this market window.
- Wider than avg wick means an absorption zone is larger than the typical rejection wick.
Do not automatically tighten every loose label. Loose can be correct if you want earlier signals. The point is to know what tradeoff you are making.
For example, if Trapped Min Range is 4 ticks and Avg Range is 40 ticks, the range gate is 10% of a typical bar. That means tiny bars can qualify. If you are seeing too many trapped signals in flat movement, raise the range gate first. If the range looks fine but the signal still fires too often, raise Trapped Min Vol.
Tune each engine from its own card
The per-engine cards explain the actual setting relationship.
Use them one at a time.
Trapped Traders
Trapped Traders uses a volume gate and a range gate.

WickFlow Tune Trapped Traders card
- Min Vol decides how much volume must accumulate at the trapped extreme.
- Min Bar Range filters out flat bars before the volume check matters.
If traps print too often on small hesitation bars, raise Min Bar Range first. If traps print on normal movement but you only want heavier trapped pockets, raise Min Vol.
Absorption
Absorption uses directional pressure plus zone size.

WickFlow Tune Absorption card
- Absorption Min Delta controls how much aggressive pressure must hit the area.
- Absorption Zone Ticks controls how far inward WickFlow scans from the wick extreme.
Compare Zone Ticks to Avg wick. If the zone is much wider than the average wick, the engine may accept tests that are no longer tight rejection pockets. If Absorption Min Delta is far above Avg |delta|, only stronger one-sided bars will qualify.
Stacked Imbalances
Stacked Imbalances are judged level by level, not by total bar volume.

WickFlow Tune Stacked Imbalances card
That is why Avg vol / level matters. If average volume per price level is 20 and Stacked Imb Min Vol is 12, each imbalance level needs about 60% of a normal level's volume. That is selective but still reachable.
Also watch the active zone count. Too many active zones usually means the retirement threshold is too loose or Min Volume is too low.
Surge
Surge has multiple paths:

WickFlow Surge calibration card
- Magnitude Surge looks for delta expansion and print-size expansion.
- Intensity Surge compares volume rate against the current speed of the market.
- Speed tag marks fast movement.
- Mag + Int shows where magnitude and intensity overlap.
Surge problems usually come from one of two places. Either the expansion multiplier is too high, so the delta or print-size leg cannot qualify, or the shared filters are too strict, so valid expansion gets blocked by minimum dominant-side volume or trades.
Use the Surge card to see which leg is blocking the signal before changing settings.
Check signal activity after calibration
Once the gates look reasonable, scroll to Signal Activity.

WickFlow signal activity density
This section counts how many signals each engine produced in the selected window. Treat it as a density check, not a quality score.
A rough reference band is 1 to 25 signals per 100 bars. That is not a rule. It is a quick way to catch obvious problems:
- None in window means the engine did not trigger at all. Check whether the related gates are rare or unreachable.
- Sparse means the engine is active, but very selective.
- In range means signal density is not obviously broken.
- Very high counts usually mean one or more gates are too loose for the current market.
Do not tune an engine only to hit a signal count. First make the gate logic match your trading idea, then use counts to check whether the result is practical.
Use raw audit numbers only when you need proof
The Raw audit numbers section is for verification.

WickFlow raw audit numbers
Most of the time, the cards above are enough. Open raw audit when you want to inspect the exact baselines behind the labels:
- Avg bar volume
- Buy / sell split
- Avg bar delta
- Avg bar |delta|
- p95 bar |delta|
- Avg volume per price level
- Avg bar range
- Avg extreme wick
- Avg dominant-side volume and trades
- Swing and Surge baselines
This is useful when a label surprises you. If the panel says a delta gate is rare, raw audit lets you verify whether recent p95 delta is actually lower than expected.
A simple calibration workflow
Use this whenever you change chart type, instrument, session, or WickFlow engine settings.
- Pick the window. Start with Last 200. Switch to Last 100 for a fresh regime or Current Session for today's behavior only.
- Read Market Scale. Note the normal bar volume, range, delta, wick size, and speed.
- Check the health cards. Look for loose, selective, rare, or wider-than-wick labels.
- Tune one engine. Change one setting at a time. Start with the gate that directly matches the problem you see.
- Apply Refresh or Reload Chart. Use the footer guidance. Green refresh settings apply faster. Orange reload settings need a chart reload to rebuild history.
- Check Signal Activity. Confirm that the engine is active enough to be useful, but not firing on every normal bar.
- Repeat only if needed. Stop when the settings match your trading idea and the signal density is usable.
Here is the practical version:
- Too many weak Trapped Trader signals? Raise Trapped Min Range, then Min Vol.
- No Absorption signals? Check whether Min Delta is above recent p95 |delta| or Zone Ticks is too narrow.
- Too many Stacked Imbalance zones? Raise per-level Min Volume or tighten zone retirement.
- Surge never fires? Check the delta leg, print-size leg, and shared dominant-side filters separately.
- Delta Flip never fires? Check Flip Min Delta against Avg |delta| and p95 |delta|.
- Delta Participation feels too rare? Compare swing requirements against the swing baselines in raw audit.
Good calibration is not about making every engine fire more. It is about making each engine fire for the kind of order-flow behavior it was built to detect.
Use the Stats panel before guessing. The market already gave you the scale. WickFlow is showing you where your settings sit on that scale.
Continue Reading
Fine-Tuning WickFlow PRO: Using the Stats Window to Calibrate Every Engine
Forget copy-pasting someone else's numbers. WickFlow PRO now ships a live stats window that tells you exactly what your chart is printing. Here is how to read it and tune every engine against your own data.
Order Flow Trading: How to Read Absorption Signals Properly
Learn how to identify and trade professional absorption signals in order flow trading. Discover the WickFlow framework for high-probability reversals.
Building a NinjaTrader 8 Indicator: What Actually Went Wrong
The real technical problems behind Key Levels PRO: SharpDX rendering, async BarsRequest threading, Volume Profile tick duplication, and C# export compatibility in NT8.