What is a worked example of Ichimoku Strategies?

What is a worked example of Ichimoku strategies?

A worked example is a fully transparent scenario that shows every input and calculation step for Ichimoku strategies, so you can reproduce the numbers and check whether the stated outputs follow from the stated assumptions. In Ichimoku practice, the “strategy” part refers to rules for interpreting the Ichimoku outputs (for example, whether the price is above or below the cloud). A worked example should therefore separate two things: (1) the stable indicator mechanics (how each line and the cloud are computed) and (2) the variable interpretation choices (the rules you apply, plus market conditions).

This article provides a worked, numeric scenario using generic “price highs and lows” over fixed lookback windows. It assumes you are using standard Ichimoku window lengths and that all calculations are done consistently from the same dataset. No real-time data or live outcomes are implied.

How does a worked example of Ichimoku strategies work?

Ichimoku (often spelled Ichimoku Kinko Hyo) uses several components. The exact naming can vary, but the typical components are:

• Tenkan-sen (Conversion line): typically the midpoint of the highest high and lowest low over a short lookback window.
• Kijun-sen (Base line): typically the midpoint of the highest high and lowest low over a medium lookback window.
• Senkou Span A (Leading span A): typically the average of Tenkan-sen and Kijun-sen, plotted forward.
• Senkou Span B (Leading span B): typically the midpoint of the highest high and lowest low over a longer lookback window, plotted forward.
• Kumo (Cloud): the shaded area between Span A and Span B.

Worked numeric scenario (with explicit assumptions)

Assumptions (state these before calculating):

1. Lookback windows are 9, 26, and 52 periods for Tenkan, Kijun, and Span B.
2. Each “period” has a high and low value.
3. All midpoint calculations are arithmetic means of the form (max(highs) + min(lows)) / 2.
4. “Forward plotting” does not change numeric values; it only shifts where you would display them.

Now assume the following computed extremes from your chosen dataset:

• For the last 9 periods: max(high)=110 and min(low)=90.
• For the last 26 periods: max(high)=120 and min(low)=85.
• For the last 52 periods: max(high)=125 and min(low)=80.

Compute each line:

1. Tenkan-sen = (110 + 90) / 2 = 100.
2. Kijun-sen = (120 + 85) / 2 = 102.5.
3. Senkou Span A = (Tenkan-sen + Kijun-sen) / 2 = (100 + 102.5) / 2 = 101.25.
4. Senkou Span B = (125 + 80) / 2 = 102.5.

Kumo (cloud) interpretation setup (not a guaranteed signal):

• At the forward-plotted position, the cloud is between Span A = 101.25 and Span B = 102.5.
• The “cloud thickness” here is 102.5 − 101.25 = 1.25 in price units.

A worked example of an “Ichimoku strategy” rule could then define what to do with these outputs, but the key point is: the indicator values above are independently verifiable from the stated max/min assumptions. The rule you choose (for example, checking whether a current reference price is above or below the cloud) is a separate, variable step.

What are the relevant limitations and risks?

A worked example helps you verify calculations, but it does not remove uncertainty. Key limitations include:

1. Parameter and data-definition mismatch: If you use different window lengths, different data (bid vs ask, different session handling), or different rounding conventions, the computed lines will change even if the underlying market is the same. 2. Interpretation is not the indicator itself: Ichimoku lines are descriptive outputs. Whether you treat “above the cloud” as bullish or “inside the cloud” as neutral depends on your rules, not on a fixed law of nature. 3. Regime shifts: Ichimoku-related interpretations can behave differently across trending vs ranging market regimes. A rule that matches one regime may underperform in another. 4. Costs and execution differences: Even if you reason correctly about indicator states, real-world outcomes can be affected by spreads, fees, slippage, and order handling. Historical relationships do not establish future results. 5. Failure mode: cloud role confusion: Some users treat the cloud as a standalone predictor without specifying the underlying timing logic (what exact period you reference, and how you align forward-shifted spans with the current bar).