- add-new-service.md: document agebd service add's actual behavior
(required flags, that it auto-creates and pushes a
feature/add-service-<name> branch, and the CI pipeline that push
triggers), explain how service-specific vs external PV naming
actually works, and correct the claim that external PVs are
read-only in dev (unenforced: get_pv_external_class() is unused
and there's no EPICS ACF in this repo).
- iocs_overview.md: fix TUNEFBX's copy-pasted "top up tool"
description, merge the AGEBD-CPCL-DBPM3/DBPM3CURR duplicate,
deduplicate the two conflicting PARAMS rows (the "PCT base
lifetime" description actually belongs to TAUPCT), clarify that
AGEBD-CPCL-ALH isn't a separate IOC, and add the services that
were missing entirely (TauPCT, TuneFBy, Params, ShiftTool,
BeamTransferChecks, all 11 OpticsFF-* beamline services).
- gui.md: warn that launching straight from a git checkout uses
unsubstituted {{ agebd_env_suffix_upper/lower }} placeholders,
since substitution only happens at deploy time.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A9GjKvXCmfgJpKzbQdZ7UA
31 lines
916 B
Markdown
31 lines
916 B
Markdown
# GUI
|
|
|
|
## Launch
|
|
|
|
```
|
|
cd <repo-root>
|
|
```
|
|
|
|
In `prod`:
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_InjectionGuard.ui
|
|
```
|
|
|
|
In `dev`:
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_InjectionGuard.ui dev
|
|
```
|
|
|
|
Any extra arguments are passed straight through to `caqtdm`, e.g. to set a macro:
|
|
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_Tune.ui dev -macro "OTHER_ENV_VAR=HEYHEY"
|
|
```
|
|
|
|
**Note:** launching straight from a git checkout, as above, uses the raw `.ui` files as
|
|
committed - including the literal `{{ agebd_env_suffix_upper }}`/`{{ agebd_env_suffix_lower }}`
|
|
placeholders in their PV names. Those only get substituted with `-DEV`/`-dev` (or emptied out,
|
|
in `prod`) at deploy time, by `.gitea/workflows/deploy.yml`'s "Qt - deploy" step, on the
|
|
*deployed* copy at `/sls/bd/hla/<env>/qt/`. If widgets show up blank or unresponsive, check
|
|
whether you're accidentally pointing at the raw checkout instead of the deployed `.ui` file.
|