Skip to content
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

address upscroll wonkiness on beeswarm #215

Closed
cnell-usgs opened this issue Mar 17, 2021 · 1 comment · Fixed by #257
Closed

address upscroll wonkiness on beeswarm #215

cnell-usgs opened this issue Mar 17, 2021 · 1 comment · Fixed by #257

Comments

@cnell-usgs
Copy link
Member

On mobile, the upscroll for the beeswarm gets off in the transition between the 100% training ANN data and the RMSE dot that moves around. The links from the error chart appear early (step_rmse+3) when they shouldn't be seen until step_error_obs, and may have their own strength that's counteracting forceCollide? It's possible this is simply due to a step numbering issue on mobile, where the forces are changing out of sync with the data in view.

@cnell-usgs cnell-usgs self-assigned this Mar 17, 2021
@cnell-usgs
Copy link
Member Author

cnell-usgs commented Mar 17, 2021

In general, on upscroll, forces and other attribute transitions should be linked to this.active.step-1 due to the way events are triggered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants