[INSTRM-1577] Verify the mechanism to store pfsDesing/pfsConfig information to opDB Created: 14/Apr/22 Updated: 09/Jul/22 Resolved: 09/Jul/22 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_iicActor, pfs_utils, spt_operational_database |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | Kiyoto Yabe | Assignee: | Kiyoto Yabe |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun, opDB | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | PreEngRun06June | ||||||||||||
| Description |
|
In the last run, we could not verify ingesting pfsDesign/pfsConfig information to opDB. The current opDB schema for pfsDesign/pfsConfig and the routine to populate have been implemented as a part of INSTRM-1348 . Please verify this for the next engineering run. |
| Comments |
| Comment by hassan [ 08/Jul/22 ] |
|
Kiyoto Yabe: has the mechanism been verified? Can we close this ticket? |
| Comment by Kiyoto Yabe [ 09/Jul/22 ] |
|
I think we verified the mechanism at least for pfsDesign-related tables in June run. There are still blank columns and we have not verified the pfsConfig (and intermediate pfsDesign tables if needed) yet, but a part of them have already been filed and others should be filed in future as separate tickets. |
| Comment by hassan [ 09/Jul/22 ] |
|
Based on Yabe-san's previous comment, implementation necessary for June run has been achieved and additional tickets filed. So closing this one. |