#17030: Knot Theory as a part of GSoC 2014.
-------------------------------------+-------------------------------------
Reporter: amitjamadagni | Owner: amitjamadagni
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: algebraic | Resolution:
topology | Merged in:
Keywords: | Reviewers:
Authors: Amit Jamadagni, | Work issues:
Miguel Marco | Commit:
Report Upstream: N/A | 37bd26ba2e6ccd45e886fd7fdcbcdfa4d0ba0d03
Branch: | Stopgaps:
u/mmarco/ticket/17030 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by mmarco):
Inthe case of git history, i like it to reflect the process that actually
took place, in case that someone in the future wants to do some
archeology.
But it is just a matter of personal taste. I understand why other people
prefear to avoid haveing too many commits in the history.
My last changes touch most of the relevant methods, so it would be
difficult to stablish a clear separation from my work and Amit's.
Here some ideas of things that non specialists in knot theory can do
towards reviewing:
- Check the documentation. In fact, it is better if they are not
specialist: the documentation should be clear for everybody. So if there
is something that someone does not understand, please point it out.
- Test some results that are known in other sources. For instance go to
the knot atlas, pick any knot or link there, create it in Sage, compute
the different invariants and compare. (Note, here we follow a different
convention than in the knot atlas for the PD code, Xa,b,c,d in the knot
atlas corresponds here to [a,d,b,c]).
- Check out also the plotting of knots (no deep knowledge of knot theory
is needed, although it is a complicated method, so it is hard to review...
but it is really cool ;) ).
Regarding the idea of separting it into smaller tickets, we could do that,
but besides the plotting, all the methods that can be separated into other
tickets (i.e. the computation of the different invariants), are pretty
trivial, since they are almost direct aplications of the conversion to
braid).
--
Ticket URL: <http://trac.sagemath.org/ticket/17030#comment:67>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
