[INSTRM-1716] Reload pfs_design_agc table using fixed pfs_utils. Created: 25/Sep/22  Updated: 01/Dec/22  Resolved: 01/Dec/22

Status: Done
Project: Instrument control development
Component/s: opdb
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: Kiyoto Yabe
Resolution: Done Votes: 0
Labels: EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-1810 Reload pfs_config_agc table with prop... Open
relates to DAMD-136 Datamodel reads in pfsDesign.guideSta... Done
Story Points: 2
Sprint: preEngRun08Nov

 Description   

DAMD-136 fixed a big where datamodel.PfsConfig loaded the guider objId as a 32-bit int instead of a 63-bit int.

But the pfs_design_agc table has been populated by older versions of that code, and the guide_star_id column is junk.

Please reload using the current pfs_utils. The version installed on pfsa is good.

 Comments   
Comment by hassan [ 25/Sep/22 ]

Appears that the same problem is apparent in the pfs_config_agc table also.

Looks like recent pfsConfig/pfsDesigns s, eg those with designId 0xb01f75df554a1ba, have been ingested without the DAMD-136 fix. But what is confusing is that the guide_star_id s in the agc_match table for this designId do look correct. This seems to imply that the agc_match table is populated differently to the pfs_design_agc table.

Example (pfs_design_id, guide_star_id) pairs investigated are:

 
0xb01f75df554a1ba, 4477444105481823616
0xb01f75df554a1ba, 4477443139107585920

(which were referred to by RHL in https://sumire-pfs.slack.com/archives/C9TDPMVHT/p1664081854893519)

So the pfs_design_id, guide_star_id values for the agc_match, pfs_design_agc and pfs_config_agc tables need to be cross-checked.

Comment by Kiyoto Yabe [ 27/Sep/22 ]

For now, only `pfs_design_agc` table was repopulated with the fixed datamodel package. We will think about `pfs_config_agc` later. We should also cross-check with `agc_match` table.

Comment by hassan [ 30/Nov/22 ]

Kiyoto Yabe: can we close this ticket and file a separate ticket on remaining actions?

Comment by Kiyoto Yabe [ 01/Dec/22 ]

Yes, I think so.

Generated at Sat Feb 10 16:38:39 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.