Make extractors more consistent; update germanium #4068
Merged
Conversation
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
sasmith
changed the title
relh
approved these changes
Dec 1, 2025
zfogg
pushed a commit
that referenced
this pull request
Dec 20, 2025
This makes some elements of extractor usage more consistent. Notably: * All extractors now use efficiency in a way that's scaled to 100. Previously most extractors expected efficiency to be ~100, and germanium expected it to be ~2. * Germanium now uses max_uses to determine its cooldown, versus the amount of germanium produced. Notably, germanium now has cooldown. * All extractors now use max_uses. This changes an invariant of Germanium having max_uses of 1. * All extractors can have have synergy. This is on by default for germanium, but everything can scale its output based on the number of agents there. * Probably one of the biggest impacts of synergy is that it allows more total production -- not just more production over time. We may need / want to tweak this in the future. In order of importance: * Having germanium use a typical efficiency of 100 seems pretty valuable for consistency in what efficiency means. * Having germanium be multi-use and have cooldown helps us work around an issue we've repeatedly had in training examples where there's one extractor and it runs out and then there's nothing to do. Germanium is still clearly distinct from carbon and silicon, since they don't do cooldowns. It's now more like oxygen, but it's default coop, so maybe distinct enough. * Allowing everything to have synergy homogenizes how we think about resource settings, and gives more potential places for multi-agent cooperation. But it's something we'll need to play with. This PR will mess up existing evals where we're setting the germanium extractor's Co-authored-by: S. Alex Smith <sasmith@stem.ai>
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.
This makes some elements of extractor usage more consistent. Notably:
In order of importance:
This PR will mess up existing evals where we're setting the germanium extractor's