irelephant [he/him]@programming.devM to Software Gore@programming.devEnglish · 9 days agoGraphing errorprogramming.devimagemessage-square19linkfedilinkarrow-up1150arrow-down12
arrow-up1148arrow-down1imageGraphing errorprogramming.devirelephant [he/him]@programming.devM to Software Gore@programming.devEnglish · 9 days agomessage-square19linkfedilink
minus-squarelemmyhavesome@lemmy.worldlinkfedilinkarrow-up7·8 days agoI’m trying to think of a bug that could cause this, but can’t come up with anything.
minus-squareemeralddawn45@discuss.tchncs.delinkfedilinkarrow-up6·8 days agoIts not a bug its a penguin. Seriously though someone probably mixed up x and y axis in some variable calculation when draeing to the screen.
minus-squareirelephant [he/him]@programming.devOPMlinkfedilinkarrow-up6·8 days agoI think its safest to assume time travel.
minus-squareArtyom@lemm.eelinkfedilinkarrow-up3·8 days agoSuper weird, yeah. Both the upper and lower ends have some slope, so it’s not just “ghost points”. Thr points are connected in a contour, so the data really is going back in time, then reaching new values. It gets weirder the more I try to solve it.
I’m trying to think of a bug that could cause this, but can’t come up with anything.
Its not a bug its a penguin. Seriously though someone probably mixed up x and y axis in some variable calculation when draeing to the screen.
I think its safest to assume time travel.
Super weird, yeah. Both the upper and lower ends have some slope, so it’s not just “ghost points”. Thr points are connected in a contour, so the data really is going back in time, then reaching new values.
It gets weirder the more I try to solve it.