We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Harvey,
In your paper it was stated that
"For each class, we pick k labeled instances as our support set and 16 instances for the query set for a k-shot task"
However in your feature_evaluation function in test.py code, the default number of query instances per class was 15: n_query = 15.
feature_evaluation
test.py
n_query = 15
Since the setting used by Ravi et al. was also 15 samples per class for D_test, was it a minor typological error in your paper?
The text was updated successfully, but these errors were encountered:
I also have this doubt, and I don't understand why there are query sets in the fine-tuning methods(baseline and baseline++)?
Sorry, something went wrong.
No branches or pull requests
Hi Harvey,
In your paper it was stated that
However in your
feature_evaluation
function intest.py
code, the default number of query instances per class was 15:n_query = 15
.Since the setting used by Ravi et al. was also 15 samples per class for D_test, was it a minor typological error in your paper?
The text was updated successfully, but these errors were encountered: