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

    User name R. Michaels

    Log entry time 10:33:28 on October 21, 2009

    Entry number 295957

    This entry is a followup to: 295900

    keyword=target epics variables into datastream / Podd

    I added the desired 2 target variables to fastEpicsLogger. They show
    up in Podd now. It should be realized that at the start of a run there
    is no EPICS data so the data may be "undefined" = -1e+32 by convention.
    There are 2 event-type 131: fast and slow. If fast doesn't have it
    but slow has it, you may get a lot of undefined. Also, the fast
    script had become slow because of a lot of obsolete garbage. Every
    undefined EPICS variable costs 1 second delay (timeout). I cleaned
    up some of that, but will certainly need to clean more before PVDIS.
    It happened because of a long history (He3 target, etc).

    One may use "grep -ai variable filename" to find EPICS variable
    "variable" in the raw CODA file "filename".

    Here are examples of the variables from Podd for "E" and "T" trees:

    analyzer [4] E->Scan("haH2_P_Fill_Target_R")
    ************************
    * Row * haH2_P_Fi *
    ************************
    * 0 * -1e+32 *
    * 1 * 42.081298 *
    * 2 * 42.081298 *
    * 3 * 41.989799 *
    * 4 * 41.989799 *

    T->Scan("haH2_P_Fill_Target_R")
    (First 349 events have no EPICS data, wasn't inserted yet.)
    * 347 * -1e+32 *
    * 348 * -1e+32 *
    * 349 * -1e+32 *
    * 350 * 42.081298 *
    * 351 * 42.081298 *
    * 352 * 42.081298 *
    * 353 * 42.081298 *

    analyzer [7] E->Scan("haL3_hp_pid.CVAL")
    ************************
    * Row * haL3_hp_p *
    ************************
    * 0 * -1e+32 *
    * 1 * 19 *
    * 2 * 19 *
    * 3 * 19 *
    * 4 * 19 *

    T->Scan("haL3_hp_pid.CVAL")
    (Ditto comment above)
    * 348 * -1e+32 *
    * 349 * -1e+32 *
    * 350 * 19 *
    * 351 * 19 *