Support for parsing d-diagrams to correspond to Manifold object.

[zitterbewegung]

Would it be useful / desirable for snappy to allow for an input of a d-diagram as a text input and then constructing the knot that would represent it? For example

(([[))]] -> Would correspond to a Manifold object of the Trefoil.

More details below.

Manturov, V.O.(2002), Knots and the Bracket Calculus, Acta Applicandae
Mathematicae, 74, (3), pp. 293–336.

https://www.researchgate.net/profile/Vassily_Manturov/publication/227058309_Knots_and_the_Bracket_Calculus/links/540d56510cf2f2b29a3839bf/Knots-and-the-Bracket-Calculus.pdf

[NathanDunfield]

What are advantages of this scheme? I am not familiar with it and it's not exactly human readable.

[zitterbewegung]

I agree with you that the notation is unreadable.I was writing a parser for the d-diagram already and I was wondering if it would be useful to contribute back to the Spherogram project. If it is undesirable I will just create my own project for it instead.

From what is in the paper you could

• construct a knot based on a finite alphabet.
• also the link recognition problem is reduced to a recognition problem in this semigroup.

[NathanDunfield]

Very sorry for the slow response, initially I suggest you do this as a separate project.

[zitterbewegung]

Yea I understood that thanks Z

…

Sent from my iPhone

On Aug 21, 2020, at 5:35 PM, Nathan Dunfield ***@***.***> wrote:  Very sorry for the slow response, initially I suggest you do this as a separate project. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[culler]

A suggestion: a function which accepts a d-diagram as input and outputs a PD code for a link projection would be something that anyone who wants to work with d-diagrams could use, in many contexts. - Marc

…

On Fri, Aug 21, 2020 at 5:35 PM Nathan Dunfield ***@***.***> wrote: Very sorry for the slow response, initially I suggest you do this as a separate project. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ6CP6JQLJDYBLBP4T3AZLSB3ZCHANCNFSM4PS4JDPA> .