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
free Pre-Lie algebras #15635
Comments
Attachment: prelie_algebra_with_several_gen_try1-fc.patch.gz |
Dependencies: #11529 |
comment:5
First step, a git branch that does not look too bad. New commits:
|
Branch: u/chapoton/15635 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed keywords from trees to trees, prelie algebra |
Author: Frédéric Chapoton |
comment:12
This should be ready, once rooted trees are ok. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:29
Thanks Travis for your comments. I have done something for the first three, but I do not I removed the shortcut I removed I used |
comment:30
Thanks! The last one was that line was commented out with a line above it saying about I plan to do a full review over this weekend. |
Reviewer: Travis Scrimshaw |
comment:31
I made some review changes:
If you're happy with my changes, then you can set a positive review. PS/EDIT - It would be nice to have the trees with specified labels, as this would allow the generic implementation of New commits:
|
Changed work issues from coercion to none |
Changed branch from u/chapoton/15635 to u/tscrim/free_pre_lie-15635 |
comment:32
Thanks a lot for your work on that ticket. I have not yet got time to look at your changes seriously.
I do not quite agree. Most people would not call them algebras, because they are NOT associative
No problem with removing s
Great !
The first point is problematic in my opinion.
yes, I agree ! |
comment:33
Doc does not build, because of the removal of s was forgotten in module_list |
comment:34
corrected the module-list there remains the problem about the entry in the catalog. New commits:
|
Changed branch from u/tscrim/free_pre_lie-15635 to public/ticket/15635 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:36
Thanks for fixing the module list (I didn't have time until this afternoon to come back to this). Replying to @fchapoton:
I understand your point, but what would people call them, non-associative algebras? The one of the current thoughts is to rename Irregardless of nomenclature, I would say that having this as a global entry point doesn't harm anyone as the name is clear (and there's no danger of confusion), it is documented that it not associative, it makes it discoverable, and Another option would be to create a (stub) category for pre-Lie algebras, werhich might be bett for the long term, and have a method
(and something similar should probably be done for associative unital algebras). |
comment:37
So I really think that the catalog 'algebras' should be kept for associative algebras. Maybe this should be discussed on sage-devel or sage-combinat-devel ? |
comment:38
Replying to @fchapoton:
I guess I forgot to add them...
Hmm...this would definitely create an mild inconsistency in the current state with
This is now https://groups.google.com/forum/#!topic/sage-devel/uXN5619Fg54. |
comment:39
Given the discussion on sage-devel, would you be okay with letting this stay in the algebras catalog? |
comment:40
Yes, ok to let it go in the algebra catalog. |
comment:41
Then positive review. |
Changed branch from public/ticket/15635 to |
one has shuffle algebras, one could have pre-Lie algebras, as soon as one has rooted trees (#11529)
Depends on #11529
CC: @sagetrac-sage-combinat @tscrim @darijgr
Component: combinatorics
Keywords: trees, prelie algebra
Author: Frédéric Chapoton
Branch/Commit:
6fa6d78
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/15635
The text was updated successfully, but these errors were encountered: