Skip to content

Fix density matrix trace drift after measurement collapse#8171

Open
anshjaiswal12 wants to merge 6 commits into
quantumlib:mainfrom
anshjaiswal12:fix/density-matrix-trace-5916
Open

Fix density matrix trace drift after measurement collapse#8171
anshjaiswal12 wants to merge 6 commits into
quantumlib:mainfrom
anshjaiswal12:fix/density-matrix-trace-5916

Conversation

@anshjaiswal12

@anshjaiswal12 anshjaiswal12 commented Jun 30, 2026

Copy link
Copy Markdown

Summary

After a measurement collapse, measure_density_matrix divides by the outcome probability. Floating-point error can leave the density matrix with trace slightly ≠ 1. Reusing final_density_matrix as initial_state compounds that drift (gh-5916).

Renormalize by trace after collapse and add regression tests.

Fixes #5916

Tests

  • test_density_matrix_trace_after_each_moment_gh5916
  • test_density_matrix_trace_stable_under_repeated_simulation
  • test_density_matrix_trace_stable_across_circuit_families
  • test_density_matrix_trace_repeated_simulation_performance_smoke

AI disclosure: Cursor IDE was used only to read/search the codebase and help debug the issue. All code in this PR was written and reviewed by me.

Post-measurement normalization by outcome probability can leave the
density matrix with trace slightly off 1; reusing it as initial_state
compounds the error. Renormalize by trace after collapse and add
regression tests that check trace at each simulation step.

Fixes quantumlib#5916
@anshjaiswal12
anshjaiswal12 requested a review from a team as a code owner June 30, 2026 07:09
@anshjaiswal12
anshjaiswal12 requested a review from dstrain115 June 30, 2026 07:09
@google-cla

google-cla Bot commented Jun 30, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@github-actions github-actions Bot added the size: M 50< lines changed <250 label Jun 30, 2026
Pull post-measurement trace correction into _renormalize_density_matrix_trace,
use np.isclose for the zero-trace guard, and deduplicate the quantumlibgh-5916 regression
circuit in tests.
@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.60%. Comparing base (daf1fa6) to head (a6db169).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8171   +/-   ##
=======================================
  Coverage   99.60%   99.60%           
=======================================
  Files        1118     1118           
  Lines      101349   101411   +62     
=======================================
+ Hits       100945   101007   +62     
  Misses        404      404           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

anshjaiswal12 and others added 2 commits July 2, 2026 00:34
Collapse _assert_density_matrix_trace_one signature to one line to
satisfy the incremental format check on CI.

@mhucka mhucka left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this work! Here are a few comments.

def _renormalize_density_matrix_trace(
density_matrix: np.ndarray, qid_shape: tuple[int, ...]
) -> None:
"""Rescale ``density_matrix`` in-place so its trace is 1."""

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Single backquotes around symbols, not double.

Suggested change
"""Rescale ``density_matrix`` in-place so its trace is 1."""
"""Rescale `density_matrix` in-place so its trace is 1."""



def _gh5916_regression_circuit() -> cirq.Circuit:
"""Circuit from gh-5916 that previously drifted trace under re-simulation."""

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the Cirq project, we have generally refrained from using a shorthand like "gh-N" for referring to issues and PRs. Could you change this to provide an actual URL in the string? The function name also doesn't need gh5916 in it.

Comment on lines +1593 to +1594
q0, q1 = cirq.NamedQubit('q0'), cirq.NamedQubit('q1')
return cirq.Circuit(cirq.CNOT.on(q1, q0), cirq.H.on(q1), cirq.measure(q1))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This compact code may seem efficient (and this was probably generated by an LLM, right?), but for human readers this is more difficult to interpret than necessary. Can you rewrite this to use simpler, one-per-line steps?

Comment on lines +1670 to +1671
q0, q1 = cirq.LineQubit.range(2)
circuit = cirq.Circuit(cirq.CNOT(q1, q0), cirq.H(q1), cirq.measure(q1))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above about readability and interpretability due to overly compact coding.

@anshjaiswal12

Copy link
Copy Markdown
Author

thank you, Michael! I really appreciate you taking the time to leave such detailed comments, this has been one of the most valuable reviews I've received because the feedback is specific and actionable. I'll go through each comment, make the necessary changes, and update the PR. thanks again for helping improve my contribution!

@anshjaiswal12

Copy link
Copy Markdown
Author

Hi @mhucka , thanks again for the detailed review. I've addressed all the comments:

Updated the docstring to use single backticks and "in place" (two words).
Renamed _gh5916_regression_circuit to _trace_drift_regression_circuit and replaced all gh-5916 shorthands with the full issue URL.
Rewrote both compact circuit constructions to use one-per-line circuit.append() steps.
All local checks pass (./check/all --changed — formatting, ruff, mypy, pytest, and coverage). Please let me know if anything else needs adjustment.

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

Labels

size: M 50< lines changed <250

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Density matrix traces not remaining at 1 after certain operations

3 participants