-
Notifications
You must be signed in to change notification settings - Fork 52
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
How to pre-process depth when the train and test data are taken from different distance? #50
Comments
Maybe changing this parameter ''depth_scale'' would help? How to confirm the value of ''depth_scale''? |
Sorry, I don't know what this parameter is, also didnot find it in args.py |
I tried pre-processed depth and non-pre-processed depth, and it didnot work well for non-pre-processed depth. So at least for my situation, I think pre-processing is necessary. |
Any new progress? Usually the depth map is normalized to [0,1]. I can't understand why the depth_mean in the code is a large number. |
I noticed that the depth map read in the sample is uint16, and the maximum value is 65535. Here is my method: Assuming the depth map is in uint8 format and the maximum value is 255, then new_depth_mean = depth_mean\65535 * 255 ≈ 74.0272. Similarly, calculate new_depth_std≈38.4435. The actual effect is basically satisfactory.(I use the SUN-RGBD model) |
The train and test data I am using was taken from different distance.
Say the train data is taken from 30m, and test data is taken from 60m.
Do I need to pre-processing the test data (eg. depth/60*30) to make it has the approximate same depth range with the train data?
Thanks.
The text was updated successfully, but these errors were encountered: