-
Notifications
You must be signed in to change notification settings - Fork 209
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
Parallelize the QubitMapper
routines
#771
Comments
This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling qiskit-community#771
This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling qiskit-community#771
This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling qiskit-community#771
This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling qiskit-community#771
Maybe this could be stated more generally as improve performance of QubitConvertor. This would allow Rust to be considered and threads etc as need. If the convertor can be given an iterator of some form then whether the operator content is created on demand as the iterator progresses or its all there up front will be transparent to the convertor though may limit how the operator is parceled out for concurrent conversion. |
* refactor: enable dict_aux_operators by default * refactor: deprecate qiskit_nature.ListOrDict This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling #771 * refactor: match return type of `BaseProblem.second_q_ops()` to Terra The algorithms in Terra always take a tuple of the main operator and some auxiliary operators. This commit changes the `BaseProblem` interface to already return the generated operators in the same format. This simplifies the handling of the main operator, a scenario that occurs very often and required manual intervention thus far.
QubitConverter
routinesQubitMapper
routines
* refactor: enable dict_aux_operators by default * refactor: deprecate qiskit_nature.ListOrDict This removes the usage of ListOrDict wherever possible. The QubitConverter class is the last place this is needed, because the UCC and UVCC ansatze pass their excitation operators for conversion as a list. That is fine for now, but may be improved when tackling qiskit-community#771 * refactor: match return type of `BaseProblem.second_q_ops()` to Terra The algorithms in Terra always take a tuple of the main operator and some auxiliary operators. This commit changes the `BaseProblem` interface to already return the generated operators in the same format. This simplifies the handling of the main operator, a scenario that occurs very often and required manual intervention thus far.
What is the expected enhancement?
It should be possible to improve the
QubitMapper
class by parallelizing its internal processes.We may also want to look into implementing generator routines which would allow "lazy conversion" of operators (assuming that we have lazy operator generation).
Note: This is a long-term goal and does not have immediate priority.
The text was updated successfully, but these errors were encountered: