@@ -16,7 +16,7 @@ This is absolutely not a comprehensive guide of git development, and it is only
16162) Set up a github account.
17173) Clone OpenPiv repository using::
1818
19- git clone http://github.com/alexlib /openpiv-python.git
19+ git clone http://github.com/openpiv /openpiv-python.git
2020
21214) create a branch `new_feature ` where you implement your new feature.
22225) Fix, change, implement, document code, ...
@@ -28,18 +28,18 @@ This is absolutely not a comprehensive guide of git development, and it is only
2828
292911) Create another branch for a new feature.
3030
31- Which language can i use?
31+ Which language can I use?
3232-------------------------
3333As a general rule, we use Python where it does not make any difference with code speed. In those situations where Python speed is
3434the bottleneck, we have some possibilities, depending on your skills and background. If something has to be written from scratch
35- use the first language from the following which you are confortable with: cython, c, c ++, fortran . If you have existing, debugged, tested code that
35+ use the first language from the following which you are confortable with: Cython, C, C ++, FORTRAN . If you have existing, debugged, tested code that
3636you would like to share, then no problem. We accept it, whichever language may be written in!
3737
38- Things OpenPiv currently needs, (in order of importance)
38+ Things OpenPIV currently needs, (in order of importance)
3939--------------------------------------------------------
40- * The implementation of advanced processing algorithms
41- * Good documentations
40+ * Good documentation (in progress)
41+ * The implementation of advanced processing algorithms (in progress)
4242* Flow field filtering and validation functions
43- * Cython wrappers for c/c ++ codes.
44- * a good graphical user interface
43+ * Cython wrappers for C/C ++ codes.
44+ * A good graphical user interface (in progress)
4545
0 commit comments