STAR Logo

STAR Newsletter #84

September 2001
Star Home Page
Editor: Howard Matis

Contents

  1. Spokesman's Column
  2. STAR Operations
  3. Detectors and Subsystems
  4. Period Coordinators Report
  5. Physics Working Groups (protected area)
  6. People: Comings and Goings
  7. Announcements
  8. Employment Opportunities

Spokesman's Column (John Harris)

Due to the tragic events of the 11th of September 2001, I first wish to express our sincere condolences and sympathy to everyone touched by this tragedy, either directly or indirectly.

I express our thanks to those from the international community, who have sent very supportive e-mail to STAR and to me, expressing their outrage, support and solidarity. Let's hope this world can figure out a way to live together with order and stability, and with peace and prosperity for all.

.............................................................................

The status of data-taking in the experiment can be found in the period coordinator reports included in this newsletter. We are still having problems filling the shift leader and detector operator shifts. All those presently qualified are urged to sign up for additional shifts. Those interested in becoming shift leaders or detector operators, please sign up as trainees, and after you have trained on shift apply for certification.

Three weeks ago, I asked the STAR Analysis Coordinator, Thomas Ullrich, to put together a task force to spend two weeks on a "critical analysis on the latest centrality and mixed trigger data, to determine that the data that is taken is appropriate for analysis, and that we are ready for data-taking in a production mode." Thomas led the task force which consisted of Thomas Ullrich, James Dunlop, Gene Van Buren, Frank Laue, Zhangbu Xu, Kai O. Schweda, Dave Hardtke, Mike Miller, and Fabrice Retiere. I wish to thank this task force for their fast and effective work. Their report can be found at http://www.star.bnl.gov/protected/common/taskforce A summary of their conclusions is:

They state that they "could not determine the 'mixed' trigger issue as quoted in the charge since we are simply not there yet. There are still some issues with the trigger and there's a certain 'nervousness' to use mixed triggers without having a second trigger word (trigger word prime) in place. First we have to wait until all defined trigger sets are finally implemented." The trigger is still being worked on and trigger word prime implemented as this newsletter goes to press.

In STAR we continue to complete the analysis and papers on our 130 A-GeV Au + Au data, with anticipation of commencing analysis of the data that we are presently taking at 200 A-GeV. However, it is still timely and important to make sure that the data that we are presently taking is of high quality at the level of the physics that we expect to be able to get from it. Thus, I would urge people to take a look at the data and convince yourselves that this is of the quality that you desire to analyse for physics in the longer term, once larger statistics are on tape. Also, please review the task force report above and ensure that you are comfortable with the status of the data-taking and data taken. In particular, it is my conclusion that the SVT data and software are still not in sufficient shape to ensure that the SVT data are of sufficient quality for production with the SVT. Your comments and help on this are invited.

There was a DOE Review of the entire RHIC Program last week at BNL. The review covered both the collider and experiments. The presentation I gave for STAR can be found at: http://star.physics.yale.edu/users/john.harris/talks/STAR_DOE_Review_2001.ppt The review went rather well for the experiments in general. It is my opinion that beyond the issues associated with getting enough good, stable beam to complete the physics program that we have planned for the coming years, the primary issue is how BNL will deal with new detectors and major upgrades (and associated R & D) in the future.

STAR Operations (Bill Christie)

No contribution this month.

Detectors and Subsystems

  • FTPC (from Volker Eckardt)
  • No contribution this month.

  • Slow Controls (from Mike Cherney)
  • Slow Controls continues to automate startup and recovery processes. The EMC electronics controls are under test. A new student, Steve Gronstal, has joined the group and will be based at Brookhaven for the remainder of the run.

  • EMC (from Thomas Cormier)
  • Over the last two weeks using both scheduled an unscheduled access to the STAR Hall, The EMC group has successfully installed readout electronics for a patch of 12 EMC modules (10% of the detector). This patch contains 480 towers and 3600 channels of shower maximum detector. Work on debugging the patch readout continues and has obviously been complicated by lack of ready access to the electronics. However, at this time, the EMC towers have been readout through DAQ for both pedestals and LED pulsers. Overall system noise is found to be at the level of or better than that seen on the bench. The towers are ready for first inclusion in STAR running and we expect that this will occur over the next day or so. Once the EMC towers are included in the STAR data path we can begin to study the EMC level-0 trigger capability.

    The shower maximum detectors have one or two more technical issues to resolve related to calibration, timing and busy's. It is expected, however, that inclusion of the SMD in the data stream will follow shortly on successful operation of the towers through DAQ.

  • TPC (from Blair Stringfellow)
  • No contribution this month.

  • Level 3 Trigger (from the commissioning contingent)
  • No contribution this month.

  • Endcap EMC (from Will Jacobs)
  • First (prototype) machined lead sheets arrive at IUCF from Vulcan Lead. Gluing jig table with vacuum bagging, sheet flippers, stainless steel cover sheets and component production parts (Dubna) all available to begin fabrication of a full size (1/2 Endcap) test radiator laminate.

    SMD design details from recent review finalized; 3 scintillator strip detector blank "gluings" from ANL ready for cutout and machining at IUCF. LED driven "fiber clasps" delivered (KSU) for first SMD final fibering and assembly.

    Leaky fiber characteristics optimized for more uniform light deposition; tower megatile retrofit underway to incorporate new leaky fibers and production style fiber connectors.

    Endcap assembly strongback and lifting fixture designed; detector backplate and hub bid.

    Work underway for plan to install a prototype PMT box (TAMU) with pre-production PMT housings (Dubna) on the back of the STAR west poletip during the break before polarized pp running begins.

    Preparing for a major construction review of the STAR Endcap EMC at BNL 3-4 October, 2001.

  • SVT
  • No contribution this month..

  • RICH
  • No contribution this month.

  • TOFp - (Frank Geurts)
  • Over the last two months the TOFp and pVPD detector have been commissioned. The pVPD detector, used as the start for the Time-Of-Flight system, successfully operated in zero and half field conditions. However, after the first full field runs it turned out that the shielding of the PMT assemblies was not sufficient. On August 7 both pVPDs were moved some 36" outboard after which they operated successfully again in any field setting. The coincidence rates of the pVPDs vary with those of the ZDCs.

    The TOF system has its own trigger logic based on coincidences of the pVPD and timing of L0s delivered to the subsystem. Somewhere in the 2nd week of August, the TOF local trigger busied out STAR DAQ and the TOFp was removed from the data stream. It turned out that the L0 trigger distribution had been changed and delayed by some 300ns. The window in which the L0 was expected therefore closed prematurely and the system turned busy. Once it was clear that the L0 moved 300ns we moved and increased our windows such that these busies are virtually eliminated. Ever since these changes the TOFp system is part of the standard data stream without any problems towards STAR DAQ.

    After the first weeks of data we identified a substantial DC offset in all the 41 TOFp channels in the tray. To deal with this we DC-decoupled all the analog signals from the ADCs. Unfortunately the DC offset creates high effective thresholds for the TDC signals. We are currently investigating this offset which did not appear in full system tests before installation into STAR.

    Since some channels turn out to be less affected by this offset which varies channel to channel, we decided to keep the TOF system in the STAR data stream and analyze its data.

    Period Coordinator Reports

    The main focus of STAR during these two weeks was the commissioning of the STAR trigger. The trigger developments included:

    Killer bits The fast detectors in the trigger are the ZDCs and the CTB. Both suffer from the problem that the signals ring. Thus a valid event can fire the discriminators for several crossings after an event takes place. This ringing confuses the scale downs and causes gaps in the TPC timing in multiples of the RHIC clock. To prevent this problem, after a trigger takes place, the following 10 RHIC clock ticks are killed by the trigger. This method was tested and checked exhaustively and shown to work properly. The resulting dead time can be calculated and a correction can be applied for absolute cross section measurements. At the design luminosity for the heavy ion program, this correction will be on the order of 1 part in 1000. (1 microsecond compared to 1 millisecond)

    Prescales We implemented and checked the trigger prescales. We did the check by running a minimum bias trigger along with a central trigger with a prescale factor of 4:1. The central trigger was based on the CTB total signal which was not calibrated so the resulting data cannot be analyzed. The prescale factors were analyzed offline and worked as expected.

    Minimum bias trigger The minimum bias trigger is based on the zero degree calorimeters (ZDC), east and west. The gains on the signals from the ZDCs are set so that the single neutron peak is well above the pedestal. The threshold for triggering on each ZDC is set above the pedestal and as far below the single neutron peak as practical. Several runs were taken to verify the pedestal, offset, gain, and threshold of the ZDC. The threshold is set 2.5 sigma below the peak value.

    Z vertex trigger at level 0 The minimum bias trigger is composed of a coincidence between the ADC values of the east and west ZDCs. In addition, a timing signal is produced between each ZDC and the RHIC clock. These analog signals are digitized and the difference between the two values is proportional to the Z vertex position. This difference is used to trigger on events with Z vertices within ± 25 of the center of STAR. The standard minimum bias trigger will be a coincidence between the two ZDCs and a timing signal with ±25 cm. To allow the extraction of absolute cross sections by providing a measurement of the interaction diamond, a scaled down trigger comprised of a ZDC coincidence with the timing signal outside the ± 25 cm range will also be collected.

    We have a plan to verify the operation of this trigger that will be carried out when the beam returns. In addition, the bunch crossing timing signals of the blue and yellow rings will be added to the minimum bias trigger.

    Interleaved triggers for the TPC and SVT We have set up interleaving of laser events with data events for the TPC. This method required that the killer bits work properly. We also implemented and check an interleaved charge injection pulser for the SVT interspersed with data events. Thus the calibration of the TPC and SVT can be monitored throughout the run.

    Central trigger Considerable effort was invested in the calibration of the CTB slats. The CTB slat calibration was done by using minimum bias events analyzed off line. Events with low to medium multiplicity were selected and slats were analyzed with one and only one minimum ionizing particle (mip) hitting the center of the slat. The CTB voltages were adjusted to put the mip peak at an ADC value of 5. Last year's voltages could not be used because we are now running full field and the pulse height of the CTB pmt's is strongly affected by the higher field. Currently, we think we are one iteration from having the CTB calibrated and being able to trigger on central collisions.

    Once the calibration is complete, we need to choose the threshold for central collisions. We cannot choose the threshold so high that we select events that are so central that the ZDC cannot fire. John Harris had requested a 5% central trigger cut but we must be sure that we are not biasing our data by setting the central threshold too high. The current opinion is that we will run again with a 15% central trigger.

    Production running with the central trigger must include the ZDC Z vertex trigger at level 0. Presumably the central trigger must also include scaled triggers not in the Z vertex range.

    Peripheral collisions trigger The main effort here has been to set up the multiwire counter (MWC) of the TPC to be part of the trigger at level 0. The problem was that the signals from the MWC do not all fall in the same RHIC clock tick. Because the level 0 trigger can only trigger on information in one crossing, an effort was made to adjust the thresholds of the MWC to improve its efficiency without increasing its noise. Delay was added to the level 0 trigger to allow the digitization of the MWC to be complete before the trigger decision was made. This action added three RHIC clock ticks to the STAR level 0 trigger timing, effectively reducing the size of the TPC at large |Z| values by a few cm.

    The plan for the peripheral collisions trigger is to install completely new trigger software incorporating all of the previous work on min bias and central triggers. The CTB total signal will be scaled down to free up bits that need to be used in the peripheral trigger.

    Final trigger plan The final trigger will include minimum bias, central, and peripheral triggers with and without Z vertex. These triggers will include interspersed laser triggers for the TPC and charge injection for the SVT. The job of the Collaboration will be to verify that these triggers are robust and that the resulting data are analyzable.

    - Gary Westfall (29 July through August 13)

    RHIC STATUS

    The first week (August 26- September 1) RHIC provided useful beam on the level of 30%. The RHIC goal to lengthen stores led to a 12 hour store (one time).

    RHIC studies of longitudinal profile using 200MHz RF were continued, as well as tests of switching between running of heavy ions and slow extracted protons. The latest results show that this switch can be completed in 30 min. During the week of September 2 - September 9 there was practically no data taking. We have had beam stored and cogged a few times, but it died usually with a quentch fault in 15-20 minutes. The RHIC goal for the coming week(s) is to improve machine stability and work on understanding of process of de-bunching (loss is significantly different in short time intervals (1-2 hour) in both rings; rapid de-bunching occurs mainly in blue).

    There were three scheduled down times: two access periods (to work on EMC and TOF) and one due to a DOE visit to STAR. There were two incidents (5 days apart, first at 1:30 am on August 29) where the STAR detector was blasted off with radiation. The big background current went up in all detectors 10-20 times normal levels. The RHIC ZDC signal dropped from 130 to 20 in 5 min. The first time beam recovered (by itself ?), the second time an immediate dump followed. Almost all our detectors tripped instantly. In both cases, beam loss monitors did not register losses. Other experiments were not affected. There is a plan to install a chipmunk detector in the STAR area to help with diagnostics. This needs to be followed up.

    Phobos reported another (similar) blast last week. This one triggered alarms in the MCR. Fortunately Phobos detectors did not have HV on due to some other work in progress.

    At the 9 am meeting (September 10) Tom Kirk said that the RHIC DOE review (last week) concluded the following:

    STAR STATUS

    These two weeks were devoted to defining the production trigger for this year's run. The STAR Trigger Board made the following decisions (See Star Trigger Board Summary Minutes of 9/6/01 for details):

    The Minimum Bias Set trigger was implemented, and all 3 components were tested separately (but without the SVT). The Production MinBias trigger was not, however, tested in its final version (all components of mixed trigger together). It is ready and waiting for beam. There was a problem with > 33K CTB part of the ProductionMinBias trigger. This was solved by swapping the Layer2 CTB-MWC DSM Board. The new DSM board seems to work fine. During the time of setting up and fixing of the production trigger (ProductionMinBias), the MinBiasVtx trigger was run .

    The CENTRAL Trigger is not set up yet. The first test of the UPC Topology Trigger was successful. A second test, with modified parameters, yielded zero triggers.

    SUBSYSTEM STATUS

    RUN SUMMARY

    As of today we took slightly over 2.5 M MinBiasVtx events. The RunLog Browser provides information run-by-run.

    Organizational items:

    Things to be followed:

    Due to RunLog problems (it stalled practically every day. Later, the problem was found and fixed) there is a significant lack of comments for runs taken last week. Those comments can be entered either at the site or via the RunLog web interface. Shift leaders have been asked to enter comments related to their shifts. Particularly important is to state which runs should not be considered for the analysis.

    From QA off-line report:

    - Grazyna Odyniec (August 28 - September 11)

    Physics Working Groups - (See the protected area)

    This section contains summaries of the status of the physics working groups. These articles are in a protected area for STAR collaboration members only. This link uses the standard STAR account and password for physics results. If you do not have this information, please contact your council representative.

    People

    Announcements

    None this month

    Employment Opportunities


    Return to the Newsletter Index - Last Modified: Thursday, September 13, 2001