Home

computing

Database

Updated on Tue, 2009-06-09 09:40 by testadmin. Originally created by staruser on 2006-10-26 08:53. Under:

These pages describe how to use the BEMC database.  There is a browser-based tool that you can use to view any and all BEMC tables available at:

»

Run 4 BTOW Calibration

Updated on Sat, 2008-03-08 12:03. Originally created by kocolosk on 2006-10-26 08:20. Under:

Introduction:

The recalibration of the BEMC towers for Run 4 includes the following improvements:

»

Run 5 BTOW Calibration

Updated on Sat, 2008-03-08 12:04. Originally created by kocolosk on 2006-10-26 08:10. Under:

Introduction

The final BTOW calibration for Run 5 offers the following improvements over previous database calibrations:

»

Single Spin Asymmetries by Fill

Updated on Sun, 2008-09-21 08:34. Originally created by kocolosk on 2006-10-26 07:45.

Away-side only

BJP1 (hardware & software & geometric) requirement, only use pions with dR > 1.5

Action Items

Updated on Tue, 2012-11-27 11:15 by jwebb. Originally created by potekhin on 2006-10-25 10:21. Under:

Immediate action items:

»

Data Management

Updated on Thu, 2009-09-24 13:16 by testadmin. Originally created by stargrid on 2006-10-23 11:18. Under:

The data management section will have information on data transfer and development/consolidation of tools used in STAR for Grid data transfer.

 

Run 6 BTOW Calibration

Updated on Thu, 2009-09-03 16:42 by mattheww. Originally created by kocolosk on 2006-10-23 10:18. Under:

Introduction

This is not the final calibration for the 2006 data, but it's a big improvement over what's currently in the DB.  It uses MIPs to set relative gains for the towers in an

»

Using your Grid CERT to sign or encrypt Emails

Updated on Thu, 2006-10-19 21:09. Originally created by stargrid on 2006-10-19 20:00. Under:
Apart from allowing you to access the Grid, an SSL Client Certificate is imported into the Web browser from which you requested your Grid certificate. This certificate could be used to digtially sign or encrypt Email. For the second, you will need te certificate from the correspondign partner in order to encrypt Emails. To make use of it, folow the below guidance.
»

GridLeak: Gain Study

Updated on Thu, 2006-10-19 22:29. Originally created by genevb on 2006-10-19 17:37. Under:
In February 2005, Blair took some special runs with altered TPC gains so we could study the effect on the GridLeak distortion.
»

GridLeak Studies

Updated on Fri, 2013-03-01 14:01. Originally created by genevb on 2006-10-19 17:34. Under:

Datasets

Updated on Tue, 2012-11-27 11:34 by jwebb. Originally created by potekhin on 2006-10-12 17:33. Under:

Here we present information about our datasets.

Adding a New Detector to STAR

Updated on Thu, 2013-12-19 09:47 by jwebb. Originally created by potekhin on 2006-10-12 17:18. Under:

The STAR Geometry Model

»

R&D Tags

Updated on Tue, 2011-10-25 15:54 by jwebb. Originally created by perev on 2006-10-12 15:58. Under:

The R&D conducted for the inner tracking upgrade required that a few specialized geometry tags be created. For a complete set of geometry tags, please visit the STAR Geometry in simulation & reconstruction page.

»

2005

Updated on Thu, 2006-10-12 17:34. Originally created by potekhin on 2006-10-10 20:19. Under:
Description
Dataset name
Statistics, thousands
Status
Moved to HPSS
Comment
Herwig 6.507, Y2004Y
rcf1259
225
Finished
Yes
   7Gev<Pt<9Gev
Herwig 6.507, Y2004Y
rcf1258
248
Finished
Yes
   5Gev<Pt<7Gev
Herwig 6.507, Y2004Y
rcf1257
367
Finished
Yes
   4Gev<Pt<5Gev
Herwig 6.507, Y2004Y
rcf1256
424
Finished
Yes
   3Gev<Pt<4Gev
