acceptodds
Under review as a conference paper at ICLR 2027

Can Weak Models Explore? Scope Then Cover for LLM Agent Adaptation

Abstract

Adapting a language-model agent to a new environment requires exploration, and the prevailing assumption is that stronger models explore better. We examine two regimes where model capability alone is insufficient for discovery: when the available information does not help locate the target, and when the discovery advantage over uniform inspection diminishes as the candidate space grows. These observations motivate combining task-informed guidance with broad inspection: a strong actor selects a candidate scope, and weak scouts inspect candidates within it in parallel. We instantiate this scope-then-cover decomposition as a single explore action for frozen test-time actors. On ALFWorld, WebShop, and SWE-Bench-Verified, adding the explore action improves task performance over the actor-only baseline by assigning additional inspections to weak scouts.

Primary area:
foundation or frontier models, including LLMs
Keywords:
LLM Agents, Exploration, Test-Time Adaptation

Reviews

Among:
Shape:
1234this paper, Bottom 1%
Figure 1. Mean review rating of the reviewed papers at ICLR 2027. This paper averages 1.00 over 2 reviews, above 0% of the others.
Reviewer_JCPkOpenReview ↗
Rating
1
Confidence
3
Informativeness
1
Presentation
3
Soundness
2
Read review
Paper summary

This paper studies the assumption in test-time adaptation for LLM agents -- stronger models explore better than the weaker counterparts. The studies examine how the benefits of model capability depend on the information available about the target location and the size of the inspectable candidate space. From the observations, the authors propose a hybrid strategy that combines task-informed guidance and broad inspection to improve performance from LLM agent exploration. The authors evaluate the proposed scope-then-cover exploration strategy on three agentic benchmarks and show performance gain over actor-only baseline.

Critical strengths
  • This paper addresses a practically important problem in test-time adaptation for LLM agents.
  • The authors evaluate the proposed scope-then-cover method across various agentic benchmarks which span different agentic skills -- the evaluation offers comprehensive coverage.
  • The formulation of the budget-prior framework is sound and easy to follow.
Critical weaknesses
  1. The experiments only test one model family (i.e., Qwen3), therefore "stronger model" here refers to "larger model" and it remains unclear if the proposed method would generalize across model families. For instance, the discovery approach may differ across models (e.g., scope size selected by different models may exhibit different model biases).
  2. The proposed scope-then-cover strategy does not compare against other exploration-based baseline methods under matched computational budgets in the main evaluation. In addition, the performance gains may just come from additional test-time compute budget -- it is unclear if the performance lift mainly comes from the design of scope-then-cover strategy, or just additional compute budget.
  3. The methodological novelty appears to be limited, specifically the proposed method of using stronger model for task-informed scoping and weaker model for covering appears to be the main novelty of this work. However, delegating subtasks to different agents depending on task difficulty has been extensively studied in prior work to improve effectiveness or efficiency. Therefore it remains unclear if the decomposition strategy in scope-then-cover offers much methodological novelty. Moreover, the budget-prior formulation mainly formalizes intuitive relationships among search space size, scope recall, inspection budget, rather than providing new theoretical insights. Hence the overall contribution and novelty of this paper may be limited.
  4. The authors match exploration budget across model sizes as wall-clock time in the controlled experiment (Appendix D.2, fixed budget is TT times per-inspection wall-clock under a single H100 GPU). However, monetary cost is also an important metric to be considered for practical agent exploration, particularly for running multiple scout agents in parallel. It would strengthen the comprehensiveness of the studies, and offer valuable insights in practical settings, if the authors can consider measuring using monetary cost, and compare cost-performance trade-offs.
Questions for authors
  1. Figure 2 main caption is missing.
  2. In ALFWorld randomized probe in Figure 2a, how do you randomize object placements in the experiment setup?
1 comment

Thank you for your constructive comments. We respond to each concern in detail below.

W1. Generalization beyond the Qwen family

We added a DeepSeek-Flash actor and compared the following configurations on the same 200 WebShop tasks and 274 ALFWorld tasks. Both scout configurations use self-prompt exploration.

ConfigurationWebShop scoreALFWorld success rate
DeepSeek-Flash actor only61.61%90.88%
+ Qwen3-4B scouts69.07%93.80%
+ DeepSeek-Flash scouts68.03%93.43%

