Skip to content

Unnecessary re-evals, especially in single-task mode? #357

Description

@YonatanGideoni

I've noticed that in execute_proposal in reflective_mutation.py there are two separate evaluation calls to the adapter. Isn't this re-evaluation sometimes wasteful? E.g. for circle packing the parent was presumably an accepted mutation at some point previously, so it already has been evaluated. In that case this is wasteful in terms of runtime, but if the evaluator uses LLM calls then it could also waste a budget up to twice as quickly vs if previous candidates' scores are cached.

Activity

  1. LakshyAAAgrawal commented on May 15, 2026

    @LakshyAAAgrawal
    Contributor

    Dear @YonatanGideoni, thanks for flagging this. This is a valid issue. We have a related issue here: #4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions