RigNet icon indicating copy to clipboard operation
RigNet copied to clipboard

How to reduce/eliminate the "randomness" of the predicted skeleton?

Open kts707 opened this issue 2 years ago • 4 comments

Hi @zhan-xu

Thanks for the great work!

As discussed in #41, "randomness" mainly comes from random sampling. I tried to manually set a fixed seed before all the operations involving such random sampling. However, the randomness is still there...

I was wondering if there is any way to reduce/eliminate the result's randomness as my output differs by a lot in each run. Any suggestion/comment will be greatly appreciated!

kts707 avatar Aug 23 '22 03:08 kts707

So far as I tried, setting numpy.random.seed() and seed in sample_points_poisson_disk() could help reproduce results. e.g. codes here: https://github.com/zhan-xu/RigNet/blob/master/geometric_proc/common_ops.py#L50 samples = mesh.sample_points_poisson_disk(number_of_points=4000, seed=123)

CoolGua0113 avatar Sep 22 '22 02:09 CoolGua0113

Hi @CoolGua0113 ,

Thanks for your answer! I set the numpy seed and the seed in sample_points_poisson_disk(). However, I am still getting different results every time. Is there anything that you changed to get consistent results?

kts707 avatar Sep 24 '22 01:09 kts707

Nothing else sorry...I could get completely same results each run after setting these two seeds. Maybe you could check the input to RigNet(in create_single_data()) first? As mentioned by the author, the randomness of the network might be less important.

CoolGua0113 avatar Sep 24 '22 03:09 CoolGua0113

Did you set the numpy seed before every numpy operation that involves randomness?

I am basically running quick_start.py with numpy seed set before loading the network only, however, still getting different results in each run (the sample_points_poisson_disk() seed is also set to a deterministic number, and the input is also the same each time)

kts707 avatar Sep 24 '22 04:09 kts707