image-2019-09-03-15-05-17-678.png
image-2019-09-03-15-10-02-523.png
[INSTRM-754] fiberIds are incorrect in (at least) mcsData and CobraConfig tables Created: 04/Sep/19 Updated: 08/Dec/21 Resolved: 08/Dec/21 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | rhl | Assignee: | chyan |
| Resolution: | Done | Votes: | 0 |
| Labels: | MCS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
image-2019-09-03-15-05-17-678.png
image-2019-09-03-15-10-02-523.png
|
| Reviewers: | hassan |
| Description |
|
Looking at the data for e.g. visits BETWEEN 1762300 AND 1762349 I discovered that the fiberIds in the database are incorrect. For example, for fiberIds 102..103 the figure shows that the spots at e.g. y = 960 are assigned to fibres 102 and 103.
The problem also shows up in the mapping of nominal positions to fiberId:
Note that as a function of visit number the fiberIds change |
| Comments |
| Comment by chyan [ 23/Oct/19 ] |
|
The fiberID in mcsData and mcsData is the raw data retuned by MCS camera. According to the original design, the MCS will not When matching with the science fibers or fiducial fibers, the fiberID in mcsData is dropped. You can see the code in FpsCmd.py under fpsActor (from line 162 - 186). Instead, the correct fiberIDs are populated after the matching. In the current software structure, we use testLoop function in FpsCmd.py. All the matching results are discarded without saving them. Therefore, the fiberID is not correct in mcsData. So, I need advise how to populate these matched data. Kiyoto Yabe and cloomis Any idea? |
| Comment by chyan [ 08/Dec/21 ] |
|
I would like to close this ticket since this should be replaced my another ticket
|
