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-621 Instrument control development <p>We will be using the STS system for propagating alerts at Subaru. We need such a system which the H4 cryostats are cold at JHU, so install and run the STS VM/container from Subaru.</p> INSTRM-621

Run real STS server at JHU

Task Normal Won't Fix Won't Fix cloomis cloomis SPS Wed, 6 Mar 2019 15:39:50 +0000 Wed, 21 Oct 2020 17:18:51 +0000 Wed, 21 Oct 2020 17:18:49 +0000 0 3 <p>The VM image and associated documents have been uploaded to <a href="https://pfs.ipmu.jp/internal/webdav/tech/software/sts/sts/" class="external-link" rel="nofollow">https://pfs.ipmu.jp/internal/webdav/tech/software/sts/sts/</a>.</p> <p>Craig needs to rename the optics lab system before performing testing. This is subject of a separate ticket that Craig will file shortly.</p> <p>Running STS server now, but requires more configuration. Will be addressed in the next few days.</p> <p>Is there a mechanism for creating fields/"data sources" which does not involve the GUI? We would like to batch this, based on config files. If not I'll create a ticket for that.<br/> FWIW we do not yet have a defined config yet so that would be part of any ticket.</p> <p>No. You will have to batch-insert them into the table by SQL then.</p> <p>So the SQL schema holds all the configuration, and simply creating rows is all we need to do? That's nice.</p> <p>Do the datum IDs need to be sequential for you? I.e. could you pre-assign a block of 1000 datums to PFS? That way we could create the correct and final configuration files for our sources, and not need to renumber them later.</p> <p>No, they don't. I think the easiest thing for us to do is to just bump the next available STS radio ID by ~1000 on the Subaru side.</p> <p>Great! However you want to do it &#8211; just tell me what range we can permanently allocate.</p> <p>1139 - 2138 have been reserved for PFS.</p> <p>Please specify STS radio IDs in your JSON configuration with "id" keys for each data sources, or modify batchconf.py and change the FIRST_STSRADIO_ID to 1139, if you are starting with the empty data source table.</p> <p>Got it, thanks. </p> <p>The title part of the ticket is no longer relevant. The STS id allocation part is encoded in the alertsActor.</p> Relates INSTRM-593 Development Rank 0|zyi00n:y Sprint 2019 C SM1-2019 E SM1-2019 G SM1-2019 K Story Points 2.0