• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name Domi

    Log entry time 03:33:26 on January 12, 2004

    Entry number 72786

    keyword=RC Report - January 11th, 2004

    Run Coordinator's report - January 11th,  2004


    General concerns :
  •  G0 shifts (leader, worker) started at noon today.
  • After being expected for 2 days,  40uA G0 beam was delivered to hall C at 9:15pm today allowing Kaz to perform the first part of his parity quality beam study. First results can be found in g0log : entries #72780, #72781 and #72783. During these studies, no beam was sent to hall A at the same time.
  •  1h30 later HallA received 100uA beam while no beam was sent to HallC.
  •  Due to RF "limitations" in the injector (120uA total), HallA(100uA)/HallC(40uA) compatibility test can't be achieved right away.  It only needs a specific "tuning" from RF people which is scheduled tomorrow morning starting at 8am.
  • At midnight, HallA energy spread minimization started with 8uA beam. This should last 2hours.
  • After HallA energy spread measurement, we will get the G0 beam back so that Kaz will be able to continue his program : RHWP/IA/PZT scans and then perform long feed back runs (runs of 1hours each) until MCC  will take the beam back for HallA/HallC compatibility test around 8am.
  • Depending Accelerator plan we will decide the more appropriate time to start cooling down our target which requires a short controlled access and then 2 to 3 hours of cooling. We will have a better idea after the 7:45 meeting.


    • DAQ status :
    Following up g0log entry  #72713 , Paul and I  have been investigating the problem from 11:30am until 7pm. Steve, Jean-Claude Cuzon have been called. Suspecting ROC3, network problems (EPICS for the Musson's box), extra TS0 scalers, ... we made several DAQ tests (see g0log entries #72763 and #72768) along which we modified TS0 buffer size and set DMCH1 as the master board instead of DMCH7 which seemed to cause a problem while running in stand alone mode. At the end, we were rather frustrated because it worked well within ts_full run type without understanding what caused the problem. Such an intermittent problem could reappear anytime... I will investigate why DMCH7 as the master board in stand alone mode was a problem. Furthermore, near the end of our tests, we have seen that even when TS0 was complaining it wasn't crashing anymore.
    All the DMCH boards have been re-cabled so that the French electronics is ready to go.
    ts_scaler, ts_fb_epics run types are running well.

    Future plans :

  • If allowed by the PD, taking parasitic ts_scaler runs during hallA/hallC compatibility test to be able to look at beam quality.
  • Take advantage of the first opportunity to cool our target : requires a short control access, target experts and Jlab cryo people.
  • While no beam available is scheduled (control access, specific accelerator studies, ...) : DAQ test with the full time encoding set up (NA + 9 DMCH boards) using a generator signal sent to some of the splitted channels (NA octants, det. 14 and 15) to check TOF obtained with the 2 types of electronics. Paul and Domi.
  • When no beam in the hall is sceduled for a long period of time (at least 2 hours), perform FR DNL measurements (HV.fullgain_2nd_engineering_calibrated, FR thresholds 20mV, Reference_FoB, Prescale set to maximum (no fast-bus events, 30Hz data) .
  • Once a day take 120Hz data  for 10 minutes (feedback on and off).
  • Check beam quality. Pay attention to halo rates to avoid beam tails when running at a beam current below 40uA.
  • Take asymmetry data on empty target (gazeous H2) : check the maximum beam current we can ask.
  • Moller measurement.
  • Halo calibration.
  • As soon as we will take data on LH2 (40uA, good parity quality beam), take asymmetry data (40 minutes) with external YO and filtered YO for French electronics to investigate time bin correlations.

    • Dominique Marchand
    pager : 584 - 5474