You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ledsa/README.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# LEDSmokeAnalysis
2
2
3
-
How to use LEDSA:
3
+
<b>How to use LEDSA:</b>
4
4
5
5
Set your PYTHONPATH to find the ledsa folder so the package can be imported.
6
6
Now, the package can be accessed via import ledsa.
@@ -25,11 +25,16 @@ it,there must be the coordinates of the two outermost LEDs for each LED array sa
25
25
line_edge_coordinates inside config.ini
26
26
27
27
28
-
How this git repo is structured:
28
+
<b>How this git repo is structured:</b>
29
29
30
30
To introduce new, tested and stable changes, push requests to the development branch are used.
31
+
31
32
If the master branch is not ahead of the push and no other push request to master is open, the request can go directly to master instead.
33
+
32
34
Push request drafts to the development branch can be used to communicate about changes and new functionality.
35
+
33
36
After reviewing the changes, they will be merged into the branch.
37
+
34
38
Merges to development must be tested again after merging master into it before merging it to master. If there is an open push request to master, it must be merged with development and tested as well before pushing development to master.
39
+
35
40
Every merge with master is followed by introducing a new version tag corresponding to the semantic versioning pradigm.
0 commit comments