75
Introduction Arcs and Arclists Tightness Checking Bypasses Final Results and Thoughts Improving on an Existing Program That Checks for Tight Contact Structures on the Solid Torus Northeastern Illinois University SCSE Research Symposium Christopher L. Toni Kelly Hirschbeck Nathan Walter William Krepelin Donald Barkley William Byrd John Wallin Mayra Bravo-Gonzalez Banlieman Kolani Dr. Tanya Cofer October 2, 2009 Christopher L. Toni, Donald Barkley Computational Contact Topology 1 / 20

SCSE Symposium Presentation

Embed Size (px)

Citation preview

Page 1: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Improving on an Existing Program That Checksfor Tight Contact Structures on the Solid TorusNortheastern Illinois University SCSE Research Symposium

Christopher L. Toni Kelly Hirschbeck Nathan WalterWilliam Krepelin Donald Barkley William Byrd

John Wallin Mayra Bravo-Gonzalez Banlieman KolaniDr. Tanya Cofer∗

October 2, 2009

Christopher L. Toni, Donald Barkley Computational Contact Topology 1 / 20

Page 2: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Outline

1 Introduction

2 Arcs and Arclists

3 Tightness Checking

4 Bypasses

5 Final Results and Thoughts

Christopher L. Toni, Donald Barkley Computational Contact Topology 2 / 20

Page 3: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology?

Topology is a field of mathematics that does not focus on anobject’s shape, but the properties that remain consistentthrough deformations like:

1 twisting2 bending3 stretching

To illustrate this, visualize a coffee cup and a doughnut (torus).

Christopher L. Toni, Donald Barkley Computational Contact Topology 3 / 20

Page 4: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology?

Topology is a field of mathematics that does not focus on anobject’s shape, but the properties that remain consistentthrough deformations like:

1 twisting

2 bending3 stretching

To illustrate this, visualize a coffee cup and a doughnut (torus).

Christopher L. Toni, Donald Barkley Computational Contact Topology 3 / 20

Page 5: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology?

Topology is a field of mathematics that does not focus on anobject’s shape, but the properties that remain consistentthrough deformations like:

1 twisting2 bending

3 stretching

To illustrate this, visualize a coffee cup and a doughnut (torus).

Christopher L. Toni, Donald Barkley Computational Contact Topology 3 / 20

Page 6: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology?

Topology is a field of mathematics that does not focus on anobject’s shape, but the properties that remain consistentthrough deformations like:

1 twisting2 bending3 stretching

To illustrate this, visualize a coffee cup and a doughnut (torus).

Christopher L. Toni, Donald Barkley Computational Contact Topology 3 / 20

Page 7: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology?

Topology is a field of mathematics that does not focus on anobject’s shape, but the properties that remain consistentthrough deformations like:

1 twisting2 bending3 stretching

To illustrate this, visualize a coffee cup and a doughnut (torus).

Christopher L. Toni, Donald Barkley Computational Contact Topology 3 / 20

Page 8: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

What is Topology? (cont.)

The torus and the coffee cup are topologically equivalentobjects. We see above that through bending and stretching, thetorus can be morphed into a coffee cup and vice versa.

Christopher L. Toni, Donald Barkley Computational Contact Topology 4 / 20

Page 9: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Formulating the Problem

On the solid torus (defined by S1×D2), dividing curves arelocated where twisting planes switch from positive to negative.

These dividing curves keep track of and allow for investigationof certain topological properties in the neighborhood of asurface.

Christopher L. Toni, Donald Barkley Computational Contact Topology 5 / 20

Page 10: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Formulating the Problem

On the solid torus (defined by S1×D2), dividing curves arelocated where twisting planes switch from positive to negative.

These dividing curves keep track of and allow for investigationof certain topological properties in the neighborhood of asurface.

Christopher L. Toni, Donald Barkley Computational Contact Topology 5 / 20

Page 11: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Formulating the Problem

On the solid torus (defined by S1×D2), dividing curves arelocated where twisting planes switch from positive to negative.

These dividing curves keep track of and allow for investigationof certain topological properties in the neighborhood of asurface.

