-
Notifications
You must be signed in to change notification settings - Fork 41
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
permuteind! for AdjointTensorMap #2
Comments
lkdvos
added a commit
that referenced
this issue
Jun 8, 2024
This changes the behaviour of copy as an instantiator for creating a TensorMap from a BraidingTensor. The rationale is that while this does sometimes happen in Julia Base, this is always in the context of lazy wrapper types, for which it makes sense to not copy the parent and then create a new wrapper. BraidingTensor does not wrap anything, so this definition makes less sense.
Jutho
added a commit
that referenced
this issue
Jul 18, 2024
* Add .vscode to gitignore * Add changelog.md * Change type signature: `AbstractTensorMap{<:Number,<:IndexSpace,N1,N2}` (#1) * Add scalartype parameter to `AbstractTensorMap` * Add scalartype in definition of TensorMap * Add scalartype to AdjointTensorMap * Add scalartype to BraidingTensor * Implement changes for indexmanipulations * Implement scalartype for linalg * implement changes for tensoroperations * implement changes for planaroperations * implement changes for ChainRules * small fixes * Fix typo * Fix missing change * Formatter * Apply scalartype changes to tests * Fix some ambiguities * De-specialize `trace_permute` * Despecialize `_contract!` * Remove unused type-parameter * Despecialize `planaradd!` and `planartrace!` * Small fixes * Change braidingtensor syntax to resolve ambiguities * despecialize some linalg methods * formatter * Add changelog entry * Fix ambiguity on Julia1.6 * Update Changelog.md * Change `copy(BraidingTensor)` to return a `BraidingTensor` (#2) This changes the behaviour of copy as an instantiator for creating a TensorMap from a BraidingTensor. The rationale is that while this does sometimes happen in Julia Base, this is always in the context of lazy wrapper types, for which it makes sense to not copy the parent and then create a new wrapper. BraidingTensor does not wrap anything, so this definition makes less sense. * Move sectors to separate module (#3) * Split Sectors module * convert submodule into its own module * Organize tests * Add precompile statements * Add non-unicode alternative `fusionproduct` for `⊗` * Add `directproduct` for `×` * split "trivial.jl" * Formatter * Change unicode alternatives to `otimes` and `times` Incorporate changes from #aada0b2 * Update some testset descriptions * Resolve method ambiguities * Change some formatting * Import local version of `TensorKitSectors` * Enable TensorKitSectors github action * Switch to local include for CI * Remove `NewSU2Sector` tests from main package * Refactor sectors to group Fsymbol and Rsymbol operations * Update CI Sectors to only trigger when files are changed in that path * fix and improve copy(::BraidingTensor) (#5) * copy entire template and stop using copy(b.V1), copy(b.V2) as they do not work * formatting * Refactor TensorMap constructors (#6) - Refactored `TensorMap` constructors to be in line with `Array` counterparts: ```julia TensorMap{E}(undef, codomain, domain) # + some variants ``` - Added support for `zeros`, `ones`, `rand`, and `randn`. - Streamlined the interface for these functions, along with `isomorphism`, `unitary` and `isometry` into the form: ```julia function([T], codomain, domain) # + some variants ``` * Update TensorOperations v5 compatibility (#7) * Update TensorOperations v5 compatibility * Manually add unreleased TensorOperations version * Update CI.yml * Revert tensoroperations v5 attempts * Changes to incorporate v5 * Remove manual installation of TensorOperations in docs CI [no ci] * Update changelog [no ci] * Address review comments * Rename `isqrtdim` -> `invsqrtdim` * `T` is scalartype, `TT` is tensortype --------- Co-authored-by: Jutho <[email protected]> Co-authored-by: Victor Vanthilt <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: