Embedding

Welcome to the STAR Embedding Pages!

Embedding data are generally used in STAR experiments for detector acceptance & reconstruction efficiency study. In general, the efficiency depends on running conditions, particle types, particle kinematics, and offline software versions. In principle, each physics analysis will need to formulate its own embedding requests by providing all the above relevant information. In STAR Collaboration, the embedding team is assigned to process those embedding requests and provide these embedding data, you can find out how the embedding team works in the Embedding structure page.

Over the past years, lots of embedding requests from different PWG's have been processed by the embedding team, please find the list in STAR Simulations Requests interface. If you want to look at some of these data, but do not know where these data are stored, please go to this page. If you can not find similar embedding request, you need to formulate your own embedding request for your particular study, please go to this page for more information about how to formulate an embedding request.

Finding existing embedding data

Embedding data were produced for each embedding request in the STAR Simulations Request page.
Normaly, they will be stored in PDSF/RCF NFS disks for a while for end users to do their analysis.
However, NFS disk space is limited, and we have new requests constantly, the data will be finally moved
from disks to HPSS for permanent storage on tape, but they can be restaged to disk for analysis later.

In order to find the existing embedding either on disks or in HPSS. Please follow the procedures below:

1) Find the request ID of a particular request that you are interested in, in the STAR Simulations Request page.
    You can use the "Search" box at the top right of this page.

2) For the requests before 2016 (ID# < 2016xxxx), look for the samples at RCF first.
    First, look at the list of embedding samples produced at RCF maintained by Lidia. If you can find the 
    data in this list, then logon to RCF, look for '/star/data18' to see whether the following directories exist:

    /star/data18/embedding/${Trigger set name}/${Embeded Particle}_${fSet}_${RequestID}/

    If it exists, you can further check whether all the ${fSet} from 'fSet min' to 'fSet max' are there. If all exist, 
    you can start to use it. If none of them are there or only some fraction of 'fSet' are there, write to the embedding list
    and ask the Emebedding Coordinator to restage it to there from HPSS.

3) If the samples that you are looking for is not in Lidia's list. They must be in PDSF, which is our major site for
    embedding production now. At PDSF, all the samples on disk are stored at:
    
     /projecta/projectdirs/starprod/embedding/${Trigger set name}/${Embeded Particle}_${fSet}_${RequestID}/

    You can logon to PDSF, and look around these directories first to see whether the data are there. Or, you can explore
    the structure of "/projecta/projectdirs/starprod/embedding/" directory in a nice weblist, maintained by Jochen Thaeder.
    If you can not find the embedding data in this directory, the data must be in PDSF HPSS. Unfortunately, there is not
    a list of data stored in PDSF HPSS yet. Please write to the embedding list, provide the request ID, Particle Name, file type
    (minimc.root or event.root), and ask the Embedding Coordinator to restage the data to disk for you.


Operations (OBSOLETE)

The full list of STAR embedding requests (Since August, 2010):
http://drupal.star.bnl.gov/STAR/starsimrequest
The operation status of each request can be viewed in its page and history.

The information below (and in sub-pages) are only valid to OLD STAR embedding requests.

Request status

- Currently pending requests

- Old Requests summary (circa Nov 2006)

New requests

 

 

Current Requests

Current Requests were either submitted using the cgi web interface before it had to be removed (September 2007) or via email to the embedding-hn hypernews list.

As such there is not a single source of information. The excel spreadsheet here is a summary of the known requests as of August 2008 (also pdf printout for those without access to excel). The co-ordinator should keep this updated.

Heavy flavour have also kept an up to date page with their extensive list of requests. See here.

[The spreadsheet was part of a presentation (ppt|pdf) in August 2008 on the state of embedding at the end of my tenure as EC - Lee Barnby]

New Requests

In the near future we hope to have a dedicated drupal module available for entering embedding (and simulation) requests. This will have fields for all the required information and a work flow which will indicate the progress of the request. At the time of writing (August 2008) this is not available. A workable interim solution is to make requests using this page by selecting the 'Add Child Page' link. One should then write a page with the information for the request. Follow-up by members of the embedding team and requestors canthen use the 'Comment' facility on that page.

The following is required

  • pt range
  • pt distribution (flat, exponential)
  • rapidity
  • ...
  • (to be completed)

 

Old Requests

Overview



This page is intended to provide details of embedding jobs currently in production.

ID Date Description Status Events Notes
1121704015 Mon Jul 18 12:26:55 2005 J/Psi Au+Au Open   pgw Heavy
1127679226 Fri Sep 16 20:34:17 2005 Photon embedding for 62 GeV AuAu data for conversion analysis Open   pgw High Pt
1126917257 Sun Sep 25 16:13:46 2005 AMPT full chain Open   pgw EbyE
1130984157 Wed Nov 2 21:15:57 2005 pizero embedding in d+Au for EMCAL Open   pgw HighPt
1138743134 Tue Jan 31 16:32:14 2006 dE/dx RUN4 @ high pT Done   pgw Spectra
1139866250 Mon Feb 13 16:30:50 2006 Muon embedding RUN4 Test Sample   pgw Spectra
1139868572 Mon Feb 13 17:09:32 2006 pi+/-, kaon+/-, proton/pbar embedding to RUN5 Cu+Cu 62 GeV data open   pgw Spectra
1144865002 Wed Apr 12 14:03:22 2006 Lambda embedding for spectra (proton feeddown) Open   pgw Strangeness
1146151888 Thu Apr 27 11:31:28 2006 pi,K,p 200 GeV Cu+Cu Open   pgw Spectra
1146152319 Thu Apr 27 11:38:39 2006 K* for 62 GeV Cu+Cu Open   pgw Spectra
1146673520 Wed May 3 12:25:20 2006 K* for 200 GeV Cu+Cu Done   pgw Spectra
1148574792 Thu May 25 12:33:12 2006 Anti-alpha in 200 GeV AuAu Closed   pgw Spectra
1148586109 Thu May 25 15:41:49 2006 He3 in 200GeV AuAu Test Sample   pgw Spectra
1148586313 Thu May 25 15:45:13 2006 Deuteron in 200GeV AuAu Done   pgw Spectra
1154003633 Thu Jul 27 08:33:53 2006 J/Psi embedding for pp2006 Open   pgw Heavy
1154003721 Thu Jul 27 08:35:21 2006 Upsilon embedding for pp2006 Open   pgw Heavy
1154003879 Thu Jul 27 08:37:59 2006 electron embedding for Cu+Cu 2005 Test Sample   pgw Heavy
1154003931 Thu Jul 27 08:38:51 2006 pi0 embedding for Cu+Cu 2005 for heavy flavor group open   pgw Heavy
1154003958 Thu Jul 27 08:39:18 2006 gamma embedding for Cu+Cu 2005 for heavy flavor group open   pgw Heavy
1154004033 Thu Jul 27 08:40:33 2006 electron embedding for p+p 2005 for heavy flavor group (e-h correlations) Test Sample   pgw Heavy
1154004074 Thu Jul 27 08:41:14 2006 pi0 embedding for p+p 2005 for heavy flavor group (e-h correlations) Test Sample   pgw Heavy
1154626301 Thu Aug 3 13:31:41 2006 AntiXi Cu+Cu (P06ib) Done   pgw Strangeness
1154626418 Thu Aug 3 13:33:38 2006 Xi Au+Au (P05ic) Done   pgw Strangeness
1154626430 Thu Aug 3 13:33:50 2006 Omega Au+Au (P05ic) Done   pgw Strangeness
1156254135 Tue Aug 22 09:42:15 2006 Phi in pp for spin-alignment open   pgw Spectra
1163565625 Tue Nov 14 23:40:25 2006 muon CuCu 200 GeV open   pgw Spectra
1163627909 Wed Nov 15 16:58:29 2006 muon CuCu 62 GeV open   pgw Spectra
1163628205 Wed Nov 15 17:03:25 2006 phi CuCu 200 GeV Test Sample   pgw Spectra
1163628539 Wed Nov 15 17:08:59 2006 K* pp 200 GeV (year 2005) Open   pgw Spectra
1163628764 Wed Nov 15 17:12:44 2006 phi pp 200 GeV (year 2005) Open   pgw Spectra

 

