-
Notifications
You must be signed in to change notification settings - Fork 61
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
Transpiler padding #1429
Comments
@Simone-Bordoni can you take a look at the description? I'm not asking you to implement anything of what I described. And maybe it's not even urgent to anything at all. But at least I would have a consistent issue for when someone will be able to take over the project. |
Similarly, I'd like to open an issue about the naming of qubits and nodes in the connectivity graph. Would it be better to discuss this here, or should I create a separate issue? |
The two things are related, and they will be most likely solved together. Feel free to discuss it even here :) |
Currently, the transpiler is designed to interpret integer connectivity graph nodes qibo/src/qibo/transpiler/placer.py Lines 203 to 205 in 21732ad
For example, consider the connectivity graph: and the physical-to-logical mapping:
If we want to enable custom string names for qubits, the naming scheme will need to be updated. Possible options are:
|
At the moment it is possible to select a subset of qubits in the connectivity when defining a transpiling pipeline (PR #1121). |
Yes, indeed. That's why I linked immediately qiboteam/qibolab#1009, as a "dependency" of this issue (there are parts of this issue that could be worked on before, but that has to be solved first to complete this). |
Thanks, then I will update the |
Currently, the transpiler is already providing some padding
qibo/src/qibo/transpiler/optimizer.py
Lines 19 to 33 in ecbd16d
but just applying the basic approach, i.e. padding at the end.
However, there is not much more that can be done at the moment, since Qibolab does not support using its own qubits' names in circuits.
qiboteam/qibolab#1009
As soon as that will be available, it would be interesting to offer the option to choose which subset of qubits should be targeted. And applying padding only at the end.
This last part could be done even immediately: sometimes it may be interesting to route a circuit on a subset of the whole qubits and connectivity (even though some subsets will make impossible to execute some circuits), so padding as preprocessing and padding as postprocessing are truly two different features, and only the first is currently available (unless I'm missing something).
The text was updated successfully, but these errors were encountered: