Some workflows may want to keep track of the history of the acquisition functions used throughout it, in the database. This is something we may want to support in DIAL.
A possible idea for a history struct:
class AcquisitionHistory(BaseModel):
strategy: Literal[...] # all strategies that we support
dataset_x_len: int # size of dataset_x at time user generated history; this includes masked values
dataset_y_len: int # size of dataset_y at time user generated history; this includes masked values
points: list[list[float]] # these are the points the model suggested, NOT necessarily accepted
We can make using this history optional per request, perhaps with a use_history: bool flag (default false) which can be stuck on the input Dataclasses. Not every workflow would need the history, and this would require an additional database call with each stateless function.
Some workflows may want to keep track of the history of the acquisition functions used throughout it, in the database. This is something we may want to support in DIAL.
A possible idea for a history struct:
We can make using this history optional per request, perhaps with a
use_history: boolflag (default false) which can be stuck on the input Dataclasses. Not every workflow would need the history, and this would require an additional database call with each stateless function.