You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is because sometimes the two latest values are extremely close to one another. Not sure if best fixed in front end (looka at more than one interval? Use a minimum interval?) or the back end (enforce a certain interval byt waiting to update a minimum ammount of time regardless of parent streams?).
The text was updated successfully, but these errors were encountered:
I mean, isn't this really a back-end issue? at least partly... I can space out the predictions nicely but they won't be accurate anyway if the algorithm is expecting evenly spaced inputs...
I marked this as wontfix, because it should probably be fixed in the backend. Another good reason for this is that an uneven interval gives a lower quality on predictions.
This is because sometimes the two latest values are extremely close to one another. Not sure if best fixed in front end (looka at more than one interval? Use a minimum interval?) or the back end (enforce a certain interval byt waiting to update a minimum ammount of time regardless of parent streams?).
The text was updated successfully, but these errors were encountered: