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-1099 Instrument control development <p>Currently, we are not forwarding any bench temperature to STS.<br/> All 20 values would be overkill, so we need basically to decide which one to forward.</p> <p>Another solution would be to take the median as <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl" class="user-hover" rel="rhl">rhl</a> proposes.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=fmadec" class="user-hover" rel="fmadec">fmadec</a> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> any opinion ?</p> INSTRM-1099

Forward bench temperature values to STS

Task Normal Done Done arnaud.lefur arnaud.lefur SPS Fri, 6 Nov 2020 15:13:16 +0000 Wed, 15 Feb 2023 01:48:14 +0000 Wed, 15 Feb 2023 01:48:14 +0000 ics_alertsActor ics_enuActor 0 2 <p>A median sounds decent, I guess. Isn't STS intended for a) values which can trigger alarms, and b) values which day staff use to interpret the <em>health</em> of the instrument? For any more detailed investigations, the PFS plot tools will always be better. Sending tons of informative but not important values to STS just clogs up a view of what should be essential information.</p> <p>I've created some aggregate keys in enuActor that could be representative.<br/> Basically 3 values : </p> <ul> <li>mean of the bench temperature outside cover.</li> <li>the temp inside the covers.</li> <li>delta between those two.</li> </ul> <p>I'll push those new keys to STS, whenever I confirm that's good.<br/> but I need a bit more data, especially for sm3.</p> Development Rank 0|02qpgz:8 Sprint SM1PD-2021 A 12 2DDRP-2023 A