i05 - add exit_slit device - s6 motors #435

Activity

1. oliwenmandiamond

   added a parent issue on Oct 23, 2026

   • Scripting Vertical Slice project - i05 #429
2. oliwenmandiamond

   changed the title [-]`exit_slit`[/-] [+]i05 - add `exit_slit` device - s6 motors[/+] on Oct 23, 2026
3. oliwenmandiamond commented on Oct 23, 2026

   

   oliwenmandiamond

   on Oct 23, 2026

   CollaboratorAuthor

   More actions

   I have spoken to beamline staff on this. The reason they call s6.ygap exit_slit is because every APRES beamline has a variable called exit_slit, so make it very convenient for the users.

   I have spoken to them about this, they would be fine with using the proposed solution above, on the client they make a variable called exit_slit = sy.ygap and just use that. However, all metadata and logging will refer to it as original s6.ygap.

   So we have a couple solutions:

   1. create s6 object as above. Let client rename it for convenience but still use s6.ygap object throughout server
   2. create s6 object as above, but it has a dependency on exit_slit for device creation and we create exit_slit as own device
   3. we just duplicate, we create s6 composite of motor object and we create exit_slit motor object, both using same PV

   I personally don't like option 3, I really dislike duplicating multiple objects using the same PV for the same thing, but might best way?
4. DG-At-Diamond commented on Nov 10, 2026

   

   DG-At-Diamond

   on Nov 10, 2026

   Collaborator

   More actions

   Are you saying you vote for option 3? 2 looks like the best one of these to me but 3 would be fine as well, I'm not that against reusing PVs.
5. DG-At-Diamond

   self-assigned this

   on Nov 10, 2026
6. oliwenmandiamond commented on Nov 13, 2026

   

   oliwenmandiamond

   on Nov 13, 2026

   Last edited by oliwenmandiamond

   CollaboratorAuthor

   More actions

   I've tested with blueapi, the issue with option 2 is that device manager will rename the device name to be whatever the new factory was. So I think in this case, we duplicate. But we put a clear doc string of the factory to indicate that it corresponds to s6.ygap device, why we have to duplicate, and this is specifically for ARPES annotation