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

Order of training the captioning module v/s the proposal module (and whether training is E2E?) #2

Closed
amanchadha opened this issue May 18, 2020 · 2 comments

Comments

@amanchadha
Copy link

Hi Vladimir,

First, thanks for the great codebase - everything is neatly organized in the source files - a nice deviation compared to what AI codebases from papers usually look like :)

Some questions:

Train and Predict
Run the training and prediction script. It will, first, train the captioning model and, then, evaluate the predictions of the best model in the learned proposal setting.

From your comments on training, it is clear that the captioning module is trained first (on GT proposals?). However, it is not very clear when the proposal module is trained. Is the training end-to-end as in Zhuo et al. [59] where both modules are trained in unison (where the captioning module is able to influence the event proposal mechanism)? Can you explain this sequence clearly (maybe for the sake for everyone by updating the readme?). Thanks!

@v-iashin
Copy link
Owner

Hi,
Thanks for the positive words and feedback.

Regarding your questions:

  • The training is not "end-to-end"
  • We train only the captioning module (yes, on GT proposals)
  • We use the predictions (./data/bafcg_val_100_proposal_result.csv – we contacted the authors for it) from the model proposed in Wang et. al 2018 which wasn't finetuned anyhow

Therefore, the sequence of training:

  1. Training the captioning module on GT proposals (it will evaluate the model on GT automatically)
  2. Evaluate the captioning module with the proposals from Wang et. al 2018

@amanchadha
Copy link
Author

Thank you - you've been very helpful!

This issue was closed.
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