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-1574 Instrument control development <p>There are several FF disabled because the position is unstable and affects on accuracy/precision of the coordinate transformation. These position need to be stored either on pfs_insdata or on operation database, depending on how static they are. Like dot position (<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1535" title="Determine (again) the places to store the dot position" class="issue-link" data-issue-key="INSTRM-1535"><del>INSTRM-1535</del></a>), it can be stored pfs_insdata first, and if they are found rather dynamical, these information should be moved to operatn database.</p> <p>By the way, where the ID and position of the broken FFs are stored at present?</p> INSTRM-1574

Store disabled FF information

Task Normal Done Done karr yuki.moritani EngRun Fri, 8 Apr 2022 19:43:23 +0000 Wed, 14 Sep 2022 05:01:51 +0000 Wed, 14 Sep 2022 05:01:51 +0000 0 4 <p>According to the discussion in ICS/MCS meeting, we have create ticket <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1581" title="Adding a mask field to the fiducial fiber table in opDB" class="issue-link" data-issue-key="INSTRM-1581"><del>INSTRM-1581</del></a> to address this issue. It is suggested to use the bit mask to indicate the FF status. So, I would suggest to close this ticket.</p> <p>It is nice to have bit mask on opDB. Please confirm that FF status is dynamic? For example, Cobra status (disabled etc.) are stored in xml file, and the status are ingested to opDB too, arent' they? I' wonder if it is nice to have the same thing...</p> <p>Currently, the bit `mask` column is in `fiducial_fiber` table, which is basically static. `fiducial_fiber_geometry` is a more dynamic table, which can be updated every time we do measurement. So, I guess that bit mask should be in this table if the information persists in opDB.</p> <p>I've put the bad fibre information (as well as the indices out the outer ring fiducials that are used for the initial mask) in a yaml file in pfs_instdata, which is read using a routine in mcsRoutines/mcsRoutines.py. </p> <p>Code has been check to make sure the routines returns the same values as teh code previous in McsCmd.py</p> <p>Both ticket branches (pfs_instdata and ics_mcsActor) are tagged 1661, as there are two tickets related to this work. </p> <p> </p> <p> </p> <p>According to the meeting with <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a>, we need to think further about where `mask` should be in order to trace the history of the mask update.</p> <p>At the moment I have a yaml file; ultimately, I think incorporating it into the butler with a sequence of dated files and automatic read of the most recent would work best. (ie, the same way the geometry files/dot files are handled). </p> <p>branch 1661 of pfs_instdata merged to master (with the yaml file)</p> Relates INSTRM-1661 INSTRM-1620 Development Rank 0|zzsui6:r Sprint preEngRun07Sep Story Points 2.0