[INSTRM-621] Run real STS server at JHU Created: 07/Mar/19 Updated: 22/Oct/20 Resolved: 22/Oct/20 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 2 | ||||||||
| Sprint: | 2019 C, SM1-2019 E, SM1-2019 G, SM1-2019 K | ||||||||
| Description |
|
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. |
| Comments |
| Comment by Yoshida, Hiroshige [ 07/Mar/19 ] |
|
The VM image and associated documents have been uploaded to https://pfs.ipmu.jp/internal/webdav/tech/software/sts/sts/. |
| Comment by hassan [ 14/Mar/19 ] |
|
Craig needs to rename the optics lab system before performing testing. This is subject of a separate ticket that Craig will file shortly. |
| Comment by hassan [ 21/Mar/19 ] |
|
Running STS server now, but requires more configuration. Will be addressed in the next few days. |
| Comment by cloomis [ 31/May/19 ] |
|
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. |
| Comment by Yoshida, Hiroshige [ 31/May/19 ] |
|
No. You will have to batch-insert them into the table by SQL then. |
| Comment by cloomis [ 31/May/19 ] |
|
So the SQL schema holds all the configuration, and simply creating rows is all we need to do? That's nice. |
| Comment by cloomis [ 04/Jul/19 ] |
|
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. |
| Comment by Yoshida, Hiroshige [ 04/Jul/19 ] |
|
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. |
| Comment by cloomis [ 04/Jul/19 ] |
|
Great! However you want to do it – just tell me what range we can permanently allocate. |
| Comment by Yoshida, Hiroshige [ 04/Jul/19 ] |
|
1139 - 2138 have been reserved for PFS. |
| Comment by Yoshida, Hiroshige [ 04/Jul/19 ] |
|
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. |
| Comment by cloomis [ 04/Jul/19 ] |
|
Got it, thanks. |
| Comment by cloomis [ 22/Oct/20 ] |
|
The title part of the ticket is no longer relevant. The STS id allocation part is encoded in the alertsActor. |