Log entry time 15:12:25 on September 27, 2010

Entry number 332939

Followups:

• 332993 09/28/10 09:45 R. Michaels solution to EPICS truncation

This entry is mostly for my own reference.

I checked that the calo anode currents are saved in the coda file: yes they are but I cannot get 
them decoded correctly by the hall analyzer. I'll try to get that fixed at some point.

Below are some details, showing that the date appear to be saved in the coda file but are not 
showing up in the epics tree from the analyzer. 




The data below are from run 6757. The variables I am looking at (calo anode currents) are of 
type haVMI3128_X_AIX where X is a number. The data are saved by the slow epic logger.


For example, looking at the data with  evio2xml, by typing that command:
evio2xml -ev 131 /adaql2/data1/dvcs10_6757.dat.0
I get:




   
<![CDATA[
Mon Sep 27 10:58:28 EDT 2010
IPM1H04A                      0
[skipping many lines]
COMPTON_SERVO_FASTai          -7.50595
COMPTON_CAVPOLAR_ca           93.0866
COMPTON_PW1R_S2_ca            11.6785
COMPTON_PW1R_S1_ca            327.875
COMPTON_PVAL_Y_ao             10625
COMPTON_CAVSLOW_bo            ON
 COMPTON_LASERT_RAMPDT --- Invalid channel name
COMPTON_CAVPLUSOFT_ca.B       0.015
COMPTON_CAVMOINSOFT_ca.B      0.015
haVMI3128_1_AI1               -0.00488281
haVMI3128_1_AI2               -0.00610352
haVMI3128_1_AI3               -0.012207
haVMI3128_1_AI4               -0.00610352
haVMI3128_1_AI5               -0.00732422
haVMI3128_1_AI6               -0.00976562
haVMI3128_1_AI7               -0.00732422
haVMI3128_1_AI8               -0.00610352
haVMI3128_1_AI9               -0.00366211
haVMI3128_1_AI10              -0.00366211

This shows I think that the data are indeed in the coda file. 
Next I try to look at these data with the Hall A analyzer. I configured my odef file to save these 
data in the epics tree by adding these lines in the file

begin epics
        haVMI3128_1_AI1
        haVMI3128_2_AI1
        haVMI3128_3_AI1
        haVMI3128_1_AI5
        haVMI3128_2_AI5
        haVMI3128_3_AI5
        hac_bcm_average
end epics

I get only -1e+32 values saved in the tree, for example:

Attaching file rootfiles/onlana_dvcs_notreeLHRSonly_6757.root as _file0...
analyzer [1] E->Scan()                                                                    
************************************************************************************************
************
*    Row   * haVMI3128 * haVMI3128 * haVMI3128 * haVMI3128 * haVMI3128 * haVMI3128 * 
hac_bcm_a * timestamp *
************************************************************************************************
************
*        0 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0216144 *   
2371066 *
*        1 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0216092 *   
2371076 *
*        2 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0216697 *   
2371086 *
*        3 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0217016 *   
2371096 *
*        4 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0216589 *   
2371105 *
*        5 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0217068 *   
2371115 *
*        6 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0217444 *   
2371126 *
*        7 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 *    -1e+32 * 0.0217323 *   
2371136 *