Also, I found a thread on this for the NT7 version. I am not a programmer, so would need your assistance here. Lets fix it as this indicator opens interesting trading possibilities. Here is the NT7 solution:
Announcement
Collapse
Looking for a User App or Add-On built by the NinjaTrader community?
Visit NinjaTrader EcoSystem and our free User App Share!
Have a question for the NinjaScript developer community? Open a new thread in our NinjaScript File Sharing Discussion Forum!
Have a question for the NinjaScript developer community? Open a new thread in our NinjaScript File Sharing Discussion Forum!
See more
See less
Partner 728x90
Collapse
NinjaTrader
NT7 Swing Indicator Returning Different Values with COBC=false
Collapse
X
-
Yes, ok, but what is the expected timeline for this? Do you think you can provide a version for real time processing within a week, a month or are we talking abt longer period?
Also, I found a thread on this for the NT7 version. I am not a programmer, so would need your assistance here. Lets fix it as this indicator opens interesting trading possibilities. Here is the NT7 solution:
Last edited by eddi0505; 06-03-2018, 01:07 PM.
-
Hello eddi0505,
Thank you for your response.
There is no expected timeline for this.
You are going to need to explain your longer time frame question further. Are you referring to the bar type or the days to load?
The thread you linked does not explain the matter nor resolve it for NinjaTrader.
I will follow up here when I have more details.
Comment
-
Hi, here is the solution which was used in NT7 in order to amek Swing indicator work properly in real time processing. How to amend the NT8 Swing indicator to make it work under real time processing?
"
Hi Chelsea,
I have inserted those statements at line 175 of the original Swing indicator. So it looks like this
Code:
if (saveCurrentBar != CurrentBar)
{
// bunch of code
}
else
{
// update the caches
if (High[0] > (double) lastHighCache[lastHighCache.Count - 1])
lastHighCache[lastHighCache.Count - 1] = High[0];
if (Low[0] < (double) lastLowCache[lastLowCache.Count - 1])
lastLowCache[lastLowCache.Count - 1] = Low[0];
if (High[0] > High[strength] && swingHighSwings[strength] > 0.0)
{
swingHighSwings.Set(strength, 0.0);
for (int i=0; i<=strength; i++)
SwingHighPlot.Reset(i);
currentSwingHigh = 0.0;
}
.... continue with rest of code.....
}
You should see the difference when you run it with COBC = false. Previously the indicator would plot the dots incorrectly using the value first stored in the cache, which was essentially the Open of the bar, rather than the high/low, so the dots would 'cut across' the bar.
Hope this helps.
"
Comment
-
Hello eddi0505,
Thank you for your post.
Currently the Swing is considered working as it is waiting for the strength on either side and the the close of the bar for confirmation.
However, I am in fact still working on the indicator working with calculation on tick and price change. Anomalies are still seen when adjusting the code for calculations on tick and price change. Therefore debugging and testing has continued.
What do you mean "Min 2 weeks"?
I look forward to your response.
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by andrewtrades, Today, 04:57 PM
|
1 response
5 views
0 likes
|
Last Post Today, 05:02 PM | ||
Started by chbruno, Today, 04:10 PM
|
0 responses
3 views
0 likes
|
Last Post
by chbruno
Today, 04:10 PM
|
||
Started by josh18955, 03-25-2023, 11:16 AM
|
6 responses
436 views
0 likes
|
Last Post
by Delerium
Today, 03:42 PM
|
||
Started by FAQtrader, Today, 03:35 PM
|
0 responses
7 views
0 likes
|
Last Post
by FAQtrader
Today, 03:35 PM
|
||
Started by rocketman7, Today, 09:41 AM
|
5 responses
19 views
0 likes
|
Last Post Today, 03:33 PM |
Comment