Yong-Yue Zong

Some feedback: 1.Using ```TensorKit.set_blockscheduler!(:dynamic)``` throws an error: ```julia ERROR: LoadError: MethodError: no method matching setindex!(::ScopedValue{Scheduler}, ::DynamicScheduler{OhMyThreads.Schedulers.FixedCount, ChunkSplitters.Consecutive}) The function `setindex!` exists, but no method is defined for this combination of...

In the second case, I changed bAs and bBs to dicts, and the program ran successfully. I then simulated a Hubbard model of size 2×5 with D=512 and found that...

``add!`` throws an error now: ```julia Warning: The function `add!` is not implemented for (values of) type `Tuple{Base.ReshapedArray{Float64, 2, SubArray{Float64, 1, Vector{Float64}, Tuple{UnitRange{Int64}}, true}, Tuple{}}, Float64, VectorInterface.One, VectorInterface.One}`; │ this...

Thank you very much for your prompt fix -- it has resolved all the bugs I have found.

Possible bug? In multithreading, using SU(2) symmetry causes @planar to throw an error, but using only U(1) symmetry does not: ```julia TensorKit.with_blockscheduler(DynamicScheduler()) do TensorKit.with_subblockscheduler(DynamicScheduler()) do E = e_plus(Float64, SU2Irrep, U1Irrep;...

eplus is the same creation operator you originally had in MPSKitModels, except that I added a filling parameter. Setting filling = (1,1) is fine. ```julia function e_plus(elt::Type{1, (1,1//2,Q-P)=>1, (0,0,2*Q-P)=>1) vspace...

The bug occurs when e_min is created, this is the full error info: ```julia ERROR: LoadError: ArgumentError: Arguments of type Base.Iterators.ProductIterator{Tuple{Base.Iterators.ProductIterator{Tuple{TensorKitSectors.SectorSet{ProductSector{Tuple{FermionParity, SU2Irrep, U1Irrep}}, TensorKit.var"#93#94"{GradedSpace{ProductSector{Tuple{FermionParity, SU2Irrep, U1Irrep}}, TensorKit.SortedVectorDict{ProductSector{Tuple{FermionParity, SU2Irrep, U1Irrep}}, Int64}}},...