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
Cup product for cochains #21081
Comments
comment:1
Using (The |
comment:2
What about splitting |
comment:3
That sounds like a good idea. |
Commit: |
New commits:
|
Author: Volker Braun |
comment:6
There is something wrong here (cochains should be chains in the OUTPUT):
and also here (two blank lines is too much):
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/vbraun/cup_product_for_cochains to u/jhpalmieri/cup_product_for_cochains |
comment:9
I made some trivial changes: fixed a few typos (like New commits:
|
Reviewer: Frédéric Chapoton, John Palmieri |
comment:10
Thanks! |
Changed branch from u/jhpalmieri/cup_product_for_cochains to |
It would be nice to have the cup product available for arbitrary cochains, without involving
homology_vector_space_with_basis
. Of course its not well-defined on the level of cochains, but at least one could check that products are non-zero if there is torsion over ZZ etc.There are potentially two places where to put it:
Method of
Chain.Element
, then chains would need to know about their cell (sub)complex. Right now they don't reference their cell complex as far as I can see.Method
GenericCellComplex.cup_product(self, left_cochain, right_cochain)
. Then chains need to know their degree (dimension of cells). Right now they don't store their degree, although the documentation says that they must be of homogeneous degree.Thoughts?
CC: @jhpalmieri @tscrim
Component: algebraic topology
Author: Volker Braun
Branch/Commit:
e2b36a3
Reviewer: Frédéric Chapoton, John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/21081
The text was updated successfully, but these errors were encountered: