Workflow recorganization in favor of sting removal

Problem

1. Sting removal involves more pre-processing than expected,
   
2. it needs to be broken down into more parent processes

Solution: new workflow

1. edge detection
2. clear edge angular redundancy
3. bottom fix (an optional set of bottom data, in addition to the original raw edge):
   
4. sting removal

Detail

1. what's the diff b/w lateral (r-wise) and vertical (z-wise) data?
   
2. from the fig., lateral top edges imply the linearity of the bottom seg in 2D.
3. however, since top edges are flat, there is no indication of the undulation of the bottom from viewing the top.
4. if only we can trust the width and use w/z ratio to fix it...., but for sting removal, we can't trust it.
   
5. we won't trust the sting segs, but we can trust most segs along the groove.
   
6. from angular redundancy test, we know roughly where the stings are.
   
7. to think out of the box, if stings are gone, we can fix the z data by using w/z;
8. before this can happen, we can't trust w/z as a condition but a question.
9. so the bottom fix should take two steps,
   
10. before sting removal, simply do lateral fix, i.e., much like groove retaching, retach the bottoms in the sense of CC angular link.
11. after sting removal, and the main-thread construction, we fix the depth by further w/z-based method.