Skip to content

FIX: ctrlenv PYDM_DISPLAYS_PATH#344

Merged
vespos merged 1 commit into
masterfrom
zlentz/fix_pydm_displays_path
Jul 23, 2026
Merged

FIX: ctrlenv PYDM_DISPLAYS_PATH#344
vespos merged 1 commit into
masterfrom
zlentz/fix_pydm_displays_path

Conversation

@ZLLentz

@ZLLentz ZLLentz commented Jul 23, 2026

Copy link
Copy Markdown
Member

Description

Set up the previously forgotten PYDM_DISPLAYS_PATH in ctrlenv_setup.sh
This will point first to our released screens area, and then second to the dev screens area.

Motivation and Context

We had some screens previously that relied on this environment variable being set in order to locate some displays to embed in the screen.

One example is the KFE vacuum screen: https://github.com/pcdshub/lcls-pydm-vacuum/blob/62ca8dfbe53e60467e46121ba589ff8ab3116a2a/screens/sxrVac.ui#L1168

For context, here's how it was set up previously for dev_conda and pcds_conda:

export PYDM_DISPLAYS_PATH="${PCDSDEVICES_PROD_UI}:${TYPHOS_PROD_DEVICES_UI}:${PCDSDEVICES_DEV_UI}:${EPICS_DEV}/screens/pydm:${EPICS_DEV}"

Compared to before, I have:

  • Removed all dedicated dev typhos directories, because I don't want to deploy typhos screens like that any more
  • Add in the prod/released ui directory, because I want people to be able to do e.g. common/v1.0.0/screen_name.ui as a versioned embedded display. (It also seemed strange to me that only the dev directory had path support here).

How Has This Been Tested?

I made sure the KFE vacuum screen opened correctly with this environment variable set. (Previously, it opened up with errors)

Where Has This Been Documented?

Here only

@ZLLentz
ZLLentz requested a review from a team as a code owner July 23, 2026 01:33
@vespos
vespos merged commit 13b4db4 into master Jul 23, 2026
7 checks passed
@ZLLentz
ZLLentz deleted the zlentz/fix_pydm_displays_path branch July 23, 2026 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants