Closed qzhang234 closed 2 years ago
Suresh mentioned that since the IOC has been rebuilt, there are discrepancies in some of the PV names. I did notice that although acquisition time and period seem to update upon running the Bluesky plan, the Acquire button is not pressed and the PV name 8LAMBDA1:cam1:Acquire
is not defined anywhere in the current Bluesky version. Maybe lambda_750k.py
in /instrument/device
needs to be rebuilt?
Pete and I discussed the issue and we went over your suggestion of changing IMMout
to imm1
. The problem is, Lambda calls ad_imm_plugin.py
, and if we want to implement the change, we need to change that file which will change the behavior for ALL detectors that use .imm
.
@sureshnaps Is this the direction we want to go?
@prjemian I talked to Suresh earlier today and we at 8-ID decided to switch from IMMout
to imm1
for all occurrences since Rigaku imm plugin is also using imm1
. Could you provide some pointers on how we should proceed?
There are at least two different types of edit to make. In one case, the IMMout plugin is named and the IMM1 plugin can replace. The other case is when various IMMxxx plugins are in a list. In that case, remove the IMMout from the list. Do this in a branch so we can look at it together.
This issue is not relevant anymore. Closing it now.
@prjemian The shutdown has officially started and Suresh has switched to Keenan's Lambda IOC without the previous .imm issue. When I ran
AD_Acquire
I get the following error:Error from terminal output
``` In [17]: In [17]: AD_Acquire(lambdadet, 'A001_Test', 0.1, 0.11, 100, '/home/8ididata/2021-2/rigaku202107') Out[17]: