irelephant [he/him]@programming.devM to Software Gore@programming.devEnglish · 4 days agoGraphing errorprogramming.devimagemessage-square19fedilinkarrow-up1144arrow-down11
arrow-up1143arrow-down1imageGraphing errorprogramming.devirelephant [he/him]@programming.devM to Software Gore@programming.devEnglish · 4 days agomessage-square19fedilink
minus-squarelemmyhavesome@lemmy.worldlinkfedilinkarrow-up6·3 days agoI’m trying to think of a bug that could cause this, but can’t come up with anything.
minus-squareirelephant [he/him]@programming.devOPMlinkfedilinkarrow-up5·2 days agoI think its safest to assume time travel.
minus-squareemeralddawn45@discuss.tchncs.delinkfedilinkarrow-up5·3 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-squareArtyom@lemm.eelinkfedilinkarrow-up2·2 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.
I think its safest to assume time travel.
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.
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.