Herwig 6.507, Y2004Y
rcf1255
407
Finished
Yes
   2Gev<Pt<3Gev
Herwig 6.507, Y2004Y
rcf1254
225
Finished
Yes
   35Gev<Pt<100Gev
Herwig 6.507, Y2004Y
rcf1253
263
Finished
Yes
   25Gev<Pt<35Gev
Herwig 6.507, Y2004Y
rcf1252
263
Finished
Yes
   15Gev<Pt<25Gev
Herwig 6.507, Y2004Y
rcf1251
225
Finished
Yes
   11Gev<Pt<15Gev
Herwig 6.507, Y2004Y
rcf1250
300
Finished
Yes
   9Gev<Pt<11Gev
Hijing 1.382 AuAu 200 GeV minbias, 0< b < 20fm
rcf1249
24
Finished
Yes
 Tracking,new SVT geo, diamond: 60, +-30cm, Y2005D
Herwig 6.507, Y2004Y
rcf1248
15
Finished
Yes
 35Gev<Pt<45Gev
Herwig 6.507, Y2004Y
rcf1247
25
Finished
Yes
 25Gev<Pt<35Gev
Herwig 6.507, Y2004Y
rcf1246
50
Finished
Yes
 15Gev<Pt<25Gev
Herwig 6.507, Y2004Y
rcf1245
100
Finished
Yes
 11Gev<Pt<15Gev
Herwig 6.507, Y2004Y
rcf1244
200
Finished
Yes
   9Gev<Pt<11Gev
CuCu 62.4 Gev, Y2005C
rcf1243
5
Finished
No
 same as 1242+ keep Low Energy Tracks
CuCu 62.4 Gev, Y2005C
rcf1242
5
Finished
No
 SVT tracking test, 10 keV e/m process cut (cf. rcf1237)
10 J/Psi, Y2005X, SVT out
rcf1241
30
Finished
No
Study of the SVT material effect
10 J/Psi, Y2005X, SVT in
rcf1240
30
Finished
No
Study of the SVT material effect
100 pi0, Y2005X, SVT out
rcf1239
18
Finished
No
Study of the SVT material effect
100 pi0, Y2005X, SVT in
rcf1238
20
Finished
No
Study of the SVT material effect
CuCu 62.4 Gev, Y2005C
rcf1237
5
Finished
No
 SVT tracking test, pilot run
Herwig 6.507, Y2004Y
rcf1236
8
Finished
No
 Test run for initial comparison with Pythia, 5Gev<Pt<7Gev
Pythia, Y2004Y
rcf1235
100
Finished
No
 MSEL=2, min bias
Pythia, Y2004Y
rcf1234
90
Finished
No
 MSEL=0,CKIN(3)=0,MSUB=91,92,93,94,95
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1233
308
Finished
Yes
 4<Pt<5, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1232
400
Finished
Yes
 3<Pt<4, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1231
504
Finished
Yes
 2<Pt<3, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1230
104
Finished
Yes
 35<Pt, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1229
208
Finished
Yes
 25<Pt<35, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1228
216
Finished
Yes
 15<Pt<25, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1227
216
Finished
Yes
 11<Pt<15, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1226
216
Finished
Yes
 9<Pt<11, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1225
216
Finished
Yes
 7<Pt<9, MSEL=1, GHEISHA
Pythia, Y2004Y, sp.2
(CDF tune A)
rcf1224
216
Finished
Yes
 5<Pt<7, MSEL=1, GHEISHA
Pythia special tune2
Y2004Y, GCALOR
rcf1223
100
Finished
Yes
4<Pt<5, GCALOR
Pythia special tune2
Y2004Y, GHEISHA
rcf1222
100
Finished
Yes
4<Pt<5, GHEISHA
Pythia special run 3
Y2004C
rcf1221
100
Finished
Yes
 ENER 200.0, MSEL 2, MSTP (51)=7,
MSTP (81)=1, MSTP (82)=1, PARP (82)=1.9,
PARP (83)=0.5, PARP (84)=0.2,
PARP (85)=0.33, PARP (86)=0.66,
PARP (89)=1000, PARP (90)=0.16,
PARP (91)=1.0, PARP (67)=1.0
Pythia special run 2
Y2004C
(CDF tune A)
rcf1220
100
Finished
Yes

ENER 200.0, MSEL 2, MSTP (51)=7,
MSTP (81)=1, MSTP (82)=4, PARP (82)=2.0,
PARP (83)=0.5, PARP (84)=0.4,
PARP (85)=0.9, PARP (86)=0.95,
PARP (89)=1800, PARP (90)=0.25,
PARP (91)=1.0, PARP (67)=4.0

»

2006

Updated on Thu, 2007-01-04 14:57. Originally created by potekhin on 2006-10-10 14:42. Under:
Description
Dataset name
Statistics, thousands
Status
Moved to HPSS
Comment
AuAu 200 GeV central

rcf1289

»

STARSIM

Updated on Tue, 2006-10-10 14:34. Originally created by potekhin on 2006-10-10 14:34. Under:

Starsim

Production Geometry Tags

Updated on Mon, 2009-11-30 16:01 by testadmin. Originally created by perev on 2006-10-10 14:06. Under:

This page was merged with STAR Geometry in simulation & reconstruction and maintained by STAR's librarian.

 

 

OFC West possible distortion

Updated on Tue, 2006-10-03 18:20. Originally created by genevb on 2006-10-03 17:39. Under:
There remains a possible distortion due to a potential short in the OFC west as well. We see a bimodal pattern of 0 or 80 excess nanoAmps coming out of the OFC West field cage resistor chain (it has been there since the start of the 2005 run). That corresponds to a 0.38 MOhm short (420nA = 2 MOhms). The corresponding distortion depends on the location of the electrical short. The plot shown here is the distortion in azimuth (or rPhi) at the outermost TPC padrow near the sector boundaries (r=195 cm, the pads are closer to the OFC near the sector boundaries) due to such a short between different possible field cage rings:

In terms of momentum distortion, a 1mm distortion at the outermost padrows would cause a sagitta bias of perhaps about 0.5mm for global tracks (and even less for primary tracks), corresponding to an error in pt in full field data of approximately 0.006 * pt [GeV/c] (or 0.6% per GeV/c of pt). This is certainly at the level where it is worthwhile to try to fix the distortion if we can figure out where the short is. It is also at the level where we should be able to see with the lasers perhaps to within 50cm where the short is.

Just as a further point of reference, the plot for radius = 189cm, corresponding to the radius of the outermost padrow in the middle of a sector (its furthest point from the OFC) can be found here.

This possible distortion remains uninvestigated at this time.

Gene Van Buren
gene@bnl.gov

»

Update on 2006 issues

Updated on Wed, 2006-09-06 11:01. Originally created by genevb on 2006-09-06 10:53. Under:
BeamLineUpdate


FINDINGS:

BeamLine position does move with SpaceCharge(+GridLeak) correction. Here I plot the BeamLine constraint as a function of turning on the SpaceCharge correction 10% at a time:


The cause appears to be the Minuit Vertex Finder exhibiting something like a (x,y) = (0,0) bias which gets worse when the distortion corrections are not proper. To demonstrate this, I plot the beamline position as reconstructed using SpaceCharge,GridLeak,ShortedRing-corrected data (left) and uncorrected data (right). The center point in each plot is the "as-is" reconstructed beamline x and y intercepts. I shift all the hits in the TPC by +/-0,1,2 mm in x and y and re-calibrated the BeamLine for each shift. The blue dots represent those shifts given to the TPC hits, while the arrowheads point at the value that comes from the calibration for the respective shifts. Some bias appears to remain even with the calibrations in place, but the bias is clearly stronger for uncorrected data.

In this case, the uncorrected data is actually using calibrations as they were in June when the BeamLine calibration was originally done: no SpaceCharge, and only a partial Shorted Ring correction.




A few more things can be learned from the data by excluding sections of the TPC. In these plots, I show sector positions as they are in the TPC, divided into 12 supersectors with inner (padrows 1-12) and outer (padrows 14-45) subsectors. Each bin then represents the y-intercept of the beamline when I EXCLUDE the vertices which have any tracks passing through that part of the TPC. I include in text below the plot the y-intercepts for the minimum and maximum shown in the plots, and for the FULL TPC (not excluding any vertices). I can exclude some sectors simultaneously too. EAST IS ON TOP, WEST IS ON BOTTOM (unless I tied east and west exclusion together, so I only show one plot). The disc in the center of each plot represents the FULL TPC position for comparison.

First, using the corrections as they were in June, one can clearly see the effect caused by uncorrected SpaceCharge:

Uncorrected July corrections August corrections
Full TPC y = -0.060040 +/- 0.009377
Minimum y = -0.179608
Maximum y = 0.056453
 Full TPC y = -0.266030 +/- 0.004800
Minimum y = -0.276851
Maximum y = -0.245626
 Full TPC y = -0.259742 +/- 0.002232
Minimum y = -0.263649
Maximum y = -0.241834

In FullField data like this, SpaceCharge makes tracks rotate clockwise when viewed along the positive axis. So SpaceCharge-distorted tracks at positive x tend to want a higher vertex position, while ones at negative x want a lower vertex position. Therefore, excluding vertices which use tracks at positive x from uncorrected data will effectively lower the average vertex position, and vice versa for negative x. The uncorrected data is dominated by SpaceCharge, so both halves of the TPC look pretty much the same.

With Shorted Ring and SpaceCharge corrections as they were in July (SpaceCharge calibration had been done without the final Shorted Ring corrections), one can see that we were probably slightly over-correcting for this data, but not by much as the minimum and maximum were both within ~300 microns of using the whole TPC.

With the SpaceCharge+GridLeak re-calibrated using the final Shorted Ring corrections in place, the fully corrected plot now appears as in the August-corrections column above. The max-min diff has gone from 310 microns to 220 microns! And the west tpc (bottom) looks essentially flat: there is no distortion apparent in the beamline from the west TPC! The east still shows some remnant distortion. This could be due to either more SpaceCharge in the east than west, or due to not-quite-complete corrections of the shorted ring in the east TPC. Either explanation is viable.

These graphs also demonstrate that there is unlikely to be much contribution from misalignment of TPC (sub)sectors.

We can remove azimuthally symmetric distortions like our standard SpaceCharge+GridLeak and the Shorted Ring by tying together (excluding at the same time) opposing (in phi) subsectors of the TPC:

Full TPC y = -0.259742 +/- 0.002232
Minimum y = -0.263744
Maximum y = -0.243980

Here I think it is of interest to notice that the major cause for altered beamline in the east TPC is from the outer subsectors at 3 and 9 o'clock. Shorted ring distortions are primarily an inner sector effect and should not show up in this plot anyhow. This means that it is more likely to be due to additional ionization in the east TPC over the west.

We can also analyze the horizontal determination of the beamline.

Full TPC x = -0.009712 +/- 0.002242
Minimum x = -0.018511
Maximum x = 0.000031

Again, more distortions in the east TPC. Overall max-min diff here is only 185 microns! It's curious that this is not symetric about 6 and 12 o'clock. Tying opposing subsectors shows something else:


Full TPC x = -0.009712 +/- 0.002242
Minimum x = -0.015330
Maximum x = -0.002258

Both the east and west show something at 5 and/or 10 o'clock (and a bit at 4/10) contributing (minutely - were talking on the order of below 100 microns) to the horizontal position of the beam.

»

dAu photon embedding details

Updated on Wed, 2006-12-27 16:31. Originally created by starembed on 2006-08-30 08:30. Under:
    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
»