You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just had a case where I am trying to create a graph and noticed its representation was wrong given the list of nodes and edges given as inputs.
The reason turns out to be that my nodes used very long numbers as ID (int64 that were stored as strings in a database).
In my case I am using Python (Jupyter notebook), and I doubled checked that the IDs I use when I build my node list are actually stored as strings in Python.
However, it is probably the javascript code generated by Brunel that tries to convert those strings into integers (because in my case my IDs are only numbers).
JavaScript does not support 64 bits integers and thus the IDs were no longer correct, leading to wrong data representation.
A workaround in my case was just to prefix all my ID with "id_" which would prevent Javascript from trying to convert my strings IDs into integers.
The text was updated successfully, but these errors were encountered:
Hello,
I just had a case where I am trying to create a graph and noticed its representation was wrong given the list of nodes and edges given as inputs.
The reason turns out to be that my nodes used very long numbers as ID (int64 that were stored as strings in a database).
In my case I am using Python (Jupyter notebook), and I doubled checked that the IDs I use when I build my node list are actually stored as strings in Python.
However, it is probably the javascript code generated by Brunel that tries to convert those strings into integers (because in my case my IDs are only numbers).
JavaScript does not support 64 bits integers and thus the IDs were no longer correct, leading to wrong data representation.
A workaround in my case was just to prefix all my ID with "id_" which would prevent Javascript from trying to convert my strings IDs into integers.
The text was updated successfully, but these errors were encountered: