• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT
    Make New Entry, Make Followup Entry

    User name pzhu

    Log entry time 15:40:06 on March 31, 2012

    Entry number 368661

    Followups:

    keyword=spot++ and spoth++ script update

    I updated the spot++ ,spot_L, spot_R ,spoth++, spoth_L, spoth_R script.
    
    spot_L is used for getting bpm information from left arm fastbus ADC
    usage: spot_L runnumber maxevent firstevent forcereplay
    if just type spot_L will take the spot for the newest run
    it will use existed rootfile is there already have that rootfile, if set
    forcereplay to 1 it will force replay again
    maxevent is the maximum event number used for replay
    firstevent is the first event number used for re[lay
    
    spot_R is used for getting bpm information from left arm fastbus ADC
    same usage as spot_L
    
    spot++ is the softlink for spot_L
    
    spoth_L is used for getting bpm information from left arm happex ADC
    usage: spoth_L runnumber maxevent forcereplay
    runnumber, maxevent and forcereplay is same as spot_L
    if runnumber=1 spoth_L will get the happex bpm information by using
    tcp-ip, that's the newest bpm information and do not need CODA run
    
    spoth_R is used for getting bpm information from right arm happex ADC
    same usage as spoth_L
    
    spoth++ is used for getting bpm information from two arm's happex ADC
    you can use this to get the bpm information from both arm's happex ADC
    information, that is, run number can be left arm's and right arm's
    if runnumber=0 or leave it empty, it will get newest run's information,
    no matter left or right arm.
    if runnumber=1, it will use right arm happex tcp-ip information, same as
    spoth_R
    


    A copy of this log entry has been emailed to: camsonne,vasulk,rbziel,melissac,cg2ja,pzhu,kalyan,tbadman,min,jixie,jie