Strategy using the Bollinger band with the Keltner Channels. Watch for the Bollinger bands (blue/red lines) squeezing inside the Keltner Channels (pink dots) for a breakout - this could be up or down so use in conjunction with other indicators.
This is a script for a view I wanted to go along with the Autoview plugin I bought. Keep in mind this is my first script and was created for me to learn the Pinescript framework. This isn't meant to be perfect. Indicator colors are usually blue or green or red. Also keep in mind since this is my first script in a new framework, the more stuff I build the better...
Channels help with identifying buying and selling opportunities and avoid bad trades. This channel consists of two lines parallel to a moving average. The distance between the lines vary depending on the market's volatility (standard deviation channels). Channels mark the boundaries between normal and abnormal price action. The market is undervalued below its...
This indicator is almost identical to "Bollinger Bands %BB" except its calculations are performed in logspace and it adds an optional EMA line (after LazyBear's idea).
This is a simple experimental study designed to outline trend activity and volatility. In this study, the amount of change between current source and source of a specified lookback is calculated, then added to and subtracted from current source. Next an exponential moving average is taken of the values for smoothing over the specified period. Lastly, a midline is...
Indicator make histogram from difference of: - classic ATR (default period - 14) - Simple Moving Average (default period - 100) to this ATR. Histogram colored (green when >0, red <0). Volatility increase signal - histogram crosses the zero line. For greater visibility, a colored variable moving average (variable SMA for histogram) was added (green when...
This is an experimental study designed to track directional polarities across multiple timeframes and express them as a simple two color grid. The polarity in this calculation is determined by divergence between a fast and slow McGinley Dynamic. Your current resolution's polarity is the top row, the rows below are are for higher timeframes of your choice.
This is an experimental study designed to track the average magnitude of price movements. First the range between high and low, and the range between open and close are calculated. Then a positive and negative root mean square is taken of both ranges, and the results are smoothed with an exponential moving average. And lastly, the median value between the ranges...
This is an experimental study that utilizes Kaufman's Adaptive Moving Average and the McGinley Dynamic. First, a fast and slow KAMA based McGinley Dynamic are calculated. The divergence between them is used to indicate wave direction. The channel's bounds are calculated by taking the highest high and lowest low of the slow McGinley Dynamic over a specified channel...
This is version 2 of Special features: Added partial profit taking as price rises. Profit taking is triggered by price crossing an EMA. After profit taking, price has to rise by a user-specified percent before taking profits again. Also includes condition for fully closing position after meeting specified profit target. To incorporate into your algo,...
Here's how to create a trailing stop with a manual buy order, on an exchange that does not support native trailing stops. Code can easily be copy+pasted into your normal algos. To set the entry price for your manual trade, specify the bar time when the trade was made. Note that the time you specify needs to correspond to an opening time on your chart--if it's a 3...
This is an experimental study in which a geometric moving average is taken of price, then the range is multiplied by average annualized volatility based on the current trading timeframe and specified lookback, and by Fibonacci numbers 1 through 21.
This version triggers every batch within each candle. The previous version only triggered one batch per candle. This will not trigger batches in perfect order, but I left the "sequential" option because it still triggers the batches in order more often than not.
This script lets you separate alerts into batches, and trigger each batch in either sequential order or (pseudo)random order. You can also specify the number of batches being used. This is helpful when you have alerts to be triggered on every candle, but the number of alerts causes API errors if they are all executed at once.