[INSTRM-725] Flag suspect cobra motion as soon as possible, warn/disable cobra. Created: 01/Aug/19 Updated: 25/Mar/22 Resolved: 25/Mar/22 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | ics_cobraCharmer, ics_mcsActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | chyan |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | EngRun, PFI | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 2 | ||||||||
| Sprint: | PreEngRun05 A, PreEngRun05 B, PreEngRun05 D, PreEngRun05 E | ||||||||
| Description |
|
When doing the fiber image centroiding and the centroid-to-cobra assignment, we need to look for wildly unexpected/impossible fiber positions or focus. Not obvious what to do at that point. Certainly warn, very loudly. If the fiber is within the safe footprint, we could simply flag and disable the cobra (call it "broken"?). Outside of that we may want to stop operations? Thinking of the one broken off shaft; the worst case is bad. |
| Comments |
| Comment by chihyi [ 09/Dec/21 ] |
|
We should do this for sure, since there are always some things weird happened. But we need to do our best to identify the fiber, if we can detrmine the cobra geometry accurately, then this issue could be minimized. The cobra gemoetry could be revised after we took the first 'homed' image. |
| Comment by chyan [ 25/Mar/22 ] |
|
As discussed in the collaboration meeting, there are certain levels of "suspect" cobra motions. We have a list of suspect cobras. However, we think most of them can be fixed by tuning their frequencies and on-time. A close look of those wired cobra is needed before next engineering run. Since the system is able to return the list of non-converged cobras, I would suggest we close this ticket and create another ticket for a cobra inspection activity. |