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

Import CSV error edges #1848

Closed
jorgaf opened this issue Nov 17, 2017 · 6 comments
Closed

Import CSV error edges #1848

jorgaf opened this issue Nov 17, 2017 · 6 comments

Comments

@jorgaf
Copy link

jorgaf commented Nov 17, 2017

Expected Behavior

Import a CSV file and get 176 nodes and 246 edges.

Current Behavior

I get 176 nodes, but only 225 edges.

Possible Solution

Review import spread sheets.

Steps to Reproduce

  1. In Gephi 0.9.1 and 0.9.2 import attachment CSV file like as edge table
  2. In version 0.91 you will get 176 nodes and 246 edge, but in 0.9.2 you will get 176 and 225 edges.

Context

Your Environment

  • Version used: Gephi 0.9.2 201709242018
  • Java version: 1.8.0_144; Java HotSpot(TM) 64-Bit Server VM 25.144-b01
  • Operating System: Mac OS X versión 10.13.1 que se ejecuta en x86_64; UTF-8; es_ES (gephi)
@eduramiba
Copy link
Member

Can you attach the file? What edge merge strategy do you choose during import report? Do you get any warning in the report?

@jorgaf
Copy link
Author

jorgaf commented Nov 17, 2017

The file. The strategy was sum and I did not get any warning, the message was about merge strategy.
I am doing some test. I am not sure, but the problem is when the file is something like this:
Source,Target
loja,postalecu911
postalecu911,loja

The report show me nodes: 2 and edges: 2. If I select undirected graph, it has not edge, but if I choose directed graph, it has one edge between nodes.

@eduramiba
Copy link
Member

Ok, If I choose directed and sum, I get the 246 edges.

The problem is, when undirected, opposite edges cannot coexist, and they should be merged, but it seems no edge is created at all when opposite undirected edges exist.

I will investigate this problem, thanks for the report!

@eduramiba eduramiba added this to the 0.9.3 milestone Nov 17, 2017
eduramiba added a commit that referenced this issue Nov 17, 2017
@eduramiba
Copy link
Member

After fixing this problem, now forcing undirected correctly includes an loja,postalecu911 edge with Weight = 2, but the final amount of edges is 224 (might be right, due to opposite undirected edges being incompatible).
It seems everything is fine, so I am not sure if I am missing something... Can you please check the new output and confirm it's fine? This is what it produces:
testEdgesTableOppositeForceUndirected_Issue1848_edges.zip

@jorgaf
Copy link
Author

jorgaf commented Nov 18, 2017

I checked the new graph. It looks ok.
I am closing the issue.

@jorgaf jorgaf closed this as completed Nov 18, 2017
@eduramiba
Copy link
Member

Great, thanks! I will merge this soon into master, so next 0.9.3-SNAPSHOT should contain the fix.
Also, this fix will be available in next batch of updates for 0.9.2 (in-app Tools-Plugins menu) soon.

eduramiba added a commit that referenced this issue Nov 18, 2017
Based on commit 6634da3

#1516 Edge labels not retained on graphml export
#1788 GephiFormatException: Gephi failed saving the project.
#1789 NullPointerException: The fileObject parameter cannot be null
#1802 Exception with no-merge strategy in some cases. Incompatible edge should not be created
#1810 GephiFormatException can cause ArrayIndexOutOfBoundsException: 0
#1811 NullPointerException on EdgeTypeFilter
#1812 CSV files are no longer imported correctly when double quotes inside strings are delimited with backslashes
#1815 Add support of Byte Order Mark to CSV parser
#1840 Import of graphml still confuses d3 and label fields
#1848 Import CSV error edges: force undirected makes edges disappear when merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants