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.

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

added wrapped decoherence #377

Merged
merged 1 commit into from
Aug 24, 2023
Merged

added wrapped decoherence #377

merged 1 commit into from
Aug 24, 2023

Conversation

TysonRayJones
Copy link
Member

Added all decoherence channels which can be directly mapped (without unacceptable performance damage) to a cuQuantum call.

The cuQuantum calls are:

  • custatevecApplyMatrix
  • custatevecApplyGeneralizedPermutationMatrix

and are called with matrices (some, diagonal) describing the channel superoperators.

The remaining decoherence channels require linearly combining device vectors (may use Thrust), bespoke GPU kernels, or a clever decomposition of the channel (e.g. 2 qubit depolarising) into a sequence of cuStateVec calls

Added all decoherence channels which can be directly mapped (without unacceptable performance damage) to a cuQuantum call.

The cuQuantum calls are:
- custatevecApplyMatrix
- custatevecApplyGeneralizedPermutationMatrix

and are called with matrices (some, diagonal) describing the channel superoperators.

The remaining decoherence channels require linearly combining device vectors (may use Thrust), bespoke GPU kernels, or a clever decomposition of the channel (e.g. 2 qubit depolarising) into a sequence of cuStateVec calls
@TysonRayJones TysonRayJones merged commit 67153b9 into cuquantum Aug 24, 2023
5 of 6 checks passed
@TysonRayJones TysonRayJones deleted the cuquantum-decoherence branch August 24, 2023 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant