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

same data,different result #3

Open
hbsun2113 opened this issue Jan 12, 2018 · 4 comments
Open

same data,different result #3

hbsun2113 opened this issue Jan 12, 2018 · 4 comments

Comments

@hbsun2113
Copy link

image

@hbsun2113
Copy link
Author

Why?

@hbsun2113
Copy link
Author

@srajama1
Copy link
Contributor

@gslota

@gslota
Copy link
Contributor

gslota commented Jan 15, 2018

I've gotten a change to take another look. I'm unable to reproduce the error/non-determinism in output:

(xenial)gmslota@localhost:~/Documents/github/Connectivity/multistep$ ./scc p2p-Gnutella06.txt
Multistep SCC time: 0.010057
Num SCCs: 3732, Nontrivial: 1, Max SCC: 4986, Unassigned 0
(xenial)gmslota@localhost:~/Documents/github/Connectivity/multistep$ ./scc p2p-Gnutella06.txt
Multistep SCC time: 0.010057
Num SCCs: 3732, Nontrivial: 1, Max SCC: 4986, Unassigned 0
(xenial)gmslota@localhost:~/Documents/github/Connectivity/multistep$ ./scc p2p-Gnutella06.txt
Multistep SCC time: 0.010057
Num SCCs: 3732, Nontrivial: 1, Max SCC: 4986, Unassigned 0

Can you please verify that your .graph file follows the specified format in the README exactly. There should be only spaces (no tabs) and unix-style newlines -- our parser isn't particularly intelligent. If that's correct, then can you let me know your hardware configuration. As mentioned in my email, we make a few architectural assumptions that should be valid on most, but possibly not all, modern architectures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants