1
1
# Simphony
2
2
A Simulator for Photonic circuits
3
3
4
+ ![ Text] ( ./docs/source/_static/images/simphony_logo.jpg )
5
+
4
6
Authors: [ Sequoia Ploeg] ( https://github.com/sequoiap ) ,
5
7
[ Hyrum Gunther] ( https://github.com/rumbonium/ )
6
8
7
9
Developed by [ CamachoLab] ( https://camacholab.byu.edu/ ) at
8
10
[ Brigham Young University] ( https://www.byu.edu/ ) .
9
11
12
+ # About this branch
13
+
14
+ Previous development branches required the component models (from which instances
15
+ are created) to be instantiated first. This attempt tries to keep them as simple
16
+ classes, removing the requirement to instantiate. It also tries to keep the
17
+ s-parameters with the classes, without so many file i/o and parsing algorithms.
18
+
19
+ # Description
20
+
10
21
This package is still under development. It initially began as an extension to
11
22
[ SiEPIC-Tools] ( https://github.com/lukasc-ubc/SiEPIC-Tools ) , but was ported here
12
23
once it became large enough to be considered its own stand-alone project. There
13
- is a repository, [ SiEPIC-Simphony] ( https://github.com/sequoiap/SiEPIC-Simphony ) ,
24
+ is a repository forked from lukasc-ubc/SiEPIC-Tools,
25
+ [ SiEPIC-Tools] ( https://github.com/sequoiap/SiEPIC-Tools ) ,
14
26
that integrates Simphony with SiEPIC-Tools and KLayout in order to perform
15
27
photonic circuit simulations using a layout-driven design methodology.
16
28
@@ -26,7 +38,7 @@ Python 2 (January 1, 2020), no future compatability is planned.
26
38
## Documentation
27
39
28
40
Documentation is built on Sphinx. They can be built using the default files by
29
- navigation to the docs directory and running:
41
+ navigating to the docs directory and running:
30
42
31
43
```
32
44
make html
@@ -36,9 +48,9 @@ The docs are written in reST. There is a nice syntax guide with guidelines that
36
48
we follow in the documentation
37
49
[ here] ( https://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html ) . The
38
50
majority of the documentation is generated from python docstrings written using
39
- NumPy documentation format.
51
+ the NumPy documentation format.
40
52
41
- The changelogs can be found in docs/changelog/. There is a changelog file for
53
+ Changelogs can be found in docs/changelog/. There is a changelog file for
42
54
each released version of the software.
43
55
44
56
## Tests
@@ -55,7 +67,7 @@ from the toplevel directory.
55
67
## Developers
56
68
57
69
This package is available on PyPI and updates are regularly pushed as "minor"
58
- or "micro" versions. Before submitting any pull requests, however, you should
70
+ or "micro" (patch) versions. Before submitting any pull requests, however, you should
59
71
ensure that a pip installation of your updated package installs and functions
60
72
properly. To test this, try installing your package locally by removing all
61
73
installed versions of Simphony (by running ``` pip uninstall simphony ```
@@ -83,16 +95,17 @@ is released on PyPI, the package should have a pull request opened to its
83
95
corresponding release branch (release-MAJOR.MINOR.x). The hierarchy is then
84
96
as follows:
85
97
86
- - release. * (stable branch)
98
+ - release- * . * .x (stable branch)
87
99
- master (integration and final testing)
88
100
- feature-name (feature development and bug fixes)
89
101
90
102
Even if you are the lone developer, we follow the methodology [ here] ( https://softwareengineering.stackexchange.com/a/294048 ) .
91
103
92
104
Be sure to update the version number manually before pushing each new version
93
105
to PyPI. Also be sure to amend the changelog. Versions can be pushed to PyPI
94
- using the command :
106
+ using the commands :
95
107
96
108
```
109
+ python3 setup.py sdist bdist_wheel
97
110
python3 -m twine upload dist/*
98
111
```
0 commit comments