General

This will contain general information about STAR as well as a container for diverses activities (operations, STSG, STAR management document, etc ...) all of public nature.

 

 

Collaboration

[Under work - see this link in the interim]

Acknowledgements

We thank the RHIC Operations Group and RCF at BNL, the NERSC Center at LBNL, and the Open Science Grid consortium for providing resources and support.  This work was supported in part by the Office of Nuclear Physics within the U.S. DOE Office of Science, the U.S. National Science Foundation, the Ministry of Education and Science of the Russian Federation, National Natural Science Foundation of China, Chinese Academy of Science, the Ministry of Science and Technology of China and the Chinese Ministry of Education, the National Research Foundation of Korea, Czech Science Foundation and Ministry of Education, Youth and Sports of the Czech Republic, Hungarian National Research, Development and Innovation Office, New National Excellency Programme of the Hungarian Ministry of Human Capacities, Department of Atomic Energy and Department of Science and Technology of the Government of India, the National Science Centre of Poland, the Ministry  of Science, Education and Sports of the Republic of Croatia, RosAtom of Russia and German Bundesministerium fur Bildung, Wissenschaft, Forschung and Technologie (BMBF) and the Helmholtz Association.

STAR Funding Agencies

STAR is supported by several funding agencies in countries on four continents, in addition to significant support from STAR member institutions. Here is a list of STAR funding agencies, with links to their web pages.

Office of Nuclear Physics,
Office of High Energy Physics,
Office of Science, Department of Energy
United States
National Science Foundation,
United States
Frankfurt Institute for Advanced Studies,
Germany
Institut National de Physique Nucleaire et de Physique des Particules,
France
Fundação de Amparo à Pesquisa do Estado de São Paulo,
Brazil
  Ministry of Science and Technology,
Russia
National Natural Science Foundation,
China
Chinese Acadamey Of Sciences (CAS),
China
Ministry of Science and Technology (MoST),
China
Department of Atomic Energy(DAE),
India
Department of Science and Technology,
India
Grant Agency of Czech Republic,
Czech Republic
Research Council of Fundamental Science & Technology (KRCF),
Korea
Research Foundation,
Korea

STAR Images

Here are some images from the STAR detector.

 

Pixel related images

End view of pixel detector mockup

 

Participants

 

Photos of visit to LBNL metrology lab

 

Zeiss machine 1

 

Zeiss machine 2

probe stands for Zeiss machine 

SketchUp STAR

SketchUp STAR

3D models of the STAR detector, the RHIC accelerator complex, a prototype of an event display for the STAR experiment in SketchUp

 

Tai Sakuma

 

I drew the STAR detector and the RHIC accelerator complex in SketchUp. Also, I built a prototype of an event display for the STAR experiment by using SketchUp Ruby API. This page shows image files generated in this project.

 

The STAR detector

icon
 

A cross sectional view of the STAR detector. This figure was used in Phys. Rev. D 86, 032006 (2012) (DOI: 10.1103/PhysRevD.86.032006 )

 
icon
 

The same 3D model as in the previous figure but in perspective. This figure has been often used in presentations at scientific meetings.

 

RHIC

icon
 

The RHIC accelerator complex

 

STAR detector subsystems

icon

The Beam-Beam Counters (BBC)

 
icon

The Barrel Electromagnetic Calorimeter (BEMC)

 
icon

A BEMC Module

 
icon

The geometry of the calorimeter towers in a BEMC module

 
icon

The Time Projection Chamber (TPC)

 
icon

The solenoidal magnet subsystem

 

Jet η and detector η

icon

Jet η and detector η

 

Jets at three levels

The following three figures illustrate jets defined at the three different levels. These figures have been used several times in scientific meetings, e.g., the slide 4 of a presentation at APS 2010 .

icon

A high-pT back-to-back dijet event at the detector level. The solid trajectories indicate TPC track measurements while the lego blocks indicate energy deposited in the BEMC towers.

 
icon

A high-pT back-to-back dijet event at the hadron level

 
icon
 

A high-pT back-to-back dijet event at the parton level

 

Jet Patch Trigger

icon

The locations of the twelve jet patches of the BJP1 trigger in Run 6. The size of a jet patch is 1.0x1.0 in the η-φ coordinate system. Each jet patch contains 400 BEMC towers. This figure was used in Phys. Rev. D 86, 032006 (2012) (DOI: 10.1103/PhysRevD.86.032006 )

 

Event Display

I developed a prototype of an event display for the STAR experiment using the SketchUp Ruby API. This prototype was used in jet analyses, in particular, in establishing a jet definition and determining background events.

icon
icon

Two snapshots showing a prototype of an event display for the STAR experiment

 

STAR Management Document

This tree contains STAR Management related documents.

Management Team 2014--2017

 

BES Milestones

 

 
 
Dear RHIC Spokespersons:
 
I am writing again to update my request for the beam use requests for the coming RHIC runs.
 
In consultation with the Office of Nuclear Physics we have decided to make a change to the future RHIC run schedule. Specifically, we now plan to run RHIC in both FY16 and FY17, followed by one year (FY18) without a RHIC run during which the low energy RHIC electron cooling (LEReC) system will be installed. The high statistics Beam Energy Scan II is then planned for the years FY19 and FY20. The modified plan will allow for a less aggressive schedule of the LEReC project. It will also relax the conflict between the heavy ion and spin physics programs of RHIC that remained unresolved at last year’s PAC meeting.
 
I request that you submit the annual beam use requests by May 19, 2015. The BURs should be for a 22-week RHIC run in FY16, and either a 15-week or a 22-week RHIC run in FY17.
 
I also ask the STAR Collaboration to present the iTPC proposal to the PAC and to provide an update on experimental efforts aimed at exploring possible phenomenological manifestations of the chiral magnetic effect.
 
Both collaborations should present a tentative schedule for the release of results from the data taken in runs 13 and 14 (p+p, Au+Au 15, Au+Au 200, 3He+Au).
 
Thanks, Berndt

From: Mueller, Berndt 
Sent: Thursday, October 23, 2014 11:53 AM
To: Xu, Zhangbu; Morrison, David
Cc: James Nagle; Dunlop, James C; Karsch, Frithjof
Subject: performance milestones
 
Dear RHIC Collaboration spokespersons & Frithjof:
 
I received a "heads up" from Jim Sowinski that a main scientific performance milestone for nuclear physics in FY15 will be the completion of the analysis of the 15 GeV Au+Au data from Run 14 and the connection of the BES data with lattice QCD calculations. Here is the statement in more detail (Jim's words in blue):
 
“FY15:  Measure bulk properties, particle spectra, correlations and fluctuations in gold + gold collisions at Relativistic Heavy Ion Collider (RHIC) to search for evidence of a critical point in the Quantum Chromodynamics (QCD) matter phase diagram.”
 
We recognize that significant progress has been made in finalizing and collecting the results from Beam Energy Scan I to make the case for BES II.   In evaluating this goal we will primarily be looking at producing results from the 15 GeV run carried out last year.   Other efforts that might contribute towards this measure could be results from the fixed target data taken last year and theoretical efforts such as progress towards better connecting measurements to QGP properties or extending LQCD calculations toward finite chemical potential.
 
It will be important to have tangible results to point to by the end of September 2015. To me this looks eminently doable and desirable in view of the Quark Matter 2015 conference in Kobe.
 
Let me know if you have any questions.
 

Organization

Organization Information

The following information is available about the STAR organization. Click on any of the following topics.

Policies

 

Statement of Support for Continued STAR Running post BES-II

Official letter from BNL Lab. management, Nov 2017


STAR Beamtime Requests

STAR Council information


Archived Collaboration Lists
The STAR Collaboration list of members
MEMO on Collaboration Institutional bylines (10/22/2015)

STAR Shift Plan
The STAR Collaboration shift policy (posted 11 July 2001)

 

2001 original bylaws

Revised Sections II and III 28 November 2001

 

I. Collaboration Membership

  1. Members

    Scientists, graduate students, engineers and other technically-oriented persons intending to make a significant contribution to this collaboration over a period of a least one year are eligible to be members. Members of other RHIC collaborations will not be members of this collaboration without permission from the Council.

     

  2. Institutions

    Institutions (universities or laboratories) are admitted to the Collaboration by the Council upon recommendation of the Spokesperson. Normally an institution will have at least two Ph.D.s who are eligible to be members. Each institution is responsible for its list of members and for designating a contact person who will receive and disseminate collaboration information within that institution.

     

II. Council

  1. Membership

    The Council will consist of one member from each collaborating institution who will represent the membership from that institution. Institutions are admitted to the Collaboration by the Council upon recommendation of the Spokesperson and upon receiving an affirmative vote of at least 75% of the Council. Each institution will select its representative. Institutions may also be admitted to the Collaboration without Council membership. Such an institution should be affiliated with another institution which has Council membership and may be given its own Council membership at a later time by a vote of the Council. The Spokesperson and Deputy Spokespersons will be ex-officio members of the Council. The Council may add extra members.

    Younger members of the collaboration will be represented by up to three at-large Council members with no more than five years experience beyond the Ph.D., at least one of whom should be a graduate student. Candidates for at-large positions can be either self-nominated or nominated by others after a call for nominations by the Spokesperson. The at-large representatives will be elected by those members of the collaboration with no more than five years experience beyond the Ph.D. Elections should take place at least every two years.

     

  2. Function

    The Council will deal with general issues which concern the collaboration. Examples include the organization and governance of the Collaboration, adoption of the bylaws and amendments thereto, the policy on admission of new members and institutions to the Collaboration, and publication policy. In addition, the Council is responsible for election of the Spokesperson and for approval of Deputy Spokesperson appointments.

     

  3. Governance and Meetings

    The chairperson of the Council is elected by majority vote of the Council from among its ranks. The term of office is two years, and is not renewable. At the end of the Chairperson's first year in office, a deputy is elected who will become the chairperson's successor. After the end of the chairperson's term of office, the chairperson will serve yet another year as deputy.

    Normally, Council meetings will be held during collaboration meetings. At the discretion of the Council Chair, additional meetings can be called with at least two weeks notice. Any Council member unable to attend a given meeting can name a substitute representing the same institution or group. All Council meetings will include a closed session, without the Spokesperson and Deputy Spokesperson(s) present. Elections by the Council, of the Spokesperson or Council Chair or Deputy Chair, must be announced publicly to the entire collaboration at least two weeks in advance of the meeting at which the elections will take place.

     

  4. Voting

    The Council will make decisions on all issues except elections and admission of new institutions based on a simple majority of all voting members. Any member may call for a secret ballot. Votes on adding extra members, admitting new institutions, or amending these bylaws must be announced ahead of time. Proxies to the Council chairperson are allowed for non-election votes, as are electronic meetings and ballots.

    Voting for Spokesperson will be carried out by secret ballot, and without proxies, at publicly announced Council meetings. A quorum of 60% of Council members must be represented at the meeting for a valid vote. A candidate for Spokesperson can be elected in the first round of voting only if he or she receives more than 50% of all votes cast, including abstentions. If no candidate obtains this absolute majority, runoff rounds will be conducted for the top vote-getters until one candidate obtains more than 50% of the votes cast, not counting abstentions. The re-election of a sitting Spokesperson requires a 2/3 majority of the voting representatives present at the meeting.

    Candidates for Spokesperson can be nominated by any member of the collaboration. An ad hoc nomination committee consisting of the Council Chair and two Council members appointed by the Chair will solicit nominations at least 30 days before the election, and will prepare and oversee the ballots.

     

III. Spokesperson

  1. Selection

    The Spokesperson is elected by the Council and serves at its discretion. The normal term of office is 3 years, renewable with a 2/3 majority of the voting Council representatives present at the meeting.

    The Council can decide to terminate the Spokesperson's term in office at any time and to request new elections. Such a termination requires a 3/4 vote of the representatives present at a Council meeting with a quorum of at least 2/3 of the members represented.

     

  2. Function of the Spokesperson

    The Spokesperson will be the representative of the Collaboration in scientific, technical, and managerial concerns. The Spokesperson will be concerned not only with the design and construction of the detector and its upgrades, but also with all other preparations required to operate the experiment efficiently and to publish results in a timely and responsible fashion, and with continued leadership of the Collaboration.

     

  3. Deputy Spokespersons

    There will be up to two deputy spokespersons. The spokesperson and the deputies must all belong to different institutions. The deputy spokespersons will be appointed by the Spokesperson subject to the approval of the Council. The deputy spokespersons provide support and assistance to the Spokesperson in the management of the experiment and collaboration. They may be appointed by the Spokesperson to act on his or her behalf and to represent the Collaboration.

     

IV. Adoption

These bylaws were adopted by the Council on 21 June 1991 and amended on 16 Nov. 1991, 21 April 1993, 7 Nov. 1995, and 28 Nov. 2001.

(Adapted from the SDC)

Publication Policies

Quick reference

 

Members

Affliation Representative E-mail Phone #
University of California, Los Angeles Huan Huang huang@physics.ucla.edu 310-825-9297
Valparaiso University Don Koetke, Chairperson donald.koetke@valpo.edu 219-464-5377
Yale University Jack Sandweiss sandweiss@hepmail.physics.yale.edu 203-432-3358
Brookhaven National Laboratory Jamie Dunlop dunlop@bnl.gov 631-344-7781
       

 

Charter

August 14, 1994

Goals. The publication goals of the STAR Collaboration are as follows:

  1. The speedy publication of results that the Collaboration has agreed are sound and ready for publication. Here "publication" means the announcement of results through seminars, conferences, and/or scientific journals.
  2. The avoidance of rumors and premature publication. 
  3. The equitable assignment of credit to individuals for their work.

     

Policies.

The following policies and practices have been adopted to further the above listed goals:

 

  1. Data from all parts of the STAR detector shall be available to all members of the STAR Collaboration for analysis. Furthermore, it is the responsibility of all collaborators to see that the necessary correction algorithms and correction parameters be updated and made available to the entire Collaboration in a timely manner. Any member of the Collaboration is free to analyze any part of the data.
  2. Given the overriding principle of open communication within the collaboration, collaborators should, upon request of a colleague, provide relevant code and input assumptions that would permit results to be checked and confirmed.
     
  3. Members of the Collaboration should exercise caution and good judgment when discussing experimental results with individuals outside the Collaboration before the results have been published (i.e., presented publicly in a seminar or conference or submitted for publication in a scientific journal). These results should clearly be labeled "Preliminary". When individuals outside the Collaboration are consulted for advice on the analysis or interpretation of the data, those individuals should be asked to respect the confidentiality of the data.
  4. Members of the Collaboration should not present unpublished experimental results in seminars or conferences until (a) a memo has been circulated to the Collaboration giving details of the analysis and results, and (b) a rehearsal has been held in front of several members of the Collaboration, including a Council member and, if possible, the Spokesperson. In particular circumstances the Spokesperson may waive both these requirements.

    The Spokesperson will be designated as the Talks Coordinator. He will strive to distribute speaking invitations received by the Collaboration on the basis of the suitability of the speaker to the topic and an equitable distribution of talks to individuals and institutions with appropriate consideration of regional distinctions. As an aid to this end, he will maintain a record of all talks; thus members of the Collaboration who receive personal invitations to give talks should inform the Talks Coordinator. Speakers are encouraged to deposit a copy of their transparencies in a file which will be maintained by one of the secretaries.

  5. A paper should not be submitted to a scientific journal until the above requirements have been met and (c) a not-far-from-final draft of the paper has been discussed at a general meeting, and (d) the final draft has been circulated. After the discussion of the not-far-from-final draft, an ad hoc committee may be appointed by the Spokesperson to facilitate the preparation and submission of the final draft. This committee would consist of the principal authors and one or more individuals not directly working on the analysis. It would be empowered to adjudicate disagreements on details of the paper. In addition, the Spokesperson will maintain the list of publications.
  6. The Spokesperson will maintain the Collaboration's current author list. In general, the authors of papers will be those collaborators who have contributed to the taking or analysis of the data reported in the paper. In recognition of their contributions, collaborators who have worked on the installation of new equipment but have left the Collaboration prior to the taking of data will be included on the initial papers of the Collaboration using that equipment. Normally individuals are dropped from the general author list one year after they leave the Collaboration; however, individuals who have made special contributions to a given topic, either in hardware or analysis, should be retained on the author list of papers for which their contributions are relevant. Technical papers need only list as authors those individuals who contributed to that project, but the "STAR Collaboration" should be acknowledged. Decisions on the inclusion of authors will be done on the basis of these guidelines by the Council member from the author's institution with the concurrence of the Spokesperson.

    The authors of papers will be listed in alphabetical order, preceded or followed by the phrase "STAR Collaboration". Papers which result from student's theses should be so indicated by appropriate footnotes. Papers for conference proceedings are normally submitted in the speaker's name, plus other major contributors if appropriate, plus "STAR Collaboration", and require only the Spokesperson's agreement on the wording of the text.

  7. The Spokesperson will maintain a list of students' thesis topics which will be updated at collaboration meetings. The Council may aid in resolving any conflicts.
  8. Members of the Collaboration should not issue press releases or call press conferences without the approval of the Spokesperson, who will consult with the members of the Council.

 

Physics Opportunities with STAR in 2020+

 

STAR run18-19 BUR

STAR run16-17 BUR

CAD luminosity projection: 

http://www.rhichome.bnl.gov/RHIC/Runs/RhicProjections.pdf

Overleaf document: 
https://www.overleaf.com/8923878fsmcynsyyzjh#/33782541/

weekly meeting eZuce: 
Title: STAR BUR 2017
Description:
Community: STAR
Meeting type: Open Meeting (Round Table)
Meeting Access Information: eZuce SRN
Application http://srn.ezuce.com/joinSRN?meeting=M2MvMB2a2iDMDl929MDM92
Mobile App : Meeting ID: 102 3196
or Link: http://srn.ezuce.com/join?meeting=M2MvMB2a2iDMDl929MDM92
- Phone Bridge ID: 102 3196

The Charge:

<<<<<<<<<<< 

 

A call for the annual Beam Use Request (BUR) has been sent from the BNL ALD to RHIC collaborations on February 22nd, 2017:

Dear RHIC Spokespersons:

I am writing to request that you submit the annual Beam Use Request for the RHIC runs in 2018 and 2019 and related material.

We current[ly] anticipate, assuming favorable budget conditions, runs of 15 cryo-weeks (including 2 weeks for the Coherent electron Cooling test)

in FY2018 and 24 cryo-weeks each in FY2019 and FY2020. Less favorable,

but still likely, budget conditions would only allow for a combined run of 20 cryo-weeks in FY2019/FY2020. The beam use request should consider both possibilities.

The submissions are due by May 15, 2017. Since PHENIX has ended data taking and sPHENIX has not yet started construction, I expect to receive a BUR from STAR only.

I also ask STAR and PHENIX to report on the status of analyses of data from previous RHIC runs, especially the runs in 2014-16.

In addition, I invite the STAR and sPHENIX Collaborations to present letters of intent for proposals of modest forward upgrades to their detectors for data taking after 2021 for consideration by the PAC.

The dates for this year’s RHIC PAC meeting are June 15-16, 2017. A list of current PAC members is attached for your information.

Thanks in advance,

Berndt

 

The Committee and responsibilities

Gang, Voloshin, Prithwish (Isobar for CME), 
Grazyna,  Geurts (BES-II), 
Cebra, Herrmann (FXT), 
Lisa, Xiaofeng (general), 
Zhenyu, Gregory (HI accomplishments), 
Renee, Oleg Eyser (Spin accomplishments), 
Flemming, Rosi (Detector upgrades)
Jerome (software)

Summary Tables

 Summary Tables 

for run 18 

year Energy  time species events priority sequence

 

18

 

200 GeV

 

200 GeV

 

27 GeV

  3.5-wk

 

  3.5-wk

 

  2-wk

Ru+Ru

 

Zr+Zr

 

Au+Au

1.2B MB

 

1.2B MB

 

>500M MB

1

 

1

 

2

2

2

3

3.0 GeV (FXT)

  3 days?

Au+Au

100M MB

3

1

for run 19 

energy  weeks Events FXT days events
19.6 4.5 400M 4.5 2 100M
14.5 5.5 300M 3.9 2 100M
11.5 5? 230M 3.5 2 100M
62.4     7.7 2 100M
39     6.2 2 100M
27     5.2 2 100M

Plan B: 

energy  weeks Events FXT days events
19.6 4.5 400M 4.5 2 100M
14.5 5.5 300M 3.9 2 100M
27 isobar 5? ? 3.5 2 100M
62.4     7.7 2 100M
39     6.2 2 100M
27     5.2 2 100M

for run 19/20 combined

for run 20 (after run 19)

energy weeks Events FXT days events
11.5 5 230M 3.5 2 100M
9.1 9.5 160M 3.2 2 100M
7.7 12 100M      


STAR run19-20 BUR

 STAR Beam Use Request for Runs 19 and 20

 

Guidance

Meeting Schedule & Time Line

  • Weekly committee meetings on Tuesday at noon (EST)
    • Blue Jeans information:
      To join the Meeting:
      https://bluejeans.com/406880288
      
      To join via Room System:
      Video Conferencing System: bjn.vc -or-199.48.152.152
      Meeting ID : 406880288
      
      To join via phone :
      1)  Dial:
      	+1.408.740.7256 (United States)
      	+1.888.240.2560 (US Toll Free)
      	+1.408.317.9253 (Alternate number)
      	(see all numbers - http://bluejeans.com/numbers)
      2)  Enter Conference ID : 406880288
      
  • Time lines:
    • draft document to Collaboration: April 17, 2018
    • final version to Berndt Mueller: May 1, 2018
    • NPP 2018 PAC Meeting: June 7-8, 2018
BUR 2018 Document

Official charge Berndt Mueller

Dear Helen & Zhangbu:

I am writing to solicit the STAR beam use requestDear Helen & Zhangbu:
 
I am writing to solicit the STAR beam use request for RHIC Run-19
and to request presentations from the RHIC collaborations at this
year’s PAC meeting, which is scheduled to be held on June 7-8, 2018.
 
We anticipate the 2019 RHIC run to constitute the first year of a
two-year high statistics beam energy scan. The 2017 PAC assigned
highest priority to proposed Au+Au runs at 11.5, 14.5, and 19.6 GeV, 
interleaved by brief fixed target runs at the same beam energies, as 
well as dedicated fixed target runs corresponding to CM energies of 
7.7, 6.2, and 5.2 GeV. The PAC tentatively recommended Au+Au runs in 
the collider mode at 9.1 and 7.7 GeV during the 2020 RHIC campaign.
 
The STAR collaboration should not simply take these tentative 
recommendations as a given, but reconsider and justify the prioritized 
set of beam energies and the requested accumulated statistics at each 
energy, assuming either 24 cryo-week runs or 20 cryo-week runs in each 
of the years 2019 and 2020.
 
The beam use request should be submitted no later than May 1 in order 
to allow the PAC members to study it in detail before the meeting.
 
In addition to the STAR beam use request, I would like to request
updates from STAR and PHENIX on the status of results from Runs 14-17 
(14-16 for PHENIX).
 
Best regards
Berndt


2018 PAC Committee Members 

M. Gazdzicki (CERN), J. Harris (Yale, chair), H. Huang (UCLA),
V. Koch (LBNL), J.C. Peng (UIUC), S. Pratt (MSU), K. Rajagopal (MIT),
A. Schaefer (Regensburg), M. Stephanov (UIC), and J. Velkovska (Vanderbilt).
Scott Pratt has indicated that he will not be able to attend.


STAR BUR Committee and Assignments

Physics Highlights (Runs 14-17) -- Heavy Ion: Xin Dong, Takafumi Niida; Spin: Kevin Adkins
Run 19/20 Requests --  BES2: Declan Keane, Grazyna Odyniec, Sevil Salur; FXT: Daniel Cebra, Terry Tarnowsky
Upgrades           --  Flemming Videbaek, Rosi Reed, Ingo Deppner
Ex-Officio         --  Helen Caines, Zhenyu Ye, Jim Drachenburg, Grigory Nigmatkulov
Frank Geurts (chair)

STAR run20-21 BUR

 STAR Beam Use Request for Runs 20 and 21

 

Guidance

Meeting Schedule & Time Line

  • Weekly committee meetings Tuesday noon - 1h30pm (EDT)
    • Blue Jeans information:
      To join the Meeting:
      https://bluejeans.com/625208370
      
      To join via Room System:
      Video Conferencing System: bjn.vc -or-199.48.152.152
      Meeting ID : 625 208 370
      
      To join via phone :
      1)  Dial:
      	+1.408.740.7256 (United States)
      	+1.888.240.2560 (US Toll Free)
      	+1.408.317.9253 (Alternate number)
      	(see all numbers - http://bluejeans.com/numbers)
      2)  Enter Conference ID : 625 208 370
      
  • Time lines:
BUR 2019 Document

Official charge Berndt Mueller

Dear Helen & Zhangbu:
 
I am writing to solicit the STAR beam use request for RHIC Run-20
and to request presentations at this year’s PAC meeting, which is 
scheduled to be held on June 10-11, 2019.
 
The 2020 RHIC run will be the second year of the planned three-year
high statistics beam energy scan. The 2018 PAC tentatively assigned 
first priority for Runs 20-21 to data taking in the collider mode at 
7.7, 9.1, and 11.5 GeV CM energy, accumulating at least 100M, 160M,
and 230M min bias events, respectively. Second priority was assigned
to fixed target runs at 3.0, 3.2, 3.5, 5.2, and 6.2 GeV CM energy, 
acquiring at least 100M events at each energy, but did not specify 
exactly in which order these data should be taken, except that 
optimal use should be made of the availability of electron cooling 
to enhance the luminosity.
 
