Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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
Make VF2Layout pass Target aware #7735
Make VF2Layout pass Target aware #7735
Changes from 9 commits
b2c9f70
ac451bd
23c0ad1
668731f
4005d94
1daa36b
5dc8b15
7ffec34
f7fb8a5
f167996
1355d86
81a2897
c8766ad
eea2444
1253533
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pre-existing and doesn't need to be changed (nor should it, this close to release!), but it's weird to me that this path doesn't divide by the size of the graph, unlike other paths this approximation is used in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's mostly a matter of relative values on the other qubits for the heuristic score that's returned. In the other paths when we have an error rate on some qubits that's always going to be < 1. So in the other paths we divide by the number of nodes in the absence of an error rate to make the value < 1 to hopefully not score super unfavorably towards qubits that could be potentially good and just happen to be missing an error rate in the backend but are still defined in the connectivity graph.
In the case of this path when we have no error rates it doesn't really matter because all the other scores are going to be in the same situation so we want to prefer to use a node with lower degree. We could divide but we don't have to as it wouldn't change the relative score compared to the other qubits.