Webinterface negative graph not in view

[volkszaehler]

Webinterface negative graph not in view

[andig]

What is the problem? Noneof your channels should have negative values?

[milefork]

The Problem is that it will not be displayed.

It should be look like this: http://puu.sh/c4LrT/c5859c25bf.png
But on the first picture the green line is in nowhere.

I can only get if i uncheck the green and recheck it then I'll see the Graph correct. But if it refreshs or something the green goes away again.

Hope you'll understand my explanation otherwise I think we could talk in german ;)

[jahir]

I think this is kind of a race condition:
In htdocs/frontend/javascripts/wui.js line 443 ymin is set to 0, but Entity.prototype.updateAxisScale in entity.js sets it to null (i.e. autoscaling) if the min value of the entity data is below zero. But when Entity.prototype.updateAxisScale is called after that (for the next entity), yaxis.min will be set to null again. This explains why it works for you when you disable the entity with negative values and enable it again.
I guess we have to store in a separate property the min value of all channels or that yaxis.min was already set (and clear this flag when loading new data, maybe vz.wui.zoom could be a good place for that).

As a workaround, you could comment this code in Entity.prototype.updateAxisScale:

                if (vz.options.plot.yaxes[this.assignedYaxis-1].min === null) {
                        // avoid overriding user-defined options
                        vz.options.plot.yaxes[this.assignedYaxis-1].min = 0;
                }

[andig]

Good catch. I'll look into this when I find the time....

Am 09.10.2014 um 18:23 schrieb jahir [email protected]:

I think this is kind of a race condition:
In htdocs/frontend/javascripts/wui.js line 443 ymin is set to 0, but Entity.prototype.updateAxisScale in entity.js sets it to null (i.e. autoscaling) if the min value of the entity data is below zero. But when Entity.prototype.updateAxisScale is called after that (for the next entity), yaxis.min will be set to null again. This explains why it works for you when you disable the entity with negative values and enable it again.
I guess we have to store in a separate property the min value of all channels or that yaxis.min was already set (and clear this flag when loading new data, maybe vz.wui.zoom could be a good place for that).

—
Reply to this email directly or view it on GitHub.

[milefork]

@jahir commenting this out helps as a short fix thx.

[rhartmannh]

The code to comment out is no longer in the source file. Obviously something has been changed. However, the error still exists. Is there another workaround?

[dervitti]

@rhartmannh I have (had) the same problem. You have to edit your /www/volkszaehler.org/htdocs/frontend/javascripts/entity.js to comment the lines. It´s in the part "Set axis minimum depending on data".

[rhartmannh]

Thanks. That helped.

On Jan 18, 2015, 4:04 PM, at 4:04 PM, Sebastian [email protected] wrote:

@rhartmannh I have (had) the same problem. You have to edit your
/www/volkszaehler.org/htdocs/frontend/javascripts/entity.js to comment
the lines. It´s in the part "Set axis minimum depending on data".

---

Reply to this email directly or view it on GitHub:
#185 (comment)

[andig]

@ALL: can you confirm that this problem only exists when channels with negative and non-negative values are mapped to the same axis?

[milefork]

yes, i can confirm that.