weird behaviour with scale object/incoming data
I am getting out-of-bound results when using the scale object. I take data from the net and they have to be scaled but for some reason the result is out of the limits. I am copying here the scale part (the whole patch is for too big and requires installing some Java objects)
When doing a forced update of the data (a forced bang). I get a good result. Something weird happening?
----------begin_max5_patcher---------- 580.3oc0V9zaaBCFF+L7ovxZGYHr4ew61tsCUZ6vtLMMUY.mDW4XPFmzzU0u 6yXfF5TZCgkv1jBD7K1u448Gu7D+nqCLqbOqFB9.36.GmGccbrgZB3zM1Atg tOWPqsSCtTTJ2tA50dKykka0Bl1dSbWzJpNeMWt5VEKW2lbDdgefG.GgZ9JN vNvbF7it0zlF8CUr1Ez7CQ0PO.LiJWAedd7BqLJyt68jdUrrTpkzM1UB+nhS EvmUhxDWyT2xjzLgcFACVUM+m1XHrevgRhK6qHTSrmbcaN4MRBksUqKkGmPn 2fPIVzfvo8r4TD5UASB7RUKR18lD1mNMauUrPipY7cLv2XT0Mk2e10ZHx1MD 0Pc.YwoK0iVlnEgmtCXLOkCtNj4S7UqOazD09juCMjIilz+YQyMzZ8WUzB1W T7b1mkhGN+2UvC5ePwISjRI+EgzD8Q6ZOHg9IHBgD6ARi7SvADD5O2PEeAMT Q9wjXSa3QchNDrfky2PEUBZN6R6RUmSELv6VhLGXPfu4iAYjo1sgRSaMnmpe ElDcl8auEDSlultN65qTSGI7+z1tIRSb.xGsfDGEe8P5r8l7.rYUBTvk+9FJ sLnI9KYYc4VUdeQ0aGCNT3ErZMWR0byloNLIasMXVq4EEL4PwWvqapmhW2Yd rBxtAiQnnvYTQihQyldvihOFaO.ddzCYLJJY93CIbzDBMSJJZDJhLiDZ78PS QQstRzppcLUcWRshw3keWox9Ood1gbY6PaFM6VcGue9QtMY6I2eAyWogd. -----------end_max5_patcher-----------
you’re setting a high and a low. If you’re getting data that’s outside the bounds that means the price hits a year low or a year high, right?
What I’d do is feed it through, compare it to the year high and year low, and then update this before scaling – that way it will adjust properly.
Alternatively, just clip using zmap instead of scale?
It seems that when I update the data, the dayprice comes in but the yearlow and yearhigh are delayed. As such, the dayprice is compared to the wring limites and gets out of bounds. I have tested with the pack object to see how fast the data come in but they always come in late and hence I get wrong results. Using pipe I cannot solve this so as it seems. Any suggestions?