Hi Anchi,
Thanks for the changes. Yesterday, I was checking and confused about whether should I use it directly in 2.2 or 2.1. Now you made me clear with making it compatible in both versions. Because I have both versions installed in parallel with two computers. The installation of 2.2 in RHEL6 machine was kept aside, since as you said to wait untill begining of this month.
Now as per your information, I feel 2.2-redux version is compatible to RHEL6 and hope it works smoothly. So, then I will try in 2.1 as per your instructions and try 2.2-redux later when I finish installation in the new RHEL6 machine. Also, give me your final opinion about 2.2-redux.
regards,
venkata
Anchi Cheng wrote:
Venkata,
I've committed the changes to 2.2 and 2.2-redux (the CentOS6 and php 5.3 compatible version) branches. I am also attaching the replacement files you could use if you decide to stay at 2.1 for a while.
Once you have updated your installation with these, you can modify the application you use to add the conditioner which currently only does buffer cycling.
Follow the instruction in Use the Application Editor to create or edit Leginon applications to add a node from Conditioner class to the application you currently use. Create a FixConditionEvent binding from the acquisition node where you want Leginon to run buffer cycle before processing a target list (targets from the same parent image). I recommend that you do this from "Exposure" node (i.e., the last of the MSI sequence) if this is MSI-T application.
When you run the new application, you should see your new node. The settings should be easy to understand. The default is Bypass, so you must deactive the bypass to use it.
Let me know if you have problem.
Again, the files attached are for 2.1 version only.