-
Notifications
You must be signed in to change notification settings - Fork 460
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
Image preprocessing #13
Comments
I have the same question. However when I do |
@zekun-li Hi, the provided *.npy file has shape (1, num_frames, 224, 224, 3), I wonder what "1" refers to? And what's its value? |
@egg347 That dimension corresponds to batch size. |
@zekun-li Thanks a lot! Have you solved your problem above? It seems that the sample data firstly rescale to [-1,1](videos to videos),and secondly rescale to [0,1](videos to *.npy file). |
@zekun-li I also have the same problem on preprocessing. No matter rescaling the image on R, G, B channel individually or across RGB channals, the results all can't match with the given .npy. Have you solved the problem? |
@zekun-li @egg347 @TianjiPang @seann999 : Hi guys, were you able to resolve the scaling. If yes, would you mind sharing what you did. Thanks |
I think I simply did what I first guessed, x/128.0-1.0. |
@seann999: I did the same too, I hope the extracted feature are alright. |
@zekun-li @seann999 @vivoutlaw @TianjiPang @egg347 I saw many people use So when you say your result doesn't match with the given |
The readme says to scale the RGB values between -1 and 1. Does this mean
x/128.0-1.0
, where x is an uint8 image?I'm more used to seeing normalizing images with mean and std, so I want to make sure.
The text was updated successfully, but these errors were encountered: