Skip to content

Should JordanMPOTensor be reworked? #424

@kshyatt

Description

@kshyatt

This grew out of a Zulip discussion with @lkdvos and I thought I should create an issue in order to not lose track of it and get feedback from others.

Right now, JordanMPOTensor wraps a SparseBlockTensorMap which itself has a Union{BraidingTensor, TensorMap} for its element type. This leads to lots of annoying storage type inference problems and many other sad situations.

It might rather be better to simply store either:

  • two separate SparseBlockTensorMaps
  • or one for the TensorMaps and just an array of scalars (this was Lukas' suggestion and I am too group-retreat drained to comment much on what it would look like)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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