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

config.pv_net.train.iter_train == False #9

Open
dustinyzr opened this issue Nov 17, 2019 · 4 comments
Open

config.pv_net.train.iter_train == False #9

dustinyzr opened this issue Nov 17, 2019 · 4 comments

Comments

@dustinyzr
Copy link

Sorry to bother you!
Should this function be TRUE or FALSE?
In the paper PVRNet, in the first 10 epochs,the feature extraction model is fixed and only finetune the other part.

And if 'config.pv_net.train.iter_train == True:',I only got a result of 92.0%+,but not 93.6%
if I change this line to False, the result can be 93.1% but still not 93.6%
Did I make something wrong in using your code?

Thank you for your reply!

@Hxyou
Copy link
Collaborator

Hxyou commented Nov 20, 2019

iter_train flag means whether to iteratively train the scoring part and the other part besides the extraction model.
In my experiments, I set it to True.
From my observation, it empirically gives more chances to output higher performance.

@dustinyzr
Copy link
Author

iter_train flag means whether to iteratively train the scoring part and the other part besides the extraction model.
In my experiments, I set it to True.
From my observation, it empirically gives more chances to output higher performance.

Yes, but I saw in the paper the train strategy is that we fix the extraction model in the first 10 epochs, then train the whole model in the other epochs. So I am confused.

So the conclusion is that iteratively train is better than then above strategy?

So, about the result, did I make something wrong in using your code?
Maybe because our different pytorch environment or hardware environment?

@Hxyou
Copy link
Collaborator

Hxyou commented Nov 20, 2019

I guess there is nothing wrong with your code and that's regular fluctuation.
Run it several times and see which one is better.

@dustinyzr
Copy link
Author

fluctuation

OK! Thank you for your help!!!

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