runs for request 1154003879

min-bias run list from Anders.


6031103 6031104 6031105 6031106 6031113 6032001 6032003 6032004 6032005 6032011 6034006 6034007 6034008 6034009 6034014 6034015 6034016 6034017 6034108 6035005 6035006 6035007 6035009 6035010 6035011 6035012 6035013 6035014 6035015 6035016 6035026 6035027 6035028 6035030 6035032 6035036 6035108 6035111 6036012 6036014 6036016 6036017 6036019 6036020 6036021 6036022 6036024 6036025 6036028 6036036 6036039 6036043 6036044 6036045 6036098 6036102 6036103 6036104 6036105 6037009 6037010 6037013 6037014 6037015 6037016 6037017 6037018 6037019 6037025 6037026 6037028 6037029 6037030 6037031 6037033 6037039 6037040 6037046 6037047 6037048 6037049 6037050 6037053 6037054 6037071 6037073 6037075 6037077 6038085 6038088 6039033 6039034 6039040 6039132 6039134 6039135 6039136 6039138 6039139 6039141 6039142 6039143 6039144 6039145 6039154 6040001 6040003 6040004 6040007 6040008 6040009 6040026 6040043 6040044 6040045 6040048 6040050 6040051 6040052 6040054 6040055 6040056 6040057 6040058 6041014 6041015 6041020 6041021 6041022 6041023 6041025 6041027 6041028 6041031 6041034 6041035 6041036 6041062 6041063 6041064 6041065 6041066 6041091 6041092 6041093 6041097 6041099 6041102 6041103 6041105 6041118 6041120 6042003 6042006 6042008 6042009 6042010 6042012 6042014 6042015 6042016 6042018 6042024 6042046 6042047 6042048 6042049 6042052 6042054 6042055 6042057 6042059 6042060 6042101 6042105 6042109 6042110 6042111 6042112 6042113 6043010 6043011 6043014 6043017 6043019 6043020 6043021 6043022 6043026 6043027 6043039 6043043 6043045 6043054 6043057 6043058 6043060 6043063 6043080 6043082 6043085 6043090 6043094 6043095 6043097 6043098 6043100 6043101 6043111 6043112 6043113 6043114 6043115 6043117 6043118 6043119 6043120 6043121 6043122 6043123 6044001 6044010 6044011 6044012 6044015 6044016 6044020 6044024 6044025 6044026 6044027 6044028 6044044 6044045 6044046 6044047 6044049 6044050 6044053 6044054 6044055 6044058 6044059 6044075 6044079 6044081 6044083 6044084 6044085 6044086 6044088 6044089 6044090 6045008 6045026 6045027 6045029 6045033 6045042 6045070 6045072 6045075 6045076 6045077 6045078 6045079 6045080 6045081 6045082 6046004 6046005 6046014 6046016 6046017 6046018 6046022 6046028 6046035 6046037 6046038 6047017 6047020 6047022 6047025 6047026 6047037 6047039 6047040 6047044

Submit a new embedding request

Before submitting a new request, a double-check in the simulation request page is recommended, to see whether there are existing requests/data can be used. If not exist, one need to submit a new request. Please first read the 'Appendix A' in the embedding structure page for the rules to follow.
If the details of the embedding request has been thoroughly discussed within the PWG and hence approved by the PWG conveners. Please the PWG convener add a new request in the simulation request page and input all of the details there.

There are some key information that must be provided for each embedding request. (If you can not find some of the following items in the form, simply input it in the 'Simulation request description' box.)

Detailed information of the real data sample (to be embedded into).

  • Trigger sets name. for example, "AuAu_200_production_mid_2014", a full list of STAR real data trigger sets can be found in the data summary page.
  • file type. for example, "st_physics", "st_ht", "st_hlt", "st_mtd", "st_ssdmb". Please note that ONLY those "st_*_adc" files can be used for embedding production. Due to limitation of disk space, we usually sample 100K events (~200-500 daq files, depending on trigger and other event cuts), and this set of daq files will be embedded multiple times to reach the desired full statistics (say 1M).
  • Production tag. for example, "P15ic"
  • Run range with list of bad runs, or a list of good runs. for example, "15076101-15167014"
  • trigger IDs of the events to be embedded. for example, HT1 "450201, 450211"
  • vertex cut, and vertex selection method. for example, "|Vertex_z|<30cm", "Vr<2cm", "vertex is constrained by VPD vertex, |Vz-Vz_{VPD}|<3cm", "PicoVtxMode:PicoVtxVpdOrDefault, TpcVpdVzDiffCut:6" or "default highest ranked TPC vertex".

  • Other possible event cuts, for example, cut on refmult or grefmult, "refmult>250"
  • Each request can only have ONE type of dataset described above.

Details for simulation and reconstruction.

  • Particle type and decay mode (for unstable particle). for example, "Jpsi to di-muon"
  • pT range of input particle and the distribution. for example, "0-20GeV/c, flat", or "0-20GeV/c exponential"
  • pseudo rapidity or rapidity range (the distribution is flat), for example, "pseudo-rapidity eta, -1 to 1", or "rapidity, y, -1 to 1". Please do make clear it is "PSEUDO" rapidly or rapidity, as they are quite different quantities.
  • Number of MC particles per event. Usually "5% of refmult or grefmult" is recommended, one can also assign a fixed number, for example "5 particle per event" for pp collisions.
  • For event generator embedding request, like Pythia/HIJING/StarLight in zero-bias events, please provide the generator version at least. For example, "Pythia 8.1.62". The PWG embedding helper or PA's are fully responsible to tune-up the parameters for the generator in such embedding requests.
  • One can add special requirement for production chain in 'BFC tags' box, for example turn off IFT tracking in Sti.

Finally, please think carefully about the number of events! The computing resources (i.e. the CPU cores and storage) are limited ! 


It is acceptable to modify the details of the request afterwards, although it will be of great help if all above detailed information can be provided when a new request is submitted, in order to avoid the time waste in communications. If this is inevitable, please notify the Embedding Coordinator immediately if the details of a request is modified, especially when the request is opened.


Work Planned (OBSOLETE)

Based on:
  • An initial meeting held during QM06 (Chair: J.Lauret, L. Barnby, O, Baranikova, A. Rose)
  • Email exchange and notes from the meeting (From: J. Lauret, Date: 11/20/2006 22:36, Subject: Summary of our embedding meeting)
  • Further EMails from L. Barnby in embedding-hn (Date: 1/18/2007 15:12, Thread ID 84)
the following task list has been defined.

