Skip to content

Program silently exits without solving if DWave is used #3

@nicholas-miklaucic

Description

@nicholas-miklaucic

If running with at_dwave set to True, this line causes the program to stop before actually solving the problem:

I assume this is meant to be a debugging aid to avoid accidentally using up your allotted time on DWave hardware, but it's quite confusing for new users who see output indicating that the system is using a quantum annealer but then don't see any output or usage on their account.

Is there a reason for the exit() call that I'm missing?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions