Rozpocznij

Wskaźnik Wolumenu

Lancelot ATR Volume MeterThis is an experiment I did a while back ago. I often think On Balance Volume is a great indicator as trend direction and volume cannot lie. However, I bumped into a few problems. It is slow, doesn't show volatility and often time it is prone to chop. That's why I added ATR to the equation. Original OBV calculation src > 0? : +volume : src < 0? -volume Modified OBV with ATR src > 0 ? +volume * (volume / atr) : src < 0? -volume * (volume / atr) I have used 2 ema for this modified OBV. ema 3 ema 18 By adding ATR to the equation we can smooth out many erratic price movement. (Stop hunting) Also, when price move slowly but steady, often prepping for a big move, this indicator will move faster. In short, this indicator prevents you from being stop hunted and also provide great entry for a trending market. Works well on BTCUSD XBTUSD, as well as other major liquid Pair. Feel free to follow me on Twitter @Lancelot_Auger for more free Alpha. Please acknowledge my effort by like and follow. And lastly, Save Hong Kong, the revolution of our times.
Wskaźnik Pine Script™
od Lancelot_Augur
19
Volume Weighted DistanceThis script holds several useful functions from statistics and machine learning (ML) and takes measurement of a volume weighted distance in order to identify local trends. It attempts at applying ML techniques to time series processing, shows how different distance measures behave and gives you an arsenal of tools for your endeavors. Tested with BTCUSD. REM: oddly enough, many people forget that the scripts in PS are generally just STUDIES, i.e. exercises, experiments, trials, and do not embody a final solution. Please treat them as intended ;))
Wskaźnik Pine Script™
od capissimo
2
Delta Volume Columns [LucF]Displays delta volume columns using intrabar volume information. Each volume column is divided into three sections: buying, selling and neutral volume. Volume for each section is determined from the volume and price movement of each intrabar at a user-selected lower resolution. Features include: - Choice of color themes for either dark or light chart backgrounds - Delta volume columns - Volume Balance displayed as the difference between the MAs of buying and selling volume - Display of divergences between a bar’s volume balance and the bar’s price movement (example: buying volume > selling volume but close < open). Divergences can be shown in 2 different color schemes (including green/red showing a tentative direction), on volume columns and/or on chart bars - Display of bar by bar volume balance with highlighting of above average volume - Display of the usual total volume MA - Choice of the lower resolution used to retrieve intrabar information - Alerts configurable on any combination of the markers, with control over long/short direction - Choice of 3 different markers: 1. Double bumps: two consecutive bars where buying or selling volume is in the same direction and where volume > volume MA 2. Divergence confirmations: direction of the price bar following a price/volume balance divergence 3. Volume balance shifts: zero level crossings of the volume balance MA delta The chart shows the two main modes of display: - Top pane : shows the stacked volume columns with divergences in orange and the flattened volume balance MAs delta at the bottom of the volume columns. This volume balance is the same shown in the bottom pane. The top pane also shows the instant volume balance strip above the volume columns. The strip’s colors show which of the buying or selling volume was greater, and colors are brighter if the total volume was above the total volume MA. - Bottom pane : shows the volume balance MAs delta with markers 1 and 2. Given that this graphic has no price momentum component, I find quite eerie how it often looks like a momentum-based signal. The default 5 minute intrabar resolution is used in combination with the weekly chart, which is excessive. This script uses a special characteristic of the security() function’s behavior when it is sent to a resolution lower than the chart’s resolution. Details are given in the script’s comments. This method has the advantage of working under more circumstances than some of the other loop-based methods, but it also has its limits. IMPORTANT This is what you need to know: - The method used does not work on the realtime bar—only on historical bars. Consequently, the volume column shown on the realtime bar is a normal volume column plotted in green or red, following price movement. The column will only show delta volume information after it closes and becomes a historical bar. - The indicator only works on some chart resolutions: 5, 10, 15 and 30 minutes, 1, 2, 4, 6, and 12 hours, 1 day, 1 week and 1 month. The script’s code can be modified to run on other resolutions, but chart resolutions must be divisible by the lower resolution used for intrabars. - Intrabar resolutions can be selected from 1, 5, 15, 30, 45 minutes, 1, 2, 3, 4 hours, 1 day, 1 week and 1 month. The intrabar resolution must of course be smaller than the chart’s resolution. - Contrary to my other indicators where alerts must be configured to trigger “Once Per Bar Close” in order to avoid false triggers (or repainting), all this indicator’s alerts are designed to trigger using previous bar information since the indicator’s calculations in the realtime bar are not exact. Markers are not plotted with a negative offset; they appear at the beginning of the realtime bar following confirmation of the marker’s condition on the previous bar. Alerts for this indicator should thus be configured to trigger “Once Per Bar” so they trigger at the beginning of the realtime bar. Note that the penalty is not that great, as it is simply the instant between the close of the previous realtime bar and the opening of the next. The advantage of using this technique is that the indicator does not repaint; a marker that appears at the beginning of the realtime bar will never disappear. - The script only plots information that is reliable in the realtime bar, i.e., total volume and markers. All other plots are set to n/a to prevent misleading traders. - When the difference between the chart’s resolution and the lower resolution is too important, volume columns will not calculate for all bars in the dataset. On Delta Volume Buying or selling volume are misnomers, as every unit of volume transacted is both bought and sold by 2 different traders. There is no such thing as “buy only” or “sell only” volume, but trader lingo is riddled with original fabulations. Without access to order book information, traders work with the assumption that when price moves up during a bar, there was more buying pressure than selling pressure. The built-in volume indicator available on TradingView uses this logic to color the volume columns green or red. While this script’s numbers are more precise because it analyses a number of intrabars to calculate its information, it uses the exact same imperfect logic to calculate its buying/selling/neutral sections. Until Pine scripts can have access to how much volume was transacted at the bid/ask prices, our so-called buying/selling volume information will always be a mere proxy. Divergences You may wonder how there can be divergences between buying/selling volume information and price movement. This will sometimes be due to the methodology’s shortcomings we have just discussed, but divergences may also occur in instances where because of order book structure, it takes less volume to increase the price of an asset than it takes to decrease it. As usual, divergences are points of interest because they reveal imbalances, which may or may not become turning points. I do not share the overwhelming enthusiasm traders have for divergences. To your pattern-hungry brain, the orange bars this indicator shows on chart will—as divergences on other indicators do–appear to often indicate turnarounds. My opinion is that reality is generally quite sobering, as many who have tried building automated rules based on divergences will tell you. I do not have hard numbers on the lack of performance of divergences—only many failed attempts to make them perform, which a few experienced strategy modelers I know share with me. Please don’t try to read too much into them. While they look great on past data, I find they are often difficult to use in realtime to make bets with good odds. Thanks to: - A guy called Kuan who commented on a Backtest Rookies presentation of an intrabar delta volume indicator using a for loop. The heart of “my” indicator is code borrowed from Kuan; I just built a hopefully useful wrapper around it. - @theheirophant, my partner in the exploration of the sometimes weird abysses of security() ’s behavior at lower resolutions.
Wskaźnik Pine Script™
od LucF
69
Volume multiple indicatorThis indicator shows when the volume is extraordinary increased or decreased. You can change *multiple*, default is 2. When today's volume is multiple times greater than yesterday's volume, background is green (regardless of close price. It is related to just volume) Black means today's volume is multiple times smaller than yesterday's volume. 간단하게 거래량 급증과 급락을 알려주는 지표입니다. multiple을 조절할 수 있고, 기본값은 2배 입니다. 오늘거래량이 어제거래량보다 2배 많으면 배경색이 초록색이 됩니다. 배경색이 검정색이 된다면, 오늘 거래량이 어제 거래량보다 2배 적다는 뜻입니다.
Wskaźnik Pine Script™
od Lee.SeongGwan
1
Volume Flow v3DepthHouse Volume Flow indicator is used to help determine trend direction strictly based on Negative and Positive volume data. How to Read: - Moving Average crossovers are used to help determine a possible trend change or retracement. - The area cloud on the bottom is calculated by the difference of the moving averages. This could be used to help determine the trending volume strength. - Bright colored volume bars are large volume spikes calculated by the x factor in the options. Other changes: - DepthHouse is going open source with numerous of its indicators. This is only one of many! - Volume is now displayed without being altered for calculations.
Wskaźnik Pine Script™
od oh92
38
Volume Profile Free Ultra SLI (100 Levels Value Area VWAP) - RRBVolume Profile Free Ultra SLI by RagingRocketBull 2019 Version 1.0 This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 100 horizontal bars. This is basically the MAX SLI version with +50 more Pinescript v4 line objects added as levels. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are several versions: Free Pro, Free MAX SLI, Free Ultra SLI, Free History. This is the Free Ultra SLI version. The Differences are listed below: - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX SLI: 50 levels, 2x SLI modes for Buy/Sell or even higher res 150 levels - Free Ultra SLI: 100 levels, packed to the limit, 2x SLI modes for Buy/Sell or even higher res 300 levels - Free History: auto highest/lowest, historic poc/va levels for each session Features: - High-Res Volume Profile with up to 100 levels (line implementation) - 2x SLI modes for even higher res: 300 levels with 3x vertical SLI, 100 buy/sell levels with 2x horiz SLI - Calculate Volume Profile on full history - POC, Developing POC Levels - Buy/Sell/Total volume modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels, Transparency for buy/sell levels WARNING: - Compilation Time: 1 min 20 sec Usage: - specify max_level/min_level/spacing (required) - select range (start_bar, range length), confirm with range highlighting - select volume type: Buy/Sell/Total - select mode Value Area/VWAP to show corresponding levels - flip/select anchor point to position the buy/sell levels - use Horiz Buy/Sell SLI mode with 100 or Vertical SLI with 300 levels if needed - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. SLI: use SLI modes to extend the functionality of the indicator: - Horiz Buy/Sell 2x SLI lets you view 100 Buy/Sell Levels at the same time - Vertical Max_Vol 3x SLI lets you increase the resolution to 300 levels - you need at least 2 instances of the indicator attached to the same chart for SLI to work 1) Enable Horiz SLI: - attach 2 indicator instances to the chart - make sure all instances have the same min_level/max_level/range/spacing settings - select volume type for each instance: you can have a buy/sell or buy/total or sell/total SLI. Make sure your buy volume instance is the last attached to be displayed on top of sell/total instances without overlapping. - set buy_sell_sli_mode to true for indicator instances with volume_type = buy/sell, for type total this is optional. - this basically tells the script to calculate % lengths based on total volume instead of individual buy/sell volumes and use ext offset for sell levels - Sell Offset is calculated relative to Buy Offset to stack/extend sell after buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - there are no master/slave instances in this mode, all indicators are equal, poc/va levels are not affected and can work independently, i.e. one instance can show va levels, another - vwap. 2) Enable Vertical SLI: - attach the first instance and evaluate the full range to roughly determine where is the highest max_vol/poc level i.e. 0..20000, poc is in the bottom half (third, middle etc) or - add more instances and split the full vertical range between them, i.e. set min_level/max_level of each corresponding instance to 0..10000, 10000..20000 etc - make sure all instances have the same range/spacing settings - an instance with a subrange containing the poc level of the full range is now your master instance (bottom half). All other instances are slaves, their levels will be calculated based on the max_vol/poc of the master instance instead of local values - set show_max_vol_sli to true for the master instance. for slave instances this is optional and can be used to check if master/slave max_vol values match and slave can read the master's value. This simply plots the max_vol value - you can also attach all instances and set show_max_vol_sli to true in all of them - the instance with the largest max_vol should become the master Auto/Manual Ext Max_Vol Modes: - for auto vertical max_vol SLI mode set max_vol_sli_src in all slave instances to the max_vol of the master indicator: "VolumeProfileFree_MAX_RRB: Max Volume for Vertical SLI Mode". It can be tricky with 2+ instances - in case auto SLI mode doesn't work - assign max_vol_sli_ext in all slave instances the max_vol value of the master indicator manually and repeat on each change - manual override max_vol_sli_ext has higher priority than auto max_vol_sli_src when both values are assigned, when they are 0 and close respectively - SLI is disabled - master/slave max_vol values must match on each bar at all times to maintain proper level scale, otherwise slave's levels will look larger than they should relative to the master's levels. - Max_vol (red) is the last param in the long list of indicator outputs - the only true max_vol/poc in this SLI mode is the master's max_vol/poc. All poc/va levels in slaves will be irrelevant and are disabled automatically. Slaves can only show VWAP levels. - VA Levels of the master instance in this SLI mode are calculated based on the subrange, not the whole range and may be inaccurate. Cross check with the full range. WARNING! - auto mode max_vol_sli_src is experimental and may not work as expected - you can only assign auto mode max_vol_sli_src = max_vol once due to some bug with unhandled exception/buffer overflow in Tradingview. Seems that you can clear the value only by removing the indicator instance - sometimes you may see a "study in error state" error when attempting to set it back to close. Remove indicator/Reload chart and start from scratch - volume profile may not finish to redraw and freeze in an ugly shape after an UI parameter change when max_vol_sli_src is assigned a max_vol value. Assign it to close - VP should redraw properly, but it may not clear the assigned max_vol value - you can't seem to be able to assign a proper auto max_vol value to the 3rd slave instance - 2x Vertical SLI works and tested in both auto/manual, 3x SLI - only manual seems to work (you can have a mixed mode: 2nd instance - auto, 3rd - manual) Notes: - This code uses Pinescript v3 compatibility framework - This code is 20x-30x faster (main for cycle is removed) especially on lower tfs with long history - only 4-5 sec load/redraw time vs 30-60 sec of the old Pro versions - Instead of repeatedly calculating the total sum of volumes for the whole range on each bar, vol sums are now increased on each bar and passed to the next in the range making it a per range vs per bar calculation that reduces time dramatically - 100 levels consist of 50 main plot levels and 50 line objects used as alternate levels, differences are: - line objects are always shown on top of other objects, such as plot levels, zero line and side cover, it's not possible to cover/move them below. - all line objects have variable lengths, use actual x,y coords and don't need side cover, while all plot levels have a fixed length of 100 bars, use offset and require cover. - all key properties of line objects, such as x,y coords, color can be modified, objects can be moved/deleted, while this is not possible for static plot levels. - large width values cause line objects to expand only up/down from center while their length remains the same and stays within the level's start/end points similar to an area style. - large width values make plot levels expand in all directions (both h/v), beyond level start/end points, sometimes overlapping zero line, making them an inaccurate % length representation, as opposed to line objects/plot levels with area style. - large width values translate into different widths on screen for line objects and plot levels. - you can't compensate for this unwanted horiz width expansion of plot levels because width uses its own units, that don't translate into bars/pixels. - line objects are visible only when num_levels > 50, plot levels are used otherwise - Since line objects are lines, plot levels also use style line because other style implementations will break the symmetry/spacing between levels. - if you don't see a volume profile check range settings: min_level/max_level and spacing, set spacing to 0 (or adjust accordingly based on the symbol's precision, i.e. 0.00001) - you can view either of Buy/Sell/Total volumes, but you can't display Buy/Sell levels at the same time using a single instance (this would 2x reduce the number of levels). Use 2 indicator instances in horiz buy/sell sli mode for that. - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed length. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Width - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors from input (only transparency) - this requires 2x plot outputs => 2x reduces the number of levels to fit the max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - You can change level transparency of line objects. Due to Pinescript limitations, only discrete values are supported. - Inverse transp correlation creates the necessary illusion of "covered" line objects, although they are shown on top of the cover all the time - If custom lines_transp is set the illusion will break because transp range can't be skewed easily (i.e. transp 0..100 is always mapped to 100..0 and can't be mapped to 50..0) - transparency can applied to lines dynamically but nva top zone can't be completely removed because plot/mixed type of levels are still used when num_levels < 50 and require cover - transparency can't be applied to plot levels dynamically from script this can be done only once from UI, and you can't change plot color for the past length bars - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input to change it - Range selection/Anchoring is not accurate on charts with time gaps since you can only anchor from a point in the future and measure distance in time periods, not actual bars, and there's no way of knowing the number of future gaps in advance. - Adjust Width for Log Scale mode now also works on high precision charts with small prices (i.e. 0.00001) - in Adjust Width for Log Scale mode Level1 width extremes can be capped using max deviation (when level1 = 0, shift = 0 width becomes infinite) - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume P.S. I am your grandfather, Luke! Now, join the Dark Side in your father's steps or be destroyed! Once more the Sith will rule the Galaxy, and we shall have peace...
Wskaźnik Pine Script™
od RagingRocketBull
109
Pump|Dump Tickerthis is just a study to investigate the pumps and dumps that have been happened in a crypto market and it should not be used as an indicator. this is also my very first Pine Script that I've written and I am sure it is not perfect. actually I am curious to know when (I mean the exact time of the day) most pumps and dumps happen as a self investigation. the method that is used to define pumps and dumps is not good (and I know that) but I will modify it for better result in next version. to use this study, you should define whether you want to display pumps or dumps or both and also you should define percent of change (threshold).
Wskaźnik Pine Script™
od ehsanha
Momentum - Multi Timeframe [WYCKOFF ARSENAL]WYCKOFF ARSENAL is now available on TradingView! Based on <> (Richard D. Wyckoff) Noted Indicators: ▪ Optimism Pessimism Index ▪ Force Index ▪ Technometer ▪ Momentum ◄ Main Features: ▪ Multi Timeframe is available ▪ Volume based indicators ▪ Can be used on pairs that have volume data ──────────────────────────── Highlights > Optimism Pessimism Index or OP The value of the OP is not important. The action of the OP is important. The action of the index must be compared to its previous action or to the price index over the same period of time. > Technometer or TEC The purpose of the Technometer is to provide a mathematical indication of the degree to which the market is overbought or oversold. The value of the Technometer could be as high as 100 or as low as 0. The other possible values would represent degrees of overbought or oversold. How to read the Technometer: | Overbought means vulnerable to a reaction | 100 - completely overbought market. ── 60 - actual overbought extreme. ──── 50 or higher is considered to be clearly over bought. ────── lower than 50 - relatively overbought. ──────── Everything in between clearly overbought and clearly oversold is neutral. ────────── A reading of 44.4 is absolute neutrality. ──────── Everything in between clearly overbought and clearly oversold is neutral. ────── higher than 38 - relatively oversold. ──── 38 or lower is considered to be clearly over sold. ── 28 - actual oversold extreme. 0 - completely oversold market. | Oversold means vulnerable to a rally | > Force The purpose of the Force Index is to provide an indication of the pressure being applied to push the market lower or the pull being applied to the market to pull it higher. > Momentum The purpose of the Momentum is to provide a measure of the speculative interest in the market.
Wskaźnik Pine Script™
od KryptoNight
3
Technometer - Multi Timeframe [WYCKOFF ARSENAL]WYCKOFF ARSENAL is now available on TradingView! Based on <> (Richard D. Wyckoff) Noted Indicators: ▪ Optimism Pessimism Index ▪ Force Index ▪ Technometer ◄ ▪ Momentum Main Features: ▪ Multi Timeframe is available ▪ Volume based indicators ▪ Can be used on pairs that have volume data ──────────────────────────── Highlights > Optimism Pessimism Index or OP The value of the OP is not important. The action of the OP is important. The action of the index must be compared to its previous action or to the price index over the same period of time. > Technometer or TEC The purpose of the Technometer is to provide a mathematical indication of the degree to which the market is overbought or oversold. The value of the Technometer could be as high as 100 or as low as 0. The other possible values would represent degrees of overbought or oversold. How to read the Technometer: | Overbought means vulnerable to a reaction | 100 - completely overbought market. ── 60 - actual overbought extreme. ──── 50 or higher is considered to be clearly over bought. ────── lower than 50 - relatively overbought. ──────── Everything in between clearly overbought and clearly oversold is neutral. ────────── A reading of 44.4 is absolute neutrality. ──────── Everything in between clearly overbought and clearly oversold is neutral. ────── higher than 38 - relatively oversold. ──── 38 or lower is considered to be clearly over sold. ── 28 - actual oversold extreme. 0 - completely oversold market. | Oversold means vulnerable to a rally | > Force The purpose of the Force Index is to provide an indication of the pressure being applied to push the market lower or the pull being applied to the market to pull it higher. > Momentum The purpose of the Momentum is to provide a measure of the speculative interest in the market.
Wskaźnik Pine Script™
od KryptoNight
34