开始

在脚本中搜索"THE SCRIPT"

Relative Volume (rVol), Better Volume, Average Volume ComparisonThis is the best version of relative volume you can find a claim which is based on the logical soundness of its calculation. I have amalgamated various volume analysis into one synergistic script. I wasn't going to opensource it. But, as one of the lucky few winners of TradingClue 2. I felt obligated to give something back to the community. Relative volume traditionally compares current volume to prior bar volume or SMA of volume. This has drawbacks. The question of relative volume is "Volume relative to what?" In the traditional scripts you'll find it displays current volume relative to the last number of bars. But, is that the best way to compare volume. On a daily chart, possibly. On a daily chart this can work because your units of time are uniform. Each day represents a full cycle of volume. However, on an intraday chart? Not so much. Example: If you have a lookback of 9 on an hourly chart in a 24 hour market, you are then comparing the average volume from Midnight - 9 AM to the 9 AM volume. What do you think you'll find? Well at 9:30 when NY exchanges open the volume should be consistently and predictably higher. But though rVol is high relative to the lookback period, its actually just average or maybe even below average compared to prior NY session opens. But prior NY session opens are not included in the lookback and thus ignored. This problem is the most visibly noticed when looking at the volume on a CME futures chart or some equivalent. In a 24 hour market, such as crypto, there are website's like skew can show you the volume disparity from time of day. This led me to believe that the traditional rVol calculation was insufficient. A better way to calculate it would be to compare the 9:30 am 30m bar today to the last week's worth of 9:30 am 30m bars. Then I could know whether today's volume at 9:30 am today is high or low based on prior 9:30 am bars. This seems to be a superior method on an intraday basis and is clearly superior in markets with irregular volume This led me to other problems, such as markets that are open for less than 24 hours and holiday hours on traditional market exchanges. How can I know that the script is accurately looking at the correct prior relevant bars. I've created and/or adapted solutions to all those problems and these calculations and code snippets thus have value that extend beyond this rVol script for other pinecoders. The Script This rVol script looks back at the bars of the same time period on the viewing timeframe. So, as we said, the last 9:30 bars. Averages those, then divides the: . The result is a percentage expressed as x.xxx. Thus 1.0 mean current volume is equal to average volume. Below 1.0 is below the average and above 1.0 is above the average. This information can be viewed on its own. But there are more levels of analysis added to it. Above the bars are signals that correlate to the "Better Volume Indicator" developed by, I believe, the folks at emini-watch and originally adapted to pinescript by LazyBear. The interpretation of these symbols are in a table on the right of the indicator. The volume bars can also be colored. The color is defined by the relationship between the average of the rVol outputs and the current volume. The "Average rVol" so to speak. The color coding is also defined by a legend in the table on the right. These can be researched by you to determine how to best interpret these signals. I originally got these ideas and solid details on how to use the analysis from a fellow out there, PlanTheTrade. I hope you find some value in the code and in the information that the indicator presents. And I'd like to thank the TradingView team for producing the most innovative and user friendly charting package on the market. (p.s. Better Volume is provides better information with a longer lookback value than the default imo) Credit for certain code sections and ideas is due to: LazyBear - Better Volume Grimmolf (From GitHub) - Logic for Loop rVol R4Rocket - The idea for my rVol 1 calculation And I can't find the guy who had the idea for the multiples of volume to the average. Tag him if you know him Final Note: I'd like to leave a couple of clues of my own for fellow seekers of trading infamy. Indicators: indicators are like anemometers (The things that measure windspeed). People talk bad about them all the time because they're "lagging." Well, you can't tell what the windspeed is unless the wind is blowing. anemometers are lagging indicators of wind. But forecasters still rely on them. You would use an indicator, which I would define as a instrument of measure, to tell you the windspeed of the markets. Conversely, when people talk positively about indicators they say "This one is great and this one is terrible." This is like a farmer saying "Shovels are great, but rakes are horrible." There are certain tools that have certain functions and every good tool has a purpose for a specific job. So the next time someone shares their opinion with you about indicators. Just smile and nod, realizing one day they'll learn... hopefully before they go broke. How to forecast: Prediction is accomplished by analyzing the behavior of instruments of measure to aggregate data (using your anemometer). The data is then assembled into a predictive model based on the measurements observed (a trading system). That predictive model is tested against reality for it's veracity (backtesting). If the model is predictive, you can optimize your decision making by creating parameter sets around the prediction that are synergistic with the implications of the prediction (risk, stop loss, target, scaling, pyramiding etc). <3
Pine Script®指标
由kurtsmock提供
74
Tic Tac Toe (For Fun)Hello All, I think all of you know the game "Tic Tac Toe" :) This time I tried to make this game, and also I tried to share an example to develop a game script in Pine. Just for fun ;) Tic Tac Toe Game Rules: 1. The game is played on a grid that's 3 squares by 3 squares. 2. You are "O", the computer is X. Players take turns putting their marks in empty squares. 3. if a player makes 3 of her marks in a row (up, down, across, or diagonally) the he is the winner. 4. When all 9 squares are full, the game is over (draw) So, how to play the game? - The player/you can play "O", meaning your mark is "O", so Xs for the script. please note that: The script plays with ONLY X - There is naming for all squears, A1, A2, A3, B1, B2, B3, C1, C2, C3. you will see all these squares in the options. - also You can set who will play first => "Human" or "Computer" if it's your turn to move then you will see "You Move" text, as seen in the following screenshot. for example you want to put "O" to "A1" then using options set A1 as O How the script play? it uses MinMax algorithm with constant depth = 4. And yes we don't have option to make recursive functions in Pine at the moment so I made four functions for each depth. this idea can be used in your scripts if you need such an algorithm. if you have no idea about MinMax algorithm you can find a lot of articles on the net :) The script plays its move automatically if its turn to play. you will just need to set the option that computer played (A1, C3, etc) if it's computer turn to play then it calculates and show the move it wants to play like "My Move : B3 <= X" then using options you need to set B3 as X Also it checks if the board is valid or not: I have tested it but if you see any bug let me know please Enjoy!
Pine Script®指标
由LonesomeTheBlue提供
29
VWAP forex Yesterday Hi/Low update fix This script is an updte fix of an earlier script that stopped functioning when TradingView updated Pine script. This script plots Forex (24 hour session) VWAP, yesterday's high, low, open and close (HLOC), the day before's HLOC - Also plots higher timeframe 20 emas 1 minute 5, 15, 60 period 20 ema 5 minute 15, 60 period 20 ema 15 minute 60, 120 , 240 period 20 ema 60 minute 120, 240 period 20 ema 120 minute 240, D period 20 ema 240 minute D period 20 ema Also signals inside bars (high is less than or equal to the previous bar's high and the low is greater than or equal to the previous low) the : true inside bars have a maroon triangle below the bar as well as a ">" above the bar. If subsequest bars are inside the last bar before the last true inside bar they also are marked with an ">" This is probably a slight variation from the way Leaf_West plots the inside bars. It appears that he marks all bars that are inside the original bar until one a bar has a high or low outside the original bar. But I would need to see an example on his charts. The Time Session Glitch and the Fix FX_IDC, COINBASE and BITSTAMP: The script will correctly default to 1700 hrs to 1700hrs EDT/EST session for FXCM. Strangely some securities appear to erroneously start their session at 1200 hrs ie. My guess is that they are somehow tied to GMT+0 instead of New York time (GMT+5). See this for yourself by selecting EURUSD using the FXCM exchange (FX:EURUSD) and then EURUSD from the IDC exchange (FX_IDC:EURUSD). The FX-IDC session opening range starts 5 hours before it actually should at 1700 hrs EDT/EST. To correct for this I have implemented an automatic fix (default) and a user selected "5 hour time shift adjust. ment needed on some securities". There is also a 4 hour time shift button which might be necessary when New York reverts from Eastern Standard Time to Eastern Daylight Time (1 hour difference) in March (and then back again in November). In the default auto adjust mode you will need to select the 1 hour time shift. That is if this glitch still exists at that time. I have looked at other scripts, other than my own and where the script is available, that need to use information about the opening bar and all have the same time shift issue COINBASE and BITSTAMP open at 0000 hours GMT. Since I use lines instead of circles or crosses I had to make a small adjustment to plot the lines correctly. If it needs work let me know. Jayy
Pine Script®指标
由jayy提供
6
alpha Renko intraday wave timeI was asked to share my experimental Renko intraday wave time. So here it is warts and all. The same for the rest - except the Weis cumulative volume. Renko wave time is in minutes. This script is strictly intraday and has not been played with extensively. You must use traditional Renko and set the script wave size to the same size as the Renko brick size. If you click on the sideways wishbone or "V" in the middle upper part of the chart you will get all of the scripts in this particular sandbox. After clicking the sideways wish bone click on "make it mine". You will then have the whole sandbox. The only published script is the Weis cumulative wave. The "Boys MAs" is supposed to be a script for daily charts and from within some kind of consolidation. In any case I am intrigued by some signals. You have a variety of sandbox options in the format section of the boys MAs. These codes are pretty rough with lots of abandoned lines of script.
Pine Script®指标
由jayy提供
11
Long/Short Ratio Aggregated (Lite)Description — Long/Short Ratio Aggregated (Lite) This indicator provides a cross-exchange, open-interest-weighted aggregation of the Long/Short Ratio (LSR) for the cryptocurrency asset currently on your chart. It is designed to unify fragmented derivatives positioning data from multiple major exchanges into a single normalized signal that more accurately reflects real market sentiment and positioning bias across platforms. Concept and Originality Traditional Long/Short Ratio indicators are exchange-specific. They show how many traders are long versus short, but only within the scope of one venue (e.g., Binance or Bybit). This makes them incomplete and often misleading for directional bias analysis, since different exchanges host different participant profiles, levels of leverage, and quote-currency exposures. This script addresses that limitation by: Aggregating LSR data across multiple exchanges (Binance and Bybit). Weighting each ratio by Open Interest (OI) — ensuring exchanges with higher open positions contribute proportionally more to the overall sentiment. Normalizing all contract types (USDT, USDC, and USD-margined) into a consistent base-currency format. This step corrects for structural differences between coin- and stablecoin-margined instruments, producing a true like-for-like comparison. The result is a globalized Long/Short Ratio, normalized by exposure and liquidity, suitable for multi-venue orderflow estimation and directional bias assessment. Note for moderators: I know there are already other scripts out there, but they may not support Open Interest Weighting or the same number of pairs. They also might not support proper normalization like in my script. Calculation Methodology For each supported exchange and contract type: The script retrieves the latest Long/Short Ratio (LSR) and Open Interest (OI) values. OI is used as the weighting factor, creating a proportional representation of positioning volume. Values denominated in USD are normalized into base currency using close-price adjustment. The final value is computed as: Weighted LSR = (Σ (LSRᵢ × OIᵢ)) / (Σ OIᵢ) This ensures that if, for example, Binance has twice the open interest of Bybit, its LSR contributes twice as much to the total weighted sentiment. Interpretation Value > 1.0 → Market participants are net-long (bullish bias). Value < 1.0 → Market participants are net-short (bearish bias). Strength of deviation from 1.0 indicates positioning imbalance magnitude. Because the ratio is OI-weighted, large players or heavily margined exchanges influence the output proportionally more than smaller, low-volume venues — making this metric a better reflection of true market positioning rather than isolated retail sentiment. Usage and Applications Use this indicator as a component in: Orderflow and sentiment confirmation, alongside price action and volume. Funding rate correlation studies. Intraday reversals or exhaustion zones, when combined with volatility or OI delta metrics. Overlaying or combining this indicator with open interest change, cumulative volume delta, or funding rate divergence allows traders to build a high-resolution understanding of positioning shifts and crowd behavior. Notes The “Lite” version is optimized for execution and accessibility, focusing on accuracy while staying within Pine Script’s computational limits. Exchange data availability may vary by symbol; unsupported pairs automatically return na and are automatically not included in the weighted calculation. In summary: This indicator transforms fragmented, exchange-specific Long/Short Ratio into a unified, OI-weighted global sentiment measure — a foundational tool for traders seeking to quantify derivative-side orderflow bias with cross-venue accuracy.
Pine Script®指标
由mxdvt07提供
Lunar calendar day Crypto Trading StrategyLunar calendar day Crypto Trading Strategy This strategy explores the potential impact of the lunar calendar on cryptocurrency price cycles. It implements a simple but unconventional rule: Buy on the 5th day of each lunar month Sell on the 26th day of the lunar month No trades between January 1 (solar) and Lunar New Year’s Day (holiday buffer period) Research background Several academic studies have investigated the influence of lunar cycles on financial markets. Their findings suggest: Returns tend to be higher around the full moon compared to the new moon. Periods between the full moon and the waning phase often show stronger average returns than the waxing phase. This strategy combines those observations into a practical implementation by testing fixed entry (lunar day 5) and exit (lunar day 26) points, while excluding the transition period from solar New Year to Lunar New Year, effectively capturing mid-month lunar effects. How it works The script includes a custom lunar date calculation function, reconstructing lunar months and days for each year (2020–2026). On lunar day 5, the strategy opens a long position with 100% of equity. On lunar day 26, the strategy closes the position. No trades are executed between Jan 1 and Lunar New Year’s Day. All trades include: Commission: 0.1% Slippage: 3 ticks Position sizing uses the entire equity (100%) for simplicity, but this is not recommended for live trading. Why this is original Unlike mashups of built-in indicators, this script: Implements a full lunar calendar system inside Pine Script. Translates academic findings on lunar effects into an applied backtest. Adds a realistic trading filter (holiday gap) based on cultural/seasonal calendar rules. Provides researchers and traders with a framework to explore non-traditional, time-based signals. Notes This is an experimental, research-oriented strategy, not financial advice. Results are highly dependent on the chosen period (2020–2026). Using 100% equity per trade is for simplification only and is not a viable money management practice. The purpose is to investigate whether cyclical patterns linked to lunar time can provide any statistical edge in ETHUSDT.
Pine Script®策略
由lsh9500提供
IU Trailing Stop Loss MethodsThe 'IU Trailing Stop Loss Methods' it's a risk management tool which allows users to apply 12 trailing stop-loss (SL) methods for risk management of their trades and gives live alerts when the trailing Stop loss has hit. Below is a detailed explanation of each input and the working of the Script. Main Inputs: - bar_time: Specifies the date from which the trade begins and entry price will be the open of the first candle. - entry_type: Choose between 'Long' or 'Short' positions. - trailing_method: Select the trailing stop-loss method. Options include ATR, Parabolic SAR, Supertrend, Point/Pip based, Percentage, EMA, Highest/Lowest, Standard Deviation, and multiple target-based methods. - exit_after_close: If checked, exits the trade only after the candle closes. Optional Inputs: ATR Settings: - atr_Length: Length for the ATR calculation. - atr_factor: ATR multiplier for SL calculation. Parabolic SAR Settings: - start, increment, maximum: Parameters for the Parabolic SAR indicator. Supertrend Settings: - supertrend_Length, supertrend_factor: Length and factor for the Supertrend indicator. Point/Pip Based: - point_base: Set trailing SL in points/pips. Percentage Based: - percentage_base: Set SL as a percentage of entry price. EMA Settings: - ema_Length: Length for EMA calculation. Standard Deviation Settings: - std_Length, std_factor: Length and factor for standard deviation calculation. Highest/Lowest Settings: - highest_lowest_Length: Length for the highest/lowest SL calculation. Target-Based Inputs: - ATR, Point, Percentage, and Standard Deviation based target SL settings with customizable lengths and multipliers. Entry Logic: - Trades initiate based on the entry_type selected and the specified bar_time. - If Long is selected, a long trade is initiated when the conditions match, and vice versa for Short. Trailing Stop-Loss (SL) Methods Explained: The strategy dynamically adjusts stop-loss based on the chosen method. Each method has its calculation logic: - ATR: Stop-loss calculated using ATR multiplied by a user-defined factor. - Parabolic SAR: Uses the Parabolic SAR indicator for trailing stop-loss. - Supertrend: Utilizes the Supertrend indicator as the stop-loss line. - Point/Pip Based: Fixed point-based stop-loss. - Percentage Based: SL set as a percentage of entry price. - EMA: SL based on the Exponential Moving Average. - Highest/Lowest: Uses the highest high or lowest low over a specified period. - Standard Deviation: SL calculated using standard deviation. Exit Conditions: - If exit_after_close is enabled, the position will only close after the candle confirms the stop-loss hit. - If exit_after_close is disabled, the strategy will close the trade immediately when the SL is breached. Visualization: The script plots the chosen trailing stop-loss method on the chart for easy visualization. Target-Based Trailing SL Logic: - When a position is opened, the strategy calculates the initial stop-loss and progressively adjusts it as the price moves favorably. - Each SL adjustment is stored in an array for accurate tracking and visualization. Alerts and Labels: - When the Entry or trailing stop loss is hit this scripts draws a label and give alert to the user that trailing stop has been hit for the trade. Note - on the historical data The Script will show nothing if the entry and the exit has happened on the same candle, because we don't know what was hit first SL or TP (basically how the candle was formed on the lower timeframe). Summary: This script offers flexible trailing stop-loss options for traders who want dynamic risk management in their strategies. By offering multiple methods like ATR, SAR, Supertrend, and EMA, it caters to various trading styles and risk preferences.
Pine Script®指标
由Shivam_Mandrai提供
8
chrono_utilsLibrary "chrono_utils" 📝 Description Collection of objects and common functions that are related to datetime windows session days and time ranges. The main purpose of this library is to handle time-related functionality and make it easy to reason about a future bar checking if it will be part of a predefined session and/or inside a datetime window. All existing session functionality I found in the documentation e.g. "not na(time(timeframe, session, timezone))" are not suitable for strategy scripts, since the execution of the orders is delayed by one bar, due to the script execution happening at the bar close. Moreover, a history operator with a negative value that looks forward is not allowed in any pinescript expression. So, a prediction for the next bar using the bars_back argument of "time()"" and "time_close()" was necessary. Thus, I created this library to overcome this small but very important limitation. In the meantime, I added useful functionality to handle session-based behavior. An interesting utility that emerged from this development is data anomaly detection where a comparison between the prediction and the actual value is happening. If those two values are different then a data inconsistency happens between the prediction bar and the actual bar (probably due to a holiday, half session day, a timezone change etc..) 🤔 How to Guide To use the functionality this library provides in your script you have to import it first! Copy the import statement of the latest release by pressing the copy button below and then paste it into your script. Give a short name to this library so you can refer to it later on. The import statement should look like this: import jason5480/chrono_utils/2 as chr To check if a future bar will be inside a window first of all you have to initialize a DateTimeWindow object. A code example is the following: var dateTimeWindow = chr.DateTimeWindow.new().init(fromDateTime = timestamp('01 Jan 2023 00:00'), toDateTime = timestamp('01 Jan 2024 00:00')) Then you have to "ask" the dateTimeWindow if the future bar defined by an offset (default is 1 that corresponds th the next bar), will be inside that window: // Filter bars outside of the datetime window bool dateFilterApproval = dateTimeWindow.is_bar_included() You can visualize the result by drawing the background of the bars that are outside the given window: bgcolor(color = dateFilterApproval ? na : color.new(color.fuchsia, 90), offset = 1, title = 'Datetime Window Filter') In the same way, you can "ask" the Session if the future bar defined by an offset it will be inside that session. First of all, you should initialize a Session object. A code example is the following: var sess = chr.Session.new().from_sess_string(sess = '0800-1700:23456', refTimezone = 'UTC') Then check if the given bar defined by the offset (default is 1 that corresponds th the next bar), will be inside the session like that: // Filter bars outside the sessions bool sessionFilterApproval = view.sess.is_bar_included() You can visualize the result by drawing the background of the bars that are outside the given session: bgcolor(color = sessionFilterApproval ? na : color.new(color.red, 90), offset = 1, title = 'Session Filter') In case you want to visualize multiple session ranges you can create a SessionView object like that: var view = SessionView.new().init(SessionDays.new().from_sess_string('2345'), array.from(SessionTimeRange.new().from_sess_string('0800-1600'), SessionTimeRange.new().from_sess_string('1300-2200')), array.from('London', 'New York'), array.from(color.blue, color.orange)) and then call the draw method of the SessionView object like that: view.draw() 🏋️‍♂️ Please refer to the "EXAMPLE DATETIME WINDOW FILTER" and "EXAMPLE SESSION FILTER" regions of the script for more advanced code examples of how to utilize the full potential of this library, including user input settings and advanced visualization! ⚠️ Caveats As I mentioned in the description there are some cases that the prediction of the next bar is not accurate. A wrong prediction will affect the outcome of the filtering. The main reasons this could happen are the following: Public holidays when the market is closed Half trading days usually before public holidays Change in the daylight saving time (DST) A data anomaly of the chart, where there are missing and/or inconsistent data. A bug in this library (Please report by PM sending the symbol, timeframe, and settings) Special thanks to @robbatt and @skinra for the constructive feedback 🏆. Without them, the exposed API of this library would be very lengthy and complicated to use. Thanks to them, now the user of this library will be able to get the most, with only a few lines of code!
Pine Script®库
由jason5480提供
6
Swing Assassin's Consolidated ScriptI put this script together to essentially consolidate a number of scripts that I use on a daily basis into one script. This is an ongoing improvement effort, so there may be some garbage in here right now so keep that in mind if you intend to use this to help in your trading. There are 5 moving averages (Hull). I use the Fast, Mid and Slow to find entries after I us the Medium Slow and Super Slow to identify a trend. Otherwise, I have those three turned off. This script also uses Bollinger Bands which I literally cannot trade without. The script also has anchored VWAP , automated support/resistance lines, and a homebrewed Volume Profile that is a copy from Ildar Akhmetgaleev's indicator "Poor Man's Volume Profile" used under Mozilla Public License Version 2.0.
Pine Script®指标
由UnknownUnicorn16914442提供
3
PriceCatch Opensource CPRHi Friends & TradingView community. Greetings to you. Some traders like to use Central Pivot Range (CPR) in their chart for assessing price movement. It is usually used in combination with Pivot Levels. Calculating CPR is a simple matter. There a few CPR scripts in the Public Library, but have the code hidden. I thought there may many users who may want to know how CPR is calculated and study it for use in their own scripts. So, here is the CPR script with the code. Use it as you please. Note: CPR is plotted only on intra-day time-frames. The light magenta (band) range is current day CPR. The light blue (band) range is tomorrow's CPR projected for you today itself based on current day's price action and range. Queries / feedback welcome. All the best. PS: The script is developed to the best of my ability and as with all indicators, you have to decide if it might be useful to you when adding to your chart.
Pine Script®指标
由PriceCatch提供
Pinescript - Standard Array Functions Library by RRBStandard Array Functions Library by RagingRocketBull 2021 Version 1.0 This script provides a library of every standard Pinescript array function for live testing with all supported array types. You can find the full list of supported standard array functions below. There are several libraries: - Common String Functions Library - Common Array Functions Library - Standard Array Functions Library Features: - Supports all standard array functions (30+) with all possible array types* (* - except array.new* functions and label, line array types) - 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: show errors, hide all excluded and show only allowed functions using a list of function names - Console customization options: set custom text size, color, page length, line spacing Notes: - uses Pinescript v3 Compatibility Framework - uses Common String Functions Library - has to be a separate script to reduce the number of local scopes in Common Array Function Library, there's no way to merge these scripts into a single library. - lets you live test all standard array functions for errors. If you see an error - change params in UI - array types that are not supported by certain functions and producing a compilation error were disabled with "error" showing up as result - if you see "Loop too long" error - hide/unhide or reattach the script - doesn't use pagination, a single str contains all output - for most array functions to work (except push), an array must be defined with at least 1 pre-existing dummy element 0. - array.slice and array.fill require from_index < to_index otherwise error - array.join only supports string arrays, and delimiter must be a const string, can't be var/input. Use join_any_array to join any array type into string. You can also use tostring() to join int, float arrays. - array.sort only supports int, float arrays. Use sort_any_array from the Common Array Function Library to sort any array type. - array.sort only sorts values, doesn't preserve indexes. Use sort_any_array from the Common Array Function Library to sort any array while preserving indexes. - array.concat appends string arrays in reverse order, other array types are appended correctly - array.covariance requires 2 int, float arrays of the same size - tostring(flag) works only for internal bool vars, flag expression can't depend on any inputs of any type, use bool_to_str instead - 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 - source_array and create_any_array2 use this loophole to return an int_arr pointer of a var type array - this works for all array types defined with/without var keyword. This doesn't work for string arrays defined with var keyword for some reason - you can't do this with var type vars, this can be done only with var type arrays because they are pointers passed by reference, while vars are the actual values passed by value. - wrapper functions solve the problem of returning var array types. This is the only way of doing it when the top level arr type is undefined. - 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 result type - get_var_types solves this problem by generating a list of dummy values of every possible type including the source type, allowing a single valid branch to execute without error - examples of functions supporting all array types: array.size, array.get, array.push. Examples of functions with limited type support: array.sort, array.join, array.max, tostring - unlike var params/global vars, you can modify array params and global arrays directly from inside functions using standard array functions, but you can't use := (it only works for local arrays) - inside function always work with array.copy to prevent accidental array modification - you can't compare arrays - there's no na equivalent for arrays, na(arr) doesn't work P.S. A wide array of skills calls for an even wider array of responsibilities List of functions: - array.avg(arr) - array.clear(arr) - array.concat(arr1, arr2) - array.copy(arr) - array.covariance(arr1, arr2) - array.fill(arr, value, index_from, index_to) - array.get(arr, index) - array.includes(arr, value) - array.indexof(arr, value) - array.insert(arr, index, value) - array.join(arr, delimiter) - array.lastindexof(arr, value) - array.max(arr) - array.median(arr) - array.min(arr) - array.mode(arr) - array.pop(arr) - array.push(arr, value) - array.range(arr) - array.remove(arr, index) - array.reverse(arr) - array.set(arr, index, value) - array.shift(arr) - array.size(arr) - array.slice(arr, index_from, index_to) - array.sort(arr, order) - array.standardize() - array.stdev(arr) - array.sum(arr) - array.unshift(arr, value) - array.variance(arr)
Pine Script®指标
由RagingRocketBull提供
2
CSPDMost Advanced & Accurate CandleStick Pattern Detector Looking All Over of All Markets for All Important Powerful Reversal | Corrective Patterns (25 type) Filtering the Results with Optional Features like Oscillator, Bollinger Bands, Volume Confirmation, Prior and Following Candles Confirmation which are Fully Customizable. With this you can detect: Hammer | Shooting star Inverted Hammer | Hanging Long legged Doji | Dragonfly Doji | Gravestone Doji Bullish tweezers | Bearish tweezers Bullish inside bar | Bearish inside bar Bullish three line strike | Bearish three line strike Bullish engulfing | Bearish engulfing Piercing line | Dark cloud cover Bullish abandoned baby | Bearish abandoned baby Morning star | Evening star Three white soldiers | Three black crows *Bullish kayo | *Bearish kayo Features: Prior and Following candles Confirmation    You can set prior and following candle as basic prerequisites for marking candles as pattern to make sure you are at the top or bottom of the trend. Volume confirmation    You can active volume increasing confirmation for some of pattern with adjustable increase % relative to prior candle | candles. Oscillator Confirmation    Active oscillator confirmation. Select your approved oscillator from list (Stochastic, RSI, StochRSI, MFI, StochMFI) then enter desired value for marking candles as bullish | bearish pattern. Bollinger Bands Confirmation    Active BB confirmation. Configure your Bollinger Bands. Now only see the patterns which reached or crossed from Bands. Also you can enable BB clod to have your BB indicator at the same time. Adjustable Flexibility and Precision    You can set tolerance% for Osc and BB Confirmation - each one separately - for more control. Self-adaptability    The properties of markets change over time, for example the amplitude of fluctuations and the intensity of movements. The script is designed in such a way that you can examine the price history as a benchmark for changes in market properties to adopt determinants. Also you can control those manually. Self-regulatory    The user has the ability to change input factors depending on their point of view. Behind the pattern recognition algorithms, there are relationships and similarities in their appearance that cause them to be influenced by each other. Simultaneously with changing the determining factors of each pattern by you, script automatically adjusts other details in accordance with your changes. Alerts    You can set for type of pattern or each one of pattern have been detected. Fully Costumizable    All of these options can be change and adjust. Note 1.    The patterns are based on extensive study of reference and famous sources and the experience of me and my friends in trading and analysis with price action methods. Note 2.    Due to the Pine limitations in the number of outputs | plots for each script, our attempt has been made to select the best and most important patterns. Note 3.    So far, many scripts have been written in this field, but our experience with all of them and even the build in version was not satisfactory, and this was the initial motivation for making the script. We strive to improve progress and elimination of shortcomings and we will continue to make this better. Note 4.    Through personal experience and based on the principles of market and candlestick psychology, we discovered a new type of pattern and named it as Kayo. kayo is a two candle pattern which formed when:     1.We have a pivot point with prior candles as left bars and following candles as right bar. Pivot candle called as second candle.     2.In a bullish kayo, first candle must closed descending and second candle must closed as ascending. For bearish kayo vise versa.     3.In a bullish kayo, second candle's lower wick must be longer then upper wick.     4. A pattern marked as kayo when its conditions do not correspond to any of the other patterns(include the confirmation that user added), ie it has the last naming priority over the other patterns. Note 5.    When you active confirmation options for patterns like hammer, engulf and etc which they conditions are like kayo in some extent, if they can't pass the confirmation steps, they can be marked as kayo pattern. Note 6.    If you active volume confirmation for Three white soldiers | Three black crows, the confirmation get passed if the volume of forth or third candle increased as value as entered relative to volume EMA3 of 3 candles. Note 7.    In a bullish pattern all highs of following candles MUST be higher than prior highs and all lows of following candles MUST be higher than prior lows. For bearish patterns vise versa. This type of confirmation depends on High and Low NOT close! Gift to price action lovers! Support us with your like and comments. let us know your experience, points and idea to make this better together.
Pine Script®指标
由Algorca提供
38
MIDAS VWAP Jayy his is just a bash together of two MIDAS VWAP scripts particularly AkifTokuz and drshoe. I added the ability to show more MIDAS curves from the same script. The algorithm primarily uses the "n" number but the date can be used for the 8th VWAP I have not converted the script to version 3. To find bar number go into "Chart Properties" select " "background" then select Indicator Titles and "Indicator values". When you place your cursor over a bar the first number you see adjacent to the script title is the bar number. Put that in the dialogue box midline is MIDAS VWAP . The resistance is a MIDAS VWAP using bar highs. The resistance is MIDAS VWAP using bar lows. In most case using N will suffice. However, if you are flipping around charts inputting a specific date can be handy. In this way, you can compare the same point in time across multiple instruments eg first trading day of the year or an election date. Adding dates into the dialogue box is a bit cumbersome so in this version, it is enabled for only one curve. I have called it VWAP and it follows the typical VWAP algorithm. (Does that make a difference? Read below re my opinion on the Difference between MIDAS VWAP and VWAP ). I have added the ability to start from the bottom or top of the initiating bar. In theory in a probable uptrend pick a low of a bar for a low pivot and start the MIDAS VWAP there using the support. For a downtrend use the high pivot bar and select resistance. The way to see is to play with these values. Difference between MIDAS VWAP and the regular VWAP MIDAS itself as described by Levine uses a time anchored On-Balance Volume (OBV) plotted on a graph where the horizontal (abscissa) arm of the graph is cumulative volume not time. He called his VWAP curves Support/Resistance VWAP or S/R curves. These S/R curves are often referred to as "MIDAS curves". These are the main components of the MIDAS chart. A third algorithm called the Top-Bottom Finder was also described. (Separate script). Additional tools have been described in "MIDAS_Technical_Analysis" Midas Technical Analysis: A VWAP Approach to Trading and Investing in Today’s Markets by Andrew Coles, David G. Hawkins Copyright © 2011 by Andrew Coles and David G. Hawkins. Denoting the different way in which Levine approached the calculation. The difference between "MIDAS" VWAP and VWAP is, in my opinion, much ado about nothing. The algorithms generate identical curves albeit the MIDAS algorithm launches the curve one bar later than the VWAP algorithm which can be a pain in the neck. All of the algorithms that I looked at on Tradingview step back one bar in time to initiate the MIDAS curve. As such the plotted curves are identical to traditional VWAP assuming the initiation is from the candle/bar midpoint. How did Levine intend the curves to be drawn? On a reversal, he suggested the initiation of the Support and Resistance VVWAP (S/R curve) to be started after a reversal. It is clear in his examples this happens occasionally but in many cases he initiates the so-called MIDAS S/R VWAP right at the reversal point. In any case, the algorithm is problematic if you wish to start a curve on the first bar of an IPO . You will get nothing. That is a pain. Also in Levine's writings, he describes simply clicking on the point where a S/R VWAP is to be drawn from. As such, the generally accepted method of initiating the curve at N-1 is a practical and sensible method. The only issue is that you cannot draw the curve from the first bar on any security, as mentioned without resorting to the typical VWAP algorithm. There is another difference. VWAP is launched from the middle of the bar (as per AlphaTrends), You can also launch from the top of the bar or the bottom (or anywhere for that matter). The calculation proceeds using the top or bottom for each new bar. The potential applications are discussed in the MIDAS Technical Analysis book.
Pine Script®指标
由jayy提供
21
ULTIMATE ORDER FLOW SYSTEM🔥 ULTIMATE ORDER FLOW SYSTEM Overview This comprehensive order flow analysis tool combines **Volume Profile**, **Cumulative Delta**, and **Large Order Detection** to identify high-probability trading setups. The script analyzes institutional order flow patterns and volume distribution to pinpoint key levels where price is likely to react. 📊 Core Components & Methodology 🔥 ULTIMATE ORDER FLOW SYSTEM Overview This comprehensive order flow analysis tool combines Volume Profile, Cumulative Delta, and Large Order Detection to identify high-probability trading setups. The script analyzes institutional order flow patterns and volume distribution to pinpoint key levels where price is likely to react. ________________________________________ 📊 Core Components & Methodology 1. Volume Profile Analysis The script constructs a horizontal volume profile by: • Dividing the price range into configurable rows (default: 20) • Accumulating volume at each price level over a lookback period (default: 50 bars) • Separating buy volume (green bars close > open) from sell volume (red bars) • Identifying three critical levels: o POC (Point of Control): Price level with highest traded volume - acts as a strong magnet o VAH/VAL (Value Area High/Low): Contains 70% of total volume - defines fair value zone o HVN (High Volume Nodes): Resistance zones where institutions accumulated positions o LVN (Low Volume Nodes): Thin zones that price moves through quickly - ideal targets Why This Matters: Institutional traders leave footprints through volume. HVN zones show where large players defended levels, making them reliable support/resistance. ________________________________________ 2. Cumulative Delta (Order Flow) Tracks the running total of buying vs selling pressure: • Bar Delta: Difference between buy and sell volume per candle • Cumulative Delta: Sum of all bar deltas - shows net directional pressure • Delta Moving Average: Smoothed delta (20-period) to identify trend • Delta Divergences: o Bullish: Price makes lower low, but delta makes higher low (absorption at bottom) o Bearish: Price makes higher high, but delta makes lower high (exhaustion at top) How It Works: When cumulative delta trends up while price consolidates, it signals accumulation. Delta divergences reveal when smart money is positioned opposite to retail expectations. ________________________________________ 3. Large Order Detection Identifies institutional-sized orders in real-time: • Compares current bar volume to 20-period moving average • Flags orders exceeding 2.5x average volume (configurable multiplier) • Distinguishes bullish (green circles below) vs bearish (red circles above) large orders Rationale: Sudden volume spikes at key levels indicate institutional participation - the "fuel" needed for breakouts or reversals. ________________________________________ 🎯 Trading Signal Logic Combined Setup Criteria The script generates SHORT and LONG signals when multiple conditions align: SHORT Signal Requirements: 1. Price reaches an HVN resistance zone (within 0.2%) 2. Large sell order detected (volume spike + red candle) 3. Cumulative delta is bearish OR bearish divergence present 4. 10-bar cooldown between signals (prevents overtrading) LONG Signal Requirements: 1. Price reaches an HVN support zone 2. Large buy order detected (volume spike + green candle) 3. Cumulative delta is bullish OR bullish divergence present 4. 10-bar cooldown enforced ________________________________________ 🔧 Customization Options Setting - Purpose - Recommendation Volume Profile Rows - Granularity of level detection - 20 (balanced) Lookback Period - Historical data analyzed - 50 bars (intraday), 200 (swing) Large Order Multiplier - Sensitivity to volume spikes - 2.5x (standard), 3.5x (conservative) HVN Threshold - Resistance zone detection - 1.3 (default) LVN Threshold - Target zone identification - 0.6 (default) Divergence Lookback - Pivot detection period - 5 bars (responsive) ________________________________________ 📈 Dashboard Indicators The real-time panel displays: • POC: Current Point of Control price • Location: Whether price is at HVN resistance • Orders: Current large buy/sell activity • Cumulative Δ: Net order flow value + trend direction • Divergence: Active bullish/bearish divergences • Bar Strength: % of candle volume that's directional (>65% = strong) • SETUP: Current trade signal (LONG/SHORT/WAIT) ________________________________________ 🎨 Visual System • Yellow POC Line: Highest volume level - primary pivot • Blue Value Area Box: Fair value zone (VAH to VAL) • Red HVN Zones: Resistance/support from institutional accumulation • Green LVN Zones: Low-liquidity targets for quick moves • Volume Bars: Green (buy pressure) vs Red (sell pressure) distribution • Triangles: LONG (green up) and SHORT (red down) entry signals • Diamonds: Divergence warnings (cyan=bullish, fuchsia=bearish) ________________________________________ 💡 How This Script Is Unique Unlike standalone volume profile or delta indicators, this script: 1. Synthesizes three complementary methods - volume structure, order flow momentum, and liquidity detection 2. Requires multi-factor confirmation - signals only trigger when price, volume, and delta align at key zones 3. Adapts to market regime - delta filters ensure you're trading with the dominant order flow direction 4. Provides context, not just signals - the dashboard helps you understand why a setup is forming ________________________________________ ⚙️ Best Practices Timeframes: • 5-15 min: Scalping (use 30-50 bar lookback) • 1-4 hour: Swing trading (use 100-200 bar lookback) Risk Management: • Enter on signal candle close • Stop loss: Beyond nearest HVN/LVN zone • Target 1: Next LVN level • Target 2: Opposite value area boundary Filters: • Avoid signals during major news events • Require bar delta strength >65% for aggressive entries • Wait for delta MA cross confirmation in ranging markets ________________________________________ 🚨 Alerts Available • Long Setup Trigger • Short Setup Trigger • Bullish/Bearish Divergence Detection • Large Buy/Sell Order Execution ________________________________________ 📚 Educational Context This methodology is based on principles used by professional order flow traders: • Market Profile Theory: Volume distribution reveals fair value • Tape Reading: Large orders show institutional intent • Auction Theory: Price seeks areas of liquidity imbalance (LVN zones) The script automates pattern recognition that discretionary traders spend years learning to identify manually. ________________________________________ ⚠️ Disclaimer This indicator is a trading tool, not a trading system. It identifies high-probability setups based on order flow analysis but requires proper risk management, market context, and trader discretion. Past performance does not guarantee future results. ________________________________________ Version: 6 (Pine Script) Type: Overlay + Separate Pane (Delta Panel) Resource Usage: Moderate (500 bars history, 500 lines/boxes) ________________________________________ For questions or support, please comment below. If you find this script valuable, please boost and favorite! 🚀 1. Volume Profile Analysis The script constructs a horizontal volume profile by: - Dividing the price range into configurable rows (default: 20) - Accumulating volume at each price level over a lookback period (default: 50 bars) - Separating buy volume (green bars close > open) from sell volume (red bars) - Identifying three critical levels: - POC (Point of Control): Price level with highest traded volume - acts as a strong magnet - VAH/VAL (Value Area High/Low): Contains 70% of total volume - defines fair value zone - HVN (High Volume Nodes): Resistance zones where institutions accumulated positions - LVN (Low Volume Nodes): Thin zones that price moves through quickly - ideal targets Why This Matters: Institutional traders leave footprints through volume. HVN zones show where large players defended levels, making them reliable support/resistance. --- 2. Cumulative Delta (Order Flow) Tracks the running total of buying vs selling pressure: - **Bar Delta**: Difference between buy and sell volume per candle - **Cumulative Delta**: Sum of all bar deltas - shows net directional pressure - **Delta Moving Average**: Smoothed delta (20-period) to identify trend - **Delta Divergences**: - **Bullish**: Price makes lower low, but delta makes higher low (absorption at bottom) - **Bearish**: Price makes higher high, but delta makes lower high (exhaustion at top) **How It Works**: When cumulative delta trends up while price consolidates, it signals accumulation. Delta divergences reveal when smart money is positioned opposite to retail expectations. --- ### 3. **Large Order Detection** Identifies **institutional-sized orders** in real-time: - Compares current bar volume to 20-period moving average - Flags orders exceeding 2.5x average volume (configurable multiplier) - Distinguishes bullish (green circles below) vs bearish (red circles above) large orders **Rationale**: Sudden volume spikes at key levels indicate institutional participation - the "fuel" needed for breakouts or reversals. --- ## 🎯 Trading Signal Logic ### Combined Setup Criteria The script generates **SHORT** and **LONG** signals when multiple conditions align: **SHORT Signal Requirements:** 1. Price reaches an HVN resistance zone (within 0.2%) 2. Large sell order detected (volume spike + red candle) 3. Cumulative delta is bearish OR bearish divergence present 4. 10-bar cooldown between signals (prevents overtrading) **LONG Signal Requirements:** 1. Price reaches an HVN support zone 2. Large buy order detected (volume spike + green candle) 3. Cumulative delta is bullish OR bullish divergence present 4. 10-bar cooldown enforced --- ## 🔧 Customization Options | Setting | Purpose | Recommendation | |---------|---------|----------------| | **Volume Profile Rows** | Granularity of level detection | 20 (balanced) | | **Lookback Period** | Historical data analyzed | 50 bars (intraday), 200 (swing) | | **Large Order Multiplier** | Sensitivity to volume spikes | 2.5x (standard), 3.5x (conservative) | | **HVN Threshold** | Resistance zone detection | 1.3 (default) | | **LVN Threshold** | Target zone identification | 0.6 (default) | | **Divergence Lookback** | Pivot detection period | 5 bars (responsive) | --- ## 📈 Dashboard Indicators The real-time panel displays: - **POC**: Current Point of Control price - **Location**: Whether price is at HVN resistance - **Orders**: Current large buy/sell activity - **Cumulative Δ**: Net order flow value + trend direction - **Divergence**: Active bullish/bearish divergences - **Bar Strength**: % of candle volume that's directional (>65% = strong) - **SETUP**: Current trade signal (LONG/SHORT/WAIT) --- ## 🎨 Visual System - **Yellow POC Line**: Highest volume level - primary pivot - **Blue Value Area Box**: Fair value zone (VAH to VAL) - **Red HVN Zones**: Resistance/support from institutional accumulation - **Green LVN Zones**: Low-liquidity targets for quick moves - **Volume Bars**: Green (buy pressure) vs Red (sell pressure) distribution - **Triangles**: LONG (green up) and SHORT (red down) entry signals - **Diamonds**: Divergence warnings (cyan=bullish, fuchsia=bearish) --- ## 💡 How This Script Is Unique Unlike standalone volume profile or delta indicators, this script: 1. **Synthesizes three complementary methods** - volume structure, order flow momentum, and liquidity detection 2. **Requires multi-factor confirmation** - signals only trigger when price, volume, and delta align at key zones 3. **Adapts to market regime** - delta filters ensure you're trading with the dominant order flow direction 4. **Provides context, not just signals** - the dashboard helps you understand *why* a setup is forming --- ## ⚙️ Best Practices **Timeframes:** - 5-15 min: Scalping (use 30-50 bar lookback) - 1-4 hour: Swing trading (use 100-200 bar lookback) **Risk Management:** - Enter on signal candle close - Stop loss: Beyond nearest HVN/LVN zone - Target 1: Next LVN level - Target 2: Opposite value area boundary **Filters:** - Avoid signals during major news events - Require bar delta strength >65% for aggressive entries - Wait for delta MA cross confirmation in ranging markets --- ## 🚨 Alerts Available - Long Setup Trigger - Short Setup Trigger - Bullish/Bearish Divergence Detection - Large Buy/Sell Order Execution --- ## 📚 Educational Context This methodology is based on principles used by professional order flow traders: - **Market Profile Theory**: Volume distribution reveals fair value - **Tape Reading**: Large orders show institutional intent - **Auction Theory**: Price seeks areas of liquidity imbalance (LVN zones) The script automates pattern recognition that discretionary traders spend years learning to identify manually. --- ## ⚠️ Disclaimer This indicator is a **trading tool, not a trading system**. It identifies high-probability setups based on order flow analysis but requires proper risk management, market context, and trader discretion. Past performance does not guarantee future results. --- **Version**: 6 (Pine Script) **Type**: Overlay + Separate Pane (Delta Panel) **Resource Usage**: Moderate (500 bars history, 500 lines/boxes) --- *For questions or support, please comment below. If you find this script valuable, please boost and favorite!* 🚀
Pine Script®指标
由harshivsymposium提供
Gann Astronomical Turning PointsThis is a comprehensive Pine Script that implements W.D. Gann's astronomical theories to identify potential market turning points. Here's a detailed breakdown of the script: Overview The script identifies and displays astronomical events (sun angles, moon phases, and Mercury retrogrades) that Gann theorists believe correlate with market turning points. It also analyzes historical price performance following these events to provide statistical significance. Key Components 1. Input Parameters Date Range: Users can set the analysis period (start and end dates) Display Options: Toggle visibility of different astronomical events and tables Analysis Settings: Configure the lookback period for price change analysis (1-20 days) 2. Astronomical Calculations The script includes several functions to calculate celestial positions: getDaysSinceEpoch(t): Calculates days since January 1, 2000 (reference point) getSunLongitude(t): Computes the Sun's position in the ecliptic (0-360°) getMoonPhase(t): Determines the Moon's phase angle relative to the Sun getMercuryLongitude(t): Calculates Mercury's position in the ecliptic 3. Gann Critical Angles (Sun Events) The script identifies when the Sun reaches four critical angles that Gann considered significant: 0° Aries (Spring Equinox) 90° Cancer (Summer Solstice) 180° Libra (Fall Equinox) 270° Capricorn (Winter Solstice) These are detected by tracking when the Sun's longitude crosses these specific angles. 4. Moon Phases Four key moon phases are identified: New Moon: Moon passes between Earth and Sun First Quarter: Moon is 90° east of Sun Full Moon: Moon is opposite the Sun Last Quarter: Moon is 270° east of Sun 5. Mercury Retrograde Periods The script detects when Mercury appears to move backward in its orbit: Identifies start and end dates of retrograde motion Displays these periods as highlighted zones on the chart 6. Price Change Analysis For each astronomical event, the script: Calculates the percentage price change over a user-defined lookback period Categorizes changes as positive or negative Stores this data for statistical analysis 7. Statistical Significance The script calculates several metrics for each event type: Average Price Change: Mean percentage change following events Up/Down Ratio: Number of positive vs. negative changes Accuracy Percentage: How often the dominant direction occurred 8. Visual Elements The script includes multiple display components: Event Labels Sun Angles: Orange sun symbols displayed above price bars Moon Phases: Moon phase emojis displayed below price bars Mercury Retrograde: Red boxes highlighting the retrograde periods Information Tables Events Table: Shows upcoming and recent astronomical events Significance Analysis Table: Displays statistical performance of each event type Forecast Section: Identifies the next upcoming event and predicted direction 9. Forecasting Functionality The script predicts market direction for the next astronomical event based on: Historical average price change for that event type Statistical accuracy of previous similar events Color-coded forecast (green for bullish, red for bearish) This script offers an interesting implementation of Gann's astronomical theories, but should be used as part of a broader analysis rather than as a standalone trading system. Disclaimer: This indicator is for educational purposes only. Past performance does not guarantee future results. Always conduct your own research and risk assessment before trading.
Pine Script®指标
由kingshukghosh71提供
3
CNagda-MomentumX - Institutional FlowMomentumX is designed to empower traders with a deeper understanding of market movements by focusing on Institutional Flow and advanced market structure analytics. The core goal is to identify and visualize where major market participants are operating, and to translate these complex footprints into clear, actionable trading signals — all in real time. Real-time institutional activity mapping Actionable entry and exit signals based on live market structure Intuitive dashboard and dynamic chart visuals Fully customizable modules for trend, liquidity, and order blocks Core Logic Design At the heart of MomentumX lies a robust algorithmic engine built to capture and surface institutional trading behavior. By leveraging advanced mathematical models, the indicator calculates institutional volume ratios and price momentum to pinpoint aggressive moves from large participants. Institutional Volume & Price Momentum: Utilizes custom volume indicators and price change analysis to detect strong buying or selling pressure, filtering out retail noise. Liquidity Grab Detection & Activity Zones: The script identifies liquidity grabs by monitoring abrupt price sweeps at major support/resistance levels—often where institutions trigger stop hunts or reversals. All critical activity zones are automatically color-coded on the chart for instant recognition. Dashboard Visualization: A fully dynamic dashboard table overlays live scores for accumulation, distribution, strength, and weakness—giving traders a real-time scan of market health. Trendline & Order Block Architecture: The logic auto-detects pivot highs/lows to draw smart trendlines, while the order block system highlights key reversal areas and breaker zones—making market structure clear and actionable. MomentumX is packed with high-performance modules, each engineered to simplify complex market behavior and enhance decision-making for traders: Institutional Flow Signals: Instantly identifies spots where institutional players drive momentum, using unique volume and price activity analytics. Bullish/Bearish Liquidity Grab Detection: Marks abrupt price moves that signal stop hunts or reversals, letting traders anticipate snap-backs or trend shifts. Trendline Auto-Detection: Smartly draws trendlines based on significant swing highs and lows, automatically adjusting as price evolves. Order Block System (Rejection/Breaker): Spots and highlights key reversal zones with order block rectangles, confirming rejections or breakouts at strategic levels. Dashboard and Bar Coloring: A clean dashboard overlay presents live market scores, while dynamic bar coloring makes trend, strength, and high-activity periods instantly visible. User Input Toggles for Each Module: Every major feature is fully customizable—enable or disable modules to match individual trading setups or preferences. Scripting/Development MomentumX’s scripting process is modular, enabling clarity, scalability, and fast optimization throughout development: Initialization & Inputs: Start by defining all user input options, module toggles, color settings, and calculation parameters—ensuring maximum flexibility early on. Core Calculation Functions: Script advanced institutional volume and price momentum algorithms. Build out swing length logic, market state filters, and activity scoring methods. Detection Engines: Develop and integrate engines for liquidity grabs, automated trendline detection, and order block identification—each with dedicated functions for speed and precision. Visual Overlays & Plotting: Implement powerful plotting logic for colored bars, score dashboards, trendlines, reversal zones, and liquidity markers—making every data point clear and actionable on the chart. Testing Handlers: Add diagnostic panels and debug outputs to refine calculations and assure accuracy in every market environment. Sample Trade Setups (Usage) Cnagda MomentumX delivers clarity for multiple trading styles by providing timely, actionable setups grounded in institutional behavior and market structure. Here’s how traders can leverage the indicator for confident decision-making: Liquidity Grab Reversal Enter trades around detected liquidity grabs when price sweeps major support/resistance and the dashboard signals a momentum shift. Example: Wait for a bullish/Bearish grab near market lows/high, with institutional flow turning positive/negative—enter long/short for potential mean reversion. Order Block Breakout Trade breakouts when price cleanly rejects or flips key order block zones highlighted on the chart. Example: Short at a marked breaker block after a rejection signal, confirmed by a downward institutional activity spike. Trendline Continuation Ride established market moves by entering on trendline confirmations plotted by the auto-detect system. Example: Go long after a trendline retest, confirmed by a green bar color and dashboard strength score. Dashboard Confirmation Combine dashboard metrics (strength, accumulation, distribution) with bar color overlays for multi-factor entries. Example: Enter trades only when all market signals align in real time for maximum probability. For Short Entry check -- Weakness : For Long Entry Check - Strength With Other Indications MomentumX is not just another indicator – it’s your edge for reading the market like an insider. By transparently mapping institutional flow, uncovering hidden liquidity zones, and color-coding every major structure shift, MomentumX transforms complexity into actionable clarity. Whether you’re scalping, swing trading, or investing, you’ll gain a decisive, real-time advantage on every chart. Embrace smarter decisions, adapt to changing market conditions instantly, and join a new generation of technically empowered traders. Customize, observe, and let the market reveal opportunities in a way you’ve never experienced before. Happy Trading
Pine Script®指标
由cnagda3提供
7
Forex Heatmap█   OVERVIEW This indicator creates a dynamic grid display of currency pair cross rates (exchange rates) and percentage changes, emulating the Cross Rates and Heat Map widgets available on our Forex page. It provides a view of realtime exchange rates for all possible pairs derived from a user-specified list of currencies, allowing users to monitor the relative performance of several currencies directly on a TradingView chart. █   CONCEPTS Foreign exchange The Foreign Exchange (Forex/FX) market is the largest, most liquid financial market globally, with an average daily trading volume of over 5 trillion USD. Open 24 hours a day, five days a week, it operates through a decentralized network of financial hubs in various major cities worldwide. In this market, participants trade currencies in pairs , where the listed price of a currency pair represents the exchange rate from a given base currency to a specific quote currency . For example, the "EURUSD" pair's price represents the amount of USD (quote currency) that equals one unit of EUR (base currency). Globally, the most traded currencies include the U.S. dollar (USD), Euro (EUR), Japanese yen (JPY), British pound (GBP), and Australian dollar (AUD), with USD involved in over 87% of all trades. Understanding the Forex market is essential for traders and investors, even those who do not trade currency pairs directly, because exchange rates profoundly affect global markets. For instance, fluctuations in the value of USD can impact the demand for U.S. exports or the earnings of companies that handle multinational transactions, either of which can affect the prices of stocks, indices, and commodities. Additionally, since many factors influence exchange rates, including economic policies and interest rate changes, analyzing the exchange rates across currencies can provide insight into global economic health. █   FEATURES Requesting a list of currencies This indicator requests data for every valid currency pair combination from the list of currencies defined by the "Currency list" input in the "Settings/Inputs" tab. The list can contain up to six unique currency codes separated by commas, resulting in a maximum of 30 requested currency pairs. For example, if the specified "Currency list" input is "CAD, USD, EUR", the indicator requests and displays relevant data for six currency pair combinations: "CADUSD", "USDCAD", "CADEUR", "EURCAD", "USDEUR", "EURUSD". See the "Grid display" section below to understand how the script organizes the requested information. Each item in the comma-separated list must represent a valid currency code. If the "Currency list" input contains an invalid currency code, the corresponding cells for that currency in the "Cross rates" or "Heat map" grid show "NaN" values. If the list contains empty items, e.g., "CAD, ,EUR, ", the indicator ignores them in its data requests and calculations. NOTE: Some uncommon currency pair combinations might not have data feeds available. If no available symbols provide the exchange rates between two specified currencies, the corresponding table cells show "NaN" results. Realtime data The indicator retrieves realtime market prices, daily price changes, and minimum tick sizes for all the currency pairs derived from the "Currency list" input. It updates the retrieved information shown in its grid display after new ticks become available to reflect the latest known values. NOTE: Pine scripts execute on realtime bars only when new ticks are available in the chart's data feed. If no new updates are available from the chart's realtime feed, it may cause a delay in the data the indicator receives. Grid display This indicator displays the requested data for each currency pair in a table with cells organized as a grid. Each row name corresponds to a pair's base currency , and each column name corresponds to a quote currency . The cell at the intersection of a specific row and column shows the value requested from the corresponding currency pair. For example, the cell at the intersection of a "EUR" row and "USD" column shows the data retrieved for the "EURUSD" currency pair, and the cell at the "USD" row and "EUR" column shows data for the inverse pair ("USDEUR"). Note that the main diagonal cells in the table, where rows and columns with the same names intersect, are blank. The exchange rate from one currency to itself is always 1, and no Forex symbols such as "EUREUR" exist. The dropdown input at the top of the "Settings/Inputs" tab determines the type of information displayed in the table. Two options are available: "Cross rates" and "Heat map" . Both modes color their cells for light and dark themes separately based on the inputs in the "Colors" section. Cross rates When a user selects the "Cross rates" display mode, the table's cells show the latest available exchange rate for each currency pair, emulating the behavior of the Cross Rates widget. Each cell's value represents the amount of the quote currency (column name) that equals one unit of the base currency (row name). This display allows users to compare cross rates across currency pairs, and their inverses. The background color of each cell changes based on the most recent update to the exchange rate, allowing users to monitor the direction of short-term fluctuations as they occur. By default, the background turns green (positive cell color) when the cross rate increases from the last recorded update and red (negative cell color) when the rate decreases. The cell's color reverts to the chart's background color after no new updates are available for 200 milliseconds. Heat map When a user selects the "Heat map" display mode, the table's cells show the latest daily percentage change of each currency pair, emulating the behavior of the Heat Map widget. In this mode, the background color of each cell depends on the corresponding currency pair's daily performance. Heat maps typically use colors that vary in intensity based on the calculated values. This indicator uses the following color coding by default:  • Green (Positive cell color): Percentage change > +0.1%  • No color: Percentage change between 0.0% and +0.1%  • Bright red (Negative cell color): Percentage change < -0.1%  • Lighter/darker red (Minor negative cell color): Percentage change between 0.0% and -0.1% █   FOR Pine Script™ CODERS • This script utilizes dynamic requests to iteratively fetch information from multiple contexts using a single request.security() instance in the code. Previously, `request.*()` functions were not allowed within the local scopes of loops or conditional structures, and most `request.*()` function parameters, excluding `expression`, required arguments of a simple or weaker qualified type. The new `dynamic_requests` parameter in script declaration statements enables more flexibility in how scripts can use `request.*()` calls. When its value is `true`, all `request.*()` functions can accept series arguments for the parameters that define their requested contexts, and `request.*()` functions can execute within local scopes. See the Dynamic requests section of the Pine Script™ User Manual to learn more. • Scripts can execute up to 40 unique `request.*()` function calls. A `request.*()` call is unique only if the script does not already call the same function with the same arguments. See this section of the User Manual's Limitations page for more information. • Typically, when requesting higher-timeframe data with request.security() using barmerge.lookahead_on as the `lookahead` argument, the `expression` argument should use the history-referencing operator to offset the series, preventing lookahead bias on historical bars. However, the request.security() call in this script uses barmerge.lookahead_on without offsetting the `expression` because the script only displays results for the latest historical bar and all realtime bars, where there is no future information to leak into the past. Instead, using this call on those bars ensures each request fetches the most recent data available from each context. • The request.security() instance in this script includes a `calc_bars_count` argument to specify that each request retrieves only a minimal number of bars from the end of each symbol's historical data feed. The script does not need to request all the historical data for each symbol because it only shows results on the last chart bar that do not depend on the entire time series. In this case, reducing the retrieved bars in each request helps minimize resource usage without impacting the calculated results. Look first. Then leap.
Pine Script®指标
由TradingView提供
2
MACD with DPO Strategy by NGExplanation of the MACD with DPO Strategy: MACD (Moving Average Convergence Divergence): The MACD is a trend-following indicator that shows the relationship between two moving averages of a price. In this script: We calculate the MACD line by subtracting the slow moving average (typically 26-period EMA) from the fast moving average (typically 12-period EMA). The Signal line is calculated as a 9-period EMA of the MACD line. The Histogram is the difference between the MACD line and the Signal line, indicating the momentum of the price trend. Buy Condition: The script generates a buy signal when the MACD histogram crosses from negative to positive (indicating a bullish momentum) and DPO is also positive. Sell Condition: The script generates a sell signal when the MACD histogram crosses from positive to negative (indicating a bearish momentum) and DPO is also negative. DPO (Detrended Price Oscillator): The DPO removes long-term trends from prices, making it easier to identify shorter-term cycles or oscillations. In this script: We calculate the DPO by subtracting a shifted simple moving average (SMA) from the close price. The shifting period depends on half the specified period. We also calculate the DPO SMA as a 30-period EMA of the DPO values. DPO Color: The DPO line is colored green when the DPO is above zero (indicating upward momentum) and red when it is below zero (indicating downward momentum). The histogram is also colored based on whether the DPO is positive or negative. Plotting and Alerts: The script plots the MACD, Signal, and Histogram on the chart. Additionally, it plots the DPO and its SMA with different colors depending on whether the DPO is above or below zero. Buy Signal: A green arrow labeled "BUY" is plotted below the bar when both MACD and DPO indicate a bullish condition. Sell Signal: A red arrow labeled "SELL" is plotted above the bar when both MACD and DPO indicate a bearish condition. Background colors are used to highlight the chart whenever a buy or sell condition occurs. The script also includes alerts for both buy and sell signals, allowing users to set notifications when conditions are met. How to Use: Identify Buy and Sell Signals: The script generates a Buy signal when: The MACD histogram crosses from negative to positive (bullish momentum), and The DPO is above zero (indicating upward momentum). The script generates a Sell signal when: The MACD histogram crosses from positive to negative (bearish momentum), and The DPO is below zero (indicating downward momentum). Chart Visualization: The MACD histogram and Signal line help visualize the momentum and potential trend reversal. The DPO and DPO SMA help visualize the shorter-term price cycles. The signals (Buy and Sell) will be plotted on the chart with arrows indicating entry points. Customization: You can adjust the MACD and DPO parameters (such as fast_length, slow_length, period_) to fit your trading style or market conditions. The script can be used in any timeframe depending on your strategy (e.g., intraday trading or longer-term trading). Example Scenario: If you're looking for potential buy opportunities, wait for the script to generate a buy signal (green arrow) where the MACD histogram has shifted to positive, and DPO is also in the green (above zero). This signals that both momentum and cycle direction are aligned for a potential upward movement. Conversely, for sell opportunities, wait for the red arrow where MACD momentum is turning negative and DPO is also negative (below zero), indicating a bearish condition. This combination of MACD and DPO allows traders to identify stronger and more reliable entry/exit points by confirming the trend with the MACD and detecting shorter-term price cycles with the DPO.
Pine Script®指标
由WatcharinDangjae提供
Ticker Tape█   OVERVIEW This indicator creates a dynamic, scrolling display of multiple securities' latest prices and daily changes, similar to the ticker tapes on financial news channels and the Ticker Tape Widget . It shows realtime market information for a user-specified list of symbols along the bottom of the main chart pane. █   CONCEPTS Ticker tape Traditionally, a ticker tape was a continuous, narrow strip of paper that displayed stock prices, trade volumes, and other financial and security information. Invented by Edward A. Calahan in 1867, ticker tapes were the earliest method for electronically transmitting live stock market data. A machine known as a "stock ticker" received stock information via telegraph, printing abbreviated company names, transaction prices, and other information in a linear sequence on the paper as new data came in. The term "ticker" in the name comes from the "tick" sound the machine made as it printed stock information. The printed tape provided a running record of trading activity, allowing market participants to stay informed on recent market conditions without needing to be on the exchange floor. In modern times, electronic displays have replaced physical ticker tapes. However, the term "ticker" remains persistent in today's financial lexicon. Nowadays, ticker symbols and digital tickers appear on financial news networks, trading platforms, and brokerage/exchange websites, offering live updates on market information. Modern electronic displays, thankfully, do not rely on telegraph updates to operate. █   FEATURES Requesting a list of securities The "Symbol list" text box in the indicator's "Settings/Inputs" tab allows users to list up to 40 symbols or ticker Identifiers. The indicator dynamically requests and displays information for each one. To add symbols to the list, enter their names separated by commas . For example: "BITSTAMP:BTCUSD, TSLA, MSFT". Each item in the comma-separated list must represent a valid symbol or ticker ID. If the list includes an invalid symbol, the script will raise a runtime error. To specify a broker/exchange for a symbol, include its name as a prefix with a colon in the "EXCHANGE:SYMBOL" format. If a symbol in the list does not specify an exchange prefix, the indicator selects the most commonly used exchange when requesting the data. Realtime updates This indicator requests symbol descriptions, current market prices, daily price changes, and daily change percentages for each ticker from the user-specified list of symbols or ticker identifiers. It receives updated information for each security after new realtime ticks on the current chart. After a new realtime price update, the indicator updates the values shown in the tape display and their colors. The color of the percentages in the tape depends on the change in price from the previous day . The text is green when the daily change is positive, red when the value is negative, and gray when the value is 0. The color of each displayed price depends on the change in value from the last recorded update, not the change over a daily period. For example, if a security's price increases in the latest update, the ticker tape shows that price with green text, even if the current price is below the previous day's closing price. This behavior allows users to monitor realtime directional changes in the requested securities. NOTE: Pine scripts execute on realtime bars when new ticks are available in the chart's data feed. If no new updates are available from the chart's realtime feed, it may cause a delay in the data the indicator receives. Ticker motion This indicator's tape display shows a list of security information that incrementally scrolls horizontally from right to left after new chart updates, providing a dynamic visual stream of current market data. The scrolling effect works by using a counter that increments across successive intervals after realtime ticks to control the offset of each listed security. Users can set the initial scroll offset with the "Offset" input in the "Settings/Inputs" tab. The scrolling rate of the ticker tape display depends on the realtime ticks available from the chart's data feed. Using the indicator on a chart with frequent realtime updates results in smoother scrolling. If no new realtime ticks are available in the chart's feed, the ticker tape does not move. Users can also deactivate the scrolling feature by toggling the "Running" input in the indicator's settings. █   FOR Pine Script™ CODERS • This script utilizes dynamic requests to iteratively fetch information from multiple contexts using a single request.security() instance in the code. Previously, `request.*()` functions were not allowed within the local scopes of loops or conditional structures, and most `request.*()` function parameters, excluding `expression`, required arguments of a simple or weaker qualified type. The new `dynamic_requests` parameter in script declaration statements enables more flexibility in how scripts can use `request.*()` calls. When its value is `true`, all `request.*()` functions can accept series arguments for the parameters that define their requested contexts, and `request.*()` functions can execute within local scopes. See the Dynamic requests section of the Pine Script™ User Manual to learn more. • Scripts can execute up to 40 unique `request.*()` function calls. A `request.*()` call is unique only if the script does not already call the same function with the same arguments. See this section of the User Manual's Limitations page for more information. • This script converts a comma-separated "string" list of symbols or ticker IDs into an array . It then loops through this array, dynamically requesting data from each symbol's context and storing the results within a collection of custom `Tape` objects . Each `Tape` instance holds information about a symbol, which the script uses to populate the table that displays the ticker tape. • This script uses the varip keyword to declare variables and `Tape` fields that update across ticks on unconfirmed bars without rolling back. This behavior allows the script to color the tape's text based on the latest price movements and change the locations of the table cells after realtime updates without reverting. See the `varip` section of the User Manual to learn more about using this keyword. • Typically, when requesting higher-timeframe data with request.security() using barmerge.lookahead_on as the `lookahead` argument, the `expression` argument should use the history-referencing operator to offset the series, preventing lookahead bias on historical bars. However, the request.security() call in this script uses barmerge.lookahead_on without offsetting the `expression` because the script only displays results for the latest historical bar and all realtime bars, where there is no future information to leak into the past. Instead, using this call on those bars ensures each request fetches the most recent data available from each context. • The request.security() instance in this script includes a `calc_bars_count` argument to specify that each request retrieves only a minimal number of bars from the end of each symbol's historical data feed. The script does not need to request all the historical data for each symbol because it only shows results on the last chart bar that do not depend on the entire time series. In this case, reducing the retrieved bars in each request helps minimize resource usage without impacting the calculated results. Look first. Then leap.
Pine Script®指标
由TradingView提供
4
Risk Management Calculator with Fees and Take Profit [CHE]Risk Management Calculator with Fees and Take Profit Welcome to the Risk Management Calculator with Fees and Take Profit script! This powerful tool is designed to help traders manage their risk effectively, calculate leverage, and set take profit targets. The script is inspired by and builds upon the ideas from the following TradingView script: (). This script is inspired by and builds upon the ideas from the following TradingView script: Features 1. Portfolio Size Input: Enter the size of your portfolio to accurately calculate your risk and leverage. 2. Max Loss Percent Input: Specify the maximum percentage of your portfolio that you are willing to risk on a single trade. 3. Max Leverage Input: Set the maximum leverage you are comfortable using. 4. Trading Fee Input: Include trading fees in your calculations to get a more realistic view of your potential losses and gains. 5. ATR Settings: Configure the ATR period and multiplier to calculate your stop loss and take profit levels. 6. RSI Settings: Adjust the RSI period for trend analysis. How to Use Portfolio Size - Description: This is the total value of your trading account. - Input: `portfolioSize` - Default Value: 100 - Minimum Value: 0.001 Max Loss Percent - Description: The maximum percentage of your portfolio you are willing to lose on a single trade. - Input: `maxLossPercent` - Default Value: 3% - Range: 0.1% to 100% Max Leverage - Description: The maximum leverage you wish to use. - Input: `maxLeverage` - Default Value: 125 - Range: 1 to 125 Trading Fee - Description: The fee percentage you pay per trade. - Input: `feeRate` - Default Value: 1% - Range: 0% to 10% ATR Settings - ATR Period: Number of bars used to calculate the Average True Range. - Input: `atrPeriod` - Default Value: 5 - ATR Multiplier: Multiplier for ATR to set stop loss levels. - Input: `atrMultiplier` - Default Value: 2.0 Take Profit Multiplier - Description: Multiplier for ATR to set take profit levels. - Input: `takeProfitMultiplier` - Default Value: 2.0 RSI Settings - RSI Period: Period for the RSI calculation. - Input: `rsiPeriod` - Default Value: 14 Dashboard The script includes a customizable dashboard that displays the following information: - Portfolio Size - Maximum Loss Amount - Entry Price - Stop Loss Price - Stop Loss Percentage - Calculated Leverage - Order Value - Order Quantity - Trend Direction - Adjusted Maximum Loss Percentage - Take Profit Price Dashboard Settings - Location: Choose the position of the dashboard on the chart. - Options: 'Top Right', 'Bottom Right', 'Top Left', 'Bottom Left' - Size: Adjust the size of the dashboard text. - Options: 'Tiny', 'Small', 'Normal', 'Large' - Text/Frame Color: Set the color for the text and frame of the dashboard. Underlying Principles and Assumptions Leverage Calculation The leverage calculation is fundamental to risk management in trading. It ensures that the risk per trade does not exceed a specified percentage of the portfolio. This calculation takes into account the potential loss from the entry price to the stop loss level, adjusted for trading fees. By dividing the maximum acceptable loss by the total potential loss (including fees), we derive a leverage that limits the exposure per trade. This approach helps traders avoid over-leveraging, which can lead to significant losses. ATR and Stop Loss The Average True Range (ATR) is used to set stop loss levels because it measures market volatility. A higher ATR indicates more volatility, which means wider stop losses are needed to avoid being prematurely stopped out by normal market fluctuations. By using an ATR multiplier, the stop loss is dynamically adjusted based on current market conditions, providing a more robust risk management strategy. Take Profit Calculation The take profit level is calculated as a multiple of the ATR, ensuring that it is set at a realistic level relative to market volatility. This method aims to capture significant price movements while avoiding the noise of smaller fluctuations. Setting take profit targets this way helps in locking in profits when the market moves favorably. RSI for Trend Confirmation The Relative Strength Index (RSI) is used to confirm the trend direction. An RSI above 50 typically indicates a bullish trend, while an RSI below 50 indicates a bearish trend. By aligning trades with the prevailing trend, the script increases the probability of successful trades. This trend confirmation helps in making informed decisions about leverage and position sizing. Risk Color Coding The script uses color coding to visually indicate the risk level and trend direction. Green indicates a favorable condition for long trades, red for short trades, and gray for neutral conditions. This intuitive color coding aids in quickly assessing the market conditions and making timely trading decisions. Conclusion This script aims to provide a comprehensive risk management tool for traders. By integrating portfolio size, leverage, fees, ATR, and RSI, it helps in making informed trading decisions. We hope you find this tool useful in your trading journey. Happy Trading!
Pine Script®指标
由chervolino提供
2
Sessions [UkutaLabs]█ OVERVIEW Sessions is a trading toolkit that displays the different trading sessions on your chart during a trading day. By default, Sessions displays the four standard trading sessions; New York, Tokyo, London, and Sydney. Each of the four sessions can be toggled, and the Sessions indicator is completely customizable, allowing users to define their own sessions to be generated by the script. The aim of this script is to improve the trading experience of users by automatically displaying information about each default or custom session to the user. █ USAGE This script will automatically detect and label different market sessions. By default, the script will identify the four standard trading sessions, but each of these can be toggled off in the settings. However, users are not limited to these four trading sessions and have the ability to define their own sessions to be identified by the script. When a session begins, the script will automatically start outlining the market data of that session, including the high and low of the period that is represented by the session. If the market is within two or more sessions at the same time, then each session will be treated individually and will overlap with each other. The sessions will be identified as a colored box surrounding the market data of the period that it represents, and a label will be displayed above the box to identify the session that it represents. The label, color and period of each session is completely customizable. The user can also adjust all sessions at once to account for timezones in the settings. █ SETTINGS Session 1 • Session 1: Determines whether or not this session will be drawn by the script. • A string field to determine the name of the session that will be displayed above the session range. • Two time fields representing the start and finish of the session. • A color field to determine the color of the range and label. Session 2 • Session 2: Determines whether or not this session will be drawn by the script. • A string field to determine the name of the session that will be displayed above the session range. • Two time fields representing the start and finish of the session. • A color field to determine the color of the range and label. Session 3 • Session 3: Determines whether or not this session will be drawn by the script. • A string field to determine the name of the session that will be displayed above the session range. • Two time fields representing the start and finish of the session. • A color field to determine the color of the range and label. Session 4 • Session 4: Determines whether or not this session will be drawn by the script. • A string field to determine the name of the session that will be displayed above the session range. • Two time fields representing the start and finish of the session. • A color field to determine the color of the range and label. Time Zones • UTC +/-: Determines the offset of each session. Enter - before the number to represent a negative offset.
Pine Script®指标
由UkutaLabs提供
1
Daniels Script v2 EMA 4h y DTitle: "EMA 200 Dynamic Projection on 4H and Daily Charts" Description: "This script is designed to provide traders with a comprehensive view of market trends by displaying the 200-period Exponential Moving Average (EMA) on both 4-hour and daily charts simultaneously. Unlike typical EMA representations, this script enhances user decision-making by projecting the potential future path of these EMAs using a dynamic slope calculation. The dynamic projection feature calculates the slope based on recent changes in the EMA, allowing traders to visualize potential future trends more accurately. This innovative approach helps in identifying potential areas of support and resistance before they are fully formed, offering traders a strategic advantage in planning their entries and exits. Key Features: Dual Time Frame Analysis: View 200-period EMAs for both 4-hour and daily charts on a single graph. Dynamic EMA Projections: Projected using a calculated slope from recent EMA changes, presented as dotted lines for clear distinction. Enhanced Trend Visualization: Helps in recognizing trend continuations or reversals early, aiding in risk management and decision-making processes. Usage: Simply add the script to your chart, and the EMAs along with their projections will automatically be displayed. The 4-hour EMA is shown in green, while the daily EMA is in red. Projections extend from the last known data point, providing a visual guide to potential future movements. This script is unique in its approach to combining real-time EMA analysis with predictive modeling, making it a valuable tool for traders looking to enhance their technical analysis capabilities." ## SPANISH Título del Script: "Proyección Dinámica de la EMA 200 en Gráficos de 4H y Diarios" Descripción del Script: "Este script está diseñado para proporcionar a los traders una visión integral de las tendencias del mercado al mostrar la Media Móvil Exponencial (EMA) de 200 periodos tanto en los gráficos de 4 horas como diarios simultáneamente. A diferencia de las representaciones típicas de la EMA, este script mejora la toma de decisiones del usuario al proyectar el posible camino futuro de estas EMAs utilizando un cálculo de pendiente dinámico. La función de proyección dinámica calcula la pendiente basada en cambios recientes en la EMA, permitiendo a los traders visualizar tendencias futuras potenciales con mayor precisión. Este enfoque innovador ayuda a identificar áreas potenciales de soporte y resistencia antes de que se formen completamente, ofreciendo a los traders una ventaja estratégica en la planificación de sus entradas y salidas. Características Clave: Análisis de Doble Marco Temporal: Visualiza las EMAs de 200 periodos para los gráficos de 4 horas y diarios en un solo gráfico. Proyecciones Dinámicas de la EMA: Proyectadas utilizando una pendiente calculada a partir de cambios recientes en la EMA, presentadas como líneas punteadas para una clara distinción. Visualización Mejorada de Tendencias: Ayuda en el reconocimiento temprano de continuaciones o reversos de tendencias, asistiendo en la gestión de riesgos y en los procesos de toma de decisiones. Uso: Simplemente añade el script a tu gráfico, y las EMAs junto con sus proyecciones se mostrarán automáticamente. La EMA de 4 horas se muestra en verde, mientras que la EMA diaria está en rojo. Las proyecciones se extienden desde el último punto de datos conocido, proporcionando una guía visual hacia movimientos futuros potenciales. Este script es único en su enfoque de combinar análisis de EMA en tiempo real con modelado predictivo, convirtiéndolo en una herramienta valiosa para traders que buscan mejorar sus capacidades de análisis técnico."
Pine Script®指标
由unixbsd提供
Triple MA HTF strategy - Dynamic SmoothingThe triple MA strategy is a simple but effective method to trade the trend. The advantage of this script over the existing triple MA strategies is that the user can open a lower time frame chart and select higher time frame inputs for different MA types mainting the visibility on the chart. The dynamic smoothing code makes sure the HTF trendlines are not jagged, but a fluid line visiable on the lower time frame chart. The script comes with a MA crossover and crossunder strategy explained below. Moving Averages (MA) Crossover for Entry: Long Entry: A long entry signal is triggered when the moving average line 1 crosses above the moving average line 2. This crossover indicates a potential shift in market sentiment towards the upside. However, to validate this signal, the strategy checks if the moving average 3 on a higher time frame (eg. 4 hour) is in an upward trend. This additional filter ensures that the trade aligns with the prevailing trend on a broader time scale, increasing the probability of success. Short Entry: Conversely, a short entry signal occurs when the moving average line 1 crosses below the moving average line 2. This crossover suggests a possible downturn in market momentum. However, for a short trade to be confirmed, the strategy verifies that the moving average 3 on the higher time frame is in a downward trend. This confirmation ensures that the trade is in harmony with the overarching market direction. Exit from Long Position: The strategy triggers an exit signal from a long position when the moving average line 1 crosses below the moving average line 2. This crossover indicates a potential reversal in the market trend, prompting the trader to close their long position and take profits or minimize losses. Exit from Short Position: Similarly, an exit signal from a short position occurs when the moving average line 1 crosses above the moving average line 2. This crossover suggests a potential shift in market sentiment towards the upside, prompting the trader to exit their short position and manage their risk accordingly. Features of the script This Triple MA Strategy is basically the HTF Trend Filter displayed 3 times on the chart. For more infomation on how the MA with dynamic smoothing is calculated I recommend reading the following script: For risk management I included a simple script to opt for % of eauity or # of contracts of in the instrument. For explanation on how the risk management settings work I refer to my ealier published script: The strategy is a simplified example for setting up an entry and exit logic based on multiple moving avarages. Hence the script is meant for educational purposes only.
Pine Script®策略
由Harrocop提供