26

edits

Jump to navigation
Jump to search
##
Geometry package:GSoC17
(edit)

###
Revision as of 10:00, 1 August 2017

140 bytes added
, 10:00, 1 August 2017

→Syncing matGeom and geometry

Line 61:
Line 61:
−

===Syncing matGeom and geometry===

===Syncing matGeom and geometry===

The goal is to devise a somewhat automated way to ensure that the functions which are there in geometry are synced with those in matGeom without manually checking the edits.

The goal is to devise a somewhat automated way to ensure that the functions which are there in geometry are synced with those in matGeom without manually checking the edits.

−To achieve this, first a workaround is implemented on a dummy repository [https://github.com/piyush-jain1/dummyMatGeom/ dummyMatGeom]. Its master branch is matGeom (dummy) and there is another branch (named geometry) is created which contains geometry package (dummy). ~~Lets assume that local directory of matGeom is named as ~~dummyMatGeom and ~~local directory of ~~geometry ~~is dummyGeom~~. Then~~, ~~follow ~~these ~~steps ~~:~~

+1. go to the local dummyMatGeom directory and pull upstream (dummy matGeom) using these commands :

+To achieve this, first a workaround is implemented on a dummy repository [https://github.com/piyush-jain1/dummyMatGeom/ dummyMatGeom]. Its master branch is matGeom (dummy) and there is another branch (named geometry) is created which contains geometry package (dummy).

+To test the entire procedure, go to the dummy repository [https://github.com/piyush-jain1/dummyMatGeom/ dummyMatGeom, pull both branches in different folders, say "dummyMatGeom" for master branch and "dummyGeom" for geometry branch.

+Then follow the given steps.

+1. go to the local dummyMatGeom directory (named dummyMatGeom) and pull upstream (dummy matGeom) using these commands :

- git fetch origin master

- git fetch origin master

- git reset --hard FETCH_HEAD

- git reset --hard FETCH_HEAD

Line 84:
Line 87:
4. Now, update your local geometry repo by force pulling from the remote branch.

4. Now, update your local geometry repo by force pulling from the remote branch.

- git pull -f origin master:geometry

- git pull -f origin master:geometry

+
+
* '''Challenges : '''

* '''Challenges : '''

−Clearly, the above procedure will only sync the script of the function, not it's tests and demo, which are in separate folders in a Matlab package structure. Even if we try to concatenate their corresponding test/demo scripts with the function scripts (as it is in an octave package structure), there will be discrepancies because the notion or writing tests for octave and matlab packages are quite different. The way octave allows tests to work is unique to octave as explained [http://wiki.octave.org/FAQ#What_features_are_unique_to_Octave.3F here]. SO, we can't simply concatenate the Matlab test scripts with the functions. ~~ ~~

+Clearly, the above procedure will only sync the script of the function, not it's tests and demo, which are in separate folders in a Matlab package structure. Even if we try to concatenate their corresponding test/demo scripts with the function scripts (as it is in an octave package structure), there will be discrepancies because the notion or writing tests for octave and matlab packages are quite different. The way octave allows tests to work is unique to octave as explained [http://wiki.octave.org/FAQ#What_features_are_unique_to_Octave.3F here]. SO, we can't simply concatenate the Matlab test scripts with the functions.

=== Discoveries ===

=== Discoveries ===

26

edits

Retrieved from "https://wiki.octave.org/Special:MobileDiff/10453"