Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
gaoqiong
lm-evaluation-harness
Commits
3c75a2c7
Unverified
Commit
3c75a2c7
authored
Dec 04, 2023
by
Lintang Sutawika
Committed by
GitHub
Dec 04, 2023
Browse files
Merge pull request #1062 from EleutherAI/haileyschoelkopf-patch-2
parents
fde2b77e
3512f742
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
19 deletions
+0
-19
lm_eval/api/samplers.py
lm_eval/api/samplers.py
+0
-19
No files found.
lm_eval/api/samplers.py
View file @
3c75a2c7
...
...
@@ -112,22 +112,3 @@ def get_sampler(name):
raise
ValueError
(
f
"Attempted to use contextsampler '
{
name
}
', but no sampling strategy for this name found! Supported model names:
{
', '
.
join
(
SAMPLER_REGISTRY
.
keys
())
}
"
)
# TODO: how should we do design here? might be better to have a single sampler and pass more kwargs at init.
# Depends what's easier for new user to add own functionality on top of
# types of sampler:
# - class-balanced, randomly shuffled
# - class-balanced, one particular set of fewshot examples for all evaled instances
# - hand-specify number of fewshot examples per class?
# - random, varies per example (check that this is curr. default in old repo)
# - random, unified per example
# - enforce a specific fixed fewshot string! (or should we not use this, in favor of including it in prompt template directly)
# - user-specified doc indices to restrict fewshot doc options to
# - user specifies split to use for drawing fewshot instances (TODO: manually prevent this from being same split you eval!)
# - user specifies a prepended "description"/string to add in front of the (prompted) input
# - user specifies a location to draw fewshot samples from? DO THIS IN TASK CLASS
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment