Not signed in (Sign In)

Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

  • Sign in using OpenID

Site Tag Cloud

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry book bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics comma complex complex-geometry computable-mathematics computer-science constructive cosmology deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration finite foundation foundations functional-analysis functor gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory k-theory lie-theory limits linear linear-algebra locale localization logic mathematics measure-theory modal modal-logic model model-category-theory monad monads monoidal monoidal-category-theory morphism motives motivic-cohomology nlab noncommutative noncommutative-geometry number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf simplicial space spin-geometry stable-homotopy-theory stack string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory tqft type type-theory universal variational-calculus

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome to nForum
If you want to take part in these discussions either sign in now (if you have an account), apply for one now (if you don't).
    • CommentRowNumber1.
    • CommentAuthorSam Staton
    • CommentTimeAug 14th 2019

    Explain the connection with enriched monads

    diff, v15, current

    • CommentRowNumber2.
    • CommentAuthorSam Staton
    • CommentTimeAug 15th 2019

    “alternative definition” -> “concrete definition”, since it is not an alternative concept, it is the same

    diff, v16, current

    • CommentRowNumber3.
    • CommentAuthorSam Staton
    • CommentTimeAug 15th 2019

    parameterized formulation

    diff, v17, current

    • CommentRowNumber4.
    • CommentAuthorSam Staton
    • CommentTimeAug 15th 2019

    Added proposition about strength being unique when 1 is a generator.

    diff, v18, current

    • CommentRowNumber5.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 17th 2020

    Added prettier diagrams, and generalized to monoidal categories. More changes to come soon.

    diff, v19, current

    • CommentRowNumber6.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 23rd 2020

    In section 6 of the article, it says that since in some contexts a monad admits a unique strength, a strength can be thought of as a property rather than a structure. I feel this is misleading, since this does not automatically imply that morphisms of monads will preserve the strength. A better term would be property-like structure, rather.

    Any thoughts?

    • CommentRowNumber7.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 24th 2020

    Initiated makeover. (No content will be deleted.)

    diff, v21, current

    • CommentRowNumber8.
    • CommentAuthorMike Shulman
    • CommentTimeJan 24th 2020

    It’s true that the statement “a monad has at most one strength” doesn’t itself imply that every morphism of monads preserves the strength. But I wouldn’t be surprised if the same, or slightly stronger, hypotheses actually do imply this stronger result. Have you looked into it?

    In particular I would be shocked if a morphism of monads on SetSet could fail to preserve their strengths. (-:

    • CommentRowNumber9.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 27th 2020

    That’s a good point. No, I haven’t looked into that (yet).

    • CommentRowNumber10.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 27th 2020

    added costrength

    diff, v22, current

    • CommentRowNumber11.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 27th 2020

    Added examples

    diff, v23, current

    • CommentRowNumber12.
    • CommentAuthorPaoloPerrone
    • CommentTimeJan 28th 2020

    Started part on closed monoidal categories

    diff, v26, current

    • CommentRowNumber13.
    • CommentAuthorPaoloPerrone
    • CommentTimeFeb 2nd 2020

    Added equivalence of costrength and pointwise structure, with examples and references.

    diff, v34, current

    • CommentRowNumber14.
    • CommentAuthorMike Shulman
    • CommentTimeFeb 17th 2021

    Added definition of “bistrength”, made definition of commutative strength more explicit.

    diff, v38, current

    • CommentRowNumber15.
    • CommentAuthoranuyts
    • CommentTimeMar 5th 2021

    Add section on interaction with Kleisli category (in previous edit), try to get it to render properly.

    diff, v41, current

    • CommentRowNumber16.
    • CommentAuthoranuyts
    • CommentTimeMar 5th 2021

    Fixing lists. Correcting diagram.

    diff, v41, current

    • CommentRowNumber17.
    • CommentAuthoranuyts
    • CommentTimeMar 5th 2021
    So I added a section to make sense of what happens at https://ncatlab.org/nlab/show/call-by-push-value#as_an_adjoint_logic
    • CommentRowNumber18.
    • CommentAuthorTim_Porter
    • CommentTimeJun 1st 2021

    Fixed some awkward formatting

    diff, v42, current

    • CommentRowNumber19.
    • CommentAuthormattecapu
    • CommentTimeSep 22nd 2021
    • (edited Sep 22nd 2021)

    It has been pointed to me that the definition of costrength on this page doesn’t agree with most literature. It also doesn’t agree with the convention that if X goes ABA \to B, coX goes BAB \to A.

    To be clear, the current definition of costrength is TABT(AB)T A \otimes B \to T(A\otimes B) (so the difference with a strength is in which of the factors of the domain TT is applied to, whereas in the literature [1,2,3] I find T(AB)ATBT(A \otimes B) \to A \otimes TB

    Who’s right?

    [1] First hit for ’costrong comonad’ on Google: https://www.chrisstucchio.com/blog/2014/costrong_comonads_are_boring.html

    [2] Def 4.6 in https://arxiv.org/abs/1505.04330

    [3] https://library.oapen.org/bitstream/handle/20.500.12657/48221/9783030720193.pdf?sequence=1#page=248

    • CommentRowNumber20.
    • CommentAuthorvarkor
    • CommentTimeSep 22nd 2021
    • (edited Sep 22nd 2021)

    I think “strength” and “costrength” have been used entirely inconsistently in the literature. For example, Comonadic Notions of Computation uses the same terminology as the nLab. However, I agree this usage is very confusing, as it is not consistent with the usage of “co-” in the rest of category theory.

    (I’m not sure who introduced this terminology, as “costrength” and “costrong” were not used in the papers of Kock I looked in.)

    I think the most appropriate terminology would be “right-strength” for TABT(AB)TA \otimes B \to T(A \otimes B) and “left-strength” for ATBT(AB)A \otimes TB \to T(A \otimes B), and “right-costrength” for T(AB)TABT(A \otimes B) \to TA \otimes B and “left-costrength” for T(AB)ATBT(A \otimes B) \to A \otimes TB. I know various other people have the same complaint, so perhaps the nLab page would be an opportunity to provide clearer terminology (though giving a remark to say that the existing literature is inconsistent). This is also consistent with terminology like left closed and right closed for nonsymmetric monoidal categories.

    • CommentRowNumber21.
    • CommentAuthormattecapu
    • CommentTimeSep 23rd 2021
    • (edited Sep 23rd 2021)
    I like right/left strength, Nathanael. If we agree on this I can overhaul the page as soon as I'm on a train and clear up the confusion, with due warnings to the readers.
    • CommentRowNumber22.
    • CommentAuthorvarkor
    • CommentTimeMay 25th 2022

    Replace terminology “strength” and “costrength” with “left-strength” and “right-strength”, following the discussion on the nForum. This terminology is more in line with conventional categorical terminology and also widely used in the literature. It is unclear who introduced the terminology “strength” and “costrength”, as this terminology does not appear in Kock’s original papers.

    diff, v47, current

    • CommentRowNumber23.
    • CommentAuthorUrs
    • CommentTimeNov 11th 2022
    • (edited Nov 11th 2022)

    added pointer to:

    • Kruna Segrt Ratkovic, Def. 3.1.6 in: Morita theory in enriched context (2013) [arXiv:1302.2774]

    for the terminology “very strong monad” for the case that the strength is a natural iso.

    But I got this just by googling around. Please drop a note if there is other terminology for this.

    diff, v53, current

    • CommentRowNumber24.
    • CommentAuthorvarkor
    • CommentTimeNov 11th 2022

    Please drop a not if there is other terminology for this.

    In Gabriel-Morita theory for excisive model categories, a monad satisfying this condition is called “linear”. Since one of the coauthors of the paper is Ratkovic, I suppose they now prefer “linear” over “very strong”.

    • CommentRowNumber25.
    • CommentAuthorUrs
    • CommentTimeNov 11th 2022

    Thanks! That makes sense.

    I have added the pointer here.

    diff, v54, current

    • CommentRowNumber26.
    • CommentAuthorUrs
    • CommentTimeNov 11th 2022

    for what it’s worth, this thesis also uses the terminology “very strong” (Def. 8.10):

    • Daniel Schmitter, On Operations with Binders and Operations with Equations (2020) [web, pdf]

    Not that it matters very much, either way. But I have added that pointer to the entry now, too.

    diff, v55, current

    • CommentRowNumber27.
    • CommentAuthorUrs
    • CommentTimeNov 22nd 2022

    I have added the actual publication data for these items:

    diff, v56, current

    • CommentRowNumber28.
    • CommentAuthorvarkor
    • CommentTimeMay 3rd 2023
    • CommentRowNumber29.
    • CommentAuthorvarkor
    • CommentTimeMay 3rd 2023

    Move some discussion to tensorial costrength.

    diff, v60, current

  1. I’m not an expert on category theory or anything, but shouldn’t Mixed Associativity say “(XY)[Z]X(Y[Z])(X \otimes Y) \odot [Z] \cong X \odot (Y \odot [Z])” rather than “(XY)[Z]X(Y[Z])(X \otimes Y) \odot [Z] \cong X \otimes (Y \odot [Z])”?

    Plugging Y=IY=I into the latter gives “X \odot [Z] \cong X \otimes [Z]”!

    The old equation looks more balanced, i.e. one \otimes and one $\odot” on both sides, which caused the typo?

    Carlo

    diff, v65, current

    • CommentRowNumber31.
    • CommentAuthorUrs
    • CommentTimeNov 17th 2023

    I see that you fixed it, so I gather your question is rethorical.

    But yes, this is the “actor isomorphism” of an action of a monoidal category. (Or should be. I didn’t write this, but that’s what it seems to be getting at.)

    • CommentRowNumber32.
    • CommentAuthorUrs
    • CommentTimeNov 17th 2023

    (That section, “Interaction with the Kleisli category”, is due to revision 41 in March 2022.)

    • CommentRowNumber33.
    • CommentAuthorncfavier
    • CommentTimeFeb 24th 2024

    Addressed (and removed) anuyts’ question block in section 5 by fixing ε Y:X[X,Y]Y\epsilon_Y : X \otimes [X, Y] \to Y to ε Y:[X,Y]XY\epsilon_Y : [X, Y] \otimes X \to Y in the first paragraph, fixing the inconsistency.

    diff, v69, current