config update: test measurement and initial thinking

<test config>
1. backscan depth, modthresh
2. speed, intensity
- FilterIntensity0=1,85
- VSISpeed=23
--V:11, I: 52
--V:3, I:23
--V:1, I:14.5
3. specify grid files in config
- STAGEFILENAME=
4. tilt
5. automation
- AUTORUNFLAG=1
- RESETSEQUENCE=1
- USESTAGE=1
<refocusing>
1. see whether backscan accounts for measurement,
if true, then starts really low, we are still fine
- true
2. two-phase, focus stay deep below the bottom
- phase 1, use only backscan and set depth to zero; those who cannot survice this phase need refocusing in phase 2
- phase 2, from the analysis of phase 1, we refocus

<organize output opd from iteration>
- good data accumulate in a group

- bad data found -> compare with stats of the good data,

<reginal random sampling>
don't do full random, finely divide the entire surface into subrigion, then sample within each (sub dividing scheme flexible)

<python>
1. ini parser

<matlab>
0. grid division and sampling
1. opd analysis
2. output read-for-parse to python
3. read history of python

1. if starting high above,
- then we tend to miss bottom > top from above
- to get the top and hopefully the bottom again, we need to lower the lens or enlarge the depth
- matlab should
- extract all problematic FOVs,
- put them into a new grid
- make the decision whether to do a manual turret-- or simply depth++
2. matlab also need to
- to move up or down?
- no idea, unless we try twice, first down, then up
- how much for the next iteration?
- if new backscan+length > THRESH, we need to manually refocus

3. top only, if down 1*gd (groove depth), if bottom only or nothing, back up for 20um; init focus?
4. NO USE measuring initial depth, because whatever result we get, even if we ge the top, we don't konw which portino it appears along the veritical scale of our chosen depth

<grid>
1. grid should be calc through multi-parts of the whole circle, right half has larger radius!!
2. remedy code, enlarge circle!