[PIPE2D-997] Measurement error in black dot optimization routine Created: 05/Mar/22  Updated: 19/Mar/22  Resolved: 19/Mar/22

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: ncaplar Assignee: ncaplar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File example_of_bot_left_corner_Nov_run.png     PNG File example_of_top_right_corner_Nov_run.png     PNG File sigma_of_solutions.png    
Issue Links:
Relates
relates to PIPE2D-954 Incorporate black dot optimization al... Done
Story Points: 2
Sprint: 2DDRP-2022 B

 Description   

yuki.moritani noticed that the solutions of black dots optimizations are different between February and January run (even though the setup is the same). This is not unexpected - the black dot optimization algorithm has some inherit uncertainty because the initial simplex for Nelder-Mead is generated from random distribution.
The goal is to estimate what is the distributions of the results between runs that operate on the same dataset. As Robert states in the comments, we need to estimate if these differences are significant. Depending on the result, it might be needed to modify/improve the algorithm.



 Comments   
Comment by rhl [ 05/Mar/22 ]

The problem is presumably that there are multiple local minima, otherwise the initial simplex wouldn't matter. Are the differences significant? If so, we'll have to switch to something that explores the full parameter space (e.g. by simulated annealing), and/or use MCMC to evaluate the errors. Sounds slow!

Another option would be to take more cobra tracks through the spots; I think that'd be better

Comment by ncaplar [ 11/Mar/22 ]

I have ran 101 iterations of the algorithm for November, January and February data.
The scatter of the solutions around the median solution for each spot is shown at (note that scaling is different for November panel!!!) !sigma_of_solutions.png|thumbnail! - for some reason the image is not rendering for me?

The quantity I am showing is a mean scatter, where I calculated scatter along x and y dimensions independently, and then take mean of those two values.

As we can see the scatter of solutions is large, and dependent on the position on the plane. For example, look at the distribution of solution for the spot in absolute top right corner for November run (left panel - arrow point to median solution, small black dots and solutions from individual runs). We see that the solution is very degenerate because of the lack of constraining power along one of the dimensions

Having said that, even in best case (bottom left), there is still quite large scatter (50 microns in each dimension)

Comment by ncaplar [ 19/Mar/22 ]

Discussed on ICS telecons on March 18, 2022 and March 16, 2022. The algorithm has sufficient precision, given the quality of the data. Will be tested with data where there is actual double crossing of black dots across the focal plane.

Generated at Sat Feb 10 16:00:59 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.