Christopher L. Toni, Donald Barkley Computational Contact Topology 5 / 20

Page 12: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Formulating the Problem (cont.)

We define n to be the number of dividing curves, p to be thenumber of times the dividing curves are wrapped about thelongitudinal section of the torus, and q to be the number oftimes the dividing curves are wrapped about the meridinalsection of the torus.

Christopher L. Toni, Donald Barkley Computational Contact Topology 6 / 20

Page 13: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Formulating the Problem (cont.)

We define n to be the number of dividing curves, p to be thenumber of times the dividing curves are wrapped about thelongitudinal section of the torus, and q to be the number oftimes the dividing curves are wrapped about the meridinalsection of the torus.

Christopher L. Toni, Donald Barkley Computational Contact Topology 6 / 20

Page 14: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 15: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 16: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired

2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 17: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 18: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 19: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.

The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 20: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem.

There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 21: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview

The first computational task is to generate arclists for a givennumber of vertices M, where M = np.

DefinitionAn arc is a path between vertices subject to:

1 All M vertices in a configuration must be paired2 Paths cannot cross

An arclist is a set (list) of legal pairs of arcs.

We can think of arclists for M vertices as certain permutationsof M objects.The solution is to “walk” a new element throughthe solution set for a smaller problem. There is one challenge:the algorithm is space and time intensive!

Christopher L. Toni, Donald Barkley Computational Contact Topology 7 / 20

Page 22: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm - Arcs and Arclist

Christopher L. Toni, Donald Barkley Computational Contact Topology 8 / 20

Page 23: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm - Arcs and Arclist

Christopher L. Toni, Donald Barkley Computational Contact Topology 8 / 20

Page 24: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Arcs and Arclists

For the case of n = 2, p = 4, q = 3, we haveM = np = (2)(4) = 8.

The arclists for M = 8 vertices are:

(0 1)(2 5)(3 4)(6 7)(0 1)(2 7)(3 4)(5 6)(0 3)(1 2)(4 5)(6 7)(0 1)(2 3)(4 5)(6 7)(0 1)(2 7)(3 6)(4 5)(0 3)(1 2)(4 7)(5 6)(0 7)(1 2)(3 4)(5 6)

(0 5)(1 2)(3 4)(6 7)(0 7)(1 4)(2 3)(5 6)(0 1)(2 3)(4 7)(5 6)(0 5)(1 4)(2 3)(6 7)(0 7)(1 2)(3 6)(4 5)(0 7)(1 6)(2 5)(3 4)(0 7)(1 6)(2 3)(4 5)

Data files for required values of M were produced and saved.These files were then used as input to the Tightness Checkingmodule.

Christopher L. Toni, Donald Barkley Computational Contact Topology 9 / 20

Page 25: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Arcs and Arclists

For the case of n = 2, p = 4, q = 3, we haveM = np = (2)(4) = 8.The arclists for M = 8 vertices are:

(0 1)(2 5)(3 4)(6 7)(0 1)(2 7)(3 4)(5 6)(0 3)(1 2)(4 5)(6 7)(0 1)(2 3)(4 5)(6 7)(0 1)(2 7)(3 6)(4 5)(0 3)(1 2)(4 7)(5 6)(0 7)(1 2)(3 4)(5 6)

(0 5)(1 2)(3 4)(6 7)(0 7)(1 4)(2 3)(5 6)(0 1)(2 3)(4 7)(5 6)(0 5)(1 4)(2 3)(6 7)(0 7)(1 2)(3 6)(4 5)(0 7)(1 6)(2 5)(3 4)(0 7)(1 6)(2 3)(4 5)

Data files for required values of M were produced and saved.These files were then used as input to the Tightness Checkingmodule.

Christopher L. Toni, Donald Barkley Computational Contact Topology 9 / 20

Page 26: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Arcs and Arclists

For the case of n = 2, p = 4, q = 3, we haveM = np = (2)(4) = 8.The arclists for M = 8 vertices are:

(0 1)(2 5)(3 4)(6 7)(0 1)(2 7)(3 4)(5 6)(0 3)(1 2)(4 5)(6 7)(0 1)(2 3)(4 5)(6 7)(0 1)(2 7)(3 6)(4 5)(0 3)(1 2)(4 7)(5 6)(0 7)(1 2)(3 4)(5 6)

(0 5)(1 2)(3 4)(6 7)(0 7)(1 4)(2 3)(5 6)(0 1)(2 3)(4 7)(5 6)(0 5)(1 4)(2 3)(6 7)(0 7)(1 2)(3 6)(4 5)(0 7)(1 6)(2 5)(3 4)(0 7)(1 6)(2 3)(4 5)

Data files for required values of M were produced and saved.These files were then used as input to the Tightness Checkingmodule.

Christopher L. Toni, Donald Barkley Computational Contact Topology 9 / 20

Page 27: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Arcs and Arclists

For the case of n = 2, p = 4, q = 3, we haveM = np = (2)(4) = 8.The arclists for M = 8 vertices are:

(0 1)(2 5)(3 4)(6 7)(0 1)(2 7)(3 4)(5 6)(0 3)(1 2)(4 5)(6 7)(0 1)(2 3)(4 5)(6 7)(0 1)(2 7)(3 6)(4 5)(0 3)(1 2)(4 7)(5 6)(0 7)(1 2)(3 4)(5 6)

(0 5)(1 2)(3 4)(6 7)(0 7)(1 4)(2 3)(5 6)(0 1)(2 3)(4 7)(5 6)(0 5)(1 4)(2 3)(6 7)(0 7)(1 2)(3 6)(4 5)(0 7)(1 6)(2 5)(3 4)(0 7)(1 6)(2 3)(4 5)

Data files for required values of M were produced and saved.These files were then used as input to the Tightness Checkingmodule.

Christopher L. Toni, Donald Barkley Computational Contact Topology 9 / 20

Page 28: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Arcs and Arclists

For the case of n = 2, p = 4, q = 3, we haveM = np = (2)(4) = 8.The arclists for M = 8 vertices are:

(0 1)(2 5)(3 4)(6 7)(0 1)(2 7)(3 4)(5 6)(0 3)(1 2)(4 5)(6 7)(0 1)(2 3)(4 5)(6 7)(0 1)(2 7)(3 6)(4 5)(0 3)(1 2)(4 7)(5 6)(0 7)(1 2)(3 4)(5 6)

(0 5)(1 2)(3 4)(6 7)(0 7)(1 4)(2 3)(5 6)(0 1)(2 3)(4 7)(5 6)(0 5)(1 4)(2 3)(6 7)(0 7)(1 2)(3 6)(4 5)(0 7)(1 6)(2 5)(3 4)(0 7)(1 6)(2 3)(4 5)

Data files for required values of M were produced and saved.These files were then used as input to the Tightness Checkingmodule. Christopher L. Toni, Donald Barkley Computational Contact Topology 9 / 20

Page 29: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker

Once the arclists are found, it is possible to determine how thevertices on the left and right cutting disks match up.

The formula x → x−nq+1 mod np maps the vertices on theleft cutting disk to the right cutting disk.

The formula x → x +nq−1 mod np maps the vertices on theright cutting disk to the left cutting disk.

To determine if the torus admits a tight or overtwisted contactstructure, the dividing curves and arcs need to be analyzed.

Christopher L. Toni, Donald Barkley Computational Contact Topology 10 / 20

Page 30: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker

Once the arclists are found, it is possible to determine how thevertices on the left and right cutting disks match up.

The formula x → x−nq+1 mod np maps the vertices on theleft cutting disk to the right cutting disk.

The formula x → x +nq−1 mod np maps the vertices on theright cutting disk to the left cutting disk.

To determine if the torus admits a tight or overtwisted contactstructure, the dividing curves and arcs need to be analyzed.

Christopher L. Toni, Donald Barkley Computational Contact Topology 10 / 20

Page 31: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker

Once the arclists are found, it is possible to determine how thevertices on the left and right cutting disks match up.

The formula x → x−nq+1 mod np maps the vertices on theleft cutting disk to the right cutting disk.

The formula x → x +nq−1 mod np maps the vertices on theright cutting disk to the left cutting disk.

To determine if the torus admits a tight or overtwisted contactstructure, the dividing curves and arcs need to be analyzed.

Christopher L. Toni, Donald Barkley Computational Contact Topology 10 / 20

Page 32: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker

Once the arclists are found, it is possible to determine how thevertices on the left and right cutting disks match up.

The formula x → x−nq+1 mod np maps the vertices on theleft cutting disk to the right cutting disk.

The formula x → x +nq−1 mod np maps the vertices on theright cutting disk to the left cutting disk.

To determine if the torus admits a tight or overtwisted contactstructure, the dividing curves and arcs need to be analyzed.

Christopher L. Toni, Donald Barkley Computational Contact Topology 10 / 20

Page 33: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker (cont.)

If a single closed curve can betraced on the torus, it isconsidered to be a potentiallytight contact structure.

If more than one closed curvecan be traced on the torus, itis considered to be anovertwisted structure.

Christopher L. Toni, Donald Barkley Computational Contact Topology 11 / 20

Page 34: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker (cont.)

If a single closed curve can betraced on the torus, it isconsidered to be a potentiallytight contact structure.

If more than one closed curvecan be traced on the torus, itis considered to be anovertwisted structure.

Christopher L. Toni, Donald Barkley Computational Contact Topology 11 / 20

Page 35: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Overview - Tightness Checker (cont.)

If a single closed curve can betraced on the torus, it isconsidered to be a potentiallytight contact structure.

If more than one closed curvecan be traced on the torus, itis considered to be anovertwisted structure.

Christopher L. Toni, Donald Barkley Computational Contact Topology 11 / 20

Page 36: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm - Tightness Checker

All vertices hook up to a singlecurve. Thus, the structure is

potentially tight.

Only a few vertices hook up toa curve. Thus, the structure is

overtwisted.

Christopher L. Toni, Donald Barkley Computational Contact Topology 12 / 20

Page 37: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm - Tightness Checker

All vertices hook up to a singlecurve. Thus, the structure is

potentially tight.

Only a few vertices hook up toa curve. Thus, the structure is

overtwisted.

Christopher L. Toni, Donald Barkley Computational Contact Topology 12 / 20

Page 38: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm - Tightness Checker

All vertices hook up to a singlecurve. Thus, the structure is

potentially tight.

Only a few vertices hook up toa curve. Thus, the structure is

overtwisted.

Christopher L. Toni, Donald Barkley Computational Contact Topology 12 / 20

Page 39: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8.

Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 40: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8. Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 41: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8. Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 42: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8. Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 43: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8. Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 44: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker

Consider M = np = 8. Given the arclist {(0 1)(2 7)(3 6)(4 5)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,6,3,6,1,0,5,4,7,2,7,2,5,4,1,0, . . .

0, 3,6 , 3,6 , 1,0 , 5,4 , 7,2 , 7,2 , 5,4 , 1,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 13 / 20

Page 45: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8.

Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 46: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8. Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 47: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8. Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 48: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8. Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 49: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8. Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 50: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Algorithm Output - Tightness Checker (cont.)

Consider M = np = 8. Given the arclist {(0 7)(1 4)(2 3)(5 6)},the left cutting disk hooks up with the right cutting disk asfollows:

0→ 0−5 mod 8 = 31→ 1−5 mod 8 = 42→ 2−5 mod 8 = 53→ 3−5 mod 8 = 6

4→ 4−5 mod 8 = 75→ 5−5 mod 8 = 06→ 6−5 mod 8 = 17→ 7−5 mod 8 = 2

Using the arclist as a guide, the output be a list of numbers

0,3,2,7,0,3,2,7,0,3,2,7,0 . . .

0, 3,2 , 7,0 , 3,2 , 7,0 , 3,2 , 7,0 , . . .

Christopher L. Toni, Donald Barkley Computational Contact Topology 14 / 20

Page 51: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses

A bypass exists when a line can be drawn through three arcson a cutting disk.

There are two possiblebypasses on this cutting disk.

There are no possiblebypasses on this cutting disk.

Christopher L. Toni, Donald Barkley Computational Contact Topology 15 / 20

Page 52: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses

A bypass exists when a line can be drawn through three arcson a cutting disk.

There are two possiblebypasses on this cutting disk.

There are no possiblebypasses on this cutting disk.

Christopher L. Toni, Donald Barkley Computational Contact Topology 15 / 20

Page 53: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses

A bypass exists when a line can be drawn through three arcson a cutting disk.

There are two possiblebypasses on this cutting disk.

There are no possiblebypasses on this cutting disk.

Christopher L. Toni, Donald Barkley Computational Contact Topology 15 / 20

Page 54: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses

A bypass exists when a line can be drawn through three arcson a cutting disk.

There are two possiblebypasses on this cutting disk.

There are no possiblebypasses on this cutting disk.

Christopher L. Toni, Donald Barkley Computational Contact Topology 15 / 20

Page 55: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses (cont.)

When a bypass is performed, it produces an already existingarclist!

This is crucial in determining if these arclists form a tightcontact structure on the torus.

The bypass can be viewed as an equivalence relationbetween arclists.

If one arclist is overtwisted in an equivalence class, the entireequivalence class is associated to an overtwisted structure.Thissaves time in the calculation process.

Christopher L. Toni, Donald Barkley Computational Contact Topology 16 / 20

Page 56: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses (cont.)

When a bypass is performed, it produces an already existingarclist!

This is crucial in determining if these arclists form a tightcontact structure on the torus.

The bypass can be viewed as an equivalence relationbetween arclists.

If one arclist is overtwisted in an equivalence class, the entireequivalence class is associated to an overtwisted structure.Thissaves time in the calculation process.

Christopher L. Toni, Donald Barkley Computational Contact Topology 16 / 20

Page 57: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses (cont.)

When a bypass is performed, it produces an already existingarclist!

This is crucial in determining if these arclists form a tightcontact structure on the torus.

The bypass can be viewed as an equivalence relationbetween arclists.

If one arclist is overtwisted in an equivalence class, the entireequivalence class is associated to an overtwisted structure.Thissaves time in the calculation process.

Christopher L. Toni, Donald Barkley Computational Contact Topology 16 / 20

Page 58: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses (cont.)

When a bypass is performed, it produces an already existingarclist!

This is crucial in determining if these arclists form a tightcontact structure on the torus.

The bypass can be viewed as an equivalence relationbetween arclists.

If one arclist is overtwisted in an equivalence class, the entireequivalence class is associated to an overtwisted structure.

Thissaves time in the calculation process.

Christopher L. Toni, Donald Barkley Computational Contact Topology 16 / 20

Page 59: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Brief Overview - Bypasses (cont.)

When a bypass is performed, it produces an already existingarclist!

This is crucial in determining if these arclists form a tightcontact structure on the torus.

The bypass can be viewed as an equivalence relationbetween arclists.

If one arclist is overtwisted in an equivalence class, the entireequivalence class is associated to an overtwisted structure.Thissaves time in the calculation process.

Christopher L. Toni, Donald Barkley Computational Contact Topology 16 / 20

Page 60: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions

1 Formula for computing the number of arclists for a givennumber of vertices and web implementation of this formula.

2 Software module to produce arclists For various number ofvertices.

3 Modification of succeeding software modules (bypass andtightness checking) to read these arclists as input.

4 Manually produced algorithms and results sets for variousvalues of n, p, q to be used for software testing.

Christopher L. Toni, Donald Barkley Computational Contact Topology 17 / 20

Page 61: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions

1 Formula for computing the number of arclists for a givennumber of vertices and web implementation of this formula.

2 Software module to produce arclists For various number ofvertices.

3 Modification of succeeding software modules (bypass andtightness checking) to read these arclists as input.

4 Manually produced algorithms and results sets for variousvalues of n, p, q to be used for software testing.

Christopher L. Toni, Donald Barkley Computational Contact Topology 17 / 20

Page 62: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions

1 Formula for computing the number of arclists for a givennumber of vertices and web implementation of this formula.

2 Software module to produce arclists For various number ofvertices.

3 Modification of succeeding software modules (bypass andtightness checking) to read these arclists as input.

4 Manually produced algorithms and results sets for variousvalues of n, p, q to be used for software testing.

Christopher L. Toni, Donald Barkley Computational Contact Topology 17 / 20

Page 63: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions

1 Formula for computing the number of arclists for a givennumber of vertices and web implementation of this formula.

2 Software module to produce arclists For various number ofvertices.

3 Modification of succeeding software modules (bypass andtightness checking) to read these arclists as input.

4 Manually produced algorithms and results sets for variousvalues of n, p, q to be used for software testing.

Christopher L. Toni, Donald Barkley Computational Contact Topology 17 / 20

Page 64: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions (cont.)

N[2] = 1N[4] = 2N[6] = 5N[8] = 14

N[10] = 42N[12] = 132N[14] = 429N[16] = 1430N[18] = 4862N[20] = 16796

N[22] = 58786N[24] = 208012N[26] = 742900N[28] = 2674440N[30] = 9694845N[32] = 35357670N[34] = 129644790N[36] = 477638700N[38] = 1767263190N[40] = 6564120420

Note that the number of arclists increase rapidly as the numberof vertices get larger. At M = 28, its well over a million!

Christopher L. Toni, Donald Barkley Computational Contact Topology 18 / 20

Page 65: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Results and Conclusions (cont.)

N[2] = 1N[4] = 2N[6] = 5N[8] = 14

N[10] = 42N[12] = 132N[14] = 429N[16] = 1430N[18] = 4862N[20] = 16796

N[22] = 58786N[24] = 208012N[26] = 742900N[28] = 2674440N[30] = 9694845N[32] = 35357670N[34] = 129644790N[36] = 477638700N[38] = 1767263190N[40] = 6564120420

Note that the number of arclists increase rapidly as the numberof vertices get larger. At M = 28, its well over a million!

Christopher L. Toni, Donald Barkley Computational Contact Topology 18 / 20

Page 66: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Future Research

Future goals include, but not limited to:

1 Publication of Findings in Undergraduate Journal

2 Extension of Algorithm to the two-holed torus

3 Enhance software (requiring a reduced memory footprint)to produce results for larger number of vertices.

Christopher L. Toni, Donald Barkley Computational Contact Topology 19 / 20

Page 67: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Future Research

Future goals include, but not limited to:

1 Publication of Findings in Undergraduate Journal

2 Extension of Algorithm to the two-holed torus

3 Enhance software (requiring a reduced memory footprint)to produce results for larger number of vertices.

Christopher L. Toni, Donald Barkley Computational Contact Topology 19 / 20

Page 68: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Future Research

Future goals include, but not limited to:

1 Publication of Findings in Undergraduate Journal

2 Extension of Algorithm to the two-holed torus

3 Enhance software (requiring a reduced memory footprint)to produce results for larger number of vertices.

Christopher L. Toni, Donald Barkley Computational Contact Topology 19 / 20

Page 69: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Future Research

Future goals include, but not limited to:

1 Publication of Findings in Undergraduate Journal

2 Extension of Algorithm to the two-holed torus

3 Enhance software (requiring a reduced memory footprint)to produce results for larger number of vertices.

Christopher L. Toni, Donald Barkley Computational Contact Topology 19 / 20

Page 70: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20

Page 71: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20

Page 72: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20

Page 73: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20

Page 74: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20

Page 75: SCSE Symposium Presentation

IntroductionArcs and Arclists

Tightness CheckingBypasses

Final Results and Thoughts

Acknowledgements

We would like to thank:

∙ The SCSE (Dept. of Education) for funding the researchover summer.

∙ Dr. Tanya Cofer for leading us through tough concepts andtedious calculations.

∙ Donald Barkley for helping us program the algorithms inJava.

Donald Barkley will now talk about the programming part of theproject.

Christopher L. Toni, Donald Barkley Computational Contact Topology 20 / 20