Closed stsievert closed 3 years ago
@crcox does this resolve your issue? I think this is similar to the external ID/ext_id
you mentioned in #117.
Yes, that will do the trick. Clarification on validation queries: is it something like
samplers: {
Validation: {},
queries: [[0, 1, 2], [3, 4, 5]]
}
or
samplers: {
Validation: {
queries: [[0, 1, 2], [3, 4, 5]]
}
}
?
basic.yaml shows an example of how to specify the indices. Here's a snippet:
samplers:
ARR: {}
Random: {}
Validation:
queries: [[0, 1, 2], [3, 4, 5], [6, 7, 8]]
(updated to reflect sampler renaming)
Perfect, thanks!
Most tests are passing locally, all except 3. That's a non-issue; I'm testing that errors get logged, and can't restart docker in the middle of the tests. If I could, those tests would pass.
What does this PR implement? It allows the following:
n_search
queries (instead of asynchronously).queries: [[0, 1, 2], [3, 4, 5]]
ininit.yaml
under thesamplers
heading.http://localhost:8421/?puid=foobar
.samplers_per_user
/query?ident=
.samplers_per_user
ininit.yaml
.sampling
key in init.yml.torch.no_grad
inscore
.Backwards incompatible changes
RandomSampling
toRandom
to fit with naming scheme of other samplers.Runner
toSampler
.Reference issues/PRs This closes #114 and #117.