CAVEAT: The analyses described here have to be considered just as "exploratory" analyses, not much more reliable than parton-level-analyses with some detector smearing.
FAMOS and ORCA single top analyses are described here.

CMSJET fast simulation analysis:

~/cmsjet/cmsjet_pyt_m.f reads the filename.ntpl ntuples, giving as output the column-wise ntuples filename.hbook containing the following informations:

TRANCH   * CIRC
TRANCH   * TREN
TRANCH   * TRMA
PTMIS    * PTMT(2)
PTMIS    * PTM(2)
PTMIS    * PZNU(2)
LEPTONS  * NLE_CWN
LEPTONS  * PL_CWN(4,NLE_CWN)
LEPTONS  * KL_CWN(NLE_CWN)
LEPTONS  * MRL_CWN(NLE_CWN)
LEPTONS  * LISOL_CWN(NLE_CWN)
GAMMAS   * NGAM_CWN
GAMMAS   * PG_CWN(4,NGAM_CWN)
GAMMAS   * LISGAM_CWN(NGAM_CWN)
JETS     * NJG_CWN
JETS     * PJG_CWN(4,NJG_CWN)
JETS     * MRKJET_NJG(NJG_CWN)
JETS     * BTAG_NJG(NJG_CWN)
The useful ones are:
All the analysis parameters and switches for ~/cmsjet/cmsjet_pyt_m.f, as well as the input and output ntuple files, are given by cmsjet_pyt_m.dat (also needed is myrandom.dat, which has to contain a 10-digits random seed).

I use a slightly modified version with whom I also save number and 4-momentum of the true top quarks. To compile (on lxplus) use this Makefile.    

PAW macro ~/scratch0/top/top.kumac opens the ntuples from CMSJET and plots the required variable comparing different event classes.
The analysis file ~/scratch0/top/readcwn.f (to be compiled with ~/scratch0/top/readcwn.csh), whose parameters and common blocks are in ~/scratch0/top/readcwn.inc, computes how many leptons (from W->l or not) are isolated, how many jets (from b quark or not) are b-tagged, and how many events are selected for different event classes.
Currently the following preselection criteria are chosen:


The PAW macro ~/scratch0/top/top2.kumac permits, after the execution of readcwn, to plot some variables after preselection.
To use Mreco (invariant mass of b+l+"nu") one has to choose one b-jet and one solution for the neutrino (since the W-mass constrain gives a second order equation). For the neutrino I choose the solution that gives the smaller |Mreco-Mtop|. For the b, I choose the "best" b-jet (i.e. the one with the largest b-tagging variable).
This gives an ambiguity for s-channel signal and for ttbar and Wbbbar backgrounds. This is not a serious problem when looking for single top vs. ttbar and Wbbbar, since s-channel is a small signal component (and the ambiguity in the choice broadens the Mreco distribution for the backgrounds, making them easier to throw out), but a better criterion should be found when trying to discriminate among the signal components.

For single top selection I cut on Mreco and Ht. Using the set of cuts in file cuts_singletop.inc (selectionmode=1 in ~/scratch0/top/readcwn.inc) I obtain the following results: sn_singletop.out (table preselected, table selected).

If I restrict the search to the s-channel (better theoretical errors, and bigger improvement on the main systematics is foreseen from high statistics LHC background studies, e.g. qq'->W) I impose two b-jets in the final state and use also the eta and momentum of the less b-like jet, and its angular distance from the most b-like. Using cuts_schannel.inc (selectionmode=2 in ~/scratch0/top/readcwn.inc) I obtain: sn_schannel.out (table preselected (2 b-jets instead of 1), table selected).

It's quite easy to select an almost pure t-channel sample (its advantages -and drawbacks- for studying single top polarization are discussed here): I impose only one b-jets in the final state, anti-tagging the second jet, and reject all events in which the angular distance between jets is below 3.2 (very few non-t-channel events fulfill this requirement). Using cuts_tchannel.inc (selectionmode=3 in ~/scratch0/top/readcwn.inc) I obtain: sn_tchannel.out (table selected).

(Results obtained with sn.f, which contains the theoretical cross sections and reads the efficiencies from readcwn, writing the results as a LaTeX table. The script sn.csh executes readcwn for all the signal and background channels, and at last launches sn.)        

Trigger studies:

We want to see the effect, on the selection efficiencies and on the shape of the variables, of the cuts listed in the DAQ TDR at page 285.
In trigger.f I gather several selection streams.        

Last developments (after CPT week, may'04):