Edge merging: what could be wrong

What happened?

• somewhere, there is a radius discrepancy
• it happened at only one boundary among two

What happened?

• CCs are valleys; so edges of a CC are Infs;
  
• they need to be extended one pixel, or, re-extracted from the "holes"

What else happened?

• Wrong edges from nb attached CCs.
• Detaching function should take care of nb-FOVs by filling the necessary points in overlaps

When and how to extract bottom?

• If we do it in individual FOVs, then if one top edge is missing, the missing bottom radius can't be obtained through top edges -> has to remain NaN;
• If we do it in main-thread, then how do we trace back to what's inside the valley?
• Conclusion: In individual FOV, at least get the radial position of the missing points
  

Go back: edge

Currently: edge = all detected pixel edges
Risk: Some of them are on the same theoretical angular position, so the extracted edge is distorted (extended, spread out)
Solution:

• Don't take every point;
• Make our sampling a 2-phase process:
  
• Phase 1: the edge extraction uses a strict pixel-precision sampling, i.e., the angular sampling rate is limited to 1-pixel wide, so that at each pixel angular position, no two points exist in our edge array.
• Phase 2: audio re-sampling

Plan: don't do this until we hear the sound.

FOV chain

What should we do

• make sure it's correct for all FOV.CC.edge's

Test Design

1. For all FOV.CC.edge's in a FOV, show all nb-FOV.CC.edge, and next focus-FOV.CC.edge
   
2. For all ...., show consolidated edge

Need to do next

1. bottom r/z, NaN case
   

FOV chain, edge/bottom extraction, attach/broken

What do we have

1. FOV chain not fully tested
2. edge extraction problematic
3. bottom extraction not implemented
4. attach / broken not fully tested

What is the most important

1. FOV chain

How to achieve the most-important goal?

1. CC-edge exit points should be correct -> edge extraction....
2. does edge extraction need correct attach/broken treatment? -> not everywhere