fix: run embedding novelty check before evaluation to avoid wasted compute#459
Open
octo-patch wants to merge 1 commit intoalgorithmicsuperintelligence:mainfrom
Open
Conversation
…mpute (fixes algorithmicsuperintelligence#439) When novelty checking is enabled, programs that are too similar to existing island programs were being fully evaluated before the similarity check rejected them. Move the embedding-based cosine similarity check into the worker process, executed immediately after code generation and before the expensive evaluation step. A global _worker_embedding_client is lazily initialized per worker using the same config as the database. The LLM-based novelty judge in database.add() is preserved as a fallback for borderline cases. Add tests for _pre_eval_novelty_check covering: disabled client, zero threshold, missing embeddings, similar code rejection, orthogonal code acceptance, and API error graceful handling. Co-Authored-By: Octopus <liyuan851277048@icloud.com>
|
octo-patch seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
1 similar comment
|
octo-patch seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #439
Problem
When novelty checking is enabled via
embedding_modelin the database config, the embedding-based similarity check was being called insidedatabase.add(), which runs after the program has already been evaluated. This means every program is fully evaluated (potentially running expensive external code) before discovering it's too similar to an existing program and getting rejected.Current flow:
database.add()→_is_novel()→ embedding similarity checkSolution
Move the embedding-based cosine similarity check into the worker process, executed immediately after code generation and before evaluation.
New flow:
database.add()→_is_novel()(still runs as a safety fallback)Implementation details:
_worker_embedding_clientglobal to worker process, lazily initialized in_lazy_init_worker_components()usingconfig.database.embedding_model_pre_eval_novelty_check()function that gets the embedding for the generated code and compares it with embeddings of existing programs in the target island (from the db snapshot)_run_iteration_worker()between code generation and evaluationdatabase.add()is preserved as a fallback for borderline casesTesting
tests/test_pre_eval_novelty_check.pycovering: