Closed jilavsky closed 5 years ago
Thinking we did this in early April. We'll check and verify tomorrow.
Still a problem. Here's how we tested it.
screen usaxs_user_main.ui, tab Fly scans/SAXS/WAXS
check Use Specific location?
set new values for SX, SY positions (set them to different values then current for diagnostic purposes)
9idcLAX:USAXS:UseSpecificTuneLocation
9idcLAX:USAXS:preUSAXStuneSX
9idcLAX:USAXS:preUSAXStuneSY
RE(preUSAXStune())
-- did SX and SY move to expected positions? (not today)
Add to the preUSAXStune()
code that if 9idcLAX:USAXS:UseSpecificTuneLocation
is set, then move sample to the X & Y positions indicated.
FYI, the signals are all available now:
In [1]: terms.preUSAXStune.use_specific_location.value
Out[1]: 0
In [2]: terms.preUSAXStune.sx.value
Out[2]: 2.0
In [3]: terms.preUSAXStune.sy.value
Out[3]: -3.0
Added to spec already - and will be added in March to epics: control where preUSAXStune is run. This is bit touchy, so three PVs are added: Variable/PV which controls where preUSAXStune is done. If set to 0, preUSAXStune is done wherever the instrument is. If set to 1, preUSAXStune moves before tuning to position defined by the two other PVs. The control variable/PV is set by default always to 0 by "startup script" and needs to be set in spec command file (BS "plan"?) to 1 by user intentionally. It cannot be set automatcially or left in place - it could cause disasters. PV names will be provided when added to LAX.