Qwen3-4B scouts improve task performance in both environments and achieve results close to those of DeepSeek-Flash scouts. This extends the evidence to a non-Qwen actor and demonstrates cooperation across model families.

Due to time constraints, the corresponding three-arm SWE-bench evaluation has not yet been completed. We will update the results once it is complete.

W2. Exploration baselines and compute allocation

Our added comparison includes using the actor model itself, DeepSeek-Flash, in the scout role. With the same DeepSeek-Flash actor and task sets, both scout configurations use self-prompt exploration: DeepSeek-Flash scouts achieve 68.03% on WebShop and 93.43% on ALFWorld, compared with 69.07% and 93.80% using Qwen3-4B scouts. This directly compares allocating scoped exploration to the same strong model versus a weaker model. Their similar task performance supports the use of weaker models for scoped information gathering, while the actor retains responsibility for task understanding and subsequent decisions.

The controlled WebShop probe separately examines compute allocation under a matched time budget. Based on measured per-inspection times, the 0.6B, 4B, and 8B models receive 30, 12, and 8 inspections, respectively. This tests the role of increased inspection coverage by weaker models within the same time allowance. Together, the two experiments examine the capability required for the exploration role and the capability-coverage trade-off under a fixed budget. W4 reports the monetary cost and task performance of the fully API-based configurations.

W3. Contribution beyond existing multi-agent delegation

Our contribution is to characterize when weaker models can take over information gathering within a scope selected by a stronger actor. We implement this division of labor through an explicit explore action: the actor specifies the missing information and search scope, scouts inspect that scope and return evidence, and the actor uses the evidence to make subsequent decisions.

We analyze and test when this division of labor is effective. Controlled probes examine whether greater inspection coverage can compensate for weaker model capability; return-content ablations examine which information helps the actor; and the added strong-actor comparison tests whether weaker scouts can fulfill this role in full tasks.

The theory further gives a condition for this division of labor to help. Under the proposition's uniformity and reliable-inspection assumptions, discovery lift in the non-saturated regime is characterized by r/rho: narrowing the scope improves over uniform inspection at the same budget when the retained target probability exceeds the scope fraction, i.e., r > rho. This provides a testable quantitative basis for the trade-off among scope size, target recall, and inspection budget.

W4. Monetary cost and performance

We estimate API costs for the fully API-based configurations in W1 using recorded token usage, including recorded reruns. Cached input, uncached input, and output are priced at $0.003, $0.15, and $0.60 per million tokens, respectively, using the historical off-peak reference rates in the experiment scripts.

EnvironmentConfigurationTask performanceEstimated API cost/task (USD)
WebShopDeepSeek-Flash actor only61.61%$0.002902
WebShop+ DeepSeek-Flash scouts68.03%$0.003095
ALFWorldDeepSeek-Flash actor only90.88%$0.001685
ALFWorld+ DeepSeek-Flash scouts93.43%$0.001949

Adding DeepSeek-Flash scouts increases the WebShop score by 6.42 points at approximately 6.6% higher API cost, and ALFWorld success by 2.55 percentage points at approximately 15.6% higher API cost. These results quantify the performance-cost trade-off of delegated exploration.

Qwen3-4B scouts are locally hosted. Their recorded allocation across eight H20 replicas is 0.026556 GPU-hours per WebShop task and 0.008605 per ALFWorld task, including loading and idle time. Converting this allocation to a total monetary cost requires the GPU-hour price in addition to the actor's API charges; the API-only comparison above therefore uses the two fully API-based configurations.

Q1. Figure 2 caption

Thank you for pointing this out. We will add the missing caption.

Q2. ALFWorld probe randomization

Thank you for pointing this out. We will clarify the randomization procedure.

Reviewer_qfSkOpenReview ↗
Rating
1
Confidence
4
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

This paper studies how prior information and inspection coverage affect agent exploration. Its scope-then-cover approach uses a strong actor to select a promising region and weaker scouts to inspect candidates within it. A budget–prior analysis motivates this division of work. Experiments on ALFWorld, WebShop, and SWE-Bench Verified report improvements over actor-only systems, with analyses of scope quality and scout behavior.

Critical strengths

S1. Splitting exploration into choosing a scope and checking candidates within it is easy to understand and useful. The r/rho result also makes clear why scope recall and size matter, under the stated assumptions.

S2. The controlled probes distinguish target discovery from final selection, and the paper reports explore-action gains on ALFWorld, WebShop, and SWE-Bench. These observations provide a useful starting point for studying how to divide exploration work.

Critical weaknesses

W1. The main comparison adds scout computation and separate environment sessions. The fixed-time WebShop probe helps, but the full-system budget comparison remains unresolved. The actors are also all from the Qwen family. Without testing a stronger API actor with and without scouts, it is unclear whether this division of labor remains useful when the actor itself explores more effectively.

W2. I could not reconcile the ALFWorld 8B results: Table 1 gives 24.82/45.26, while Appendix E.1 reports 29.6/42.7 for what is described as the same 274-task evaluation. Appendix C.5 only states that scouts are frozen, without supplying a per-environment configuration there. The protocol mapping and complete model settings need to be explicit before the results form a coherent main comparison.

W3. The interpretation of the SWE return-content result depends on how test files are selected. The example identifies gold source/test files and pre-fetched test content, but the procedure does not make clear which information was available when choosing the payload. Until that provenance is explicit, the result is difficult to use as clean evidence of scout-driven discovery.

W4. The full-system experiments do not yet isolate the weak-scout mechanism. Table 2 describes scope inclusion, and Figure 3 studies inspection allowance and selection diversity across independent runs. The controlled probes in Figure 2 are useful, but do not replace a comparison of inspector capability within identical states, scopes, and total budgets on the actual tasks. The current evidence more directly supports additional inspection than the specific allocation of model capability.

Questions for authors

Q1. For the self-prompt variant, can a representative strong API actor be evaluated with and without the same weak scouts? Please account for the complete exploration budget, including extra actor-only exploration, in monetary cost and latency. Within the same scope, a deterministic or uniform inspector would also help show what is gained by using weak language-model scouts.

Q2. For the SWE return-content ablation, how are source files and test files located and chosen? Are all returned tests already present in the base repository, with no reference patch, benchmark test patch, or hidden evaluation feedback used for selection? Please also explain how the scope groups and their validation set were constructed.

Q3. Please reconcile the ALFWorld 8B results in Table 1 and Appendix E.1, and provide the complete actor/scout checkpoints, decoding settings, trigger thresholds, per-call tool budgets, and accounting for replay/environment steps. Which exact protocol supports the principal cross-environment conclusion?

Q4. Can scope quality and inspector capability be varied separately from the same pre-call states on actual agent tasks? Keeping non-repetition rules and total budgets fixed, compare weak scouts, stronger scouts, and a simple inspector within the same scope. Reporting task outcomes as well as target hits would connect the probe interpretation to the claimed division of labor.

Q5. For the Sokoban study in Figure 4, are collector interaction budgets, retained training-example counts, and actor updates matched between Base and +Explore? Please specify what changes besides the collector. The curve alone does not show whether the benefit comes from better information or simply collecting more training data.

3 comments

We sincerely thank the reviewer for the constructive feedback. We respond to each concern in detail below.

W1. Strong API actor and the exploration budget

We added a stronger, non-Qwen actor, DeepSeek-Flash, and evaluated three configurations on the same 200 WebShop tasks and 274 ALFWorld tasks. Both scout-enabled arms use self-prompt exploration.

ConfigurationWebShop scoreALFWorld success rate
DeepSeek-Flash actor only61.61%90.88%
+ Qwen3-4B scouts69.07%93.80%
+ DeepSeek-Flash scouts68.03%93.43%

WebShop score is the mean native attribute-match reward multiplied by 100. Qwen3-4B scouts improve the WebShop score by 7.45 points and ALFWorld success by 2.92 percentage points, including a setting where actor-only success is already 90.88%. Replacing them with DeepSeek-Flash scouts yields no further improvement in these runs. This extends the evidence to a stronger actor from another model family and supports using weaker models for scoped inspection.

The actor model and requested decoding settings are shared across the three arms. This comparison varies scout capability; the fixed-time WebShop probe separately examines inspection under a matched time allowance. Additional actor-only exploration at matched total cost remains a separate control. Resource accounting and execution conditions are detailed in Q1.

Due to time constraints, the corresponding three-arm SWE-bench evaluation has not yet been completed. We will update the results once it is complete.

W2. Reconciling the ALFWorld results

Table 1 and Appendix E.1 report two runs on the same 274 ALFWorld tasks, both using a Qwen3-8B actor with temperature 0.7. Table 1 uses seed 42 and reports actor-only and self-prompt success rates of 24.82% and 45.26%, respectively. Appendix E.1 reports the version without a fixed random seed, with success rates of 29.6% and 42.7%, respectively. We will make this distinction explicit in the paper.

W3. SWE test-file selection and information provenance

The scout is not given gold source/test paths, the test patch, the FAIL_TO_PASS list, or the reference patch for file selection; it locates relevant files by searching the repository based on the issue. The "gold source" and "gold test" labels in Appendix E.2 are retrospective annotations.

W4. Separating scope selection from inspection capability

The added comparison in W1 fixes the actor model and task sets while varying scout capability. Qwen3-4B scouts achieve task outcomes comparable to DeepSeek-Flash scouts in these runs, supporting their use for the inspection role. The controlled probes separately examine inspection budget and model size.

Q4 adds a full-episode simple-inspector control under the original WebShop navigation procedure. The rule-based arm scores 68.08, compared with 69.07 using Qwen3-4B scouts and 68.03 using DeepSeek-Flash scouts. The simple inspector achieves a score close to both model-based inspectors. On ALFWorld, the added random-action control succeeds on 249/274 tasks (90.88%), compared with 93.80% and 93.43% for the two model-based scouts. Q4 reports token usage separately by model and role, including recorded rerun overhead. The full-episode runs allow actor trajectories and selected scopes to diverge, so they complement the requested comparison from identical pre-call states.

Q1. Strong API actor and simple-inspector comparisons

The strong API actor comparison is reported in W1. Q4 reports the simple-inspector controls on the same task sets, together with task performance and per-task actor and scout token usage.

Q2. File selection, scope construction, and validation

The issue-guided procedure for locating source and test files is described in W3.

We used a small, separate validation batch with no overlap with the 500 evaluation instances. We ultimately adopted prompt-based scoping: the actor chooses the exploration scope from the current task and observations. In ALFWorld and WebShop, it names individual receptacles or products; in SWE-bench, it specifies the exploration direction through a free-text query. The validation concerned this prompting approach. We will clarify Appendix C.8 so that "granularity selection" refers to this procedure, and provide the validation batch size and instance list.

Q3. Per-environment configuration and the main protocol

The difference between the two ALFWorld evaluations is explained in W2. The principal cross-environment comparison uses the main runs in Table 1. The recovered seed-42 logs verify the following serving labels and actor settings for all five policies in ALFWorld and WebShop:

EnvironmentTasksActor serving labelScout serving labelActor turn limit
ALFWorld274qwen3_8b_mainqwen3_4b_scout50
WebShop200qwen3_30b_mainqwen3_4b_scout20

Recorded actor decoding is temperature 0.7, top_p 0.8, top_k 20, min_p 0.0, repetition penalty 1.05, and seed 42. The WebShop records use the revised implementation, including action-parsing corrections and preservation of the actor's browsing context after scout feedback; we will identify that version explicitly alongside its repeated results and resource accounting.

An actor-issued explore action consumes one actor turn. Scout internal steps are additional environment interactions and do not consume further actor turns. Candidate limits and worker action limits specify different resources and will be listed separately for each policy and environment.

Q4. Simple-inspector controls

We added full-episode controls using the same tasks, DeepSeek-Flash actor, actor settings, and scout-call limits as W1. On WebShop, the simple inspector follows the original navigation procedure and returns rule-extracted product facts for the actor to assess. On ALFWorld, it samples information-gathering actions within the actor-selected scope and returns a rule-extracted object report. Neither simple inspector calls a scout model.

EnvironmentInspectorTask performanceActor tokens/taskScout tokens/task
WebShopRule-based product facts68.08%37,5230
WebShopQwen3-4B scouts69.07%32,786438
WebShopDeepSeek-Flash scouts68.03%38,068398
ALFWorldRandom actions + object report90.88%38,4710
ALFWorldQwen3-4B scouts93.80%27,3631,395
ALFWorldDeepSeek-Flash scouts93.43%26,1431,207

The scouts take over part of the information processing required during exploration. Compared with simple inspectors that leave the actor to interpret the collected facts, Qwen3-4B scouts reduce actor token usage by 12.6% on WebShop and 28.9% on ALFWorld, using 438 and 1,395 scout tokens per task, respectively. WebShop scores increase from 68.08 to 69.07, and ALFWorld success increases from 90.88% to 93.80%. Together, these results support the value of delegating exploration-related information processing to scouts: the actor uses fewer tokens while task performance is maintained or improved.

Q5. Sokoban collection and training budgets

Base and +Explore use the same training settings: 20 update steps per round with 64 game samples per step, yielding 1,280 samples per round and 3,840 samples over three rounds (60 update steps). We calibrate the number of collection runs using small-batch timing measurements to match total collection time between the two conditions. Training retains both successful and unsuccessful trajectories; experiential knowledge is extracted using the specified format and truncated to the context limit. Each game is capped at five interaction turns, with at most 1,024 response tokens per turn.

Dear authors,

Thank you for the additions. I think the strong-actor results show that weak scouts can assist a capable actor. I also understand the ALFWorld seed explanation and the SWE selection clarification. However, my central concerns in Q1/Q4 remain. Although the discussion deadline is approaching, two points still affect my assessment.

1. Allocation versus additional exploration

Matching actor-turn limits still gives the scout-enabled system additional environment interactions. Your reported WebShop self-prompt run uses 42.48 steps versus 9.09 for actor-only. Comparing weak and strong scouts does not establish whether the actor could achieve similar gains with an equivalent total exploration budget. Without this control, I remain unconvinced that the end-task improvement demonstrates the proposed resource allocation rather than additional exploration. The fixed-time probe does not resolve this full-system concern.

2. The contribution of task-informed scoping

All added inspector comparisons retain actor-selected scopes, so they do not isolate this component of Q4. Please identify the evidence that task-informed scopes improve discovery over size-matched random scopes, with the inspector and inspection budget fixed. The report-based inclusion proxy in Table 2 is not true scope recall and cannot establish this comparison. In my reading, this remains a missing link between the theoretical decomposition and the evaluated system.

Comments on the paper

2 comments

Thank you for your careful review. We respond to each concern in detail below.

W1. End-task comparison of scout capability

We use a stronger actor, DeepSeek-Flash, to compare actor-only, Qwen3-4B scouts, and DeepSeek-Flash scouts on the same 200 WebShop tasks and 274 ALFWorld tasks. Both scout configurations use self-prompt exploration.

ConfigurationWebShop scoreALFWorld success rate
Actor only61.61%90.88%
+ Qwen3-4B scouts69.07%93.80%
+ DeepSeek-Flash scouts68.03%93.43%

Qwen3-4B scouts improve task performance in both environments and achieve results close to those of stronger scouts, supporting the use of weak models for exploration within an actor-selected scope.

Due to time constraints, the corresponding three-arm SWE-bench evaluation has not yet been completed. We will update the results once it is complete.

W2. The role of the theory and its connection to the experiments

The theory identifies when this division of labor helps: the actor must preserve sufficient target recall while narrowing the search space, and the scouts cover the selected scope. Proposition 1 quantifies this trade-off as r/rho: under its uniformity and reliable-inspection assumptions, discovery improves over uniform inspection at the same budget when recall r exceeds scope fraction rho. Eq. 6 gives the corresponding condition for comparison with an informed direct-search policy. The analysis thus provides a basis for considering scope size, target recall, and inspection coverage together.

For Boundary 2, we will add a sufficient condition: at a fixed budget, if the maximum conditional target probability tends to zero as the candidate space grows, discovery under finitely many inspections and its absolute advantage also tend to zero. In WebShop at T=8, increasing the pool from 100 to 1,000 reduces the absolute gap from approximately 33 to 7 percentage points, while relative lift increases from approximately 5.1x to 9.8x. “Eroding advantage” refers to the former; we will distinguish the two measures explicitly.

Analysis of the same ALFWorld calls separates scope inclusion (31.71%) from actual discovery (21.95%), with 69.23% discovery conditional on inclusion; definitions are given in Q4. Finally, r/rho measures discovery lift, whereas Table 1 measures final task performance. SWE-bench still requires a correct repair after locating relevant code, so the cross-environment rankings of these gains need not coincide.

Q1. ALFWorld run mapping and WebShop results across seeds

Both ALFWorld evaluations use Qwen3-8B, temperature 0.7, and the same 274 tasks. Table 1 uses seed 42, yielding 24.82% actor-only and 45.26% self-prompt success. Appendix E.1 uses no fixed random seed, yielding 29.6% and 42.7%, respectively.

WebShop is evaluated on the same 200 tasks with seeds 42, 43, and 44. The revised implementation corrects action parsing and preserves the actor's browsing context after scout feedback.

PolicyMean score95% CI
Actor-only44.26%[40.47%, 48.06%]
Forced-pre55.44%[51.55%, 59.34%]
Forced-mid46.51%[44.71%, 48.31%]
Self-signal44.45%[39.60%, 49.31%]
Self-prompt48.84%[47.53%, 50.14%]

The approximate confidence intervals use Student-t across the three seed-level means. Forced-pre scores highest in all three runs, averaging 11.18 percentage points above actor-only, consistent with the value of obtaining product information before subsequent shopping decisions.

Q2. Actor turns and exploration costs

An explore call consumes one actor turn; the scout's internal actions do not consume additional actor turns. The following are per-task means for seed 42, covering actor and scout usage on 274 ALFWorld tasks and 200 WebShop tasks.

EnvironmentPolicyEnvironment stepsTotal tokensElapsed seconds
ALFWorldActor-only40.7677,65166.83
ALFWorldForced-pre45.3280,95768.87
ALFWorldForced-mid45.3683,13168.31
ALFWorldSelf-signal48.4986,38473.32
ALFWorldSelf-prompt41.0788,12398.86
WebShopActor-only9.0933,04554.39
WebShopForced-pre15.0639,73479.70
WebShopForced-mid12.4435,78063.40
WebShopSelf-signal8.6131,16877.42
WebShopSelf-prompt42.4868,003122.43

For ALFWorld self-prompt, steps and tokens exclude auxiliary diagnostic calls whose outputs were not returned to the actor; recorded elapsed time may include them.

Q3. Test-file selection and validation instances

The Read test scout searches the issue text and repository contents for relevant source code, then uses class or function names to locate related tests. The selector inputs do not include the test patch, FAIL_TO_PASS list, or reference patch. The appendix's “gold source/test” labels are retrospective annotations, not paths supplied to the scout.

A separate small validation batch, with no overlap with the 500 evaluation instances, was used to validate prompt-guided scoping. The actor selects the scope from the current task and observations: specific receptacles or products in ALFWorld and WebShop, and a free-text query specifying the exploration direction in SWE-bench.

Q4. Report-based inclusion proxy

The proxy uses each task's first scout call: it is 1 if any per-target report contains the literal string “contains [”, and 0 otherwise; tasks without a call are excluded. It is 91.49% in the 100-task, K=6 analysis. Because it uses scout reports, it reflects scope selection, inspection, and reporting.

We therefore also use evaluator-side location records to distinguish whether the selected locations contain the target from whether a scout actually reaches a target location and observes it. In the main seed-42 run, 123 first calls satisfy target-matching and location-record consistency criteria, yielding the 31.71% inclusion and 21.95% discovery rates reported in W2. These diagnostics and the historical report proxy use different cohorts and are calculated separately.

Q5. Scope size and the actor's decision

The actor decides whether to explore, which candidates to select, and what information to request. A candidate-count limit constrains call size but does not choose the candidates; equally sized scopes can contain different objects.

In WebShop, 162 of 200 tasks call scouts. At their first call, the numbers selecting 2, 3, 4, 5, and 6 distinct products are 2, 12, 9, 112, and 27, respectively, showing that the selected scope size is not fixed. In SWE-bench, the actor specifies the exploration direction through a free-text query.

Q6. Repeatability of the return-content ablation

On the same 50 instances, factual briefs and source excerpts each achieve 52% resolution, Read test achieves 58%, and the structural-scan baseline and both judgment-bearing variants achieve 48%. This comparison supports the usefulness of concrete factual information, especially test code. Each configuration has been evaluated once; the stated pattern describes this comparison.

Q7. Sokoban evaluation size, seeds, and learning curves

Sokoban is evaluated on 128 held-out maps, averaged over 10 evaluation seeds, with one training run per condition. The paper presents the full learning curves. At the final recorded step, 60, Base and Explore achieve 14.84% and 21.09% accuracy, respectively, a difference of 6.25 percentage points.

From OpenReview, CC BY 4.0. Authors as signed there; shown unedited.

Related papers

Loading the map…

Discussion (0)

Sign in to comment.