Do not deduplicate against FAILED in GenerationStrategy/Node #2488
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.
Summary:
We have an implicit rule that the
ABANDONED
trials failed deterministically and should not be generated again, whileFAILED
trials are unknown and may be generated again if the model chooses to do so. This rule is encoded in the utilities used to extractpending_observations
from experiment while generating candidates, which countsCANDIDATE
(as of D57514290),STAGED
,RUNNING
&ABANDONED
trials. TheEARLY_STOPPED
andCOMPLETED
trials have data associated with them, which was a similar effect topending_observations
in discouraging the models from generating them again. Notably,FAILED
trials do not fall into either category, thus they are fair game for the model to generate again, if it determines that to be the optimal next step.This conflicts with the current deduplication against
experiment.arms_by_signature
which includes all arms on the experiment regardless of the trial status. To make the behavior consistent, this diff adds a newarms_by_signature_for_deduplication
property on theExperiment
that excludes arms attached to theFAILED
trials.Differential Revision: D57478100