2023-05-17 Leap Release¶
Reverse Annealing May Have Returned Low-Quality Solutions¶
An issue with the reverse-annealing
protocol, affecting all QPU solvers in Leap between April 19 and May 17, 2023,
may have compromised solution quality. This affected problems submitted with the
reverse-annealing protocol and the reinitialize_state
parameter set to
False; no other submissions were affected. For the affected
problems, the initial state was not correctly set.
If you submitted such problems during the relevant time frame, we recommend that
you resubmit them. Contact D-Wave Support if needed.
2023-04-05 Leap Release¶
Leap Hybrid CQM Solver Failed to Solve Some Previously Solved Problems¶
Because of a code error in version 1.8.0, the hybrid constrained quadratic model (CQM) solver failed to return feasible solutions to some problems previously solved by version 1.7.2.
2023-03-22 Leap Release¶
2023-03-08 Leap Release¶
2023-02-22 Leap Release¶
Leap’s Advantage_system4.1 QPU: Performance Temporarily Degraded¶
From about 0200 to 0800 Pacific time on February 21, 2023, the Advantage_system4.1 QPU’s performance had degraded.
2023-01-25 Leap Release¶
Leap Hybrid BQM Solver: Some Problems Failed with an Illegal Memory Access Error¶
Certain jobs sent to the hybrid binary quadratic model (BQM) solver failed with the following error message:
cuMemAlloc failed: an illegal memory access was encountered.
2022-10-05 Leap Release¶
Leap CQM Hybrid Solver: Problems in Pending State Longer Than Expected¶
On September 30, 2022, problems submitted to Leap CQM hybrid solvers might have remained in a pending state longer than expected.
2022-08-24 Leap Release¶
Leap Admin: Solver Usage Report Data for End Date Was Not Included¶
On the Reporting tab, the date in the End Date field for the Custom Range option was not inclusive; that is, solver usage data on the specified end date was not included in the solver usage report.
2022-07-27 Leap Release¶
Some CQM Problems May Have Taken Longer Than Expected to Solve¶
For some problems with self-loops, the Leap Constrained Quadratic Model (CQM) solver may have run longer than expected, possibly exceeding the specified time_limit. The amount of excess runtime was proportional to the problem size; users were not charged for the excess runtime.
2022-07-13 Leap Release¶
pip freeze and
pip list Did Not Output Python System Packages By Default¶
pip commands for the Leap IDE were configured for user mode.
pip freeze or
pip list did not output
the IDE workspace’s preinstalled Python packages
by default because they were installed as system packages.
To output these IDE workspace packages, you had to use the
As of this release, the
pip commands for the Leap IDE are no longer configured
for user mode and the output of
pip freeze or
pip list also includes
the IDE workspace packages by default.
2022-06-29 Leap Release¶
Leap IDE and Leap Sessions Could Have Been Out-of-Sync¶
Your Leap session could have timed out while you were logged in to a Leap IDE session. Consequently, you might still have been able to use your workspaces, but when submitting problems an error would have occurred fetching the API token.
2022-06-01 Leap Release¶
Solver-Access Time Incorrectly Displayed for Expired/Inactive Projects¶
After a user accepted their invitation and became active in a project that was expired or had not been activated yet, their maximum solver-access time was incorrectly displayed as 0 (zero) in the Solver Access Time column on the Users tab. This issue was display-only; the system correctly maintained the user’s maximum solver-access time.
2022-05-04 Leap Release¶
Changing Unit of Time Incorrectly Converted Solver-Access Time¶
If the Project Member Default Solver Access Time field contained a value greater than or equal to 60 and you changed the unit of time, the value was incorrectly converted.
2022-03-09 Leap Release¶
Leap Dashboard Incompletely Displayed Large Problem Results¶
Large problem results (for example, those from large hybrid jobs) sometimes take too long to process and are not displayed on the Solution and Timing tabs of the problem details dialog box, which opens when you click on your problem in the Problem Status section of the dashboard.
2022-02-16 Leap Release¶
Solver Time Used Was Sometimes Incorrectly Displayed¶
From 12 January to 15 February 2022, the solver access time was sometimes incorrectly displayed in the Leap Dashboard’s Time Used field and the Leap Admin solver usage reports.
This issue was display-only; the system correctly recorded solver usage.
If you need corrected solver usage data for the affected dates, then rerun solver usage reports for those dates.
2022-02-09 Leap Release¶
Two Problem Submissions Incorrectly Failed¶
Due to a system error, two problem submissions incorrectly failed and returned an internal SAPI error.
Failed problem submissions do not consume any solver access time.
2021-12-01 Leap Release¶
Incorrect QPU Plots in Documentation¶
The Energy (Joules) scale’s exponent for the annealing schedule plots in the following documents was incorrect. The plots have now been corrected.
QPU Solver Datasheet (specifically, the annealing functions plot)
The following Physical Properties documents on the QPU-Specific Characteristics page:
QPU-Specific Physical Properties: Advantage_system3.2
QPU-Specific Physical Properties: Advantage_system4.1
QPU-Specific Physical Properties: Advantage_system5.1
QPU-Specific Physical Properties: DW_2000Q_6
2021-11-17 Leap Release¶
Usage Statistics Graph Displayed Incorrectly on Leap Dashboard¶
The following issue, present in the previous release of the Leap Dashboard pages, is now resolved:
Usage Statistics Graph May Be Displayed Incorrectly
2021-11-03 Leap Release¶
Leap Administration Not Resending Invitations¶
The following issue, present in the previous release of the Leap Admin pages, is now resolved:
Resend Invitation Does Not Work
2021-10-20 Leap Release¶
Readout Fidelity Issue in Advantage_system4.1¶
Some qubits on the Advantage_system4.1 QPU suffered a slight degradation in readout fidelity.
2021-10-13 Leap Release¶
Resolved Issues Affecting Leap Administration¶
The following issues, present in the previous release of the Leap Admin pages, are now resolved:
Cannot edit Customer Reference ID field
Assign Project Admin menu missing
Adding email addresses to invitations fails due to mismatched letter casing
2021-09-27 Leap Release¶
Leap IDE Workspace Outage¶
From September 9 to September 14, 2021, users were unable to access existing workspaces and create new ones in the Leap IDE.
Problems Completed Panel in the Leap Dashboard is Overbroad¶
In previous releases, in the Problem Completed panel on the Leap dashboard, the total number of completed problems shown included canceled and failed problems. However, such problems did not decrement solver access time and they did not appear in the usage statistics that show problems completed over time.
2021-08-25 Leap Release¶
DQM Solver Scaling Issue¶
In previous releases, the hybrid_discrete_quadratic_model_v1 solver returned different quality results for the same problem submitted at different scales.
QPU Access Time Issue in Leap Dashboard¶
In previous releases, the QPU access time used by a hybrid problem was incorrectly displayed on the Leap dashboard. For example, a problem with QPU access time of 32,519 microseconds was shown in the in the dashboard as 0.33 seconds instead of 0.033 seconds. This display-only issue was limited to the Leap dashboard: the Ocean response object reported the QPU access time correctly.
2021-02-10 Leap Release¶
Energy Offset Issue Affecting Some Hybrid Problems¶
Some customers may have encountered an issue where the energy offset was
dropped for some sparse problems submitted to the
MFA Email Issue¶
Some customers may have received multiple multi-factor authentication (MFA) emails when logging into Leap.
2021-01-13 Leap Release¶
Incorrect Energies Returned by Hybrid Solver¶
This release resolves an issue where some problems
hybrid_binary_quadratic_model_version2 returned noticeably incorrect energies.
2020-11-04 Leap Release¶
Failures on Version 2 of Hybrid BQM Solver¶
This release resolves an issue that affected problems submitted to the following hybrid solver:
Previously, problems with over 20,000 variables submitted to this solver may have failed.
Affected problems did not consume any solver access time.