https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-1348 Instrument control development <p>Per discussion with <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hassan" class="user-hover" rel="hassan">hassan</a>, we file a separate ticket regarding the opDB I/O for <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1278" class="external-link" rel="nofollow">INSTRM-1278</a>. The task of this ticket is to write and test (example) codes to ingest `pfsDesign/pfsConfig` files (or DataFrames from <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1278" class="external-link" rel="nofollow">INSTRM-1278</a>) to opDB and read necessary information for those tables. We actually had <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1143" title="Add a tool to ingest data from pfsDesign file to opDB" class="issue-link" data-issue-key="INSTRM-1143"><del>INSTRM-1143</del></a>, which has been already closed, but this ticket handles a complete set of `pfsDesign` file with the latest datamodel (e.g., guidestars HDU).</p> INSTRM-1348

Ingest pfsDesign/pfsConfig files to opDB

Task Normal Done Done Kiyoto Yabe Kiyoto Yabe EngRun opDB Fri, 3 Sep 2021 11:34:22 +0000 Thu, 14 Apr 2022 02:29:30 +0000 Fri, 1 Apr 2022 06:28:46 +0000 spt_operational_database 0 5 <p>I don't think we need this as part of the post-Sept run, but we do need it for November.  I propose that we remove it from the  EngRun3Cleanup sprint</p> <p> </p> <p>Now moved to PreEngRun4 sprint.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a>: following <a href="https://pfspipe.ipmu.jp/jira/browse/DAMD-120" title="Add designName to pfsDesign header?" class="issue-link" data-issue-key="DAMD-120"><del>DAMD-120</del></a>, you will need to add <tt>designName</tt> to the schema I believe.</p> <p>I have filed a separate ticket for this.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a>: as part of this work, will you provide a routine which takes a pfsDesign/pfsConfig and populates the opDB tables? That way, <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1427" title="Publish pfsConfig files when the PFI is light source" class="issue-link" data-issue-key="INSTRM-1427"><del>INSTRM-1427</del></a> can use that to write directly to the opDB.</p> <p>If that work is needed to be in a separate ticket, I can file that.</p> <p>Should that routine be in `pfs_utils` or `spt_operational_database`?</p> <p>I would say <tt>pfs_utils</tt>. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=arnaud.lefur" class="user-hover" rel="arnaud.lefur">arnaud.lefur</a>?</p> <p><tt>pfs_utils</tt> , yes.</p> <p>I pushed the routine to `pfs_utils`.  Another question: can we get timestamps (designed/configured) from pfsDesign/pfsConfig object?</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a> can we close this ticket now? Or what additional work is needed to complete this?</p> <p>I was thinking that this would be verified in the next engineering run. The implementation was completed (I guess) but we couldn't test that in Nov. In opDB side, the change has been merged, but not in `pfs_util` side yet. Should I close this ticket with the one at this moment and file another ticket for the next engineering run?</p> <p>Hi <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a> yes, that sounds like a good proposal. Please close this ticket and file a new one.</p> <p>OK, I have merged the change on `pfs_utils`. I'll file a ticket to verify the implementation.</p> Blocks INSTRM-1338 INSTRM-1352 Relates INSTRM-1577 DAMD-120 INSTRM-1427 INSTRM-1437 INSTRM-1379 INSTRM-1143 INSTRM-1278 Development Rank 0|zzs2xb: Sprint PreEngRun4 Story Points 3.0