Open LilithHafner opened 2 years ago
I'm on a macOS 11.4
Please create your own desired output directory and specify it in the argument: --output_directory. 'output_directory' was set as the default directory for the output files, but users need to create their own output directories and specify in the command lines.
Thanks for the speedy reply! I did that, ran into another error,
Traceback (most recent call last):
File "hyper_preferential_attachment.py", line 442, in <module>
main()
File "hyper_preferential_attachment.py", line 435, in main
generator.generate()
File "hyper_preferential_attachment.py", line 267, in generate
sampled_number = np.random.choice(a = maximum_number + 1, size = 1, replace = False, p = distribution)
File "mtrand.pyx", line 1023, in mtrand.RandomState.choice (numpy/random/mtrand/mtrand.c:7507)
ValueError: probabilities do not sum to 1
And then changed python to python3 which fixed that error (on my machine python points to python 2 while python3 points to python 3 to preserve backward compatibility). Now it runs, but its been thinking hard for quite a while without terminal output. Any idea how long its supposed to take to run python3 hyper_preferential_attachment.py --name=DAWN --file_name=DAWN --num_nodes=3029 --simplex_per_node_directory='simplex per node' --size_distribution_directory='size distribution' --output_directory=output_directory
?
Perhaps the need to manually create an output directory should be in the user guide?
By periodically checking the size of the output file, it looks like the runtime is about 1 microsecond times the number of edges generated squared. Perhaps that is the asymptotic runtime for small hyper edge size and large edge count?
Any idea how long its supposed to take to run python3 hyper_preferential_attachment.py --name=DAWN --file_name=DAWN --num_nodes=3029 --simplex_per_node_directory='simplex per node' --size_distribution_directory='size distribution' --output_directory=output_directory?
Update, it ran successfully in 7 hours (7:14:08) on my 2019 MacBook Air. If this is expected behavior, and executing examples.sh without manually creating an output_directory is supposed to error, then aside from some documentation issues (letting folks know about runtime & output_directory), there don't seem any strict bugs in this issue thread.
If you'd like to help folks avoid a file-not-found error, I made a fairly non-invasive PR #5 that should help.
I suspect that the output folders are not checked into GitHub and the examples fail to create them.
Reproduce this error by cloning the repository and following the instructions in user_guide.pdf: