Changes between Version 4 and Version 5 of GSoC/2016/Additional_segmentation_algorithms/weekly_report

Timestamp:

May 29, 2016, 10:46:59 AM (8 years ago)

Author:

hao2309

Comment:

--

GSoC/2016/Additional_segmentation_algorithms/weekly_report

@@ -22 +22 @@
 == 16 – 21 May week 0: Setup coding environmental, get familiar with programming manual ==
 * A small exercise too get more familiar with basic GRASS code
-
 >>Moritz:
 >>As as part of bonding period, and as you are now able to compile GRASS, I would like to propose a small exercise which is already a first step in the direction of your project and which should allow you to become a bit more familiar with the code and with coding practices: As currently i.segment only provides one algorithm, the entire layout of the module GUI is related to that one algorithm. In the attached screenshot you see the current GUI. My idea would be to have the three  mandatory inputs in the Required tab, then one tab per algorithm with algorithm-specific parameters, then the Optional tab. Otherwise, I'm afraid that the current'Settings' tab becomes overcrowded.
-
-
+>>
 >>The code that defines options and which 'guisection' they are in is in parse_args.c [1]. For more info about how the command parser and its options work, see [2], but the existing examples in the code might already be enough.
-
+>>
 >>You can add new parameters there without them being used in the code, yet, so don't hesitate, at this stage, to add one phony parameter per new algorithm, just to get the relevant tabs.
-
+>>
 >>Once you've done this, compile just the i.segment module (by running make in the directory) and see if the GUI corresponds to what you aim for. Then, send me a diff of the code.