The STAR collaboration should not simply take these tentative 
recommendations as a given, but reconsider and justify the 
prioritized set of beam energies and the requested accumulated 
statistics at each energy, assuming either a 24 or a 28 cryo-week 
run in FY2020, followed by a 20 cryo-week run in FY2021. STAR should
also consult with C-AD about the number of dedicated LEReC 
commissioning weeks that are expected to be required during Run-20.
 
In addition, I request presentations on (i) the status of data 
analysis from previous RHIC runs and (ii) an update of the physics
goals for a short (16 cryo-weeks) forward Spin physics run in FY22 
with 500 GeV p+p collisions. 
 
The beam use request should be submitted no later than May 15 in 
order to allow the PAC members to study it in detail before the meeting.
 
Best regards
Berndt


2019 PAC Committee Members 

Masayuki Asakawa, John Harris (chair), Huan Huang, Volker Koch, Jen-Chieh Peng,
Scott Pratt , Krishna Rajagopal, Mikhail Stephanov, Julia Velkovska

Bill Christie, Dmitri Denisov, Jamie Dunlop, Wolfram Fischer, Achim Franz (secretary),
Hong Ma, Berndt Mueller, Thomas Roser, Ferdinand Willeke


STAR BUR Committee and Assignments

Physics Highlights -- 
  - Heavy Ions: Aya Jowzaee (BulkCorr), Hanseul Oh (Jets), Xin Dong (HF), Sevil Salur (Spectra);
  - Spin: Zilong Chang, Jinlong Zhang
BES-II Upgrades:  Irakli Chakaberia (iTPC), Tetyana Galatyuk (eTOF), Rosi Reed (EPD)
BES-II Run Plan: Dan Cebra, Declan Keane, Grazyna Odyniec, Xiaofeng Luo
pp 500 Run Plan: Jim Drachenberg, Elke Aschenauer, Scott Wissink
The case for AuAU at 16.7GeV: Xiaofeng Luo
The case for a small systems scan: Wei Li

Ex-Officio    --  Helen Caines, Zhenyu Ye, Grigory Nigmatkulov
Chair         --  Frank Geurts

STAR Technical Support Group

On this site you'll be able to:

 

 

Electronics Lab private network

 

Plan Overview:
 

In Room 1-232 (the "Electronics Lab"), our goal is to remove experimental test equipment and unsupported (or poorly supported) computer systems from the "public" network.   These are likely sources of Cyber Security concerns and may benefit from a less volatile network environment than the campus network.  To do this, we will create a private network in the Electronics Lab, with one maintained Linux node that will be dual-homed on the public network to act as a gateway to access the private network as needed.   With the introduction of one (or more) Linux box(es), eventually we hope to retire the old Sun workstation completely.

The address space we will use is 192.168.140.0/255.255.255.0 (256 IP addresses).  This is "registered" with ITD network operations as a STAR private network, so that if anything "escapes" from the private space into the campus network, they will know who to call.

Given the short list of anticipated devices (below), no name server is planned, nor other common network services such as DHCP (subject to change as needed). 

Devices Using This Network:

  1. The Linux gateway system -- presley.star.bnl.gov (Scientific Linux 4.5) using 192.168.140.1
  2. One Sun Ultra E450 -- "svtbmonitor" (Solaris 8) using 192.168.140.2 
  3. One serial console server using 192.168.140.3 
  4. Several (~4-5) rack-mounted MVME or similar devices at any time.  An initial set have been assigned 192.168.140.11-15.  A set of working sample boot parameters are included in a file attached to this page (see the links in the Attachments section below).
  5. Update August 4, 2009:  Six more processors are being added to the network.  The name trgfe6 through trgfe11 have been assigned 192.168.140.16-21 (ie. added to /etc/hosts on presley and svtbmonitor).
  6. Several Windows PC's, including laptops that may come and go (which will require manual configuration -- a small inconvenience that can perhaps be overcome with networking "profile" software that stores multiple configurations on the node -- to be investigated, such as http://www.eusing.com/ipswitch/free_ip_switcher.htm

Status:

A Linux box named presley.star.bnl.gov is configured on the public network, with a second NIC using 192.168.140.1 to act as a manual gateway node as needed.  It is in the south-west corner of the lab.  An account named daqlab has been created (contact Wayne or Danny for the password if appropriate)

 

For the effort to replace svtbmonitor,  the home directory of svtbmonitor's testlab account have been copied over to presley in /home/svtbmonitor/testlab. 

Danny and Phil identified a handful of files from svtbmonitor as important so far:

  • emc.tcl
  • smd_qa.tcl
  • tower_qaodt.tcl
  • grab (compiled C code to open a window and connect to a specified node on the serial console server)
  • grab.bag (used by grab to "resolve" common names into ports on the console server)

The original versions of these files are all in their original (relative) paths, and modified versions for presley and the current networking setup were created and put in /home/daqlab/.  The Tcl scripts were modified to account for the slightly different environment on presley and were demonstrated to work (at least the basics - still needs testing to confirm full functionality).  The "grab" executable had to be recompiled from source (simple enough - the required source code consists of "grab.c" and only required a single minor change for the new environment on presley).  So far so good there.

 

Two small "desktop" 10/100 Mbps switches have been connected to each other to serve as the "backbone":

  • one is on a shelf on the west wall
  • the other is on a shelf on the north wall

 

This is easy to expand with one or two 16-port switches if needed (well, it actually is needed as I write this...).  (In fact, these switches have been rather fluid in the first months, coming and going and being swapped for others, all at a slight inconvenience to those of us trying to work with them...)

