Hi,
I d like to put forward a list of remaining tasks in software. I want to
do so because a lot of them require interaction between us earthy
programmers and people in verious groups of the experment. Please take a
look and give your suggestion for solutions and/or make additions to the
list:
1. blast.sc_cal: I am personally very excited about the calibration Pete
put out. In the mean time, i have the following questions:
adc pedestals: Adrian knows them by heart but unfortunately, they are
not written into blast.sc_cal. It is partly because, I guess, Pete
generates tdc offsets by program which does not know about
pedestals.
other parameters in blast.sc_cal: speed of light in scintillator,
tdc/adc scales. Do we have any interest in calibrate those? seems
we can well get away with the current dummy values. Also, though
we do need the 50ps/channel conversion for tdc, do we really need
the 50fC/channel conversion for adc?
2. interface to NC/LADS calibration: soon NC/LADS tdc/adc will be
calibrated, and we need an interface to feed them into the library.
extending blast.sc_cal seems to be a valid option but we do need to see
what Pete have to say since it is his little baby.
3. LADS recon. I told Vitaliy I was gonna try to look into it during the
holiday but I lied, or I did not have a chance. I guess I am still suppose
to do it. basically, charged particles punch TOF and get into LADS will
generate hits and these hits could be geometrically identified as
generated by the charged particle. The LADS hits left will be candidates
for Neutrons but one need to be care for do not create two neutron tracks
when only on neutrons hit both NC and LADS.
4. BATS: though my group is in conflict for space with BATS, they
seem always win in the priority wrestling, so I had thought about
"BATS reconstruction". but it could be quite a long story, starting about
how BATS signals are treated in trigger, extend to who the CC box will be
connected to BATS, for instance, does trigger from bats already require
the CC or we have to make CC/BATS coinc in software.
5. interface to Compton. It would be easier for analysis if we could
include Compton info into data storage. so we need a way to fetch compton
info into a running cruncher and write them into dst/lr.
6. eloss. This would involve a lot of playing with blastmc. so first one
needs to make sure that blastmc and BlastLib2 work with each other. never
tried lately. I estimate a reasonable eloss in lib would require at least
two weeks.
7. some study on PID performace is in order, do we need to handcraft cuts
in mass spectra for various particle or the current comparison method is
sufficient, especially, is it possible to seperate proton and deuteron at
crunching level or we ll have to do extra cuts at analysis time. what is
the misidentify rate. is it possible to seperate pions?
8. after a improved WC calibration is provided, a lot of tuning must be
done on the library.
9. (a little off the line) radiative correction in generators.
10. methods to fetch environmental files like emap, epicsmap, blast.sc_cal
automatically. assuming those files in blast environment are always up to
date, this is only useful for recrunching runs a long time ago, which does
not seem to happen very often.
Thanks
Chi
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST