[Bug] Nighly 8.1.2 (2020-12-03) Perspective Power Chart Erronous Average

So, I was trying to add a powerchart. For testing purpose, I added a Status (value 0-6). In the stats at the bottom, I noticed that the average was actually higher than the maximum. See the screenshot.

1 Like

Hi Calimero

I thought this was maybe something to do with the Time weighted average calc, and the decided to add my own table with some aggregation methods as well. The min and max aggregation match but the average is way off?

This is in 8.1 not even on the nightly build.

I’m having a very similar issue. When I export the data & calculate averages through Excel, the numbers I get make a lot more sense & are no where near what Perspective is displaying. We’re currently running 8.1.0.

Note: as I watch my data right now, the average is actually continuing to climb despite already being well above maximum.

I’m running 8.1.0 and see the same bug.

The problem is for the method historian use to compress data specially when there is no change in tag and you set the history mode to OnChange.
In this mode history only log the change value of tag and in some cases there is small changes so there is not enough data for calculation of min max avg.
The main bug is for the interpolation doesn’t work for aggregation functions.
What I do most of the time I use system.tag.history and make it return enough point and interpolation is true.
Then loop through the result and calculate min max avg in python.

1 Like

Ok, the issue is really with the tag historian interpolation, even when it’s not needed. I have a value of SetSpeed, which is the actual speed the operator wants when the equipment is running. This value change once or twice a day. With the tag historian query, when not enough values, I seems to have an average of some sort, even when I select a different aggregation mode, LastValue being the aggregation mode I want

@nader.chinichian 2 questions:

  • Do you have a sample of what you do?
  • Do you have a query that replace tag historian query as in my case it messes with the data?

I don’t understand your first question.
Yes I have to use to get enough data with average aggregation mode and loop via dataset and cal want I want

Do you still use tag historian binding or you use a query binding?

Tag history with return value to 500 and interpolation is on and aggregation lastvalue or average.
Then loop through the result dataset by adding script transform.

I must be missing something here. Why doesn’t the average just work? I hope this is on IA’s radar to fix soon.

We are not sure about average work correctly or not .
People see number and if number is logical range they believe it is correct. But for min and max the value is totally can detect by naked eyes.

In my case, the average is outside min/max range, so obviously, it is not working as the average can’t be higher than the maximum

1 Like

Just got this.

Yes as told before for now it’s better to cal statical value yourself till this fix

Just FYI, it looks like the average that gets displayed when you use the Range Brush feature of the power chart is correct. It’s not an ideal workaround, but at least it’s something.

1 Like

FYI… This bug was fixed for the 8.1.2 release. It was merged later in the month of December, so it wouldn’t have been part of the nightly listed in the title if this post.

1 Like

Hi Jashua,
I also see this bug with system.tag.history function which give wrong value some times depend on points available in database. Will this fix include for system.tag functions or not?

Hi Nader, this fix was done only at the chart level (improper average calculation within the component). If you can provide a repeatable test of the issue you’re having with system.tag.history, I’ll open up a ticket for it.

The issue is still there in French, but works in English.

An issue with the Locale??