> For the complete documentation index, see [llms.txt](https://chartschool.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chartschool.stockcharts.com/table-of-contents/glossary/glossary-w.md).

# Glossary - W

<table data-header-hidden><thead><tr><th width="127"></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><a href="/table-of-contents/glossary/glossary-a.md"><strong>A</strong></a></td><td><a href="/table-of-contents/glossary/glossary-f.md"><strong>F</strong></a></td><td><a href="/table-of-contents/glossary/glossary-k.md"><strong>K</strong></a></td><td><a href="/table-of-contents/glossary/glossary-p.md"><strong>P</strong></a></td><td><a href="/table-of-contents/glossary/glossary-u.md"><strong>U</strong></a></td></tr><tr><td><a href="/table-of-contents/glossary/glossary-b.md"><strong>B</strong></a></td><td><a href="/table-of-contents/glossary/glossary-g.md"><strong>G</strong></a></td><td><a href="/table-of-contents/glossary/glossary-l.md"><strong>L</strong></a></td><td><a href="/table-of-contents/glossary/glossary-q.md"><strong>Q</strong></a></td><td><a href="/table-of-contents/glossary/glossary-v.md"><strong>V</strong></a></td></tr><tr><td><a href="/table-of-contents/glossary/glossary-c.md"><strong>C</strong></a></td><td><a href="/table-of-contents/glossary/glossary-h.md"><strong>H</strong></a></td><td><a href="/table-of-contents/glossary/glossary-m.md"><strong>M</strong></a></td><td><a href="/table-of-contents/glossary/glossary-r.md"><strong>R</strong></a></td><td><a href="/table-of-contents/glossary/glossary-w.md"><strong>W</strong></a></td></tr><tr><td><a href="/table-of-contents/glossary/glossary-d.md"><strong>D</strong></a></td><td><a href="/table-of-contents/glossary/glossary-i.md"><strong>I</strong></a></td><td><a href="/table-of-contents/glossary/glossary-n.md"><strong>N</strong></a></td><td><a href="/table-of-contents/glossary/glossary-s.md"><strong>S</strong></a></td><td><a href="/table-of-contents/glossary/glossary-x-y-z.md"><strong>X, Y, Z</strong></a></td></tr><tr><td><a href="/table-of-contents/glossary/glossary-e.md"><strong>E</strong></a></td><td><a href="/table-of-contents/glossary/glossary-j.md"><strong>J</strong></a></td><td><a href="/table-of-contents/glossary/glossary-o.md"><strong>O</strong></a></td><td><a href="/table-of-contents/glossary/glossary-t.md"><strong>T</strong></a></td><td></td></tr></tbody></table>

### Washout Day <a href="#washout_day" id="washout_day"></a>

A selling climax or high volume decline that “washes out” all the sellers and paves the way for buyers to take over. This may also take the form of a high volume [hammer](/table-of-contents/glossary/glossary-h.md#hammer) after an extended decline.

### Wedge <a href="#wedge" id="wedge"></a>

A reversal chart pattern characterized by two converging trend lines that connect at an apex. The wedge is slanted either downwards or upwards, demonstrating bullish or bearish behavior respectively. See our ChartSchool articles on [Falling Wedge (Reversal)](/table-of-contents/chart-analysis/chart-patterns/falling-wedge.md) and [Rising Wedge (Reversal)](/table-of-contents/chart-analysis/chart-patterns/rising-wedge.md).

### Weekly Reversal <a href="#weekly_reversal" id="weekly_reversal"></a>

An upside weekly reversal is present when prices open lower on Monday, but then, on Friday, close above the prior week's close. A downside weekly reversal opens the week higher but closes down by Friday.

### Weighted Average <a href="#weighted_average" id="weighted_average"></a>

A moving average that uses a selected time span but gives greater weight to the more recent price data.

### Weighted Close <a href="#weighted_close" id="weighted_close"></a>

A weighted average of the high, low and close that places more weight on the closing value by counting it twice.

### Whipsaw <a href="#whipsaw" id="whipsaw"></a>

A whipsaw occurs when a buy or sell signal is reversed in a short time. Volatile markets and sensitive indicators can cause whipsaws. For example, a whipsaw would occur if a position trader initiates a long position on a bullish [MACD](/table-of-contents/glossary/glossary-m.md#macd_moving_average_convergence_divergence) crossover and has to close it the next day because of a bearish moving average crossover. The signal was reversed and the trader had to exit quickly.

### Wilder, Welles <a href="#wilder_welles" id="wilder_welles"></a>

Developer of the [RSI](/table-of-contents/glossary/glossary-r.md#relative_strength_index_rsi) indicator and the [Directional Movement Indicator (DMI)](/table-of-contents/glossary/glossary-d.md#directional_movement_indicator_dmi).

### Williams %R <a href="#williams_r" id="williams_r"></a>

Developed by Larry Williams, Williams %R is a momentum indicator much like the [Stochastic Oscillator](/table-of-contents/glossary/glossary-s.md#stochastic_oscillator), often used for measuring overbought and oversold levels. The scale ranges from 0 to -100, with readings from 0 to -20 considered overbought and readings from -80 to -100 considered oversold. Typically, Williams %R is calculated using 14 periods and can be used on intraday, daily, weekly or monthly data. See our ChartSchool article on [Williams %R](/table-of-contents/technical-indicators-and-overlays/technical-indicators/williams-r.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://chartschool.stockcharts.com/table-of-contents/glossary/glossary-w.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.