Skip to content

chore: clarify user input convention for multiorbital non-reciprocal models - #12

Open
marcelolooser wants to merge 3 commits into
HyperCells:masterfrom
marcelolooser:chore/no-ref/NonReciprocalAbelianBlochHamiltonian
Open

chore: clarify user input convention for multiorbital non-reciprocal models#12
marcelolooser wants to merge 3 commits into
HyperCells:masterfrom
marcelolooser:chore/no-ref/NonReciprocalAbelianBlochHamiltonian

Conversation

@marcelolooser

@marcelolooser marcelolooser commented May 2, 2025

Copy link
Copy Markdown
Member

The user input for the construction of non-reciprocal hyperbolic lattice models with multiple orbitals per site is not explained in detail. This PR clarifies the used conventions through a general two-orbital {p, q}-lattice model with two sites per unit cell, together with an explicit example with symbolic coupling constants.

@marcelolooser
marcelolooser force-pushed the chore/no-ref/NonReciprocalAbelianBlochHamiltonian branch from ae86dfb to 359922e Compare June 20, 2025 17:10
@marcelolooser
marcelolooser force-pushed the chore/no-ref/NonReciprocalAbelianBlochHamiltonian branch from e89fe4d to eecc377 Compare September 3, 2025 07:33
@marcelolooser
marcelolooser force-pushed the chore/no-ref/NonReciprocalAbelianBlochHamiltonian branch from eecc377 to 61321a3 Compare October 10, 2025 10:42

@patrick-lenggenhager patrick-lenggenhager left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please have a look at the comment, thanks!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description of options is doubled. Please check if they are identical and remove one (the old) copy of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants