Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execution parameters in protocols #890

Open
alecandido opened this issue Jun 19, 2024 · 0 comments
Open

Execution parameters in protocols #890

alecandido opened this issue Jun 19, 2024 · 0 comments

Comments

@alecandido
Copy link
Member

As pointed out in #887, sometimes the routines might want to specify the ExecutionParameters by themselves.

However, direct usage of params.execution_parameters would be advantageous for all the routines, since it would leave the freedom to the caller to always override the parameters.
Still, when parameters are not specified, some default values should be clearly routine-dependent (in particular, acquisition_type and averaging_mode).

Thus, we should enforce the internal usage of params.execution_parameters everywhere, but leave some space for the routine implementor to specify a default value, to be carefully used.
If there is no special default value to recommend (like it will be always, or almost always, the case for nshots and relaxation_time), it should be left empty in the routine, and just use the one determined globally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant