[SURVEY-13] Confirm whether the operational database can trace the progress of the fiber configuration Created: 24/May/19 Updated: 06/Sep/19 Resolved: 06/Sep/19 |
|
| Status: | Done |
| Project: | Survey operation on planning and tracking |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | Kiyoto Yabe | Assignee: | Kiyoto Yabe |
| Resolution: | Done | Votes: | 0 |
| Labels: | opDB | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Fiber configuration is made with some iteration with PFI and MCS. Check whether we can trace the configuration progress for a given pfsConfigId. The following may be questions:
|
| Comments |
| Comment by cloomis [ 22/Aug/19 ] |
|
I think we do want an "mcsExposure" table, which has at least rotator angle and altitude. I think the mcsActor should populate it when it is populating the centroids table. Unless there is a strong argument against this I will make a table on the running db and populate it for chyan 's fpsActor work. |
| Comment by Kiyoto Yabe [ 22/Aug/19 ] |
|
I don't have a strong objection to this. Please let me know what columns do we need. Or, I can change the model based on the results after you create the table on the living db. |
| Comment by chyan [ 23/Aug/19 ] |
|
I have started something in fpsActor. It is an interface DB accessing. I will use it for fps to DB connection. Maybe that is a good start. |