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

Allowing more flexible parametrization of the cost estimate functions #768

Open
PabloAMC opened this issue Feb 6, 2022 · 0 comments
Open

Comments

@PabloAMC
Copy link

PabloAMC commented Feb 6, 2022

In the recent cost estimates functions, there are a number of hardcoded parameters in the system:

for logical_data_qubit_distance in range(7, 35, 2):
params = AlgorithmParameters(
physical_error_rate=physical_error_rate,
surface_code_cycle_time=datetime.timedelta(microseconds=1),
logical_data_qubit_distance=logical_data_qubit_distance,
magic_state_factory=factory,
toffoli_count=num_toffoli,
max_allocated_logical_qubits=num_logical_qubits,
factory_count=4,
routing_overhead_proportion=0.5,
proportion_of_bounding_box=portion_of_bounding_box)
cost = params.estimate_cost()
if cost.algorithm_failure_probability > 0.1:

Should we add them as parameters to some class that the user can willingly change?

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

No branches or pull requests

1 participant