[INSTRM-1490] Solving why Nov convergence tests showed inconsistent numbers in different iteration Created: 16/Dec/21  Updated: 11/Feb/22  Resolved: 23/Jan/22

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Attachments: PDF File 69990.pdf     PNG File Figure 1-19.png     PNG File Figure 1-7.png     PNG File Figure 1-8.png     PNG File Screen Shot 2021-12-16 at 12.55.12 AM.png    
Issue Links:
Relates
relates to INSTRM-1506 Comparing frame-by-frame and first-fr... Done
relates to INSTRM-1498 Taking seeing data with dome opened a... Won't Fix
Story Points: 6
Sprint: PreEngRun05 A, PreEngRun05 B

 Description   

During the November engineering run, we did the convergence test at different EL angles.  However, we see the strange phenomenon in visitID=69990.  As you can see from plot, the 12th iteration is not the best result.  We need to investigating the reason.  

 Comments   
Comment by chyan [ 16/Dec/21 ]

We select cobra ID 1400 as our example.

 In the following plot, we see the cobra steps are zero after the cobra reaches the 10 micron area.  

Therefore, we are certain that the cobra is not moving when it reaches the targets.  

Comment by yuki.moritani [ 17/Dec/21 ]

In formal telecon on 17 Dec. Chi-Hung will check FF fiber positions to see if it is seeing effect or not.

Comment by chyan [ 06/Jan/22 ]

In this file 69990.pdf, I plotted the variation of FF. As we can see, there are frame-by-frame effect in FFs. Therefore, I did the same test on test bench. The results showed that the number of converged fibers are consistent with previous tests. This suggested that the frame-by-frame correction is needed.

Comment by hassan [ 14/Jan/22 ]

chyan will close this ticket and file a new ticket to cover the frame-by-frame and first frame only methods.

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