Skip to content
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

Pre-training and Data Augmentation #16

Closed
tonmoyborah opened this issue Aug 30, 2018 · 2 comments
Closed

Pre-training and Data Augmentation #16

tonmoyborah opened this issue Aug 30, 2018 · 2 comments

Comments

@tonmoyborah
Copy link

Hi Nwojke,
I had a few doubts I would like to clear. Since this is not pre-trained on Imagenet and you report that performance can increase with imagenet pre training, how should I go about it if I want to pre-train it? Will the improvement be significant in your opinion?
Also is test time augmentation done while reporting the results of this paper?
Again, since the image names carry vital info like tracklet id, label and camera, how can one do train data augmentation and still somehow take care of the image names? I presume these info are used during training somehow and augmenting will only disturb it. What are your thoughts on it?

@nwojke
Copy link
Owner

nwojke commented Apr 30, 2019

Hi tonmoyborah,

sorry for the late reply, I hope my answer it still helps.

  • For ImageNet pretraining you could either write your own training script around the network architecture code provided in this repository or you try to integrate a pretrained network into this repository. I am not sure what is the better fit in your case.
  • We didn't do test time augmentation.
  • It is best to do data augmentation on the fly, i.e., load raw images and their labels from disk, then manipulate the image data according to data augmentation, then place it in the training queue. This way, you won't have any issues with filenames and don't generate excessive amounts of data on your hard drive.

@nwojke
Copy link
Owner

nwojke commented Jul 10, 2019

I am closing this issue due to inactivity. Re-open if the problem is not solved.

@nwojke nwojke closed this as completed Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants