Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Commit 598ba4fe authored by augustin_s's avatar augustin_s :snake:
Browse files

Update README.md

parent a2929824
No related branches found
No related tags found
No related merge requests found
...@@ -10,11 +10,11 @@ The `data` folder contains some channel lists and output files for testing. ...@@ -10,11 +10,11 @@ The `data` folder contains some channel lists and output files for testing.
## check ## check
`./sani.py check data/test_chans_good.txt` `./sani.py check data/test_chans_good.txt`
<br>
<img src="docs/check_good.png" width="491"> \ <img src="docs/check_good.png" width="491">
`./sani.py check data/test_chans_bad.txt` `./sani.py check data/test_chans_bad.txt`
<br>
<img src="docs/check_bad.png" width="491"> <img src="docs/check_bad.png" width="491">
Successful connections will be marked in green, failed connection in red, and alarm states will be printed in yellow. Successful connections will be marked in green, failed connection in red, and alarm states will be printed in yellow.
...@@ -23,11 +23,11 @@ Successful connections will be marked in green, failed connection in red, and al ...@@ -23,11 +23,11 @@ Successful connections will be marked in green, failed connection in red, and al
## compare ## compare
`./sani.py compare data/test1.csv data/test4 -v` `./sani.py compare data/test1.csv data/test4 -v`
<br>
<img src="docs/compare_good.png" width="568"> \ <img src="docs/compare_good.png" width="568">
`./sani.py compare data/test1.csv data/test3` `./sani.py compare data/test1.csv data/test3`
<br>
<img src="docs/compare_bad.png" width="658"> <img src="docs/compare_bad.png" width="658">
Entries that are identical in both files will not be shown. Differences will be printed as `LEFT | RIGHT`. Entries that are identical in both files will not be shown. Differences will be printed as `LEFT | RIGHT`.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment