05/02/00   10:40 PM EDT
PHENIX VRDC Production Iteration #11 - FAQs about DSTs
------------------------------------------------------
COMMENT: A page of this sort will be produced for each significant
iteration of the CRS (production) farm. "Significant iterations"
include any that contain the results of significant code changes.
There may be less significant iterations that occur in between.
These are mainly to try to keep the farm running, and for me to
learn how to run it better.
FAQs answered here: (click to jump to a desired section)
Q1. How many reconstructed events are available, in how many files,
and of what types?
Q2. Where are the DST files?
Q3. How do I utilize these DST files?
Q4. Is the quality of these files assured?
Q5. Under what conditions were these events reconstructed?
Q1. How many reconstructed events are available, in how many files,
and of what types?
o Central arm only at this time.
o Includes signal-mixed, but no pure signal.
(PWGs can do those themselves.)
o For a more extensive summary, see Tarun, Indrani's, and Naoki's
web pages, referenced from my main Analysis Resources page.
Here's a QUICK SUMMARY:
o Umm, why are there fewer hijing central and pythia events
than expected?
==> Good question. I am looking into this...
o NOTE: PLEASE READ this message from Jeff Mitchell. It
details the configuration of LUXOR for this iteration.
Q2. Where are the DST files?
o All DST files can be found in the HPSS, under
/home/phnxreco/vrdc/dst011
To conveniently inspect this area, use my HPSS Inventory.
You can also access the inventory from unix - just do this:
cd ~tlthomas/HPSS-inventory
(and try using xfm... do a 'man xfm' to learn more.)
o These files are also available ON DISK...!
--> Under /phenix/data05/phnxreco/vrdc/dst011/
(It's the same file hierarchy as in HPSS.)
o One needs to understand at least the basics of the
file naming conventions to make sense of these files.
Here is my 12/21/99 posting to off-l defining this,
and here's an example usage of the naming scheme.
The iteration 11 DST files have a prefix of DST011.
Q3. How do I utilize these DST files?
o Pick which ones you want to analyze.
(Assuming you understand about the naming conventions...)
The correspondence between the "Standard Name" of a file
and the internal conditions of the file is presently
established using the so-called "MDC2 Extension", which has
been removed from the DST file names. To learn about or select
based on the internal conditions of these VRDC simulation
results, please make use of my "DataBasette" files, which
can be found in the top path of the HPSS inventory:
~tlthomas/HPSS-inventory/PRDF-DataBasette.txt and
" / " /DST011-DataBasette.txt
These files contain a list of Standard Names and the corresponding
Extensions that are part of the PRDF files but have not been
included in the name of the DST files.
For example, if you want to identify all AuAu files that have
a Z vertex of -15 cm, you might say:
grep 'nv15' PRDF-DataBasette.txt
o NOTE: These "DataBasettes" will be replaced eventually by
a combination of simulation and production data bases.
o FINALLY, refer to the various tutorial resources listed on my
main Analysis Resources page to learn how to create analysis
programs and run them. (And if you learn of new resources,
please let me know so I can add links to them.)
Q4. Is the quality of these files assured?
o Check out the following two Q.A. resources:
o Here is a web page, made by Jeff Mitchell, that references
the histograms produced by his camcheck*.C macros
(see /afs/rhic/phenix/software/pyrite/macros/VRDC011)
for one particular hijing central arm central DST file.
o I have produced a root file - using those same macros - for
a different central arm central file, namely
DST011_29_RTKG00030_0001.PROOT
The histogram file is this one:
/phenix/data08/tlthomas/testdata/D011QA_29_RTKG00030_0001.ROOTG
o NOTE: For future iterations, such Q.A. root histogram
files will be produced on disk as part of the standard farm
job operation.
Q5. Under what conditions were these events reconstructed?
o FIRST, PLEASE READ this message from Jeff Mitchell. It
details the configuration of LUXOR for this iteration.
o See [Similar document from muon sector.]
o The "Setup":
unsetenv ONLINE_MAIN; unsetenv OFFLINE_MAIN
setenv ONLINE_MAIN /afs/rhic/phenix/oncs/R-pro/online_distribution
source /opt/phenix/bin/phenix_setup.csh -v pro
--> In the future, online will be done differently; e.g., I will
explicitly set ONLINE_MAIN to .../oncs/R2.6.2a/online_distrib
--> More detailed config info than this (e.g., MD5 checksums of
ASCII text database files and rootcint macros used, etc.) is
stored in the log files of each farm job and will not be
documented here. Ask me if you want to know more.
o For iteration 11, the CRS farm ran from 4/20::00:30 thru 4/23::11:00.
During that period, the Frozen library versions used were these:
o OFFLINE LIBRARIES: 'pro', built from tag 'OffApr00c'...
cvs history -T -a
T 04/18 22:01 +0000 momchil phuniverse [OffApr00c:2000.04.09.05.30.00]
o SIMULATION LIBRARY: [the "Saint Patty's Day library"]
/afs/rhic/phenix/PHENIX_LIB/simulation/pro/i386_linux61/lib/ :
-rwxr-xr-x 1 maguire rhphenix 2382345 Mar 17 15:59 libPISARoot.so
ldd libPISARoot.so
libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2 (0x40215000)
libm.so.6 => /lib/libm.so.6 (0x4025b000)
libc.so.6 => /lib/libc.so.6 (0x40277000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
o ONLINE LIBRARIES: basically, R-pro -> R2.6.2a ; but please see
this page for more details.