Open godspeed1989 opened 5 years ago
sorry for late reply.
Thanks!
For question 1, do you mean the function noise_per_object_v3_
in second.core.preprocess
file?
I am afraid can't figure out your explanation from it.
Could you give me a little more tips?
the function noise_per_object_v3_
first generate noises with shape [num_boxes, num_try, noise_ndim]
, then apply noise sequentially. For every box, this function firstly compute location after apply noise, then test collision between this box and other boxes, if collision exists, then drop this noise and try next one.
Thank you very much.
The collision detection and selection are done in function noise_per_box_v2_
Sorry to bother you again.
I notice in all .config files, global_random_rotation_range_per_object
under database_sampler
are all set to [0,0]
Which means _enable_global_rot
are always False.
and prep.noise_per_object_v3_
will never be called.
https://github.com/traveller59/second.pytorch/blob/93e5bb7164b3f3ee649337b38111c7048dca0644/second/core/sample_ops.py#L249-L258
That's wired. Does this function really useful?
Thank you in advance.
Sorry to bother you again. But i still want to know the answer about my last question. :)
Hi, I have two questions about data augmentation. First, In config file, I notice you set target random rotation at range [-45,45]. https://github.com/traveller59/second.pytorch/blob/fb28d7b606dc0dcfbe73b78df285b9d8cd3df34a/second/configs/car.config#L123 and random shifting at https://github.com/traveller59/second.pytorch/blob/fb28d7b606dc0dcfbe73b78df285b9d8cd3df34a/second/configs/car.config#L121 My question is whether these two ranges are a little too wide which may cause the collision of targets. Second, I notice you do not switch on this flag https://github.com/traveller59/second.pytorch/blob/fb28d7b606dc0dcfbe73b78df285b9d8cd3df34a/second/configs/car.config#L129 But i think this operation will help to generate samples closer to real. Have you ever try it?
Thank you in advance.