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
In DbAnalysisResultV1 there is a required field called device_components, which defines the target components of the analysis (e.g. qubits or resonators). Currently all analysis classes just specify qubits even when they should be resonators.
some experiment, such as resonator spectroscopy #90, will need to put Resonator instead of Qubit.
We need to generalize definition the target element, i.e. from qubits to device component.
Otherwise frequency value measured by the resonator spectroscopy experiment will be shown as
qubit frequency in result db.
The text was updated successfully, but these errors were encountered:
I think there are not many types of device components besides qubits and resonators, therefore generalizing these few lines to also enable resonators should be enough (like done in #387 ). By enabling only pre-determined types we can also make the searches in the DB easier.
If I am wrong, and there might be more types that we don't think of right now, I think that creating a method that other subclasses can override will indeed be a better solution.
Informations
What is the current behavior?
In
DbAnalysisResultV1
there is a required field calleddevice_components
, which defines the target components of the analysis (e.g. qubits or resonators). Currently all analysis classes just specify qubits even when they should be resonators.Steps to reproduce the problem
What is the expected behavior?
Suggested solutions
Per @nkanazawa1989 :
The text was updated successfully, but these errors were encountered: