Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I've been trying to work with the following scan code. Unfortunately, there appears to be a 3 bar/candle delay built into the logic (see "hlc3[-3]" references)...
Given my limited thinkscripting abilities, I am able to grasp and understand certain basic aspects of the code. However, I am currently unable to make the necessary changes in order to draw the signal on the current or just completed bar/candle. Is it possible?
Thanks in advance for any assistance/guidance in this endeavor. It is certainly appreciated
Can you help answer these questions from other members on NexusFi?
The 3 candle plot delay comes from the text with the strikethrough, you can delete it or put a pound sign in front if you want to convert it to text to save it.
Unfortunately, the commenting out/removing of the "thirdBarClosed" variable and associated references did not affect the 3 bar/candle delay. I think the remaining bold/underlined hlc3[-3] code is also affecting the delay, not to mention the bold/underlined hlc3[-2] code that I think would create a 2 bar/candle delay if the hlc3[-3] code was removed...
Now that I'm looking more closely, it looks like the script is written to yield attractive historical results. Worthwhile signals 3 or 2 bars/candles ago are not very helpful now in a scan
Thank you for the swift response, rmejia Your assistance is certainly appreciated...
I tried the study as a regular study and it plots a dot (point) when triggered. With the "thirdbarClosed" it waits 2 candles after the signal is activated to draw the dot, without that it draws it after the signal is activated and the candle closes.
The trigger part of the script compares the previous candle [-1] to the 2 previous ones before it [-2] & [-3] and if it is higher or lower than either of those it triggers the signal.
Some studies like the TTM Scalper Alert plot signals with a couple of candle delays; don't know how to make use of that for real time trading.
Thanks for the follow-up and additional debugging, as well as providing a clear and concise explanation of the internal mechanics of the script, rmejia I really appreciate it...
I've gone back and tried the script as a regular study, with the "thirdBarClosed" variable and references removed, in order to visualize what you relayed in your last post. Unfortunately, I'm not seeing any signals being placed any earlier than the 3 bar/candle delay
I find it ironic that a script named "TTM Scalper Alert" incorporates delays. I would have thought a "Scalper" tool would be much more fast acting...