After the primary breakout signal system had been running for several months, a pattern I kept noticing in the post-session reviews was pushing me toward adding something new. Stocks that generated a confirmed signal would sometimes pull back after the initial breakout, trade sideways for a while, and then make another strong move. The primary signal had already fired. The system had done its job. But from a practical trading perspective, the second move was often just as tradeable as the first — sometimes more so, because the stock's behavior over the intervening period had provided additional information about whether the original buying interest was genuine.
The primary signal system had nothing to say about this situation. Once a signal was confirmed, the system tracked the stock's state but didn't generate any further alerts about its subsequent behavior. I was watching these second moves happen on the dashboard and having no systematic way to flag them. This post explains how I designed the secondary signal layer to address that gap, and what I learned in the process.
What the Secondary Signal Is Designed to Detect
The secondary signal fires when a stock that has already generated a primary breakout signal subsequently crosses above its 120-period moving average from below. The moving average is calculated from 144-tick candles — the same candle structure used throughout the rest of the system — rather than from time-based bars. This keeps the indicator consistent with the underlying data framework and ensures it updates continuously during the trading session rather than resetting at fixed intervals.
Each time the price crosses above the moving average, a counter increments and the signal updates with three pieces of information: the cumulative number of crossings that day, the ratio of current trading value to the stock's baseline trading value since the primary signal fired, and the ratio of current trade intensity to baseline — both expressed as multiples. The signal also records the exact time of the most recent crossing.
The design choice to track crossings rather than position relative to the moving average was deliberate. I wasn't interested in whether the stock was above or below the moving average at any given moment — that's a relatively common condition. I was interested in the dynamic event of a crossing: the specific moment when price was below the average and then moved above it, which often coincides with a shift in short-term momentum.
The First Design Version and Why It Failed
The first version of the secondary signal used a different trigger: a drop of 10% from the primary breakout high, followed by a surge in trading value and trade intensity relative to a baseline. The idea was to identify a meaningful pullback after the primary breakout and then flag when conditions looked strong again.
This version had a serious problem that showed up almost immediately in live data. The baseline trading value calculation — which used the average trading value since the primary signal fired — could produce extremely small denominators in the early minutes after a signal, when very little trading had occurred. A small number of trades in a quiet moment could push the computed multiple to absurdly high values — 50x, 80x, even approaching 100x — which weren't meaningful signals, just artifacts of dividing by a near-zero baseline.
I tried several approaches to stabilize the calculation: minimum sample requirements, floor values on the denominator, expanding the baseline window. Each fix addressed one edge case but created another. The calculation was fragile, and I was spending more time managing the edge cases than improving the underlying logic.
The redesign to a crossing-based trigger solved this cleanly. A crossing is a discrete event that either happened or didn't. It doesn't require a ratio calculation with a potentially unstable denominator. The trading value and trade intensity ratios are still computed and displayed at the moment of each crossing — but they're used as supplementary context rather than as the trigger itself, which means their occasional instability affects interpretation but not system behavior.
What the Crossing Count Revealed About Stock Behavior
Once the crossing-based design was live, the crossing count metric produced an unexpected insight. On some days, a stock would show crossing counts above 100 by mid-session. That seemed like a lot — a hundred crossings should mean a hundred meaningful momentum shifts. But when I pulled up the chart for these high-count stocks, the pattern was almost always the same: the stock was trading in a very tight range directly on top of the moving average, oscillating back and forth across it with small price moves.
This is a classic characteristic of sideways consolidation — when price has no clear direction and straddles a reference level, crossing it frequently in both directions on minimal movement. The high crossing count wasn't a signal of repeated momentum shifts. It was a signal that the stock was going nowhere.
This observation led me to rethink how to interpret the crossing count. A high count combined with low trading value multiples at each crossing is a consolidation signal — the stock is range-bound. A low count combined with high trading value multiples at each crossing is what you actually want to see: the crossing is rare, which means it's a genuine directional event rather than range noise, and the trading value surge at that moment confirms real participation.
The most reliable secondary signals in my experience have been stocks where the crossing count is low — typically under 10 for the session — and the trading value at the crossing is running at 2x to 3x or more above the post-primary baseline. These tend to coincide with the stock making a genuine second leg of its move rather than just testing a level it had already broken.
How the Secondary Signal Appears on the Dashboard
On the live dashboard, the secondary signal appears as an additional block below the primary signal card for each stock that has generated both. It shows the crossing count, the most recent crossing time, the current signal grade, and the trading value and trade intensity multiples at the most recent crossing.
Stocks where the secondary signal has fired but the crossing count is very high — above 50, say — I've learned to treat as consolidating rather than breaking out again. The numerical display makes this judgment possible at a glance without needing to pull up the individual chart.
Today's Investing Insight — Why Moving Average Crossings Work as Event Triggers
Moving averages are often used as a static reference — is the price above or below this line? But some traders find them more useful as dynamic event triggers: the crossing itself, rather than the position, is what matters. The logic is that a crossing represents a change in the relationship between current price and recent average price — specifically, a shift from price being below average to above it. In momentum-driven contexts, this shift can signal that the balance between buyers and sellers has changed. It's not reliable in isolation — as the high crossing counts in consolidating stocks showed clearly — but combined with volume confirmation, it identifies moments where the shift appears to be driven by real participation rather than random drift.
---
This post documents a personal journey of building an algorithmic trading system and is not a recommendation of any specific stock or strategy. Secondary signals are supplementary information and do not predict future price movements. All investment decisions and their outcomes are the sole responsibility of the investor.
Comments
Post a Comment