Comparing 2.8.8 chart with 3.2.2

[Phillip Weeks]

I am wondering why it is, when our meters reset to 0 on the 26th, the delta chart run on latest 3.2.2 shows a big negative number reflecting the delta change from 20k to 0 while the delta for the other chart does not show this negative value and therefor does NOT biasly skew the size of the columns? Is there a parameter set to ignore values below 0 in 2.8.8 Iam not aware of? The point definitions are identical. The first is run in 3.2.2 and the second is rum in 2.8.8
Can someone explain what is going on as it is the same code being run on both instances?? Thanks in advance. ;)

.

[JoelHaggar]

The delta calculation is just that so if your data rolls over to 0 then the negative value is a correct delta calculation. There has never been special handling for roll overs so I would check your raw data.

[Phillip Weeks]

so why are these two charts different? Same data. This is the data from 2.8.8 and does not show a negative delta in the chart above.

[Phillip Weeks]

Hi Joel, our issues with the bar charts not displaying at all and/or the graphs looking different with the previous charting version began when we moved to mango version 3. Is there a way to substitute/ revert to or otherwise incorporate the previous charting object from 2.8.8 back into v3.2.2 ? I love the designer and would never want to revert back to 2.8.8 just to get decent looking charts.

The chart renderings above showing a negative delta's and no negative delta, I really have no idea what is happening because the data is exactly the same as I demonstrate when I display first values under 2.8.8 and show the values drop to zero on the 26th yet no coinciding negative bar graph value is rendered using delta as does happen with the latest charting object so it's obvious the behavior of the latest charting object renders different than its predecessor. If we must live with the latest charting object version, we need to resolve rendering issues else we cannot produce professional client dashboards.

[Jared Wiltshire]

@Phillip-Weeks can you put a <pre ng-bind="pointValues | json"></pre> on each page so we can see the actual content of the point values (post the content up here). This will verify if the values coming back are different or if the charting component behavior changed.

[Phillip Weeks]

@jared-wiltshire said in Comparing 2.8.8 chart with 3.2.2:
This code was cut and paste into the v3 designer page in the next post.

[Phillip Weeks]

This is with version v3. This is a delta chart..

[Jared Wiltshire]

Can you post the JSON, not pictures please.

[Phillip Weeks]

Data From 2.8.8:

[
  {
    "value": -9399.5,
    "timestamp": 1514174400000,
    "annotation": null
  },
  {
    "value": 80.5,
    "timestamp": 1514260800000,
    "annotation": null
  },
  {
    "value": 66,
    "timestamp": 1514347200000,
    "annotation": null
  },
  {
    "value": 37,
    "timestamp": 1514433600000,
    "annotation": null
  },
  {
    "value": 0,
    "timestamp": 1514520000000,
    "annotation": null
  }
]
[
  {
    "value": -20117,
    "timestamp": 1514174400000,
    "annotation": null
  },
  {
    "value": 231,
    "timestamp": 1514260800000,
    "annotation": null
  },
  {
    "value": 180.5,
    "timestamp": 1514347200000,
    "annotation": null
  },
  {
    "value": 133.5,
    "timestamp": 1514433600000,
    "annotation": null
  },
  {
    "value": 0,
    "timestamp": 1514520000000,
    "annotation": null
  }
]

Data from 3.2.2:

[
  {
    "annotation": null,
    "value": -9399.5,
    "timestamp": 1514174400000,
    "rendered": "-9399.5"
  },
  {
    "annotation": null,
    "value": 80.5,
    "timestamp": 1514260800000,
    "rendered": "80.5"
  },
  {
    "annotation": null,
    "value": 66,
    "timestamp": 1514347200000,
    "rendered": "66"
  },
  {
    "annotation": null,
    "value": 37,
    "timestamp": 1514433600000,
    "rendered": "37"
  },
  {
    "annotation": null,
    "value": 15.5,
    "timestamp": 1514520000000,
    "rendered": "15.5"
  }
]
[
  {
    "annotation": null,
    "value": -20116,
    "timestamp": 1514174400000,
    "rendered": "-20116"
  },
  {
    "annotation": null,
    "value": 231,
    "timestamp": 1514260800000,
    "rendered": "231"
  },
  {
    "annotation": null,
    "value": 180.5,
    "timestamp": 1514347200000,
    "rendered": "180.5"
  },
  {
    "annotation": null,
    "value": 133.5,
    "timestamp": 1514433600000,
    "rendered": "133.5"
  },
  {
    "annotation": null,
    "value": 67.5,
    "timestamp": 1514520000000,
    "rendered": "67.5"
  }
]

[Phillip Weeks]

So Jared, any info on what is going on here?

[Jared Wiltshire]

@Phillip-Weeks not exactly. It seems that yes maybe something did change (either in our serial chart component or in the amCharts library) which affects how it draws the graph. As far as I can see though it is charting the values correctly in v3.2 as the JSON does indeed contain negative values.

If this is not what you desire I suggest that you try playing with the amCharts options for the valueaxis, try setting minimum: 0, strictMinMax: true.

So

<ma-serial-chart ... options="{valueAxes: [{minimum: 0, strictMinMax: true}]}"></ma-serial-chart>