Auf geht's

In den Scripts nach "美股标普500指数基金中国" suchen

Momentum Performance This Indicator displays the momentum (performance) of the symbol in percent. You can compare the performance with other symbols. The default benchmarks are the S&P 500, the MSCI World and the FTSE All World EX US. The default length corresponds to one year in the timeframes monthly, weekly and daily. In intraday the default length is 200, but you can also set your own setting. You have also the opportunity to display a average momentum performance of the main symbol.
Pine Script® Indikator
von brettkind
SPX Intraday Mood IndicatorThe SPX Intraday Mood Indicator tries to gauge the intraday market direction of the S&P 500 (SPX) by focusing on internal market data. Based on the 0DTE Mood Indicator concept. Overall strength/weakness is converted into a directional Mood Percentage which can help with choosing a trade type. Use at your own risk and discretion. Potential trade ideas offer no guarantees. Intraday Charts Only. Turn off extended hours data. Only works on SPX. This first version is untested and I am only sharing it to gather feedback on its accuracy, use at your own risk.
Pine Script® Indikator
von millerrh
50
5MA_X_LThis is a 5 day moving average crossing long strategy in 10 min. chart, used in short term momentum trading strategy. Momentum trading Strategy: When S&P 500 index is at up trend (or above 60 sma ), buy 10+ stocks in top 20% stock RS ranking at equal weight using this MA5X_L strategy. Change stocks when any stock exited by algorithm. Back test start since 2020/7/1, each long entry for condition 1 is $30000, condition 2 is $20000, with max of 2 long positions. Setup: 10 minutes chart Buy condition 1) 3 wma cross up 195 wma (5day) 2) 3wma > 78wma > 195wma UP Trend Arrangement (UTA) Exit condition 1) 3 wma cross under 195 wma 2) position profit > 20% and 3 wma cross under 6 ATRs line (green)
Pine Script® Strategie
von FinTasticTrading
Stochastic Optimized Trend Tracker *Strategy*Stochastic OTT is Anıl Özekşi's latest derived version of Optimized Trend Tracker on Stochastic Oscillator. He tried to solve the fake signals of Stochastic Oscillator by adopting OTT on the indicator. He advised users to set the stochastic smoothing parameters to 500 and 200 on his latest video about SOTT. He personally uses 1 min charts on stock market so the parameters of the indicator might have to be optimized for other time frames nad markets. He exaggerated the Stochastic to 1000's to have better signals of percent values of OTT . Also hes used VIDYA in both calculations of OTT and Stochastic smoothing. Said, Kıvanç Özbilgiç. I just made a Strategy version of the script so that we lads can backtest it. The codes for that are yet again from Kıvanç Özbilgiç :) I just copy-pasted a few and did some adjustments. Hope you enjoy! #betonyetmez
Pine Script® Strategie
von lucidreamer15
11
Stochastic OTTStochastic OTT is Anıl Özekşi's latest derived version of Optimized Trend Tracker on Stochastic Oscillator. You might like to view the original version of the indicator if you don't know about OTT yet: He tried to solve the fake signals of Stochastic Oscillator by adopting OTT on the indicator. He advised users to set the stochastic smoothing parameters to 500 and 200 on his latest video about SOTT. He personally uses 1 min charts on stock market so the parameters of the indicator might have to be optimized for other time frames nad markets. He exaggerated the Stochastic to 1000's to have better signals of percent values of OTT. Also hes used VIDYA in both calculations of OTT and Stochastic smoothing. Hope you'll enjoy the SOTT in your profitable trades. Kıvanç
Pine Script® Indikator
von KivancOzbilgic
49
stop out or margin call price levelsAbstract This script finds the potential stop out or margin call price levels without considering timeframe. This script computes stop out or margin call price levels that over leveraged positions buy cheap enough. You can use this indicator to follow stop hunters. Introduction Stop hunting exists because of benefit conflict. When most of retails traders are in the correct direction, big banks do not want to buy more expensive then retail traders. Therefore, Big banks create sell pressure to make retail traders misunderstand their trade decisions are wrong. When retail traders decide to cut loss, it is time big banks buy cheaper. Many courses recommend average true range as a stop loss reference. However, in different timeframe, average true ranges are different. Therefore, we need to have a method to measure potential stop hunting levels which is not relative to timeframe. There is a method because there are observable levels where over leveraged positions must cut loss. For example, for a 100 leverage position, its margin call level is 0.005, so 0.005 drawdown is a potential stop hunting level. Computing For buy potential stop out or margin call price level = low * ( 1 - ratio ) For sell potential stop out or margin call price level = high * ( 1 + ratio ) Parameters There are 4 levels available for adjusting. The default values are : (1) 0.001 : 500 leverage , 50% margin call (2) 0.0025 : 200 leverage , 50% margin call (3) 0.005 : 100 leverage , 50% margin call (4) 0.010 : 50 leverage , 50% margin call Usage (1) Find an oversold price level. If you don't want to use an another indicator, you can use previous low. (2) Memorize their stop out or margin call price levels of that level. (2) Consider buy near those levels. (3) If there are quick price rejection near those levels, better entry opportunities. (4) Take profit and stop loss : you decide. Conclusion This script can find potential stop out or margin call price levels that over leveraged positions buy cheap enough. If you are bored, you can consider find 100 signals you are interested in and share your observation. Reference Brokers, leverage and margin call threshold
Pine Script® Indikator
von clocks156t174
1
Main MAs and EMAs multi-timeframe for supportObjective is to map out different multi-timeframe support/resistance , all at once. Includes weekly, daily and 4H EMAs and MAs, as per the follow (allowing customization) WEEKLY (in pink/purple variations): - 13 EMA - 21 EMA - 34 EMA - 50 M.A DAILY (in green variations): - 21 EMA - 50 EMA - 120 M.A. - 200 M.A. 4H (in yellow/golden colors): - 400 EMA - 500 EMA - 675 EMA - 715 EMA - 920 EMA - 1150 EMA Notes: - Quite useful to all types of assets; crypto, commodities , stocks, etc... - Ideally not to be visible all the time, as it can "pollute" the charts. But very helpful in moments of great volatility
Pine Script® Indikator
von Ferafer
Pinescript - Common Label & Line Array Functions Library by RRBPinescript - Common Label & Line Array Functions Library by RagingRocketBull 2021 Version 1.0 This script provides a library of common array functions for arrays of label and line objects with live testing of all functions. Using this library you can easily create, update, delete, join label/line object arrays, and get/set properties of individual label/line object array items. You can find the full list of supported label/line array functions below. There are several libraries: - Common String Functions Library - Standard Array Functions Library - Common Fixed Type Array Functions Library - Common Label & Line Array Functions Library - Common Variable Type Array Functions Library Features: - 30 array functions in categories create/update/delete/join/get/set with support for both label/line objects (45+ including all implementations) - Create, Update label/line object arrays from list/array params - GET/SET properties of individual label/line array items by index - Join label/line objects/arrays into a single string for output - Supports User Input of x,y coords of 5 different types: abs/rel/rel%/inc/inc% list/array, auto transforms x,y input into list/array based on type, base and xloc, translates rel into abs bar indexes - Supports User Input of lists with shortened names of string properties, auto expands all standard string properties to their full names for use in functions - Live Output for all/selected functions based on User Input. Test any function for possible errors you may encounter before using in script. - Output filters: hide all excluded and show only allowed functions using a list of function names - Output Panel customization options: set custom style, color, text size, and line spacing Usage: - select create function - create label/line arrays from lists or arrays (optional). Doesn't affect the update functions. The only change in output should be function name regardless of the selected implementation. - specify num_objects for both label/line arrays (default is 7) - specify common anchor point settings x,y base/type for both label/line arrays and GET/SET items in Common Settings - fill lists with items to use as inputs for create label/line array functions in Create Label/Line Arrays section - specify label/line array item index and properties to SET in corresponding sections - select label/line SET function to see the changes applied live Code Structure: - translate x,y depending on x,y type, base and xloc as specified in UI (required for all functions) - expand all shortened standard property names to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - create param arrays from string lists (required for create/update* from arrays and set* functions, not needed for create/update* from lists) - create label/line array from string lists (property names are auto expanded) or param arrays (requires already expanded properties) - update entire label/line array or - get/set label/line array item properties by index Transforming/Expanding Input values: - for this script to work on any chart regardless of price/scale, all x*,y* are specified as % increase relative to x0,y0 base levels by default, but user can enter abs x,price values specific for that chart if necessary. - all lists can be empty, contain 1 or several items, have the same/different lengths. Array Length = min(min(len(list*)), mum_objects) is used to create label/line objects. Missing list items are replaced with default property values. - when a list contains only 1 item it is duplicated (label name/tooltip is also auto incremented) to match the calculated Array Length - since this script processes user input, all x,y values must be translated to abs bar indexes before passing them to functions. Your script may provide all data internally and doesn't require this step. - at first int x, float y arrays are created from user string lists, transformed as described below and returned as x,y arrays. - translated x,y arrays can then be passed to create from arrays function or can be converted back to x,y string lists for the create from lists function if necessary. - all translation logic is separated from create/update/set functions for the following reasons: - to avoid redundant code/dependency on ext functions/reduce local scopes and to be able to translate everything only once in one place - should be faster - to simplify internal logic of all functions - because your script may provide all data internally without user input and won't need the translation step - there are 5 types available for both x,y: abs, rel, rel%, inc, inc%. In addition to that, x can be: bar index or time, y is always price. - abs - absolute bar index/time from start bar0 (x) or price (y) from 0, is >= 0 - rel - relative bar index/time from cur bar n (x) or price from y0 base level, is >= 0 - rel% - relative % increase of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc - relative increment (step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc% - relative % increment (% step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - x base level >= 0 - y base level can be 0 (empty) or open, close, high, low of cur bar - single item x1_list = "50" translates into: - for x type abs: "50, 50, 50 ..." num_objects times regardless of xloc => x = 50 - for x type rel: "50, 50, 50 ... " num_objects times => x = x_base + 50 - for x type rel%: "50%, 50%, 50% ... " num_objects times => x_base * (1 + 0.5) - for x type inc: "0, 50, 100 ... " num_objects times => x_base + 50 * i - for x type inc%: "0%, 50%, 100% ... " num_objects times => x_base * (1 + 0.5 * i) - when xloc = xloc.bar_index each rel*/inc* value in the above list is then subtracted from n: n - x to convert rel to abs bar index, values of abs type are not affected - x1_list = "0, 50, 100, ..." of type rel is the same as "50" of type inc - x1_list = "50, 50, 50, ..." of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "50" - single item y1_list = "2" translates into (ragardless of yloc): - for y type abs: "2, 2, 2 ..." num_objects times => y = 2 - for y type rel: "2, 2, 2 ... " num_objects times => y = y_base + 2 - for y type rel%: "2%, 2%, 2% ... " num_objects times => y = y_base * (1 + 0.02) - for y type inc: "0, 2, 4 ... " num_objects times => y = y_base + 2 * i - for y type inc%: "0%, 2%, 4% ... " num_objects times => y = y_base * (1 + 0.02 * i) - when yloc != yloc.price all calculated values above are simply ignored - y1_list = "0, 2, 4" of type rel% is the same as "2" with type inc% - y1_list = "2, 2, 2" of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "2" - you can enter shortened property names in lists. To lookup supported shortened names use corresponding dropdowns in Set Label/Line Array Item Properties sections - all shortened standard property names must be expanded to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - examples of shortened property names that can be used in lists: bar_index, large, solid, label_right, white, left, left, price - expanded to their corresponding full names: xloc.bar_index, size.large, line.style_solid, label.style_label_right, color.white, text.align_left, extend.left, yloc.price - all expanding logic is separated from create/update* from arrays and set* functions for the same reasons as above, and because param arrays already have different types, implying the use of final values. - all expanding logic is included in the create/update* from lists functions because it seemed more natural to process string lists from user input directly inside the function, since they are already strings. Creating Label/Line Objects: - use study max_lines_count and max_labels_count params to increase the max number of label/line objects to 500 (+3) if necessary. Default number of label/line objects is 50 (+3) - all functions use standard param sequence from methods in reference, except style always comes before colors. - standard label/line.get* functions only return a few properties, you can't read style, color, width etc. - label.new(na, na, "") will still create a label with x = n-301, y = NaN, text = "" because max default scope for a var is 300 bars back. - there are 2 types of color na, label color requires color(na) instead of color_na to prevent error. text_color and line_color can be color_na - for line to be visible both x1, x2 ends must be visible on screen, also when y1 == y2 => abs(x1 - x2) >= 2 bars => line is visible - xloc.bar_index line uses abs x1, x2 indexes and can only be within 0 and n ends, where n <= 5000 bars (free accounts) or 10000 bars (paid accounts) limit, can't be plotted into the future - xloc.bar_time line uses abs x1, x2 times, can't go past bar0 time but can continue past cur bar time into the future, doesn't have a length limit in bars. - xloc.bar_time line with length = exact number of bars can be plotted only within bar0 and cur bar, can't be plotted into the future reliably because of future gaps due to sessions on some charts - xloc.bar_index line can't be created on bar 0 with fixed length value because there's only 1 bar of horiz length - it can be created on cur bar using fixed length x < n <= 5000 or - created on bar0 using na and then assigned final x* values on cur bar using set_x* - created on bar0 using n - fixed_length x and then updated on cur bar using set_x*, where n <= 5000 - default orientation of lines (for style_arrow* and extend) is from left to right (from bar 50 to bar 0), it reverses when x1 and x2 are swapped - price is a function, not a line object property Variable Type Arrays: - you can't create an if/function that returns var type value/array - compiler uses strict types and doesn't allow that - however you can assign array of any type to another array of any type creating an arr pointer of invalid type that must be reassigned to a matching array type before used in any expression to prevent error - create_any_array2 uses this loophole to return an int_arr pointer of a var type array - this works for all array types defined with/without var keyword and doesn't work for string arrays defined with var keyword for some reason - you can't do this with var type vars, only var type arrays because arrays are pointers passed by reference, while vars are actual values passed by value. - you can only pass a var type value/array param to a function if all functions inside support every type - otherwise error - alternatively values of every type must be passed simultaneously and processed separately by corresponding if branches/functions supporting these particular types returning a common single type result - get_var_types solves this problem by generating a list of dummy values of every possible type including the source type, tricking the compiler into allowing a single valid branch to execute without error, while ignoring all dummy results Notes: - uses Pinescript v3 Compatibility Framework - uses Common String Functions Library, Common Fixed Type Array Functions Library, Common Variable Type Array Functions Library - has to be a separate script to reduce the number of local scopes/compiled file size, can't be merged with another library. - lets you live test all label/line array functions for errors. If you see an error - change params in UI - if you see "Loop too long" error - hide/unhide or reattach the script - if you see "Chart references too many candles" error - change x type or value between abs/rel*. This can happen on charts with 5000+ bars when a rel bar index x is passed to label.new or line.new instead of abs bar index n - x - create/update_label/line_array* use string lists, while create/update_label/line_array_from_arrays* use array params to create label/line arrays. "from_lists" is dropped to shorten the names of the most commonly used functions. - create_label/line_array2,4 are preferable, 5,6 are listed for pure demonstration purposes only - don't use them, they don't improve anything but dramatically increase local scopes/compiled file size - for this reason you would mainly be using create/update_label/line_array2,4 for list params or create/update_label/line_array_from_arrays2 for array params - all update functions are executed after each create as proof of work and can be disabled. Only create functions are required. Use update functions when necessary - when list/array params are changed by your script. - both lists and array item properties use the same x,y_type, x,y_base from common settings - doesn't use pagination, a single str contains all output - why is this so complicated? What are all these functions for? - this script merges standard label/line object methods with standard array functions to create a powerful set of label/line object array functions to simplify manipulation of these arrays. - this library also extends the functionality of Common Variable Type Array Functions Library providing support for label/line types in var type array functions (any_to_str6, join_any_array5) - creating arrays from either lists or arrays adds a level of flexibility that comes with complexity. It's very likely that in your script you'd have to deal with both string lists as input, and arrays internally, once everything is converted. - processing user input, allowing customization and targeting for any chart adds a whole new layer of complexity, all inputs must be translated and expanded before used in functions. - different function implementations can increase/reduce local scopes and compiled file size. Select a version that best suits your needs. Creating complex scripts often requires rewriting your code multiple times to fit the limits, every line matters. P.S. Don't rely too much on labels, for too often they are fables. List of functions*: * - functions from other libraries are not listed 1. Join Functions Labels - join_label_object(label_, d1, d2) - join_label_array(arr, d1, d2) - join_label_array2(arr, d1, d2, d3) Lines - join_line_object(line_, d1, d2) - join_line_array(arr, d1, d2) - join_line_array2(arr, d1, d2, d3) Any Type - any_to_str6(arr, index, type) - join_any_array4(arr, d1, d2, type) - join_any_array5(arr, d, type) 2. GET/SET Functions Labels - label_array_get_text(arr, index) - label_array_get_xy(arr, index) - label_array_get_fields(arr, index) - label_array_set_text(arr, index, str) - label_array_set_xy(arr, index, x, y) - label_array_set_fields(arr, index, x, y, str) - label_array_set_all_fields(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) - label_array_set_all_fields2(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) Lines - line_array_get_price(arr, index, bar) - line_array_get_xy(arr, index) - line_array_get_fields(arr, index) - line_array_set_text(arr, index, width) - line_array_set_xy(arr, index, x1, y1, x2, y2) - line_array_set_fields(arr, index, x1, y1, x2, y2, width) - line_array_set_all_fields(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) - line_array_set_all_fields2(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) 3. Create/Update/Delete Functions Labels - delete_label_array(label_arr) - create_label_array(list1, list2, list3, list4, list5, d) - create_label_array2(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array3(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array4(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array5(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array6(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array2(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array4(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array_from_arrays2(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - create_label_array_from_arrays4(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - update_label_array_from_arrays2(label_arr, x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) Lines - delete_line_array(line_arr) - create_line_array(list1, list2, list3, list4, list5, list6, d) - create_line_array2(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array3(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array4(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array5(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array6(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array2(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array4(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array_from_arrays2(x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d) - update_line_array_from_arrays2(line_arr, x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d)
Pine Script® Indikator
von RagingRocketBull
13
Bollinger DCA v1Simple "benchmark" strategy for ETFs, Stocks and Crypto! Super-easy to implement for beginners, a BTD (buy-the-dip) strategy means that you buy a fixed amount of an ETF / Stock / Crypto every time it falls. For instance, to BTD the S&P 500 ( SPY ), you could purchase $500 USD each time the price falls. Assuming the macro-economic conditions of the underlying country remain favourable, BTD strategies will result in capital gains over a period of many years, e.g. 10 years. Recommended Chart Settings: Asset Class: ETF / Stocks / Crypto Time Frame: H1 (Hourly) / D1 (Daily) / W1 (Weekly) / M1 (Monthly) Necessary ETF Macro Conditions: 1. Country must have healthy demographics, good ratio of young > old 2. Country population must be increasing 3. Country must be experiencing price-inflation Necessary Stock Conditions: 1. Growing revenue 2. Growing net income 3. Consistent net margins 4. Higher gross/net profit margin compared to its peers in the industry 5. Growing share holders equity 6. Current ratios > 1 7. Debt to equity ratio (compare to peers ) 8. Debt servicing ratio < 30% 9. Wide economic moat 10. Products and services used daily, and will stay relevant for at least 1 decade Necessary Crypto Conditions: 1. Honest founders 2. Competent technical co-founders 3. Fair or non-existent pre-mine 4. Solid marketing and PR 5. Legitimate use-cases / adoption Default Robot Settings: Contribution (USD): $500 When: Dips below lower Bollinger Band *Robot buys $500 worth of ETF , Stock, Crypto, every time price falls below the lower Bollinger Band *Equity curve can be seen from the bottom panel* Risk Warning: This strategy is low-risk, however it assumes you have a long time horizon of at least 5 to 10 years. The longer your holding-period, the better your returns. The only thing the user has to keep-in-mind are the macro-economic conditions as stated above. If unsure, please stick to ETFs rather than buying individual stocks or cryptocurrencies.
Pine Script® Strategie
von UnknownUnicorn1373033
1
Fixed price Stop Loss [Takazudo]This strategy is a demo for fixed price stop loss. This strategy enables you to specify fixed price stop loss. Let's say your deposit is USD. When you trade EURCAD, you need to specify the quantity for trade. Here comes three chances for trade. A: SL pips: 500 B: SL pips: 200 C: SL pips: 100 In these trade, the risk is different for each. ABC risk ratio is 5:2:1. And, you cannot know how much to lose if the price hits the stop loss. This is a huge problem. With this strategy, You can specify the fixed risk price for each trade. If you specify 100 USD for the risk, this strategy calculates how much quantity to buy or sell for each entry. In the case above, this strategy guides you how much quantity to buy or sell like below. A: 2,000 qty (SL: 500pips) B: 5,000 qty (SL: 200pips) C: 10,000 qty (SL: 100pips) If you make entries with those quantity and the price hits the stop loss, You will lose the money like below. A: 100 USD B: 100 USD C: 100 USD This is what this script does. Fixed price SL. I tested this caliculation for OANDA's main 28 currency pairs forex listed below. AUDUSD, EURUSD, GBPUSD, NZDUSD, USDCAD, USDCHF, USDJPY, AUDCAD, AUDCHF, AUDJPY, AUDNZD, CADCHF, CADJPY, CHFJPY, EURAUD, EURCAD, EURCHF, EURGBP, EURJPY, EURNZD, GBPAUD, GBPCAD, GBPCHF, GBPJPY, GBPNZD, NZDCAD, NZDCHF, NZDJPY I may add more pairs later. Note: The entry strategy in this script is not intented to win. Check the result. Be careful.
Pine Script® Strategie
von Takazudo
Key SR Levels. I am the original creator of this indicator for tradingview, it can be used separately now, it is a PVSRA indicator, where it marks the key points of support and resistance. Market makers pull the market above the key level for distribution in bearish and pull below the key level for accumulation in bullish Mainly used for We have Whole level: main resistance ended in 000 We have a Key level ending in 250 We have half level finished in 500 And we have a Key level ending in 750. Enjoy the indicator, share with friends. If it happens to be dented, pull until the graph stretches. Note. This indicator works only for Forex, it can make a difference in pairs with Japanese Yen.
Pine Script® Indikator
von Victoredbr
15
Combo VIX and DXYHello traders It's been a while :) I wanted to share a cool script that you can use for any asset class. The script isn't really special - though what it displays is super helpful Volatility Index $VIX (Source: Wikipedia) VIX is the ticker symbol and the popular name for the Chicago Board Options Exchange's CBOE Volatility Index, a popular measure of the stock market's expectation of volatility based on S&P 500 index options. It is calculated and disseminated on a real-time basis by the CBOE, and is often referred to as the fear index or fear gauge. I consider that a $VIX above 30% is a very bearish signal. Above 30% translating investors selling in masse their assets. #blood #on #the #street Dollar Index $DXY (Source: Wikipedia) The U.S. Dollar Index (USDX, DXY, DX, or, informally, the "Dixie") is an index (or measure) of the value of the United States dollar relative to a basket of foreign currencies, often referred to as a basket of U.S. trade partners' currencies. The Index goes up when the U.S. dollar gains "strength" (value) when compared to other currencies. The index is designed, maintained, and published by ICE (Intercontinental Exchange, Inc.), with the name "U.S. Dollar Index" a registered trademark. It is a weighted geometric mean of the dollar's value relative to following select currencies: Euro (EUR), 57.6% weight Japanese yen (JPY) 13.6% weight Pound sterling (GBP), 11.9% weight Canadian dollar (CAD), 9.1% weight Swedish krona (SEK), 4.2% weight Swiss franc (CHF) 3.6% weight In "bear markets", the $DXY usually goes up. People are selling their hard assets to get some $USD in return - pumping the $DXY higher Corollary I'm not sure which one happens first between a bearish $DXY or bearish $DXY... though both are usually correlated If: - $VIX goes above 30%, usually $DXY increases and assets versus the good old' $USD drop - $VIX goes below 30%, usually $DXY decreases and assets versus the good old' $USD increases This is a nice lever effect between both the $VIX, $DXY and the assets versus the $USD That's being said, I don't only use those 2 information to enter in a trade. It gives me though a strong confirmation whenever I'm long or short Imagine I get a LONG signal but the combo $VIX + $DXY is bearish... this tells me to be cautious and to: - enter at a pullback - protect my position quickly at breakeven - take my profit quick For a mega bull market (some called it hyperinflation), you want your fiat to drop in value for the counter-asset to increase in value. And before you ask.... yes I look at what $DXY is doing before taking a trade on $BTCUSD :) In other words, $DXY going down is quite bullish for Bitcoin. Settings and Alerts The settings by default are the ones I use for my trading. The background colors will be colored whenever the COMBO is bullish (green) or bearish (red) Alerts are enabled using the brand new alert function published last week by @TradingView That's it for today, I hope you'll like it :) PS: In this chart above, I'm using the Supertrend indicator from @KivancOzbilgic Dave
Pine Script® Indikator
von Daveatt
8
Price Action - Support & Resistance by DGTSᴜᴘᴘᴏʀᴛ ᴀɴᴅ Rᴇꜱɪꜱᴛᴀɴᴄᴇ , is undoubtedly one of the key concepts of technical analysis █  Sᴜᴘᴘᴏʀᴛ ᴀɴᴅ Rᴇꜱɪꜱᴛᴀɴᴄᴇ Dᴇꜰɪɴɪᴛɪᴏɴ Support and Resistance terms are used by traders to refer to price levels on charts that tend to act as barriers, preventing the price of an financial instrument from getting pushed in a certain direction. A support level is a price level where buyers are more aggressive than sellers. This means that the price is more likely to "bounce" off this level rather than break through it. However, once the price has breached this level it is likely to continue falling until meeting another support level. A resistance level is the opposite of a support level. It is where the price tends to find resistance as it rises. Again, this means that the price is more likely to "bounce" off this level rather than break through it. However, once the price has breached this level it is likely to continue rising until meeting another resistance level. A previous support level will sometimes become a resistance level when the price attempts to move back up, and conversely, a resistance level will become a support level as the price temporarily falls back. █  Iᴅᴇɴᴛɪꜰʏɪɴɢ Sᴜᴘᴘᴏʀᴛ ᴀɴᴅ Rᴇꜱɪꜱᴛᴀɴᴄᴇ Support and resistance can come in various forms, and the concept is more difficult to master than it first appears. Identification of key support and resistance levels is an essential ingredient to successful technical analysis. If the price stalls and reverses in the same price area on minimum of two different occasions, then a horizontal line is drawn to show that the market is struggling to move past that area. Those areas are static barriers, one of the most popular forms of support/resistance and are highlighted with horizontal lines. Repeated test , the more often a support/resistance level is "tested" over an extended period of time (touched and bounced off by price), the more significance is given to that specific level High volume , the more buying and selling that has occurred at a particular price level, the stronger the support or resistance level is likely to be Market psychology , plays a major role as traders and investors remember the past and react to changing conditions to anticipate future market movement. Psychological levels , is a price level that significantly affects the price of an underlying financial instrument. Typically, near round numbers often serve as support and resistance The following support and resistance related topics are beyond the scope of this study, so they will be mentioned roughly only as a reference for support and resistance concept Trendlines , Support and resistance levels in trends are dynamic. Throughout an uptrend, levels of support tend to look like a trendline, usually clustering around higher lows. As the price rises, the price where buyers consider the stock to be “too cheap” also changes, which creates new support levels on the way up. The same is also true for resistance levels. In an uptrend, a stock is continuously breaking through perceived resistance levels and making new highs Moving Averages , is a constantly changing line that smooths out past price data while also allowing the trader to identify support and resistance. In the example Notice how the price of the asset finds support at the moving average when the trend is up, and how it acts as resistance when the trend is down The Fibonacci Retracement/Extension tool , is a favorite among many short-term traders because it clearly identifies levels of potential support and resistance Pivot Point Calculations , is another common technical analysis technique, where pivot point is calculated based on the high, low, and closing prices of previous trading session/day and support & resistance levels are projected based on the pivot point, different calculation techniques are available, as presented in this example of an pivot point indicator : PVTvX by DGT █  Tʀᴀᴅɪɴɢ Bᴀꜱᴇᴅ ᴏɴ Sᴜᴘᴘᴏʀᴛ ᴀɴᴅ Rᴇꜱɪꜱᴛᴀɴᴄᴇ Once an area or "zone" of support or resistance has been identified, those price levels can serve as potential entry or exit points because, as a price reaches a point of support or resistance, it will do one of two things—bounce back away from the support or resistance level (trading ranges), or violate the price level and continue in its direction (trading breakouts) —until it hits the next support or resistance level The basic trading method for using support and resistance is to buy near support in uptrends or the parts of ranges or chart patterns where prices are moving up and to sell/sell short near resistance in downtrends or the parts of ranges and chart patterns where prices are moving down. Buying near support or selling near resistance can pay off, but there is no assurance that the support or resistance will hold. Therefore, consider waiting for some confirmation that the market is still respecting that area Trading breakouts, a breakout is a potential trading opportunity that occurs when an asset's price moves above a resistance level or moves below a support level on increasing volume. The first step in trading breakouts is to identify current price trend patterns along with support and resistance levels in order to plan possible entry and exit points. Once the asset trades beyond the price barrier, volatility tends to increase and prices usually trend in the breakout's direction. Breakouts are such an important trading strategy since these setups are the starting point for future volatility increases, large price swings and, in many circumstances, major price trends. When trading breakouts, it is important to consider the underlying asset's support and resistance levels. The more times an asset price has touched these areas, the more valid these levels are and the more important they become. At the same time, the longer these support and resistance levels have been in play, the better the outcome when the asset price finally breaks out. Asset prices will often move slightly further than we expect them to. This doesn't happen all the time, but when it does it is called a false breakout. Therefore it is important to consider waiting for some confirmation while trading breakouts. It’s also popular for traders to sell 50% of their positions at the resistance level, and hold the rest in anticipation of a breakout above resistance █  Pʀɪᴄᴇ Aᴄᴛɪᴏɴ - Sᴜᴘᴘᴏʀᴛ & Rᴇꜱɪꜱᴛᴀɴᴄᴇ ʙʏ DGT Sᴛᴜᴅʏ This experimental study attempts to identify the support and resistance levels. Assumes a simple logic to discover moments where the price is rising or falling consecutively for minimum 3 bars with the condition volume increases on each bar and the last bar’s volume should be bigger than the long term volume moving average. A line will be drawn at the end of the move (highest or lowest, depending on the move direction), the line will be drawn at minimum on the 3rd bar and if condition holds for other consecutive bars the line will switch to 4th, 5th etc bar. Lines will not be deleted so the historical ones will remain and will emphasis the levels significance when they overlap in feature. Strong levels are more likely to hold and cause the price to move in the other direction, whereas the minor levels may only cause the price to pause and keep moving in the same direction. Determining future levels of support and resistance can drastically improve the returns of a short-term investing strategy Bar colors will be painted based on the volume of the specific bar to its long term volume moving average. This will help identifying the support and resistance levels significance and emphasis the sings of breakouts Finally, Volume spikes will be marked on top of the price chart. A high volume usually indicates more interest in the security and the presence of institutional traders. However, a rapidly rising price in an uptrend accompanied by a huge volume may be a sign of exhaustion. Traders usually look for breaks of support and resistance to enter positions. When security break critical levels without volume , you should consider the breakout suspect and prime for a reversal off the highs/lows. Volume spikes are often the result of news-driven events. Volume spike will often lead to sharp reversals since the moves are unsustainable due to the imbalance of supply and demand A good example with many support and resistance concepts observed on a stock chart and detected by the study Settings: Length of volume moving average, where volume moving average is used to detect support and resistance levels, is used as reference to compare with threshold values for volume spikes and colors of the bars Hint, to get more historical lines scrolling chart to left will enable visualization of them. Please note they may appear to much all 500 line limit is used 😉 Special thanks to @HEMANT Telegram user, for his observations and suggestions Disclaimer: Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold dgtrd TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script
Pine Script® Indikator
von dgtrd
297
Trend Reversal Indicator (EMA of slopes)Good morning Traders Inspirated by lukescream EMA-slope strategy, today I want to share with you this simple indicator whose possible use-case would be for detecting in advance possible trend reversals, specially on higher timeframes. Once that you've chosen the desired source (RSI, EMA or Stochastic k or d), the indicator will calculate its "slope" approximating its first order derivative by the division between the last variation of the series and its last value. You can see the slope as a white line by enabling the relative checkmark (it's disabled by default since it simply messes up the the graph) Then, the slope itself becomes the source for two exponential moving averages: the fast one (in blue) has a period of 20 while the slow one (in red, it becomes similiar to a horizontal line actually) has a period of 500 Why the slope? Since all the sources mentioned before are directly or indirectly calculated on the price action, a more aggressiveness in the price movement would be translated into a more (positive/negative) steepness of those indicator (of course this effect would be far more evident if the indicators are calculated on low periods, but really low periods could compromise the consistency of the signals). In this way, the slope would mirror the decisiveness of price movements and a comparison between two averages calculated from it (the first one based on more recent values, the second one that conisders also older values) could tell you in advance what direction the market is possibly about to take The usage is simple: once that the fast moving average crosses upward the slow one, this could be a sign of potential trend reversal from bearish to bullish. On the contrary, if the fast EMA crosses downward the slow one, this could be a sign of potential trend reversal from bullish to bearish. What I suggest you is to integrate this indicator with Exponential Moving Averages plotted on the price candles, in order to have a general bias for opening long or short positions, and with an oscillator as well such as the Stochastisc RSI in order to detect the overbought/oversold zones for opening/closing positions at the right moment. Happy Trading!
Pine Script® Indikator
von Drun30
8
Relative Volume at Time█  OVERVIEW This indicator calculates relative volume, which is the ratio of present volume over an average of past volume. It offers two calculation modes, both using a time reference as an anchor.                                          █  CONCEPTS Calculation modes The simplest way to calculate relative volume is by using the ratio of a bar's volume over a simple moving average of the last n volume values. This indicator uses one of two, more subtle ways to calculate both values of the relative volume ratio: current volume:past volume . The two calculations modes are:  1 — Cumulate from Beginning of TF to Current Bar where:     current volume = the cumulative volume since the beginning of the timeframe unit, and     past volume = the mean of volume during that same relative period of time in the past n timeframe units.  2 — Point-to-Point Bars at Same Offset from Beginning of TF where:     current volume = the volume on a single chart bar, and     past volume = the mean of volume values from that same relative bar in time from the past n timeframe units. Timeframe units Timeframe units can be defined in three different ways:  1 — Using Auto-steps, where the timeframe unit automatically adjusts to the timeframe used on the chart:     — A 1 min timeframe unit will be used on 1sec charts,     — 1H will be used for charts at 1min and less,     — 1D will be used for other intraday chart timeframes,     — 1W will be used for 1D charts,     — 1M will be used for charts at less than 1M,     — 1Y will be used for charts at greater or equal than 1M.  2 — As a fixed timeframe that you define.  3 — By time of day (for intraday chart timeframes only), which you also define. If you use non-intraday chart timeframes in this mode, the indicator will switch to Auto-steps. Relative Relativity A relative volume value of 1.0 indicates that current volume is equal to the mean of past volume , but how can we determine what constitutes a high relative volume value? The traditional way is to settle for an arbitrary threshold, with 2.0 often used to indicate that relative volume is worthy of attention. We wanted to provide traders with a contextual method of calculating threshold values, so in addition to the conventional fixed threshold value, this indicator includes two methods of calculating a threshold channel on past relative volume values:  1 — Using the standard deviation of relative volume over a fixed lookback.  2 — Using the highs/lows of relative volume over a variable lookback. Channels calculated on relative volume provide meta-relativity, if you will, as they are relative values of relative volume. █  FEATURES Controls in the "Display" section of inputs determine what is visible in the indicator's pane. The next "Settings" section is where you configure the parameters used in the calculations. The "Column Coloring Conditions" section controls the color of the columns, which you will see in three of the five display modes available. Whether columns are plotted or not, the coloring conditions also determine when markers appear, if you have chosen to show the markers in the "Display" section. The presence of markers is what triggers the alerts configured on this indicator. Finally, the "Colors" section of inputs allows you to control the color of the indicator's visual components. Display Five display modes are available:  • Current Volume Columns : shows columns of current volume , with past volume displayed as an outlined column.  • Relative Volume Columns : shows relative volume as a column.  • Relative Volume Columns With Average : shows relative volume as a column, with the average of relative volume.  • Directional Relative Volume Average : shows a line calculated using the average of +/- values of relative volume.   The positive value of relative volume is used on up bars; its negative value on down bars.  • Relative Volume Average : shows the average of relative volume. A Hull moving average is used to calculate the average used in the three last display modes. You can also control the display of:  • The value or relative volume, when in the first three display modes. Only the last 500 values will be shown.  • Timeframe transitions, shown in the background.  • A reminder of the active timeframe unit, which appears to the right of the indicator's last bar.  • The threshold used, which can be a fixed value or a channel, as determined in the next "Settings" section of inputs.  • Up/Down markers, which appear on transitions of the color of the volume columns (determined by coloring conditions), which in turn control when alerts are triggered.  • Conditions of high volatility. Settings Use this section of inputs to change:  • Calculation mode : this is where you select one of this indicator's two calculation modes for current volume and past volume , as explained in the "Concepts" section.  • Past Volume Lookback in TF units : the quantity of timeframe units used in the calculation of past volume .  • Define Timeframes Units Using : the mode used to determine what one timeframe unit is. Note that when using a fixed timeframe, it must be higher than the chart's timeframe.   Also, note that time of day timeframe units only work on intraday chart timeframes.  • Threshold Mode : Five different modes can be selected:    — Fixed Value : You can define the value using the "Fixed Threshold" field below. The default value is 2.0.    — Standard Deviation Channel From Fixed Lookback : This is a channel calculated using the simple moving average of relative volume     (so not the Hull moving average used elsewhere in the indicator), plus/minus the standard deviation multiplied by a user-defined factor.     The lookback used is the value of the "Channel Lookback" field. Its default is 100.    — High/Low Channel From Beginning of TF : in this mode, the High/Low values reset at the beginning of each timeframe unit.    — High/Low Channel From Beginning of Past Volume Lookback : in this mode, the High/Low values start from the farthest point back where we are calculating past volume ,     which is determined by the combination of timeframe units and the "Past Volume Lookback in TF units" value.    — High/Low Channel From Fixed Lookback : In this mode the lookback is fixed. You can define the value using the "Channel Lookback" field. The default value is 100.  • Period of RelVol Moving Average : the period of the Hull moving average used in the "Directional Relative Volume Average" and the "Relative Volume Average".  • High Volatility is defined using fast and slow ATR periods, so this represents the volatility of price.   Volatility is considered to be high when the fast ATR value is greater than its slow value. Volatility can be used as a filter in the column coloring conditions. Column Coloring Conditions  • Eight different conditions can be turned on or off to determine the color of the volume columns. All "ON" conditions must be met to determine a high/low state of relative volume,   or, in the case of directional relative volume, a bull/bear state.  • A volatility state can also be used to filter the conditions.  • When the coloring conditions and the filter do not allow for a high/low state to be determined, the neutral color is used.  • Transitions of the color of the volume columns determined by coloring conditions are used to plot the up/down markers, which in turn control when alerts are triggered. Colors  • You can define your own colors for all of the oscillator's plots.  • The default colors will perform well on light or dark chart backgrounds. Alerts  • An alert can be defined for the script. The alert will trigger whenever an up/down marker appears in the indicator's display.   The particular combination of coloring conditions and the display settings for up/down markers when you create the alert will determine which conditions trigger the alert.   After alerts are created, subsequent changes to the conditions controlling the display of markers will not affect existing alerts.  • By configuring the script's inputs in different ways before you create your alerts, you can create multiple, functionally distinct alerts from this script.   When creating multiple alerts, it is useful to include in the alert's message a reminder of the particular conditions you used for each alert.  • As is usually the case, alerts triggering "Once Per Bar Close" will prevent repainting. Error messages Error messages will appear at the end of the chart upon the following conditions:  • When the combination of the timeframe units used and the "Past Volume Lookback in TF units" value create a lookback that is greater than 5000 bars.   The lookback will then be recalculated to a value such that a runtime error does not occur.  • If the chart's timeframe is higher than the timeframe units. This error cannot occur when using Auto-steps to calculate timeframe units.  • If relative volume cannot be calculated, for example, when no volume data is available for the chart's symbol.  • When the threshold of relative volume is configured to be visible but the indicator's scale does not allow it to be visible (in "Current Volume Columns" display mode). █  NOTES For traders The chart shown here uses the following display modes: "Current Volume Columns", "Relative Volume Columns With Average", "Directional Relative Volume Average" and "Relative Volume Average". The last one also shows the threshold channel in standard deviation mode, and the TF Unit reminder to the right, in red. Volume, like price, is a value with a market-dependent scale. The only valid reference for volume being its past values, any improvement in the way past volume is calculated thus represents a potential opportunity to traders. Relative volume calculated as it is here can help traders extract useful information from markets in many circumstances, markets with cyclical volume such as Forex being one, obvious case. The relative nature of the values calculated by this indicator also make it a natural fit for cross-market and cross-sector analysis, or to identify behavioral changes in the different futures contracts of the same market. Relative volume can also be put to more exotic uses, such as in evaluating changes in the popularity of exchanges. Relative volume alone has no directional bias. While higher relative volume values always indicate higher trading activity, that activity does not necessarily translate into significant price movement. In a tightly fought battle between buyers and sellers, you could theoretically have very large volume for many bars, with no change whatsoever in bid/ask prices. This of course, is unlikely to happen in reality, and so traders are justified in considering high relative volume values as indicating periods where more attention is required, because imbalances in the strength of buying/selling power during high-volume trading periods can amplify price variations, providing traders with the generally useful gift of volatility. Be sure to give the "Directional Relative Volume Average" a try. Contrary to the always-positive ratio widely used in this indicator, the "Directional Relative Volume Average" produces a value able to determine a bullish/bearish bias for relative volume. Note that realtime bars must be complete for the relative volume value to be confirmed. Values calculated on historical or elapsed realtime bars will not recalculate unless historical volume data changes. Finally, as with all indicators using volume information, keep in mind that some exchanges/brokers supply different feeds for intraday and daily data, and the volume data on both feeds can sometimes vary quite a bit. For coders Our script was written using the PineCoders Coding Conventions for Pine . The description was formatted using the techniques explained in the How We Write and Format Script Descriptions PineCoders publication. Bits and pieces of code were lifted from the MTF Selection Framework and the MTF Oscillator Framework , also by PineCoders. █  THANKS Thanks to dgtrd for suggesting to add the channel using standard deviation. Thanks to adolgov for helpful suggestions on calculations and visuals. Look first. Then leap.
Pine Script® Indikator
von TradingView
52
Phoenix085-Studies-PerCentage Current Price ((fib-pivot-%))Misc Details : Another Indicator and Totally my own concept... If others have similar study already then Credit to them for coming up with this even before I did but this is just me fiddling with pinescript trying to paint my dream like a great man once said... Background : I am a strong believer of Market being Fractals and what best way to script it than Pivots. So I just wanted to identify the Pivot High and Pivot Low of some period(in the script it is set to 500, please do play with it to get the best setting which captures atleast the major highs and lows of recent past) I also think that Fibonacci levels are very crucial and so wanted to see how the market reacts at the Fibonacci ratios from Pivot High and Low. Overview : As said above the price at Pivot Low is considered as 0% on the graph and Value at Pivot High as the 100%. Depending on the CMP, the thick white line is plotted... The main thing of interest here is the Horizontal lines are Fib Levels and the market kinda reacts around those levels as the buyers and sellers have to come to equilibrium... A price retracing from the 100% level just means Double Top = Sell(Probable) and a bounce from the 0% just means a double bottom = Buy(Probable).... Also this indicator along with my other Public indicator() might give a better understanding of the price actions (I Hope)... This is free to use and share with as many as you like... Credits: All the great people who have greatly influenced and still continue to do so... @JustUncleL @BigBitsIO @TheArtofTrading @QuantNomad @SquigglesNiggles and many many many more
Pine Script® Indikator
von Phoenix085
2
Waindrops [Makit0]█  OVERALL Plot waindrops (custom volume profiles) on user defined periods, for each period you get high and low, it slices each period in half to get independent vwap, volume profile and the volume traded per price at each half. It works on intraday charts only, up to 720m (12H). It can plot balanced or unbalanced waindrops, and volume profiles up to 24H sessions. As example you can setup unbalanced periods to get independent volume profiles for the overnight and cash sessions on the futures market, or 24H periods to get the full session volume profile of EURUSD The purpose of this indicator is twofold: 1 — from a Chartist point of view, to have an indicator which displays the volume in a more readable way 2 — from a Pine Coder point of view, to have an example of use for two very powerful tools on Pine Script:    • the recently updated drawing limit to 500 (from 50)    • the recently ability to use drawings arrays (lines and labels) If you are new to Pine Script and you are learning how to code, I hope you read all the code and comments on this indicator, all is designed for you, the variables and functions names, the sometimes too big explanations, the overall structure of the code, all is intended as an example on how to code in Pine Script a specific indicator from a very good specification in form of white paper If you wanna learn Pine Script form scratch just start HERE In case you have any kind of problem with Pine Script please use some of the awesome resources at our disposal: USRMAN , REFMAN , AWESOMENESS , MAGIC █  FEATURES Waindrops are a different way of seeing the volume and price plotted in a chart, its a volume profile indicator where you can see the volume of each price level plotted as a vertical histogram for each half of a custom period. By default the period is 60 so it plots an independent volume profile each 30m You can think of each waindrop as an user defined candlestick or bar with four key values:  • high of the period  • low of the period  • left vwap (volume weighted average price of the first half period)  • right vwap (volume weighted average price of the second half period) The waindrop can have 3 different colors (configurable by the user):  • GREEN: when the right vwap is higher than the left vwap (bullish sentiment )  • RED: when the right vwap is lower than the left vwap (bearish sentiment )  • BLUE: when the right vwap is equal than the left vwap ( neutral sentiment ) KEY FEATURES  • Help menu  • Custom periods  • Central bars  • Left/Right VWAPs  • Custom central bars and vwaps: color and pixels  • Highly configurable volume histogram: execution window, ticks, pixels, color, update frequency and fine tuning the neutral meaning  • Volume labels with custom size and color  • Tracking price dot to be able to see the current price when you hide your default candlesticks or bars █  SETTINGS Click here or set any impar period to see the HELP INFO : show the HELP INFO, if it is activated the indicator will not plot PERIOD SIZE (max 2880 min) : waindrop size in minutes, default 60, max 2880 to allow the first half of a 48H period as a full session volume profile BARS : show the central and vwap bars, default true    Central bars : show the central bars, default true    VWAP bars : show the left and right vwap bars, default true    Bars pixels : width of the bars in pixels, default 2    Bars color mode : bars color behavior    • BARS : gets the color from the 'Bars color' option on the settings panel    • HISTOGRAM : gets the color from the Bearish/Bullish/Neutral Histogram color options from the settings panel    Bars color : color for the central and vwap bars, default white HISTOGRAM show the volume histogram, default true    Execution window (x24H) : last 24H periods where the volume funcionality will be plotted, default 5    Ticks per bar (max 50) : width in ticks of each histogram bar, default 2    Updates per period : number of times the histogram will update    • ONE : update at the last bar of the period    • TWO : update at the last bar of each half period    • FOUR : slice the period in 4 quarters and updates at the last bar of each of them    • EACH BAR : updates at the close of each bar    Pixels per bar : width in pixels of each histogram bar, default 4    Neutral Treshold (ticks) : delta in ticks between left and right vwaps to identify a waindrop as neutral, default 0    Bearish Histogram color : histogram color when right vwap is lower than left vwap, default red    Bullish Histogram color : histogram color when right vwap is higher than left vwap, default green    Neutral Histogram color : histogram color when the delta between right and left vwaps is equal or lower than the Neutral treshold, default blue VOLUME LABELS : show volume labels    Volume labels color : color for the volume labels, default white    Volume Labels size : text size for the volume labels, choose between AUTO, TINY, SMALL, NORMAL or LARGE, default TINY TRACK PRICE : show a yellow ball tracking the last price, default true █  LIMITS This indicator only works on intraday charts (minutes only) up to 12H (720m), the lower chart timeframe you can use is 1m This indicator needs price, time and volume to work, it will not work on an index (there is no volume), the execution will not be allowed The histogram (volume profile) can be plotted on 24H sessions as limit but you can plot several 24H sessions █  ERRORS AND PERFORMANCE Depending on the choosed settings, the script performance will be highly affected and it will experience errors Two of the more common errors it can throw are:  • Calculation takes too long to execute  • Loop takes too long The indicator performance is highly related to the underlying volatility (tick wise), the script takes each candlestick or bar and for each tick in it stores the price and volume, if the ticker in your chart has thousands and thousands of ticks per bar the indicator will throw an error for sure, it can not calculate in time such amount of ticks. What all of that means? Simply put, this will throw error on the BITCOIN pair BTCUSD (high volatility with tick size 0.01) because it has too many ticks per bar, but lucky you it will work just fine on the futures contract BTC1! (tick size 5) because it has a lot less ticks per bar There are some options you can fine tune to boost the script performance, the more demanding option in terms of resources consumption is Updates per period , by default is maxed out so lowering this setting will improve the performance in a high way. If you wanna know more about how to improve the script performance, read the HELP INFO accessible from the settings panel █  HOW-TO SETUP The basic parameters to adjust are Period size , Ticks per bar and Pixels per bar  • Period size is the main setting, defines the waindrop size, to get a better looking histogram set bigger period and smaller chart timeframe  • Ticks per bar is the tricky one, adjust it differently for each underlying (ticker) volatility wise, for some you will need a low value, for others a high one.    To get a more accurate histogram set it as lower as you can (min value is 1)  • Pixels per bar allows you to adjust the width of each histogram bar, with it you can adjust the blank space between them or allow overlaping You must play with these three parameters until you obtain the desired histogram: smoother, sharper, etc... These are some of the different kind of charts you can setup thru the settings:  • Balanced Waindrops (default): charts with waindrops where the two halfs are of same size.    This is the default chart, just select a period (30m, 60m, 120m, 240m, pick your poison), adjust the histogram ticks and pixels and watch  • Unbalanced Waindrops: chart with waindrops where the two halfs are of different sizes.    Do you trade futures and want to plot a waindrop with the first half for the overnight session and the second half for the cash session? you got it;    just adjust the period to 1860 for any CME ticker (like ES1! for example) adjust the histogram ticks and pixels and watch  • Full Session Volume Profile: chart with waindrops where only the first half plots.    Do you use Volume profile to analize the market? Lucky you, now you can trick this one to plot it, just try a period of 780 on SPY, 2760 on ES1!, or 2880 on EURUSD    remember to adjust the histogram ticks and pixels for each underlying  • Only Bars: charts with only central and vwap bars plotted, simply deactivate the histogram and volume labels  • Only Histogram: charts with only the histogram plotted (volume profile charts), simply deactivate the bars and volume labels  • Only Volume: charts with only the raw volume numbers plotted, simply deactivate the bars and histogram If you wanna know more about custom full session periods for different asset classes, read the HELP INFO accessible from the settings panel EXAMPLES Full Session Volume Profile on MES 5m chart: Full Session Unbalanced Waindrop on MNQ 2m chart (left side Overnight session, right side Cash Session): The following examples will have the exact same charts but on four different tickers representing a futures contract, a forex pair, an etf and a stock. We are doing this to be able to see the different parameters we need for plotting the same kind of chart on different assets The chart composition is as follows:  • Left side: Volume Labels chart (period 10)  • Upper Right side: Waindrops (period 60)  • Lower Right side: Full Session Volume Profile The first example will specify the main parameters, the rest of the charts will have only the differences MES :  • Left: Period size: 10, Bars: uncheck, Histogram: uncheck, Execution window: 1, Ticks per bar: 2, Updates per period: EACH BAR,    Pixels per bar: 4, Volume labels: check, Track price: check  • Upper Right: Period size: 60, Bars: check, Bars color mode: HISTOGRAM, Histogram: check, Execution window: 2, Ticks per bar: 2,    Updates per period: EACH BAR, Pixels per bar: 4, Volume labels: uncheck, Track price: check  • Lower Right: Period size: 2760, Bars: uncheck, Histogram: check, Execution window: 1, Ticks per bar: 1, Updates per period: EACH BAR,    Pixels per bar: 2, Volume labels: uncheck, Track price: check EURUSD :  • Upper Right: Ticks per bar: 10  • Lower Right: Period size: 2880, Ticks per bar: 1, Pixels per bar: 1 SPY :  • Left: Ticks per bar: 3  • Upper Right: Ticks per bar: 5, Pixels per bar: 3  • Lower Right: Period size: 780, Ticks per bar: 2, Pixels per bar: 2 AAPL :  • Left: Ticks per bar: 2  • Upper Right: Ticks per bar: 6, Pixels per bar: 3  • Lower Right: Period size: 780, Ticks per bar: 1, Pixels per bar: 2 █  THANKS TO PineCoders for all they do, all the tools and help they provide and their involvement in making a better community scarf for the idea of coding a waindrops like indicator, I did not know something like that existed at all All the Pine Coders, Pine Pros and Pine Wizards, people who share their work and knowledge for the sake of it and helping others, I'm very grateful indeed I'm learning at each step of the way from you all, thanks for this awesome community; Opensource and shared knowledge: this is the way! (said with canned voice from inside my helmet :D) █  NOTE This description was formatted following THIS guidelines ═════════════════════════════════════════════════════════════════════════ I sincerely hope you enjoy reading and using this work as much as I enjoyed developing it :D GOOD LUCK AND HAPPY TRADING!
Pine Script® Indikator
von makit0
108
Phoenix085-Strategies==>MTF - Average True Range + MovAvgFIRSTLY, Here are a few who have influenced my pinescripting immensely recently: @JustUncleL @BigBitsIO @TheArtofTrading @QuantNomad @SquigglesNiggles and many many many more. Overview: > This indicator is a simple crossover of Moving Averages. > In addition I am using ATR rising as an indication for Trending Price. > The entry is made once the smaller moving average crosses the bigger moving average, and also the Closes above the Smaller moving average. > but the only twist here is, - the ATR source is One timeframe Higher(In this case same as the session).whereas the source for the Moving averages is one Timeframe Lower. >i.e., if the Session is 1D, the Indicator checks if the ATR is rising in the DAILY TIMEFRAME, *_* the trade entry is made once the MOVING AVERAGE crossover happens on ONE TIME FRAME lower, as per example, ATR --> 1D = MA -->4H. > Moving Average -> - Thick -> Bigger MA, - Thin and Transparent -> Smaller MA, > Also, the Color of the Thicker MOVING AVERAGE Changes as Below: - When LongCondition is satisfied --> Color=Lime - When ShortCondition is satisfied --> Color=Red - When neither condition is satisfied --> Color=Gray NOTE: 1) There is a limitation in using the Securities function for FREE USERS --> Only 500 bars are allowed. So to use the indicators with more data, you need an upgraded TV account. 2) Strategy still needs Fine tuning, but for now, use the Thicker moving average color LIME FOR LONG ENTRIES and RED FOR SHORT ENTRIES. This is Free for Use and share
Pine Script® Strategie
von Phoenix085
2
Ichimoku Strategy with Buy and Sell ZonesIchimoku strategy with Buy and Sell Zones basicly using Ichimoku Cloud Tenkan-sen (Conversion Line): (9-period high + 9-period low)/2 On a daily chart, this line is the midpoint of the 9-day high-low range, which is almost two weeks. Kijun-sen (Base Line): (26-period high + 26-period low)/2 On a daily chart, this line is the midpoint of the 26-day high-low range, which is almost one month. Senkou Span A (Leading Span A): (Conversion Line + Base Line)/2 This is the midpoint between the Conversion Line and the Base Line. The Leading Span A forms one of the two Cloud boundaries. It is referred to as “Leading” because it is plotted 26 periods in the future and forms the faster Cloud boundary. Senkou Span B (Leading Span B): (52-period high + 52-period low)/2 On the daily chart, this line is the midpoint of the 52-day high-low range, which is a little less than 3 months. The default calculation setting is 52 periods, but it can be adjusted. This value is plotted 26 periods in the future and forms the slower Cloud boundary. Chikou Span: Represents the closing price and is plotted 26 days back. Kumo Cloud: Kumo cloud between Senkuo Span A and Senkou Span B lines. It can be green or red. Color can be change with the trend. And, it has 2 zones includes Buy and Sell Zone For Buy Zone Alert; - Tenkansen (Conversion Line) should crossover Kijunsen (Base line) above the highest line of cloud - Price should be above the highest line of cloud - Chikouspan should be above the cloud For Sell Zone Alert: - Kijunsen (Base Line) should crossover Tenkansen (Conversion Line) below the lowest line of cloud - Price should be below the lowest line of cloud - Chikouspan should be below the cloud The indicator has some of Simple Moving Averages and Exponentianl Moving Averages It includes: - SMA 50 - SMA 200 - EMA 21 - EMA 500 You have chance to show or hide everything from settings section. If you hide everything you can only see Buy and Sell zones.
Pine Script® Indikator
von ErdemDemir
8
Let it snow... [QuantNomad]It's almost the end of 2020. If you don't have any snow outside but still you want some Christmas mood - feel free to use my indicator. TradingView added a possibility to use up to 500 labels, so I decided to create something fun and completely useless. Snowflakes suppose to fall nicely, but labels are not regularly updated by TradingView. If you know how to make it better - let me know ) For the best experience use Dark Theme and play the "Let it snow" song ) Merry Christmas & Happy New Year!
Pine Script® Indikator
von QuantNomad
5