-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Component/s: ics_alertsActor, SPS, STS
-
Labels:None
SPS was assigned a large pre-allocation of STS ids. If I remember right, 1000 starting at 1140, or something similar.
We were slightly careless about using that range for SM1, and would like to renumber the two existing rough1 IDs so that we can assign to all the SPS components with a straightforward formula. SM1 was allocated with 60 IDs per cryostat (very many!!); 200 total per module, so we might as well stick to that basic numbering and make it useable for SM1-4.
stsBase = 1140 smNbase = stsBase + smModuleNum * 200 # 0..3 camArmNBase = smNbase + armNum * 60 # r=0, b=1, n=2 enuNbase = smNbase + 180 roughNbase = stsBase + 4*200 + roughN*10 # 0..1
In other words, can we renumber rough1's 1280 and 1281 STS ids to 1940 and 1941, Yoshida, Hiroshige? This would need to be done in sync with the matching alertsActor change.
Note: the camera numbering is r,b,n, but I do not think we should change all that.
Added logic in the ticket description, plus sts.host and alerts.parts configuration tweaks. config/STS.yaml has been regenerated with the requested renumbering.
I believe that if we stopped alertsActor, renumbered the two STS ids, then restarted with this version of the actor we would be done.
alertsActor changes reviewed by arnaud.lefur, merged at 65fb488, tagged 1.2.0. Installed at Subaru.
Next step: stop running alertsActor, renumber rough1 ids in STS, start this version.
merged a while ago
Yes, we can do this.