Bug with indicators called by Signal using additional BarsOfData - [CLOSED] MC-2206

#1

MultiCharts Support
Last seen online at Apr 17, 2024 - 12:37
Show user details

Mar 29, 2017 - 16:14

The reason of that behavior is that you do not have the same starting calculation point for the studies. Please set up identical MaxBarsBack for the indicators and the calculation results will be the same.

#2

saltminer (saltminerbugreporter)

saltminerbugreporter
Last seen online at May 12, 2017 - 03:57
Show user details

Mar 29, 2017 - 19:34

Thanks, but your answer doesn't make sense nor changes any result.
I set the MaxBarsBack of the Signal and the two chart indicators to 50, and got identical incorrect results.
Perhaps you have not actually looked at my coded example.

It is simple.

protected override void Create()
{
// create variable objects, function objects, order objects etc.
slopeIndicatorChart = (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),1);
slopeIndicator2 = (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),2);
}
protected override void StartCalc()
{
// assign inputs
slopeIndicatorChart.length = length;
slopeIndicatorChart.displace = displace;
slopeIndicatorChart.lookback = lookback;

        slopeIndicator2.length = length;
        slopeIndicator2.displace = displace;
        slopeIndicator2.lookback = lookback;

    }
    protected override void CalcBar()
    {
        Output.WriteLine(Bars.TimeValue+" Chart Slope "+slopeIndicatorChart.Plots[0].Values[0]+", 2nd Panel "+BarsOfData(2).TimeValue+" Slope "+slopeIndicator2.Plots[0].Values[0]);
    }

With this output I can check the values on the chart indicators visually against the values the Signal
receives from identically configured indicators it is accessing.
The indicator calculating on BarsOfData(2) is incorrect.

PLEASE REVISIT THIS ISSUE.

Edit comment #2

Comment visibility (whether to hide this comment for "regular users")

Comment

Selected syntax: Markdown ▼

Thanks, but your answer doesn't make sense nor changes any result. 
I set the MaxBarsBack of the Signal and the two chart indicators to 50, and got identical incorrect results. 
Perhaps you have not actually looked at my coded example.

It is simple.

protected override void Create() 
		{
			// create variable objects, function objects, order objects etc.
			slopeIndicatorChart = (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),1);
			slopeIndicator2 = (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),2);
		}
		protected override void StartCalc() 
		{
			// assign inputs 
			slopeIndicatorChart.length = length;
			slopeIndicatorChart.displace = displace;
			slopeIndicatorChart.lookback = lookback;
			
			slopeIndicator2.length = length;
			slopeIndicator2.displace = displace;
			slopeIndicator2.lookback = lookback;
			
		}
		protected override void CalcBar()
		{
			Output.WriteLine(Bars.TimeValue+" Chart Slope "+slopeIndicatorChart.Plots[0].Values[0]+", 2nd Panel "+BarsOfData(2).TimeValue+" Slope "+slopeIndicator2.Plots[0].Values[0]);
		}

With this output I can check the values on the chart indicators visually against the values the Signal 
receives from identically configured indicators it is accessing. 
The indicator calculating on BarsOfData(2) is incorrect.

PLEASE REVISIT THIS ISSUE.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

If you want to add text that is not supposed to be parsed, put it inside tags, or start the line with a space.
See more formatting tips in WikiFormatting.

or cancel

Reply to comment #2

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Markdown ▼

