Get started

Indicators and strategies

Modified Mannarino Market Risk Indicator MMMRI MMRIModified Mannarino Market Risk Indicator MMMRI was developed by "Nobody Special Finance" as an enhancement to the original MMRI developed by Gregory Mannarino. The original and modified version were created as a way to gauge current level of risk in the market. This published indicator includes both versions along with ability to customize the symbols, denominators, and ratio factors that are used within their formulas. Additional options have been included to colorize the candles, plot, and level fills, as well as the option to show or hide a table containing the realtime values for both versions, along with the current dollar strength and 10Y yield. Levels of market risk are denoted by dashed lines which represent the following levels: 0-50 slight risk, 50-100 low risk, 100-200 moderate risk, 200-300 high risk, 300+ extreme risk. The plot displays whichever of the following two formulas has been selected in the indicator settings, the default choice has been set to MMMRI: MMRI = (USD Strength * USD Interest Rate) / 1.61 MMMRI = (Debt / GDP) * (USD Strength * USD Interest Rate) / 1.61 NOTICE: This is an example script and not meant to be used as an actual strategy. By using this script or any portion thereof, you acknowledge that you have read and understood that this is for research purposes only and I am not responsible for any financial losses you may incur by using this script!
Pine Script® indicator
by allanster
25
RedK EVEREX - Effort Versus Results ExplorerRedK EVEREX is an experimental indicator that explores "Volume Price Analysis" basic concepts and Wyckoff law "Effort versus Result" - by inspecting the relative volume (effort) and the associated (relative) price action (result) for each bar - showing the analysis as an easy to read "stacked bands" visual. From that analysis, we calculate a "Relative Rate of Flow" - an easy to use +100/-100 oscilator that can be used to trigger a signal when a bullish or bearish mode is detected for a certain user-selected length of bars. Basic Concepts of VPA ------------------------------- (The topics of VPA & Wyckoff Effort vs Results law are too comprehensive to cover here - So here's just a very basic summary - please review these topics in detail in various sources available here in TradingView or on the web) * Volume Price Analysis (VPA) is the examination of the number of shares or contracts of a security that have been traded in a given period, and the associated price movement. By analyzing trends in volume in conjunction with price movements, traders can determine the significance of changes in price and what may unfold in the near future. * Oftentimes, high volumes of trading can infer a lot about investors’ outlook on a market or security. A significant price increase along with a significant volume increase, for example, could be a credible sign of a continued bullish trend or a bullish reversal. Adversely, a significant price decrease with a significant volume increase can point to a continued bearish trend or a bearish trend reversal. * Incorporating volume into a trading decision can help an investor to have a more balanced view of all the broad market factors that could be influencing a security’s price, which helps an investor to make a more informed decision. * Wyckoff's law "Effort versus results" dictates that large effort is expected to be accompanied with big results - which means that we should expect to see a big price move (result) associated with a large relative volume (effort) for a certain trading period (bar). * The way traders use this concept in chart analysis is to mainly look for imbalances or invalidation. for example, when we observe a large relative volume that is associated with very limited price change - that should trigger an early flag/warning sign that the current price trend is facing challenges and may be an early sign of "reversal" - this applies in both bearish and bullish conditions. on the other hand, when price starts to trend in a certain direction and that's associated with increasing volume, that can act as kind of validation, or a confirmation that the market supports that move. How does EVEREX work --------------------------------- * EVEREX inspects each bar and calculates a relative value for volume (effort) and "strength of price movement" (result) compared to a specified lookback period. The results are then visualized as stacked bands - the lower band represents the relative volume, the upper band represents the relative price strength - with clear color coding for easier analysis. * The scale of the band is initially set to 100 (each band can occupy up to 50) - and that can be changed in the settings to 200 or 400 - mainly to allow a "zoom in" on the bands. * Reading the resulting stacked bands makes it easier to see "balanced" volume/price action (where both bands are either equally strong, or equally weak), or when there's imbalance between volume and price (for example, a compression bar will show with high volume band and very small/tiny price action band) - another favorite pattern in VPA is the "Ease of Move", which will show as a relatively small volume band associated with a large "price action band" (either bullish or bearish) .. and so on. * a bit of a techie piece: why the use of a custom "Normalize()" function to calculate "relative" values in EVEREX? When we evaluate a certain value against an average (for example, volume) we need a mechanism to deal with "super high" values that largely exceed that average - I also needed a mechanism that mimics how a trader looks at a volume bar and decides that this volume value is super low, low, average, above average, high or super high -- the issue with using a stoch() function, which is the usual technique for comparing a data point against a lookback average, is that this function will produce a "zero" for low values, and cause a large distortion of the next few "ratios" when super large values occur in the data series - i researched multiple techniques here and decided to use the custom Normalize() function - and what i found is, as long as we're applying the same formula consistently to the data series, since it's all relative to itself, we can confidently use the result. Please feel free to play around with this part further if you like - the code is commented for those who would like to research this further. * Overall, the hope is to make the bar-by-bar analysis easier and faster for traders who apply VPA concepts in their trading What is RROF? -------------------------- * Once we have the values of relative volume and relative price strength, it's easy from there to combine these values into a moving index that can be used to track overall strength and detect reversals in market direction - if you think about it this a very similar concept to a volume-weighted RSI. I call that index the "Relative Rate of Flow" - or RROF (cause we're not using the direct volume and price values in the calculation, but rather relative values that we calculated with the proprietary "Normalize" function in the script. * You can show RROF as a single or double-period - and you can customize it in terms of smoothing, and signal line - and also utilize the basic alerts to get notified when a change in strength from one side to the other (bullish vs bearish) is detected * In the chart above, you can see how the RROF was able to detect change in market condition from Bearsh to Bullish - then from Bullish to Bearish for TSLA with good accuracy. Other Usage Options in EVEREX ------------------------------------ * I wrote EVEREX with a lot of flexibility and utilization in mind, while focusing on a clean and easy to use visual - EVEREX should work with any time frame and any instrument - in instruments with no volume data, only price data will be used. * You can completely hide the "EVEREX bands" and use EVEREX as a single or dual period strength indicator (by exposing the Bias/Sentiment plot which is hidden by default) - here's how this setup would look like - in this mode, you will basically be using EVEREX the same way you're using a volume-weighted RSI * or you can hide the bias/sentiment, and expose the Bulls & Bears plots (using the indicator's "Style" tab), and trade it like a Bull/Bear Pressure Index like this * you can choose Moving Average type for most plot elements in EVEREX, including how to deal with the Lookback averaging * you can set EVEREX to a different time frame than the chart * did i mention basic alerts in this v1.0 ?? There's room to add more VPA-specific alerts in future version (for example, when Ease-of-Move or Compression bars are detected...etc) - let me know if the comments what you want to see Final Thoughts -------------------- * EVEREX can be used for bar-by-bar VPA analysis - There are so much literature out there about VPA and it's highly recommended that traders read more about what VPA is and how it works - as it adds an interesting (and critical) dimension to technical analysis and will improve decision making * RROF is a "strength indicator" - it does not track price values (levels) or momentum - as you will see when you use it, the price can be moving up, while the RROF signal line starts moving down, reflecting decreasing strength (or otherwise, increasing bear strength) - So if you incorporate EVEREX in your trading you will need to use it alongside other momentum and price value indicators (like MACD, MA's, Trend Channels, Support & Resistance Lines, Fib / Donchian..etc) - to use for trade confirmation
Pine Script® indicator
by RedKTrader
252
Markdown: The Pine Editor's Hidden Gem💬 Markdown, a markup language Markdown is a portable, lightweight markup language that can be used for everything whether you're building a website, documentation, or even presentations. Platforms like Discord, Reddit, and GitHub support Markdown and is the widely go-to option for text formatting due to its simplicity. Pine Script is a language that also utilizes Markdown, specifically in the Pine Editor where it can really be used to some extent. Since the release of libraries, user-defined types, and methods, Pine Script is entering an age where developers will be highly dependent on libraries due to the capabilities Pine has inherited recently. It would be no surprise if a few people got together and took their time to thoroughly develop an entire project/library centered around improving Pine Script's built-in functions and providing developers with easier ways of achieving things than they thought they could. As you're all aware, hovering over functions (and more) in the editor pops up a prompt that specifies the parameters, types, and what the function returns. Pine Script uses Markdown for that, so I figured we could go ahead and push that feature to its limits and see what we can do. Today we'll go over how we can utilize Markdown in Pine Script, and how you can make your library's built-in functions stand out more than they did previously. For more information, visit www.markdownguide.org 📕 General Notes Markdown syntax only works on functions and methods. Using arrays as parameters as of 2/21/2023 breaks the Markdown system. The prompt window holds a max of 166 characters on one line before overflowing. There is no limit on how long the prompt window can be. 🔽 Getting Started 🔽 ▶️ Headings If you have experience in HTML, Markdown, or even Microsoft Word then you already have a grasp of how headings work and look. To simplify it, headings make the given text either massive or tiny depending on how many number symbols are provided. When defining headings, you must have a space between the number (#) symbol, and the text. This is typical syntax throughout the language. Pine Script uses bold text by applying (**) for their titles on their built-ins (e.g. @returns) but you could also use heading level 4 (####) and have it look the same. ▶️ Paragraphs & Line Breaks You may want to provide extensive details and examples relating to one function, in this case, you could create line breaks. Creating line breaks skips to the next line so you can keep things organized as a result. To achieve a valid line break and create a new paragraph, you must end the line with two or more spaces. If you want to have an empty line in between, apply a backslash (\). Backslashes (\) are generally not recommended for every line break. In this case, I only recommend using them for empty lines. ▶️ Text Formatting Markdown provides text formatting such as bold, italics, and strikethrough. For bolding text, you can apply open and close (**) or (__). For italicizing text, you can apply open and close (*) or (_). For bolding and italicizing text, you can apply open and close (***) or (___). For s̶t̶r̶i̶k̶e̶t̶h̶r̶o̶u̶g̶h̶, you need to apply open and close (~~). This was mentioned in the Headers section, but Pine Script's main titles (e.g. @returns or @syntax) use bold (**) by default. ▶️ Blockquotes Blockquotes in Pine Script can be visualized as a built-in indentation system. They are declared using greater than (>) and everything will be auto-aligned and indented until closed. By convention you generally want to include the greater than (>) on every line that's included in the block quote. Even when not needed. If you would like to indent even more (nested blockquotes), you can apply multiple greater than symbols (>). For example, (>>) Blockquotes can be closed by ending the next line with only one greater than (>) symbol, or by using a horizontal rule. ▶️ Horizontal Rules Horizontal rules in Pine Script are what you see at the very top of the prompt in built-ins. When hovering, you can see the top of the prompt provides a line, and we can actually reproduce these lines. These are extremely useful for separating information into their own parts and are accessed by applying 3 underscores (___), or 3 asterisks (***). Horizontal rules were mentioned above, when we were discussing block quotes. These can also be used to close blockquotes as well. Horizontal rules require a minimum of 3 underscores (___) or 3 asterisks (***). ▶️ Lists Lists give us a way to structure data in a somewhat neat way. There are multiple ways to start a list, such as 1. First Item (number followed by a period) - First Item (dash) + First Item (plus sign) * First Item (asterisk) Using number-based lists provide an ordered list, whereas using (-), (+), or (*) will provide an unordered list (bullet points). If you want to begin an unordered list with a number that ends with a period, you must use an escape sequence (\) after the number. Standard indentation (tab-width) list detection isn't supported, so to nest lists you have to use blockquotes (>) which may not look as appealing. ▶️ Code Blocks Using code blocks allows you to write actual Pine Script code inside the prompt. It's a game changer that can potentially help people understand how to execute functions quickly. To use code blocks, apply three 3 open and close backquotes (```). Built-in's use (```pine) but there's no difference when we apply it. Considering that tab-width indentation isn't detected properly, we can make use of the blockquotes mentioned above. ▶️ Denotation Denoting can also be seen as highlighting a background layer behind text. They're basically code blocks, but without the "block". Similar to how code blocks work, we apply one backquote open and close (`). Make sure to only use this on important keywords. There really isn't a conventional way of applying this. It's up to you to decide what people should have their eyes tracked onto when they hover over your functions. If needed, look at how Pine Script's built-in variables and functions utilize this. ▶️ Tables Tables are possible in Markdown, although they may look a bit different in the Pine Editor. They are made by separating text with vertical bars (|). The headers are detected when there is a minimum of one hyphen (-) below them. You can align text by using a colon as I do in the photo. Hyphens must be connected to the colon in order to display correctly. Tables aren't ideal to use in the editor but are there if anyone wants to give it a go. ▶️ Links & Images Markdown supports images and hyperlinks, which means we can also do that here in the Pine Editor. Cool right? If you want to create a hyperlink, surround the displayed text in open and close brackets . If you want to load a photo into your prompt, it's the same syntax as the hyperlink, except it uses a (!) See syntax list below. Here are realistic usage examples. (Snippets from code below) These follow the same syntax as the built-ins. I'm not using horizontal rules here, but it's entirely up to you. ▶️ Syntax List Headings Level 1: # Level 2: ## Level 3: ### Level 4: #### Level 5: ##### Level 6: ###### Line Breaks Text (two spaces) Text\ (backslash) Text Formatting Bold (**) Italic (**) Strikethrough (~~) Blockquotes Indent (>) Double Indent (>>) Triple Indent (>>>) and so on. Horizontal Rules (___) or (***) Lists Ordered List (1.) Unordered List (-) or (+) or (*) Code Blocks (```) or (```pine) Denotation (`) Tables (|) and (-) and (:) Hyperlinks (URL) Images ! (URL) Hope this helps. 👍
Pine Script® library
by HoanGhetti
16
Elliott Wave [LuxAlgo]The Elliott Wave indicator allows users to detect Elliott Wave (EW) impulses as well as corrective segments automatically on the chart. These are detected and displayed serially, allowing users to keep track of the evolution of an impulse or corrective wave. Fibonacci retracements constructed from detected impulse waves are also included. This script additionally allows users to get alerted on a wide variety of trigger conditions (see the ALERTS section below). 🔶 SETTINGS 🔹 Source • "high" -> options high, close, maximum of open/close • "low" -> options low, close, minimum of open/close 🔹 ZigZag • The source and length are used to check whether a new Pivot Point is found. Example: • source = high/low, length = 10: • There is a new pivot  high when: - previous high is higher than current high - the highs of 10 bars prior to previous high are all lower • These pivot  points  are used to form the ZigZag lines, which in their turn are used for pattern recognition 🔶 USAGE The basic principles we use to identify Elliott Wave impulses are: • A movement in the direction of the trend ( Motive/Impulse wave ) is divided in 5 waves (Wave 1 -> 5) • The Corrective Wave (against the trend) is divided in 3 waves (Wave A -> C) • The waves can be subdivided in smaller waves • Wave 2 can’t retrace more than the beginning of Wave 1 • Wave 4 does not overlap with the price territory of Wave 1 Here we see an example: Let's look at the development: • 1 bar after point (5) a confirmed 5 Motive Wave pattern is found (1 -> 5; The 5 Waves can also be seen as one large Wave 1 ). • Next, the script draws a set of Fibonacci lines, which are area's where the Corrective Wave potentially will bounce. Here we see the fifth wave is getting larger, the previous highest point is updated, and the Wave 5 is larger than Wave 3 : (At this point, the pattern is invalidated, and it display as dotted) Further progression in time: At this point, a confirmed " 3 Corrective Wave pattern " is found (a -> c) When a new high has developed, a circle is drawn (in the same color of the lines) However, when the bottom of the drawn box has breached, a red cross will be visualized. Further progression: Later on, a bearish  confirmed " 5 Motive Wave pattern " is found (1 -> 5): When a Corrective Wave becomes invalidated, the ABC pattern will display as dashed (not dotted): 🔶 TECHNIQUES Pine Script™ introduces methods! • More information can be found here: • Pine Script™ v5 User Manual 👉 Methods • Pine Script™ language reference manual 👉 method 🔶 ALERTS Dynamic alerts are included in the script, you only need to set 1 alert to receive following messages: • When a new EW Motive Pattern is found (Bullish/Bearish ) • When a new EW Corrective Pattern is found (Bullish/Bearish ) • When an EW Motive Pattern is invalidated (Bullish/Bearish ) • When an EW Corrective Pattern is invalidated (Bullish/Bearish ) • When possible, a start of a new EW Motive Wave is found (Bullish/Bearish ) • Here is information how you can set these alerts()
Pine Script® indicator
by LuxAlgo
156
Fundamentals Graphing [Kioseff Trading]Hello! This script "Fundamental Comparison" allows you to compare almost any fundamental metric across 40 assets; various charting methods are employable! Thank you to @TradingView / @PineCoders for providing the framework in the "Financials on Chart" indicator - thereby expediting a generous portion of work (: Features Most metrics included in the "Financials on Chart" indicator are graphable Scatter chat Histogram Bar chart Pie chart Reversible scaling Adjusts to the size of your chart 10 industry presets Custom symbol dataset Retrieve, graph, and compare fundamental data by quarter/year. The indicator can "look back" to grab fundamental data from previous quarters/years. Sortable data - ascending/descending Built-in search function Self-Adjusting Graph The graph adjusts to the orientation/size of your chart! The image above shows the graph on a price chart with a 229 bar difference. The image above shows the same price chart; however, there's now a 1941 bar difference to which the fundamentals graph automatically adjusts! The images above show the same expansion/reduction for the pie chart; all graph types shrink and expand with the price chart. Fundamental Metrics The image above shows most of the settings for the indicator! Most of the metrics from the "Financials on Chart" indicator are included! Quarterly or annual data are retrievable, in addition to industry presets. Additionally, you can retrieve the financial data any number of intervals back (so long as the data exists and is provided by TradingView) The image above shows an example of retrieving a fundamental metric from a previous FQ. The same can be done with FY! Sortable Data All data retrieved by the indicator is sortable - allowing for, hopefully, easier evaluations (: The image above exemplifies the capability! Data from any quarter/year can be sorted similarly. Reversible Scale / Reversible Color Scheme A seemingly trivial feature: a reversible scale and color scheme should assist in instances where "a higher number is bad" and a "lower number is good" - in addition to other scenarios. For instance, The image above shows a graph for taxes. The scale and color scheme have not been reversed and, presently, larger columns are correlating to a smaller amount of money out/in than smaller columns. This can be fixed by reversing the scale. The image above shows the "Reverse Scale" feature selected. Consequently, larger columns correlate to a larger amount of money out/in. Similarly, a "Reverse Colors" feature is available. A useful option when a more positive number is "bad" and a less positive number is "good". For instance, The image above shows graphing for the Beneish M-Score. A more positive number is generally interpreted as "bad"; a less positive number is generally interpreted as "good". However, our color scheme doesn't seem to correspond (unless one considers red = good and green = bad) Let's enable the reverse color feature. The image above shows the completion of the process! Finally, there's a built-in search feature that's a bit difficult to use; however, should you grow comfortable with it you may save some time sorting through fundamental data. Big thanks to @rumpypumpydumpy for providing an easy-to-work-with framework for the pie chart! That's all for now; thank you for checking this out.
Pine Script® indicator
by KioseffTrading
41
Flare🔶 METHODS • Pine Script™ introduces methods ( 1 , 2 )! Much kuddos for the developers, Tradingview, and all who has worked on it! • This educational script will show the simplified way of writing built-in methods, not to create a new method. 🔹 Simplified way of writing built-in methods: · Instead of: newArray = array.new() array.unshift(newArray, 1) lin = line.new(na, na, na, na) line.set_xy1(lin, bar_index , close) line.set_xy2(lin, bar_index + 10, close) label newLabel = label.new(bar_index, high) if barstate.islast label.delete(newLabel) · We now can write it like this: newArray = array.new() newArray.unshift(1) lin = line.new(na, na, na, na) lin.set_xy1(bar_index , close) lin.set_xy2(bar_index + 10, close) label newLabel = label.new(bar_index, high) if barstate.islast newLabel.delete()                                                                   —————————————————————————————————————————————————————————— · When using sometimes brackets are necessary: label lab = label.new(bar_index, high) if barstate.islast label.set_color(lab, color.red) label.delete(lab ) · -> label lab = label.new(bar_index, high) if barstate.islast lab.set_color(color.red) (lab ).delete() // lab .delete() doesn't compile at the moment                                                                   —————————————————————————————————————————————————————————— 🔶 OVERVIEW OF SCRIPT • The basic principles are: · Find 1 point ( close ) x bars back from current bar ( settings: 'x close back'). · Create a 'Flare' shaped object from that point to current bar or further (dependable of "Width of Flare"). · Calculate where current close is located versus the Flare lines. · On that bases, change colour and draw plotshapes.       · Below bar if current close is located in the upper part of the Flare       · Above bar if current close is located in the lower part of the Flare       · Above & Below if located in the middle part of the Flare          -> Above & Below colours has 3 different colours (adjustable), dependable on the position 🔶 EXAMPLES · Neutral zone: · Light Bullish zone: · Bullish zone: · Very Bullish / Overbought zone: · Light Bearish zone: · Bearish zone: · Very Bearish / Oversold zone: 🔶 TECHNIQUES 🔹 I. Make a User Defined Type (UDT) Flare, with: · 5x linefill - array of linefill · int iDir, which captures the direction (current location of close in Flare) · color cCol, this is a colour variable in relation to the direction. 🔹 II. Different functions will add a new Flare object, and update the values on each bar. · Explanation of each function can be found in the script. 🔶 EXTRA's · The input.color() is located in the function set_flare_B(flare obj) · Best to put the inputs at the beginning of the script, I included this alternative just to show it is possible (but mostly not ideal) · Background colour (settings: Bgcolor) can be enabled for better visibility of colours
Pine Script® indicator
by fikira
30
Recursive Auto-Pitchfork [Trendoscope]"Say Hi" to object oriented programming with Pinescript using types and methods. This is the beginning of new era of Pinescript where we are moving from isolated scripts containing indicator and strategies to whole ecosystem of Object Oriented Programming with libraries of highly reusable components. Those who are familiar with programming would have already realised how big these improvements are and what it brings to the table. With this script, I am not just providing an indicator for traders but also an introduction for programmers on how to design and build object oriented components in Pinescript using types and methods. Big thanks to Tradingview and Pine development team for making this happen. We look forward for many such gifts in the future :) 🎲 Architecture As mentioned before, we are not just building an indicator here. But, an ecosystem of components. Using Types and Methods we can visualise libraries as Classes. Thus, we can build an ecosystem of libraries in layered approach to enhance effective code reusability. Generic architecture can be visualised as below Coming to the specific case of Auto Pitchfork indicator, the indicator code is less than 50 lines for logic and around 100 lines of inputs. But, most of the heavy-lifting is done by the libraries underneath. Here is a snapshot of related libraries and how they are connected. All libraries are divided into two portions. Types - Contains only type definitions Methods - Contains only method definitions related to the types defined in the Types library Together, these libraries can be visualised as Class. Methods are defined in such a way all exported methods are related to Types and no other functions or features are defined. If we need further functionality which does not depend on the types, we need to do this via some other library and use them here. Similarly, we should not define any methods related to these types in other libraries. Reason for splitting the libraries to types and methods is to enable updating methods without disturbing types. Since libraries create interdependencies due to versioning, it is best if we do less updates on the type definitions. Splitting the two enables adding more features while keeping the type definition version intact. 🎲 Base Libraries Base libraries are those which does not have any dependency. They form basic structures which are later used in other libraries. These libraries need to be crafted carefully so that minimal updates are done later on. Any updates on these libraries will impact all the dependent libraries and scripts. 🎯 Drawing DrawingTypes - Defines basic drawing types Point, Line, Label, Box, Linefill and related property types. DrawingMethods - All the methods or functionality surrounding Basic types are defined here. 🎲 Layer 1 Libraries These are the libraries which has direct dependency on base libraries. 🎯 Zigzag ZigzagTypes - Types required for defining Zigzag and Divergence ZigzagMethods - Methods associated with Zigzag Type definitions. 🎯Pitchfork PitchforkTypes - Basic and Drawing Types for Pitchfork objects PitchforkMethods - Methods associated with Pitchfork type definitions 🎲 Indicator and Settings Indicator draws pitchfork based on recursive zigzag configurations. Recursive zigzag is derived with following logic: Base level zigzag is calculated with regular zigzag algorithm with given length and depth Next level zigzag is calculated based on base zigzag. And we recursively calculate higher level zigzags until we are left with 4 or less pivots or when no further reduction is possible On every level of zigzag, we then check the last 3 pivots and draw pitchfork based on the retracement ratio. Indicator settings are summarised in the tooltips and are as below. Finally, big thanks to my partner @CryptoArch_ for bringing up the topic of pitchfork for our next development.
Pine Script® indicator
by Trendoscope
47
Intrabar Analyzer [Kioseff Trading]Hello! This indicator (Intrabar Analyzer) presents intrabar data in various derivative forms. On-Chart Features Traditional price data down to 1 min. Heikin-Ashi price data down to 1 min. Kagi price data down to 1 min. Point & Figure price data down to 1 min. Renko price data down to 1 min. Linebreak price data down to 1 min. LinReg channel SMA EMA ALMA Echomorphic Average (A @kaigouthro special!) HMA RMA WMA VWMA VWAP SWMA SAR Supertrend On-Chart Features Price x Volume graph Intrabar technical rating Positive volume index Negative volume index Price volume trend RSI %k ROC MFI MFC OBV CCI BBW CMO COG KCW MOM RANGE %r Let's look at the objects populated by the indicator! The image above shows what data correlates to the populated graphs! Let's dial in on the price x volume graph. The image above provides an example/explanation of the price x volume graph. All data is sourced from a lower timeframe (configurable - default = 1 minute). Colors are configurable; the plot characters are configurable. The numbers above show an alternative view of the price x volume graph! Price graph The price graph can populate 6 variations of price data: traditional, heikin-ashi, renko, point & figure, line break, and kagi. The subsequent images will show all available forms of price data, in addition to a randomly selected, on-chart technical indicator! Kagi + LinReg Traditional + EMA Renko + SAR Point & Figure + ALMA Heikin-Ashi + Supertrend Line Break + VWAP You can display up to three indicators concomitantly - all calculated using intrabar data! Lastly, the indicator displays the TradingView calculated technical rating for the intrabar. The technical ratings are multiplied by x100 and oriented left & right of the price box. Left values are negative; right values are positive. The "0" value is not shown; therefore, if the technical rating isn't highlighted then the rating is "0". The image above shows the technical rating system in action (: That's it! This was a fun project and I'm certainly willing to add more - let me know if there's anything you'd like included. Additionally, a future feature involves compatibility with any custom indicator! Stay tuned; thank you for checking this out (: Thank you to @kaigouthro, TradingView and @PineCoders for providing some cool libraries to play with!
Pine Script® indicator
by KioseffTrading
45
Recession Warning Traffic LightThis is an indicator that uses 6 different metrics to determine the combined probability of a recession and compares the high probability warning periods against actual historical periods of recession. GREEN tells us that the referenced recession indicators are not exhibiting any warning. Observe the long stretches of “all-green” in between recessionary periods in the chart above. RED will show a full-on warning level for that particular recession indicator, signaling that monitoring of this sector is clearly showing a problem – which has in the past, reliably exhibited itself as a forewarning of recessions. Adding green and red together can help determine a combined probability of recession. IMPORTANT: Your chart should be on 1d and set to SPX , DJI ,or NDQ indices Precious metals: This indicator calculates the relative prices of Gold & rhodium. Gold is a flight-to-quality asset. Rhodium is the rarest of precious industrial metals and prices spike when the economy is heating up. In front of a recession, the upper relative movement of rhodium precedes gold. Stock markets: This indicator compares closing prices to growth rate curves of the SPX. This indication is the noisiest but tells us very well when the recession has ended. Stock market indices, which respond to “smart money” moving out of markets when the other indicators begin to warn of recession, or when markets become overheated and rise to historically unsustainable levels. Yield curve: This indicator compares the 3m & 10y treasuries and detects yield curve inversions. Interest rates are controlled by the Federal Reserve and by the purchasers in the Federal Treasury auction markets, which together create the treasury yield curve. This inversion is the most reliable recession indicator. These happen during a flight to quality. Federal Reserve: This indicator measures GDP and detects contraction which is technically a recession. This is usually one of the last indicators to enter a Warning state, and it could be 6 months delayed simply confirming what may have already been projected. Money Supply. This indicator measures the M2 money supply, which typically grows about 1% per calendar quarter. When this shrinks, it's tapping the brakes on the economy. This can also lead to yield curve inversion. This is also a measure of inflation and its effects on the aggregate money supply (liquid capital) available for short-term economic activity, or which can be directed into the purchase of long-term, less liquid assets. Leading Economic factors: There is a whole basket of leading economic indicators that, as collections, reflect overall growth or contraction of economic activity. These indicators include measures of level and growth in productivity, employment, housing, consumer confidence, industrial purchasing confidence, and much more. These indicators may or may not be detached from the broader economy, and often provide up to 6 months of foresight. For more information please visit www.conference-board.org Actual Recession: Central Bank indicators are published by the Federal Reserve and reflect their own analysis of national and regional economic health, as well as their calculations of the likelihood of a recession. The Federal Reserve has a recession ticker which is used to plot periods of actual recessions on this indicator for comparison.
Pine Script® indicator
by BarefootJoey
27
RSI Impact Heat Map [Trendoscope]Here is a simple tool to measure and display outcome of certain RSI event over heat map. 🎲 Process 🎯Event Event can be either Crossover or Crossunder of RSI on certain value. 🎯Measuring Impact Impact of the event after N number of bars is measured in terms of highest and lowest displacement from the last close price. Impact can be collected as either number of times of ATR or percentage of price. Impact for each trigger is recorded separately and stored in array of custom type. 🎯Plotting Heat Map Heat map is displayed using pine tables. Users can select heat map size - which can vary from 10 to 90. Selecting optimal size is important in order to get right interpretation of data. Having higher number of cells can give more granular data. But, chart may not fit into the window. Having lower size means, stats are combined together to get less granular data which may not give right picture of the results. Default value for size is 50 - meaning data is displayed in 51X51 cells. Range of the heat map is adjusted automatically based on min and max value of the displacement. In order to filter out or merge extreme values, range is calculated based on certain percentile of the values. This will avoid displaying lots of empty cells which can obscure the actual impact. 🎲 Settings Settings allow users to define their event, impact duration and reference, and few display related properties. The description of these parameters are as below: 🎲 Use Cases In this script, we have taken RSI as an example to measure impact. But, we can do this for any event. This can be price crossing over/under upper/lower bollinger bands, moving average crossovers or even complex entry or exit conditions. Overall, we can use this to plot and evaluate our trade criteria. 🎲 Interpretation Q1 - If more coloured dots appear on the top right corner of the table, then the event is considered to trigger high volatility and high risk environment. Q2 - If more coloured dots appear on the top left corner, then the events are considered to trigger bearish environment. Q3 - If more coloured dots appear on the bottom left corner of the chart, then the events are considered insignificant as they neither generate higher displacement in positive or negative side. You can further alter outlier percentage to reduce the bracket and hence have higher distribution move towards Q4 - If more coloured dots appear on the bottom right corner, then the events are considered to trigger bullish environment. Will also look forward to implement this as library so that any conditions or events can be plugged into it.
Pine Script® indicator
by Trendoscope
23
Market Sessions - By LeviathanA simple indicator to help you keep track of 4 market sessions (default: Tokyo, London, New York, Sydney) in 4 different visual forms (boxes, timeline, zones, colored candles) with many other useful tools. You can choose between 4 different market sessions. The default ones are Tokyo, London, New York and Sydney but you can easily customize the times, names and colors to make the script plot any session you need. Sessions can be viewed in 4 different ways: boxes, zones, timelines, or just colored candles, all with customizable appearances. You can make your chart cleaner by merging sessions overlaps, choosing a custom lookback period and also picking between various additional settings such as viewing session High/Low or Open/Close change in % or pips, hiding weekends, viewing the Open/Close Line to identify session’s direction and 0.5 level to see session’s “Equilibrium” and much more. More updates with interesting tools will be added in the future. Note: The script will plot the correct default Tokyo, London, New York and Sydney sessions automatically, your chart/Tradingview app timezone does not matter! If you wish to tweak the open/close times of sessions, just make sure you input them in UTC (but even this can be changed later in the settings) Settings Overview SESSIONS - You can show/hide Tokyo Session, rename it, change the color and set up start/end time. - You can show/hide London Session, rename it, change the color and set up start/end time. - You can show/hide New York Session, rename it, change the color and set up start/end time. - You can show/hide Sydney Session, rename it, change the color and set up start/end time. * Keep in mind that you can fully change and customize these sessions and therefore create any other sessions or a zone you wish to display. ADDITIONAL TOOLS AND SETTINGS 1. “Change (Pips)” - this will add the pip distance between Session High and Session Low or the pip distance between Session Open and Session Close to the session label. 2. “Change (%)” - this will add the percentage distance between Session High and Session Low or the percentage distance between Session Open and Session Close to the session label. 3. “Merge Overlaps” - this will merge the overlapping sessions and show only one at a time (end of Tokyo is moved to start of London, the end of London is moved to the start of New York, end of New York is moved to start of Sydney and end of Sydney is moved to start of Tokyo). 4. “Hide Weekends” - this will prevent the script from plotting sessions over the weekend when the markets are closed. 5. “Open/Close Line” - this will draw a line from the session open to the session close (or current price, if session is ongoing). 6. “Session 0.5 Level” - this will draw a horizontal line halfway between the session’s high and the session’s low. 7. “Color Candles” - this will color the bars/candlesticks with the color of the session in which they occurred. 8. Display Type” - Choose between three different ways of session visualization (Boxes, Zones and Candles). 9. “Lookback (Days)” - this input tells the script to only draw sessions for X days back (1 = one day). 10. “Change (%/Pips) Source) - this is where you choose the source of “Change (Pips)” and ”Change (%) ” labels. Picking “Session High/Low” will show you the change between Session High and Session Low and picking “Session Open/Close” will show you the change between Session Open and Session Close. 11. “Input Timezone” - this defines the timezone of the session start/end inputs (you don’t have to change this unless you know what you’re doing) Make sure to read future update logs to keep track of the most recent additions and settings of this script. Box generation code inspired by Jos(TradingCode), session box visuals inspired by @boitoki's FX Market Sessions
Pine Script® indicator
by LeviathanCapital
56
Financials - Comparing CompaniesHello All For a while I have been working on this indicator to compare financials of the companies and sort them accordingly. Finally I completed and published it. I preferred using new object type feature in Pine language™ and I hope it might be an example and helpful for the developers. First of all, as we have limitation on security calls, the indicator can get and compare financials for 5 companies only. also Chart time frame must be 1Day or higher! ( I recommend 1Day time frame ). if not then the indicator stops and shows the error message: "Please set the time frame 1Day or higher" . More important than others: You should choose the companies from the same sector! Compare apples to apples :) The Financials in the indicator: Earnings Per Share Price to Earnings Ratio Price to Sales Ratio Price to Book Ratio Profit Margin Dept to Equity Current Ratio Market Capitalization Also more information shown for each stocks: Closing Price, sets the color accordingly 2 Simple/Exponential moving average, you can set the length, also it checks if it is rising/falling and sets the color accordingly Volume info Average volume (20 days), you can set the period Currency for each security Lets see some features in it: it sorts the companies according to the financials: If you move the mouse onto any header then it shows explanation about the financial: You can change location and text size: You can set the type of Moving averages as SMA or EMA and you can also set the length for both . Headers for both are changed automatically by MA type and length Colors for Closing price and MA cells are set automatically: For new Objects in Pine language click here P.S. You can use this indicator while analyzing the financials of the companies in same sector/industry. So please don't ask for the alerts :) Enjoy!
Pine Script® indicator
by LonesomeTheBlue
31
Golden PocketGolden Pocket This marks up the fibonacci retracement levels of 0.65 and 0.618 by default, these levels are often referred to as the golden pocket. They are known by this because when price has an impulse either to the up or downside, price will end up retracing at some point. This Golden pocket often lines up with other means of confluence where it's considered a good entry price from the retrace. Unlike standard fib retracement indicators, these boxes will extend with current price until they are hit. As well as this, there is a moving average filter which you can set to higher timeframes meaning that you can choose to only look for golden pockets which are following the higher time frame trend. You can easily monitor all of your settings by setting up just 1 alert. Settings You have the option to enable/disable the line which marks out the pivot points the fib is being calculated from, you can also change the colour and style of the line. Below this you have the option to choose what colour the fib boxes are and what colour they change to once price hits it. If you want them to disappear change the colours opacity to 0%. If you want to change the golden pocket levels you can do that by changing the 0.618 or 0.65 levels in the settings. The pivot distance controls what part defines a pivot high or low, it must be the highest/lowest to the left/right of the pivot candle count. MA filter will only accept golden pockets which are trending with the Moving average. You can change all the settings of the Moving average which acts as a filter including which timeframe it is calculated on. Alerts Simply toggle this on int the settings and then click on the 3 dots next to the indicators name, 'add alert', leave the top boxes as they are, you can name the alert anything you like but once you confirm this, it will monitor all golden pockets on the particular asset and timeframe you are looking at. The alerts are set up to trigger as soon as price touches one of the boxes. Use Cases We like setting are moving average up on the daily timeframe and using the Moving average filter so we know we are only trading with the higher timeframe trend. From there we can set up alerts on any lower timeframe. Feel free to use any part of this script in your own code, please just give us a mention so we can check out your contributions to the community as well! Happy to take in any suggestions or ways of improving
Pine Script® indicator
by TradingWolf
33
Pivot and Price DiscoveryA Population Sampled linear regression model that provides additional detail about the distribution moments (skew, kurtosis, variance and mean) as well as providing indicators that track when a pivot has enough momentum to trade on as well as expected ranges of future price action based on Std Devs. For the momentum lines -- red indicates that there has been a reducing pivot with momentum, this continues as a grey line for continuation, and will be cancelled when an increasing pivot with momentum is encountered. Forward looking trend triangle captures the +/- stated standard deviation from the latest bar_index over 2 periods. Movements that trace outside of this can be considered a precursor to an upcoming pivot, and by analyzing skewness and kurtosis, the probability of an upcoming pivot should be better understood. I have really only looked at this for timescales greater than 5 minutes. Adjust the lookback length accordingly when moving to different timescales: For example, 1 hr at 10m timescale will be a lookback length of 6 which is too low for accurate analysis, so keep the lookback length appropriate for the timescales being used. Also realize that trade volume will skew the deviations and regression if you are including data outside of regular trading hours (futures are different, but also experience volume sensitivity -- I maylook into accounting for this in future versions.) © TheGeeBee
Pine Script® indicator
by TheGeeBee
12
Fair value bands / quantifytools— Overview Fair value bands, like other band tools, depict dynamic points in price where price behaviour is normal or abnormal, i.e. trading at/around mean (price at fair value) or deviating from mean (price outside fair value). Unlike constantly readjusting standard deviation based bands, fair value bands are designed to be smooth and constant, based on typical historical deviations. The script calculates pivots that take place above/below fair value basis and forms median deviation bands based on this information. These points are then multiplied up to 3, representing more extreme deviations. By default, the script uses OHLC4 and SMA 20 as basis for the bands. Users can form their preferred fair value basis using following options: Price source - Standard OHLC values - HL2 (High + low / 2) - OHLC4 (Open + high + low + close / 4) - HLC3 (High + low + close / 3) - HLCC4 (High + low + close + close / 4) Smoothing - SMA - EMA - HMA - RMA - WMA - VWMA - Median Once fair value basis is established, some additional customization options can be employed: Trend mode Direction based Cross based Trend modes affect fair value basis color that indicates trend direction. Direction based trend considers only the direction of the defined fair value basis, i.e. pointing up is considered an uptrend, vice versa for downtrend. Cross based trends activate when selected source (same options as price source) crosses fair value basis. These sources can be set individually for uptrend/downtrend cross conditions. By default, the script uses cross based trend mode with low and high as sources. Cross based (downtrend not triggered) vs. direction based (downtrend triggered): Threshold band Threshold band is calculated using typical deviations when price is trading at fair value basis. In other words, a little bit of "wiggle room" is added around the mean based on expected deviation. This feature is useful for cross based trends, as it allows filtering insignificant crosses that are more likely just noise. By default, threshold band is calculated based on 1x median deviation from mean. Users can increase/decrease threshold band width via input menu for more/less noise filtering, e.g. 2x threshold band width would require price to cross wiggle room that is 2x wider than typical, 0x erases threshold band altogether. Deviation bands Width of deviation bands by default is based on 1x median deviations and can be increased/decreased in a similar manner to threshold bands. Each combination of customization options produces varying behaviour in the bands. To measure the behaviour and finding fairest representation of fair and unfair value, some data is gathered. — Fair value metrics Space between each band is considered a lot, named +3, +2, +1, -1, -2, -3. For each lot, time spent and volume relative to volume moving average (SMA 20) is recorded each time price is trading in a given lot: Depending on the asset, timeframe and chosen fair value basis, shape of the distributions vary. However, practically always time is distributed in a normal bell curve shape, being highest at lots +1 to -1, gradually decreasing the further price is from the mean. This is hardly surprising, but it allows accurately determining dynamic areas of normal and abnormal price behaviour (i.e. low risk area between +1 and -1, high risk area between +-2 to +-3). Volume on the other hand is typically distributed the other way around, being lowest at lots +1 to -1 and highest at +-2 to +-3. When time and volume are distributed like so, we can conclude that 1) price being outside fair value is a rare event and 2) the more price is outside fair value, the more anomaly behaviour in volume we tend to find. Viewing metric calculations Metric calculation highlights can be enabled from the input menu, resulting in a lot based coloring and visibility of each lot counter (time, cumulative relative volume and average relative volume) in data window: — Alerts Available alerts are the following: Individual - High crossing deviation band (bands +1 to +3 ) - Low crossing deviation band (bands -1 to -3 ) - Low at threshold band in an uptrend - High at threshold band in a downtrend - New uptrend - New downtrend Grouped - New uptrend or downtrend - Deviation band cross (+1 or -1) - Deviation band cross (+2 or -2) - Deviation band cross (+3 or -3) — Practical guide Example #1 : Risk on/risk off trend following Ideal trend stays inside fair value and provides sufficient cool offs between the moves. When this is the case, fair value bands can be used for sensible entry/exit levels within the trend. Example #2 : Mean reversions When price shows exuberance into an extreme deviation, followed by a stall and signs of exhaustion (wicks), an opportunity for mean reversion emerges. The higher the deviation, the more volatility in the move, the more signalling of exhaustion, the better. Example #3 : Tweaking bands for desired behaviour The faster the length of fair value basis, the more momentum price needs to hit extreme deviation levels, as bands too are moving faster alongside price. Decreasing fair value basis length typically leads to more quick and aggressive deviations and less steady trends outside fair value.
Pine Script® indicator
by quantifytools
46
Motion▮ FEATURES Now as library version :) String-based transition-effects Performance optimization. Reduced memory consumption up to >90% by kicking the output to the "stdout". Use marquee- or loader-effect on any possible string location. Example: UI Price-Ticker ---------------------------------------------------------------------------- Library "Motion" _getStringMono(_len, _str, _sep)   Parameters:      _len      _str      _sep marquee(this, _extern, _ws, _subLen, _subStart)   Parameters:      this      _extern      _ws      _subLen      _subStart transition(this, _subLen, _subStart)   Parameters:      this      _subLen      _subStart hold(this)   Parameters:      this keyframe   keyframe A keyframe object.   Fields:      seq      intv      step      length      update_no      frame_no      ltr      hold
Pine Script® library
by cryptolinx
5
Machine Learning: Lorentzian Classification█ OVERVIEW A Lorentzian Distance Classifier (LDC) is a Machine Learning classification algorithm capable of categorizing historical data from a multi-dimensional feature space. This indicator demonstrates how Lorentzian Classification can also be used to predict the direction of future price movements when used as the distance metric for a novel implementation of an Approximate Nearest Neighbors (ANN) algorithm. █ BACKGROUND In physics, Lorentzian space is perhaps best known for its role in describing the curvature of space-time in Einstein's theory of General Relativity (2). Interestingly, however, this abstract concept from theoretical physics also has tangible real-world applications in trading. Recently, it was hypothesized that Lorentzian space was also well-suited for analyzing time-series data (4), (5). This hypothesis has been supported by several empirical studies that demonstrate that Lorentzian distance is more robust to outliers and noise than the more commonly used Euclidean distance (1), (3), (6). Furthermore, Lorentzian distance was also shown to outperform dozens of other highly regarded distance metrics, including Manhattan distance, Bhattacharyya similarity, and Cosine similarity (1), (3). Outside of Dynamic Time Warping based approaches, which are unfortunately too computationally intensive for PineScript at this time, the Lorentzian Distance metric consistently scores the highest mean accuracy over a wide variety of time series data sets (1). Euclidean distance is commonly used as the default distance metric for NN-based search algorithms, but it may not always be the best choice when dealing with financial market data. This is because financial market data can be significantly impacted by proximity to major world events such as FOMC Meetings and Black Swan events. This event-based distortion of market data can be framed as similar to the gravitational warping caused by a massive object on the space-time continuum. For financial markets, the analogous continuum that experiences warping can be referred to as "price-time". Below is a side-by-side comparison of how neighborhoods of similar historical points appear in three-dimensional Euclidean Space and Lorentzian Space: This figure demonstrates how Lorentzian space can better accommodate the warping of price-time since the Lorentzian distance function compresses the Euclidean neighborhood in such a way that the new neighborhood distribution in Lorentzian space tends to cluster around each of the major feature axes in addition to the origin itself. This means that, even though some nearest neighbors will be the same regardless of the distance metric used, Lorentzian space will also allow for the consideration of historical points that would otherwise never be considered with a Euclidean distance metric. Intuitively, the advantage inherent in the Lorentzian distance metric makes sense. For example, it is logical that the price action that occurs in the hours after Chairman Powell finishes delivering a speech would resemble at least some of the previous times when he finished delivering a speech. This may be true regardless of other factors, such as whether or not the market was overbought or oversold at the time or if the macro conditions were more bullish or bearish overall. These historical reference points are extremely valuable for predictive models, yet the Euclidean distance metric would miss these neighbors entirely, often in favor of irrelevant data points from the day before the event. By using Lorentzian distance as a metric, the ML model is instead able to consider the warping of price-time caused by the event and, ultimately, transcend the temporal bias imposed on it by the time series. For more information on the implementation details of the Approximate Nearest Neighbors (ANN) algorithm used in this indicator, please refer to the detailed comments in the source code. █ HOW TO USE Below is an explanatory breakdown of the different parts of this indicator as it appears in the interface: Below is an explanation of the different settings for this indicator: General Settings: Source - This has a default value of "hlc3" and is used to control the input data source. Neighbors Count - This has a default value of 8, a minimum value of 1, a maximum value of 100, and a step of 1. It is used to control the number of neighbors to consider. Max Bars Back - This has a default value of 2000. Feature Count - This has a default value of 5, a minimum value of 2, and a maximum value of 5. It controls the number of features to use for ML predictions. Color Compression - This has a default value of 1, a minimum value of 1, and a maximum value of 10. It is used to control the compression factor for adjusting the intensity of the color scale. Show Exits - This has a default value of false. It controls whether to show the exit threshold on the chart. Use Dynamic Exits - This has a default value of false. It is used to control whether to attempt to let profits ride by dynamically adjusting the exit threshold based on kernel regression. Feature Engineering Settings: Note: The Feature Engineering section is for fine-tuning the features used for ML predictions. The default values are optimized for the 4H to 12H timeframes for most charts, but they should also work reasonably well for other timeframes. By default, the model can support features that accept two parameters (Parameter A and Parameter B, respectively). Even though there are only 4 features provided by default, the same feature with different settings counts as two separate features. If the feature only accepts one parameter, then the second parameter will default to EMA-based smoothing with a default value of 1. These features represent the most effective combination I have encountered in my testing, but additional features may be added as additional options in the future. Feature 1 - This has a default value of "RSI" and options are: "RSI", "WT", "CCI", "ADX". Feature 2 - This has a default value of "WT" and options are: "RSI", "WT", "CCI", "ADX". Feature 3 - This has a default value of "CCI" and options are: "RSI", "WT", "CCI", "ADX". Feature 4 - This has a default value of "ADX" and options are: "RSI", "WT", "CCI", "ADX". Feature 5 - This has a default value of "RSI" and options are: "RSI", "WT", "CCI", "ADX". Filters Settings: Use Volatility Filter - This has a default value of true. It is used to control whether to use the volatility filter. Use Regime Filter - This has a default value of true. It is used to control whether to use the trend detection filter. Use ADX Filter - This has a default value of false. It is used to control whether to use the ADX filter. Regime Threshold - This has a default value of -0.1, a minimum value of -10, a maximum value of 10, and a step of 0.1. It is used to control the Regime Detection filter for detecting Trending/Ranging markets. ADX Threshold - This has a default value of 20, a minimum value of 0, a maximum value of 100, and a step of 1. It is used to control the threshold for detecting Trending/Ranging markets. Kernel Regression Settings: Trade with Kernel - This has a default value of true. It is used to control whether to trade with the kernel. Show Kernel Estimate - This has a default value of true. It is used to control whether to show the kernel estimate. Lookback Window - This has a default value of 8 and a minimum value of 3. It is used to control the number of bars used for the estimation. Recommended range: 3-50 Relative Weighting - This has a default value of 8 and a step size of 0.25. It is used to control the relative weighting of time frames. Recommended range: 0.25-25 Start Regression at Bar - This has a default value of 25. It is used to control the bar index on which to start regression. Recommended range: 0-25 Display Settings: Show Bar Colors - This has a default value of true. It is used to control whether to show the bar colors. Show Bar Prediction Values - This has a default value of true. It controls whether to show the ML model's evaluation of each bar as an integer. Use ATR Offset - This has a default value of false. It controls whether to use the ATR offset instead of the bar prediction offset. Bar Prediction Offset - This has a default value of 0 and a minimum value of 0. It is used to control the offset of the bar predictions as a percentage from the bar high or close. Backtesting Settings: Show Backtest Results - This has a default value of true. It is used to control whether to display the win rate of the given configuration. █ WORKS CITED (1) R. Giusti and G. E. A. P. A. Batista, "An Empirical Comparison of Dissimilarity Measures for Time Series Classification," 2013 Brazilian Conference on Intelligent Systems, Oct. 2013, DOI: 10.1109/bracis.2013.22. (2) Y. Kerimbekov, H. Ş. Bilge, and H. H. Uğurlu, "The use of Lorentzian distance metric in classification problems," Pattern Recognition Letters, vol. 84, 170–176, Dec. 2016, DOI: 10.1016/j.patrec.2016.09.006. (3) A. Bagnall, A. Bostrom, J. Large, and J. Lines, "The Great Time Series Classification Bake Off: An Experimental Evaluation of Recently Proposed Algorithms." ResearchGate, Feb. 04, 2016. (4) H. Ş. Bilge, Yerzhan Kerimbekov, and Hasan Hüseyin Uğurlu, "A new classification method by using Lorentzian distance metric," ResearchGate, Sep. 02, 2015. (5) Y. Kerimbekov and H. Şakir Bilge, "Lorentzian Distance Classifier for Multiple Features," Proceedings of the 6th International Conference on Pattern Recognition Applications and Methods, 2017, DOI: 10.5220/0006197004930501. (6) V. Surya Prasath et al., "Effects of Distance Measure Choice on KNN Classifier Performance - A Review." . █ ACKNOWLEDGEMENTS @veryfid - For many invaluable insights, discussions, and advice that helped to shape this project. @capissimo - For open sourcing his interesting ideas regarding various KNN implementations in PineScript, several of which helped inspire my original undertaking of this project. @RikkiTavi - For many invaluable physics-related conversations and for his helping me develop a mechanism for visualizing various distance algorithms in 3D using JavaScript @jlaurel - For invaluable literature recommendations that helped me to understand the underlying subject matter of this project. @annutara - For help in beta-testing this indicator and for sharing many helpful ideas and insights early on in its development. @jasontaylor7 - For helping to beta-test this indicator and for many helpful conversations that helped to shape my backtesting workflow @meddymarkusvanhala - For helping to beta-test this indicator @dlbnext - For incredibly detailed backtesting testing of this indicator and for sharing numerous ideas on how the user experience could be improved.
Pine Script® indicator
by jdehorty
783
Hurst Diamond Notation PivotsThis is a fairly simple indicator for diamond notation of past hi/lo pivot points, a common method in Hurst analysis. The diamonds mark the troughs/peaks of each cycle. They are offset by their lookback and thus will not 'paint' until after they happen so anticipate accordingly. Practically, traders can use the average length of past pivot periods to forecast future pivot periods in time🔮. For example, if the average/dominant number of bars in an 80-bar pivot point period/cycle is 76, then a trader might forecast that the next pivot could occur 76-ish bars after the last confirmed pivot. The numbers/labels on the y-axis display the cycle length used for pivot detection. This indicator doesn't repaint, but it has a lot of lag; Please use it for forecasting instead of entry signals. This indicator scans for new pivots in the form of a rainbow line and circle; once the hi/lo has happened and the lookback has passed then the pivot will be plotted. The rainbow color per wavelength theme seems to be authentic to Hurst (or modern Hurst software) and has been included as a default.
Pine Script® indicator
by BarefootJoey
84
Harmonic Patterns Based Trend FollowerEarlier this week, published an idea on how harmonic patterns can be used for trend following. This script is an attempt to implement the same. 🎲 Process 🎯 Derive Zigzag and scan harmonic patterns for last 5 confirmed pivots 🎯 If a pattern is found, highest point of pattern will become the bullish zone and lower point of the pattern will become bearish zone. 🎯 Since it is trend following method, when price reaches bullish zone, then the trend is considered as bullish and when price reaches bearish zone, the trend is considered as bearish. 🎯 If price does not touch both regions, then trend remains unchanged. 🎯 Bullish and bearish zone will change as and when new patterns are formed. 🎲 Note Patterns are not created on latest pivot as last pivot will be unconfirmed and moving. Due to this, patterns appear after certain delay - patterns will not be real time. But, this is expected and does not impact the overall process. When new pattern formed When price breaks over the zones 🎲 Output 🎯 Patterns formed are drawn in blue coloured lines. Due to pine limitation of max 500 lines, older patterns automatically get deleted when new ones come. 🎯 Bullish Zone and Bearish Zone are plotted in green and red colours and the zone will change whenever new pattern comes along. 🎯 Bar colors are changed according to calculated trend. Trend value can be 1 or -1 based on the current trend. You can also find the value in data window. 🎯 For simplicity purpose, input option for selection of specific patterns are not provided and also pattern names are not displayed on the chart.
Pine Script® indicator
by Trendoscope
35
CVD - Cumulative Volume Delta (Chart)█   OVERVIEW This indicator displays cumulative ​volume delta (​CVD) as an on-chart oscillator. It uses intrabar analysis to obtain more precise ​volume delta information compared to methods that only use the chart's timeframe. The core concepts in this script come from our first ​ CVD indicator , which displays CVD​ values as plot candles in a separate indicator pane. In this script, CV​D values are scaled according to price ranges and represented on the main chart pane. █   CONCEPTS Bar polarity Bar polarity refers to the position of the close price relative to the open price. In other words, bar polarity is the direction of price change. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script utilizes a LTF to analyze intrabars, or price changes within a chart bar. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display information due to the limited number of intrabars that can be analyzed. Volume delta Volume delta is a measure that separates ​volume​ into "up" and "down" parts, then takes the difference to estimate the net demand for the asset. This approach gives traders a more detailed insight when analyzing volume​ and market sentiment. There are several methods for determining whether an asset's volume​ belongs in the "up" or "down" category. Some indicators, such as On Balance Volume​ and the Klinger Oscillator , use the change in price between bars to assign ​volume​ values to the appropriate category. Others, such as Chaikin Money Flow , make assumptions based on open, high, low, and close prices. The most accurate method involves using tick data to determine whether each transaction occurred at the bid or ask price and assigning the ​volume​ value to the appropriate category accordingly. However, this method requires a large amount of data on historical bars, which can limit the historical depth of charts and the number of symbols for which tick data is available. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. This indicator uses intrabar analysis to achieve a compromise between simplicity and accuracy in calculating ​volume delta on historical bars. Our Volume Profile indicators use it as well. Other ​volume delta indicators in our Community Scripts , such as the Realtime 5D Profile , use real-time chart updates to achieve more precise ​volume delta calculations. However, these indicators aren't suitable for analyzing historical bars since they only work for real-time analysis. This is the logic we use to assign intrabar ​volume to the "up" or "down" category:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars comprising a chart bar are analyzed, we calculate the net difference between "up" and "down" intrabar volume​ to produce the volume​ delta for the chart bar. █   FEATURES CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. By periodically resetting the volume​ delta accumulation, we can analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta accumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On trend changes : Calculations reset on the direction change of either the Aroon indicator, Parabolic SAR , or Supertrend .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Display This script displays raw or cumulative volume​ delta values on the chart as either line or histogram oscillator zones scaled according to the price chart, allowing traders to visualize volume​ activity on each bar or cumulatively over time. The indicator's background shows where CVD​ resets occur, demarcating the beginning of new zones. The vertical axis of each oscillator zone is scaled relative to the one with the highest price range, and the oscillator values are scaled relative to the highest volume​ delta. A vertical offset is applied to each oscillator zone so that the highest oscillator value aligns with the lowest price. This method ensures an accurate, intuitive visual comparison of volume​ activity within zones, as the scale is consistent across the chart, and oscillator values sit below prices. The vertical scale of oscillator zones can be adjusted using the "Zone Height" input in the script settings. This script displays labels at the highest and lowest oscillator values in each zone, which can be enabled using the "Hi/Lo Labels" input in the "Visuals" section of the script settings. Additionally, the oscillator's value on a chart bar is displayed as a tooltip when a user hovers over the bar, which can be enabled using the "Value Tooltips" input. Divergences occur when the polarity of ​volume delta does not match that of the chart bar. The script displays divergences as bar colors and background colors that can be enabled using the "Color bars on divergences" and "Color background on divergences" inputs. An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, the average quantity of intrabars per chart bar, and the number of chart bars for which there is LTF data. This is enabled using the "Show information box" input in the "Visuals" section of the script settings. FOR Pine Script™ CODERS  • This script utilizes `ltf()` and `ltfStats()` from the lower_tf library.   The `ltf()` function determines the appropriate lower timeframe from the selected calculation mode and chart timeframe, and returns it in a format that can be used with request.security_lower_tf() .   The `ltfStats()` function, on the other hand, is used to compute and display statistical information about the lower timeframe in an information box.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • The newly added session.isfirstbar_regular built-in allows for resetting the ​CVD segments at the start of the regular session.  • The VisibleChart library developed by our resident PineCoders team leverages the chart.left_visible_bar_time and chart.right_visible_bar_time variables to optimize the performance of this script.   These variables identify the opening time of the leftmost and rightmost visible bars on the chart, allowing the script to recalculate and draw objects only within the range of visible bars as the user scrolls.   This functionality also enables the scaling of the oscillator zones.   These variables are just a couple of the many new built-ins available in the chart.* namespace.   For more information, check out this blog post or look them up by typing "chart." in the Pine Script™ Reference Manual .  • Our ta library has undergone significant updates recently, including the incorporation of the `aroon()` indicator used as a method for resetting ​CVD segments within this script.   Revisit the library to see more of the newly added content! Look first. Then leap.
Pine Script® indicator
by TradingView
53
Musashi_Fractal_Dimension === Musashi-Fractal-Dimension === This tool is part of my research on the fractal nature of the markets and understanding the relation between fractal dimension and chaos theory. To take full advantage of this indicator, you need to incorporate some principles and concepts: - Traditional Technical Analysis is linear and Euclidean, which makes very difficult its modeling. - Linear techniques cannot quantify non-linear behavior - Is it possible to measure accurately a wave or the surface of a mountain with a simple ruler? - Fractals quantify what Euclidean Geometry can’t, they measure chaos, as they identify order in apparent randomness. - Remember: Chaos is order disguised as randomness. - Chaos is the study of unstable aperiodic behavior in deterministic non-linear dynamic systems - Order and randomness can coexist, allowing predictability. - There is a reason why Fractal Dimension was invented, we had no way of measuring fractal-based structures. - Benoit Mandelbrot used to explain it by asking: How do we measure the coast of Great Britain? - An easy way of getting the need of a dimension in between is looking at the Koch snowflake. - Market prices tend to seek natural levels of ranges of balance. These levels can be described as attractors and are determinant. Fractal Dimension Index ('FDI') Determines the persistence or anti-persistence of a market. - A persistent market follows a market trend. An anti-persistent market results in substantial volatility around the trend (with a low r2), and is more vulnerable to price reversals - An easy way to see this is to think that fractal dimension measures what is in between mainstream dimensions. These are: - One dimension: a line - Two dimensions: a square - Three dimensions: a cube. --> This will hint you that at certain moment, if the market has a Fractal Dimension of 1.25 (which is low), the market is behaving more “line-like”, while if the market has a high Fractal Dimension, it could be interpreted as “square-like”. - 'FDI' is trend agnostic, which means that doesn't consider trend. This makes it super useful as gives you clean information about the market without trying to include trend stuff. Question: If we have a game where you must choose between two options. 1. a horizontal line 2. a vertical line. Each iteration a Horizontal Line or a Square will appear as continuation of a figure. If it that iteration shows a square and you bet vertical you win, same as if it is horizontal and it is a line. - Wouldn’t be useful to know that Fractal dimension is 1.8? This will hint square. In the markets you can use 'FD' to filter mean-reversal signals like Bollinger bands, stochastics, Regular RSI divergences, etc. - Wouldn’t be useful to know that Fractal dimension is 1.2? This will hint Line. In the markets you can use 'FD' to confirm trend following strategies like Moving averages, MACD, Hidden RSI divergences. Calculation method: Fractal dimension is obtained from the ‘hurst exponent’. 'FDI' = 2 - 'Hurst Exponent' Musashi version of the Classic 'OG' Fractal Dimension Index ('FDI') - By default, you get 3 fast 'FDI's (11,12,13) + 1 Slow 'FDI' (21), their interaction gives useful information. - Fast 'FDI' cross will give you gray or red dots while Slow 'FDI' cross with the slowest of the fast 'FDI's will give white and orange dots. This are great to early spot trend beginnings or trend ends. - A baseline (purple) is also provided, this is calculated using a 21 period Bollinger bands with 1.618 'SD', once calculated, you just take midpoint, this is the 'TDI's (Traders Dynamic Index) way. The indicator will print purple dots when Slow 'FDI' and baseline crosses, I see them as Short-Term cycle changes. - Negative slope 'FDI' means trending asset. - Positive most of the times hints correction, but if it got overextended it might hint a rocket-shot. TDI Ranges: - 'FDI' between 1.0≤ 'FDI' ≤1.4 will confirm trend following continuation signals. - 'FDI' between 1.6≥ 'FDI' ≥2.0 will confirm reversal signals. - 'FDI' == 1.5 hints a random unpredictable market. Fractal Attractors - As you must know, fractals tend orbit certain spots, this are named Attractors, this happens with any fractal behavior. The market of course also shows them, in form of Support & Resistance, Supply Demand, etc. It’s obvious they are there, but now we understand that they’re not linear, as the market is fractal, so simple trendline might not be the best tool to model this. - I’ve noticed that when the Musashi version of the 'FDI' indicator start making a cluster of multicolor dots, this end up being an attractor, I tend to draw a rectangle as that area as price tend to come back (I still researching here). Extra useful stuff - Momentum / speed: Included by checking RSI Study in the indicator properties. This will add two RSI’s (9 and a 7 periods) plus a baseline calculated same way as explained for 'FDI'. This gives accurate short-term trends. It also includes RSI divergences (regular and hidden), deactivate with a simple check in the RSI section of the properties. - BBWP (Bollinger Bands with Percentile): Efficient way of visualizing volatility as the percentile of Bollinger bands expansion. This line varies color from Iced blue when low volatility and magma red when high. By default, comes with the High vols deactivated for better view of 'FDI' and RSI while all studies are included. DDWP is trend agnostic, just like 'FDI', which make it very clean at providing information. - Ultra Slow 'FDI': I noticed that while using BBWP and RSI, the indicator gets overcrowded, so there is the possibility of adding only one 'FDI' + its baseline. Final Note: I’ve shown you few ways of using this indicator, please backtest before using in real trading. As you know trading is more about risk and trade management than the strategy used. This still a work in progress, I really hope you find value out of it. I use it combination with a tool named “Musashi_Katana” (also found in TradingView). Best! Musashi
Pine Script® indicator
by Musashi-Alchemist
24
Dynamic Linear Regression ChannelsPlots new linear regression channels from points where a previous channel is broken thus keeping the length of bars in the trend dynamic. Regression channels are useful in detecting trend changes, support and resistance levels and to trade mean reversions. Note: Setting higher values of upper and lower deviation may result in error if the price never breaks the channel and the script references too many bars than supported.
Pine Script® indicator
by iravan
61
Electrocardiogram ChartThis is an attempt to develop alternative visualisation of financial charts. This script also makes use of new pine feature types which represents User Defined Object Types. You can refer to below documentation to understand more about this feature: www.tradingview.com www.tradingview.com 🎲 Structure of new chart components 🎯Instead of candles/bars, this type of chart contains Electrocardiogram blocks which resembles the heartbeat signals on electrocardiogram. Body color of the block is defined by the open and close prices of the bar. If close is greater than open, body is green. Otherwise, the body is painted red. Border color of the block is defined by the close prices of current and previous bar. If the close of current bar is greater than that of last bar, then the border color is green. Otherwise, border color is painted red. 🎯Inside each blocks there will be 5 connecting lines called the signal lines. open-open open-firstPeak(high or low of the bar whichever comes first) firstPeak-secondPeak(high or low of the bar whichever comes last) secondPeak-close close-close 🎯 Color of the signal lines are determined by which among the high/low of the bar comes last. If highest part of the bar reached after reaching the lowest part of the bar, then signal lines are coloured green signifying bullish sentiment towards the end of bar. If lowest part of the bar reached after reaching the highest part of the bar, then signal lines are coloured red signifying bearish sentiment towards the end of bar. Pictorial examples here: 🎲 Limitations with pinescript implementation Since, pinescript can only use maximum 500 lines and each block will take 1 box and 5 lines, it is not possible to display more than 100 bars. Each block of new Electrocardiogram chart will take the space of 7 bars of candlestick chart. Due to this, the alignment of regular OHLC candles is not inline with the new chart type. Background highlighting is done for the part of the OHLC candles where Electrocardiogram blocks are plotted so that it helps users to map the bars manually Thanks to @theheirophant for suggestion of name :)
Pine Script® indicator
by Trendoscope
48