October 22, 2020
This example identifies trending states using a higher timeframe and various indicators. It is composed of four main conditions. A long signal is generated when the following conditions occur:
1) On the 5 Minute chart, the EMA 3 and 8 must be above the EMA 50.
2) The remaining conditions run on the 1 Minute chart. Again, the EMA 3 and 8 must be above the EMA 50.
3) This utilizes a slow and fast MACD. The fast MACD signal line must be sloping up, and above the slower MACD line. Also, the fast MACD signal line must be above the zero line.
4) The RSI 10 must be sloping up, and greater than 50.
All the conditions are reversed for a short signal.
This topic demonstrates how to define a maximum number of pullback bars requirement for a pullback system (rule #3). A long signal is generated when the following conditions occur:
1) The EMA 200 must be sloping upward.
2) The close of the pullback bars must stay above the EMA 34.
3) The pullback bars are restricted to a maximum of 5 bars.
4) The signal occurs on the reversal up bar.
All the conditions are reversed for a short signal.
October 15, 2020
This example identifies two criteria. When the closing price crosses the EMA 8, or when a bar closes near its high(for a long) and its bottom wick touches the EMA 8. More specifically, for a long signal the close price must be within 5 ticks of the high(near the top of the bar). The open must be above the EMA 8. The low wick must touch or penetrate through the EMA 8.
October 1, 2020
This demonstrates how to reset the Signal Blocker node so that only 1 signal can occur for each swing point line. For long signals, a new swing high line must occur before the next long signal is allowed to plot. i.e. For each swing high line, there will only be one long signal. Any additional long signals are blocked until a new swing high point is detected. The conditions are reversed for short signals.
September 24, 2020
This example demonstrates how to detect doji bars, and then modify the output so it can be used to block signals that occur on those doji bars.
September 17, 2020
This demonstrates two solutions for reducing unwanted small/minor inflections(reversals) of an indicator when used in the Inflection solver. In doing so, the medium to large inflections of the indicator are identified by the Inflection solver. The MFI indicator is used for this topic.
This demonstrates how to identify when bar wicks (high or low price) crossover a moving average, and how to reverse the signal from long to short or short to long depending if you want a signal with the trend or counter trend. The EMA 55 is used.
September 10, 2020
This example produces a signal after the high and low of a bar is contained in between the SMA 20 and SMA 50, and then the closing price breaks/closes outside of the SMA’s. When price is above the SMA 200, only long signals occur and vice versa. After this system is built, an additional filter is added to restrict/remove signals. This provides a good example of using the If-Then node. A long signal is generated when the following conditions occur:
1) Price must be above the SMA 200.
2) An entire bar must be in between the SMA 20 & 50. This begins looking for the breakout bar.
3) When a bar closes below or above one of the SMA’s a long signal occurs. It does not matter if the SMA 20 is above or below the SMA 50. The SMA’s can be stacked in any order.
Afterwards, this filter/condition is added to the original system.
4) The long signal is only permitted when the closing price crosses above the SMA 20 or 50. Crossing below does not give a signal. This is when the If-Then nodes are used.
September 3, 2020
This example identifies a possible bounce/rejection of price off of a moving average, and the moving average, on a 15 minute higher timeframe, must be sloping/trending in the direction of the bounce. A long signal is generated when the following conditions occur:
1) The EMA 18 and EMA 20 must both be sloping up.
2) The EMA 18 and EMA 20 on the 15 minute timeframe must both be sloping up.
3) 4 bars must have been above the EMA 18 prior to the bounce. The bars must not have touched the EMA.
4) Signal when price touches the EMA 18.
All the conditions are reversed for a short signal.
August 27, 2020
This answers a two part question. The first part generates a long signal when the closing price crosses above a (imaginary) +10 tick offset distance above the SMA 200 line. And, generates a short signal when price crosses below the -10 tick offset distance below the SMA 200 line.
The second part generates a long signal when price crosses the +10 tick offset distance above the SMA 200 in either direction. And, generates a short signal when price crosses the -10 tick offset distance below the SMA in either direction.
Lastly, we demonstrate how to implement these signals into Raven to submit a market order.
This example builds two Crossover solvers to generate signals in opposite directions. The first Crossover solver generates a long signal when the closing price crosses below the lower Bollinger band. And, a short signal when price crosses above the upper Bollinger band.
The second Crossover solver generates a long signal when the closing price crosses above the upper Bollinger band. And, a short signal when price crosses below the lower Bollinger band.
August 20, 2020
This system generates a signal whenever price is near the EMA 30 and other trend filters are in place. The baseline trend direction is determined by the amaATRTrailingStop indicator. For a long signal, price must be below a recent swing high as determined by the Swing indicator. Also, the high price must be within 3 ticks of the EMA30 or above it, and below the amaATRTrailingStop. All the conditions are reversed for a short signal.
This example demonstrates how to detect when the MACD, or similar indicators, reverse direction before crossing the zero line and near the zero line. For this example the MACD must get within a 0.5 range of the zero line to detect the reversal. For a long reversal signal, the MACD must cross down through the +0.5 level, and then reverse before crossing the zero line into negative values. For a short reversal signal, the MACD must cross up through the -0.5 level, and then reverse before crossing the zero line.
This topic could be considered identifying a trend continuation condition. A long output is generated when the following conditions occur:
1) Price must be above all EMAs. The EMA 20, EMA 50, EMA 100, and EMA 200.
2) The EMA 20 must cross below the EMA 50, and then cross back above the EMA 50.
a) Price must close above the EMA 20 & 50.
b) The bar must close up. This is labeled Bar1.
3) A signal is generated on the next bar (Bar2) if,
a) The EMA 20 is still above the EMA 50.
b) The EMA 20 is sloping up.
c) The bar closes up as well.
All the conditions are reversed for a short signal.
August 13, 2020
Shark Week. No workshop
July 30, 2020
The first part of this topic starts by building two systems/logics that generate a signal when only 2 out of 3 indicators go into an extreme overbought or oversold condition(above 95 or below 5). The Additive node is the key to identifying/signaling when a fewer number of conditions need to occur out of a higher number of possible conditions that are being monitored. This design can easily be modified for identifying 3 out of 5, or 4 out of 7, or whatever number of conditions your system uses by simply reducing the Output value of the solvers going into the Additive node. This example looks for the Double Stochastics or RSS to go above 95 or below 5, or the Stoch RSI to go above 0.9 or below 0.1. It identifies when 2 of the 3 indicators go into the extreme ob/os levels and generates a setup signal.
The second part uses the setup signal to start looking for two situations when the indicator(s) make a limited/minor pullback from the ob/os levels, and generates a signal if one of the situations occurs. If one of the ob/os indicators pulls back too far, to less than 60 or more than 40 or the StochRSI to 0.6 or 0.4, then the second part fails and there is no signal. A long signal is generated when the indicators are oversold, and a short signal when overbought, making this a counter trend system.
- The first situation is when only one of the indicators pulls back, and one indicator remains in the extreme ob/os level. If the indicator, that pulls back, returns to the extreme ob/os level a signal occurs.
- The second situation is when all the indicators pullback. At least 2 of the 3 indicators must re-enter the extreme ob/os level within 10 bars of leaving the ob/os level.
July 23, 2020
This example is designed to work on a hybrid renko chart. Long signals are generated when a reversal up bar occurs higher than the previous reversal up bar to form a higher low point (HL). A short signal is generated when a reversal down bar occurs lower than the previous reversal down bar to form a lower high point (LH).
A follow up question is asked to add the slope of an EMA 120 from the 3, 5, and 10 minute timeframes as a filter to the signals.
This example creates an exit signal when the slope of the EMA 9 does not match the slope of the amaADXVMA 2. e.g. When the EMA and the amaADXVMA are both sloping up together, if the ADXVMA goes flat or slopes down, while the EMA is still sloping up, then an exit signal is generated, because the slopes no longer match.
July 9, 2020
This is a simple demonstration of adding the slope direction of 2 indicators as a filter to an existing system. In this example the slope of the EMA 21 and slope of the amaDynamicTradersIndex » Signal Line are used.
July 2, 2020
This example demonstrates combining multiple indicator conditions together, attempting to identify an early trend move. A long output is generated when the following conditions occur:
1) The EMA 5 is above the EMA 10 for the default timeframe and the 4Hr chart.
2) The RSI must be above 50.
3) The Stochastics D is sloping up, and below the oversold level (75). And as an alternative, later on another solver is created for the Stochastics to be above the oversold level.
4) The MACD histogram is sloping up, and below the zero line.
All the conditions are simply reversed for a short signal.
June 18, 2020
In this question, the customer wants to generate a signal when a custom indicator’s output (something similar to a momentum indicator) returns back to zero after the output has been a positive or negative value. A long signal occurs when the indicator output is a positive value and then goes to zero. A short signal occurs when the output is a negative value and then returns to zero.
May 14, 2020
This workshop lesson uses an EMA 10, SMA 20, and SMA 40 combined with a price extension and pullback conditions to produce a signal. The following four rules/requirements must occur in the following order to produce a long signal:
1) The EMA 10 must cross above the SMA 20.
2) A bar must touch the SMA 40. #1 and #2 might occur on the same bar.
3) The must occur on a different bar from #2. A bar must touch the EMA 10. If the body any bar (open and close prices) is below the SMA 20, the set up is invalid.
4) A signal occurs when the body of a bar is above the EMA 20. This may be the same bar as #3, because the wick may touch the EMA 10.
April 30, 2020
This topic demonstrates how to find a simple 4 or 5 bar reversing renko bar pattern. All 4 reversal bars are consecutive (all in a row, no continuation bars in between).
This demonstrates building a bounce signal off of an EMA14 moving average, with some custom requirements to help eliminate signals during consolidation. Some of the rules/requirements are set up in such a way that this design is tailored for a 5 range chart. A long signal is generated when the following conditions occur:
1) The EMA 14 must have a minimum slope at the signal bar. A 0.5 ticks of slope is used in the Slope solver.
2) The entire bar (low price) must have been above the EMA14 and the EMA 5.
3) The low price of the bar, 2 bars back from the signal bar, must be above the EMA 5.
4) 2 bars are allowed for price to pullback to the EMA 14 to possibly form a signal bar.
5) The Signal bar has the following requirements:
a) The signal bar must not extend below the EMA14 by more than 3 ticks. i.e. The low of the bar may not go more than 3 ticks below the EMA14.
b) The low of the signal bar must get within 1 tick of the EMA14. i.e. Within 1 tick above the EMA 14.
c) The signal bar must close above the EMA14, and below the EMA5.
This demonstrates building an Ichimoku signal with a few custom filters of the Kumo cloud and Chikou span. This system uses, and thus requires, the amaIchimokuKinkoHyo indicator from LizardIndicators.com. A long signal is generated when the following conditions occur:
1) The signal trigger is the Tenkan crossing above the Kijun. The remaining rules are filtering conditions.
2) If the Tenkan and Kijun cross above occurs below the Kumo cloud, then the Kumo must have a minimum thickness of 4 ticks. This is later adjusted to 8 ticks. If the crossover occurs above the Kumo there is no thickness requirement.
3) The Kumo cloud that is visually extended into the future must be in a bullish direction.
4) Price must not have touched the Chikkou span during the last 26 bars. i.e. The Chikou must be above the high price looking back for 26 bars.
5) The closing price must be above the Tenkan and Kijun on the crossover bar (#1 above).
This system is plugged into BlackBird (May 1st workshop), along with a custom entry order and stop-loss.
This aims to address a growing misunderstanding of BloodHound’s ability to perform pattern recognition. This video discusses the kind of simple candlestick patterns that BH can identify versus the candlestick patterns that are too complex, and the larger price/charting patterns as well.
April 23, 2020
No recording today.
April 9, 2020
Stochastic K Counter Trend Signal with HTF EMA Slope Filter
This example builds a Stochastic K oversold/overbought crossover signal filtered by a higher timeframe EMA20 direction. This was designed to work on a range chart. A long signal is generated when the Stochastic K crosses below the 30 value, and the EMA 20 on a 10 range chart must be sloping up on the crossover or a couple of bars just before the crossover. Then wait for the first up bar to fire off the signal. The reverse conditions will generate a short signal.
April 2, 2020
This system uses the Swing Highs & Lows indicator to identify a price breakout and pullback condition on a renko chart. A long signal is generated when the following conditions occur:
1) A renko bar crosses above the swing high line, and at least 1 more up bar must occur after the crossing bar. (2 concurrent up bars minimum)
2) Price must pullback to within 1 renko brick length from the swing high line. If price crosses below the swing high line, it must be limited to 2 bars. 3 bars crossing the swing line invalidates the setup.
3) The signal occurs if the next bar is a reversal bar.
All the conditions are simply reversed for a short signal.
March 19, 2020
No workshop topics to post today
March 5, 2020
This demonstrates how to compare a 5 minute bar price (intra-day timeframe) to a moving average indicator running on a daily chart/timeframe. BloodHound will run on the intra-day chart, and the Chameleon indicator is used to acquire daily timeframe bars and input that data series into an SMA50. A Comparison solver is used to detect when the 5 minute closing price is within a few points of the SMA50 running on a daily chart/timeframe.
This system detects consolidation of hybrid-renko bars, and the direction that price breaks out from that pattern. The consolidation pattern is 4 or more reversal bars in a row. A breakout is when price stops reversing and thus a second bar in the same occurs (a non-reversing bar). Also included, is a failed breakout detection.
February 28, 2020
The Time Session solver was improved in version 126.96.36.199. The new session interface alleviates a limitation the previous Time solver had, because it used NinjaTrader’s ‘Trading Hours’ session interface. This video explains how to use the new Scheduler interface, and some examples of how and why you might use the Time Session solver.
February 20, 2020
This illustrates filtering renko reversal bars. A long signal is generated on a reversal up bar only if the low of the bar is below the swing low point. In other words, the current reversal up bar must be lower than the previous reversal up bar. The reverse conditions produce a short signal. The Swing Highs & Lows indicator is used to identify when a lower low or higher high is made in the reversal bars.
This lesson expands upon the topic from Feb 6, 2020 Counter Trend VWAP Signal at Std. Dev. 2 Line, to establish a minimum and maximum slope of the Std. Devl 2 lines to qualify/filter signals. We take that system and apply a slope requirement to the VWAP Std. Dev. 2 lines. For a long signal the Std. Dev. 2 Lower line must have a little downward slope, but no more than 0.8 ticks of downward slope.
February 13, 2020
This topic shows how to build a simple logic that identifies when the High price is above the highest moving average (MA) of 2 other MA’s. Or, if the Low price is below the lowest of the 3 MA’s.
In this topic a customer wanted to identify when a swing point line has been plotting/existed for more than 40 bars. And also, generate a signal if price breaks the swing point line after the 40 bar minimum. The Signal Counter node is used to identify if 40 bars of a swing point plot has occurred. Along with 2 Comparison solvers that identify when a new swing point occurs, and when price breaks a swing point line. Those 2 solvers are used to reset the Signal Counter node.
February 6, 2020
Counter Trend VWAP Signal at Std. Dev. 2 Line
This demonstrates how to build counter trend signals when price crosses the VWAP Std. Dev. #2 line. A long signal occurs when price crosses below the VWAP Std. Dev. 2 Lower line, and a short signal occurs when price crosses above the VWAP Std. Dev. 2 Upper line. This will be used in the next BlackBird workshop to apply a stop-loss and profit target to the signals.
Are you a “price action” type of trader that visually picks subjective/discretionary support/resistance lines based on a chart’s price action, and trades them? No S/R indicator is used. This lesson will help you understand how to implement those s/r lines/price values into a BloodHound system. In this specific example, a Target s/r line, Stop-out s/r line, and a Signal s/r line are used to identify a price pullback based pattern and then a trade signal occurs. The basics of the price pattern is for price to pullback and touch the Signal line before touching the Target line. Also, when price pullback to the Signal line, it must not touch the Stop-out line before crossing back over the Signal line.
January 30, 2020
Blocking the First 2 Signals and Allowing the 3rd and Any Other Signals
This demonstrates how to use the Signal Counter node to block X number of first signals in the same direction, and then allowing any remaining/following signals through.
January 23, 2020
No Workshop Today
January 16, 2020
If your system generates multiple signals in the same direction, but you only want to hear a sound alert on the first signal, this will demonstrate how to do that using two BloodHound indicators on the chart. The process is to create two logic templates. The first logic template is your original system with all the signals. The second logic template only allows the first signal through. All the signals afterwards that are in the same direction are blocked, until a signal in the opposite direction occurs.
This is to help clear up some confusion about charts that have several Data Series (timeframes) on the same chart. e.g. A 1 Minute Data Series, a 5 Minute Data Series, and a 15 Minute Data Series can all be added to the same chart window. And so, there has been some confusion as to which timeframe BloodHound is using or running on. This video explains how this all works.
This demonstrates how to identify when 3 MACD-BB indicators, that are running on different timeframes, are all sloping up together or down together. A 2 Minute, 5 Minute, and 15 Minute Data Series are placed on the same chart, along with 3 Sim22_MacdBBGaplessV4 on each of those timeframes. The Sim22_MacdBBGaplessV4 can be downloaded from Futures.io.
This demonstrates how to generate a long signal when the RSI crosses up above 15, and a short signal when the RSI crosses down below 85.
An up trend flag pattern is defined as follows:
1) A new daily high must be made. This is the first bar that potentially starts a flag pattern.
2) The next bar(s) must make a lower or equal high. This is the flag pattern forming. A maximum of 3 bars is allowed for this condition, thus limiting the flag pattern to a maximum of 4 bars.
3) The signal bar occurs, ending the flag pattern, when the current bar ‘s high is higher than the previous bar high.
4) Also, the signal bar’s low must not go lower than the previous bar’s low.
All the conditions are simply reversed for a short flag pattern.
December 12, 2019
This example demonstrates how to identify the broader trending state of the CCI indicator. The trend direction is determined by the CCI staying above the zero line for at least 6 bars or below the zero line for at least 6 bars. When either of those conditions occur, it is fed into the Toggle node so that the trend is held onto until the opposite trend direction condition occurs.
This example identifies pullback signals on renko charts where the trend direction is determined by two EMA's. The system rules are as follows.
1) The EMA 10 must be above the EMA 20.
2) A renko bar must pullback and touch the EMA 10.
3) The wick of the reversal bar must touch either the EMA 10 or EMA 20.
All the conditions are simply reversed for a short.
December 5, 2019
This example uses the Woodies CCI indicator to build signals based on the Turbo plots and filtered using the direction of the CCI. The system rules are as follows.
1) CCI 14 is above the zero line.
2a) The Turbo plot crosses below +100 and then crosses above +100 for the signal.
2b) Or, the Turbo plot crosses below zero and then crosses above zero for the signal.
1) CCI 14 is below the zero line.
2a) The Turbo plot crosses above -100 and then crosses below -100 for the signal.
2b) Or, the Turbo plot crosses above zero and then crosses below zero for the signal.
November 28, 2019
No Workshop - Thanksgiving Holiday
November 21, 2019
This example comes from a paper titled “A Refined MACD Indicator – Evidence against the Random Walk Hypothesis”, in which the customer summarized the system rules for Model #1. An Entry and Exit signal are built.
A long signal is generated when the MACD line crosses above the Average line, and the MACD line stays above the Avg. line for a minimum of 3 bars. If the MACD line crosses back down below the Avg. line before the 3rd bar, the signal is canceled. The signal occurs on the 3rd bar after the crossover.
An Exit signal is generated if the MACD crosses the Avg. line in the opposite direction.
Setting up a 4% profit target, along with the exit signal is demonstrated using the Raven strategy.
November 14, 2019
This topic teaches how to take an oscillator, MACD in this case, and create zones when signals are allowed or blocked. When the MACD is between zero and +0.25, long signals are permitted. When the MACD is above +0.25, signals are blocked/prevented. When the MACD is between zero and -0.25, short signals are permitted. When the MACD is below -0.25, signals are blocked. The signal trigger part is when price crosses above the recent swing high for a long signal, or when price crosses below the recent swing low for a short. Also, the Swing Trend indicator is used to identify a price action based nearterm market trend.
October 24, 2019
This example demonstrates the Signal Blocker function node to remove unwanted extra signals. The Signal Block node allows the first signal through, and blocks the additional signals that occur afterwards.
Filtering/Blocking Signals When Indicator is Overbought or Oversold
This example demonstrates how to filter out (remove) long signals when the Stochastics indicator is greater than 80, and filter out short signals when below 20. Setting up the Outputs correctly for the Threshold solver is the key.
October 17, 2019
This example identifies when the MACD Histogram bars/line is sloping in the opposite direction of the MACD line. When the Histogram bars are negative (below the zero line) and they are sloping toward the zero line, and the MACD line is sloping/moving away from the zero line, a long (exit) signal is given. The opposite condition generates a short signal. The Lookback function node is added to the system to require a minimum number of divergence bars before the signal is given.
October 10, 2019
This example shows how to detect a reversal bar on a renko, followed by a confirmation bar.
September 19, 2019
This example shows how to add a confirmation bar, in the same direction, check to any signal. The Swing Trend indicator > Swing Direction output is used to generate signals in the direction of the swing’s direction. When an up swing is generated a long signal is given and the bar afterwards must also be an up bar for the signal to occur. Otherwise the signal is prevented. The next day’s BlackBird workshop covers the other half of this topic.
This example demonstrates how to find bars with equal High or Low prices. And, how to compare the relative bar sizes to each other. For the 3 bar pattern, the first bar must be a long “thrust” bar. The second, or middle, bar must be half the size or smaller, and pointing in the opposite direction of the first thrust bar. The third bar must also be a long thrust bar, and in the same direction as the first thrust bar. The 4 bar pattern is similar except it has 2 middle bars.
September 12, 2019
This example shows how to detect when MAs (moving averages) are stacked or aligned in a trending order to create a long or short trending state. For this demo, 3 EMAs are used. An EMA 40, 80, and 120 period. A long state occurs when the EMA40 is above the EMA80, and the EMA80 is above the EMA120. A short state is the reverse order. When the stacking order is mixed there is no state/output.
August 22, 2019
This system looks for price to move downward, and volume to decrease, for several bars. All while price is approaching a support resistance line to generate a long signal. Two ways of using the Slope solver are shown for analyzing price and volume movements. The Support Resistance solver is used to determine when price is in close proximity to a pivot line.
August 8, 2019
This example demonstrates how to identify a specific renko bar pattern, including evaluating RSI values as confirmation or filtering. The pattern typically generates counter trend signals. The pattern for a long signal is as follows. After a down trend, of renko bars, identify 3 reversal bars. The last reversal bar is up. As a filter, look at the RSI values of the prior 2 down bars. The RSI value of the most recent reversal down bar must be higher than the prior down bar. In other words, the RSI is making higher low values.
This simple example shows how to setup a Comparison solver and AND node so that only long signals occur when price is above a moving average (EMA160). Or, show only short signals when price is below the MA.
August 1, 2019
This is a derivative of the K. A long signal is generated when a few bars are located below the VWAP line and above the lower std. dev #2 line. And, then price touches or breaks the lower std. dev #2 line. A short signal occurs using the reverse of those conditions. A secondary long signal is generated when bars move below the lower std. dev #2 line, and then cross back up above the lower std. dev #2 line.
Two Exit signals are created as well. The first is when price touches/hits the std. dev #3 line. The second is when price touches the VWAP line, for a profit exit.
How to block/filter out a signal if price is too far away from a fast moving average. This example uses EMA crossovers as the signal source. The crossover signals are to be blocked if price is 20 ticks or more away from the faster EMA.
How to block/filter out signals when the RSI goes above 70 or below 30. This example uses EMA crossovers as the signal source. Long signals are blocked if the RSI is above 70, and short signals are blocked if the RSI is below 30.
July 18, 2019
This shows how to add a 10 bar minimum requirement to a crossover signal. The fast moving average (MA) must stay on one side of the fast MA for at least 10 bars or the crossover signal is blocked.
This system demonstrates two main conditions. First, is detecting when the wick of a renko bar is touching a moving average. Second, is setting a minimum slope requirement for the signal. The signal occurs on the reversal of a renko bar. The wick of the reversal bar must be touching the EMA. The EMA must have a significant slope.
July 11, 2019
This topic is for hybrid renko charts. It demonstrates how to require a minimum number of pullback bars before a continuation signal can occur. And also, how to set a maximum number of pullback bars before a continuation signal can occur.
July 4, 2019
No workshop today. Happy 4th of July!
June 27, 2019
This illustrates how to take the MACD direction from two timeframes, and identify when they are in agreement/synchronized. A MACD from a 5 Minute chart and a 1940 Tick chart are used. When both MACD’s are trending up a long signal occurs. When both MACD’s are trending down a short signal occurs. When the MACD’s are mixed, no signal.
This shows 2 different ways to build a Stochastics 80/20 crossover signal.
June 13, 2019
June 6, 2019
This example shows how to find long wicks on indicators that visually display as a candlestick on the chart. Specifically we use NinjaTrader’s Order Flow Cumulative Delta indicator to find topping tails and bottoming tails, on a minute chart.
May 30, 2019
This example uses the Sim22 Heiken Ashi indicator from Futures.io. The first part demonstrates how to detect the H/A bar direction. The second part shows how to identify reversal points, plus wait for at least a 2 tick movement away from the reversal point price before the reversal signal occurs.
These signals are composed of two sets of rules. The first set is, a signal occurs in the direct of the CCI crossing the zero line, if the closing price is on the same side of the EMA 120. I.e. When the CCI crosses above the zero line, the close must be above the EMA 120. The second set is as follows. For a long signal the CCI must be above 100. Then cross below 100, but stay above zero. Then cross above 100 again, and the close must be above the EMA 120. Reverse the conditions for a short signal.
May 16, 2019
This example builds a simple crossover signal in the direction of the trend. Price must first cross an EMA 9 in the opposite direction of the trend, and then a signal is given when price crosses the EMA 9 again in the direction of the trend. The question started off using the Swing indicator to determine the trend direction, but it was discovered that the delay in Swing indicator was to slow for changing the trend direction. Thus, the slope of the SMA 30 was used instead.
May 2, 2019
This topics starts by showing how to setup multiple instruments in BloodHound. Followed by using two Slope solvers to illustrate a simple example of the logic. Next, the BloodHound template is setup in the Market Analyzer, with a brief explanation of using BloodHound in the M/A and some tips.
April 18, 2019
Allowing Signals 5 Bars After 5pm or after 1am, Whichever Comes First
This system looks for a simple price action to cross below the amaPivotDaily S1 or above the R1 lines, between 5pm to Noon the next day. A long signal set up is as follows. There must be a minimum of 2 consecutive bars who’s Close price must close above R1, and the signal occurs when a whole bar closes completely above R1. The last part can take more than 2 bars. The time period in which a signal is allowed is as follows. The time period starts at 5pm and ends at noon the next day. A signal is allowed to fire when the first condition occurs. The 5th bar that prints after 5pm. Or, the bar that prints after 1am. Only 1 long signal and 1 long signal is permitted per day.
April 4, 2019
This topic uses the Support/Resistance solver to generate short only signals when price is near the lower 3 S/R lines of a pivot indicator. Whether price is above or below the S/R line, only a short signal is generated. Long signals are generated when price is near the upper 2 S/R lines.
March 28, 2019
Price Touching the Band, Then Pulls Back to the Mean Signal
This system looks for price to touch the outer bands of an indicator. Then, pullback to the midline/mean, and bounce off of the midline. In this example the Keltner channels are used for the outer bands.
March 21, 2019
How can multiple threshold levels/values be tested/analyzed for various indicators (such as the MACD)? I.e. What is a good way to test different threshold values to find the right one? In this demonstration the MACD (5, 20, 30), and threshold values of 2.5, 5, and 10 are used to explain how one might go about comparing the results of all three threshold values in a nearly seamless process.
March 7, 2019
This system looks for the Close of the bar to go below the Order Flow VWAP 2nd lower band for a long setup or above the 2nd upper band for a short setup. Also, the Stochastics must be below 30 for a long, or above 70 for a short. When both indicator conditions occur together a signal is generated.
February 28, 2019
This system looks for a breakout of the Bollinger bands and the amaTradersDynamicIndex (TDI) indicator. Another lesson taught by this system is synchronizing two Unirenko charts. On a higher timeframe (HTF) renko chart a couple of conditions are looked for. 1) 1 to 5 renko bars must break below the lower Bollinger band, and stay below the band. If more than 5 bars in a row breakout of the band then this condition is invalid. 2) The TDI Price Line must also break below its lower bollinger band. 3) The setup is complete when a reversal bar occurs before #1 is invalidated. The same conditions must occur on the LTF renko chart with a few exceptions. Any number of bars can breakout of the bollinger for rule #1. The LTF reversal bar may close before the HTF reversal bar closes and that is acceptable as long as it only has 1 tick remaining to close the reversal bar. Because the HTF reversal bar does not have to finish closing this system must be run with Calculate = On Price Change.
February 7, 2019
This logic looks for the Closing price of an up bar to equal the Open price of a following down bar. First bar is up and second bar is down. The tops of those bars must be the same price. And, there must not be any upper wicks on the tops of the bars.
This system uses 3 higher time-frames, the Darvas, Lin.Reg, Stochastics, and EMA, indicators to find price bounces off of the Darvas lines. The 10 brick, 15 brick, and 25 brick renko charts must be moving in the same direction. Next, find price bouncing off a Darvas line. At the same time price must cross the Lin.Reg. indicator, and the Lin.Reg. must be sloping in the directions of the bounce. The Stochastics K line must be crossing above the 20 level, for a long, or crossing below the 80 level for a short. The EMA must not be flat/range bound. This lesson will teach how to adjust the solvers and use Lookback nodes to help match all these indicators/conditions together, because they do not all occur together on the same bar. They typically occur a bar or two apart from each other.
January 31, 2019
This system has 3 major components/conditions. First, is the market trend direction. Second, is wait for a pullback in price. Third, is wait for CCI, MACD, and RSI to align with trend. The system uses a hybrid renko chart.
Market Trend: This is determined by price crossing above the swing high or below the swing low. Also, when a higher low is made or a lower high. When one of these swing patterns occur the trend is established.
Price Pullback: This is simply looking for reversal renko bars. Once a bar reverses in the direction of the trend, that creates the setup condition. The next step is for the indicator filters to all align with the trend.
Indicator Filters: The CCI must be greater than 50 for a long signal, or less than -50 for a short. The MACD Diff plot must be above the zero line for longs, or below for shorts. The RSI must be above 30 for longs, or below 70 for shorts. A signal occurs once all 3 indicators meet their requirements.
This shows how to use the ADXVMA neutral/flat trend state to create an Exit signal on the first bar of a neutral trend.
January 24, 2019
How to use the ADXVMA to block signals when the indicator is in a neutral trend/state. This example uses the amaADXVMA » DataSeries Trend, in a Threshold solver, to identify when the indicator is in a long or short trend, and output both long and short outputs, but no output when the ADXVMA is neutral.
How to generate a signal from the ADXVMA indicator when a trend starts. This shows how to use the amaADXVMA » DataSeries Trend, in a Threshold solver, to identify when the indicator is in a long or short trend. Then we add boolean logic, instead of the Signal Blocker node, that only allows the first bar of the trend to show a signal.
January 17, 2019
This system finds bars that straddle a swing point line and then reverses on the next bar. I.E. A short signal is produced when a renko bar closes above a swing high, but the bar open is still below that swing high, and then the next bar is a reversal down bar. The opposite condition create a long signal.
This shows how to setup a solver to filter out/block signals or conditions when any price breaks outside the Bollinger bands. I.E When the entire bar is inside the Bollinger bands, any signal can pass through, but if any part of the bar breaks outside of the bands then the signal is blocked.
This demonstrates how to use the Signal Counter and the LookBack function nodes to find when a minimum number of bars are above or below an SMA 30. The Signal Counter and LookBack nodes can be used to detect when a condition has occurred X number of bars.
January 10, 2019
How to nest an indicator into another indicator. I.E. Change the Input Series of an indicator to another indicator.. In this example, we demonstrate how to change the Input Series (nesting) of an indicator within a solver. The EMA 20 is used to smooth the Lin. Reg. indicator.
Building a simple signal when the closing price moves 8 ticks away from the EMA 55. Every time price moves to within 8 ticks of the EMA and then moves 8 ticks away from the EMA a signal is generated. This signal will be used in the next BlackBird workshop.
0:00:33 - How to produce signals when renko bars have a wick size of 6 ticks or more, and after a trend pullback that does not break a moving average by more than 1 tick. For a long signal, the trend pullback signal requires the pullback bars to stay above the SMA 20, but can break below the SMA by 1 tick.
0:43:51 - Building a Regression Channel signals in the direction of the channels slope/angle. The signal direction is filtered by the angle of the channel. I.e. When the channel is sloping up only long signals occur. For a long signal, the low price must be below the lower channel line, and for a short signal the high price must be above the upper channel. The amaRegressionChannel indicator(from LizardIndicators.com) is required, because the NinjaTrader Reg. Channel indicator does not calculate the channel slope.
1:14:22 - How to fine tune the Slope solver’s Max. & Min. Slope settings to find the right indicator angle you want. In this example the Sim22_MacdBBGaplessV4 upper and lower band plots are used to demonstrate setting the Max. & Min. Slope settings.
00:00 - How to add a 2 bar continuation requirement to a with-trend renko reversal bar signal. The ‘with trend renko reversal bar’ is defined as price being above the EMA 55 for a long trend, and a reversal up bar trigger a long signal. Reverse the conditions for a short trend. This topic shows how to take that basic signal and add a secondary requirement/filter. Wait until 2 more continuation bars form, immediately after the reversal bar, and then the signal occurs.
18:08 - How to add a 2 counter trend bar requirement to a with-trend renko reversal bar signal. The ‘with trend renko reversal bar’ is defined as price being above the EMA 55 for a long trend, and a reversal up bar trigger a long signal. Reverse the conditions for a short trend. This topic shows how to take that basic signal and add a secondary requirement/filter. There must be a minimum of 2 counter trend bars immediately before the reversal bar. Otherwise, the signal is canceled.
00:00 - Identifying an over-extended price move with minor pullbacks in price allowed, but to large of a pullback resets the price move. When an over extended price move is detected, then block/prevent signals in that direction.
21:29 - How to detect when the High of the bar is within a few ticks or above the upper band of the Bollinger calculating on the High price. And, when the Low of the bar is within a few ticks or lower than the lower band of the Bollinger calculating on the Low price.
11/01/2018 Breakout Above a “Signal Bar”
00:00 - Building a Linear Regression, DM, and Chandelier Signal Bar breakout system A long Signal Bar is identified when the bar direction is up. The LinReg indicator is sloping up, and the DM +DI plot is sloping up. Also, the Close price must be above amaChandelier indicator. When all those conditions line up on the same bar a Signal Bar is formed. The final signal occurs when price closes above the high of the Signal Bar. The amaChandelier indicator is available from LizardIndicators.com.
59:42 - How to block signals when the bar is touching the Donchian channel. e.g. When the bar is touching the upper channel plot block long signals. The opposite for blocking short signals.
10/18/2018 Designing a Scaling-In Signal System (raw recording)
1) This example builds a 3 signal system. The first signal is the main/initial entry signal, and the other 2 signals are for scaling in more contracts with BlackBird. This teaches how different indicator conditions can be used to create secondary or scale-in signals only after the primary signal has occurred, and the primary signal usually has a more complex set of indicator rules. This system uses the fpgMultiREMAExtended custom indicator, which can be downloaded from Futures.io, and the WisemanAlligator and WisemanAwsomeOscillator indicators. The primary signal has a more rigid set of rules. While the secondary signals, that requires a pull-back in trend, has an easier/less restrictive set of conditions. Which is why the secondary signals only occur after a primary signal. The secondary signals are limited to 2 signals per primary signal.
10/11/2018 EMA60 Pullback Signal & Determine When CD Volume and Bar Direction Sync (raw recording)
1) Building an EMA 60 pullback signal with a bar in the direction of the trend. This example starts by taking an existing BloodHound template, from a previous workshop, that uses the T3 moving average. The T3 is replaced with an EMA 60 period MA, and some other adjustments are made to the solvers as well.
2) How to determine when the cumulative delta volume (positive or negative) and the bar direction are in sync. This system uses the Order Flow+ Cumulative Delta indicator, a Bar Direction solver, and a AND node. Also, logic to identify when the two components are out of sync is included.
09/20/2018 Stochastics Pullback with EMA Filter
0:00 - Building a Stochastics over-sold/over-bought with EMA10 above/belowEMA20 confirmed with a bar in the direction of the trend. This system has a setup condition and a signal bar. A long setup condition looks for the Stochastics to dip below 20 while the EMA10 is above the EMA20. Then wait for the signal bar. The signal bar is the first up bar, with the EMA10 above the EMA20, either during the setup phase or a few bars afterwards.
Also, a simple EMA10 and EMA20 crossover Exit signal is added.
0:00 - How to detect a break above or break below a “Setup” bar’s high or low prices. The term “Setup” bar usually is used to refer to a specific bar on which a special setup conditions occurs. E.g. The bar on which a MA crossover occurs, or (in this example) the pullback bar that touches a MA (moving average). When a long Setup bar occurs, any of the next 5 bars that print 1 tick higher that the high of the Setup bar produces a long signal. Or, when a short Setup bar occurs, any of the next 5 bars that print 1 tick lower that the low price of the Setup bar produces a short signal. The first half of this topic shows how to create the Setup bar’s condition. A pullback bar to an EMA 20. The later half shows how to build the logic for detecting the break above/below the Setup bar’s high/low price.
00:00 - How to block signals when price moves X ticks away from a MA. This example blocks signals when the Close price is more than 10 ticks away from an EMA 6. Also shown, is how to block signals using the High and Low prices, instead of the Close.
21:52 - Can BloodHound track the price of a bars that a crossover occurs on, or when other special conditions occur? No, that is what other indicators are designed to do. This topic explains what BloodHound can and can not do in regards to tracking prices.
28:37 - How to build an Exit signal when the entire bar is below a MA and 2 higher high bars occur to exit a long position. The opposite conditions for a short Exit signal. At the end of this topic the Exit signal conditions are simplified so that only 2 bars, in a row, above or below the MA are needed.
0:00:00 - Building an EMA trend with two HH/LL price confirmations and a fast stochastics pullback entry. This system looks for a fast EMA above a slow EMA for the trend direction. Then the bar high must move higher that the previous bar high. That must occur two time, and then the trend direction is confirmed as a long trend. The opposite conditions for a short trend. The Fast Stochastics indicator is used for a pullback entry signal. The Fast Stochastics must touch or move below the 25 level for a long pullback, and touch or exceed 75 for a pullback during a short trend..
1:00:46 - A renko pullback system with a narrow pullback distance/range. An SMA 50 is used to determine the trend directions. A faster SMA 14 is used to set the pullback distance. The Close price of the renko bar must close at or below the SMA 14, but must not exceed the SMA 14 by 5 ticks or more. If the pullback bars close more than 5 ticks below the SMA 14 then the pullback is disqualified. The signal occurs if the next bar is an up (reversal) bar. And, the reversal bar must touch the SMA 14.
1:28:08 - How to generate signals on renko bars with wicks/tails 3 ticks or longer.
08/16/2018 A Simple Bollinger Breakout Signal (raw unedited recording)
1) The OpenRange (OR) breakout system from last week (8/9/18) is modified to allow only 5 re-touch signals per direction. If prices breaks the OR to the up side, only 5 long re-touch signals can occur. Any other long re-touch signals are ignored/blocked. Afterwards, if price breaks the OR to the down side, only 5 short re-touch signals can occur. All other short re-touch signals are ignored/blocked.
2) 2 bar Bollinger band breakout logic. This logic generates a long signal when; 1) The bar low is below the Bollinger middle line. 2) The next bar’s high breaks above the Bollinger upper band. The opposite conditions for short signals.
08/09/2018 OpenRange Breakout & Identifying BetterVolume Volume Patterns (raw unedited recording)
1) An OpenRange (OR) breakout system that generates multiple touch signals, and reverses direction when price crosses through to the other side of the OR. The Close of the bar must close at least 1 tick beyond the high or low of the range to qualify as a breakout of the range or to reverse the OR breakout direction. Price is considered to retouch the OR when;
A) The Low wick has touched or penetrated through the OR high, and the Close of the bar must close at least 1 tick beyond the OR high for a long signal.
B) The High wick has touched or penetrated through the OR low, and the Close of the bar must close at least 1 tick beyond the OR low for a short signal.
2) A price snap back/over extended move back to the SMA. This system looks for extreme price moves in the opposite direction of the SMA’s slope. For a long signal, the SMA 50 must be sloping up or flat, and the Low of the bar must be 50 ticks or more below the SMA. For a short signal, the SMA 50 must be sloping down or flat, and the High of the bar must be 50 ticks or more above the SMA.
3) Various examples of comparing the MACD plots to either the zero line or 1/-1 level, and comparing the MACD plots to themselves such as the MACD line to the Diff/Histogram line.
4) How to identify BetterVolume patterns on multiple timeframes. This example finds Breakout volume bars followed by a Churn bar. That pattern is identified on a 90 Second chart, and then looks for the same pattern to occur on the 3 Minute chart, within 2 90 Second bars (a 3 minute period).
0:00:00 - How to build a tailless Heiken Ashi and EMA 120 system. The setup rules are simple; 1) The EMA 120 must be sloping in the direction of the signal. 2) The Heikin Ashi bar must be pointed in the direction of the setup. 3) The H/A bar must Not have a tail (no low wick for longs, or high wick for shorts). All condition must occur on the same bar. Exit when the H/A bar reverses direction of the setup.
0:18:39 - How to find an Engulfing bar body that engulfs the previous bars high and low length. And, the next bar (called the confirmation bar) must surpass a bullish engulfing bars high price, or surpass a bearish engulfing bars low price.
1:03:00 - How to identify when a slower ADXVMA and a faster ADXVMA indicator are out of sync and in-sync. Out-of-sync is one ADXVMA showing an up trend and the other ADVMA is not, or one ADXVMA showing a down trend and the other ADVMA is not. In-sync is when both are showing an up trend together, or both are showing a down trend.
00:00 - Various ways to filter signals whether price is inside or outside of the Bollinger Bands. Two sets of filters are created. The first set uses the Closing price of the bar. Signals are allowed when the Close is inside the bands, or outside the bands. The second set looks at the entire bar. Signals are allowed when the entire bar is inside the bands, or completely outside the bands.
00:00 - This topic focuses on identifying an oscillator as oversold or overbought for X number of bars before it crosses outside the oversold/overbought levels. This example uses the Ultimate Oscillator indicator to find 3 bars of the last 5 bars are below 30 or above 70. If 3 bars are found then generate a signal when the oscillator crosses above 30 or below 70.
22:54 - This is an example of building a multi-timeframe (MTF) system that uses 3 MACDs. The three timeframes are; a Daily chart, 89 Range chart, and 4 brick ProRenko chart. A signal occurs when the bar direction of all 3 timeframes are the same (all up or all down). And, all 3 MACDs must be sloping in the same direction as the bars. The signal ends when 2 of the MACDs slope in the opposite direction. Note: If you do not have the ProRenko bar, it can be substituted with the UniRenko bar.
00:00 - How to modify existing trade signals so that they only occur when the direction of the signal matches the bar direction. I.E. A long signal will only occur with an up bar, and a short signal will only occur with a down bar. Two ways of filtering the signals are shown. The first simply uses a Bar Direction solver with a AND node. That allows all the matching signals to show. The second method shows how to block consecutive signal, so that only the first signal is seen and any signals immediately after are blocked.
18:35 - A demonstration of various solvers to use with a BB MACD type of indicator. The anaMACDBBLines indicator is used in this example. It can be downloaded from LizardTrader.com. A Comparison solver is used to detect when the bands are wider than a certain distance, and to detect when the bands are narrow or close together. A Crossover solver is used to detect then the MACD line crosses the Bollinger bands. And, another Comparison solver is used to detect when the MACD is above or below the bands.
05/10/2018 Detecting Crossbacks
0:00 - How to build a crossback detection, as a real-time bar is building. An example of a crossback is when price starts above a MA (moving average). Price cross below that MA (this is a crossover). Then if price crosses back over and above the MA, that is the crossback. Its price dipping below the MA and them moves/crosses back up. And, vise versa for a short crossback. This can only be detected in real-time when Calculate on Bar Close = False.
0:00 - anaOpenRange modification for Stop entry orders.
04/26/2018 anaOpenRange Breakout Signal
0:00 - Build an Opening Range Breakout signal using the anaOpenRange indicator. In this example we build the basic price breakout signal, which generates signals whenever price crosses outside the opening range for the entire day. Next, a filter is applied so that only the first signal of the day is shown. The rest of the signals are blocked using the Signal Blocker function node.
0:00 - How to detect when 2 different anaSuperTrendU11 indicators are on the same side of price or same trend direction. This example uses 2 anaSuperTrend indicators with different Offset Multiplier settings, which places them at different offsets from price. This condition signal will be used in the next BlackBird workshop for a trailing stop-loss trigger.
0:00:23 - Trend pullback signal with a pullback distance requirement below the MA. The MA used is the T3 indicator. This pullback system has the following requirements for a long signal;
a) The MA must always be sloping up. A downward slope cancels the signal.
b) The trend move starts with 4 continuous bars must be above the MA.
c) Price must cross below the MA.
d) The closing price of the signal bar (a reversal up bar) must not exceed 3 ticks above the MA. The bar close can be any distance below the MA.
Reverse the conditions for a short setup.
0:58:45 - How to identify 2 renko bars in a row with wicks.
1:04:49 - How to identify the first wick touch of the SuperTrend line. This system uses the anaSuperTrend indicator. After the indicator changes trend direction, the first time price touches the SuperTrend line that bar is marked with a signal. The logic uses the Toggle node to isolate the first touch, and block any other touches per trend direction.
1:25:13 - Using the Signal Counter node to count renko reversal bars. This system first identifies an overbought/oversold Stochastics condition. Then identifies the second reversal bar to product a counter trend/reversal signal.
1:47:21 - How to identify confluence of 3 moving averages with the bar direction. The system uses the EMA 5 & 7, and SMA 50 indicators. For a long trend, the EMA 5 must be above the EMA 7, and the EMA 7 must be above the SMA 50. Then the bar direction must be up.
00:00 - This topic combines new price highs/lows, an overbought/oversold RSI, and an RSI divergence. Specifically, the following conditions are identified for a short setup.
a) The RSI must be above 80 (overbought). Long condition is below 20 (oversold).
b) Within 50 bars, price must make another new higher high.
c) The RSI must be diverging from price (an RSI divergence).
Reverse these conditions for a short setup.
00:00 - This example shows how to analyze an indicator vs price condition at a specific time of day to establish a trend for the day, and then use that trend direction to filter trade signals in that direction afterwards. The time of day is the 3am bar. The trend indicator is the anaHiLoActivatorU1 (from Lizard Trader, free download). At 3am price must be 3 ticks above or below the anaHiLoActivator. If price is not, then check the next bar and so forth. Once the trend is identified then mark all the bars the pull back and touch the anaHiLoActivator indicator line. This system uses the TimeBlock indicator to identify the 3:00am bar; the anaHiLoActivatorU1 indicator to identify trend direction and is the pull back support/resistance line.
00:00 - How to identify when a swing high and swing low expands or contracts. The definition of swing point expansion is when the swing high moves higher and the swing low moves lower. Swing point contraction is the opposite movements.
00:00 - Signal when 2 bars in a row make a new daily high or low. If two consecutive bars make a new daily high then print a signal on the second bar. Vise versa for a short signal.
12:00 - How to use a “choppy” indicator to block signals. This is a follow up to the Jan 18th, 2018 workshop. In this example when the indicator (StochasticsFast) is choppy it is used as a filter to remove/block trade signals.
28:14 - How to identify when two trend line indicators are getting close to each other. This examples uses two SMA indicators, and when they get within a few ticks of each other a signal occurs.
02/01/2018 Identify When an Indicator is Flat
00:00 - How to identify when an indicator is flat/horizontal. This example identifies when the WilliamsR indicator reaches its maximum value of zero or minimum value of -100. The Slope and Threshold solvers are used.
18:14 - This next part takes the signals from the above question and creates a signal when the WilliamsR signals end. This condition is wanted for an Exit signal.
01/25/2018 StochasticsFast 3 Signals Per Trend Example
0:00 - A StochasticsFast 3 signals per trend direction example. This system uses a UniRenko chart and the StochasticsFast indicator to generate signals on key reversal bars. Only 3 signals are generated per trend direction. The first signal occurs when a trend setup is identified. The second and third signals are trend continuation signals.
The rules for the first long signal are;
1a) The StochasticsFast moves above the 50 level.
1b) Next, the StochasticsFast makes a retracement (and price pulls back as well).
1c) With the StochasticsFast still above 50, price reverses in the direction of the trend.
The 2nd and 3rd long signals occur when;
2a) The StochasticsFast rises above 70, and must remain above 70.
2b) After a pullback in price, signal when price reverses in the direction of the trend.
The first signal can setup again after the StochasticsFast touches the 30 level. Short signals are the reverse logic of the long rules. This system uses the Signal Blocker, Toggle, Long/Short Modifier, and Lookback function nodes.
01/18/2018 How to Identify a Choppy Indicator
0:00:00 - Building a swing point price action signal. For a long signal, after a higher or equal swing high is made, then signal on a higher swing low. For a short signal, after a lower or equal swing low is made, then signal on a lower swing high.
1:24:05 - How to sound an audio alert every time a new bar closes/forms on the chart, with the racing strips turned off so signals are not seen on the chart.
1:31:12 - A general way to detects when an indicator becomes choppy (or lack of smoothness). This example uses the Stochastic oscillator.
01/04/2018 Pullback Signal to Lowest Low of Last 5 Bar
0:00:00 - How to build a pullback signal that looks for price to pullback to the lowest low of the last 5 bars, for a long signal, when the EMA 20 is sloping up. When the EMA is sloping down look for price to pullback the highest high of the last 5 bars. The EMA acts as a simple trend direction filter. The Donnchian Channel tracts the highest high and lowest low of the last 5 bars. Several variances are made of this system. This system is demonstrated in Raven, and also in the next days BlackBird workshop.
1:04:04 - An explanation of why adjusting the Max Slope and Min Slope in the Slope solver, using the MACD, does not change the solvers output. A customer wanted to get the direction of the MACD by using the Slope solver, and also wanted to remove flat areas in the MACD. But, was not seeing any flat spots removed when adjusting the Max & Min Slope settings. This explains why that may occur when using indicators such as the MACD that have their own Y-axis scaling. Other common indicators are the Stochastics and ADX. These indicators run in their own sub-panel, and have their own unique Y-axis values.
11/09/2017 Gap Ups Making New Highs
00:00 - A quick demonstration using the Support/Resistance solver to block long signals when the market is below and near resistance, and block short signals when the market is above and near support.
19:29 - How to detect a gap up in price that makes a new high, and the bar closes down. A Comparison solver is used to detect gaps in price. The slope of the Donchian Channel indicator is used to detect if a new high is made.
00:00 - This renko chart system generates counter-trend signals when price crosses the previous swing point and then reverses direction. A long signal occurs when price crosses the previous swing low, two more down bars must occur, then a reversal bar up and one more up bar must occur.
26:39 - How to detect when volume exceeds 1000 using the Threshold solver.
40:14 - A review of using solver weight sliders with the Additive node to add various solver outputs together.
54:32 - How to confirm a moving average has been sloping up or down for a minimum of 3 bars. This can help remove erratic slope detection when a MA is flat-ish and bouncing up and down every other bar.
0:00 - How to block a solver’s output when an indicator outputs a specific value. A group of Threshold solvers are to be blocked when the custom indicator that is used in those Threshold solvers outputs a value of zero.
0:00:00 - How to detect a 50% volume increase above the 20 period volume MA (VolMA). This finds volume spikes above the averaged volume. We use Chameleon to apply a 50% factor to the VolMA indicator, which then allows a Comparison solver to detect the volume spikes.
0:17:04 - How to detect Heiken Ashi(HA) bars in the opposite direction of a trend marking moving average(MA). In this example we use the anaSuperTrend as the trending MA. When the MA is trending up, all down HA bars are marked.
0:35:45 - This is a follow up to the previous topic. This example marks the HA reversal bar in the direction of the MA. When the MA is trending up, after a down HA bar, the reversal up HA bar is marked with a long signal, and vise-versa for a down trend.
0:47:35 - How to detect if the range between the low and high prices, of the last 28 bars, is less than 20 ticks/pips. At first we detect if the range is greater than 20 ticks, and then later on create another Comparison solver to detect if the range is less than 20 ticks. As an added option, we use the TimeBlock indicator to isolate the signal to a specific time of day (7:00am).
1:17:40 - Why some reversal bars may not be detected by the Inflection solver set to analyse price.
00:00 - How to test when the Ask or Bid touches the anaSuperTrend. The signal will be used as an Exit signal to close the trade for a profit. Instead of using a profit target, the trader wants to exit the trade at market as soon as the Ask or Bid touches the anaSuperTrend line. This Exit signal will be used in the next BlackBird workshop.
22:43 - Using a market condition or trend/chop detection type of indicator as a filter to block or allow trade signals through. In this question the trader has an indicator that outputs a positive value when market conditions are unfavorable, thus signals are to be blocked for an hour, and then allowed afterwards until the indicator changes states.. The indicator outputs a negative value when market conditions are favorable, thus signals are allowed through for an hour, and then blocked afterwards until the indicator changes states.
00:00 - How to build a signal on the 3rd bar after a reversal bar on a renko chart. This question starts off being asked, how to create a signal on the 3rd bar after a crossover, but then later is changed to using a reversal bar. The signal will be in the direction of the 3rd bar, regardless of which direction the reversal bar is. E.G. A reversal bar up may start the signal, but the next bar may reverse down and then if the next bar is also down that will generate a short signal, even though a reversal up bar started the process.
35:06 - When Raven receives a signal from BloodHound, is the signal received on the signal bar or is the signal received on the next bar? In this topic we address the exact timing of how NinjaTrader executes strategy trade signals and orders. Also discussed, is how ‘Calculate on bar Close’ affects strategies.
40:16 - This is a continuation of item #2 above. How to have Raven’s Exit Logic operate intra-bar (in real-time), but have the Entry Logic (entry signals) wait for the bar to close. I.E. The Exit Logic will run with Calculate on bar Close = False, but the Entry Logic will run as if Calculate on bar Close = True. The trick to having Raven run this way is to use a Lookback node in the BloodHound logic.
8/10/2017 Price Crossing the VWAP Example
0:00 - This is simple signal example built from price crossing the VWAP indicator. A long signal occurs when price crosses above the VWAP, and vise versa for a short signal. This was built for the following day’s BlackBird workshop.
8/03/2017 Market Replay Best Practices
00:00 - Best practices when using Market Replay.
21:18 - How to use the NYSE Tick, or any other instrument, as a signal filter. In this example we show how to setup the Threshold solver with a AND node to filter signals. Only long signals will show when the NYSE Tick is above 0, and only short signals when the Tick is below 0.
0:00:00 - How to incorporate discretionary price levels (such as custom pivot levels) into your BloodHound system. This examples builds the following rules; #1 Two bars in a row must close above a moving average (SMA 10). #1a, Rule #1 must happen during the market session. #2 When price is above the discretionary price generate a long signal.
Reverse #1 and #2 for a short signal.
6/29/2017 Detecting RSI Hidden Divergence
0:00:00 - In this workshop we build an RSI Hidden Divergence system. Two different methods are used that produce slightly different result and different drawbacks. The first system uses the SiSwingsHighsLows indicator to monitor price swing points. Both systems use the DonchianChannel indicator to monitor the RSI indicator for swing points. The second RSI Hidden Divergence system uses the DonchianChannel to monitor price swing points.
0:00:00 - Looking for a rare Heiken Ashi (HA) bar condition. In a HA up trend, the current bar and the previous bar must both be up bars (two up bars in a row). The current bar’s Close price must be below the previous bar’s Open price. IE, the current up bar is below the previous up bar.
0:00:00 - CCI Exit signals. In this example we demonstrate how to build 2 exit signals per trade direction. The exit rules are as follows. For a Long position; Exit when the CCI crosses below +100. Or, if the CCI doesn't happen to reach +100, as a failsafe, the trade is exited when the CCI crosses below -100. And vice versa for shorts. Also in this clip, the entry signals are built to help explain the whole customer question.
A follow up to the above exit signals. How to clean up the “unused/extra” exit signals. The exit signal logic, from above, created some extra exit signals in certain situations. They are “extra” exit signals, because there would not be a position to exit from. Which is ok since they will have no effect, but looks a little cluttered on the chart.
0:42:39 - Can BloodHound be used inside a different instance of BloodHound? In this clip, we show to accomplish this, and discuss the pros and cons of running BloodHound inside of BloodHound.
0:51:15 - How to generate a long signal when the Open price is above the EMA 10 and within 4 ticks of it. Vise versa for a short signal.
1:01:06 - A quick demo on how to get signals on bar close, instead of intra bar, when BloodHound has to be run with ‘Calculate on Bar Close’ (CoBC) is false. Some indicators (IE volume profile, volume footprint type indicator) have to run with CoBC = false, and therefore BloodHound must be run with CoBC = false. Below are some other good clips on this topic.
6/01/2017 Using BloodHound’s Fuzzy Logic Output
0:00 - Learning how to make the most of BloodHould’s “fuzzy logic” using indicators like the Stochastics indicator.
0:00 - How to build crossover signals from the Aroon indicator. In this example we use the Aroon 100 period on a daily chart with the Crossover solver to generate the signals. We then put this into a Market Analyzer.
0:00 - How to allow the first two signals, in the same direction, and block any additional signals afterwards in the same direction. Always allowing the first two signals in the opposite direction to show. In this demonstration we use the Signal Counter and Inverter nodes with a AND node to accomplish this.
5/04/2017 Workshop recording failed
00:00 - How to build a reset signal, for any Function node, when Renko bars form a long wick. The simplest solution to identify renko bar wicks is to use the Bar Length solver. This example also includes a bar reversal as part of the reset signal to a Signal Blocker node.
14:17 - When Raven is enabled/running, is it safe to modify the BloodHound logic while Raven is running it? The simple answer is no, but this is a more thorough answer.
00:00 - How to detect the bar direction for Range bar dojis. In this example we show how to setup the Comparison solver to get the bar direction for dojis. In the next software update the Bar Direction solver will be able to do this, instead of having to use the Comparison solver.
11:58 - An overview of solver Output values and BloodHound’s output values to the chart. Every solver has an Output section, and this topic focuses on what values to use in the solver’s Output sections.
29:06 - How to build a doji bar trigger that signals in the direction of a moving average. When range bar dojis are detected the signal direction is controlled by the direction of a MA.
35:12 - Next, we demonstrate placing the above signal in Raven.
40:56 - This example demonstrates, in theory, how to setup the logic that will automatically select/use different solvers depending on the chart’s bar type.
4/13/2017 Range Bar Bounce Off an EMA
0:00 - How to build an EMA bounce signal for Range bars. This bounce signal consists of the following conditions; #1 A minimum of 2 bars retracing back to the EMA, and must not touch the EMA. #2 Wait for a reversal bar to confirm the bounce. The reversal bar may touch the EMA.
00:00 - Building an Exit signal when the Moving Average slope direction goes against the trade for 2 bars. If in a long trade, when the MA slopes down for to 2 bars. Plus, the angle must keep increasing. If the slope flattens by any amount on the second bar the exit condition is not met. This example uses the Change In Slope solver, and the Slope solver. The Slope solver is used to set a minimum required angle of the MA to qualify as an exit condition, so that exit signals do not occur to early.
53:43 - Why does changing a solver on one Logic template also change a solver on a different Logic template?
0:00 - How to determine when the HMA reverses direction on the 5 minute chart, when using BloodHound on a Renko chart.
5:51 - Discussion on some lesser-known features of the BloodHound interface.
0:00 - Is it possible to display on the chart the times a Time Session solver is setup to allow signals? Yes, this can be done by modifying the BloodHound logic, or a 3rd party indicator.
0:00:10 - Various ways that a bar time span or bar timer indicator can be used in BloodHound. In these examples we use the mahBarET indicator, which can be found on Futures.io. BloodHound is able to identify bars with time durations greater than X seconds or less than X seconds. This indicator includes an average time duration calculation, so BloodHound can identify when the bar times are increasing in duration or decreasing in duration. mahBarET can be found at… https://futures.io/local_links_search.php?action=show&userid=7033&sort=d
0:31:22 - Can Raven be used for Sim trading? Yes.
0:33:00 - This section discusses a few topics on the Slope solver. How to identify when an indicator has been sloping up for X number of bars. How to identify when an indicator is flat (no slope).
0:44:38 - How to identify when Open price of a bar is 2 ticks away from the EMA 20, and within 10 ticks of the EMA.
0:57:19 - An overview of how the Time Session solver can color the chart and what color changes can be made. And, the SiTimeBlock indicator can be used to color the chart during a custom set time of day.
1:07:43 - How to have a Higher Time-Frame bar direction fill in when the waiting for the 3rd bar in the same direction on the Lower Time-Frame. This example uses HTF and LTF bar direction to determine the market direction. The LTF must have 3 bars in the same direction before the trend can be identified as up or down. During the first and second LTF bar, the HTF bar direction is used for the trend direction.
00:00 - Time Session solver tip. This topic discusses the connection between BloodHound’s Time solver and NinjaTrader’s Session Manager, and how editing one of NinjaTrader’s Session templates, through the Time solver, may affect the chart.
11:52 - How to detect full body candles. A full body candle/bar is a bar with no wicks
35:47 - How to generate a signal at a specific time. In this example we show how to general a signal at 9:32am using the SiTimeBlock indicator.
55:13 - How to nest price data or indicator data into another indicator within BloodHound. On a NinjaTrader chart, the way to display the EMA of the High price is to change the EMA’s Input Series to the High price. This example show how to do that in BloodHound by using the SiChameleon indicator.
1/27 - 2/17/2017 No Workshop due to illness
1/20/2017 Two With-Trend Swing Point Trend Filters
00:00 - How to use the SiSwings and SiSwingsHighsLows indicators to filter signals in the directions of price action. We first look at the SiSwings OverallTrend output and discover how it calculates a swing point trend change.
19:29 - Next, we continue the above topic by using the SiSwingsHighsLows indicator to build a faster swing point trend filter. Any higher swing point (HL or HH) will begin a long trend, and any lower swing point (LH or LL) will begin a short trend.
41:23 - A simple example of using the Stochastics indicator in the Crossover solver.
0:00:00 - How to block/prevent signals when price pushes the Donchian Channel up or down. What this effectively does is signals can only occur when price is range bound between the channels. This example demonstrates how to take a solver’s output, that identifies an indicator condition, and use that output to prevent (trade) signals.
0:15:39 - How to reset/turn off the Signals Extender when price pushes the Donchian Channel up or down. This is an extension of the previous topic
0:21:31 - How to switch from Setup mode to Real-time mode.
0:28:24 - How to use multiple logic templates to quickly change indicator settings/periods in the BloodHound logic. This example uses a simple condition that identifies whether price is above or below an EMA. Different EMA periods are used throughout the day, and during a trade, so a quick way is needed to change the EMA period in the BloodHound logic. Also, the ability to quickly add or remove a MACD filter is needed as well.
1:12:57 - How to use the Threshold solver to identify when the ATR is inside a specific range (eg in between 0.8 to 1.4)
0:00:00 - A very quick explaination of the Ratio node.
0:08:05 - A very quick explaination of the Inflection solver.
0:16:09 - We build a price bounce signal using the Support Resistance solver (instead of the Comparison solver). The example detects price bouncing off of an EMA 55 moving average (MA). It uses a Comparison solver to verify price has been trending for enough bars to filter out price consolidation around the MA. the Support Resistance solver detects when price is close enough to the MA for a possible bounce. An Inflection solver is used to confirm the price bounce.
1:09:21 - A follow up discussion of how the above price bounce logic can be modified for use in a fibonacci retracement signal.
00:00 - How to build a bar direction solver that works for Range or Renko bar doji. The Bar Direction solver requires a bar body to determine a bar direction. Range bars will quite often have up or down dojis, and this topic will demonstrate how to setup a Comparison solver that will detect bar direction for these dojis.
08:17 - How to generate a signal on the bar after a long series of signals end. E.G. If you have a group of solver that outputs a continuous signal, on the first bar the signal has ended is when this new signal occurs.
15:32 - Example system of price crossing over the GMMA indicator. This example detects if the GMMA indicator is crossed up for a long trend, or crossed down for a short trend. Signals can only occur in that trend direction. The signal occurs when price crosses the fastest moving GMMA line, in the direction of the GMMA trend.
30:14 - Detecting price action trend direction using the Swing indicator. When price breaks the swing high or low a trend direction is established. When a lower high forms during a long trend, or higher low forms during a short trend, the trend ends.
00:00 - How to see a Higher Time-frame condition on a Lower Time-frame chart. In this simple example of using multiple time-frames we show how to detect if price is above or below the EMA 50 on a HTF chart, and display it on the LTF chart.
12:03 - This is a specific lesson on using the Sliders to increase a solver’s output value. The Sliders modify the output value of any node, which is only necessary when using BloodHound’s fuzzy logic capability. In this lesson we demonstrate how to adjust a solver’s output, connected to a AND node with other solvers, so that when this solver’s output reaches 0.65 (instead of the default 0.8) a signal is generated from the AND node.
00:00 - Three steps to take before using Raven (and BlackBird) in the Strategy Analyzer.
08:44 - An overview of BloodHound’s file saving behavior.
11:30 - An example Renko bar pull-back signals for discretionary use in Raven. This example shows one way to create a pull-back filter by counting the number of pull-back bars. If the number of pull-back bars exceeds the number then the signal is blocked. Lastly, we load the system into Raven to demonstrate using Raven in a discretionary way.
40:27 - Detecting consolidation by using the EMA & ADX indicators. This logic looks for a flat EMA and the ADX below 25 at the same time to signal consolidation.
52:09 - How to generate a signal when price crosses over a moving average. This uses a Crossover solver.
54:11 - How to block an immediate reversal signal. E.G. If a long signal occurs, then on the next bar a short signal occurs, how can the short signal be blocked, because a long signal occurred on the previous bar.
11/04/2016 Indicators that Identify the HH/LL of X Bars
00:00 - Which indicators will identify the highest high/lowest low of the last 10 bars.
04:06 - How to block Exit and Entry Reversal signals between 8pm – 9:30pm.
16:26 - How to detect a bar reversal bounce off of support/resistance. This example provides a brief introduction on using the Support/Resistance, Slope, and Bar Direction solver to build a simplistic version of a bar reversal bounce logic. Previous Workshops are shown that have a more complex system that provide better signal filters.
47:28 - Two ways to build a bar reversal exit signal.
0:00:00 - Using the Inflection solver with price bars. In this example we explain a misunderstanding when using the Inflection solver with price/bars. A visual tip is demonstrated to help visualize how the Inflection solver works with price data.
0:10:23 - A brief explanation of the SiSwings > Double Top/Bottom Threshold parameter.
0:26:31 - How to determine the swing trend direction at the swing high & low points. And, how to show only the first bar of a swing trend direction change.
0:35:06 - How to detect a swing point reversal bar (HH, LL, LH, HL) with the following CandleStickPattern indicator settings; Bearish Engulfing (short), Bullish Engulfing (long), Hammer (long), and Hanging Man (short)
0:59:00 - How to Reset the Signal Blocker node at the beginning of a new day. This example demonstrates how to use the TimeBlock indicator to reset the Signal Blocker on the first bar of a new day.
1:13:02 - How to compare the Close price with the previous swing point values of the SiSwingsHighsLows Widest Tops/Bottoms plots. The SiSwingsHighsLows indicator plots the current swing point price, so how can the previous or past swing points be accessed in BloodHound.
1:21:56 - A brief explanation of the bar indexing difference between the Lookback Period vs. Displacement settings.
1:24:11 - Is there a solver that detects if the close of a bar is greater than the open of the same bar? Yes, the Bar Direction solver. And, how to detect up bars where the Close price is at the high of the bar, and a lower wick exists.
00:23 - Using both the Bar Direction and Indicator Inflection solvers together.
10:35 - Adding a bool condition to get an order to fire only once per bool condition. We use the Signal Blocker to accomplish this.
39:23 - Overview of NinjaTrader’s “Set Default” file.
0:00:20 - How to detect when signals from two different charts occur together, and limit the signals from 1am to 6am. In this example one signal is from a 5 minute ES chart and the other signal from a 450 tick YM chart. This example use two Comparison solvers and the CurrentDayOHL indicator to generate signals, to help demonstrate this concept.
0:28:10 - Can Chameleon (indicator) read a moving average from another time frame? No, Chameleon can not. This is a brief explanation of what Chameleon is designed for.
0:36:48 - What is BloodHound’s MarketAnalyzer plot for?
0:50:55 - How to build a StochasticsFast trigger, to take profits in BlackBird, when the stochastics hits 100 for long positions or hits 0 for short positions. This example shows how to build the logic in BloodHound which can then be used in BlackBird to close a profitable position.
1:00:43 - Bollinger Band reversal signal with a Stochastics filter. This example uses the Bollinger Band, price action, and a Stochastics filter to generate a reversal signal. The Long condition signal occurs when: 1) The current bar closes above or equal to the prior bar’s Close. 2) The current bar’s Low is lower than the previous bar’s Low. 3) The current bar closes below or equal to the lower Bollinger Band. 4) The Stochastic %K is less than 20. Reverse the conditions for a Short signal.
Thanks to Tony L. for providing a recording of this week’s workshop (Zac forgot to hit “record”).
Some of the recording was unusable so many questions are missing, sorry if any content is cut off.
One question is covered. It has a few conditions.
9/30/2016 How to Modify the Divergence Template to Compare 2 Instruments
9/23/2016 Bollinger Band 2nd Failed Breakout Signal System
00:29 - How to prevent Raven from taking multiple trades in the same direction. In this example we use a Slope solver which generates continuous signals. However, we want Raven to only take the first trade signal, and not the rest of the signals. This example shows two ways
20:10 - How to build a MA (moving average) crossover Exit Logic for Raven or BlackBird.
27:06 - How to detect gaps between the previous bar’s Closing price and the next bar’s Opening price.
35:43 - Next, we combine the previous gap detection with a break of the Bollinger bands. For a long signal, the High of the bar must be above the upper Bollinger band, and then a gap down.
Note: You must have the following free indicator installed from LizardTrader.com to load the BloodHound template: anaBetterVolumeOverlay.
00:28 - How to use the Threshold solver to detect 3rd party indicator signals. In this example we use the CandleStickPattern indicator.
13:46 - How to identify a bar color from an indicator that colors bars. In this example we use the anaBetterVolumeOverlay indicator that colors bars based on volume patterns. The anaBetterVolumeOverlay uses a DataSeries that outputs values 1 through 10. This lesson shows how to use the Threshold solver to identify a 1, 2, 3, 4 …etc. value.
59:29 - How to build a CCI double crossover signal.
00:29 - Two examples looking at the direction of the BOP (Balance of Power) indicator. The first example uses the Comparison solver, and the second examples uses the Slope solver to detect the BOP direction.
16:56 - How to use the inflection (reversal) of an indicator (e.g. anaSuperTrend) to filter trade signals. The customer has a custom indicator that only the Inflection solver could detect a trend change from that indicator. Typically the Comparison or Slope solvers are used for trend direction filtering, but not with this customer’s custom indicator. This examples shows how to use the Toggle node and Inflection solver instead for trend filtering,.
32:23 - A simple look at the new SiTimeBlock indicator, and how to use it in the Threshold solver.
8/26/2016 Potential Trade Failure Warning Signal
00:30 - A few Slope solver examples. A simple introduction to the Slope solver using the EMA55. Another example using the Stochastics indicator. Lastly, how to detect a flat moving average.
16:49 - An example using the Stochastics in the Inflection solver.
19:19 - Potential trade failure warning signal. This signal is an example that will be used in BlackBird Workshops. The warning signal is generated when a moving average reverses directions, against the trend, for 2 or 3 bars. The signals could just be a retracement of price, or an indication of a reversal.
00:30 - How to detect a crossover above or below an SMA 50. This is a multiple MA (moving average) system. An SMA 50 is the trend direction filter. An SMA 5 crossing over the Donchian 14 Mean line is the signal trigger. The SMA crossover of the Donchian Mean must be above the SMA 50 for a long signal, and below the SMA 50 for a short signal.
21:31 - EMA 5 above/below EMA 20 and Stochastics K above/below the D line. This system is to simply demonstrates using the Signal Blocker function node to clean up the extra signals.
0:00:30 - How to build a dual TriggerLine and EMA direction system. This system uses a fast moving TriggerLine crossover as the trade signal, and a slower moving TriggerLine as a trend direction filter, along with an EMA 200 as a second trend filter.
0:26:26 - Blocking continuous signals. A short explanation on using the Signal Blocker to clean up signals on the chart. When your BloodHound system generates a signal and the same signal continues for many bars afterwards, they can be “cleaned up” by using the Signal Blocker.
0:35:08 - How to detect when the Donchian Channel indicator is expanding or contracting, which can them be used to either allow or block trade signals. In this example we use a contracting Donchian Channel to allow trade signals, and an expanding Donchian Channel to block trade signals.
1:07:44 - Several examples of using the anaHiLoActivatorU1 indicator in three different solvers. We use the Threshold and Comparison solver to create a trend filter. Also, we use the Crossover solver to generate a trade entry signal and a trade exit signal.
1:18:57 - How to detect when the Closing price of a bar closes 1 tick above the previous bar’s High or 1 tick below the previous bar’s Low.
1:27:50 - How to build a breakout system when price breaks above the previous swing high or breaks below the previous swing low. This system has a couple of constraints. The distance between the swing high and swing low must be greater than 6 ticks and no more than 15 ticks.
8/05/2016 Miscellaneous BloodHound & Raven Topics
00:20 - A short example of using Raven to execute an order to be manually managed across two charts.
11:50 - Advice on file/template management
17:27 - Mixing different timeframes into one BH file; and how the Solvers tab calculates the output.
24:42 - Is it better to combine multiple BloodHound templates into one template/file, or is it better to run multiple instances of BH on the chart. E.G. Keep the systems separate and run an instance of BloodHound for each template.
32:42 - Miscellaneous BloodHound interface tips (description areas, override signal thresholds)
0:00:24 - Why BloodHound sometimes has an extra 1 Min timeframe added to it when the BloodHound system does not use a secondary time frame. This is a NinjaTrader issue, and this will explain what the issue is.
0:13:35 - How to build a BloodHound system that is always in the market. In other words, the system is always reversing trade positions.In this example we build a simple EMA 100 reversal system bloodhound, and then demonstrate how to set up Raven to execute the trades. We then expand upon the previous topic, and shows how to use a higher timeframe for the entry signals and a lower time frame for the exit signals.
0:44:31 - How to filter the Bar Direction solver with the anaSuperTrend indicator, so that the bar direction matches the anaSuperTrend direction.
1:04:35 - How to detect when price is at or near the daily high or low. This example covers various modifications.
00:32 - How to identify the bar color for an indicator that colors bars, to identify trend direction.
06:36 - Low of the High Bar Reversal signal. This customer question creates a reversal signal at a new 20 bar high or low. For a Short signal; when a bar make a new 20 bar high that becomes a setup bar, for a possible reversal short. The next few bars must close below the setup bar’s Low price to trigger the short signal. The opposite price action must occur for a Long signal.
52:22 - How to detect when an ATR Stop indicator reverses direction. In this example we use the anaSuperTrend indicator.
58:20 - How to setup two different profit targets (in Raven) for BloodHound Logic templates that have multiple trade signals in one Logic template. The different trade signals must be separated into separate Logic templates, and then two instances of Raven must be run. This will show how that is done.
0:00:32 - ADX & PPO opposing swing point correlation with DI trend direction. For a Long condition, an ADX swing high must occur within a few bars of a PPO swing low. The ADX must be rising, and one of the following conditions must be met; 1) The PPO crosses above the Signal Line, and the +DI is already above the -DI, or 2) The +DI crosses above the -DI, and the PPO is already above the Signal Line. The reverse conditions are used for a Short condition.
The Exit condition for the above system is when the PPO crosses the Signal Line in the opposite direction of the trade.
1:24:12 - How to detect, or filter a signal, when a minimum volume (400 in this example) has been reached.
1:29:26 - How to detect a Renko 2 bar pullback with a 3 bar continuation after the pullback..
1:55:46 - How to detect when the Fisher Transform indicator is coming from above +2 and crosses below +2, and when the Fisher Transform indicator crosses above -2.
0:00:32 - Two EMA crossover system with trading time constraints and only allowing the second signal to show, on a 1 minute chart. This system looks for the EMA 20 to cross the EMA 50 between the hours of 10am to 12pm. The first crossover signal is ignored/blocked, and the second crossover signal is given. A Crossover solver, Time Session solver, and Signal Counter function node is used.
0:36:01 - How to setup Raven to place a Limit order 1 tick above or below the Close price.
0:47:15 - Two ways to access different instrument data or timeframe data in BloodHound.
1:09:20 - The typical way to read a custom indicator’s signal, in BloodHound. We use the CandleStickPattern indicator to demonstrate reading a 3rd-party indicator.
00:32 - A shorter explanation of the Dorschden Swing Volatility solver.
42:16 - How to detect a Kangaroo Tail, but without the left and right body size requirements. The Kangaroo Tail is from Dr. Alexander Elder’s book “Come Into my Trading Room”. A summarized description is given in the video.
0:00:32 - HA and IchiMoku Entry
0:54:23 - Using the SiTimeBlock indicator to create an Exit signal at a specific time of day.
1:13:47 - How to block a Long signal on a down bar
1:18:44 - An example of how to read an Indicator’s signal plot.
1:35:37 - How to detect when price breaks the Swing indicator by 1 tick.
0:00:32 - General discussion on BloodHound templates and file management.
0:33:23 - How to build a +DI crossover of -DI condition. Then we add a filter that requires both DI plots to be above 20 after they crossover.
1:16:45 - Follow-up to the DI question above: How to require both DI plots to be above 20 prior to their crossover, using the Displacement setting.
This example shows how to detect when the PPO (momentum) and ADX (trend strength) indicators move towards each other and then bounce away from each other, creating a “pinched” look on the chart. That is the key component to this lesson along with many other rules and components to this PPO & ADX system.
This system also uses the DM, RSI, and EMA indicators. We take the customer’s set of rules and break them down into the individual solvers that detect each rule. This is a very good example demonstrating the process of translating written rules into a BloodHound system. We also demonstrate how to handle conservative trade signals vs. liberal trade signals vs. a trade signal combined with an indicator condition called the Sweet Spot.
The Workshop videos between these dates are being edited.
00:32 - This example shows how to use the If Then node so that system A can override system B to the final output. e.g. When system A has a long or short condition it will always show on the chart. But when system A is neutral (no output) then system B will show on the chart. In this example system A is an overbought/oversold condition, and system B is a trending condition.
21:44 - This example shows how to use an indicator (such as divergence), that gives a long bias or short bias, to block trade signals in the opposite direction. e.g. A divergence indicator may warn of a short divergence condition, for which you would want to block long trade signals from occurring. This demonstrates how to use the Inverter node with a AND node to do this.
34:01 - How to build an Exit signal when the bar is completely above or below a moving average. When a Exit long condition occurs this will also prevent Raven from taking any long trades, and the opposite is true for a Exit short condition.
43:02 - How to detect when the CCI crosses above 100 for 3 bars or more and then crosses below 100 for a short signal. And, when the CCI crosses below -100 for 3 bars or more and then crosses above -100 for a long signal.
0:00:32 - What is the Default Timeframe in BloodHound, and how do you change it? This discusses what the Default Timeframe is and how it works.
0:06:55 - How to create an Exit template that works for two different trading sessions/time periods. The scenario is Session 1 is from 6pm - 3am, and Session 2 is from 3am - 5pm. The key question is how to exit trades from session 1 at 3am before session 2 starts, because the two session use different trading rules/logic. This topic also discusses the pros & cons of mixing non-time based bars with time based conditions such as Ninja’s Session templates.
0:50:43 - A short example of how the If Then node works. There is a more complete video on the If Then help guide page… https://www.sharkindicators.com/documentation/logic-templates/if-then-node/
1:43:22 - A short example of how the Relational node works. There is a more complete video on the Relational help guide page… https://www.sharkindicators.com/documentation/logic-templates/relational-node/
1:58:42 - Then the Relational node discussion turns into a math discussion. An example shows how to use the Long/Short Modifier node to add solvers together(although the Additive node is a better solution) and how to subtract solvers from each other.
00:32 - The effect a Session template in the Chart’s Data Series has on indicators vs. using Session template in BloodHounds’s Time Session solver.This discussion, with a user, explains how a Chart’s Session template affects the calculations of indicators, and what is the difference of a Session template in the Time Session solver.
16:05 - How to block signals when price is more than 10 ticks away from a moving average (MA).
26:53 - How to block Entry signals for 15 bars after an Exit signal has occurred.
00:32 - Two ways to build a signal when the CCI crosses 100 or -100. This demonstrates the difference between the Threshold solver and Crossover solver.
14:31 - Accessing indicator data from its DataSeries. This example uses the SiSwings to demonstrate how a indicator DataSeries can be used with BloodHound to access the indicator’s custom data.
00:32 - How to read a custom indicator with a DataSeries that outputs 2, 1, 0, -1, or -2 etc. values. This lesson shows how to use the Threshold solver to identify when 1 or -1, 2 or -2, 3 or -3 values occur.
28:56 - How to create an Exit signal when price crosses the Open price of the Entry bar. e.g. When an Entry signal occurs use the Open of that bar as an exit trigger if price reverses the wrong direction and crosses that Open price.
12/11/2015 Fundamentals of Building a BloodHound System
1) Trading systems consist of various rules and price action or indicator conditions that need to happen in a certain order. These rules/conditions sometimes need to occur within a certain number of bars from each other, or sometimes the rules allow the number of bars between each condition to change a lot. When building a system in BloodHound it is important to understand how to link all the setup condition together. That is what's covered here. For example, condition #1 is a crossover, condition #2 is a pullback in price, Condition #3 requires a minimum pullback distance.
0:00:32 - Using BloodHound to show more then just buy and sell signals. This workshop will demonstrate how BloodHound can communicate additional information inconjunctions with buy and sell signals. We use a Stocks & Commodities magazine article from Feb. 2012 that uses Trend, Momentum, and Volume Volatility indicators (TMV) to create a BloodHound system.
0:42:51 - How a solver’s Input > Type > Price functions work. Most solvers use an Indicator Value or Price as an input. A visual explanation is given for the Price functions.
1:41:44 - How to identify a “trigger” bar with a bottom wick that is 45% of the entire candlestick length. Then detect if price crosses below the Low price of the trigger bar within a 30 bar period. A custom indicator is needed to track the Low price of the trigger bar.
1) “Back-Painting” Indicators. We demonstrate how to test for back-painting indicators, and how they affect your BloodHound system.
2) How to generate a reversal signal off the daily high or low. This system looks for price to make a new daily high or low, and the bar must close in the opposite direction.
3) A simple demonstration and example of why BloodHound should be placed on the lowest time-frame (LTF) when building a multi time-frame (MTF) system.
4) Why a 3rd party custom indicator’s plot named Default may not work in Bloodhound. A plot named Default may be a place holder added by NinjaTrader, but isn’t an actual plot.
5) Why you may not be seeing the crossover signals from a Crossover solver when using a indicator that has two or more plots.
0:00:32 - Market Profile indicators that have been tested with BloodHound, and a few examples.
0:26:25 - How to detect when price is above the Ichimoko cloud (Senkou lines).
0:36:17 - Detecting when the WoodiesCCI Turbo line crosses the zero line, and when the Turbo line is above 100 or below -100.
0:41:08 - Detecting a 2 tick move in price from the previous bar’s Close price. When a setup signal occurs, the setup signal is confirmed as a trade signal when price move 2 ticks beyond the Close price of the setup signal bar.
1:01:44 - Detecting when volume moves 50% or more, up or down. And, the Close price is above or below the previous bar’s High or Low price.
1:28:28 - How to get a signal when price touches or crosses a 50% fibonacci line or some other support/resistance line. This uses the Crossover solver.
11/06/2015 Putting Trade Rules Together
0:00:32 - Building a system that has 3 separate rules/conditions. This example demonstrates how to connect 3 setup rules together that happen at different times on the chart to build a trade signal.
0:53:14 - Using the Higher TimeFrame (HTF) bar direction to filter trade signals. This example uses the direction of the renko bar on a HTF to filter out trade signals on the Lower TimeFrame. Only LTF signals in the same direction as the HTF renko bars are allowed.
1:15:33 - How to build a Price above the EMA 50 moving average Long only or Price below the EMA 50 Short only signal filter.
00:32 - How to build an Exit signal 2 bars after a Entry signal. This shows which Function nodes are used to take a Entry signal and convert it to a Exit signal with a 2 bar delay.
18:55 - Why a crossover of 2 indicators on the same panel cannot be detected.
23:39 - Building an Exit signal using the anaSuperTrend (SuperTrend) indicator.
49:51 - Using the Lookback node to delay an Entry signal by 3 bars.
10/23/2015 Preventing Signals Above HH or Below LL
00:32 - An explanation of the Large Amount & Small Amount settings are for in the Comparison solver.
27:05 - How to block signals when price is above or below the Highest High or Lowest Low swing points of the SiSwingsHighsLows indicator. Signals are only allowed when price is between the HH and LL as identified by SiSwingsHighsLows.
44:33 - How to identify 3 up bars in a row after price crosses above the SMA 14. Price must first cross above or below a moving average, and then wait for 3 consecutive bars in the same direction as the crossover.
00:32 - How to use the Slope solver to identify a specific angle of an indicator. In this example we identify a 0.5 tick angle of the SMA 5.
08:45 - Build and Exit signal when the body of the candle touches a moving average. This example generates a signal only when the candle body touches the ALMA indicator.
56:18 - Examples of how the NinjaTrader setting ‘Calculate on Bar Close’ (CoBC) affects the way BloodHound signals are generated.
1) How to detect when price crosses a supply / demand zone indicator. The Pivot indicator is used to illustrate this example. because there is no freely available S/D zone indicator.
2) How to use a “signaling” plot to create a long/short trend filter. This example uses the ErgodicHist indicator (click for download). The ErgodicHist has a special crossover signal plot called CrossDot. The CrossDot plot is used to create the long/short trend filter with a Threshold solver and Toggle node. Then the ErgodicHist is placed on a higher time-frame.
3) How to check the slope direction of the VWAP indicator (click for download).
4) How to use the Crossover solver to build a Bollinger Band cross-in Entry signal & cross-out Exit signal. A Entry signal is generated with price crosses into the bands, and an Exit signal is generated when prices crosses out of the bands.
5) How to detect when a moving average (EMA) begins to flatten out after the MA has a strong move up or down. This example uses the Change In Slope solver.
6) How to use the ATR measurement unit in the Slope solver. The ATR creates a self adjusting slope measurement based on volatility, that the ATR calculates.
7) Do indicators change when using SiBackTestRenko with Wave mode: Off vs. Wave mode: On? Watch for a full explanation and testing of which indicators may change.
10/02/2015 Using Lookback Period to Connect Conditions
00:32 - How to use the Lookback Period setting, in Solvers and Function nodes, to link condition #1 to condition #2 to condition #3. In this lesson we use the Classic Stock system to demonstrate the use of the Lookback Period. FYI, the Classic Stock system template is included with BloodHound examples.
33:51 - How to detect when two indicator plots are within 8 ticks of each other, and when price touches a indicator plot. This example uses two pairs of moving averages for the setup conditions, and then waits for price to touch a indicator. The EMA 5 above or below the EMA 12 determines the trend direction. Next, the SMA 12 must be within 8 ticks of the SMA 25. Then, wait for price to touch an indicator (the EMA 5 was used) to trigger the trade.
00:32 How to use the ^TICK index to build an exit logic. The ^TICK index is not a tradable instrument. It is NYSE exchange data. This topic explains how to setup BloodHound and a Threshold solver to utilize the ^TICK index.
29:59 How to use the anaSuperTrend indicator on a higher time-frame to filter trades on a lower time-frame. This example uses the anaSuperTrend on a 60 Minute chart to determine the HTF trend. The trade signals, on a 60 Tick chart, occur when price crosses the anaSuperTrend, and these signals are filter by the HTF trend.
00:32 - How to detect if the High price of the last 3 or 4 bars stepped higher each bar, and if the Low prices stepped lower. Regardless of the bar direction.
20:17 - How to detect a 3 Linebreak pattern. IE, when the close of the current bar breaks above the highest high of the last 3 bars, or breaks the lowest low of the last 3 bars.
32:53 - How to detect a percent move in price. IE, how to check of the Close price of the current moved 5% higher than the previous bar’s closing price.
00:32 Using the Strategy Analyzer’s Optimization with Raven. What can be optimized. Downloading data before using the Strategy Analyzer.
23:58 How the Signal Blocker function node works.
0:00:32 We start with a customer question asking if the following system can be built.
1:02:26 How the Lookback function node works.
22:49 Identifying the reversal points of the RSI indicator.
27:39 How the Inverter function node works.
39:21 How the Long/Short Modifier function node works.
0:00:32 How the Dorschden Swing Trend solver works.
1:10:25 How to count the number of swing points in a trend. This example shows how to count three HH (Higher Highs) in a up trend and three LL (Lower Lows) in a downtrend. Once three swing points are counted trade signals are blocked until the trend changes direction.
1:49:54 Detecting when price crosses a HH or LL.
1:54:48 How the Time Session solver works, and some examples of using it. Also building an Exit logic for the market close.
0:00:32 The first question uses the Bollinger bands, Keltner channels, and Stochastics to determine signal direction. The system looks for the Bollinger bands to cross outside the Keltner channels as the trade trigger, and the slope direction of the Stochastics determines the direction of the signal.
0:28:02 How to use the Support Resistance solver. This discusses the various setting of the S/R solver, and some common uses for it.
1:46:57 This shows how to isolate the first signal when a long set of continuous signals occur. Sometimes your logic may generate periods of continuous signals (such as 20 long signals in a row), and you may only want to see the first long signal, but not the rest. To demonstrate this we build a simple SMA 20, 50, & 200 comparison system. The second part shows how to generate an exit signal when the continuous entry signals end.
0:00:32 - How to generate a signal when price makes a deep pullback on a Renko bar. Then a continuation of this topic with an ADX slope filter added to it.
0:59:39 - How to build a trend filter using the DM indicator. This trend filter uses the following conditions: ADX must be sloping up. ADX must be above 19. +DI must be above -DI for long trend, and opposite for short trend. +DI must be sloping up for long trend, or -DI sloping up for short trend.
1:28:22 - How to use the Regression Channel Width solver.
00:32 How to add a Long only or Short only filters/bias to your BloodHound signals. A simple MA crossover system, which proves both Long & Short signals, is used to demonstrates how to make a Long only, Short only, and both Long & Short signal system. Then we show how to setup Raven so that you can instantly change Raven from a Long & Short system to Long only or Short only trades.
16:49 Next we expand upon the topic above and use a MACD indicator on a Higher Time-Frame to filter the MA crossover signals to Longs only when the MACD is above the zero line and Shorts only when the MACD is below the zeroline.
30:00 How to visually distinguish different trade setups within a Logic template. A Logic template can contain any number of different trade signals, which BloodHound will show them all as green or red. This topic demonstrates how to show the different trade signals as different colors, so that they can visually be distinguished on the chart.
44:22 This example builds a TriggerLine system, but the main concept is how to identify when a moving average is between two other moving averages. More specifically, when is the fast small triggerline in between the two large triggerlines. This uses the anaTriggerLine indicator. Triggerlines are a pair of smoothed moving averages.
0:00:32 How to use the Gom Volume Ladder in BloodHound. The question was asked how to read data such as Delta volume from that indicator. We use NinjaTrader’s VolumeOscillator indicator to simulate how you might detect when the Delta volume (from any volume profile type of indicator) is greater than 300 or less the -300, using the Threshold solver.
0:30:50 This is a sub-topic of the above topic that discusses the effects of Calculate on Bar Close (CoBC) setting. We discuss when BloodHound should have CoBC = False for certain indicators the need to run with CoBC = False.
0:44:52 Limiting the trade signals to only 5 signals per day. This example will show how to place a daily limit on the number of signals your system will give in any day.
1:32:15 How to build a Daily Engulfing bar trend filter. This filter uses the PriorDayOHLC indicator to find an Engulfing bar on the daily chart to filter trades on a intra-day chart.
1) We start off demonstrating how to use the Regression Channel Position solver. We build a solver that identifies a trending direction move in price, and a counter trend direction move output signal.
2) Here we cover the Slope solver again. Using the SMA 14 to find a non-flat sloping areas, and another solver to identify flat areas in the SMA 14.
3) Here we identify when the Close price is within 5 ticks of a EMA 10 smoothing of the SMA 30.
1) What is, and how to resolve the Missing Data error message.
2) A quick demonstration using solvers on multiple time-frames, and using them in a system. This example looks at the slope of four SMA 14 indicators all on different time-frames. All four Slope solver are connected together with a AND node to detect when the SMA 14 is sloping up on all time-frames at the same time.
3) An updated training look at the Indicator Threshold solver. We build several trade filters to demonstrate using the Threshold solver.
4) How to read an arrow signal or a dot signal from a 3rd party indicator. In this example we use the 3rd party Flux indicator in the Threshold solver to demonstrate how BloodHound can read signals.
5) Detecting when the Close price is within 4 ticks of the anaCurrentDayVWAPV42 indicator. Two solvers are built to detect when price is near the Session VWAP plot, and the Upper/Lower Band SD 1 plots. Then we compare the EMA 8 to see if it is above or below the anaCurrentDayVWAPV42 indicator.
6/26/2015 Blocking Signals at HH/LL Swings Points
1) How to refresh your BloodHound license after purchasing a Maintenance Extension.
2) How to use the Support Resistance solver to block trade signals when price is too close to a support or resistance plot. This example blocks a Long signal when price is too close to the previous swing highest high (HH), and blocks a Short signal when too close to the swing lowest low (LL) of the SiSwingsHighsLows indicator.
6/19/2015 Recording Failed
1) We start off with training on the Crossover solver, with a couple of examples.
2) This section shows how to use the Comparison solver to detect when the Close price gets within 5 ticks of the upper Keltner band for a short signal, and a long signal when the Close price gets within 5 ticks of the lower Keltner band.
3) This system looks for 6 or more bars in the same direction and then a reversal bar with a long wick to qualify the reversal signal. 6 up bars, or more, followed by a down bar with a 80% wick length will give a Long signal, and the opposite setup for a Short signal.
0:00:35 Detecting expansion or contraction (divergence or convergence) of indicator bands. The logic demonstrated uses the Bollinger Band indicator, but can be used for other indicators as well.
0:48:38 How to determine when a plot value is unchanged (stays the same) from bar to bar for a certain number of bars. IE, If you want to detect that a Fib line has changed. This example uses the TTP_AutoFibRetracement indicator.
2:05:48 How to detect when the Bollinger bands are inside the Keltner Channel bands.
00:32 - How to add a crossover condition filter to an existing trade signal. This example shows how to extend an existing signal forward until a crossover condition works. This uses the Signal Extender node.
28:58 - Detecting when the EMA of a CCI crosses the zero line. And, then we add a filter that checks for the CCI to be above or below the zero line.
45:24 - We discuss a general question “Can a solver (BH or Raven) generate OCO orders.”
47:12 - We discuss a general question “Will a system work on any time frame or bar type?”
0:00:32 - The following 3 part setup is built. For a Long setup, there must be 4 up bars in a row, then 4 down bars in a row, and the reversal down bar must have a upper wick.
0:45:52 - How to remove a signal when a small number of reversal bars occur.
0:57:07 - How to detect when a Moving Average line falls to cross another MA. Similar to a rejection. This example uses the anaTriggerLine indicator, therefore the logic is a little more sophisticated.
2:02:28 - A quick example on how to extend a signal forward for a couple of bars.
0:00:32 - How to shift a signal to next bar when the next bar is in the same direction.
0:12:01 - Can BloodHound send the signal data to a text file.
0:15:08 - How to block / prevent a signal when price is moving into a Moving Average.
0:32:13 - How to setup BloodHound to show a discrete trade setup and a trend filter both on the chart at the same time.
0:44:51 - A quick backtest example. A thorough Raven training video can be found here… https://youtu.be/Jx0Nv9AlFSc
0:49:08 - How to use the anaSuperTrend as a trend filter to filter trade signals.
0:59:02 - A brief explanation of the Support Resistance solver.
1:11:58 - Building a trend filter to allow Longs only when price is more than 10 ticks above a MA, and allow Short only when price is more than 10 ticks below a MA.
1:23:03 - Building a trend filter of the ADXVMA above or below the T3 indicator.
1:31:12 - Does SiChameleon have a EMA or HMA smoothing of the price data? How to use the Open price into a moving average.
1:36:00 - How to nest or feed price data from a different timeframe into a moving average or any other indicator.
1) Detecting when a bar closes at the top/upper 25% or the bottom/lower 25% of the bar.
2) Detecting the second bar, in the same direction, without a wick and right after price reverses. In other words, price must reverse. Then the second bar after must not have a wick.
3) A very simple example of testing a 3rd party or custom indicator. This Tips & Tricks video is more informative… https://www.youtube.com/watch?v=-LCEyL7kW-Y
00:33 - We start with a simple explanation and demonstration of using Raven to forward test a BloodHound system
31:41 - This is another example of detecting bar wicks to create or permit trade signals when price reverses. Conditions for a Long signal; A down bar must have a upper wick. The next bar must reverse up, with a lower wick. The next bar must be another up bar, for 2 up bars in a row.
1) In this example a customer wants to use the anaADXVMA to learn how to use its DataSeries Trend to build various Exit signal conditions. The Entry signals are simple, see below. The Exit signals are based on two bars and a combination of output values from the DataSeries Trend. A DataSeries is the same as a Plot, but it is not visible on the chart. It is data that is passed from one indicator to another without being seen on the chart.
Entry signals and conditions:
1. When DataSeries ‘Trend’ = +1, enter a Long trade.
2. When DataSeries ‘Trend’ = -1, enter a Short trade.
3. Only one entry signal can be produced until there is an intervening exit signal.
Exit Long trades when any of the following occur:
1. A bar where Close < Open(down bar) is followed by a DataSeries value of 0,
2. Two bars in a row where the Close < Open.
3. A DataSeries value of 0 and the next bar has Close < Open.
4. Two DataSeries values = 0 in a row.
5. A stop loss of 10 ticks just in case.
6. A profit target of 15 ticks.
Exit Short trades
1. Switch the Close < Open to Close > Open(up bar) in the above Long trade exits.
0:00:32 - This workshop covers a complete overview of Raven, and includes some NinjaTrader tips for using strategies.
0:15:36 Adding and setting up a Time Session Solver.
0:33:09 The process of adding Raven to the chart.
0:34:22 Loading BloodHound into Raven.
0:36:40 Entry & Exit Logic - Note: Leaving Entry Logic set to <None> will allow you to choose your Entry Logic template from the chart’s drop-down menu. An Exit Logic must be selected in order to use the Exit Logic functionality. This was not explained in this video.
0:38:26 Long/Short Threshold values explanation.
0:45:05 Confidence Use Compare explanation.
0:47:15 2. Entry Order Options.
0:59:06 The difference between BloodHound and Raven.
1:00:50 3. Options - Note: This video was filmed before the ‘Start Auto Enabled On’ option was added. That option must be set to True to reveal the Backtest Mode option.
1:09:21 4. Trade Management - Using an ATM.
1:13:41 Trade Management - Using the Default option.
1:25:25 5. Signals - Play Alert
1:26:29 General Section - NT Standard Settings
2:41:09 - Is there a limitation to the number of charts, BloodHounds, and Ravens that can be run at the same time.
2:44:16 - A quick lesson on using BloodHound in the Market Analyzer.
1) How the Change In Slope solver works.
2) This example uses the Comparison solvers to define No Trade Zones. This system blocks trade signals when the Close price is within 10 ticks of $48, $49, and $50 instrument price.
3) This example shows how to take a primary trade signal and use it as a prerequisite to a secondary simple price action condition. The second condition requires the current Close price to be greater than the previous Close price for a Long signal.
4) Using the RSI as an Exit template. When the RSI crosses 70 a Long position will be exited. And, when the RSI crosses 30 a Short position will be exited.
5) This system is an alteration of #2 above. It blocks trading when price is within 10 ticks of the highest high or lowest low of the past 24 bars.
0:00:32 - Detecting tight consolidation of the UniRenko and SiBacktestRenko bars, and then generate a signal on the first breakout bar. Followed by generating the signal on the second breakout bar in an attempt to eliminate a failed breakout of the first breakout bar.
0:19:06 - Then further enhancements are added by generating a reversal signal when the first breakout bar fails.
0:41:21 - A demonstration of how the above system works one the 5 Minute, SiBacktestRenko, and SiProRenko charts.
0:45:31 - A brief explanation why Renko bars can not be back-tested accurately.
0:53:59 - Here we look at simple Back-test results, of the above system, using the UniRenko vs. the SiBacktestRenko.
1:03:27 - How to generate a discrete signal from the anaADXVMA indicator. Make sure you have the anaADXVMA indicator installed before opening the BH template. The whole ana indicator package can be downloaded from www.trade-the-plan.com
1:24:15 - How to use the slope of an indicator to block/prevent a signal. This example uses the Stochastic indicator. The If-Then node & the AND node are used to demo two different ways to accomplish this.
1:38:22 - How to setup BloodHound to see an entry signal template and an exit signal template on the chart at the same time.
36:55 - How to find a price pullback after the EMA 14 crosses the EMA 30.
59:02 - How to find a Higher Low of the DM +DI plot when the +DI is above the -DI, and a Higher Low of the DM -DI plot when the -DI is above the +DI. The SiSwingsHighsLows is used to determine when a Higher Low of the DI plots is made.
Please note, the SiSwingsHighsLows indicator setting on the chart and in the Solvers have been changed slightly from what was built in the video. The SiSwingsHighsLows - Widest Bottoms plot was replaced with the Tightest Bottoms plot. Using the Tightest Bottoms plot seems to give better results.
1:41:43 - This short demonstration shows one of the ways an indicator can expose to BloodHound (and any other indicator) when a plot color changes.
0:00:32 - This lesson demonstrates how to link several conditions (that happen at different times on the chart) together to generate the final trade signal. Condition #1 looks for the Stochastics to cross above 10 or cross below 90. Condition #2 needs price to reverse direction in the direction of the Stochastics. Condition #3 looks for a Higher Low(Long setup) or Lower High(Short setup) to happen after condition #1. Condition #3 can happen a unknown number of bars after #1 & #2. The key lesson to learn in this example is how to extend conditions #1 & #2 forward in time until condition #3 occurs. This system uses the Signal Extender node to accomplish that, and demonstrates ways to experiment and test various reset logic to turn the Signal Extender off when condition #3 fails to setup.
2:50:16 - How to identify the second bar after the Close price crosses a moving average.
2:54:59 - Detecting when the DM indicator’s +DI and -DI plots are diverging.
00:32 - Detecting when both the Open & Close price of a bar is above or below both of the anaTriggerLines.
00:32 - This example looks for large moves in price as measured from the previous bar’s High or Low price. This will detect when price moves 2 x ATR(10) above the previous bar’s High for a Long signal, or below the previous bar’s Low for a Short signal. To do this we will use the Comparison solver - Difference - Large Amount, ATR measurement.
28:58 - This is a follow up to the previous question. This example will detect when the Closing price breaks above the Highest High of the last 2 bars for a Long signal, or if the Close breaks below the Lowest Low of the last 2 bars for a short signal.
40:46 - The next example will trigger a break above an upper resistance line or below a lower support line, only when the S/R lines have a 30 tick separation. The key to this is building a solver that detects when the S/R lines are separated by 30 ticks as a permissive.
0:52:07 - How to determine when two moving averages (MA) are 3 ticks apart/separated.
0:00:32 - How to detect a crossover of a EMA8 on a 4 Range chart and a EMA8 on a 1 Minute chart.
0:12:11 - We build an Exit logic when there is a 10 tick profit or loss from the High or Low price of the bar that the trade signal occurred. IE: When a Long trade signal occurs, exit 10 ticks above the High of the signal bar for a profit. And, exit 10 ticks below the Low of the signal bar for a stop loss.
1:55:26 - If you have an Exit logic and an exit signal occurs, this will show how to hold on to or extend the exit signal forward in time. This can be useful when you want to use an exit condition to block trade signals.
0:00:32 - An explanation on using the new feature Type > Price option available in solvers.
0:32:36 - How to find a bar that straddles the Bollinger band. This requires two Comparison solvers.
0:45:46 - A quick question, can Raven generate backtest results when ‘Calculate on Bar Close’ = false?
0:48:22 - Which nodes to use for a sequence of conditions. Condition #1 happens on bar 1. Condition #2 happens on bar 2. Condition #3 happens on bar 3. To accomplish this we will use the Lookback node.
0:59:39 - Getting crossover condition from a Range chart (non-time based chart) on to a Minute chart.
1:25:16 - Detecting when the Close price breaks above the High of the previous bar for a long signal. and vise versa for a short signal.
0:00:32 - Installing BloodHound v1.220, and what is included in this update.
0:12:37 - Connecting condition #1 to condition #2 using the Toggle node. Condition 1, look for a new intraday High or Low to be made. The trade will be in the opposite direction. Condition 2, wait for price to cross the EMA(50) moving average to execute the trade.
1:20:47 - Can BloodHound access the Close price of a signal bar?
09:37 - The pitfalls of using “Set as default”
13:06 - Removing a “set as default” file.
16:06 - Find out if the slope of the MACD line is greater than the Average line using that indicator’s histogram.
29:14 - Rename logic nodes.
30:04 - Using ATM in Raven
37:12 - Using Raven’s drop down menu above the chart
00:00:32 - Daniel Roe from Trade-The-Plan.com presents this workshop and demonstrates building a Fibonocci retracement system. Daniel has provided a free indicator he had made for this system. The indicator is available on his web site in the Download section. This BloodHound example focuses on the 61.8% retracement line.
01:45:39 - Afterwards we demonstrate filtering Higher lows (HL) or Lower highs (LH) with the Stochastics indicator. A Long signal occurs when a HL is set and then the Stochastic must cross the 80 level. A Short signal occurs when a LH is set and the Stochastic crosses the 20 level.
02:25:58 - How can indicators share their data with BloodHound.
02:29:43 - What is the difference of a BloodHound template and NinjaTrader Chart template.
0:00:38 - We revisit detecting when price reaches with 1 tick of a Moving Average (MA) for a bounce off of the MA.
0:18:07 - How to use a Limit order in Raven.
0:26:16 - General comment about determining trend using the SiSwings indicator.
0:35:15 - Comparing the UniRenko to the ProRenko bars.
0:44:04 - Detecting Volume high points (spikes) and low points (valleys). We use the SiSwingsHighsLows to determine these points for BloodHound.
0:00:34 - When working with multiple time frames within BloodHound, all BH charts will use the same Calculate On Bar Close (COBC) setting that the BloodHound indicator is set to. When COBC = True, a daily chart does not calculate indicators on the current day’s bar, so BH can not analyze indicator values on that bar. Discussion on the risks of adjusting COBC and how to remedy this using a Lookback Node. Function Nodes and Logic Nodes always work on the Default time frame only.
0:17:38 - How to change the speed at which NT calculates indicators when COBC = False?
0:24:24 - How do the confidence Threshold parameters work?
1:18:28 - How to obtain the template files for these workshops.
0:07:14 - Looking for an RSI overbought/oversold condition, and price crossing the Keltner Channel. Specifically, for a long signal the RSI need to be less than 25 for 3 bars in a row and the Low price must cross above the lower Keltner Channel. Opposite for a short signal.
0:57:04 - Looking for price crossing the EMA 10 on a higher 60min time-frame.
1:10:24 - Detecting possible double tops (DT) and double bottoms (DB)
1:27:47 - A simple comparison of the SiBackTestRenko to the Renko bar.
0:00:33 - How to detect when indicator plots, such as moving averages (MA), are parallel or close to parallel.
0:20:46 - How to detect price crossing above or below a moving average swing/pivot point.
0:34:19 - How to determine when price crosses a moving average on a higher time-frame (HTF), and price reverses direction on the default time-frame, on the same bar.
0:00:32 - Detecting a Stochastics crossover, after it touches overbought or oversold levels, with a EMA 200 slope direction filter.
0:29:59 - Using the Comparison solver to determine higher highs HH, higher lows HL, lower highs LH, and lower lows LL.1) Using the Comparison solver to determine higher highs HH, higher lows HL, lower highs LH, and lower lows LL.
1:29:00 - How to reset the Signal Counter or Signal Blocker at a specific time of day.
1:57:44 - Detecting when price is above the Bollinger bands and a moving average by 5 bars or more.
2:38:46 - How to setup an alert sound when price breaks/crosses a certain level.
2:44:28 - Detecting a sharp angled reversal (inflection) of an indicator. The Stochastics is used for this example.
18:12 - We build a filter using anaSuperTrend. When price moves too far away (50ticks) from the SuperTrend we want to block BloodHound signals. This is similar to finding an over extended price move.
A user has built a BH system that uses the Comparison and Slope solvers that generates a signal on almost every bar. Have a trade signal on every bar tells Raven to fire off a trade as soon as it is enabled, but we want Raven to wait until the trade direction changes before executing the first trade. The solution is to use the Crossover and Inflection solvers to generate a signal only once per trend direction.
0:00:33 - How to detect when the whole bar is in between to moving averages. Then use that condition to block a trade signal afterwards using the Toggle node.
1:14:26 - Detecting the slope of a smoothed ATR. EMA 10 of ATR 14.
1:29:11 - In this example we examine how to detect when price touches a fib line. We do not have a “Fib Line” indicator installed, so we use the Pivot indicator to simulate a fib line.
2:15:50 - Determining the trend direction using the anaADXVMA slope.
2:29:07 - In this last example we build a crossover condition that only triggers when the Closing price crosses over a moving average by 3 ticks or more. A 1 or 2 tick crossover will not fire a signal.
0:00:33 - How to reset the Signal Blocker whenever there is a retracement of one, two, three, renko bars.
0:47:14 - How to restrict Raven so it only trades during 3 different discrete times. IE 7-8am, 10-11am, and 12-2pm. We use the Time Session solver to isolate trade signals so they only occur during these times.
1:05:50 - How to detect when the Stochastics reverses direction. The direction or slope of the Stochastics, and a above 80 or below 20 filter.
1:17:32 - How to determine the bar direction of the HeikenAshi bar.
1:53:02 - IF Then Else node explanation, and simple example.
0:00:36 - How to build a multi step Stop Loss in Raven. IE. Breakeven at 15 ticks profit, and then a trailing stop loss 3 ticks below the Low of 3 bars back.
1:22:34 - Add a time filter
1:33:46 - Lastly, we answer why the Ratio node gives different results when you connect 7 solvers in to 1 Ratio node vs splitting the solver in to 3 Ratio nodes and then connecting the 3 Ratio nodes into a fourth Ratio node.
0:00:43 - This workshop covers the new SiRenkoCounter indicator settings, and how it can be used in BloodHound.
We build a set of logic that finds wicks on Renko bars, such as the BetterRenko.
A quick explanation of Chameleon: Lookback setting and how it affects the SMA and Bound plots.
9/26/2014 Engulfing Bars & 5 Indicators on MTF
1) The first lesson demonstrates how to find the High of the current bar greater than the High of one bar back, and the Low of the current bar is less than the Low of one bar back, to find an engulfing candlestick. Then we add a simple volume comparison as well. Afterwards, we use Ninja’s CandleStickPattern indicator.
2) Finding the First and Second pull-back after the trend changes direction, defined by a Moving Average crossover (in this case Nexgen Trigger lines). This lesson uses the Toggle node, Signal Blocker, and Signal Counter node.
3) Lastly we build a system that incorporates five indicators Chaikin Money Flow, MFI, CCI, and Stochastics. Each indicators has a different trending rule that uses the Threshold or Comparison solver. All indicators must agree on the trend, and we use a second time frame.
4) A simple Triggerline crossover signal with a MACD filter.
5) A simple Triggerline crossover Exit logic.
0:02:04 - We will compare the daily Open price of a stock to two Option Strike prices and find which one is closer. This set of logic can also be used to find which support or resistance line is closer.
0:41:03 - In the next example we examine a Volume Spread analysis, as explained by the customer question. The conditions in this system looks for a specific volume pattern based on percentage differences. The volume pattern to be found is the current bar's volume must be 20% greater than the previous bar's volume. And, the volume 2 bars back must also be 20% greater than the previous volume. I.E. The volume of the previous bar must be less than the bar in front and the bar behind it. We also check to make sure that “price action” is making the correct price patterns/movements as well. One of the Comparison solver for the volume pattern was corrected on 3/13/2018 thanks to a smart customer who noticed the mistake. The old file has been replaced.
1:35:50 - How to compare the Midpoint price to a moving average.
0:00:32 - A user wanted help determining when 5 Moving Averages were within 3 ticks of each other, when they were all crossing each other at the same time. After building this system we discussed how to use the solver setting to relax some of the strict conditions.
0:57:56 - A user asked “How to only take a long signal if the previous bar closed up and a short if the previous bar closed down.
1:10:20 - How is the Truth Table used, and what does it do.
0:22:23 - Tailwind mode and using other indicators with the Support Resistance.
0:28:31 - When closing price is within specific range of indicator - between 1 tick and 10 ticks below the EMA.
0:48:46 - How to get an output when the trend agrees with SiSwings.
1:05:07 - How to analyze custom indicators in BloodHound (where to learn how).
1:07:20 - Can you put more than one instance of BloodHound on the chart?
00:32 - Some examples using the ZigZag indicator.
22:01 - Some examples using different time-frames (150 Tick, 250 Tick, and 6 Range), with indicator conditions CCI crossing the zero line and CCI crossing above +100 or below -100.
51:36 - Using the slope of a moving average on multiple time-frames.
58:23 - How to calculate the angle of a moving average or plot.
0:00:30 - Setup Mode vs. Real-Time Mode
0:06:03 - Detecting when two moving averages are both touching a price bar at the same time, but the MA’s can not be touching each other.
0:52:05 - Intrabar Backtesting
0:58:12 - Detecting when price is within X ticks of a moving average.
1:09:13 - Finding a Crossover Breakout. When a moving average crossover occurs check for price to move 10 ticks past the crossover price.
0:00:30 - How to detect Double Tops and Double Bottoms, improved version.
0:33:54 - How to detect the Momentum indicator crossing the zero line only if the Momentum exceeds 0.3 or -0.3 value prior to crossing the zero line.
1:03:00 - Detecting when a moving average is touching a reversal bar. Then we modify the logic to detect the SMA touching the first and second bar after the reversal.
Daniel shows the process of building and backtesting a system with the MomentumBBLine and Keltner channel. "Always do thorough testing on your system."
Today Daniel shows how to build a custom session template in NinjaTrader to be used with the Daily Pivots indicator so that you can display the entire ETH (electronically traded hours) session, but have the ability to choose either the ETH or the RTH (regular trading hours) session for calculating the floor trader pivots.
Work with the pivots using the comparison solver.
Lookback and signal extender nodes.
Backtesting in Raven.
Today Daniel went into great detail in working with multiple time frames, as well as creating an RSI Divergence exit logic.
6/27/2014 Fuzzy Logic, Threshold & Slope Solvers
6/20/2014 Various Q & A
Daniel, from Trade-the-Plan.com, demonstrates how to use BloodHound in NinjaTrader's Market Analyzer, and explains how he likes to use the Market Analyzer to scan for potential trade setups. 2) What is a BloodHound BlackBox file, and how to convert your BloodHound system into a BlackBox.
In this Workshop we discuss what is needed for a complex crossover system to work. Afterwards, the Signal Counter's functionality and use is explained. Followed by miscellaneous questions, and setting up Raven to use execute an ATM.
When to use the Crossover solver vs. the Comparison solver? A quick explanation of the Support Resistance solver. How to detect price crossing a higher high after price makes a higher low? A quick explanation of using the Slope solver.