Skip to content

fix(#48): _simulate_values now uses cost model fidelity and warns users - #100

Merged
Manideep3969 merged 1 commit into
mainfrom
fix/issue-48-simulate-values-fidelity
Aug 20, 2026
Merged

fix(#48): _simulate_values now uses cost model fidelity and warns users#100
Manideep3969 merged 1 commit into
mainfrom
fix/issue-48-simulate-values-fidelity

Conversation

@Manideep3969

Copy link
Copy Markdown
Owner

Fixes _simulate_values which used hardcoded fidelity=0.85. Now uses cost_model.estimate_fidelity for actual circuit fidelity, falling back to 0.85 only when no circuit is available. Emits UserWarning when simulated values are used. 3 new regression tests. All 347 tests pass.

_simulate_values used a hardcoded base_fidelity=0.85 instead of the
cost model's fidelity estimate, producing arbitrary results without
any warning to users.

Fix: Store the circuit in execute() and use cost_model.estimate_fidelity
to get actual circuit fidelity. Fall back to 0.85 only if no circuit
is available. Emit UserWarning when simulated values are used.
@Manideep3969
Manideep3969 merged commit cc7a929 into main Aug 20, 2026
4 checks passed
@Manideep3969
Manideep3969 deleted the fix/issue-48-simulate-values-fidelity branch August 20, 2026 06:17
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

Successfully merging this pull request may close these issues.

1 participant