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

Decouple backend-specific functionality from benchmarking #52

Open
vprusso opened this issue Dec 3, 2024 · 0 comments
Open

Decouple backend-specific functionality from benchmarking #52

vprusso opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
refactor Code restructuring
Milestone

Comments

@vprusso
Copy link
Contributor

vprusso commented Dec 3, 2024

The bench.py file contains components that should be extracted into a separate module. For instance, any functions that pertain to acquiring the backend, circuit transpilation, etc. should all be moved. The common aspect of these functions include some aspect of obtaining an object or property that is contingent on the backend requested.

For instance, for the get_backend function, the object that is returned is the object that corresponds to the backend device for the requested backend. The transpile_circuit function transpile the input circuit on the requested backend, etc.

Perhaps this functionality would be best placed in something like a provider.py/device.py/etc. This can change as the project evolves, but it's clear that this should not be in the bench.py file.

@vprusso vprusso added the refactor Code restructuring label Dec 3, 2024
@vprusso vprusso added this to the Release 0.1.0 milestone Dec 3, 2024
@cosenal cosenal self-assigned this Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Code restructuring
Projects
None yet
Development

No branches or pull requests

2 participants