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-119 Instrument control development <p>The XCU, CCD, and HX actors all either have or will have device configuration which needs to be tracked. Examples:</p> <ul> <li>per-ccd bias offsets, other voltages</li> <li>per-motor ranges and limits</li> <li>current thresholds to track</li> <li>temperature/power/etc setpoints</li> <li>many others.</li> </ul> <p>These should not be in the code products. Much of it currently is.</p> <p>Can this list be fleshed out by LAM? Any design comments welcome.</p> <p>I'll start by proposing a tree of YAML files, one directory per actor, and one configuration item per line. I'm imagining a "default" configuration file, plus overrides. </p> <p>I'll point out that this might be the place to declare alarm thresholds, and perhaps everything which is currently in the hated ics_xcuActor/etc files. Also, the PFI configuration should not be part of this.</p> INSTRM-119

Move device configuration into ics_config product.

Task Normal Won't Fix Won't Fix cloomis cloomis Wed, 31 May 2017 14:18:20 +0000 Thu, 27 Jan 2022 16:31:12 +0000 Thu, 27 Jan 2022 16:31:12 +0000 0 3 <p>For enu, we absolutely need to track slit configuration : <b>home, tool</b> coordinates systems which come from the slit alignment procedure. For now, I was pushing it as a keyword so I can retrieve the history from the archiver.<br/> But I agree that ics_config would be a good place to put it. </p> <p>We need to talk about that next week, especially if we link that to alarm handling also</p> <p>Showed proof-of-concept to Fabrice and Arnaud. Since they will be using this, I'm asking Arnaud to review. I'd like to come out of this shutdown using both <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-119" title="Move device configuration into ics_config product." class="issue-link" data-issue-key="INSTRM-119"><del>INSTRM-119</del></a> and <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-28" title="Provide an id object to track site, camera, spectrograph, etc." class="issue-link" data-issue-key="INSTRM-28"><del>INSTRM-28</del></a></p> <p><a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-28" title="Provide an id object to track site, camera, spectrograph, etc." class="issue-link" data-issue-key="INSTRM-28"><del>INSTRM-28</del></a> is a partial requirement, since it provides a namespace for spectrograph ID interpolation.</p> <p>Interpolation is currently only done on individually fetched strings, which I think is sufficient for current needs. I think I should add an option to recursively check for strings in the returned data structure.</p> <p>That's good for me. <br/> The syntax of the YAML file can be a bit tricky. But they are really powerful and interpolate names allow to factorize even more.<br/> It will definitely make our life easier.</p> <p>which part did you feel tricky? we might be better to have them documented not to get confused and bug..</p> <p>This ticket is marked as review completed, but nothing has done on github.<br/> Just raise what to do <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>Ticket has already been addressed as part of other work.</p> Blocks INSTRM-28 Duplicate INSTRM-1281 Relates INSTRM-132 Development Epic Link INSTRM-136 Rank 0|ii02nf: Reviewers arnaud.lefur Sprint 2017-10A