Bug #8298
Inconsistent behavior when setting anode program past "Max HV"
0%
Description
I3 attempts to block settings to the anode program that exceed a calculated "Max HV" in MeV/Turn. This "Max HV" is calculated in [hv.cpp > rinit()] as:
rfmax = hvp.par.tubmax * hvp.par.tubgain * cs->pars[PAR_RFNUM] / 1000.
Where pars[PAR_RFNUM] is the number of RF stations active
and hvp.par.tubmax is the maximum tub voltage (kv) found in appdb.wu.i3_parameters
and hvp.par.tubgain is average RF cavity tube gain found in appdb.wu.i3_parameters
However, the operators have reported seeing the warning that occurs when reaching the "Max HV" threshold and stil occassionally being able to set the values higher.
I suspect what is happening may be related to the number of stations declared in I3. When this was first reported to me there were a couple MI stations left off and then turned on that day. Unfortunately, I have virtually no way of telling if any of the other parameters were edited because of issue: 8297.
Related issues
History
#1 Updated by Kyle Hazelwood almost 5 years ago
- Related to Feature #8297: RF parameters table added
#2 Updated by Kyle Hazelwood almost 5 years ago
- Subject changed from Inconsistent behavious when setting anode program past "Max HV" to Inconsistent behavior when setting anode program past "Max HV"
- Description updated (diff)
#3 Updated by Kyle Hazelwood almost 5 years ago
For reference: https://www-bd.fnal.gov/Elog/?entryIDs=48716