ID
Task
% Complete Duration Start Finish Assigned people
1
General QA consolidation
28% 109 days? Thu 11/16/06 Tue 4/17/07  
2            
3
Documentation
25% 37 days Mon 12/18/06 Tue 2/6/07  
4
Port old QA documentation to Drupal, define hierarchy
50% 4 wks Mon 12/18/06 Fri 1/12/07 Cristina Suarez[10%]
5
Add general documentation descriptive of the embedding purpose
0% 2 days Mon 1/15/07 Tue 1/16/07 Lee Barnby[10%],Andrew Rose[10%]
6
Add documentation as per the embedding procedure, diverse embedding
0% 2 days Mon 1/15/07 Tue 1/16/07 Lee Barnby[10%],Andrew Rose[10%]
7
Import PDSF documentation into Drupal
0% 1 wk Wed 1/17/07 Tue 1/23/07 Andrew Rose[10%]
8
Review and adjust documentation
0% 1 wk Wed 1/24/07 Tue 1/30/07 Olga Barranikova[10%],Andrew Rose[5%],Lee Barnby[5%]
9
Deliver documentation to collaboration for comments
0% 1 wk Wed 1/31/07 Tue 2/6/07 STAR Collaboration[10%]
10
Drop all old documentation, adjust link (redirect)
0% 1 day Wed 1/31/07 Wed 1/31/07 Andrew Rose[15%],Jerome Lauret[15%]
11            
12
Line of authority, base conventions
84% 52 days Thu 11/16/06 Fri 1/26/07  
13
Meeting with key personnel
100% 1 day Thu 11/16/06 Thu 11/16/06 Jerome Lauret[10%],Olga Barranikova[10%],Andrew Rose[10%],Lee Barnby[10%]
14
Define responsibilities and scope of diverse individual in the embedding team
100% 1 mon Mon 12/4/06 Fri 12/29/06 Jerome Lauret[15%],Olga Barranikova[6%]
15
Define file name convention, document final proposal
50% 2 wks Mon 1/15/07 Fri 1/26/07 Jerome Lauret[6%],Lee Barnby[6%],Lidia Didenko[6%],Andrew Rose[6%]
16            
17
Collaborative work
45% 60 days Mon 1/22/07 Fri 4/13/07  
18
General Cataloguing issues
0% 9 days Mon 1/29/07 Thu 2/8/07  
19
Test Catalog registration, adjust as necessary
0% 4 days Mon 1/29/07 Thu 2/1/07 Lidia Didenko[20%],Jerome Lauret[20%]
20
Extend Spider/Indexer to include embedding registration
0% 1 wk Fri 2/2/07 Thu 2/8/07 Jerome Lauret[10%]
21
Bug tracking, mailing lists and other tools
69% 60 days Mon 1/22/07 Fri 4/13/07  
22
Re-enable embedding list, establish focus comunication at PWG level and user level
75% 3 mons Mon 1/22/07 Fri 4/13/07 Jerome Lauret[10%]
23
Establish embedding RT system queue
0% 1 day Tue 1/23/07 Tue 1/23/07 Jerome Lauret[5%]
24
Exercise embedding RT queue, adjust requirement
0% 4 days Wed 1/24/07 Mon 1/29/07 Andrew Rose[10%]
25
Establish data transfer scheme to a BNL disk pool
0% 22 days Mon 1/22/07 Tue 2/20/07  
26
Define requirements, general problems and issues
0% 1 wk Mon 1/22/07 Fri 1/26/07  
27
Add data pool mechanism at BNL, transfer with any method
0% 1 wk Mon 1/29/07 Fri 2/2/07  
28
Establish security schem, HPSS auto-synching
0% 1 wk Mon 2/5/07 Fri 2/9/07  
29
Test on one or more sites (non-PDSF)
0% 1 wk Mon 2/12/07 Fri 2/16/07  
30
Integrate to all participating sites
0% 1 wk Mon 2/12/07 Fri 2/16/07  
31
Document data transfer schemeand procedure
0% 2 days Mon 2/19/07 Tue 2/20/07  
32            
33
CVS check-in and cleanup
4% 17 days? Mon 1/22/07 Tue 2/13/07  
34
Initial setup, existing framework
0% 17 days Mon 1/22/07 Tue 2/13/07  
35
Define proper CVS location for perl, libs, macros
0% 1 day Mon 1/22/07 Mon 1/22/07 Jerome Lauret[10%],Andrew Rose[10%],Lee Barnby[10%]
36
Add existing QA macros to CVS
0% 1 day Tue 1/23/07 Tue 1/23/07 Andrew Rose[20%]
37
Checkout and test on +1 site (non-PDSF), adjust as necessary
0% 1 wk Wed 1/24/07 Tue 1/30/07 Lee Barnby[10%]
38
Bootstrap on +1 site / remove ALL site specifics references
0% 1 wk Wed 1/31/07 Tue 2/6/07 Cristina Suarez[10%]
39
Commit to CVS, verify new scripts on all sites, final adjustments
0% 1 wk Wed 2/7/07 Tue 2/13/07 Cristina Suarez[10%],Andrew Rose[10%],Lee Barnby[10%]
40
QA and nightly tests
17% 7 days? Mon 1/22/07 Tue 1/30/07  
41
Establish a QA area in CVS
100% 1 day? Mon 1/22/07 Mon 1/22/07  
42
Check existing QA suite
0% 1 wk Wed 1/24/07 Tue 1/30/07  
43            
44
Development
0% 62 days Mon 1/22/07 Tue 4/17/07  
45
General QA consolidation
0% 10 days Wed 1/31/07 Tue 2/13/07  
46
Gather feedback from PWG, add QA tests relevant to Physics topics
0% 2 wks Wed 1/31/07 Tue 2/13/07  
47
Establish nightly test framework at BNL for embedding
0% 1 wk Wed 1/31/07 Tue 2/6/07  
48
General improvements
0% 35 days Mon 1/22/07 Fri 3/9/07  
49
Requirements study for an embedding request interface
0% 2 wks Mon 1/29/07 Fri 2/9/07 Andrew Rose[10%],Jerome Lauret[10%]
50
Develop new embedding request form compatible with Drupal module
0% 4 wks Mon 2/12/07 Fri 3/9/07 Andrew Rose[10%]
51
Test new interface, import old tasks (historical purposes)
0% 5 days Mon 1/22/07 Fri 1/26/07 Andrew Rose[10%],Cristina Suarez[10%]
52
Distributed Computing
0% 20 days Wed 2/14/07 Tue 3/13/07  
53
Use SUMS framework to submit embedding, establish first XML
0% 1 wk Wed 2/14/07 Tue 2/20/07 Lee Barnby[10%]
54
Test on one site
0% 1 wk Wed 2/21/07 Tue 2/27/07 Lee Barnby[10%]
55
Test on all sites, adjust as necessary
0% 2 wks Wed 2/28/07 Tue 3/13/07 Cristina Suarez[10%],Andrew Rose[10%],Lee Barnby[10%]
56
Gridfication
0% 25 days Wed 3/14/07 Tue 4/17/07  
57
Test XML using Grid policy (one site)
0% 1 wk Wed 3/14/07 Tue 3/20/07  
58
Establish test of data transfer method, GSI enabled HPSS access possible
0% 1 wk Wed 3/21/07 Tue 3/27/07  
59
Regression and stress test on one site
0% 1 wk Wed 3/28/07 Tue 4/3/07  
60
Test on +1 site, infrastructure consolidation
0% 2 wks Wed 4/4/07 Tue 4/17/07  
61            
62
Embedding operation
25% 261 days? Mon 1/1/07 Mon 12/31/07  
63
PDSF support
50% 261 days? Mon 1/1/07 Mon 12/31/07 Andrew Rose[10%]
64
BHAM support
10% 261 days? Mon 1/1/07 Mon 12/31/07 Lee Barnby[10%]
65
UIC Support including QA
15% 261 days? Mon 1/1/07 Mon 12/31/07 Olga Barranikova[5%],Cristina Suarez[10%]

Chain check, momentum issues

The below plots were the basis for the second Embedding focus meeting 2 as a follow of the Embedding focus meeting.

Olga versus Victor plots - Are they consistent?

Olga Eloss proximity
Eloss proximity from Olga
Olga Eloss idtruth
Eloss idtruth from Olga
Victor's primaries P diff
Victor's P diff (proximity)
Victor's idtruth P diff
Victor's P diff (idtruth)

idtruth versus proximity

Victor proximity
Victor's proximity plot
Victor idtruth
Victor's idtruth

bfcMixer.C Reshape

b>Date: Wednesday, 18 April 2007
Time: 12:21:45
Topic: Embedding Reshape

18 April 2007 12:21:56

Talked to Yuri on Monday (16th)

He would like 3 things worked on.

1. Integration of MC generation part into bfcMixer.C

Basically all kumac commands can be done in macro using gstar.

These would become part of "chain one"

Also need to read in a tag or MuDst file to find vertex to use for generating particles.

Can probably see how this works from bfc.C itself as bfc.C(1) creates particles and runs them through reconstruction.

- actually I could not it is inside bfc.C or StBFChain because it is part of St_geant_Maker

2. Change Hit Mover so that it does not move hits derived from MC info (based on ID truth %age)

3. [I forgot what 3 was!]

Rough sketch of chain modifications for #1

Current bfcMixer

(StChain)Chain

(StBFChain)daqChain<--daq file

(StBFChain simChain<--fz file

                                <---.dat file with vertex positions        

                        MixerMaker

(StBFChain)recoChain

New bfcMixer

(StChain)Chain

(

StBFChain)daqChain<--daq file

                (StBFChain)simChain

                |

                Geant-?-SetGeantMaker<--tags file

                

                MixerMaker

(StBFChain)recoChain

Break down into sub-tasks.

a) Run bfcMixer.C on a daq file with an associated fz and data file (to check that it works!)

b) Ignore fz file and generate MC particle (any!) on the fly

c) reading from tags file generate MC particles at desired vertex & with desired mult.

d) tidy up specify parameter interface (p distn, geant ID etc.)

Embedding Procedures

Overview




This document lists the procedures used for requesting embedding, running embedding jobs, and retrieving data. Please note that some steps require privileged accounts.


Embedding Documentation

Overview



The purpose of embedding is to provide physicists with a known; Monte Carlo tracks, where the kinematics and particle type is known exactly, are introduced into the realistic environment seen in the analysis - a real data event. How reconstruction preforms on these "standard candle" tracks provides a baseline which can be used to correct for acceptance and effciency effects in various analyses.

In STAR, embedding is achieved with a set of software tools - Monte Carlo simulation software, as well as the tools for real data event reconstruction - accessed through a suite of scripts. These documents attempt to provide an introduction to the scripts and their use, but the STAR collaborator is referred to the separate web pages maintained for Simulations and Reconstruction for deeper questions of the processes involved in those respective tasks.

Please note, the general procedure for embedding is:
  • The Physics Working Group Convenor submits an embedding request. The request will be assigned a request number and priority by the Analysis Coordinator, see this page for more information.
  • The Embedding Coordinator will coordinate the distribution of embedding requests. Users who wish to run their own embedding are encouraged to do so - but it must be verified with the Embedding Coordinator.
  • The Embedding Coordinator is responsible for the QA of all embedding requests. When the Embedding Coordinator has verified that the test sample produced is acceptable, full production is authorized.


Obsolete documentations

Embedding Production Setup

This page describes how to set up embedding production. This procedure needs to be followed for any set of daq files/production version that requires embedding. Since this typically involves hacking the reconstruction chain, it is not advised that the typical STAR PA attempt this step. Please coordinate with a local embedding coordinator, and the overal Embedding coordinator (Olga).
Note: The documentation here is very terse; it will be enriched as the documentation as a whole is iterated on. Patience is appreciated.

Get daq files from RCF.

Grab a set of daq files from RCF which cover the lifetime of the run, the luminosity range experienced, and the conditions for the production.

Rerun standard production but without corrections.

bfc.C macros are located under ~starofl/bfc. Edit the submit.[Production] script to point to the daq files loaded (as above).

Put tags files on disk.

The results of the previous jobs will be .tags.root files located on HPSS. Retrieve the files, set a pointer for the tags files in the Production-specific directory under ~starofl/embedding.


Now you're ready to start production.

Embedding Setup Off-site

Introduction

The purpose of this document is to describe step-by-step the setting up of embedding infrastructure on a remote site i.e. not at it's current home which is PDSF. It is based on the experience of setting up embedding at Birmingham's NP cluster (Bham). I will try to maintain a distinction between steps which are necessary in general and those which were specific to porting things to Bham. It should also be a useful guide for those wanting to run embedding at PDSF and needing to copy the relevant files into a suitable directory structure.

Pre-requisites

Before trying to set up embedding on a remote site you should have:
  • a working local installation of the STAR library in which you are interested (or be satisified with your AFS-based library performance).
  • a working mirror of the star database (or be satisfied with your connection to the BNL hosted db).
If these two things are working correctly you will be able to process a daq file with the usual bfc.C macro. Check that you can do this and do not proceed further if this is not the case as you will be wasting your time. You can find the correct bfc.C options to use with a particular daq file and software release combination here.

Collect scripts

The scripts are currently housed at PDSF in the 'starofl' account area. At the time of writing (and the time at which I set up embedding in Bham) they are not archived in CVS. The suggested way to collect them is to copy them into a directory in your own PDSF home account then tar and export it for installation on your local cluster. The top directory for embedding is /u/starofl/embedding . Under this directory there are several subdirectories of interest.
  • Those named after each production, e.g. P06ib which contain mixer macro and perl scripts
  • Common which contains further subdirectories lists and csh and a submission perl script
  • GSTAR which contains the kumac for running the simulation
Therefore you need to create a replica of this directory tree. From your home directory e.g. /u/user do
mkdir embedding
cd embedding
mkdir Common
mkdir Common/lists
mkdir Common/csh
mkdir GSTAR
mkdir P06ib
mkdir P06ib/setup

Now it needs populating with the relevant files. In the following /u/user/embedding as an example of your new embedding directory in your user home directory.

cd /u/user/embedding
cp /u/starofl/embedding/getVerticesFromTags_v4.C .
cp -R /u/starofl/embedding/P06ib/EmbeddingLib_v4_noFTPC/ P06ib/
cp /u/starofl/embedding/P06ib/Embedding_sge_noFTPC.pl P06ib/
cp /u/starofl/embedding/P06ib/bfcMixer_v4_noFTPC.C P06ib/
cp /u/starofl/embedding/P06ib/submit.starofl.pl P06ib/submit.user.pl
cp /u/starofl/embedding/P06ib/setup/Piminus_101_spectra.setup P06ib/setup/
cp /u/starofl/embedding/GSTAR/phasespace_P06ib_revfullfield.kumac GSTAR/
cp /u/starofl/embedding/GSTAR/phasespace_P06ib_fullfield.kumac GSTAR/
cp /u/starofl/embedding/Common/submit_sge.pl Common/


You now have all the files need to run embedding. There are further links to make but as you are going to export them to your own cluster you need to make the links afterwards.

Alternatively you can run embedding on PDSF from your home directory. There are a number of change to make first though because the various perl scripts have some paths relating to the starofl account inside them.

For those planning to export to a remote site you should tar and/or scp the data. I would recommend tar so that you can have the original package preserved in case something goes wrong. E.g.

tar -cvf embedding.tar embedding/
scp embedding.tar remoteuser@mycluster.blah.blah:/home/remoteuser

Obviously this step is unnecessary if you intend to run from your PDSF account although you may still want to create a tar file so that you can undo any changes which are wrong.

Login to your remote cluster and extract the archive. E.g
cd /home/remoteuser
tar -xvf embedding.tar

Script changes

The most obvious thing you will find are a number of places inside the perl scripts where the path or location for other scripts appears in the code. These must be changed accordingly.

P06ib/Embedding_sge_noFTPC.pl
  1. my $code_dir = "/home/starofl/embedding/P06ib";
    changes to e.g.
    my $code_dir = "/home/remoteuser/embedding/P06ib";
     
  2. use lib "/home/starofl/embedding/P06ib/EmbeddingLib_v4_noFTPC";
    changes to e.g.
    use lib "/home/remoteuser/embedding/P06ib/EmbeddingLib_v4_noFTPC";
  3. my $kumac_name = "/home/starofl/embedding/GSTAR/";
    changes to e.g.
    my $kumac_name = "/home/remoteuser/embedding/GSTAR/";
  4. $DaqDir =~ /starprod\/daq\/\d+\/(\w+)\/(\w+)/; my $daqField = $2;
    changes to e.g.
    $DaqDir =~ /star\/(\w+)\/daq\/\d+\/(\w+)\/(\w+)/; my $daqField = $3;
P06ib/EmbeddingLib_v4_noFTPC/Process_object.pm
  1. my $macro_dir = "/u/starofl/embedding";
    changes to e.g.
    my $macro_dir = "/home/lbarnby/embedding";
  2. my $header_string = "#! /usr/local/bin/tcsh\n".
    changes to e.g.
    my $header_string = "#! /bin/tcsh\n".

    This is because the location of tcsh was different and probably will be for you too.
Common/submit_sge.pl
  1.  $daqDir =~ /\/(\w+)\/starprod\/daq\/\d+\/(\w+)\/(\w+)/;
    changes to e.g.
    $daqDir =~ /\/star\/(\w+)\/daq\/\d+\/(\w+)\/(\w+)/;

    Change relates to parsing the name of the directory with daq files in to extract the 'data vault' and 'magnetic field' which form part of job name and are used by Embedding_sge_noFTPC.pl (This may not make much sense right now and needs the detailed docs on each component. It is actually just a way to pass a file list with the same basename as the job). In the original script the path to the data is something like /dante3/starprod/daq/2005/cuProductionMinBias/FullField whereas on Bham cluster it is /star/data1/daq/2005/cuProductionMinBias/FullField and thus the pattern match in perl has to change in order to extract the same information. If you have a choice then choose your directory names with care!
  2. print QSUB "\$\!/bin/sh\n";
    changes to e.g.
    print QSUB "#\!/bin/sh\n";

    Change relates to the line printing the job submission shell script that this perl script writes and submits. The first line had to be changed such that it can correctly be identified as a sh script. I am not sure how original can ever have worked?
  3. print QSUB "-M $opt{u} -m e -N $jobName -o $logDir -j y\n";
    changes to e.g.
    print QSUB "-M $opt{u} -m e -N $jobName -o $logDir -j y -cwd -V -q embedding.q\n";

    This line prints part of the job submission script where the options for the job are specified. In SGE the job options can be in the file and not just on the command line. The extra options for Bham relate to our SGE setup. The -q option provides the name of the queue to use, otherwise it uses the default which I did not want in this case. The other extra options are to make the environment and working diretory correct as they were not the default for us. This is very specific to each cluster. If your cluster does not have SGE then I imagine extensive changes to the part writing the job submission script would be necessary. The scripts use the ability of SGE to have job arrays of similar jobs so you would have to emulate that somehow.

No significant changes required for:
  • getVerticesFromTags_v4.C - none
  • GSTAR/phasespace_P06ib_fullfield.kumac, GSTAR/phasespace_P06ib_fullfield.kumac - actually there are changes but they only relate to redefining particle decay modes for (anti-)Ξ and (anti-)Ω to go 100% to charged modes of interest. This is only relevant for strangeness group
  • P06ib/bfcMixer_v4_noFTPC.C - checked carefully that chain3->SetFlags line actually sets the same flags since Andrew and I had to change the same flags e.g. add GeantOut option after I made orginal copy
  • P06ib/EmbeddingLib_v4_noFTPC/Chain_object.pm - none
  • P06ib/EmbeddingLib_v4_noFTPC/EmbeddingUtilities.pm - there are lines where you may have to add the run numbers of the daq files which you are using so that they are recognised as either full field or reversed full field. In this example (Cu+Cu embedding in P06ib) the lines begin
    my @cuFF
    and
    my @cuRFF
    . This is also something that Andrew and I both changed after I made the original copy.
  • P06ib/submit.user.pl - changes here relate to setup that you want to run and not to the cluster or directory you are using i.e. which setup file to use, what daq directories to use and any pattern match on the file names (usually for testing purposes to avoid filling the cluster with useless jobs) although you probably want to change the
    my $email = 
    line!
  • P06ib/setup/Piminus_101_spectra.setup - any changes here relate to the simulation parameters of the job that you want to do and not to the cluster or directory you are using

Create links

A number of links are required. For example in the /u/starofl/embedding/P06ib there are the following links:
  • daq_dir_2005_cuPMBFF -> /dante3/starprod/daq/2005/cuProductionMinBias/FullField
  • daq_dir_2005_cuPMBRFF -> /dante3/starprod/daq/2005/cuProductionMinBias/ReversedFullField
  • daq_dir_2005_cuPMBHTFF -> /eliza5/starprod/daq/2005/cucuProductionHT/FullField/
  • daq_dir_2005_cuPMBHTRFF -> /eliza5/starprod/daq/2005/cucuProductionHT/ReversedFullField
  • tags_dir_cu_2005 -> /dante3/starprod/tags/P06ib/2005
  • tags_dir_cuHT_2005 -> /eliza5/starprod/embedding/tags/P06ib
  • data -> /eliza12/starprod/embedding/data
  • lists ->../Common/lists
  • csh-> ../Common/csh
  • LOG-> ../Common/LOG
You will therefore need similar links to where you store your daq files (and associated tags files) and where you want the output data to go.

That is it! Some things will probably need to be adapted to your circumstances but it should give you a good idea of what to do

Author: Lee Barnby, University of Birmingham (using starembed account)


Modified: A. Rose, Lawrence Berkeley National Laboratory (using starembed account)


Modified Birmingham Files

Upload of modified embedding infrastructure files used on Birmingham NP cluster for Cu+Cu for (anti-)Λ and K0S embedding request.

Production Management

1) Usually embedding jobs are run in "HPSS" mode so the files end up in HPSS (via FTP). To transfer them from HPSS to disk copy the perl script ~starofl/hjort/getEmbed.pl and modify as needed. This script does at least two things that are not possible with, e.g., a command line hsi command: it only gets the files needed (usually the .geant and .event files) and it changes the permissions after the transfers. Note that if you do the transfers shortly after running the jobs the files will probably still be on the HPSS disk cache and transfers will be much fast than getting the files from tapes.

2) To clean up old embedding files make your own copy of ~starofl/hjort/embedAge.pl and use as needed. Note that $accThresh determines the maximum access time in days of files that will not be deleted.

Running Embedding

This page describes how to run embedding jobs once the daq files and tags files are in place (see other page about embedding production setup).

Basics:

Embedding code is located in production specific directories: ~starofl/embedding/P0xxx. The basic job submission template is typically called submit.starofl.pl in that directory.
Jobs are usually run by user starofl but personal accounts with group starprod membership will work, too (but test first as the group starprod write permissions typically are not in place by default).
The script to submit a set of jobs is submit.[user].pl. The script should be modified to submit an embedding set from the the configuration file
~starofl/embedding/[Production]/setup/[Particle]_[set]_[ID].setup
where
[Particle] is the particle type submitted (Piminus for GEANTID=9, as set inside file)
[set] is the file set submitted (more on this later)
[ID] is the embedding request number


Test procedure:

The best way to test a particular job configuration is to run a single job in "DISK" mode (by selecting a specific daq file in your submission). In this mode all of the intermediate files, scripts, logs, etc., are saved on disk. The location will be under the "data" link in the working directory. You can then go and figure out which script failed, hack as necessary and and try to make things work...

Details:


Notes

Overview



The document is intended as a forum for embedding group members to share information and notes.

LPP group (Dubna) activities

This page is intended to provide embedding progress for soft-photon study conducted by PPL (Dubna, JINR) group in Russia.
    Requested embedding is based on request ID # 1103209240 and modified to:
  • provide larger statistics for reco efficiency calculation
  • extend acceptance parameters

