Solver Decommissioning


We are transitioning the DW_2000Q_5 and DW_2000Q_VFYC_5 solvers to the DW_2000Q_6 and DW_2000Q_VFYC_6 solvers.


This will happen on May 11th, 2020 at 17:00 PT to May 19th, 2020 at 17:00 PT. Once the change-over has completed, the DW_2000Q_5 and DW_2000Q_VFYC_5 solvers will no longer be accessible. The hybrid solver service will not be affected.

Users who are doing research dependent upon chip topology will need to to manually choose the DW_2000Q_6 and DW_2000Q_VFYC_6 solvers going forward.


The DW_2000Q_6 solver has a different working graph and annealing schedule than the DW_2000Q_5 solver, so some users might need to be aware of this when running existing problems on the new solver. 
For more information, please see the links in this article:  https://support.dwavesys.com/hc/en-us/sections/360001452634
 

If you are doing research that is chip dependent, to ensure you can still access the QPU, you may need to refactor your project or setup by:

  1. Replacing hard coded sampler calls in your code to feature-based solver selection
  2. Changing the default solver in your dwave.conf file to DW2000Q_6 so you can call samplers without input parameters (ex. sampler = DWaveSampler() )

For example, to refactor a hard coded sampler call you would change

sampler = DWaveSampler(solver='DW_2000Q_5')

to

sampler = DWaveSampler(solver={'qpu': True})

Here is more information on setting up your configuration file for feature-based solver.


Please feel free to reach out to us with any questions or concerns.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

3 comments
  • Would you tell me when the DW_2000Q_5 will be unavailable ?
    May 19th, 2020 at 17:00 PT ?
    Our product use DW_2000Q_5 directly.
    We are fixing that now.

    1
    Comment actions Permalink
  • That is correct.
    The DW_2000Q_5 solver will be unavailable as of 17:00 PT on May 19th, 2020.

    We apologize for any inconvenience.
    Thank you for your understanding, and for reaching out to us with your questions.

    0
    Comment actions Permalink
  • Thank you for you answer.
    We fix by then.

    1
    Comment actions Permalink

Please sign in to leave a comment.