task:beamloss_tool
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
task:beamloss_tool [2024/10/01 15:39] – created pirkola | task:beamloss_tool [2025/06/12 15:49] (current) – ryans | ||
---|---|---|---|
Line 2: | Line 2: | ||
- | Tanner' | + | == Tanner' |
The tool configures BCM D5789 instead of D5521. Unfortunately, | The tool configures BCM D5789 instead of D5521. Unfortunately, | ||
- | |||
- | |||
The tool automatically sets BCM thresholds. The calculation need the information on AP config tab to be accurate. The MEBT threshold sets it to a value that includes some noise overhead, so instead of 25 W exactly is corresponds with ~32 W for example. | The tool automatically sets BCM thresholds. The calculation need the information on AP config tab to be accurate. The MEBT threshold sets it to a value that includes some noise overhead, so instead of 25 W exactly is corresponds with ~32 W for example. | ||
- | |||
- | |||
When running to the niobium plate, I left the destination as FS1a and just changed the “beam energy after charge stripper” to 1.5 MeV/u. This updated the BCM 1120 threshold to avoid tripping. | When running to the niobium plate, I left the destination as FS1a and just changed the “beam energy after charge stripper” to 1.5 MeV/u. This updated the BCM 1120 threshold to avoid tripping. | ||
+ | |||
+ | |||
+ | It seems that any time a TCT Parameter is changed (see ‘TCT Recent Parameter Changes’ box) threshold selections are re-established. This can be an issue if you manually stop watching a dBCM while running a lower powered beam. -ALP | ||
+ | |||
+ | |||
+ | ====Shane note==== | ||
+ | * Good info but not noob friendly | ||
+ | |||
+ | ===== Links ===== | ||
+ | *{{task: |
task/beamloss_tool.1727811565.txt.gz · Last modified: 2024/10/01 15:39 by pirkola