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-289 Instrument control development <p>Can we get a couple of STS tables which we can actually populate, just to test the plumbing and the STS python module? In STSradio.conf terms, something like (timestamp plus float):</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>LINE DT(F1,%y-%m-%d?%H:%M:%S?????) D9990(F2,%f) </pre> </div></div> <p>and maybe one covering all the basic types:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>LINE DT(F1,%y-%m-%d?%H:%M:%S?????) D9991(F2,%c) D9992(F3,%d) D9993(F4,%f) </pre> </div></div> <p>Call the columns anything you want.</p> <p>FYI the <tt>?????</tt> in the timestamp was an arrangement to put the HAST timezone in the datafile: STS require(sd) data in that TZ but does not parse the trailing timezone string, and we wanted to make the timezone explicit even though it was ignored. Obviously if any of that has changed please adjust.</p> <p>In the immediate term I can test from the existing STS client <tt>charis.sum.subaru.nao.ac.jp</tt>. I'll open a second ticket for getting access to and from a proper PFS machine.</p> INSTRM-289

Create test STS tables

Task Normal Done Done Yoshida, Hiroshige cloomis Wed, 7 Feb 2018 13:02:35 +0000 Wed, 7 Feb 2018 21:53:11 +0000 Wed, 7 Feb 2018 21:53:11 +0000 0 3 <p>If we have known MCS keywords, we could also use those. Specifically, if there are obvious detector temperatures we could make that a datum now.</p> <p>Are you developing a STS client (actor) based on the STS client module David wrote (STSlib.py or STSlib.c)? Are you trying to collect and send data programmatically or parse some log files to extract the latest data? When you call a method that updates the internal dictionary of the STS library, you need to pass a timestamp in seconds from the UNIX epoch. In other words, it does not matter how timestamps are textually represented within PFS?</p> <p>I can create Integer, Real, Text, Integer+Text, Real+Text, and Float type data for test purposes and let you know their IDs.</p> <p>Yes, <tt>STSlib.c</tt> or preferably <tt>STSlib.py</tt>, though I'd like to modify the python version a bit before using it.</p> <p>I specifically do <em>not</em> want to run the external <tt>STSradio</tt> program and point it at log files, which was the recommended solution. Instead, an actor which sees all the PFS keyword traffic will forward some of that to the STS using the <tt>STSlib.py</tt> scheme. That is what I'd like to test for real.</p> <p>The timestamp representation was only required for the <tt>STSradio</tt> log file parsing. I should perhaps not have sent it as an example.</p> <p>For the test tables, those would be perfect. Thanks.</p> <p>I have defined six (6) data sources. They are in the "Playground" public data set. Below is the list of sources and their "datum IDs" (STSradio IDs). It is <b>very important</b> for us to use the correct IDs! There should not be any difference between Float and Exponent (both are for real numbers).</p> <div class='table-wrap'> <table class='confluenceTable'><tbody> <tr> <th class='confluenceTh'>Name</th> <th class='confluenceTh'>Type</th> <th class='confluenceTh'>Datum ID</th> </tr> <tr> <td class='confluenceTd'>Playground: Integer</td> <td class='confluenceTd'>Integer</td> <td class='confluenceTd'>1090</td> </tr> <tr> <td class='confluenceTd'>Playground: Float</td> <td class='confluenceTd'>Float</td> <td class='confluenceTd'>1091</td> </tr> <tr> <td class='confluenceTd'>Playground: Text</td> <td class='confluenceTd'>Text</td> <td class='confluenceTd'>1092</td> </tr> <tr> <td class='confluenceTd'>Playground: Integer with Text</td> <td class='confluenceTd'>Integer with Text</td> <td class='confluenceTd'>1093</td> </tr> <tr> <td class='confluenceTd'>Playground: Float with Text</td> <td class='confluenceTd'>Float with Text</td> <td class='confluenceTd'>1094</td> </tr> <tr> <td class='confluenceTd'>Playground: Exponent</td> <td class='confluenceTd'>Exponent</td> <td class='confluenceTd'>1095</td> </tr> </tbody></table> </div> <p>Thanks! I'm calling this done. I'll probably test early next week when I can focus on this.</p> <p>And yes, I am aware of the importance of using the right IDs. Scary!</p> Development Rank 0|ii03vj: