-
Notifications
You must be signed in to change notification settings - Fork 198
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
Arguments for running Louvain clustering #915
Comments
It looks like it's trying to do what you want (the comparison uses max-iters and threshold). You'll have to dig into the code to see what happens. Looks like it's around here?
|
OK, but why
Instead of enactor.neighborcomm_threshold > 0 above, it should be enactor.neighborcomm_threshold >= iter-th it seems.
|
Yes, I only mean it's not intended behavior.
Thanks for catching. |
However, chances are the above suggestion will only save a few initial passes, if at all (exit iteration early); but this condition should mostly work all the time:
Now, looking at the output below, thinking about possible reasons why Louvain is running for all the #passes (note, #iters is only high for the first few phases, and diminishes with passes as expected):
|
I am trying to run Louvain for the default 10 phases and a maximum of 100 iterations/phase. I am passing the following options:
$BIN_PATH/./louvain --advance-mode=ALL_EDGES --max-iters=100 --iter-th=1e-6 --pass-th=1e-6 --1st-th=1e-6 --graph-type=market --graph-file=$file
I had expected the program to exit when the criteria is satisfied (as in exit a phase and also exit when threshold of previous and current phase is less than or equal to 1E-06), but it seems the code runs for 100 phases and 100 iterations/phase. A snapshot of the output is provided below, please advise.
Also, another question: if I add
--device=4
to the arguments above, then Louvain will run on 4 devices (as set byCUDA_VISIBLE_DEVICES
), is that right?The text was updated successfully, but these errors were encountered: