NoSQL
Hand the model a compatible, timely feature vector
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Connect serving document and model request to Match entity and feature definition. Inspect context_ok before applying time and value checks.
A serving lookup returned a document, but its contents still need to match this decision.
Inspect the component calculation
Match entity and feature definition( Serving document: Retrieved serving document Model request: Authorised model request )
Examples and results
- Retrieved serving document
{ "tenant": "north", "asset": "P7", "feature_version": "bearing-v2", "event_time": 100, "available_time": 105, "features": { "vibration": 0.8, "temperature": 30 } }- Authorised model request
{ "tenant": "north", "asset": "P7", "feature_version": "bearing-v2", "as_of": 110, "max_age": 20 }- Required result
{ "context_ok": true, "record": { "tenant": "north", "asset": "P7", "feature_version": "bearing-v2", "event_time": 100, "available_time": 105, "features": { "vibration": 0.8, "temperature": 30 } } }
- Retrieved serving document
{ "tenant": "north", "asset": "P7", "feature_version": "bearing-v1", "event_time": 100, "available_time": 105, "features": { "vibration": 0.8, "temperature": 30 } }- Authorised model request
{ "tenant": "north", "asset": "P7", "feature_version": "bearing-v2", "as_of": 110, "max_age": 20 }- Required result
{ "context_ok": false, "record": { "tenant": "north", "asset": "P7", "feature_version": "bearing-v1", "event_time": 100, "available_time": 105, "features": { "vibration": 0.8, "temperature": 30 } } }
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
The fixture checks a supplied document. It does not authenticate users, fetch historical versions, train a model or establish production safety. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
A valid context still lacks one required feature
This check uses the pieces from “Check and order a serving record”.
BOTIE
- Retrieved serving document
{ "tenant": "west", "asset": "P2", "feature_version": "pump-v3", "event_time": 200, "available_time": 204, "features": { "temperature": 28 } }- Authorised model request
{ "tenant": "west", "asset": "P2", "feature_version": "pump-v3", "as_of": 210, "max_age": 10 }- Model feature order
- 0temperature
- 1vibration
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
What should be retained so the team can reproduce the actual inputs used for a later-reviewed prediction?
Preserve appropriate model, definition and input references while keeping privacy, freshness and retention policies explicit.
The fixture checks a supplied document. It does not authenticate users, fetch historical versions, train a model or establish production safety.
Work through the Python challenges →