AuAu200 photon embedding details

    Request details:

  • Dataset and production: AuAu200, P05ic
  • Embedded particles and multiplicity: 1000 Photons per event, total 500 kEvents
  • zVertex = +-30
  • Pt: 0.020 - 0.160 GeV
  • eta: +-1.2
  • full geant reconstruction
    Embedding Files on Disk at PDSF:

  • Photon_201...215_spectra: /eliza5/starprod/embedding/P05ic/
  • Photon_301...315_spectra: /eliza5/starprod/embedding/P05ic/
  • Photon_401...415_spectra: /eliza7/starprod/embedding/P05ic/
  • Photon_501...504_spectra: /eliza5/starprod/embedding/P05ic/
  • Photon_505...515_spectra: /eliza7/starprod/embedding/P05ic/
  • Photon_601...615_spectra: /eliza7/starprod/embedding/P05ic/
  • Photon_701...715_spectra: /eliza12/starprod/embedding/P05ic/
  • Photon_802...811,817,818_spectra: /eliza12/starprod/embedding/P05ic/
    Running Jobs status:
    jobs QA and checking if this statistic is enough

dAu photon embedding details

    Request details:
  • Dataset and production: dAu200, P04if
  • Embedded particles and multiplicity: 1000 Photons per event, total 500 kEvents
  • zVertex = +-50
  • Pt: 0.020 - 0.160 GeV
  • eta: +-1.2
  • full geant reconstruction
    Running Jobs status: have not been started yet

QA Status (OBSOLETE)

The full list of STAR embedding requests (Since August, 2010):
http://drupal.star.bnl.gov/STAR/starsimrequest
The QA status of each request can be viewed in its history.

The information below are only valid for OLD embedding requests.

This document is intended to provide all the information available for each production, starting for the last or current production.

P06ib

QA Plots Phi(Feb 2009)

QA P06ib (Phi->K +K)

 

This is the QA for P06ib (Phi- > KK). reconstruction on Global Tracks (Kaons)

1. dEdx

Reconstruction on Kaon Daugthers. Plot shows MOntecarlo tracks and Ghost Tracsks.


  


 

2. DCA Distributions

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots. (MonteCarlo and MuDst) (MuDst taken from pdsf > /eliza12/starprod/reco/cuProductionMinBias/ReversedFullField/P06ib/2005/022/st_physics_adc_6022048_raw*.MuDst.root)

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 


 

3. NFit Distributions

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions. (MonteCarlo and MuDst)

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();


 

 

4. Delta Vertex

 

The following are the Delta Vertex ( Vertex Reconstructed - Vertex Embedded) plot for the 3 diiferent coordinates (x, y and z) (Cuts of vz =30 cm , NFitCut= 25 are applied)

 

5. Z Vertex and X vs Y vertex

 


 

 

 

6. Global Variables : Phi and  Rapidity

 

 

7. Pt

 Embedded Phi meson with flat pt (black)and Reconstructed Kaon Daugther (red).

8. Randomness Plots

The following plots, are to check the randomness of the input Monte Carlo (MC) tracks.

 

 

QA plots Rho (February 16 2009)

QA P06ib (Rho->pi+pi)

 

This is the QA for P06ib (Rho- > pi+pi). reconstruction on Global Tracks (pions)

1. dEdx

 Reconstruction on Pion Daugthers.


  

 

2. DCA Distributions

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 


2b. Compared with MuDst

 

3. NFit Distributions

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();


 

3b. Reconstructed compared with MuDsts

 

 

4. Delta Vertex

 

The following are the Delta Vertex ( Vertex Reconstructed - Vertex Embedded) plot for the 3 diiferent coordinates (x, y and z) (Cuts of vz =30 cm , NFitCut= 25 are applied)

 

5. Z Vertex and X vs Y vertex

 

 

 

 

6. Global Variables : Phi and  Rapidity

 

 

7. Pt

 Embedded Rho meson with flat pt (black)and Recosntructed Pion (red).

8. Randomness Plots

The following plots, are to check the randomness of the input Monte Carlo (MC) tracks.

 

 

QA plots Rho (October 21 2008)

Some QA plots for Rho:

MiniDst files are at PDSF under the path /eliza13/starprod/embedding/p06ib/MiniDst/rho_101/*.minimc.root

MuDst files are at PDSF under /eliza13/starprod/embedding/P06ib/MuDst/10*/*.MuDst.root Reconstruction had been done on PionPlus.

DCA and Nfit Distributions had been scaled by the Integral in different pt ranges

QAPlots_D0

Some QA Plots for D0 located under the path :

