You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows us to support some usage for special purpose.
Proposed Solution
Let me explain it by the following example, partial trace (although we already have ptrace, but I just want to show how I expect type = Composed would work) :
# suppose we have two subsystems A and B
NA =4
NB =2
IB =qeye(NB)
rhoAB =rand_dm((NA, NB))
basis_list = [ tensor(basis(NA, i), IB) for i in0:(NA-1)]
Problem Description
In QuTiP, the
dims
describes the Hilbert space information separately for left and right basis of theOperator
, whereQuantumToolbox.jl
does not.Here, I suggest a new type
ComposedQuantumObject
(not necessary to be this name), where the definition is as followsThis allows us to support some usage for special purpose.
Proposed Solution
Let me explain it by the following example, partial trace (although we already have
ptrace
, but I just want to show how I expecttype = Composed
would work) :The partial trace can actually be obtained as
That is,
The main thing is to support some basic functions like
kron
for two differentQobj
typeadjoint
of Composed*
between Operator and Composed ->Composed
*
between Composed and Composed ->Operator
Alternate Solutions
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: