Skip to content

Bug: EOSP_self calculates wrong indices #11

@ifsheldon

Description

@ifsheldon

pos_eosp.append(pos_rec.pop(p_max))

I think here the code stores a wrong index number into pos_eosp, since in the end of every iteration, a MPS is projected and thus one local tensor (at p_max) of it gets removed, so all the indices following p_max will be shifted by 1. Essentially p_max is an index into the current MPS (which may be projected), not an index into the initial MPS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions