- jeromel's home page
- Posts
- 2020
- 2019
- 2018
- 2017
- 2016
- 2015
- December (1)
- November (1)
- October (2)
- September (1)
- July (2)
- June (1)
- March (3)
- February (1)
- January (1)
- 2014
- 2013
- 2012
- 2011
- 2010
- December (2)
- November (1)
- October (4)
- August (3)
- July (3)
- June (2)
- May (1)
- April (4)
- March (1)
- February (1)
- January (2)
- 2009
- December (3)
- October (1)
- September (1)
- July (1)
- June (1)
- April (1)
- March (4)
- February (6)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
Status of production (readiness for Run 15)
Calibration status and general readiness
- A comprehensive summary of the S&C activities was given in starsoft in this post. We once again highly recommend to the PWGC to read those summaries and remain informed.
- We have reviewed the priorities from the Spin White Paper and Spin PWG (one convener of the Spin PWG was asked for confirming, one member of the Spin WP effort as well). The preiminary feedback was passed to the software cooridnators for consideration ...
- We will discuss the following datasets: p+p trans & long, Fixed target, p+Al
- All sub-system software coordinators were asked and polled for their readiness many times since the beginning to mid-summer. Most responded to the (not surprisingly) noticeable exception of the HFT software coordination (see later). The calibration status in this area are unknown and request for summaries and updates are not being followed.
- We already noted we have no news as per the status of the HFT calibration - high-accuracy reconstruction in the central rapidity region will not be reached. Indirect information stated that the HFT internal alignement should be ready but not more news were provided (directely in a coordinated way or indirectly through intercation with individuals).
- It is understood this is not neded for the Spin PWG tasks and objectives (TBC).
- FMS/RP/EMC/TPC base calibrations are ready - this is a good state for p+p trans and p+Au.
- The TPC group now beleives the T0 issues are understood and the [TOF,dE/dx] effect is being checked (production is running as noted here and will be done in couple of days).
- Spin related
- FMS/FPS are mainly reached - their calibrations insofar are done for p+p transverse day 77-92 and p+Au days 125-156 and moving to the p+p long and p+Al.
- The RP code is being developped and near ready. All data structures are in place in StEvent (MuDST connection missing but this is fast). The more recent news is that the RP TrackPoint code is near ready and should take another couple days to be ready (Rafal Sikora / Kin Yip)
- From a TPC perspective, the fixed target data is ready to go anytime. There has been no evaluation of the Vertex reconstruction but discussion were carried to include the possibility to add in the VF used by the FT program (and basic infrastructure / code added and ready to be tested).
- Our next dataset focus is curently p+Au
- The final chain will then need to be double checked & crystalized (never been a show-stopper, noted for consistency).
- At this point int ime, the dataset we may consider to produce are (within a week)
- Fixed Target data
- p+p 200 GeV transverse, no HFT
- Pending
- p+p 200 GeV longitudinal - more time needed for FMS calibration + note that production priorities highly depends on STAR tasks priorities (currently, the same people taking care of calibration are also suggested other tasks).
- p+Au - this has begun but not entirely ready for the TPC (FMS ready)
- p+Al - near nothing ready
- Production time estimates - subject to correction (only test jobs available), a 100% farm slot usage would indicate
- st_physics p+p 200 GeV, 10 sec/evts - 2 B in ~ 1.5-2 months
- st_rp 1 B events ata about the same time /evts => ~ 3 weeks - 1 month top
- p+Au 1.3 B evts would take ~ 1-1.5 months
- p+Al is at 24 sec/evts in our tests so x2 the time of otehr datasets but not much data available (240 M events, not Billions)
- More accurate timing being sorted out and will appear on this blog whenever available.
- ATTENTION: using the farm will proportionally delay the remainder of the Run 14 data production ...
- RunLog info
- production_pp200trans_2015 - 2.86 B evts 2.86 B
- production_pp200long_2015 - 912 M evts 912 M --> this should probably not be produced, pola. not good
- production_pp200long2_2015 - 2.46 B evts 2.46 B
- production_fms_pp200trans_2015 - 22.93 M -- --> those have no data with TPX
- production_fms_pp200long2_2015 - 11.35 M --
- production_pAu200_fms_2015 - 11.29 M --
- production_pAu200_2015 - 3.6 B 3.6 B
- production_pAl200_2015 - 1.03 M 1.03 B
- production_pAl200_2015_lowlumi - 19.52 M 19.52 M
- fixedTarget2015 - 7.2 M 5.02 M
Groups:
- jeromel's blog
- Login or register to post comments