Choose hom(B,C) = C ⊗ B^v instead of B^v ⊗ C#1501
Draft
zickgraf wants to merge 1 commit intohomalg-project:masterfrom
Draft
Choose hom(B,C) = C ⊗ B^v instead of B^v ⊗ C#1501zickgraf wants to merge 1 commit intohomalg-project:masterfrom
zickgraf wants to merge 1 commit intohomalg-project:masterfrom
Conversation
7d38af5 to
b7c7d4e
Compare
b7c7d4e to
6632eef
Compare
Member
|
Good point. If we assume that we have no braiding in a monoidal category, then we have to be careful with directions. Here are the details:
By left duals, I mean the following convention:
but you cannot build the other 2 missing combinations. In particular, setting the right internal hom as you suggest is the natural choice. |
Member
Author
|
Thanks for the analysis and confirmation @sebastianpos! I will talk to @mohamed-barakat about how we shall proceed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, CAP derives the closed structure from the rigid structure by setting hom(B,C) = B^v ⊗ C. nLab chooses hom(B,C) = C ⊗ B^v instead: https://ncatlab.org/nlab/show/compact+closed+category. This PR implement the nLab convention. This greatly simplifies the definition of the evaluation and coevaluation morphisms, which can now be defined without braidings. This in turn simplifies string diagrams and the proof that we indeed get a closed structure. On the other hand, some braidings have to be added at other places. However, those are maybe expected or could be avoided. For example, a derivation of the trace map now needs a braiding, but that already seems to be part of the definition: https://ncatlab.org/nlab/show/trace. Moreover, some derivations using TensorProductInternalHomCompatibilityMorphism now need a braiding, but maybe TensorProductInternalHomCompatibilityMorphism could be adjusted, too to avoid this.
For my applications, choosing hom(B,C) = C ⊗ B^v is much simpler, so I will use this in my thesis. Maybe that would also make sense for CAP in general?
ping @mohamed-barakat @sebastianpos @TKuh