始めましょう

ローソク足分析

NYCOB Kill Zone StrategyI have now turned the NYCOB Kill zone into a stand alone strategy! Fully customizable in regards to time of entry and levels of entry but the standard settings are the best all around. Original NYCOB Kill Zone text below This script plots the H and L of the first 2 hours of the NYC session and shades the space between in which i deem the NYC Order Block It also maps out the First two hours on the chart as well so you can understand when the OB has formed Over the past 3 years of trading cryptocurrency i have noticed a phenomena that has occurred nearly every day The H or L will 90% of the time will be posted in the first two hours of this session knowing this means you understand if you just wait til this time you can better your odds at not getting stop hunted due to poor entry A few things to take from this study are these. 1. after the OB is formed 2. whichever side gets taken out first (H/L) will 90% define the bias for the day. I have found that using the m13-m15 TF will add some more confirmation with 1-2 closes outside of range H/L/ 3. After general bias has formed 2 things can happen A) PA just takes off and there is really nothing you can do about it unless you had other studies that told you that will happen B) PA will dip back INTO the OB and create the OTE which is any retracement below the .5 Fibonacci of the shaded OB 4. Typically OTE happens after the session has ended 5. If you used OTE off of the past days NYCOB then you can use the new (forming or just formed) NYCOB to CONFIRM your initial bias presented from the previous days OTE and bias. 6. When PA cannot close outside the NYCOB it presents a range to range play where PA will visit the opposite side of the range to chase liquidity, 7. When the NYCOB is TIGHT then deviation is more likely to result in price expansion, when the NYCOB is WIDE then deviation tends to present more range to range plays. 8. After bias is formed and OTE has been made your stops should always be outside the NYCOB. I use the m30 or H1 ATR to get a slight cushion from the OB to ensure i dont get stop hunted. Standard TP are all set at the same level but you can adjust them accordingly Shout out to Elevate-Trading family member Boederzeng for helping me with the code!
Pineスクリプト™ ストラテジー
SatoshiHeavyの投稿
1
Heikin Ashi+RSI+EMA Strategy 2.0 v4 [Cryptocurrency] by GodtrixHi, I know a lot of people are looking for a more sophisticated and customizable strategy tool, I'm facing the same problem too, so I created one for myself and decided to share it for free trials and if you think this tool do what you wanted, you can contact me for the subscription "Premium" version. I'll keep it simple with point forms, if you have any further inquiries or questions, please feel free to message me. Thank you. Best profit plan with this strategy is you trade on Future leverage while you hold on to your coin, so that when price goes up, your coin value goes up, and at the same time, you trade with your leverage to earn even more, easily doubling up your total profit. Benefits: Fully customizable and you can easily personalized it and FINE TUNE it according to the market or coin you trading on. The strategy is based on REAL PRACTICAL trading skills, so it works in real-world. I fixed the "repainting" issue so the backtest it shows you IS ACCURATE when you run for real-time. We all know one indicator is not going to help you win your trades, so this strategy combines ALL three: EMA for long+short term trend, HA for short term trend, RSI for entry/exit This strategy is designed for LONG trade (Buy low, Sell high), not for SHORT trade. This is not day trading, it is more to mid-term trading, where there's only few trades per month Mainly is coded to work with 3Commas bot auto trading, so you only need to key in your Bot ID & Email Token. Bot trading NOTE: You need to replace the Alert Message with this: {{strategy.order.alert_message}} One Alert will work for both Buy and Sell Order If you using other Bot service, you can enter Custom Command too, so it works on any bot service. Lastly, regarding the setting advice, I would say you try playing with different settings and your objective is to achieve a backtest result that has: 1) Profitable is > 80% 2) Losing trades is nearly 0 or below 25% of your winning trades. Trick is using far stop loss % 3) Net Profit be almost same or more than "Buy & Hold Profit" If you interested in our subscription version, message me for price. Best Luck & a million dollar profit to you, Godtrix BITSTAMP:BTCUSD BINANCE:DOTUSDT
Pineスクリプト™ ストラテジー
godtrixの投稿
6
4H Closes [Intromoto]This script is one level from the "closes" script, but as an individual script, this allows more historical closes to be observed at once. Shows 4 hour closes from the exact candle, regardless of time frame. Number of lines plotted is limited by tradingview/pinescript, show will only show a certain number i.e recent weekly levels. Lines can be styled by user: Thickness, solid vs dotted vs dashed, range of colors, label size and X location. The "line.new" function requires that you 'show' the indicator where the close occured, in order to have the line show. The labels are there regardless and will remind you of the level, with or without the line. This is also true if you change chart resolution. You may have to 'search' for the close to have the line show up. DM for access. Thanks!
Pineスクリプト™ インジケーター
Intromotoの投稿
2
6H Closes [Intromoto]This script is one level from the "closes" script, but as an individual script, this allows more historical closes to be observed at once. Shows 6 hour closes from the exact candle, regardless of time frame. Number of lines plotted is limited by tradingview/pinescript, show will only show a certain number i.e recent weekly levels. Lines can be styled by user: Thickness, solid vs dotted vs dashed, range of colors, label size and X location. The "line.new" function requires that you 'show' the indicator where the close occured, in order to have the line show. The labels are there regardless and will remind you of the level, with or without the line. This is also true if you change chart resolution. You may have to 'search' for the close to have the line show up. DM for access. Thanks!
Pineスクリプト™ インジケーター
Intromotoの投稿
Empirical MomentsBINANCE:BTCUSDT I thought I’d make an indicator for the “fast trader”. This indicator compares the changing high prices with the close prices and in doing so, detects positive “anomalies” (the outlier drift). It gets more complicated than that; the practical indicator is the “empirically weighted drift”, which is a weighted average of the former with its derivatives up to the third order I.e. the “outlier yank”. The empirically weighted drift crossing above and below zero with long and short actions, respectively is used as the strategy. With this strategy, current backtesting for the 15 minute BTCUSDT on the Binance market yields a Sharpe ratio of 1.47 and profit factor of 1.12. Publishing the strategy as well.
Pineスクリプト™ インジケーター
cryptoglutenの投稿
Pinescript - Common String Functions Library by RRBCommon String Functions Library by RagingRocketBull 2021 Version 1.0 Pinescript now has strong support for arrays with many powerful functions, but still lacks built-in string functions. Luckily you can easily process and manipulate strings using arrays. This script provides a library of common string functions for everyday use, such as: indexOf, substr, replace, ascii_code, str_to_int etc. There are 100+ unique functions (130 including all implementations) It should serve as building blocks to speed up the development of your custom scripts. You should also be able to learn how Pinescript arrays works and how you can process strings. Similar libraries for Array and Statistical Functions are in the works. You can find the full list of functions below. Features: - 100+ unique string functions (130 including all implementations) in categories: lookup, testing, conversion, modification, extraction, type conversion, date and time, console output - Live Output for all/selected functions based on User Input. Test any function before using in script. - Live Unit Test Output for several functions based on pre-defined inputs. - Output filters: show unique functions/all implementations, grouping - Console customization options: set custom text size, color, page length - Support for Pages - auto splits output into pages with fixed length, use pages in your scripts - Several easy to use console output functions to speed up debugging/output. WARNING: - Compilation Time: 1 min Notes: - uses Pinescript v3 Compatibility Framework - this script is packed to the max and sets a new record in testing of Pinescript's limits: 500 local scopes, 4000+ lines, 180kb+ source size. It's not possible to add more ifs/fors/functions without reducing functionality - to fit the max limit of local scopes = 500 all ifs were replaced with ?: where possible, the number of function calls was reduced, some calls replaced with inline function code - ifs are faster (especially when lots of them are used in a for cycle), more readable, but ifs/fors/functions increase local scopes (+1) and compiled file size, have max nesting limit = 10. - ?: are slower (especially in for cycles), hard to read when nested, don't affect local scopes, reduce compiled file size, can't contain plots, for statements (break/continue) and sets of statements - for most array functions to work (except push), an array must be defined with at least 1 pre-existing dummy element 0. - if you see "String too long" error - enable Show Pages, reduce Max Chars Per Page < Max String Length limit = 4096. - if you see "Loop too long" error - hide/unhide or reattach the script - some functions have several implementations that can be faster/slower, use internal code/ext functions - 1 is manual string processing using for cycles (array.get) and ext functions - provided in case you want to implement your own logic, may sometimes be slower - 2 is a 2nd alternate implementation mostly done using built-in functions (array.indexof, array.slice, array.insert, array.remove, str.replace_all), attempts to minimize local scopes and dependency on ext functions, should generally be faster - 3 is a 3rd alternate (array.includes, array.fill) or a more advanced implementation (datetime3_str) with lots of params, giving you the most control over output - most functions have dependencies, such as const names, global arrays, inputs, other functions. P.S. Strings of Time may be closed unto themselves or have loose ends; they can vibrate, stretch, join or split. Function Groups: 1. Char Functions - repeat(str, num) - ascii_char(code) - ascii_code(char) - is_digit(char) - is_letter(char) - digit_to_int(char) - is_space_char(char) 2. Char Test and Lookup Functions - char_at(str, pos) - char_code_at(str, pos) - indexOf_char(str, char) - lastIndexOf_char(str, char) - nth_indexOf_char(str, char, num) - includes_char(str, char) 3. String Lookup Functions - indexOf(str, target) - lastIndexOf(str, target) - nth_indexOf(str, target, num) - indexesOf(str, target) - numIndexesOf(str, target) 4. String Conversion Functions - lowercase(str) - uppercase(str) 5. String Modification and Extraction Functions - split(str, separator) - insert(str, pos, new_str) - remove(str, pos, length) - insert_char(str, pos, char) - remove_char(str, pos) - reverse(str) - fill_char(str, char, start_pos, end_pos) - replace(str, target, new_str) - replace_first(str, target, new_str) - replace_last(str, target, new_str) - replace_nth(str, target, new_str, num) - replace_left(str, new_str) - replace_right(str, new_str) - replace_middle(str, pos, new_str) - left(str, num) - right(str, num) - first_char(str) - last_char(str) - truncate(str, max_len) - truncate_middle2(str, trunc_str, pos, max_len) - truncate_from2(str, trunc_str, pos, max_len, side) - concat(str1, str2, trunc_str, max_len, mode) - concat_from(str1, str2, trunc_str, max_len, side, mode) - trim(str) - substr(str, pos, length) - substring(str, start_pos, end_pos) - strip(str, mask, target, is_allowed) - extract_groups(str) - extract_numbers(str, d1, d2, mode) - str_to_float(str, d1, d2) - str_to_int(str) - extract_ranges(str, d1, d2, d3, type) 6. String Test Functions - includes(str, target) - starts_with(str, target) - ends_with(str, target) - str_compare(str1, str2) 7. Type Conversion Functions - tf_check2(tf) - tf_to_mins() - convert_tf(tf) - period_to_mins(tf) - convert_tf2(tf) - convert_tf3(tf) - bool_to_str(flag) - get_src(src_str) - get_size(size_str) - get_style(style) - get_bool(bool_str) - get_int(str) - get_float(str, d1, d2) - get_color(str, def_color) - color_tr2(col_str, transp) - get_month(str) - month_name(num, format) - weekday_name(num, format) - dayofweek_name(t) 8. Date and Time Functions - date_str(t, d) - time_str(t, d) - datetime_str(t, d1, d2) - date2_str(t, d, type) - time2_str(t, d, type) - datetime2_str(t, d1, d2, format1, format2) - date3_str(t, template) - time3_str(t, template) - datetime3_str(t, template) 9. Console Output & Helper Functions - echo1(con, str) - echo2(x, y, con, str) - echo3(v_shift, con, str, msg_color, text_size) - echo4(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo5(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo6(x, y, con, str) - echo7(v_shift, con, str, msg_color, text_size) - echo8(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo9(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - new_page(str, line_str, trunc_str, header_str, footer_str, length, page_count, page, mode)
Pineスクリプト™ インジケーター
RagingRocketBullの投稿
17
Arpan_Candles_OL-OH-IBThis script simply shows OL (Open=Low) , OH (Open=High) and IB (Inside Bar) . I personally use OL and OH to take quick scalping trades with very low risk. OL candle indicates that candle's Open and Low prices are same and a Long trade can be taken with a stoploss below candle low. OH candle indicates that candle's Open and High prices are same and a SHORT trade can be taken with a stoploss above candle high. Candles with navy blue colour indicates an Inside Bar . An inside bar is a common pattern where the high and low of one candle occur inside the high and low of the prior candle. Inside bar shows a contraction in volatility and are often a continuation pattern. Previous candle (prior candle to inside bar) is known as "Mother candle" and trades can be taken on breakout from "Mother candle" , in the direction of breakout and keeping a stoploss below/above "Mother candle". This script can be used in any time frame. Smaller time frames generate more signals compared to higher time frames.
Pineスクリプト™ インジケーター
truetechlevelsの投稿
3
Double DojiStrategy Kiss = 'Keep It Simple, Stupid' or 'Keep It Simple, Smart' The script simply identifies 2 consecutive Doji candles, and calculates Target on both the sides for given Reward : Risk factor. The High-Low to Open-Close ratio is set to default value 20. The Reward : Risk ratio is of default value 2. Both can be set to values of your choice. Accuracy best on Daily chart. Can be tried on any timeframe though. Trading Rules: Buy at higher / Short at lower of the 2 candles, with other as Stop Loss. If a Stop Loss is hit, go for reverse trade. If again a SL is hit, switch to other instrument. Important: If trading in Futures and target is achieved, hedge the position by buying an option (subject to liquidity). Reason is, the trend may condition to any extent and you would definitely not want to miss out the whole action. Check the shared example. For a risk to 175 points, reward is 2200+ points (more than 12.5 times).
Pineスクリプト™ インジケーター
SushilKothawadeの投稿
2
Random Synthetic Asset GenerationThis script generates pseudo-random asset data . Due to the nature of the random generator, it is impossible to use this indicator as input for other indicators because the instance of the script that the indicator is applied to will automatically be different from the instance that is plotted on the chart. Therefore, the idea is to use this script in other scripts (to make it possible to backtest on random data, for example). The script has four main input parameters. Random Number Generator Method: It supports two methods for generating the pseudo-random numbers (one by Ricardo Santos and one by Wichmann-Hill). Seed: You can specify the seed to use. Each unique seed will generate a unique set of pseudo-random data. Intrabar Volatility: This basically sets how volatile the generated wicks will be (0 = no wicks). Price Multiplier: This is just a multiplier for the generated price data, so that you can scale up or down the generated price data. You can also change the colors of the bars. In addition to this, the indicator also generates random volume. In order to make it possible to show both volume and price, you need to have two identical instances of the indicator. One on the chart, and one in its own panel. Then, go into the Style tab in the indicator settings on the instance in the panel. Untick Up-Candles and Down-Candles boxes, and tick the Volume box. In a similar manner, you can also plot the true range data and the candle change data as well, by ticking one of those boxes instead.
Pineスクリプト™ インジケーター
lejmerの投稿
13
TTT_Swing_and_Orderblock_Ver_1.0.2Hello, dear traders from all over the world! This is Tommy from Tommy Trading Team. Many inquires were delivered to us from traders recently wishing to use one of our cutting-edge technologies that was developed days ago and was only used by us. We have edited and supplemented this indicator both logically and visually. Accordingly, our team is officially launching with a new brought up name, which is “SOB(Version1.0.2), shorten for “Swing & OB(Orderblock).” This technical indicator is quite straightforward and effective to utilize since it shows traders the essential variables that are considered by many recently developed theories and state-of-the-art methodologies. And they are ‘Dow’ and ‘Orderblock’. Swing High and Low (Dow Theory) has been applied fundamentally by many other theories and methodologies such as Elliott wave theory and SR Flip techniques. A swing can be interpreted as a wave with a trend composed of a high and a low each. After succeeding on making significant highs/lows, in any existing wave theories, it is essential to monitor and spot when the next waves make HH(Higher high), LH(Lower high), HL(Higher low), or LL(Lower low). OB(Orderblock) technique is a very advanced methodology that captures the contraction, consolidation, and attraction zone. This so called ‘zone’ is interpreted differently by various stakeholders, such as institutional(whales) average entry/exit price range or peak price range with higher traded volumes. In TA perspective, it’s just a major support/resistance to consider and when this zone fails to support/resist, the price momentum tends to boost up towards the direction it failed. To give you a little tip, look for the spots usually forming horizontal parallel channel, before a big wave with a clear trend (whether up or down) appears. There are numerous ways to identify OB and we have concluded that signaling the double engulfing candles is one of the highly effective one. As just mentioned, comprehending a trend utilizing ‘Swing HL’ is fundamental and yet definite TA concept and strategy. Furthermore, OB can also be useful to spot major support and resistance area. SOB automatically identify and captures major Highs, Lows, and OBs. In addition, SOB can let traders know when the highs and lows are being replaced by higher/lower highs/lows by changing pivots color. If you are familiar with SR(Support and Resistance) Flip concept, this can be a helpful tool for you since it can signal when highs/lows are being broken above/below and by planning a retest entry trading setup. If you would like to try SOB_ver1.0.2, please let us know through comments, DM, or Telegram in English/Korean. I assure you that our SOB won’t disappoint you on your trading chart. Thank you. 안녕하세요. 트레이더 여러분! 토미 트레이딩 팀입니다~ 최근에 저희 팀이 개인적으로 사용했던 지표에 관해서 많은 분들이 문의를 주셨습니다. 약간의 보안 및 개선 작업 이후에 SOB(Version1.0.2)이라는 이름으로 정식 출시합니다. 해당 알고리즘은 기존의 여러 이론 및 방법론들에게 원천적으로 기반이 되는 다우이론(스윙 고/저점)과 오더블럭(OB)을 바로바로 잡아주기 때문에 주요 고/저점과 매물대 지지/저항 컨펌하는 용도로 활용하기 매우 유용합니다. 변동하는 가격의 흐름, 즉 추세를 파악하는 방법은 수만가지가 있습니다. 단 하나의 방법, 지표, 혹은 이론만 가지고 추세를 파악하는 건 당연히 바보 같은 짓이겠죠. 여러가지의 요소들을 복합적으로 봐야하는데 그 중에 가장 근본적이면서 중요한 게 바로 다우이론이라고 생각합니다. 이름만 거창하지 정말 별거 없습니다. 한문장으로 “전 고/저점에 비해서 이번에 나오는 고/저점이 높아졌냐 낮아졌냐”입니다. 다우 이론은 엘리엇 파동 이론 및 SR Flip 전략 등 대부분들의 기법들에 적용된 만큼 차트 보시려면 꼭 알아야 되는 개념입니다. 스윙이란 변곡이 나오기 전까지의 가격 흐름, 즉 하나의 파동이라고 생각하시면 되겠습니다. 주요 고/저점은 통상적으로 하나의 파동을 규명하기 위해 참고하는 기준들입니다. 고/저점 혹은 변곡점이 출현하고 나서 후행적으로 우리는 전 상승/하락 파동이었다고 인지를 합니다. 여기서 중요한 건 다음 파동이 전 파동보다 고/저점을 높였냐/낮추었냐입니다. 고/저점을 높여가는 파동이 나오면 상승, 낮추어가는 파동이 나오면 하락 추세에 가중을 더 두고, 고/저점을 높이다가 내리기 시작하면 혹은 내리다가 높이기 시작하면 추세가 어느정도 전환될 수 있는 시그널로 해석할 수 있습니다. OB(오더블럭) 기법은 요즘 장에 그나마 잘 먹히는 가격매물대를 찾는 방법론 중 하나입니다. 매물대란 다양한 시장참여자들에 따라 시시각각 해석될 수 있습니다. 기관(세력)들의 매집구간, 많은 참여자들의 평균 진입/청산/평단 가격 범위, 혹은 시체 쌓인 구간으로도 해석해볼 수 있습니다. 더 쉽게 설명해드리자면 거래량이 상대적으로 많은 가격 범위대라고 보시면 되겠습니다. 기술적분석 관점에서는 매물대를 주요 지지/저항구간대라고 고려하실 수 있으며 지지/저항을 실패하면, 그 실패한 방향으로 추세가 터질 가능성을 두고 전략 설계에 활용합니다. 매물대를 효과적으로 찾을 수 있는 팁 하나를 드리자면, 어느정도 명확하고 큰 추세가 나오기 전에 형성된 수평 평행 채널들을 먼저 의심해보세요. 만약에 해당 가격범위 내에 OB가 많이 내포되어 있다면 신빙성을 더 부여하실 수 있습니다. 이렇게 OB는 매물대를 식별하고 컨펌하는 용도로 매우 용이하게 활용될 수 있으며, 요즘에 유행하는 기법인 마스터패턴에도 찰떡궁합입니다. OB를 정의하는 여러가지 기법들 중 캔들봉을 활용한 방법이 그나마 가장 효과적이며 저희 개발팀은 장악형(Engulfing) 패턴이 두번 이상 출현하는 캔들봉들의 몸통들을 기준으로 OB를 찾는 로직을 지표화했습니다. 언급 드렸듯, 다우이론은 기술적 분석 기법 중 가장 근본적이면서도 동시에 실용도가 높아 차트 보시려면 무조건 숙지해야하는 개념 및 전략입니다. 또한 상대적으로 최근 시장에 효율적인 매물대 색출 전략 중 하나인 OB기법으로 주요 지지/저항으로 해석될 수 있는 메이저 매물대들의 가격 범위를 더 세분화시킬 수 있습니다. 저희 SOB 지표는 주요 고점, 저점, 그리고 OB들을 자동으로 피봇으로 잡아줄뿐더러 주요 고/저점이 뚫렸을 때, 해당 피봇의 색깔들이 변경됩니다. SR Flip (저항선이 뚫리면 지지선, 지지선이 뚫리면 저항선)개념 및 전략을 자주 활용하시는 트레이더분들은 고/저점 뚫릴 때, 즉 더 높은/낮은 고/저점이 출현하고 나서 전 고/저점을 활용해 리테스트 진입 자리 찾으실 때 유용하게 사용하실 수 있습니다. 저희 SOB_Version1.0.2 지표를 사용하고 싶으신 분들은 댓글, DM, 또는 저희 개인 채널에 문의 주십시오. 차트와 캔들 위에서만큼은 우리 SOB이 여러분들을 실망시키지 않을 것입니다. 감사합니다. 성투하세요.
Pineスクリプト™ インジケーター
Tommy_Traderの投稿
111