Thanks to visit codestin.com
Credit goes to github.com

Skip to content

missing data should be skipped in parcoords #4341

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

Open
archmoj opened this issue Nov 8, 2019 · 4 comments
Open

missing data should be skipped in parcoords #4341

archmoj opened this issue Nov 8, 2019 · 4 comments
Labels
bug something broken P3 backlog

Comments

@archmoj
Copy link
Contributor

archmoj commented Nov 8, 2019

Reported in https://community.plot.ly/t/plotly-graph-objects-parcoords-nan-replaced-by-0/29725
If some of the columns contain nan during the display of plotly.graph_objects.Parcoords the data are displayed as 0, it will be nice to don’t to treat the value as a nan and not as 0.

demo

@etpinard
Copy link
Contributor

I'm not sure about this. I think we should still draw the dimension axis and simply not draw the line.

@alexcjohnson
Copy link
Collaborator

Agreed - the ideal behavior would be to just remove the line segments to and from the nan value, but continue to show other segments of the same object.

@archmoj
Copy link
Contributor Author

archmoj commented Nov 19, 2019

What would happen with selection then?

@alexcjohnson
Copy link
Collaborator

I'd say if the dimension with nan has any constraint on it at all, this object should be filtered out, but if it's unconstrained then this object should remain selected.

@gvwilson gvwilson changed the title Should skip missing data in parcoords missing data should be skipped in parcoords Aug 9, 2024
@gvwilson gvwilson added the P3 backlog label Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken P3 backlog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants