[INSTRM-1119] Record collision history on opDB Created: 22/Nov/20 Updated: 10/Jun/22 Resolved: 10/Jun/22 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | yuki.moritani | Assignee: | karr |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun, opDB | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 3 | ||||||||
| Sprint: | PreEngRun06June | ||||||||
| Description |
|
At ICS/PFI+MCS telecon on 30 Oct 2020, Jennifer reported she had been recording which cobras had experienced collisions in the spreadsheet. We agreed that this kind of information should be recorded on opDB, so column (or table) for it needs to be added. |
| Comments |
| Comment by chyan [ 08/Dec/21 ] |
|
Currently, we did not have clear idea how to record the history of fibre collision. General speaking, we can separate information cobra-cobra and cobra-fiducial collisions. I would suggest start from cobra-fiducial collision will be easier because fiducial fibre locations are fixed and not moving with frame. |
| Comment by hassan [ 17/Dec/21 ] |
|
This could be split into two tickets: one for the cobra-fiducial fiber collisions, and one for the cobra-cobra collisions. |
| Comment by karr [ 27/May/22 ] |
|
The cobra/cobra cobra/fid calculations are very similar. I've pushed a draft plus notebook to tickets/ Note that if fibres are mid-identified (ie, when using easyID for identification), false collisions can be returned when the same spot is matched to two different cobras. This won't happen with the full identification code.
|
| Comment by karr [ 27/May/22 ] |
|
Next step would be to add cobra-elbow collisions.
|
| Comment by hassan [ 27/May/22 ] |
|
Need to discuss whether to persist the output for this. |
| Comment by karr [ 10/Jun/22 ] |
|
Will close this ticket as the code is implemented, and open another to discuss persisting hte results. |