[Feb. 19, 2009 update -- the physical layout of switches and cables has been switched around many times since this description and I don't know the current state.]

The old networking (not to mention the serial lines) is a mess of cables, old hubs and switches that I plan to ignore as long as possible, though most should be removed if it isn't nailed down.  [Feb. 19, 2009 - some clean up appears to have been done by the folks working in the lab.]

 

To Be Done, moving from svtbmonitor to presley (last updated, Feb 19, 2009):

Towards this end we've identified the following remaining tasks:

Configure backups of the home directories on presley as another safety net for the critical content from svtbmonitor that has been transferred over.

Jack Engelage and Hank Crawford have transferred a bunch of files from svtbmonitor to presley [are they done?].  A "trigger" group was created containing Jack, Chris and Hank.  They have /home/trigger to share amongst themselves.

The biggies: 

VxWorks compilers for Linux and booting the VME processors from presley.  [Feb 19, 2009 update:  Yury Gorbunov (and Jack Engelage?) have made successful boots of trgfe3 from presley via FTP, so it looks like svtbmonitor has a chance of being retired at some point.  Sample boot parameters are attached]

 

Ralph test area

This is my first test page.

Shutdown schedule

FY04

Project Start Date: Fri 1/2/04
Project Finish Date: Mon 10/25/04

STAR FY04 v3 Shutdown


ID
Name
DurationStart_DateFinish_DateResource_NamesPredecessorsSuccessors
1
STAR Detector Operations
211.35 daysMon 1/5/04Mon 10/25/04   
2
Physics Run FY04
96 daysMon 1/5/04Sat 5/15/04  5FF
3
Start Shutdown Activities
116.35 daysSat 5/15/04Mon 10/25/04   
4
Move Detector into AB
14.6 daysSat 5/15/04Thu 6/3/04   
5
Purge TPC Gas
1 daySat 5/15/04Sat 5/15/04 2FF6SS
6
Subsystem Testing
6 daysSat 5/15/04Fri 5/21/04 5SS7
7
Retract PMD Detector
0.1 daysMon 5/24/04Mon 5/24/04Mech.Tech.68
8
Remove East BBC Detector
0.25 daysMon 5/24/04Mon 5/24/04Mech.Tech.79
9
Retract East Pole Tip
0.5 daysMon 5/24/04Mon 5/24/04Mech.Tech.[2]810FF
10
Install Scaffold
0.25 daysMon 5/24/04Mon 5/24/04Carpenter[2]9FF12,11
11
Remove Shield Wall
2.5 daysMon 5/24/04Thu 5/27/04Riggers[3]1026,23,16SS,18,135
12
Remove West Pole Tip Utilities
0.25 daysMon 5/24/04Tue 5/25/04Mech.Tech.1013
13
Remove West BBC Detector
0.25 daysTue 5/25/04Tue 5/25/04Mech.Tech.1214
14
Retract West Pole Tip
0.5 daysTue 5/25/04Tue 5/25/04Mech.Tech.[2]1315FF
15
Install Scaffold
0.13 daysTue 5/25/04Tue 5/25/04Carpenter[2]14FF 
16
Disconnect Electrical Power
0.5 daysMon 5/24/04Tue 5/25/04Electrician[2]11SS18,17
17
Disconnect Magnet Power
0.5 daysTue 5/25/04Tue 5/25/04Elect.Tech.[2]1618
18
Remove Buss Bridge
0.25 daysThu 5/27/04Thu 5/27/04Mech.Tech.[2]16,17,1119,21
19
Disconnect Platform MCWS
0.5 daysThu 5/27/04Fri 5/28/04Mech.Tech.1820
20
Disconnect Subsystems Utilities
1 dayFri 5/28/04Mon 5/31/04Mech.Tech.1926
21
Remove Platform Bridge
0.25 daysThu 5/27/04Thu 5/27/04Mech.Tech.[2]1826,22
22
Remove South Platform Stairs
0.25 daysThu 5/27/04Fri 5/28/04Mech.Tech.[2]2126,24
23
Disconnect RHIC Vacuum Pipe
0.5 daysThu 5/27/04Thu 5/27/04Mech.Tech.11 
24
Remove Seismic Anchors
0.25 daysFri 5/28/04Fri 5/28/04Mech.Tech.[2]2225
25
Disconnect Magnet LCW
0.25 daysFri 5/28/04Fri 5/28/04Mech.Tech.[2]2426
26
Roll Detector into AB
1 dayMon 5/31/04Tue 6/1/04Mech.Tech.[2]11,21,22,25,2027
27
Blow-out Magnet Coils
0.5 daysTue 6/1/04Tue 6/1/04Mech.Tech.[2]2628
28
Connect South Platform Stairs
0.5 daysTue 6/1/04Wed 6/2/04Mech.Tech.[2]2729
29
Connect Platform Bridge
0.5 daysWed 6/2/04Wed 6/2/04Mech.Tech.[2]2831,30
30
Connect Seismic Anchors
0.5 daysWed 6/2/04Thu 6/3/04Mech.Tech.29 
31
Install Buss Bridge
0.5 daysWed 6/2/04Thu 6/3/04Mech.Tech.[2]2932
32
Connect Electrical Power
0.5 daysThu 6/3/04Thu 6/3/04Electrician[2]3133SS
33
Connect Subsystems Utilities
0.5 daysThu 6/3/04Thu 6/3/04Mech.Tech.32SS34SS
34
Connect Platform MCWS
0.5 daysThu 6/3/04Thu 6/3/04Mech.Tech.33SS35
35
Detector In AB
0 daysThu 6/3/04Thu 6/3/04 3437,117,121
36
Remove East & West FTPC
13.75 daysThu 6/3/04Wed 6/23/04   
37
Remove E/W IFC Air Manifolds
0.25 daysThu 6/3/04Thu 6/3/04Mech.Tech.3538
38
Remove East & West Scaffold
0.5 daysThu 6/3/04Fri 6/4/04Carpenter[2]3739
39
Install West Platform & Rails
1 dayFri 6/4/04Mon 6/7/04Carpenter[2]3840,41
40
Remove West FTPC
0.5 daysMon 6/7/04Mon 6/7/04Mech.Tech.3945
41
Rig Installation Frame into AB
0.5 daysMon 6/7/04Mon 6/7/04Riggers[3]3942SS
42
Install East Installation Frame
0.5 daysMon 6/7/04Mon 6/7/04Mech.Tech.[2]41SS43
43
Install East Rails
1 dayMon 6/7/04Tue 6/8/04Mech.Tech.[2]4244
44
Remove East FTPC
0.5 daysTue 6/8/04Wed 6/9/04Mech.Tech.[2]4345
45
East & West FTPC's Removed
0 daysWed 6/9/04Wed 6/9/04 40,4446,48
46
Maintenance on FTPC's
10 daysWed 6/9/04Wed 6/23/04Electronic Tech45 
47
Remove Cone
11.5 daysWed 6/9/04Thu 6/24/04   
48
Disconnect Utilities
4 daysWed 6/9/04Tue 6/15/04Mech.Tech.4549
49
Remove Cone from IFC
0.5 daysTue 6/15/04Tue 6/15/04Mech.Tech.4876,126
50
Remove East Installation Frame
1 dayTue 6/22/04Wed 6/23/04Mech.Tech.[2]76,12651FF
51
Remove Installation Frame from AB
0.5 daysWed 6/23/04Wed 6/23/04Riggers[3]50FF52
52
Remove Installation Frame West
1 dayWed 6/23/04Thu 6/24/04Carpenter[2]5153
53
Cone Removed
0 daysThu 6/24/04Thu 6/24/04 5257
54
Install East BEMC Modules
47.5 daysMon 6/14/04Wed 8/18/04   
55
(30) Modules Delivered
4 daysMon 6/14/04Fri 6/18/04Riggers[3]57FF-5 days56FF
56
(30) Modules Staged in AB
4 daysMon 6/14/04Fri 6/18/04Mech.Tech.[2]55FF 
57
Install East & West Scaffold
0.5 daysThu 6/24/04Fri 6/25/04Carpenter[2]5358,55FF-5 days
58
Remove East Side Cables & Tray
3 daysFri 6/25/04Wed 6/30/04Mech.Tech.[2]5759
59
Erect Installation Fixture S.E. Upper
0.5 daysWed 6/30/04Wed 6/30/04Mech.Tech.[2]5860
60
Remove S.E. TPC Support Arm
0.25 daysWed 6/30/04Thu 7/1/04Mech.Tech.[2]5961
61
Install Modules 106-103
4 daysThu 7/1/04Wed 7/7/04Mech.Tech.[2]6062
62
Erect Installation Fixture S.E. Lower
0.5 daysWed 7/7/04Wed 7/7/04Mech.Tech.[2]6163
63
Install Modules 102-89
14 daysWed 7/7/04Tue 7/27/04Mech.Tech.[2]6264
64
Install S.E. TPC Support Arm
0.5 daysTue 7/27/04Wed 7/28/04Mech.Tech.[2]6365
65
Erect Installation Fixture N.E. Lower
0.5 daysWed 7/28/04Wed 7/28/04Mech.Tech.[2]6466
66
Install Modules 77-88
12 daysWed 7/28/04Fri 8/13/04Mech.Tech.[2]6567
67
Remove Installation Fixture
0.25 daysFri 8/13/04Fri 8/13/04Mech.Tech.[2]6668
68
Install East Side Cables & Tray
3 daysFri 8/13/04Wed 8/18/04Mech.Tech.[2]6769
69
East BEMC Installation Complete
0 daysWed 8/18/04Wed 8/18/04 6882,72
70
Install BEMC PMT Boxes
35 daysWed 7/14/04Wed 9/1/04   
71
Install 208 VAC Power
15 daysWed 7/14/04Wed 8/4/04Electrician[2]72SF-10 days 
72
Install PMT Boxes
10 daysWed 8/18/04Wed 9/1/04Mech.Tech.[2]6973FF,71SF-10 days
73
Install Electronics
20 daysWed 8/4/04Wed 9/1/04Electronic Tech72FF74
74
PMT Box Installation Complete
0 daysWed 9/1/04Wed 9/1/04 73144
75
Install SSD
20.5 daysTue 6/15/04Wed 7/14/04   
76
Rig Cone to Cleanroom Roof
0.5 daysTue 6/15/04Wed 6/16/04Mech.Tech.4977,50
77
Install SSD on Cone
20 daysWed 6/16/04Wed 7/14/04Mech.Tech.7678SS,80
78
Install LV Crate & Cables
5 daysWed 6/16/04Wed 6/23/04Electronic Tech77SS79
79
Install RDO Boxes
5 daysWed 6/23/04Wed 6/30/04Electronic Tech78 
80
SSD Installed on Cone
0 daysWed 7/14/04Wed 7/14/04 7785
81
Install Cone
20.5 daysWed 8/18/04Thu 9/16/04   
82
Rig Installation Frame into AB
0.5 daysWed 8/18/04Thu 8/19/04Riggers[3]6983SS
83
Install East Installation Frame
0.5 daysWed 8/18/04Thu 8/19/04Mech.Tech.[2]82SS84
84
Install Tables & Rails
0.5 daysThu 8/19/04Thu 8/19/04Mech.Tech.8385
85
Rig Cone to Rails
0.5 daysThu 8/19/04Fri 8/20/04Mech.Tech.[2]84,8086
86
Survey SSD to SVT
2 daysFri 8/20/04Tue 8/24/04Surveyors[2]8587
87
Complete SSD Installation
2 daysTue 8/24/04Thu 8/26/04Mech.Tech.8688
88
Test Utility Connections
1 dayThu 8/26/04Fri 8/27/04Electronic Tech8789FF
89
Clean TPC IFC
1 dayThu 8/26/04Fri 8/27/04Mech.Tech.88FF90
90
Install Cone in Detector
0.5 daysFri 8/27/04Fri 8/27/04Mech.Tech.8991
91
Test IFC High Voltage
0.5 daysFri 8/27/04Mon 8/30/04Electronic Tech9092
92
Survey TPC to Magnet
2 daysMon 8/30/04Wed 9/1/04Surveyors[2]9193
93
Survey SVT to TPC
2 daysWed 9/1/04Fri 9/3/04Surveyors[2]9294
94
Install East Partitions
0.5 daysFri 9/3/04Fri 9/3/04Mech.Tech.93110
95
Connect Water Lines
0.5 daysMon 9/6/04Tue 9/7/04Mech.Tech.11096
96
Connect RDO Cables
1 dayTue 9/7/04Wed 9/8/04Electronic Tech9597
97
Remove East Rails from IFC
0.5 daysWed 9/8/04Wed 9/8/04Mech.Tech.[2]9698
98
Remove East Installation Frame
0.5 daysWed 9/8/04Thu 9/9/04Mech.Tech.[2]9799FF
99
Remove Installation Frame from AB
0.25 daysThu 9/9/04Thu 9/9/04Riggers[3]98FF100
100
East Side Complete
0 daysThu 9/9/04Thu 9/9/04 99107,101
101
Install West Partitions
0.5 daysThu 9/9/04Thu 9/9/04Mech.Tech.100112
102
Connect Water Lines
0.5 daysMon 9/13/04Mon 9/13/04Mech.Tech.114103
103
Connect RDO Cables
1 dayMon 9/13/04Tue 9/14/04Electronic Tech102104
104
Remove West Rails from IFC
0.5 daysTue 9/14/04Wed 9/15/04Mech.Tech.103105
105
Remove Installation Frame West
1 dayWed 9/15/04Thu 9/16/04Carpenter[2]104106
106
West Side Complete
0 daysThu 9/16/04Thu 9/16/04 105107
107
Cone Installation Complete
0 daysThu 9/16/04Thu 9/16/04 100,106144
108
Install FTPC East & West in AB
12.5 daysWed 8/25/04Mon 9/13/04   
109
Run & Test N. Platform
5 daysWed 8/25/04Wed 9/1/04Electronic Tech110SF-2 days 
110
Install East FTPC in Detector
1 dayFri 9/3/04Mon 9/6/04Mech.Tech.[2]94115,109SF-2 days,95
111
Run & Test N. Platform
5 daysWed 9/1/04Wed 9/8/04Electronic Tech114SF-2 days 
112
Remove West Scaffold
0.25 daysThu 9/9/04Fri 9/10/04Carpenter[2]101113
113
Install West Platform & Rails
0.25 daysFri 9/10/04Fri 9/10/04Carpenter[2]112114
114
Install West FTPC in Detector
1 dayFri 9/10/04Mon 9/13/04Mech.Tech.[2]113115,111SF-2 days,102
115
FTPC Installed in AB
0 daysMon 9/13/04Mon 9/13/04 114,110 
116
PMD Maintenance
40 daysThu 6/3/04Thu 7/29/04   
117
Subsystem Maintenance
30 daysThu 6/3/04Thu 7/15/04 35118
118
Detector Commisioning
10 daysThu 7/15/04Thu 7/29/04 117119
119
PMD Maintenance Complete
0 daysThu 7/29/04Thu 7/29/04 118 
120
EEMC Maintenance
90 daysThu 6/3/04Thu 10/7/04   
121
Maintenance
50 daysThu 6/3/04Thu 8/12/04 35122SS
122
MAPMT Installation
80 daysThu 6/3/04Thu 9/23/04Mech.Tech.[2]121SS123
123
Subsystem Testing
10 daysThu 9/23/04Thu 10/7/04 122124
124
EEMC Maintenance Complete
0 daysThu 10/7/04Thu 10/7/04 123 
125
TPC Maintenance
50 daysTue 6/15/04Tue 8/24/04   
126
Repair IFC Strip Short
5 daysTue 6/15/04Tue 6/22/04Mech.Tech.49127,50,131SS
127
Modify Resistor Chain
5 daysTue 6/22/04Tue 6/29/04Mech.Tech.126128
128
FEE & RDO Maintenance
40 daysTue 6/29/04Tue 8/24/04Electronic Tech127129
129
TPC Maintenance Complete
0 daysTue 8/24/04Tue 8/24/04 128 
130
TOF Maintenance
15 daysTue 6/15/04Tue 7/6/04   
131
Tray Maintenance
10 daysTue 6/15/04Tue 6/29/04 126SS132
132
Detector Testing
5 daysTue 6/29/04Tue 7/6/04 131133
133
TOFp Maintenance Complete
0 daysTue 7/6/04Tue 7/6/04 132 
134
FPD Installation
20 daysThu 5/27/04Thu 6/24/04   
135
Install West Detectors
10 daysThu 5/27/04Thu 6/10/04Mech.Tech.11136
136
Install N. E. Stand for 20-cm Travel
5 daysThu 6/10/04Thu 6/17/04Mech.Tech.[2]135137
137
Detector Commisioning
5 daysThu 6/17/04Thu 6/24/04 136138
138
FPD Installation Complete
0 daysThu 6/24/04Thu 6/24/04 137140
139
BBC Maintenance
15 daysThu 6/24/04Thu 7/15/04   
140
Subsystem Maintenance
10 daysThu 6/24/04Thu 7/8/04 138141
141
Detector Commisioning
5 daysThu 7/8/04Thu 7/15/04 140142
142
BBC Maintenance Complete
0 daysThu 7/15/04Thu 7/15/04 141 
143
Move Detector into WAH
27 daysThu 9/16/04Mon 10/25/04   
144
Disconnect Electrical Power
0.5 daysThu 9/16/04Thu 9/16/04Electrician[2]107,74147,145SS,146SS
145
Disconnect Platform MCWS
0.5 daysThu 9/16/04Thu 9/16/04Mech.Tech.144SS 
146
Disconnect TPC Utilities
0.5 daysThu 9/16/04Thu 9/16/04Mech.Tech.144SS 
147
Remove Buss Bridge
0.5 daysThu 9/16/04Fri 9/17/04Mech.Tech.[2]144148
148
Remove Platform Bridge
0.5 daysFri 9/17/04Fri 9/17/04Mech.Tech.[2]147149
149
Remove South Platform Stairs
1 dayFri 9/17/04Mon 9/20/04Mech.Tech.[2]148150
150
Disconnect Seismic Anchors
0.5 daysMon 9/20/04Tue 9/21/04Mech.Tech.[2]149151SS
151
Lower Detector to Rails
0.5 daysMon 9/20/04Tue 9/21/04Mech.Tech.[2]150SS152
152
Roll Detector into WAH
1.5 daysTue 9/21/04Wed 9/22/04Mech.Tech.[2]151153,154
153
Connect Magnet LCW
1 dayWed 9/22/04Thu 9/23/04Mech.Tech.[2]152 
154
Raise/Level Detector @ IR
0.5 daysWed 9/22/04Thu 9/23/04Mech.Tech.[2]152155FF,163
155
Connect Seismic Anchors
0.5 daysWed 9/22/04Thu 9/23/04Mech.Tech.[2]154FF159,156
156
Install Buss Bridge
0.5 daysThu 9/23/04Thu 9/23/04Mech.Tech.[2]155157,160
157
Connect Electrical Power
1 dayThu 9/23/04Fri 9/24/04Electrician[2]156158
158
Connect Magnet Power
1 dayFri 9/24/04Mon 9/27/04Elect.Tech.[2]157 
159
Connect All Subsystem Utilities
2 daysThu 9/23/04Mon 9/27/04Mech.Tech.[2]155168,166
160
Connect Platform MCWS
0.5 daysThu 9/23/04Fri 9/24/04Mech.Tech.156168,161
161
Connect South Platform Stairs
1 dayFri 9/24/04Mon 9/27/04Mech.Tech.[2]160162
162
Connect Platform Bridge
0.5 daysMon 9/27/04Mon 9/27/04Mech.Tech.[2]161167
163
Connect Vacuum Pipe & Supports
0.5 daysThu 9/23/04Thu 9/23/04Mech.Tech.[2]154164
164
Vacuum Pipe Bake-out
5 daysThu 9/23/04Thu 9/30/04Mech.Tech.[2]163165
165
Survey Beam Pipe & Magnet
4 daysThu 9/30/04Wed 10/6/04Surveyors[2]164 
166
Detector Safety Certification
2 daysMon 9/27/04Wed 9/29/04 159 
167
Install Shield Wall
3 daysMon 9/27/04Thu 9/30/04Riggers[3]162171
168
Subsystems testing in WAH
20 daysMon 9/27/04Mon 10/25/04 160,159169SS+5 days
169
Install Pole Tips
2 daysMon 10/4/04Wed 10/6/04Mech.Tech.[2]168SS+5 days170
170
Install BBC Detectors
1 dayWed 10/6/04Thu 10/7/04Mech.Tech.[2]169171
171
Shutdown Activities Complete
0 daysThu 10/7/04Thu 10/7/04 167,170 

FY06

STAR FY06 Shutdown Schedule


Project Start Date: 6/26/06
Project Finish Date: 10/27/06

 

STAR FY06 v5 Shutdown

IDWBS
Name
DurationStart_DateFinish_DateResource_NamesPredecessorsSuccessors
11
STAR Detector FY06 Shutdown
87 days6/26/0610/27/06   
21.1
Disconnect Detector Utilities
10.75 days6/26/067/12/06   
31.1.1
Begin Shutdown Activities
0 days6/26/066/26/06  4SS,114SS
41.1.2
Purge TPC Gas
1 day6/26/066/26/06 3SS 
51.1.3
Remove West BBC Detector
0.25 days7/5/067/5/06Mech.Tech.1146,103
61.1.4
Disconnect West Pole Tip Utilities
0.5 days7/5/067/5/06Mech.Tech.[2]57
71.1.5
Retract West Pole Tip
0.5 days7/5/067/6/06Mech.Tech.[2]68FF
81.1.6
Install Scaffold
0.25 days7/6/067/6/06Carpenter[2]7FF9
91.1.7
Remove East BBC Detector
0.25 days7/6/067/6/06Mech.Tech.810,103
101.1.8
Disconnect East Pole Tip Utilities
0.25 days7/6/067/6/06Elect.Tech.[2]911
111.1.9
Retract East Pole Tip
0.5 days7/6/067/7/06Mech.Tech.[2]1012FF,15,13
121.1.10
Install Scaffold
0.25 days7/7/067/7/06Carpenter[2]11FF19
131.1.11
Disconnect Electrical Power
0.5 days7/7/067/7/06Electrician[2]1115,14,17
141.1.12
Disconnect Magnet Power
0.5 days7/7/067/10/06Elect.Tech.[2]1315
151.1.13
Remove Buss Bridge
0.25 days7/10/067/10/06Mech.Tech.[2]13,14,1116
161.1.14
Disconnect Platform MCWS
0.5 days7/10/067/10/06Mech.Tech.[2]1518
171.1.15
Disconnect Subsystems Utilities
2 days7/7/067/11/06Mech.Tech.13 
181.1.16
Remove South Platform Stairs
0.25 days7/11/067/11/06Mech.Tech.[2]1621
191.1.17
Remove pVPD Detectors
0.25 days7/7/067/7/06Mech.Tech.[2]1220
201.1.18
Disconnect RHIC Vacuum Pipe
3 days7/7/067/12/06Mech.Tech.[2]1924
211.1.19
Remove Seismic Anchors
0.25 days7/11/067/11/06Mech.Tech.[2]1822
221.1.20
Disconnect Magnet Water
0.25 days7/11/067/11/06Mech.Tech.[2]2123
231.1.21
Blow-out Magnet Coils
1 day7/11/067/12/06Mech.Tech.[2]2224
241.1.22
Detector Utilities Disconnected
0 days7/12/067/12/06 23,2026,57
251.2
Hydraulic System Testing
6.5 days7/12/067/21/06   
261.2.1
Run & Test Hydraulics
5 days7/12/067/19/06Mech.Tech.2427FF
271.2.2
Position Detector on Beamline
0.5 days7/19/067/19/06Mech.Tech.26FF28SS
281.2.3
Survey Detector on Beamline
2 days7/19/067/21/06Surveyors[2]27SS29
291.2.4
Hydraulics Tests Complete
0 days7/21/067/21/06 2831,67,132,85
301.3
Remove Hilman Rollers
5 days7/31/068/4/06   
311.3.1
Remove Roller Assemblies
5 days7/31/068/4/06Mech.Tech.[2]29,12332FF
321.3.2
Remove Roller Assemblies
2 days8/3/068/4/06Riggers[3]31FF33FF
331.3.3
Crate & Ship Roller Assemblies
1 day8/4/068/4/06Riggers[2],Carpenter[2]32FF34FF
341.3.4
Roller Assembly Removal Complete
0 days8/4/068/4/06 33FF 
351.4
Remove West FPD++ Detector
23.5 days7/5/068/7/06   
361.4.1
Disconnect Cabling
5 days7/5/067/11/06Mech.Tech.11437SS
371.4.2
Remove Existing Cells
13 days7/5/067/21/06Mech.Tech.36SS38
381.4.3
Remove Cabling
5 days7/31/068/4/06Mech.Tech.37,12339
391.4.4
Remove Enclosures & Shield Block
0.5 days8/7/068/7/06Riggers[3]38125,40
401.4.5
FPD++ Removal Complete
0 days8/7/068/7/06 3995
411.5
East FTPC Maintenance
15 days8/7/068/25/06   
421.5.1
Remove East IFC Air Manifolds
0.5 days8/7/068/7/06Mech.Tech.67,12343
431.5.2
Remove East Scaffold
0.5 days8/7/068/7/06Carpenter[2]4244
441.5.3
Rig East FTPC Platform
0.5 days8/8/068/8/06Riggers[3]4345SS
451.5.4
Install East FTPC Platform
0.5 days8/8/068/8/06Carpenter[2]44SS46
461.5.5
Install East FTPC Rails
0.5 days8/8/068/8/06Mech.Tech.[2]4547
471.5.6
Remove East FTPC
1 day8/9/068/9/06Mech.Tech.[2]4648,74
481.5.7
Replace East FTPC FEE
5 days8/10/068/16/06Electronic Tech4749
491.5.8
Install FTPC on Rails & Test
5 days8/17/068/23/06 4850FF
501.5.9
Install East FTPC
0.5 days8/24/068/24/06Mech.Tech.[2]49FF,7551
511.5.10
Remove East FTPC Rails
0.5 days8/24/068/24/06Mech.Tech.[2]5052
521.5.11
Rig East FTPC Platform
0.5 days8/25/068/25/06Riggers[3]5153SS
531.5.12
Remove East FTPC Platform
0.5 days8/25/068/25/06Carpenter[2]52SS54
541.5.13
Install East Scaffold
0.5 days8/25/068/25/06Carpenter[2]5355
551.5.14
FTPC Maintenance Complete
0 days8/25/068/25/06 5486,70
561.6
SSD Maintenance
27.25 days7/12/068/18/06   
571.6.1
Compressor Maintenance
5 days7/12/067/19/06 24 
581.6.2
RDO maintenance
5 days7/31/068/4/06Carpenter[2]67SS59
591.6.3
Crate Maintenance
10 days8/7/068/18/06Riggers[3]58,12360
601.6.4
SSD Maintenance Complete
0 days8/18/068/18/06 59 
611.7
BEMC Maintenance
40 days7/31/069/25/06   
621.7.1
Remove & Repair Crates
20 days7/31/068/25/06Electronic Tech12363
631.7.2
Install PMT Box Remote Power
20 days8/28/069/25/06Electronic Tech[2]6264FF
641.7.3
PMT Box Maintenance
20 days8/28/069/25/06Elect.Tech.63FF65
651.7.4
BEMC Maintenance Complete
0 days9/25/069/25/06 64145
661.8
SVT RDO Box Relocation
39 days7/31/069/22/06   
671.8.1
Remove RDO Boxes
5 days7/31/068/4/06Electronic Tech29,12368,42,58SS
681.8.2
Repair RDO Boxes
20 days8/7/069/1/06Electronic Tech6769
691.8.3
Install West RDO Boxes
2 days9/12/069/13/06Electronic Tech68,8772,81,70
701.8.4
Install Remote East RDO Boxes
5 days9/14/069/20/06Mech.Tech.69,5571
711.8.5
Rout East RDO Cables
2 days9/21/069/22/06Electronic Tech[2]7072
721.8.6
SVT RDO Box Relocation Complete
0 days9/22/069/22/06 71,69139,145
731.9
HFT Prototype Installation
10 days8/10/068/23/06   
741.9.1
Install East HFT Prototype
10 days8/10/068/23/06Mech.Tech.[2]4775
751.9.2
HFT Prototype Installed
0 days8/23/068/23/06 7450
761.10
PMD Maintenance
40 days7/31/069/25/06   
771.10.1
Replace Supermodules
30 days7/31/069/11/06 12378
781.10.2
Detector Maintenance
10 days9/12/069/25/06 7779
791.10.3
PMD Maintenance Complete
0 days9/25/069/25/06 78145
801.11
EEMC Maintenance
15 days9/14/0610/4/06   
811.11.1
PMT/MAPMT Box Maintenance
12 days9/14/069/29/06Mech.Tech.[2]69,11282SS
821.11.2
Subsystem Testing
15 days9/14/0610/4/06 81SS83
831.11.3
EEMC Maintenance Complete
0 days10/4/0610/4/06 82145,115
841.12
TPC Maintenance
35.75 days7/21/069/11/06   
851.12.1
Remove East/West Bad FEE/RDO
5 days7/21/067/28/06Electronic Tech[2]2988
861.12.2
Install East FEE/RDO
5 days8/28/069/1/06Electronic Tech[2]5589,87
871.12.3
Install West FEE/RDO
5 days9/5/069/11/06Electronic Tech[2]8689,69
881.12.4
Maintenance on Gas Room UPS
1 day7/28/067/31/06 8589
891.12.5
TPC Maintenance Complete
0 days9/11/069/11/06 88,87,86139,145,107
901.13
TOF Maintenance
5 days10/5/0610/11/06   
911.13.1
Remove Old Tray
2 days10/5/0610/6/06Mech.Tech. 92
921.13.2
Install New Trays
3 days10/9/0610/11/06Mech.Tech.9193
931.13.3
TOF Installation Complete
0 days10/11/0610/11/06 92115
941.14
FMS Installation
43 days8/7/0610/6/06   
951.14.1
Install FMS Carriages
5 days8/7/068/14/06Mech.Tech.[2]4096
961.14.2
Install FMS Cells
30 days8/14/069/26/06Mech.Tech.[2]9598FF,97SS
971.14.3
Install AC Power
5 days8/14/068/21/06Electrician[2]96SS100
981.14.4
Install FMS Enclosures
5 days9/19/069/26/06Mech.Tech.[2]96FF99
991.14.5
Install FMS Cabling
8 days9/26/0610/6/06Mech.Tech.[2]98101
1001.14.6
Install Electronics Racks
10 days8/21/069/5/06Electronic Tech[2]97101
1011.14.7
FMS Installation Complete
0 days10/6/0610/6/06 99,100145
1021.15
BBC Maintenance
25 days7/6/068/10/06   
1031.15.1
Subsystem Maintenance
20 days7/6/068/3/06 5,9104
1041.15.2
Detector Commisioning
5 days8/3/068/10/06 103105
1051.15.3
BBC Maintenance Complete
0 days8/10/068/10/06 104 
1061.16
Trigger Maintenance
10 days9/12/069/25/06   
1071.16.1
Trigger Maintenance
10 days9/12/069/25/06 89108
1081.16.2
Trigger Maintenance Complete
0 days9/25/069/25/06 107145
1091.17
Pole Tip Hose Replacement
5 days7/31/068/4/06   
1101.17.1
Remove Old Hose
2 days7/31/068/1/06Mech.Tech.[2]123111
1111.17.2
Install New Braided Hose
3 days8/2/068/4/06Mech.Tech.[2]110112
1121.17.3
Hose Replacement Complete
0 days8/4/068/4/06 11181
1131.18
Magnet Power Supply Maintenance & Test
87 days6/26/0610/27/06   
1141.18.1
Power Supply Maintenance & Test
5 days6/26/066/30/06Electronic Tech[2]3SS5,36
1151.18.2
Remove East/West Scaffold
0.5 days10/12/0610/12/06Carpenter[2]83,93116SS
1161.18.3
Install East Pole Tip
1 day10/12/0610/12/06Mech.Tech.[2]115SS117
1171.18.4
Install West Pole Tip
1 day10/13/0610/13/06Mech.Tech.[2]116118,143FF
1181.18.5
Power Supply Maintenance & Test
10 days10/16/0610/27/06Electronic Tech[2]117119
1191.18.6
Power Supply Maintenance Complete
0 days10/27/0610/27/06 118146
1201.19
C-AD Maintenance
49 days7/24/069/29/06   
1211.19.1
SGIS Modifications
10 days9/18/069/29/06Elect.Tech.[2] 130,144
1221.19.2
PS Sound Barrier Wall
10 days7/31/068/11/06 123 
1231.19.3
AC Substation Maintenance
5 days7/24/067/28/06  62,110,124,128,77,42,59,31,67,38,132,122
1241.19.4
Control Room Modification
10 days7/31/068/11/06 123126
1251.19.5
Install West Tunnel Shielding
5 days8/7/068/14/06Riggers[3]39 
1261.19.6
DAQ Room A/C Upgrade
10 days8/14/068/25/06 124127
1271.19.7
Fire Sprinkler Preaction Upgrade
10 days8/28/069/11/06 126130
1281.19.8
MCW Flow Balance
10 days7/31/068/11/06Mech.Tech.[2]123129
1291.19.9
Seal Tower Basin
5 days8/14/068/18/06Mech.Tech.[2]128 
1301.19.10
C-A Maintenance Complete
0 days9/29/069/29/06 127,121 
1311.20
Connect Detector Utilities
64 days7/31/0610/27/06   
1321.20.1
Connect Magnet LCW
1 day7/31/067/31/06Mech.Tech.[2]29,123133
1331.20.2
Install Buss Bridge
0.5 days8/1/068/1/06Mech.Tech.[2]132134,137
1341.20.3
Connect Electrical Power
1 day8/1/068/2/06Electrician[2]133135,136
1351.20.4
Connect Magnet Power
1 day8/2/068/3/06Elect.Tech.[2]134 
1361.20.5
Connect All Subsystem Utilities
1 day8/2/068/3/06Mech.Tech.[2]134 
1371.20.6
Connect Platform MCWS
0.5 days8/1/068/1/06Mech.Tech.133138
1381.20.7
Connect South Platform Stairs
1 day8/2/068/2/06Mech.Tech.[2]137 
1391.20.8
Connect Vacuum Pipe & Supports
3 days9/25/069/27/06Mech.Tech.[2]72,89140SS
1401.20.9
Vacuum Pipe Bake-out
10 days9/25/0610/6/06Mech.Tech.[2]139SS141
1411.20.10
Install START Detectors
0.5 days10/9/0610/9/06Mech.Tech.140142
1421.20.11
Survey Beam Pipe
2 days10/9/0610/11/06Surveyors[2]141143
1431.20.12
Install BBC Detectors
1 day10/13/0610/13/06Mech.Tech.[2]142,117FF 
1441.20.13
Detector Safety Certification
5 days10/2/0610/6/06 121145
1451.20.14
Subsystems testing in WAH
5 days10/9/0610/13/06 144,65,108,101,72,79,83,89146
1461.20.15
Shutdown Activities Complete
0 days10/27/0610/27/06 145,119 

 

 

Users area

STAR User's home page area.

 

Bedagadas Mohanty

 

 

 

Figures from STAR publications

Baryon to Meson ratio  v2 vs. Beam energy  low pT spectra    particle ratio

 

Jet                              Typical dijet-event         Raa/dau 

 

Theory Figures

Cross-over                   Phasediagram

 

 

 

 

genevb: miscellaneous working plots

____________________________________________________________
____________________________________________________________
hello :::0 there.




_____________

:::0YYY ZZZ AAACCCDDD

Misc1

 

Misc2

 

misc3

 

Web master

The STAR www site is divided into a few parts, most will converge to a unique Drupal based content management system as time will unfold.

As a Collaboration, STAR makes use of the web for much of its daily functioning: communication, documentation, organization and many other activities. In addition to being a tool for the Collaboration, the web also serves as a means for introducing our experiment, sharing our enthusiasm, and conveying our results to the rest of the interested world. This includes both scientists and non-scientists alike.

For more information about this www site, contact the appropriate person below.

Click here to contribute news items and meeting announcements or a general comment.

 

Daniel Nemes|
David Steward|
Central site design & maintenance
PHP scripting & support
mySQL database design
STAR publications
 
Jerome Lauret | Server configuration & support
Hypernews mailing lists
Drupal site config
Liz Mogavero | Collaboration support
Meetings & events coordination