'''saltminer wrote:'''
>Thanks, but your answer doesn't make sense nor changes any result. 
> I set the MaxBarsBack of the Signal and the two chart indicators to 50, and
> got identical incorrect results. 
> Perhaps you have not actually looked at my coded example.
> 
> It is simple.
> 
> protected override void Create() 
> 		{
> 			// create variable objects, function objects, order objects etc.
> 			slopeIndicatorChart =
> (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),1);
> 			slopeIndicator2 =
> (Indicator.Mov_Avg_Slope)AddIndicator(typeof(Indicator.Mov_Avg_Slope),2);
> 		}
> 		protected override void StartCalc() 
> 		{
> 			// assign inputs 
> 			slopeIndicatorChart.length = length;
> 			slopeIndicatorChart.displace = displace;
> 			slopeIndicatorChart.lookback = lookback;
> 			
> 			slopeIndicator2.length = length;
> 			slopeIndicator2.displace = displace;
> 			slopeIndicator2.lookback = lookback;
> 			
> 		}
> 		protected override void CalcBar()
> 		{
> 			Output.WriteLine(Bars.TimeValue+" Chart Slope
> "+slopeIndicatorChart.Plots[0].Values[0]+", 2nd Panel
> "+BarsOfData(2).TimeValue+" Slope "+slopeIndicator2.Plots[0].Values[0]);
> 		}
> 
> With this output I can check the values on the chart indicators visually
> against the values the Signal 
> receives from identically configured indicators it is accessing. 
> The indicator calculating on BarsOfData(2) is incorrect. 
> 
> PLEASE REVISIT THIS ISSUE.

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

If you want to put a horizontal line in the document, use four dashes: "----".
See more formatting tips in WikiFormatting.

or cancel

#3

MultiCharts Support (MultiCharts)

MultiCharts Support
Last seen online at Apr 17, 2024 - 12:37
Show user details

Mar 30, 2017 - 13:08

We have tested it on our end and it is working fine. Please set the identical starting calculation point, so that the first calculation bar for studies matched. It can be achieved by modifying MaxBarsBack of the studies.

#4

saltminer (saltminerbugreporter)

saltminerbugreporter
Last seen online at May 12, 2017 - 03:57
Show user details

Mar 31, 00:22, in reply to comment #3

Hi Alex, I'm afraid that for me, setting both bars series to 999 bars back, and with MaxBarsBack of the Signal and both indicators set to 50, I still get incorrect results. This 'solution' makes no sense to me anyway, mucking about with start times, because the calculation in question is a simple piece of arithmetic comparing a value now with a value 12 bars ago, of a simple moving average. The start time of this hundreds of bars ago is irrelevant. Please give me an email address so I can send you a screencap of what I'm talking about. By the way, I am a professional trading software developer so I'm not a complete dummy. Thanks, saltminer

Alex MultiCharts wrote:

We have tested it on our end and it is working fine. Please set the
identical starting calculation point, so that the first calculation bar for
studies matched. It can be achieved by modifying MaxBarsBack of the
studies.

Edit comment #4

Comment visibility (whether to hide this comment for "regular users")

Comment

Selected syntax: Mediawiki ▼

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

If you want to add text that is not supposed to be parsed, put it inside tags, or start the line with a space.
See more formatting tips in WikiFormatting.

or cancel

Reply to comment #4

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Mediawiki ▼

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

URLs will be automatically transformed to links. If you want to add a title, use the link formatter: [[http://awesome.com/something An awesome link]].
See more formatting tips in WikiFormatting.

or cancel

#5

MultiCharts Support (MultiCharts)

MultiCharts Support
Last seen online at Apr 17, 2024 - 12:37
Show user details

Mar 31, 2017 - 13:17

What you did is not exactly what I mentioned in the above comment. It is not saying that you need to set the identical MaxBarsBack, it says that you need to set identical starting calculation point, and that is a different thing from my first comment.

#6

saltminer (saltminerbugreporter)

saltminerbugreporter
Last seen online at May 12, 2017 - 03:57
Show user details

Apr 01, 00:43, in reply to comment #5

Hi Alex, Yes, I have tried setting both of the bars series to the same start date and time. I have tried setting them both to BarsBack = 999. It makes no difference, and nor should it, since neither the start time nor MaxBarsBack has anything to do at all with this problem. An indicator with a MaxBarsBack of 50 should be easily able to reference a value only 12 bars ago. And, a simple moving average is not affected by its start time, and since we are using Minute bars, there is no variability of what the bars could be from a start time such as there could be on Tick or Volume or Range charts. So I am just not seeing any relevance of these instructions. The problem, as I experience it, is that an indicator hosted by a strategy on an additional timeframe cannot correctlyreference back x bars. It looks like it does "Chart Bars of x" not "its own bars of x". I have sent an email attention to you at the support email, with a screenshot clearly showing the problem.

Alex MultiCharts wrote:

What you did is not exactly what I mentioned in the above comment. It is
not saying that you need to set the identical MaxBarsBack, it says that you
need to set identical starting calculation point, and that is a different
thing from my first comment.

Edit comment #6

Comment visibility (whether to hide this comment for "regular users")

Comment

Selected syntax: Mediawiki ▼

Hi Alex,
Yes, I have tried setting both of the bars series to the same start date and time. I have tried setting them both to BarsBack = 999.
It makes no difference, and nor should it, since neither the start time nor MaxBarsBack has anything to do at all with this problem. An indicator with a MaxBarsBack of 50 should be easily able to reference a value only 12 bars ago. And, a simple moving average is not affected by its start time, and since we are using Minute bars, there is no variability of what the bars could be from a start time such as there could be on Tick or Volume or Range charts.
So I am just not seeing any relevance of these instructions. The problem, as I experience it, is that an indicator hosted by a strategy on an additional timeframe cannot correctlyreference  back x bars. It looks like it does "Chart Bars of x" not "its own bars of x". 
I have sent an email attention to you at the support email, with a screenshot clearly showing the problem.

'''Alex MultiCharts wrote:'''
>What you did is not exactly what I mentioned in the above comment. It is
> not saying that you need to set the identical MaxBarsBack, it says that you
> need to set identical starting calculation point, and that is a different
> thing from my first comment.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in WikiFormatting.

or cancel

Reply to comment #6

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Mediawiki ▼

'''saltminer wrote:'''
>Hi Alex,
> Yes, I have tried setting both of the bars series to the same start date
> and time. I have tried setting them both to BarsBack = 999.
> It makes no difference, and nor should it, since neither the start time nor
> MaxBarsBack has anything to do at all with this problem. An indicator with
> a MaxBarsBack of 50 should be easily able to reference a value only 12 bars
> ago. And, a simple moving average is not affected by its start time, and
> since we are using Minute bars, there is no variability of what the bars
> could be from a start time such as there could be on Tick or Volume or
> Range charts.
> So I am just not seeing any relevance of these instructions. The problem,
> as I experience it, is that an indicator hosted by a strategy on an
> additional timeframe cannot correctlyreference  back x bars. It looks like
> it does "Chart Bars of x" not "its own bars of x". 
> I have sent an email attention to you at the support email, with a
> screenshot clearly showing the problem.
> 
> '''Alex MultiCharts wrote:'''
> >What you did is not exactly what I mentioned in the above comment. It is
> > not saying that you need to set the identical MaxBarsBack, it says that
> you
> > need to set identical starting calculation point, and that is a different
> > thing from my first comment.
>

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in WikiFormatting.

or cancel