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
Couple of bugs that we know exist and stem from ITensorNetworks.jl
If a ITensorNetwork function f maps to 0 for a given x (because its projection ends up with 0 tensors) then calling calculate_fx(f, x) will yield Nan because the BP contraction backend in ITensorNetworks.jl doesn't correctly handle 0 tensors. A small change to ITensorNetworks.jl should fix this. For now we have to do calculate_fx(f, x; alg = "exact") to deal with it.
There seem to be some numerical issues with calling a TNO-TNS contraction with contract(O::ITensorNetwork, f::ITensorNetwork) when the bond dimension of the TNS f is 1. This is presumably stemming from something in the TTN code in ITensorNetworks.jl
The text was updated successfully, but these errors were encountered:
Couple of bugs that we know exist and stem from
ITensorNetworks.jl
If a ITensorNetwork functionf
maps to0
for a givenx
(because its projection ends up with0
tensors) then callingcalculate_fx(f, x)
will yieldNan
because the BP contraction backend inITensorNetworks.jl
doesn't correctly handle0
tensors. A small change toITensorNetworks.jl
should fix this. For now we have to docalculate_fx(f, x; alg = "exact")
to deal with it.contract(O::ITensorNetwork, f::ITensorNetwork)
when the bond dimension of theTNS f
is1
. This is presumably stemming from something in theTTN
code inITensorNetworks.jl
The text was updated successfully, but these errors were encountered: