You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be useful to have more flexible operations at hand with the protocols.
In particular, you may want to invoke only part of a routine.
E.g. it may be useful to acquire data with one protocol, and fit with another one (or "manually"), but then use again the original protocol's plot.
The original idea of protocols is to bundle together elements that are closely related, since they will be most often executed together. Nevertheless, allowing more atomic access may enhance composition.
Technical proposal
Instead of returning a dynamically defined function from Executor.__getattribute__
the access operation may return an instance of an object, whose __call__ method will reproduce the current behavior of wrapper(), but that will allow accessing the other stages (functions) and attributes (types) through dedicated methods (e.g. .acquisition and .fit), while still registering the execution results in the History as much as possible.
The text was updated successfully, but these errors were encountered:
It may be useful to have more flexible operations at hand with the protocols.
In particular, you may want to invoke only part of a routine.
E.g. it may be useful to acquire data with one protocol, and fit with another one (or "manually"), but then use again the original protocol's plot.
The original idea of protocols is to bundle together elements that are closely related, since they will be most often executed together. Nevertheless, allowing more atomic access may enhance composition.
Technical proposal
Instead of returning a dynamically defined function from
Executor.__getattribute__
qibocal/src/qibocal/auto/execute.py
Line 204 in 5ff3d90
the access operation may return an instance of an object, whose
__call__
method will reproduce the current behavior ofwrapper()
, but that will allow accessing the other stages (functions) and attributes (types) through dedicated methods (e.g..acquisition
and.fit
), while still registering the execution results in theHistory
as much as possible.The text was updated successfully, but these errors were encountered: