LISTSERV mailing list manager LISTSERV 16.5

Help for VUB-RECOIL Archives


VUB-RECOIL Archives

VUB-RECOIL Archives


VUB-RECOIL@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

VUB-RECOIL Home

VUB-RECOIL Home

VUB-RECOIL  July 2002

VUB-RECOIL July 2002

Subject:

Track killing

From:

Urs Langenegger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

03 Jul 2002 01:04:36 -0700 (PDT)Wed, 03 Jul 2002 01:04:36 -0700 (PDT)

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (59 lines)


Hoi,

the trk  killing was implemented with the  Daniele's tables, contained
in IslBrecoilUser/tablechg.dat, giving the ratio data/MC.

In momentum intervals with an  'efficiency' larger than 1, tracks were
killed in data.  In the  following, the usual plots are inverted: what
is labelled  as data is actually  generic MC, and  the histograms show
the killed and default data distributions.

The track momentum spectrum is well reproduced by this procedure on
the lepton-cut only sample: 
  http://www.slac.stanford.edu/~ursl/talks/070202/trkkill-a1600.eps.gz

There are  residual differences (and  fluctuations in data)  after all
cuts:
  http://www.slac.stanford.edu/~ursl/talks/070202/trkkill-a1610.eps.gz

This is a  bit surprising, I'd have thought that  the tables are after
all cuts.

The  effects of trk  killing are  clearly visible  in the  (fitted and
reco)  MX  distribution,  which  is systematically  shifted  to  lower
values:
  http://www.slac.stanford.edu/~ursl/talks/070202/trkkill-a2420.eps.gz

The agreement between data and MC is better for the unkilled version. 

The charged Trk multiplicity is affected, especially after the lepton
cut: 
  http://www.slac.stanford.edu/~ursl/talks/070202/trkkill-a4300.eps.gz
  http://www.slac.stanford.edu/~ursl/talks/070202/trkkill-a4320.eps.gz

The default setup shows better agreement. 

Note: These plots are a bit different from the BAD, this is due to the
fact that the BAD plots were made with the veryTight muon selector and
these here with tight.

So, technically, I think there no obvious problem with the TrkKilling.

The fits give: 

  Default: BRBR = 0.0167335 +- 0.00446966(stat) +- 0.00127934(MC stat)
  TrkKill: BRBR = 0.0218932 +- 0.00459749(stat) +- 0.00124435(MC stat)

This is  a difference of 31%.  Given the level of  disagreement in the
above distributions, I  would not say that it's a  good estimate for a
systematic. More thinking is required. 


Cheers,
--U.




Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2010
December 2009
August 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use