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

training and testing #191

Closed
Allen1207 opened this issue Jul 10, 2018 · 2 comments
Closed

training and testing #191

Allen1207 opened this issue Jul 10, 2018 · 2 comments

Comments

@Allen1207
Copy link

Dear Zhi Li,

If I train a model using the 'run_vmaf_training' process with some dataset, and then I run the 'run_testing' process with that trained model and the same dataset. Will I get the same results (SRCC, PCC, and RMSE) ?
I thought the results should be the same, but actually they are sometimes different, especially for the RMSE number. The maximum difference I have found is 3% for the RMSE (e.g., train=10.0, test=9.7).

Allen

@li-zhi
Copy link
Collaborator

li-zhi commented Jul 12, 2018

This is due to the slightly different workflows used by run_vmaf_training and run_testing. In run_vmaf_training, the feature scores (elementary metric scores) from each frame are first extracted, each feature is then temporally pooled (by arithmetic mean) to form a feature score per clip. The per-clip feature scores are then fit with the subjective scores to obtain the trained model. The reported SRCC, PCC and RMSE are the fitting result. In run_testing, the per-frame feature scores are first extracted, then the prediction model is applied on a per-frame basis, resulting "per-frame VMAF score". The final score for the clip is arithmetic mean of the per-frame scores. As you can see, there is a re-ordering of the 'temporal pooling' and 'prediction' operators. If the features from a clip are constant, the re-ordering will not have an impact. In practice, we find the numeric difference to be small.

@Allen1207
Copy link
Author

Thank you very much for your detailed explanation . I will go deep into the code as you said to see the difference.

@li-zhi li-zhi closed this as completed Jul 16, 2018
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