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
adding a small knot database #27535
Comments
Commit: |
Branch: u/chapoton/27535 |
comment:1
work in progress 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. This was a forced push. New commits:
|
comment:5
+1 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:9
Please have a look. |
Changed keywords from none to knot |
comment:12
This is a nice addition! How did you const6ruct the table of knots? Used some scripts to parse the data from the knot atlas? |
comment:13
Well, just taking the table and cleaning it by hand in emacs, using search-and-replace. |
comment:14
green bot |
Reviewer: Travis Scrimshaw |
comment:15
I think this is a little misleading about the
as it makes it seem like it should take a tuple. I think it would be better to have a more standard
A little formatting thing, I think the first entry of the knot table should be on its own line instead of part of the Other than these two things, LGTM, and this will be a very nice addition to have. |
comment:16
Doing this for links might also be a good follow-up too based on this: http://katlas.org/wiki/The_Thistlethwaite_Link_Table |
comment:18
done, thx |
comment:19
Thanks. LGTM. |
Changed branch from u/chapoton/27535 to |
CC: @tscrim @miguelmarco
Component: algebraic topology
Keywords: knot
Author: Frédéric Chapoton
Branch/Commit:
10aa203
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/27535
The text was updated successfully, but these errors were encountered: