Skip to content

Fix conversion to NonCanonical from canonical forms with LambdaSite #371

Description

@mofeing

Currently, we just set the form to be NonCanonical but we don't absorb the lambda tensors which leave them in a dangling situation that may fail on operations that expect the Tensor Network in its normal form.

It might be wiser to absorb the LambdaSites whenever we convert to NonCanonical.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions