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

    User name R. Michaels

    Log entry time 09:16:48 on February22,2011

    Entry number 348070

    This entry is a followup to: 348065

    Followups:

    keyword=more modified scaler.map

    I made some further mods to scaler.map

    First of all, just to be clear, the THaScaler inside the
    analyzer MUST HAVE these two lines -- if the defaults are not
    quite right internal to the code, which typically they
    are not because scaler land gets re-arranged frequently.

    clock 0 8 3 7 1 clock
    TS-accept 0 8 3 12 1 Trigger Supervisor accepted triggers

    The "clock" line tells where to find the clock for rate normalizing,
    and the TS-accept line tells where to find slot of the normalization
    scaler, for BCMs and such. Ok, it's perhaps a time bomb for
    the uninitiated.

    ------------------------------

    Next, scaler.map file should have lines like

    trigger-1 0 8 3 0 1 trigger 1 on Left Arm
    trigger-2 0 8 3 1 1 trigger 2 on Left Arm

    Otherwise, some of the "standard" ways to get the trigger info
    won't work. (But you can still get it other ways, so this is
    just a convenience issue.)

    I put these lines after

    T1 0 8 3 0 1 trigger 1 on Left Arm
    T2 0 8 3 1 1 trigger 2 on Left Arm

    This way, xscaler will show "T1", "T2" (as it does now).
    It's ok to define channels twice in scaler.map.
    For the purpose of xscaler, the first definition is used.

    I saved the old scaler.map in ./save2

    ---------------------------------

    At a glance, it looks like L-HRS and R-HRS are appearing in
    the datastream and look sort-of normal, but there might be some
    anomolies with the BCMs, or their calibrations have changed.
    It should be checked some more.