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

Uninformative error when creating Chord diagram #2581

Closed
gmontamat opened this Issue Apr 19, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@gmontamat

gmontamat commented Apr 19, 2018

I was trying to create a Chord diagram based on https://github.com/ioam/holoviews/blob/master/examples/gallery/demos/bokeh/route_chord.ipynb
I assumed it should work on my dataframes since they were very similar to the ones in the examples. I got the error:

ValueError: None of the available storage backends were able to support the supplied data format.

The actual issue was that I had loop edges (connecting nodes to themselves) which doesn't happen on the sample airport routes dataset. Removing those loops fixed the issue but a more clear error message would have saved me a couple hours.

@philippjfr

This comment has been minimized.

Member

philippjfr commented Apr 19, 2018

Thanks for filing this issue, that would indeed be helpful. It's not quite clear to me why loop edges shouldn't be supported so this might in fact be a bug but for now I've labeled the issue as an enhancement request.

@philippjfr

This comment has been minimized.

Member

philippjfr commented Apr 19, 2018

Would you happen to have a small example to reproduce this?

@philippjfr

This comment has been minimized.

Member

philippjfr commented Apr 19, 2018

Nevermind, this is sufficient:

hv.Chord([('A', 'B', 2), ('B', 'A', 3), ('A', 'A', 2)])
@gmontamat

This comment has been minimized.

gmontamat commented Apr 19, 2018

Is it possible to support loop edges in these charts? It would be nice to have them like on this plotly example.

@philippjfr

This comment has been minimized.

Member

philippjfr commented Apr 19, 2018

@gmontamat It will be once the PR above is merged.

@gmontamat

This comment has been minimized.

gmontamat commented Apr 19, 2018

@philippjfr great news! Thanks.

@philippjfr philippjfr added this to the v1.10.2 milestone Apr 24, 2018

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