pcdshub / btms-ui Goto Github PK

Current Behavior

The current screen is just a Typhos screen. This is fine as an expert level screen, but I think there should be a simpler screen available for basic camera operation, similar to the widgets that are available for the motors.

Having a screen like this would be a good place to add a save centroids button described in #10 .

Possible Solution

Make a small UI similar to the motor typhos widgets.

Expected Behavior

Homing the BTMS stages is easy.

Current Behavior

Due to the mechanics of the stages, there are sometimes issues with homing these stage stacks. It would be best if we could automate the stages so that operators could more easily restore normal operation.

The issues related to homing have been documented here:
https://confluence.slac.stanford.edu/display/L2SI/Beam+Transport+Troubleshooting

The python code here would likely have to be updated and appropriate buttons added to the screens in this repo.

Expected Behavior

All the GUI elements behave identically

Current Behavior

Two of the combo boxes for source destination are compressed for some reason. See the screenshot below.

Context

Your Environment

This makes the target destination hard to read.

Expected Behavior

We have all working laser sources supported via the GUI

Current Behavior

We are missing LS3, LS4, LS5, and LD1 (relatively new additions).

Possible Solution

Figure out how to add them and do it.

Context

We're in the middle of updating the BTS during the summer down. This has included 3 new source lines. One destination line (the diagnostics line) was added during the previous spring/winter.

Expected Behavior

We probably want something similar to #3 for centroids

Current Behavior

We don't have any acknowledgement

Possible Solution

Copy-pasta the code from the motion position save function, or figure out a nice way to make one function that works for both.

Expected Behavior

The repo has GH actions that actually run

Current Behavior

This repo got set up with required GH actions, but they aren't set up to run for some reason. This is preventing PRs from being merged.

Possible Solution

Configure the GH actions to run.

Current Behavior

The "Save Centroids" button is only available when clicking the "motion" expert screen. This is kind of weird.

Possible Solution

Add to a camera specific screen, similar to the motion expert screen.

Current Behavior

When saving the nominal positions of a motor assembly in the BTPS/BTMS system, the positions are silently saved if you are within the nominal range of operation for a destination. This is in contrast to saving in the "unknown" position, where the system will respond with a prompt, so the users know that something is happening.

Expected Behavior

Users would like acknowledgement that their positions were saved, regardless of if they are within nominal range or not.

Context / environment

This created some uncertainty in the laser group about whether or not something was actually saved. Manual inspection showed that it was.