Hammer and Shooting-Star Screeners: Shape Filters vs Trade Signals

Exact field rules for hammer and shooting-star matches

The public field is hammer_shooting_star_state. These are fixed screening rules; this page does not provide controls for changing the shadow ratios. All comparisons below include equality. Body color is unrestricted, and there is no positive minimum body-size requirement.

• The body-position test uses one body endpoint. It does not require the entire hammer body to lie inside the top 40% of the range.
• A zero-range candle fails. A zero-body candle can pass because the short-shadow allowance still permits one minimum tick; do not assume the screen excludes every doji.
• Minimum tick is the symbol's minimum price increment, not the number of decimals shown in a rounded table cell. It affects the short-shadow allowance when body size is smaller than one tick.

Recalculate a match before adding it to a watchlist

These hypothetical prices use one currency and a minimum tick of 0.01. For open 100, high 101.25, low 97.50 and close 101, the body is 1, upper shadow 0.25, lower shadow 2.50 and range 3.75. The hammer tests pass: 2.50 >= 2, 0.25 <= 1 and body top 101 >= 99.75. This proves only the shape.

Audit every row using its own high, low and quote precision

The public table contains daily snapshots for the selected Pineify collections. Collection membership limits the scan universe; an empty shortlist does not mean no hammer exists elsewhere. The full Market Screener exposes the Hammer / Shooting Star field for directional filtering.

• Record the collection, exchange-qualified symbol, reported state and bar date. Check the response timestamp too: the public API caches responses for up to four hours, and the underlying daily bar may be older.
• Find the same symbol in TradingView using ordinary daily candles for the same exchange and session. Check adjusted-price settings and the data feed before comparing results; a different series can have different highs and lows.
• Read all four OHLC values for the reported candle in the Data Window at sufficient precision. Verify high >= max(open, close) and low <= min(open, close). Do not calculate shadows from only the displayed last price.
• Check that symbol's minimum tick, then calculate body, range and both shadows. Preserve the original precision until every inequality has been checked; rounding 102.01 down to 102 would incorrectly pass the example above.
• Confirm that the daily candle has closed before treating its geometry as final. During an unfinished bar, a new high, low or close can remove a match.
• Keep a review row containing symbol, bar date, OHLC, tick size, shape result, trend context and confirmation status. Resolve data or formula mismatches before using the shortlist.

Add trend context and confirmation as separate decisions

TradingView describes a hammer in a decline and a shooting star in an advance. Its pattern indicators offer SMA 50, SMA 50 with SMA 200, or no trend detection. Pineify's field above has no trend condition, so its shape labels can disagree with a trend-filtered chart indicator on the same candle.

• A hammer-shaped candle after an advance has hanging-man context; a shooting-star shape after a decline has inverted-hammer context. This field does not rename those cases based on trend.
• If your review rule requires a later daily close above the hammer high, the first example remains unconfirmed until a subsequent close exceeds 101.25. A close of 101.20 fails that chosen rule even though the original shape still matched.
• For the shooting-star example, a chosen later-close-below-low rule needs a subsequent daily close below 99.75. These are example confirmation rules, not built-in filters or forecasts.
• Confirmation can occur at a less favorable price or never occur. A later gap or continued trend can invalidate a trade idea; shape and confirmation alone contain no execution-cost or risk model.

Use the hosted field or define a finite custom scan

Use Market Screener when the existing Hammer / Shooting Star field matches your rules. For a different shadow ratio, a positive-body requirement, trend context or a later-bar confirmation rule, ask Pine Script AI Coding Agent for a script using an explicit, finite symbol list. Review the source and test the output in TradingView before relying on it.

• Specify the exchange-qualified symbols, daily timeframe, completed-bar policy, tick handling, body threshold and the exact confirmation condition. Include the equality and zero-body examples above as acceptance cases.
• A generated chart script does not add a custom field to the hosted Market Screener or scan every exchange automatically. Keep the requested symbol list within the platform limits applicable to the script and account.