-
Notifications
You must be signed in to change notification settings - Fork 641
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
Greater control in downsampling used in plots #1266
Comments
Thanks for suggesting @tensorpro. Sounds like this becomes an issue where a run of interest contains significantly less data points than the others. If one were to naively adjust the sampling to match the run with the smallest number of points, this could incur an unnecessary load as significantly more data points would be retrieved from the other runs. Perhaps a better approach for this use case could be to equalize the x-axis range so that only the points being compared would be retrieved (and as a result, the same sampling would be applied)? |
That sounds like a good approach 😃 I might be able to help add this functionality with a PR if this feature seems like it would be merged. |
Proposal Summary
Allow more granular controls over how data is downsampled when its plotted.
Motivation
Currently, when we compare a run in progress to a completed run, the smoothing is inconsistently applied.
Since both the run in progress and previous run are downsampled to ~5000 steps, the completed run appears much smoother than a run in progress. This prevents the plots from being useful for comparing partially completed runs
Related Discussion
If this continues a slack thread, please provide a link to the original slack thread.
The text was updated successfully, but these errors were encountered: