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-727 Instrument control development <p>Broken cobra tracking is currently ad-hoc (lists in code). We should load those into the <tt>pfiDesign</tt> object, since that is what tracks the configuration of the modules. </p> <p>We could do this in two ways. There is a status field (unused?) in the XML file, which would keep all arm/module info in one file (good!). Or we could persist into a/the per-module YAML file in <tt>pfs_instdata</tt>. Inclined to use the status field for now; will look for any existing usage.</p> <p>Will branch this off <tt>cit_freeze</tt>.</p> INSTRM-727

Add broken cobra handling to the pfiDesign object.

Task Normal Done Done cloomis cloomis CanBeClosed PFI cit_freeze Thu, 1 Aug 2019 16:24:37 +0000 Thu, 23 Feb 2023 08:24:27 +0000 Thu, 23 Feb 2023 08:24:27 +0000 ics_cobraCharmer 0 1 <p>Went for using the XML Status field. That is currently always 1, indicating a good cobra. For backward compatibility, will keep bit 0 as indicating that the cobra is fully OK or not. And am adding, for now:</p> <ul class="alternate" type="square"> <li>bit 1: inoperable. If the cobra should not physically be commanded.</li> <li>bit 2: invisible. If the fiber cannot be seen.</li> </ul> <p>Chi-Hung has ideas for more bits, but those two cover the current issues. The <tt>PfiDesign</tt> object has grown accessors (.getGoodCobraMask(), etc), and a method to set a cobra's status.</p> <p>As of 2023 Feb, the broken cobras were listed in xml file, and branches were merged.</p> Development Rank 0|zzsvva: Story Points 1.0