Super OrderBlock / FVG / BoS Tools by makuchaku & eFeThis super indicator is a Swiss army knife for Smart Money traders for OrderBlocks / FVG / BoS
It provides many options for drawing (non-repainting) boxes for OrderBlocks, Fair Value Gaps (FVG) and Break of Structures. The boxes are extended into the future, until the first retest/mitigation.
Some of the additional options (not explained in the diagrams above)
PPDD OB : An order block which is formed after interacting with Liquidity (old low/high, fractal low/high, etc). Since these OB's are in the most premium or most discount, they are Premium Premium Discount Discount OB's (PPDD OB)
HVB Bars : When the volume of any bar is higher than the average volume of last N bars, it could mean something important (in the right context). Hence, the indicator allows for coloring them differently.
This indicator was built as a collaboration between @makuchaku & eFe
Pro tip : This indicator is a simply a tool to visualize trading concepts on the candle stick chart. It is the job of the trader to sequence these effectively into a profitable trade.
If you come across any bug or have a question on how to effectively use the indicator, please don't hesitate to ask questions.
Good luck & good trading!
Поиск скриптов по запросу "gaps"
Rolling VWAP█ OVERVIEW
This indicator displays a Rolling Volume-Weighted Average Price. Contrary to VWAP indicators which reset at the beginning of a new time segment, RVWAP calculates using a moving window defined by a time period (not a simple number of bars), so it never resets.
█ CONCEPTS
If you are not already familiar with VWAP, our Help Center will get you started.
The typical VWAP is designed to be used on intraday charts, as it resets at the beginning of the day. Such VWAPs cannot be used on daily, weekly or monthly charts. Instead, this rolling VWAP uses a time period that automatically adjusts to the chart's timeframe. You can thus use RVWAP on any chart that includes volume information in its data feed.
Because RVWAP uses a moving window, it does not exhibit the jumpiness of VWAP plots that reset. You can see the more jagged VWAP on the chart above. We think both can be useful to traders; up to you to decide which flavor works for you.
█ HOW TO USE IT
Load the indicator on an active chart (see the Help Center if you don't know how).
Time period
By default, the script uses an auto-stepping mechanism to adjust the time period of its moving window to the chart's timeframe. The following table shows chart timeframes and the corresponding time period used by the script. When the chart's timeframe is less than or equal to the timeframe in the first column, the second column's time period is used to calculate RVWAP:
Chart Time
timeframe period
1min 🠆 1H
5min 🠆 4H
1H 🠆 1D
4H 🠆 3D
12H 🠆 1W
1D 🠆 1M
1W 🠆 3M
You can use the script's inputs to specify a fixed time period, which you can express in any combination of days, hours and minutes.
By default, the time period currently used is displayed in the lower-right corner of the chart. The script's inputs allow you to hide the display or change its size and location.
Minimum Window Size
This input field determines the minimum number of values to keep in the moving window, even if these values are outside the prescribed time period. This mitigates situations where a large time gap between two bars would cause the time window to be empty, which can occur in non-24x7 markets where large time gaps may separate contiguous chart bars, namely across holidays or trading sessions. For example, if you were using a 1D time period and there is a two-day gap between two bars, then no chart bars would fit in the moving window after the gap. The default value is 10 bars.
█ NOTES
If you are interested in VWAP indicators, you may find the VWAP Auto Anchored built-in indicator worth a try.
For Pine Script™ coders
The heart of this script's calculations uses the `totalForTimeWhen()` function from the ConditionalAverages library published by PineCoders . It works by maintaining an array of values included in a time period, but without a for loop requiring a lookback from the current bar, so it is much more efficient.
We write our Pine Script™ code using the recommendations in the User Manual's Style Guide .
Look first. Then leap.
ConditionalAverages█ OVERVIEW
This library is a Pine Script™ programmer’s tool containing functions that average values selectively.
█ CONCEPTS
Averaging can be useful to smooth out unstable readings in the data set, provide a benchmark to see the underlying trend of the data, or to provide a general expectancy of values in establishing a central tendency. Conventional averaging techniques tend to apply indiscriminately to all values in a fixed window, but it can sometimes be useful to average values only when a specific condition is met. As conditional averaging works on specific elements of a dataset, it can help us derive more context-specific conclusions. This library offers a collection of averaging methods that not only accomplish these tasks, but also exploit the efficiencies of the Pine Script™ runtime by foregoing unnecessary and resource-intensive for loops.
█ NOTES
To Loop or Not to Loop
Though for and while loops are essential programming tools, they are often unnecessary in Pine Script™. This is because the Pine Script™ runtime already runs your scripts in a loop where it executes your code on each bar of the dataset. Pine Script™ programmers who understand how their code executes on charts can use this to their advantage by designing loop-less code that will run orders of magnitude faster than functionally identical code using loops. Most of this library's function illustrate how you can achieve loop-less code to process past values. See the User Manual page on loops for more information. If you are looking for ways to measure execution time for you scripts, have a look at our LibraryStopwatch library .
Our `avgForTimeWhen()` and `totalForTimeWhen()` are exceptions in the library, as they use a while structure. Only a few iterations of the loop are executed on each bar, however, as its only job is to remove the few elements in the array that are outside the moving window defined by a time boundary.
Cumulating and Summing Conditionally
The ta.cum() or math.sum() built-in functions can be used with ternaries that select only certain values. In our `avgWhen(src, cond)` function, for example, we use this technique to cumulate only the occurrences of `src` when `cond` is true:
float cumTotal = ta.cum(cond ? src : 0) We then use:
float cumCount = ta.cum(cond ? 1 : 0) to calculate the number of occurrences where `cond` is true, which corresponds to the quantity of values cumulated in `cumTotal`.
Building Custom Series With Arrays
The advent of arrays in Pine has enabled us to build our custom data series. Many of this library's functions use arrays for this purpose, saving newer values that come in when a condition is met, and discarding the older ones, implementing a queue .
`avgForTimeWhen()` and `totalForTimeWhen()`
These two functions warrant a few explanations. They operate on a number of values included in a moving window defined by a timeframe expressed in milliseconds. We use a 1D timeframe in our example code. The number of bars included in the moving window is unknown to the programmer, who only specifies the period of time defining the moving window. You can thus use `avgForTimeWhen()` to calculate a rolling moving average for the last 24 hours, for example, that will work whether the chart is using a 1min or 1H timeframe. A 24-hour moving window will typically contain many more values on a 1min chart that on a 1H chart, but their calculated average will be very close.
Problems will arise on non-24x7 markets when large time gaps occur between chart bars, as will be the case across holidays or trading sessions. For example, if you were using a 24H timeframe and there is a two-day gap between two bars, then no chart bars would fit in the moving window after the gap. The `minBars` parameter mitigates this by guaranteeing that a minimum number of bars are always included in the calculation, even if including those bars requires reaching outside the prescribed timeframe. We use a minimum value of 10 bars in the example code.
Using var in Constant Declarations
In the past, we have been using var when initializing so-called constants in our scripts, which as per the Style Guide 's recommendations, we identify using UPPER_SNAKE_CASE. It turns out that var variables incur slightly superior maintenance overhead in the Pine Script™ runtime, when compared to variables initialized on each bar. We thus no longer use var to declare our "int/float/bool" constants, but still use it when an initialization on each bar would require too much time, such as when initializing a string or with a heavy function call.
Look first. Then leap.
█ FUNCTIONS
avgWhen(src, cond)
Gathers values of the source when a condition is true and averages them over the total number of occurrences of the condition.
Parameters:
src : (series int/float) The source of the values to be averaged.
cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.
Returns: (float) A cumulative average of values when a condition is met.
avgWhenLast(src, cond, cnt)
Gathers values of the source when a condition is true and averages them over a defined number of occurrences of the condition.
Parameters:
src : (series int/float) The source of the values to be averaged.
cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.
cnt : (simple int) The quantity of last occurrences of the condition for which to average values.
Returns: (float) The average of `src` for the last `x` occurrences where `cond` is true.
avgWhenInLast(src, cond, cnt)
Gathers values of the source when a condition is true and averages them over the total number of occurrences during a defined number of bars back.
Parameters:
src : (series int/float) The source of the values to be averaged.
cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.
cnt : (simple int) The quantity of bars back to evaluate.
Returns: (float) The average of `src` in last `cnt` bars, but only when `cond` is true.
avgSince(src, cond)
Averages values of the source since a condition was true.
Parameters:
src : (series int/float) The source of the values to be averaged.
cond : (series bool) The condition determining when the average is reset.
Returns: (float) The average of `src` since `cond` was true.
avgForTimeWhen(src, ms, cond, minBars)
Averages values of `src` when `cond` is true, over a moving window of length `ms` milliseconds.
Parameters:
src : (series int/float) The source of the values to be averaged.
ms : (simple int) The time duration in milliseconds defining the size of the moving window.
cond : (series bool) The condition determining which values are included. Optional.
minBars : (simple int) The minimum number of values to keep in the moving window. Optional.
Returns: (float) The average of `src` when `cond` is true in the moving window.
totalForTimeWhen(src, ms, cond, minBars)
Sums values of `src` when `cond` is true, over a moving window of length `ms` milliseconds.
Parameters:
src : (series int/float) The source of the values to be summed.
ms : (simple int) The time duration in milliseconds defining the size of the moving window.
cond : (series bool) The condition determining which values are included. Optional.
minBars : (simple int) The minimum number of values to keep in the moving window. Optional.
Returns: (float) The sum of `src` when `cond` is true in the moving window.
Overnight Gap AnalysisThere is a wide range of opinion on holding positions overnight due to gap risk. So, out of curiosity, I coded this analysis as a strategy to see what the result of only holding a position overnight on an asset would be. The results really surprised me. The script backtests 10+ years, and here are the findings:
Holding a position for 1 hour bar overnight on QQQ since January 2010 results in a 545% return. QQQ's entire return holding through the same period is 643%
The max equity drawdown on holding that position overnight is lower then the buy/hold drawdown on the underlying asset.
It doesn't matter if the last bar of the day is green or red, the results are similar.
It doesn't matter if it is a bull or bear market. Filtering the script to only trade when the price is above the 200-day moving average actually reduces its return from 545% to 301%, though it does also reduce drawdown.
I see similar patterns when applying the script to other index ETFs. Applying it to leveraged index ETFs can end up beating buy/hold of the underlying index.
Since this script holds through the 1st bar of the day, this could also speak to a day-opening price pattern
The default inputs are for the script to be applied to 1 hour charts only that have 7 bars on the chart per day. You can apply it to other chart types, but must follow the instructions below for it to work properly.
What the script is doing :
This script is buying the close of the last bar of the day and closing the trade at the close of the next bar. So, all trades are being held for 1 bar. By default, the script is setup for use on a 1hr chart that has 7 bars per day. If you try to apply it to a different timeframe, you will need to adjust the count of the last bar of the day with the script input. I.e. There are 7 bars per day on an hour chart on US Stocks/ETFs, so the input is set to 7 by default.
Other ways this script can be used :
This script can also test the result of holding a position over any 1 bar in the day using that same input. For instance, on an hour chart you can input 6 on the script input, and it will model buying the close of the 6th bar of the day while selling on the close of the next bar. I used this out of curiosity to model what only holding the last bar of the day would result in. On average, you lose money on the last bar every day.
The irony here is that the root cause of this last bar of the day losing may be people selling their positions at the end of day so that they aren't exposed to overnight gap risk.
Disclaimer: This is not financial advice. Open-source scripts I publish in the community are largely meant to spark ideas that can be used as building blocks for part of a more robust trade management strategy. If you would like to implement a version of any script, I would recommend making significant additions/modifications to the strategy & risk management functions. If you don’t know how to program in Pine, then hire a Pine-coder. We can help!
VWAP GapsTheory of untested previous VWAPs acting in similar way to nPOC, where agreed previous 'value' based on volume acts as a liquidity area to be retested.
Indicator shows
- User selected VWAP
- Untested previous VWAPs. The line will disappear once price crosses it's value
- Sweeps of previous VWAPs. Show by both bar colours and plotted arrows under different conditions.
Sweep Filters
1. Bull or Bear Bar (required for an arrow plot)
2. Sweep Conditions i.e. open below line, high above line, and close below line
3. If current VWAP is below/above the previous VWAP value.
datsana V.1datsana ;
script uses analysis of :
- directional price movements ,
- strength / weakness of market,
- volatility
based on these indicators :
- DMI
- RSI & RSI div.
- Bollinger Bands
- Ehlers fisher transform
- DM
in order to find possible bullish / bearish reversals .
this script also uses a ‘deceleration’ system to filter reversal signals :
when a market is considered as too much volatile , then this ´deceleration system’ filters out all signals . ( you can turn off deceleration in the script settings )
you can also manage the ´deceleration density’ : the lower the deceleration density is , the more the filter be strict ( it will filter out more signals )
this indicators prints :
- RSI div. based support / resistance levels .
- bollinger bands
- ema199 / ema299 difference cloud
- liquidity gaps candles pattern ( ‘tkps’)
- possible reversal signals ( small arrows )
- filtered possible reversal signals ( triangles + ‘T’ or ‘B’ letters )
this script works better on low timeframes ( I recommend 15m to 1h TFs )
Prime Distance Frame Quant Model for Risk Reward & Pivot PointsIn this script we take all of the prime numbers up to 100 and plot them as olive lines and then consider the distance between two adjacent plots and color code these distances with the fill function. This allows us to find higher and lower prime gaps allowing us to make much more informed decisions on our risk reward for a given trade and the levels where we should consider taking profit.
The Script includes scaling for all assets and is intended to be used for crypto trading.
Time Locked Moving AverageSuccinct Description
Generates moving average that stays locked to users desired time preference.
Verbose Description
The default moving average indicator does not stay locked to the chart timeframe. Meaning, if you want to see a 1 day SMA on a 15 minute chart, you have to do math and adjust the moving average length to 96.
Needing to do this constantly (especially while flipping through multiple time frames) was really annoying, so I codded up this script to do it for me... and now it can for you too!
Error Handling
If you receive a 'study error' that says, "function sma references too many candles in history".
Go to the Time Locked Moving Average settings and increase the timeframe interval until error goes away.
Furthermore, UNCHECK gaps, to show real-time approximated moving average values.
Enjoy :)
TLS Psychological Levels (GOLD)This script automatically marks out your $5 levels on XAU/USD. Custom gaps can be set in the settings, you can also adjust the height of the bottom line if needed (Then all other levels will follow). -JG
Daily DeviationShows you the normal deviation from the OPEN based upon historical data.
Levels measured:
Normal range (1 standard deviation) of the CLOSE (vs the OPEN).
Normal daily HIGH +1, +2, +3, and +4 standard deviations.
Normal daily LOW -1, -2, -3, and -4 standard deviations.
Configuration:
Always shows you the normal CLOSE vs OPEN range for the current session.
Can display previous day's ranges (extra days) based upon the calendar (not trading days).
Normally displays which levels have been exceeded (to reduce noise and keep auto-scale to a minimum), but can show all the ranges for the current session.
The default number of days to measure (50) will affect the accuracy but outliers are cleaned to avoid dramatic variance.
Note:
These are only statistical representations of what has occurred in the past. You can interpret the current price as oversold or overbought for the day (and only that day) relative to the OPEN. Gaps high or low are not considered in the equation.
GMT Offset, without using security fn - showcaseThis script is a demo of how one can avoid the use of the request.security function and get values for a number of previous day's open/high/low/close
where the user can define a custom "start of the day" using the GMT input. This allows the user to be independent of the exchange timezone
that the security function uses internally.
Implications of this include:
Suppose you want to treat the start of your day as the NZX market open which is at 2000 UTC+0 and base you indicator calculations
on the NZK market midnight as opposed to the chart exchange timezone.
The indicator purpose is to showcase how that can be achieved in code.
If security function in the future is modified to accept a timezone parameter - obviously this code will no longer be needed as such.
We do two things here:
We plot the values for open high low close using the calc_ohlc_daysback as circles
Then we use the f_security function to get the same values but using security and plot them using solid lines
We do this both on the daily and weekly values.
What we expect to see is the lines matching thus proving that the calc_ohlc_daysback works correctly as compared to security function.
Note - the chart gmt default value is set to 0 which means the comparison will work correctly out of the box on exchanges that have weekend data.
The script is designed to work on intraday timeframes highest being 4 hour and lowest being 3 min
(programmatically the script is no bounded as sich to the intraday timeframe however if not enough data is present at a particular timeframe
values needed to display the lines will be null and hence the lines will not print.)
You can get the same results on other exchanges but might need to change the value of chart gmt
Script does not work on exchanges that have gaps on the weekend at this time
Now all of this can obviously be done with the security function - why go through the trouble? Well with security function you are bound to
the timezone of the exchange you are on. Doing it this way you are no longer bound by the exchange timezone and you can effectively change
the time at which the day starts independent of any exchange. Go ahead - change the GMT offset in settings
Future enhancements:
a) Deal with exchanges where "bar merge" is required - if possible (detect that an exchange does not have weekend data basically)
b) Deal with lower timeframes if possible (on the minute timeframe there is usually not enough data in the series to calc values several weeks back)
c) Make a library for this functionality - this will be optimal so one does not need to copy paste code.
d) Expand library to add GMT auto adjust (specifically around DST in different countries). Today this is a challenge as no relizble way exists to
extract the UTC offset from an syminfo.timezone given that syminfo.timezone returns text such as "America/New York"
For example - one might have 3 session thst they want to work with. Tokio, London and New York. Tokio does not follow DST so the market session starts at the same time all year round. London observes DST but at a different time from New York. So in order to have all this in the same chart and have it auto adjust is a bit of a challenge. With the DST offset functions - this is possible to do. (
Well, that is unless the awesome TV devs push out v6 where that is build in the security function (for it to accept a timezone offset other) in which case the code here will become useless.
Foot notes:
This script is inspired by Traders Reality indicator by @infernixx (developed by @plasmapug with additional modifications by @infernixx and @Peshocore)
Special thanks to @JayRogers for INSECURITY() which inspired the development of calc_ohlc_daysback
Elder Impulse System + ATR BandsDisregard the above chart, I am not sure why it isn't showing the one I want, which is linked below:
This is as far as I can tell the closest representation to Dr. Alexander Elder's updated "Elder Impulse System" that has added ATR-volatility bands up to 3x deviations from price. I got the idea from watching this recent video (www.youtube.com) of Dr. Elder reviewing some recent trades and noticed he had updated his system from his original books. The Impulse System colour coding was inspired by AstralLoverFlow and LazyBear. ATR Bands are pre-programmed Keltner Channels with some modifications such as filing in the ATR Zones with user-selected colour bands and modifying the ATR value to better suit the volatility of the market being traded.
The script has several components, which I will detail below:
Exponential Moving Averages:
1) A 13-period EMA that is used as a staple in all of Dr. Elder's technical analysis. He uses this EMA as the basis for all of his indicators and why it is included here.
2) A 26-period EMA which can be used as a base-line of sorts to filter when to go long or when to go short. For instance, price over the 26-EMA, price is strong and the rally upwards is likely to continue, underneath it, price is weak and likely to continue downwards for a time.
Volatility Bands:
By definition these are nothing more than 3 separate Keltner Channels of a 13-period EMA each set to one additional multiplier from the moving average. This gives us a 1x, 2x, and 3x multiplier of average volatility from the 13-period EMA based on a 14-period Average True Range (ATR) reading. The ATR was chosen as it accommodates price gaps and also is the standard formula calculation in TradingView. The values of the bands cannot be adjusted but the colour coding of them can be.
Elder Impulse System:
These colour-coded bars show you the strength and direction of the current chart resolution, calculated by the slope of a 13-period EMA and the slope of a MACD histogram. These are used not as a buying or selling recommendation alone but as trend filters, as per Dr. Elder's own description of them.
Green Bars = The 13-period EMA is sloping positively and the MACD histogram is rising compared to previous bars. The trader should only consider buying/long opportunities when a green bar is most recent.
Red Bars = The 13-period EMA is sloping negatively and the MACD histogram is falling compared to previous bars. The trader should only consider selling/short opportunities when a red bar is most recent.
Blue Bars = The 13-period EMA and the MACD histogram are not aligned. One of the indicators is sloping opposite to the other indicator. These are known as indecision bars and are typically seen near the end of a previously established trend. The trader can choose to wait for either a green or red bar to shape their trading bias if they are more risk-averse while a counter-trend trader may decide to try opening a position against the currently-established trend.
How To Trade the System:
This system is unique in that it is so versatile and will fit the styles of many traders, be it trend following traders (generally the original Elder Impulse System design) or mean-reversion/counter-trend trading (the original Keltner Channel design). None of the examples below or in the chart above are financial advice and are just there for demonstration purposes only.
1) The most basic signal given would be the moving average cross up or down. A cross of the 13-EMA over the 26-EMA signals upward trend strength and the trader could look for buying opportunities. Conversely, the 13-EMA under the 26-EMA shows downward trend strength and the trader could look for selling opportunities.
2) Following the Elder Impulse system in conjunction with the EMAs. Look for long opportunities when a green bar is printed and price is over both of the 13- and 26-period EMAs. Look for short opportunities when a red bar is printed and price is below both of the 13- and 26-period EMAs. Keep in mind this does not necessarily need a moving average cross to be viable, a green or red bar over both EMAs is a valid signal in this system, usually. Examine price more closely for better entry signals when a blue bar is printed and price is either above or below both EMAs if you are a trend trader. This is how Dr. Elder originally intended the system to be used in conjunction with his famous Triple Screen Trading System. I am not going into detail here as it is a deep subject but I would suggest an interested trader to examine this Triple Screen System further as it is widely accepted as a strong strategy.
3) Mean Reversion and Counter-Trend Trading. Dr. Elder mentions that the zone between the two EMAs is called the Value Zone. A mean reversion trader could look for buying opportunities if price has generally been in an uptrend and falls back to value, conversely, they could look for shorting opportunities if price has generally been in a downtrend and rises back to value. These are your very basic pull backs found in trends that create your higher lows in an uptrend or your lower highs in a downtrend. A mean reversion/scalper trader may also look to use the upper and lower most ATR bands as an indication of price being overbought or oversold and could look to enter a counter-trend trade here once a blue indecision bar is printed and to ride that move back down to the Value Zone.
Taking Profits and Risk Management
This system again is very versatile and will fit a wide range of trading styles. It has built in take profit levels and risk management depending on your style of trading.
1a) In original Triple Screen Trading (and the original Elder Impulse system), a trader was to place a buy order one tick above a newly printed green bar with a stop loss one tick below the most recent 2-day low, and vice-versa for red bars on short selling. as long as other criteria were met, that I will not go into. It is all over YouTube and in his books and on Investopedia if you want more information. The general idea is to continue the trend in the direction if price is strong and you are bought into that move with a close stop, or if price falls back a little bit, you can get in at a better price. This would be a system typically better suited to a scalper.
1b) The updated risk management according to the above video is to place a stop loss at least 2ATR away from price. These bands already have calculated these values so a trader can place a stop one tick below the 2 or even 3ATR zones depending on their risk appetite. This is assuming you have already received a strong buy signal based on the system you follow. This would be a system typically better suited to a trend-trader.
2a) Taking profits if you are a trend trader has several possibilities. The first, as Dr. Elder suggests, is to place a price target 2ATR values away from your entry giving you approximately a 1:1 risk-reward ratio.
2b) The second possibility if the trade is successful is to ride the trend upwards until a blue bar is printed, suggesting indecision in the market. A modified version of this that could let a winning trade run longer is to wait for the price to close under the 13-EMA in fast markets, or close under the 26-EMA in slightly slower markets to maximize potential winnings.
2c) A scalper trader may wish to have a target at either the value zone if they are playing an extended buy/short back to the mean, or if they are being at the mean, to sell or cover when price extends back out to the 2x or 3x zone.
3) Trend traders can additionally use the ATR zones as a sort of safety guidelines for entering a trade. Anything within the 1ATR zone is typically a safer entry as the market is less volatile at this time. Entering when price has gone into the 2ATR zone is signaled as a strong momentum move and can signal a stronger move in the direction of the current closing bar. While not always the case, it is suggested by Dr. Elder to not enter trend trades at the 3ATR zone as this is where you will be likely looking for a counter-trend retracement back to value and a trader entering here in the direction of the trade has a higher chance of being stopped out or not getting in at the best possible price.
Special Time PeriodWith this indicator, you can choose candles in the period you want on your chart.
How ?
• If your chart is 5 minutes, the duration should be greater than 5 on this indicator.
If you do not do it this way, there will be gaps in the price, it will not give the right result.
• If you want to see it in minutes, you must enter a direct numerical value. For example, to see 2 hours, you must enter the number 120. Because 2 hours is 120 minutes.
Like the warning above, if you want to plot a 2-hour chart with this indicator, a maximum of 1 hour should be selected on your main chart.
• Resolution, eg. '60' - 60 minutes, 'D' - daily, 'W' - weekly, 'M' - monthly, '5D' - 5 days, '12M' - one year, '3M' - one quarter
• For example, if you want to see the 2-day chart, you should have a maximum of 1 day chart open on your home screen and write "2D" to the indicator value.
• You will get much better results if the period on your main chart and the period on this indicator are multiples of each other.
• In the image below, the period on the main chart is 30 minutes, but the period on the indicator is 90
• Click on the facing brackets at the top right of the legend and your chart will enlarge.
MTF WatchList Charts [Anan]█ OVERVIEW
I am happy to present this script with a nice idea!
You can now customize a watchlist with your preferred time frame and any symbol from any market.
The main purpose is to be aware of any moves and watch a brief overview of the chart.
█ FEATURES
- 8 customizable symbols with the option to show/hide anyone
- Multi time frame support
- 3 Types of charts (Candles / Heikin Ashi / Line)
- Displaying up to 10 candles for every chart
- Customizable chart colors
- Option to Show/hide Price
- Option to Show/hide Price Line
- Option to change Labels and Text Size
- Show Symbol name and used time frame
- Option to change gaps between charts
- Hover over on the top of any candle to see (Open/High/Low/Close) Prices
█ SCREENSHOTS
-----------------------------------------------
Special thanks to @dgtrd for inspiration and for the amazing framework used here ( HTF Candles by DGT )
Special thanks to Pine Chat @fareidzulkifli @Bjorgum @JohnBaron @fpainchaud
Gap Indicator (Ruscio)Gap Indicator
This indicator allows you to view the market gaps on any underlying, and check through the statistics panel how many times the stock closes the session in the direction of the opening gap.
CME Gap BTCThis script highlights the CME gap. It takes the daily close from Friday from CME Futures Bitcoin security (can be switched) and plots the difference from current close.
With the premise that CME gaps will be filled next week; when the current close is higher than Friday close, it plots a bear color, when the current close is lower, it plots a bull color. Colors can be changed
Single Prints - Session Initial BalancesDisclaimer: Expose yourself to the knowledge of different trading methods. If you are unaware of what a Single Print is then do some research and broaden your knowledge.
This indicator has only been tested on BTCUSDT Binance pair. This indicator is meant to be used on the 30 minute timeframe to highlight Single Prints.
The calculations are base on 0000 UTC and what Single Prints are created during that day.
Single Prints
Single Prints are where prices moves to fast through an area (on a 30 minute timeframe), in the case of this indicator in $50 intervals, where the price has not yet cross back past, represented as orange lines. If you were viewing this on a Time Price Opportunity Chart (TPO) each $50 would be represented as a square with a letter in it. If price has only been through that area once, within that 24 hour period, then it is called a Single Print. If however the Single Print is on the lower wick of the candle it is called a Buying Tail and on the Upper Wick a Selling Tail.
Single Prints leave low volume nodes with liquidity gaps, these inefficient moves tend to get filled, and we can seek trading opportunities once they get filled, or we can also enter before they get filled and use these single prints as targets.
Single Prints are a sign of emotional buying or selling as very little time was spent at those levels and thus there is no value there.
The endpoints of single print sections are considered to be potential support or resistance points and or get filled (like a CME gap).
The above is only a very short summary, to understand Single Prints, Buying Tails and Selling Tails more please do your own research (DYOR).
References:
Trading Riot Volume Profile - Website
TOROS TPO Charts Explained - Youtube
Session Boxes
Session Boxes are the high and low of that markets session before the new market session opens. I used the data from the website Trading Hours for the time input.
White box – Start of day UTC 0000 to Market Close UTC 2000
Purple box – Asia Start UTC 0130 to London Start UTC 0700
Yellow box – London Start UTC 0700 to New York Start UTC 1330
Blue box – New York Start UTC 1330 to Market Close UTC 2000
Red box – Market Close UTC 2000 to End of day UTC 2359
References:
Trading Hours - Website
Initial Balance
The Initial Balance is the market range between the high and low of the first hour of trading for the market. In the case of crypto when is the Initial Balance if it is 24/7.
Context of Initial Balance:
The Initial Balance is traditionally the range of prices transacted in the first hour of trade. Many regard the Initial Balance as a significant range because, especially for the index futures which are tied to the underlying stocks, orders entered overnight or before the open are typically executed prior to the end of the first hour of trade. Some use it to understand how the rest of the day may develop, while others use it as a span of time to avoid trading altogether because of its potential volatility.
For this indicator I have coded the Initial Balance time as below:
White Box - To appear for the first hour of the day 0000 to 0100 UTC .
Purple Box - To appear for the first hour of the day 0130 to 0230 UTC .
Yellow Box - To appear for the first hour of the day 0700 to 0800 UTC .
Blue Box - To appear for the first hour of the day 1330 to 1430 UTC .
Red Box - To appear for the first hour of the day 2000 to 2100 UTC .
The diagram above shows some examples:
How price (white arrows) retraces the single prints.
How price (red arrows) uses the single prints as S/R.
References:
Not Hard Trading – Website
My Pivots Initial Balance - Website
Thanks go to:
StackOverFlow Bjorn Mistiaen
Trading View user mvs1231
Please message me if you have any feedback/questions.
I am looking at developing this indicator further in the future.
Net VolumeNet Volume, or NV in short, is a cumulative volume indicator similar to OBV and A/D. Though it might look similar to these two indicators (especially A/D), rest assured it's better and more accurate than both. What it basically does, is dividing the volume session into buyers and sellers volumes; then subtracts former from the latter and adds the result to previous session's net volume (In the script, these two intermediate volumes are not calculated and only the subtraction is formulated in an integrated form).
Another important difference between NV and A/D indicator, is that it brings price gaps into account. That's why it requires next session's open price to calculate current session's NV. What it actually mean is that the price gap, in either direction, is the result of the traders' efforts in respective direction in previous session, as if the current session closes where next session opens.
Imbalance FinderImbalance Finder
I struggled to always see it visually this marks whether there is or isn't imbalance
Very quick way of finding imbalance between bars
HTF Candles by Prosum SolutionsOverview of Features
This indicator was inspired by the work of "informanerd" in the script called "HTF Candles" as well as the built-in script called "Multi-Time Period Charts" by TradingView. The script will provide a highly customizable interface to specify the higher timeframe resolution for the candlesticks, the type of candle, as well as various styling options for the body, borders and wicks.
Usage Information
The indicator can be applied to any chart at any time frame, but resolutions less than 1 minute may demonstrate gaps between bars and the candles may not render properly.
When the "Same as chart" option is chosen for the "Resolution" field, the indicator will attempt to find a higher timeframe resolution to ensure the candlesticks are drawn.
Enjoy! 👍
How to use Leverage and Margin in PineScriptEn route to being absolutely the best and most complete trading platform out there, TradingView has just closed 2 gaps in their PineScript language.
It is now possible to create and backtest a strategy for trading with leverage.
Backtester now produces Margin Calls - so recognizes mid-trade drawdown and if it is too big for the broker to maintain your trade, some part of if will be instantly closed.
New additions were announced in official blogpost , but it lacked code examples, so I have decided to publish this script. Having said that - this is purely educational stuff.
█ LEVERAGE
Let's start with the Leverage. I will discuss this assuming we are always entering trades with some percentage of our equity balance (default_qty_type = strategy.percent_of_equity), not fixed order quantity.
If you want to trade with 1:1 leverage (so no leverage) and enter a trade with all money in your trading account, then first line of your strategy script must include this parameter:
default_qty_value = 100 // which stands for 100%
Now, if you want to trade with 30:1 leverage, you need to multipy the quantity by 30x, so you'd get 30 x 100 = 3000:
default_qty_value = 3000 // which stands for 3000%
And you can play around with this value as you wish, so if you want to enter each trade with 10% equity on 15:1 leverage you'd get default_qty_value = 150.
That's easy. Of course you can modify this quantity value not only in the script, but also afterwards in Script Settings popup, "Properties" tab.
█ MARGIN
Second newly released feature is Margin calculation together with Margin Calls. If the market goes against your trades and your trading account cannot maintain mid-trade drawdown - those trades will be closed in full or partly. Also, if your trading account cannot afford to open more trades (pyramiding those trades), Margin mechanism will prevent them from being entered.
I will not go into details about how Margin calculation works, it was all explainged in above mentioned blogpost and documentation .
All you need to do is to add two parameters to the opening line of your script:
margin_long = 1./30*50, margin_short = 1./30*50
Whereas "30" is a leverage scale as in 30:1, and "50" stands for 50% of Margin required by your broker. Personally the Required Margin number I've met most often is 50%, so I'm using value 50 here, but there are literally 1000+ brokers in this world and this is individual decision by each of them, so you'd better ask yourself.
--------------------
Please note, that if you ever encounter a strategy which triggers Margin Call at least once, then it is probably a very bad strategy. Margin Call is a last resort, last security measure - all the risks should be calculated by the strategy algorithm before it is ever hit. So if you see a Margin Call being triggred, then something is wrong with risk management of the strategy. Therefore - don't use it!
Crypto Tripple RSIGives an ability to compare 3 RSIs:
current altcoin + BTC (e.g. ADABTC) - green by default
current pair (e.g. ADAUSDT) - blue by default
BTC (e.g. BTCUSDT) - yellow by default
It helps to understand the cause of price change - whether BTC provokes price change or not. Also it shows performance of an altcoin - the bigger gaps between RSIs, the stronger (RSI of BTC is on the bottom)/ weaker (RSI of BTC is on the top) altcoin is.
FibFans on Previous HTF HL [FaizanNawaz] by DGTFibonacci Fans application on top of Previous Higher TimeFrame High and Low. Idea owner is @faizannawaz1, special thanks to him for both the idea and tesing the application
WARNING : Study includes plottings in the future, and due to temporal gaps in non 7/24 markets such as weekends, holidays etc plotting of the fans will move to the open session (the effect will be observed on Friday and Monday). With crypto no any side affect will be observed.
More about Fibonacci Fans, how to apply fibonacci fans and automated fibonacci speed and resistance fans study
Adiitonally the study includes some addons, such as
Central Pivot Range and Traditional Pivot Points
Volume Weighted Colored Bars
Price Range Meter - Horizontal HTF Candle
Disclaimer :
Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely
The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold dgtrd TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script
