search

snap-stanford / snap

Stanford Network Analysis Platform (SNAP) is a general purpose network analysis and graph mining library.
Other
2.18k stars 799 forks source link

terminate called after throwing an instance of 'TPt<TExcept>' #177

Open miguelwon opened 5 years ago

miguelwon commented 5 years ago

Hi, I'm having this problem. It runs ok with the karate edge list example but not working with my real example. This is the log:

(env) mwon@mwon:/disk2/MP2Vec/snap/examples/node2vec$ ./node2vec -i:/disk2/MP2Vec/results/adj_retweets.csv -o:/disk2/MP2Vec/results/emb_node2vec -l:10 -w -v

An algorithmic framework for representational learning on graphs. [Sep 23 2019]
================================================================================
Input graph path (-i:)=/disk2/MP2Vec/results/adj_retweets.csv
Output graph path (-o:)=/disk2/MP2Vec/results/emb_node2vec
Number of dimensions. Default is 128 (-d:)=128
Length of walk per source. Default is 80 (-l:)=10
Number of walks per source. Default is 10 (-r:)=10
Context size for optimization. Default is 10 (-k:)=10
Number of epochs in SGD. Default is 1 (-e:)=1
Return hyperparameter. Default is 1 (-p:)=1
Inout hyperparameter. Default is 1 (-q:)=1
Verbose output. (-v)=YES
Graph is directed. (-dr)=NO
Graph is weighted. (-w)=YES
Output random walks instead of embeddings. (-ow)=NO
Read 601823 lines from /disk2/MP2Vec/results/adj_retweets.csv
Preprocessing progress: 99.36% 
Walking Progress: 92.19%
Learning Progress: 91.68% 
terminate called after throwing an instance of 'TPt<TExcept>'
Aborted
Wang-Yu-Qing commented 4 years ago

Has same issue here.

Wang-Yu-Qing commented 4 years ago

Has same issue here.

It turns out that I provided the wrong relative path of the input graph. After changing the graph path to absolute path, everything wrongs fine.

lodo1995 commented 3 years ago

I have the same issue here. I do not think that it is caused by the wrong path as previous comments suggested. From the log in the original post (which looks the same as mine), it can be seen that node2vec had already successfully read the entire file when the crash occurred. The crash happens after node2vec reaches over 91% of the learning progress.

janakurrek commented 3 years ago

same issue here, was this ever fixed?

peixian commented 1 year ago

This is an old issue, but in case anyone ends up here like I have, it was an issue of the path for me.

Input like

node2vec -i:/workspace/org-data.edgelist  -o:/workspace/org-data.emb  -d:64 -l:40 -q:0.5

succeeds, it's the : between -i and -o with absolute paths that get it to work