New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeline sparkline bug #615
Comments
This is caused by any dynamic statistic that takes a window > step. For example 9.66 to 10.66 then 10.16 to 11.16 Maybe we can add validation so the user can't input a step lower than the window. |
No, this is intentional: this is how sliding windows work, and they are very useful. An acceptable solution is to rebuild intervals so that they are reduced. In your example, 9.66 to 10.16 then 10.16 to 11.16. Another example: Computed intervals are on 0 to 2, 1 to 3, 2 to 4, 3 to 5. Then they are rebuilt as: But this is a bad example, we should consider the dynamic metrics as follows. Each value is computed from a starting point to a starting point + size of the window. Then we add the tick to the starting point, and compute a new value. So the sparkline should draw this value at each starting point until the new starting point. Is it clearer? You may refer to the image embedded in Gephi dynamic metrics, icon help (i). |
Eduardo, can you provide guidance to help me fix this bug? However if it touches to Gephi architecture I must let you do it. |
Hi, My idea is: Here is the necessary code if that matches your idea https://gist.github.com/2705818 Tested it seems to work fine. |
So simple once you know the answer :) Thanks @eduramiba! |
Way to reproduce:
Screenshot: http://imageshack.us/photo/my-images/443/timelinebug.png/
The text was updated successfully, but these errors were encountered: