Skip to content

doubles sometimes treated as categories when importing from GraphML #288

@brucemcpherson

Description

@brucemcpherson
  • gephi v1.02
  • macos
  • chrome v142

I have a graphml file, which has a section describing the keys = for example

  <key id="V-depression_post" for="node" attr.name="depression_post" attr.type="double"/>
  <key id="V-depression_pre" for="node" attr.name="depression_pre" attr.type="double"/>

and example values

      <data key="V-depression_post">12</data>
      <data key="V-depression_pre">12</data>
      <data key="V-depression_post">0</data>
      <data key="V-depression_pre">27</data>

When imported they are treated sometimes as categories, and sometimes as numbers

Image

At first I thought perhaps missing values would cause them to be treated as numbers rather than categories, but I have other examples where there are no missing values.

  <key id="V-out_degree_change" for="node" attr.name="out_degree_change" attr.type="double"/>
  <key id="V-out_degree_post" for="node" attr.name="out_degree_post" attr.type="double"/>
  <key id="V-out_degree_pre" for="node" attr.name="out_degree_pre" attr.type="double"/>
      <data key="V-out_degree_change">-2</data>
      <data key="V-out_degree_post">2</data>
      <data key="V-out_degree_pre">4</data>
Image

How is it deciding what is a category and what is number ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions