GAMMASPHERE information, HK data
K - fold, number of detectors that fired in GS
In the event filter formatters (EFFs), a time gate is normally
applied to the events where there are dirty germaniums and clean
BGO events. This time gate is set in the file /usr/eff/user.eff
-- see the FAQ for details.
Thus, normally, the line in the event header that contains
the number of 'dirty germaniums' and 'clean BGO' detectors that fired
in the event are time gated by the prompt time window.
There is a problem with the above rule is we write any dirty germanium
detectors or clean BGO detectors out -- since then those multiplicities
are used to untangle the actual data on the data tapes. To overcome
this problem the expanded rule is:
- if dirty germaniums are written out, then there is no time
gate applied to the number of dirty germaniums that fired in the
header. It's the users responsibility to apply time gates.
- if clean BGOs are written out, then there is no time
gate applied to the number of clean BGOs that fired in the
header. It's the users responsibility to apply time gates.
Thus, if neither dirty germaniums or clean BGO are written out, to get
the total prompt multiplicity of an event, you need to
add
- the number of clean germaniums you see in an event after
you have applied you own time gate
- the dirty germanium count from the event header (the EFF's have
applied a time gate)
- the clean BGO count from the header (the EFF's have
applied a time gate)
(For gs_skim users: the latter two numbers are summed and put in the
first word of the skimmed-event so you only need to add the prompt-gated
clean germaniums to get the total multiplicity, tmul)
H - summed energy observed in GS
In the event header, the last two words are the sum of energy
seen in the germanium detectors and BGO detectors. Both of those
energies are time gated with the EFF time gate (see the FAQ for details on how to set
or change this time gate)
The germanium summed energy is from the low-res germanium signal
and both clean and dirty germaniums are add added with the time
gate. Thus, for the summed energies for both germanium and BGO
detectors, all time gating has been done by the EFFs (no matter
what data is written to tape). For the calibration coefficients
of the two summed energy signals, see the event header documentation
(for gs_skim users: as of 10/23/9, the above energies have been added
up as etot=(10*eBGO+16*ege)/551 and stored in the first word of the
skimmed event)
If you find errors in this GAMMASPHERE documentation;
please send E-mail to Torben@anl.gov.
GS HK response functions/matrixes
Here is an example of a response function for Gammasphere
when there are no heavy-mets in front of the BGO detectors
gsfma30_h_rsp_true.mascii;
gsfma30_h_rsp_true.mascii.dm
gsfma30_k_rsp_true.mascii;
gsfma30_k_rsp_true.mascii.dm
Here is another example of a response function for Gammasphere
when there are no heavy-mets in front of the BGO detectors
gsfma72_h_rsp_true.mascii;
gsfma72_h_rsp_true.mascii.dm
gsfma72_k_rsp_true.mascii;
gsfma72_k_rsp_true.mascii.dm
Hold shift key down when you click on the response functions to
download.
If you have other HK response functions you would like to share, send
them to me torben@anl.gov so
I can put them on this page.
torben@anl.gov