Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[QUBO] Warn users that current CPU backend not up to date with Loihi implementation #249

Closed
phstratmann opened this issue Aug 7, 2023 · 2 comments
Closed

[QUBO] Warn users that current CPU backend not up to date with Loihi implementation #249

phstratmann opened this issue Aug 7, 2023 · 2 comments
Assignees
@phstratmann
Labels
0-needs-review Has to be reviewed. 1-feature New feature or request

Comments

@phstratmann
Copy link
Contributor

User story

As a user, I want to be informed that the CPU backend shows substantially lower performance than the Loihi 2 backend.
@phstratmann phstratmann added the 1-feature New feature or request label Aug 7, 2023
@phstratmann phstratmann self-assigned this Aug 7, 2023
@github-actions github-actions bot added the 0-needs-review Has to be reviewed. label Aug 7, 2023
@tim-shea
Copy link
Contributor

tim-shea commented Aug 7, 2023

Deprecate normally means to mark something that will be removed in a future version or is not actively maintained. I don't see how that applies here.

@phstratmann phstratmann changed the title [QUBO] Deprecate CPU backend [QUBO] Warn users that current CPU backend not up to date with Loihi implementation Aug 7, 2023
@phstratmann
Copy link
Contributor Author

Deprecate normally means to mark something that will be removed in a future version or is not actively maintained. I don't see how that applies here.

Adjusted, @tim-shea

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

@phstratmann phstratmann

Labels
0-needs-review Has to be reviewed. 1-feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tim-shea @phstratmann