Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version: QuantumLattices v0.10.0 #117641

Merged

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Oct 19, 2024

## Breaking changes

Such changes do affect the public interfaces that users interact with.

### Fermion/boson/spin/phonon indexes and operators

- Construction of fermion/boson/spin/phonon indexes and operators are changed. `𝕗` (`\bbf<tab>` ferimion), `𝕓` (`\bbb<tab>`, boson), `𝕊` (`\bbS<tab>`, spin), `𝕦` (`\bbu<tab>`, displacement of lattice vibration) and `𝕡` (`\bbp<tab>`, momentum of lattice vibration) are the new interfaces to construct and display such indexes and operators.

- Underlying types to implement fermion/boson/spin/phonon indexes and operators are renamed: 1) the abstract type `IID` => `InternalIndex`, and the concrete types `FID` => `FockIndex`, `SID` => `SpinIndex`, `PID` => `PhononIndex`; 2) `CompositeIndex` => `CoordinatedIndex`.

- The `:iid` attribute of `Index` now is renamed to `:internal`.

### Coupling

- A new type, `Pattern`, is introduced to represent the coupling pattern in a `Coupling`.
- Construction of `Coupling` with constraints now uses a new macro, `@pattern`. The old `@indexes` macro is removed.
- `Coupling` with different types of `Index`es now must be initialized with the `@pattern` macro.
- The `:site` attribute of an `Index` used to construct a `Coupling` can no longer be an integer; it must now be either a `:` or an `Ordinal` to clearly indicate that it represents the ordinal in a bond.

### Quantum numbers

Quantum numbers are completely redesigned.

## Mechanism changes

Such changes typically do not affect the public interfaces that users interact with, but they are significant for developers looking to extend this package.

- New function `Patternrule` is introduced to implement default rules for coupling patterns.
- Interface of `script`, which is used to support latex-formatted output of operators, is changed.
- Interface of `expand` for a `Coupling` is changed.
- Interfaces of `Toolkit.VectorSpace` are changed.

Copy link
Contributor

github-actions bot commented Oct 19, 2024

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round.

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

UUID: 78ae1a1f-1d5d-5174-b61c-66e31b2346dc
Repo: https://github.com/Quantum-Many-Body/QuantumLattices.jl.git
Tree: 58408450ab3ea536d7a46888936293806d2398e9

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-quantumlattices-78ae1a1f-v0.10.0-dfcdd7087b branch from 32c9a19 to c82446c Compare October 20, 2024 02:44
@JuliaTagBot JuliaTagBot merged commit e54d710 into master Oct 20, 2024
9 checks passed
@JuliaTagBot JuliaTagBot deleted the registrator-quantumlattices-78ae1a1f-v0.10.0-dfcdd7087b branch October 20, 2024 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants