summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEugeniy Mikhailov <evgmik@gmail.com>2013-09-18 08:24:57 -0400
committerEugeniy Mikhailov <evgmik@gmail.com>2013-09-18 08:24:57 -0400
commit83c61051f3814f1c53d731f062643338e946d2b7 (patch)
tree39332723d843aac55f10dfc322f0faa11ef763d6
parentcab5247871e07232e5c64322b32fe9170eec4b79 (diff)
downloadmode_match-83c61051f3814f1c53d731f062643338e946d2b7.tar.gz
mode_match-83c61051f3814f1c53d731f062643338e946d2b7.zip
Readme extendedv4.0
-rw-r--r--README.t2t15
1 files changed, 12 insertions, 3 deletions
diff --git a/README.t2t b/README.t2t
index bfadaa9..337f40d 100644
--- a/README.t2t
+++ b/README.t2t
@@ -19,16 +19,22 @@ profiles after such propagation.
For a quick demo run:
``` solution_visualization_demo.m
-
== Mode matching ==
Automatically search for a way to mode match a given Gaussian beam to
desired one at given distance via set of lenses in between. Very handy for
injection of a known beam to a single mode fiber or a cavity.
-It might take a while to compute but ifor a quick demo run:
+It might take a while to compute but for a quick demo run:
``` mode_match_demo.m
+== Cavity design ==
+- calculates if resonator is stable
+- calculates and plots resonant mode profile
+
+For demo run:
+``` cavity_design_demo.m
+
= Brief history of the project =
The original code dates as old as 2004 (at least I find some files that
@@ -38,6 +44,9 @@ was started even earlier. In 2012-2013 Matt Argao extended code to
automatically find mode matching solution from given set of optical
elements.
+== Version 4.0 ==
+Cavity design module
+
== Version 3.1 ==
Demos are added/modified
@@ -48,5 +57,5 @@ Addition of the automatic mode matcher
Visual mode matcher check and beam propagation visualization
== Version 1.0 and earlier ==
-Initial abcd formalism and unrecorded modifications.
+Initial ABCD formalism and unrecorded modifications.