Engulfing Pattern Screener

The exact rules behind a matching row

Pineify reports the engulfing_state field. Both candles must have a positive high-low range and opposite, nonzero bodies. The comparison uses the immediately preceding candle; it does not search for any engulfing pair elsewhere in the visible history.

• One shared body endpoint is allowed when the other extends far enough to make the body larger. Matching both endpoints fails the strict size test.
• A prior close exactly equal to its SMA 10 fails both directional context tests. A doji with open equal to close also fails the direction test.
• Neither a prior small-body threshold nor a current above-average-body threshold is required. A gap is not mandatory, and the current close need not cross SMA 10.

Worked acceptance cases for the daily scan

These are hypothetical prices in the same currency, not observed trades. For the bullish cases, assume the prior bar opens at 101, closes at 99, has a high of 103 and a low of 98. Its preceding nine closes are 101, 102, 100, 101, 100, 102, 101, 100 and 104. Their sum is 911, so the prior SMA 10 is (911 + 99) / 10 = 101.

Check every candidate against the same chart data

A pattern label is only the first check. The public table shows daily snapshots for the selected Pineify collections, not every listed security. Start with the collection and symbol search, then inspect bullish or bearish readings. The Market Screener supports filtering the Engulfing Pattern field when you need a directional shortlist.

• Record the exchange-qualified symbol, selected collection, direction and bar date. An empty result says nothing about symbols outside that collection.
• Check the table timestamp and underlying bar date. The public API can cache a response for four hours; a newly cached response may still contain an older market bar. Do not treat missing data as a failed pattern.
• Open the result in TradingView and use ordinary daily candles for the same exchange and session. Different feeds, adjusted prices or synthetic candles can change opens, closes and SMA values.
• For the reported bar, read both candles' open and close in the Data Window. Calculate the body endpoints and sizes, then compare the prior close with SMA 10 at the prior bar, not the current value.
• Confirm that the reported daily candle has closed before treating its shape as final. Review volume, nearby support or resistance, liquidity and subsequent price action separately; none is included in this state.
• Keep a review note with symbol, bar date, reported direction, body check, SMA check and any mismatch. Resolve a mismatch in data or rules before using the row as a candidate.

Why another engulfing scanner can disagree

TradingView documents engulfing as a body pattern, so covering the previous high-low range is unnecessary. Its built-in pattern indicators offer SMA 50, SMA 50 with SMA 200, or no trend detection. Pineify uses the prior close against SMA 10. Comparing labels without matching those settings can produce different results even on the same candles.

• A long wick that crosses the prior high or low is not enough for Pineify. Both open-close endpoints must be contained.
• An outside bar can fail because its body is too small, its candles share the same direction, or its prior close is on the wrong side of SMA 10.
• Bullish describes a detected shape, not a buy order. The next session may gap down or the preceding decline may continue. There is no win-rate estimate in this screen.

Use a custom script only for rules the field does not include

Use Market Screener for the existing Engulfing Pattern field. If your definition needs a full-range engulfing rule, a volume threshold or a different trend filter, describe those differences to Pine Script AI Coding Agent and ask for a script for an explicit, finite symbol list. Review the generated source and test it in TradingView before relying on its output.

• Specify the symbol list, daily timeframe, completed-bar requirement, body equality policy and trend rule. State whether the change should replace or supplement Pineify's current test.
• Use the acceptance cases above to check the requested behavior, then add cases for each custom condition. A generated chart script does not add a new field to the hosted Market Screener or scan every market automatically.