Skip to content

CLS-8340: cap maxwell_2d_simulation width at 25 for the new synthesis flow#1618

Open
din-carmon wants to merge 1 commit into
mainfrom
CLS-8340-maxwell-new-flow-width
Open

CLS-8340: cap maxwell_2d_simulation width at 25 for the new synthesis flow#1618
din-carmon wants to merge 1 commit into
mainfrom
CLS-8340-maxwell-new-flow-width

Conversation

@din-carmon

Copy link
Copy Markdown
Collaborator

Context

maxwell_2d_simulation synthesizes with Preferences(symbolic_loops=True, transpilation_option=NONE) and Constraints(max_width=1000). Under the new synthesis flow, the block-encoding ancillas (LCU / within_apply / GQSP) are not reused the way the legacy flow reuses them, so the program comes out at ~411 qubits and fails the notebook test's validate_quantum_program_size(expected_width=25).

Change

Cap max_width at 25 in run_simulation. This forces the new flow to reuse qubits and fit within budget (resulting width 25), and remains satisfiable for the legacy flow (already ~20). The algorithm and physics result are unchanged - only the qubit-allocation budget.

Validation

Synthesized the real model in-process through the new flow (RunNewSynthesis.ALWAYS):

  • data.width = 25 (was 411)
  • export / metrics succeed (no QASM-version crash)

Note: this depends on the QASM-version-inference fix in Cadmium (CLS-8340) for the export path; the width cap addresses the separate size check.

🤖 Generated with Claude Code

… flow

The new synthesis flow does not reuse the block-encoding ancillas the way the
legacy flow does, so synthesizing maxwell_2d_simulation with an effectively
unbounded max_width (1000) produced a ~411-qubit program and failed the
notebook size check (expected_width=25). Constraining max_width to 25 makes the
new flow reuse qubits and fit within the budget (resulting width 25), while
remaining satisfiable for the legacy flow (which is already ~20).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

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