Skip to main content

AssistantMissionHoldout

The test period an IMPROVE_STRATEGY Mission judges its best variant on (T-FU-MISSION-HOLDOUT-CONSENT). Sealing it is PERMANENT for the strategy's whole lineage: no hyperopt of any version may ever use that window again. So when the lineage has none yet, the Mission cannot start until the owner consents to this exact window (approveAssistantMissionBudget's holdoutConsent), and the seal then covers exactly that window.

type AssistantMissionHoldout {
  strategyName: String!
  start: Time!
  end: Time!
  days: Int!
  existing: Boolean!
  consentRequired: Boolean!
  consented: Boolean!
  minDays: Int!
  maxDays: Int!
}

Fields​

AssistantMissionHoldout.strategyName ● String! non-null scalar​

The strategy whose lineage the holdout belongs to.

AssistantMissionHoldout.start ● Time! non-null scalar​

Start of the window (inclusive, midnight UTC).

AssistantMissionHoldout.end ● Time! non-null scalar​

End of the window (exclusive, midnight UTC).

AssistantMissionHoldout.days ● Int! non-null scalar​

Length of the window in whole days.

AssistantMissionHoldout.existing ● Boolean! non-null scalar​

True when the lineage already has a sealed holdout: the Mission uses it as it is and asks for no consent.

True when approving the budget must carry holdoutConsent: the lineage has no holdout and the owner has not consented yet.

AssistantMissionHoldout.consented ● Boolean! non-null scalar​

True once the owner consented to seal this window.

AssistantMissionHoldout.minDays ● Int! non-null scalar​

Shortest window the owner may pick, in days.

AssistantMissionHoldout.maxDays ● Int! non-null scalar​

Longest window the owner may pick, in days.

Member Of​

AssistantMission object