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

    User name R. Michaels

    Log entry time 10:36:40 on June 02, 2009

    Entry number 278441

    This entry is a followup to: 278438

    keyword=re: sfi2.crl issues (resolved, I think)

    Ok, everything makes sense now and we don't need to revert
    to the old CRL to explore anymore. Alex fixed the sfi2.crl
    around the time of run 21958 start-time (his object file was
    created at 23:12 last night). This fixed the problem.

    And why did roc2 slot 16 have data ? Because, as explained
    in my previous halog, it was being read out but not programmed,
    and so after power-cycling it has random bits and what you get is
    anyone's guess. Probably some bogus data and slightly
    more deadtime, depending on those bits. Power cycle again
    and maybe there are no data. It was a bug to read out a
    module which was not explicitly programmed.