/eliza12/starprod/embedding/P06ib/D0_001_1216876386/*

/eliza12/starprod/embedding/P06ib/D0_002_1216876386/ -> Directory empty

Global pairs are used as reconstructed tracks. SOme quality tractst plotiing level were :

Vz Cut 30 cm ; 

NfitCut : 25,

Ncommonhits : 10 ;

maxDca :1 cm ;  Assuming D0- >pi + pi

P05id


P05id Cu+Cu Embedding

Hit level check-up : At the Hit level the results look in good agreement.
  • Missing/Dead Areas (PiMinus): The next graphs show dead sectors  for embeded data and real data as well.
  • Hits-P05id_200cucu-PiMinus_hitsXYeast_p2.gif
    Hits-P05id_200cucu-PiMinus_hitsXYwest_p2.gif
  • Missing/Dead Areas (PiPlus)
  • Hits-P05id_200cucu-PiPlus_hitsXYeast_p2.gif
    Hits-P05id_200cucu-PiPlus_hitsXYwest_p2.gif

  • Track Residuals PiMinus

  • Hits-P05id_200cucu-PiMinus_longResMean_dipAng_H_p2.gif
     Hits-P05id_200cucu-PiMinus_longResMean_dipAng_p2.gif
     Hits-P05id_200cucu-PiMinus_longResMean_z_H_p2.gif
     Hits-P05id_200cucu-PiMinus_longResMean_z_p2.gif
     Hits-P05id_200cucu-PiMinus_longRes_dipAng_H_p2.gif
     Hits-P05id_200cucu-PiMinus_longRes_dipAng_p2.gif
     Hits-P05id_200cucu-PiMinus_longRes_z_H_p2.gif
     Hits-P05id_200cucu-PiMinus_longRes_z_p2.gif
     Hits-P05id_200cucu-PiMinus_transRes_crosAng_H_p2.gif
    Hits-P05id_200cucu-PiMinus_transRes_crosAng_p2.gif
     Hits-P05id_200cucu-PiMinus_transRes_z_H_p2.gif
    Hits-P05id_200cucu-PiMinus_transRes_z_p2.gif

  • Track Residuals PiPlus

  •  Hits-P05id_200cucu-PiPlus_longResMean_dipAng_H_p2.gif
     Hits-P05id_200cucu-PiPlus_longResMean_dipAng_p2.gif
     Hits-P05id_200cucu-PiPlus_longResMean_z_H_p2.gif
     Hits-P05id_200cucu-PiPlus_longResMean_z_p2.gif
     Hits-P05id_200cucu-PiPlus_longRes_dipAng_H_p2.gif
     Hits-P05id_200cucu-PiPlus_longRes_dipAng_p2.gif
     Hits-P05id_200cucu-PiPlus_longRes_z_H_p2.gif
     Hits-P05id_200cucu-PiPlus_longRes_z_p2.gif
     Hits-P05id_200cucu-PiPlus_transRes_crosAng_H_p2.gif
     Hits-P05id_200cucu-PiPlus_transRes_crosAng_p2.gif
     Hits-P05id_200cucu-PiPlus_transRes_z_H_p2.gif
     Hits-P05id_200cucu-PiPlus_transRes_z_p2.gif
  • dEdx Comparisons

  • The following are results  of dEdx calibration from embedding  for Pi Minus. Graphs 1 and 2 are Dedx vs Momentum  grapsh where Green dots are the MonteCarlo Tracks reconstructed from Embedding and  Black dots  are Data. In Graph Number 2, dots are Data and solid  lines show  Bichsel parametrisation with a factor of 1/2 offset. In the Last Graph a  projection on dEdx axis is done and a MIP of 1.26 and 1.18 are shown.

    Dedx-P05id_cucu-dedx_emb_data_rec_piminus.gif

    Dedx-P05id_cucu-dedx_piminus.gif
     Dedx-P05id_cucu-dedx_fit.gif 

P08ic -Jpsi(Test)

QA P08ic J/Psi -> ee+

This is the QA for P08id (jPsi - > ee). Reconstructin on Global Tracks and just Electrons (Positrons).

 

1. dEdx

 


 

2. DCA Distributions

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

3. NFit Distributions

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();


 

 

4. Delta Vertex

The following are the Delta Vertex ( Vertex Reconstructed - Vertex Embedded) plot for the 3 diiferent coordinates (x, y and z)

 

5. Z Vertex and X vs Y vertex

 

 

 

 

6. Global Variables : Phi and  Rapidity

 

 

7. Pt

 Embedded J/Psi with flat pt (black)and Recosntructed Electrons (red).

8. Randomness Plots

The following plots, are to check the randomness of the input Monte Carlo (MC) tracks.

 

 

 

 

 

 

 

P08id (AXi -> RecoPiPlus)

AXi-> Lamba + Pion +  ->P + Pion - + Pion +

(03 08 2009)

 

1. Dedx

 

 

 

2.Dca

 

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

3. Nfit

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

4. Delta Vertex

 

5. Z Vertex and X vs Y vertex

 

 

6. Global Variables : Phi and  Rapidity

 

 

 

7. pt

 

 

 

8. Randomness

 

 

 

P08id (Omega -> RecoPiMinus)

Omega-> Lamba + K -  ->  P + Pion - + K -

(03 08 2009)

 

1. Dedx

  

Reconstruction on pion Minus and Proton  Daugthers. 2 different plots are shown just for the sake of completenees.... Reconsructing on Kaon had very few statistics

 

Reco PionMinusReco Proton
 

 

 

 

2.Dca

 

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

*.Reconstructing on Pion

 

 

 *. Reconstructing on Proton

 

3. Nfit

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

*. Reconstructing Pion

 

 

 

*. Reconstructing Proton

 

 

4. Delta Vertex

 

 When reconstructed in Pion Minus and Proton it turns out to have the same ditreibutions so I just  posted one of them


 

5. Z Vertex and X vs Y vertex

 

 

 

6. Global Variables : Phi and  Rapidity

 

Reco PionReco Kaon
 
 

 

 

7. pt


 

 

8. Randomness

 

 

 

P08id (phi ->KK) (March 05 2009)

 

QA Phi->KK (March 05 2009)

 

1. Dedx

 Reconstruction on Kaon Daugthers. 2 different plots are shown just for the sake of completenees....

 

 

2.Dca

 

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

3. Nfit

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

4. Delta Vertex

 

5. Z Vertex and X vs Y vertex

 

 

6. Global Variables : Phi and  Rapidity

 

 

 

 

7. pt

 


8. Randomness

 

 

 

P08id (phi ->KK)

QA P08id (Phi->KK)

 

This is the QA for P08id (phi - > KK). econstructin on Global Tracks and just Kaons. Macro from Xianglei used (I found the QA macro very  familiar). scale factor of 1.38 applied.

1. dEdx

 Reconstruction on Kaon Daugthers. 2 different plots are shown just to see how Montecarlo looks on top of the Ghost Tracks

 

 

2. DCA Distributions

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

3. NFit Distributions

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

4. Delta Vertex

The following are the Delta Vertex ( Vertex Reconstructed - Vertex Embedded) plot for the 3 diiferent coordinates (x, y and z)

 

5. Z Vertex and X vs Y vertex

 

 

 

6. Global Variables : Phi and  Rapidity

 

7. Pt

 Embedded Phi meson with flat pt (black)and Recosntructed Kaons (red).

8. Randomness Plots

The following plots, are to check the randomness of the input Monte Carlo (MC) tracks.

 

 

 

 

P08id(ALambda -> P, Pion)

 

QA ALambda->P, pi (03 08 2009)

 

1. Dedx

 Reconstruction on Proton and Pion Daugthers. 2 different plots are shown just for the sake of completenees....

 

Reco ProtonReco Pion

 

 

 

2.Dca

 

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

*.Reconstructing on Proton

 

 *. Reconstructing on Pion

 

3. Nfit

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

*. Reconstructing Proton

 

 

*. Reconstructing Pion

 

4. Delta Vertex

 

 When reconstructed in Proton and pions it turns out to have the same ditreibutions so I just  posted one of them

 

5. Z Vertex and X vs Y vertex

 

 

 

6. Global Variables : Phi and  Rapidity

 

Reco ProtonReco Pion

 

 

7. pt


 

 

8. Randomness

 

 

 

 

 

P08id(Xi -> Reco(PiMinus)

 Xi-> Lamba + Pion -  ->P + Pion - + Pion -

(03 08 2009)

 

1. Dedx

 Reconstruction on PI Minus

 

2.Dca

 

An original 3D histogram had been created  and filled with pT, Eta and DCA as the 3 coordinates. Projection on PtBins and EtaBins had been made to create this "matrix" of plots.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

 

3. Nfit

Similarly An Original 3D Histogram had been created with Pt, Eta and Nfit as coordinates. Respective projections had been made  in the same pT  and Eta Bins as the DCa distributions.

Pt Bin array  used : { 0.5, 0.6, 0.8, 1.0} (moves down) and

Eta Bin array : {0.2, 0.5, 0.8, 1.0} (moves to the right)

For the Error bars, i used the option hist->Sumw2();

 

 

4. Delta Vertex

5. Z Vertex and X vs Y vertex

 

 

 

 

6. Global Variables : Phi and  Rapidity

 

 

 

7. pt

 

 

8. Randomness

 

 

 

 

 

Phi->KK(Mar 12)

 

Please find the QA plots here

http://www.star.bnl.gov/protected/lfspectra/xpzhang/talks/phikkembedQA.pdf
 

The data looks good.

Reconstructed phi meson has small rapidity dependence.

 

Yuri_Test_PionMinus_032009

QA PionMinus

 

 

 

 

 

 

 

P04if

    Hit level check-up:
  • Missing/Dead Areas (PiMinus): The next graphs show dead sectors for embeded data and real data as well.
  • Hits-P04if-PiMinus_hitsXYeast_p2.gif

    Hits-P04if-PiMinus_hitsXYwest_p2.gif
  • Missing/Dead Areas (PiPlus)
  • Hits-P04if-PiPlus_hitsXYeast_p2.gif
    Hits-P04if-PiPlus_hitsXYwest_p2.gif

  • Track Residuals PiMinus

  • Hits-P04if-PiMinus_longResMean_dipAng_H_p2.gif
    Hits-P04if-PiMinus_longResMean_dipAng_p2.gif
    Hits-P04if-PiMinus_longResMean_z_p2.gif
    Hits-P04if-PiMinus_longResMean_z_H_p2.gif
    Hits-P04if-PiMinus_longRes_dipAng_p2.gif
    Hits-P04if-PiMinus_longRes_dipAng_H_p2.gif
    Hits-P04if-PiMinus_longRes_z_p2.gif
    Hits-P04if-PiMinus_longRes_z_H_p2.gif
    Hits-P04if-PiMinus_transRes_crosAng_p2.gif
    Hits-P04if-PiMinus_transRes_crosAng_H_p2.gif
    Hits-P04if-PiMinus_transRes_z_p2.gif
    Hits-P04if-PiMinus_transRes_z_H_p2.gif

  • Track Residuals PiPlus

  • Hits-P04if-PiPlus_longResMean_dipAng_H_p2.gif
    Hits-P04if-PiPlus_longResMean_dipAng_p2.gif
     Hits-P04if-PiPlus_longResMean_z_H_p2.gif
    Hits-P04if-PiPlus_longResMean_z_p2.gif
    Hits-P04if-PiPlus_longRes_dipAng_H_p2.gif
    Hits-P04if-PiPlus_longRes_dipAng_p2.gif
    Hits-P04if-PiPlus_longRes_z_H_p2.gif
    Hits-P04if-PiPlus_longRes_z_p2.gif
    Hits-P04if-PiPlus_transRes_crosAng_H_p2.gif
    Hits-P04if-PiPlus_transRes_crosAng_p2.gif
    Hits-P04if-PiPlus_transRes_z_H_p2.gif
    Hits-P04if-PiPlus_transRes_z_p2.gif

    Previous results - May 2002



    This document is intended to provide all the information available for previous productions such that results for Quality Control studies and Productions Cross checks. Part of quality control studies include identification of missing/dead detector areas, distance of closest approach distributions (dca), and fit points distributions(Nfit). As part of production cross checks, some results in centrality dependance and efficiency are shown


    Quality Control


  • dEdx Comparisons

  • These are dedx vs P graphs. All of them show reasonable agreement with data.(Done on May 2002)

    Dedx-dedxPiPlus.gif
    Dedx-dedxKMinus.gif
    Dedx-dedxProton.gif
     Pi Minus
     K Minus
    Proton 
     Dedx-dedxPiMinus.gif
     Dedx-dedxKPlus.gif
    Dedx-dedxPbar.gif
     Pi Plus
     K Plus
     P Bar

  • Dca Distributions

  • PI PLUS.  In the following dca distributions some discrepancy is shown.  Due to secondaries?
     Dca-PiPlusDca_100pt200.gif
    Dca-PiPlusDca_200pt300.gif
    Dca-PiPlusDca_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c
     MinBias 0.2 GeV/c < pT < 0.3 Gev/c
     Central 0.3 GeV/c <pT <  0.4 GeV/c


    PI MINUS. Some discrepancy is shown.  Due to secondaries?
     Dca-PiMinusDca_100pt200.gif
     Dca-PiMinusDca_200pt300.gif
    Dca-PiMinusDca_300pt400.gif
      Peripheral 0.1 GeV/c < pT < 0.2 Gev/c   MinBias 0.2 GeV/c < pT < 0.3 Gev/c   Central 0.3 GeV/c <pT <  0.4 GeV/c

    K PLUS.  In the following dca distributions Good agreement with data is shown.
     Dca-KPlusDca_100pt200.gif
    Dca-KPlusDca_200pt300.gif
    Dca-KPlusDca_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c
     MinBias 0.2 GeV/c < pT < 0.3 Gev/c
     Central 0.3 GeV/c <pT <  0.4 GeV/c

    K MINUS. In the following dca distributions Good agreement with data is shown.

     Dca-KMinusDca_100pt200.gif
     Dca-KMinusDca_200pt300.gif
    Dca-KMinusDca_300pt400.gif
      Peripheral 0.1 GeV/c < pT < 0.2 Gev/c   MinBias 0.2 GeV/c < pT < 0.3 Gev/c   Central 0.3 GeV/c <pT <  0.4 GeV/c


    PROTON. The real data Dca distribution is wider, especially at low pT -> Most likely due to secondary tracks in the sample. A tail from background protons dominating distribution at low pt can be clearly seen. Expected deviation from the primary MC tracks.

     Dca-ProtonDca_200pt300.gif
     Dca-ProtonDca_500pt600.gif
    Dca-ProtonDca_700pt800.gif
      Peripheral 0.2 GeV/c < pT < 0.3 Gev/c   MinBias 0.5 GeV/c < pT < 0.6 Gev/c   Central 0.7 GeV/c <pT <  0.8 GeV/c

    Pbar. The real data Dca distribution is wider, especially at low pT -> Most likely due to secondary tracks in the sample.

     Dca-PbarDca_200pt300.gif
     Dca-PbarDca_300pt400.gif
    Dca-PbarDca_500pt600.gif
      Peripheral 0.2 GeV/c < pT < 0.3 Gev/c   MinBias 0.3 eV/c < pT < 0.4 Gev/c   Central   0.5 GeV/c <pT <  0.6 GeV/c

  • Number of Fitted Points

  • PI PLUS.  Good agreement with data is shown.
    NFit-PiPlusNfit_100pt200.gif
    NFit-PiPlusNfit_200pt300.gif
    NFit-PiPlusNfit_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c
     MinBias 0.2 GeV/c < pT < 0.3 Gev/c
     Central 0.3 GeV/c <pT <  0.4 GeV/c
    PI MINUS.  Good agreement with data is shown.

    NFit-PiMinusNfit_100pt200.gif
    NFit-PiMinusNfit_200pt300.gif
    NFit-PiMinusNfit_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c  Peripheral 0.2 GeV/c < pT < 0.3 Gev/c  Peripheral 0.3 GeV/c < pT < 0.4 Gev/c

    K PLUS.  Good agreement with data is shown.
    NFit-KPlusNfit_100pt200.gif
    NFit-KPlusNfit_200pt300.gif
    NFit-KPlusNfit_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c
     MinBias 0.2 GeV/c < pT < 0.3 Gev/c
     Central 0.3 GeV/c <pT <  0.4 GeV/c

    K MINUS.  Good agreement with data is shown.
    NFit-KMinusNfit_100pt200.gif
    NFit-KMinusNfit_200pt300.gif
    NFit-KMinusNfit_300pt400.gif
     Peripheral 0.1 GeV/c < pT < 0.2 Gev/c  Peripheral 0.2 GeV/c < pT < 0.3 Gev/c  Peripheral 0.3 GeV/c < pT < 0.4 Gev/c

    PROTON.  Good agreement with data is shown.
    NFit-ProtonNfit_200pt300.gif
    NFit-ProtonNfit_300pt400.gif
    NFit-ProtonNfit_500pt600.gif
     Peripheral 0.2 GeV/c < pT < 0.3 Gev/c  Peripheral 0.3 GeV/c < pT < 0.4 Gev/c Peripheral 0.5 GeV/c < pT < 0.6 Gev/c

    Pbar.  Good agreement with data is shown.
    NFit-PbarNfit_200pt300.gif
    NFit-PbarNfit_300pt400.gif
    NFit-PbarNfit_500pt600.gif
     Peripheral 0.2 GeV/c < pT < 0.3 Gev/c  Peripheral 0.3 GeV/c < pT < 0.4 Gev/c Peripheral 0.5 GeV/c < pT < 0.6 Gev/c

    Productions Cross Checks


  • Centrality Dependance

  •  Compare-PiMKMPbar8.gif Compare-PiMKMPbar7.gif Compare-PiMKMPbar6.gif Compare-PiMKMPbar5.gif
     5% central
    5 % - 10% 10% - 20%  20 % - 30 % 
     Compare-PiMKMPbar4.gif Compare-PiMKMPbar3.gif Compare-PiMKMPbar2.gifCompare-PiMKMPbar1.gif
     30% -  40% 40% - 50% 50% - 60% 60% - 80%


  • Reverse Full Field vs Full Field : No asymetry observed


  •  MinBiasCentral 
     Pi Minus
     Compare-PiM_FF-REV0.gifCompare-PiM_FF-REV8.gif
     
     Min Bias
     Central
     K Minus
      Compare-KM_FF-REV0.gif   Compare-KM_FF-REV8.gif
      MinBias Central
     Pbar  Compare-Pbar_FF-REV0.gif Compare-Pbar_FF-REV8.gif 


  • Charge Asymmetry : No asymetry observed for Pi Minus and  K Minus. For Pbar more data are needed



  •  MinBiasCentral 
     Pi Minus
      Compare-PiP-PiM0.gif Compare-PiP-PiM8.gif 
     
     Min Bias
     Central
     K Minus
      Compare-KP-KM0.gif   Compare-KP-KM8.gif
      MinBias Central
     Pbar  Compare-P-Pb0.gif Compare-Pbar_FF-REV8.gif