Changeset 16565 for trunk/FACT++


Ignore:
Timestamp:
06/02/13 02:12:46 (11 years ago)
Author:
tbretz
Message:
Ratecontrol might still believe that the trigger is on, so we force that we recive at least one new dim message which claims that the trigger is on... due to all the delays, unfortunately, this is not a guarantee...
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/FACT++/src/ratecontrol.cc

    r16450 r16565  
    317317            Info(out);
    318318
     319            fTriggerOn = false;
     320            fPhysTriggerEnabled = false;
    319321            return RateControl::State::kGlobalThresholdSet;
    320322        }
     
    336338            Info(out);
    337339
     340            fTriggerOn = false;
     341            fPhysTriggerEnabled = false;
    338342            return RateControl::State::kGlobalThresholdSet;
    339343        }
     
    529533        Info(out);
    530534
     535        fTriggerOn = false;
     536        fPhysTriggerEnabled = false;
    531537        return RateControl::State::kGlobalThresholdSet;
    532538    }
     
    537543        {
    538544            Info("Physics trigger not enabled... CALIBRATE command ignored.");
     545
     546            fTriggerOn = false;
     547            fPhysTriggerEnabled = false;
    539548            return RateControl::State::kGlobalThresholdSet;
    540549        }
     
    565574        {
    566575            Info("Physics trigger not enabled... CALIBRATE command ignored.");
     576
     577            fTriggerOn = false;
     578            fPhysTriggerEnabled = false;
    567579            return RateControl::State::kGlobalThresholdSet;
    568580        }
     
    606618        case 0:
    607619            Info("No calibration requested.");
     620            fTriggerOn = false;
     621            fPhysTriggerEnabled = false;
    608622            return RateControl::State::kGlobalThresholdSet;
    609623            break;
Note: See TracChangeset for help on using the changeset viewer.