Itep Moscow

Posted on December 27, 2011 by Admin
Itep Moscow

Itep Moscow

Hi,

I'm getting the same warning/error for my fit. I'm using root 5.32.00-rc2 (compiled with gcc 4.6.1, on Ubuntu 11.10). I do the following:
Code: Select allint dilepton_mass_fitter_y3s()
{
  TFile * file_1 = new TFile("../rootout/force_cms/systematic_studies_0/fcm_0/plot1_Run7_type12_pidopt1.root");
  TH1D *  hist   = static_cast<TH1D*>(file_1->Get("dileptonmass0_mmnopid"));
  hist->GetYaxis()->SetLabelSize(0.02);
  RooRealVar x("dilepton mass","dilepton mass/#sqrt{s}",0.88,1.03);
  RooDataHist dh("dh","dh",x,hist);

  RooRealVar mean("mean", "mean", 0.99, 0.98, 1.01);
  RooRealVar sigma("sigma", "sigma", 0.001,0.0, 0.1);
  RooRealVar alpha("alpha", "alpha", 1.2, 0.9, 2.0);
  RooRealVar n("n","n", 1, 0, 100);
 
  RooCBShape cball("cball", "Crystal Ball Shape", x, mean, sigma, alpha, n);

  RooRealVar mean_y2("mean_y2", "mean_y2", 0.965, 0.96, 0.97);
  RooRealVar sigma_y2("sigma_y2", "sigma_y2", 0.05, 0.0, 0.1);
  RooGaussian gauss_y2("gauss_y2", "gauss_y2", x, mean_y2, sigma_y2);

  RooRealVar mean_y1("mean_y1", "mean_y1", 0.91, 0.88, 0.93);
  RooRealVar sigma_y1("sigma_y1", "sigma_y1", 0.05, 0.0, 0.1);
  RooGaussian gauss_y1("gauss_y1", "gauss_y1", x, mean_y1, sigma_y1);

  RooRealVar nsig("nsig",  "#Upsilon (3S) events",1000,0.,100000) ;
  RooRealVar nsig1("nsig1","#Upsilson (1S) events",400,0.,100000) ;
  RooRealVar nsig2("nsig2","#Upsilson (2S) events",400,0.,100000) ;
  //RooRealVar nsig3("nsig3","#Upsilson (3S) events",400,0.,100000) ;


//  RooRealVar mean_y3("mean_y3", "mean_y3", 1.00, 0.96, 1.04);
//  RooRealVar sigma_y3("sigma_y3", "sigma_y3", 0.05,0.0, 0.1);
//  RooGaussian gauss_y3("gauss_y3", "gauss_y3", x, mean_y3, sigma_y3);
//  RooAddPdf sum("sum", "cb+g1+g2+g3", RooArgList(cball,gauss_y1,gauss_y2,gauss_y3), RooArgList(nsig,nsig1,nsig2,nsig3));
  RooAddPdf sum("sum", "cb+g1+g2", RooArgList(cball,gauss_y1,gauss_y2), RooArgList(nsig,nsig1,nsig2));

  sum.fitTo(dh, Range(0.88,1.03), Extended(true));
  //cball.fitTo(dh, Range(0.96,1.04));

  RooPlot * frame = x.frame(Name("frame"), Title("Dilepton Mass"));
  frame->SetLabelSize(0.02);
  frame->GetYaxis()->SetLabelSize(0.025);
  frame->GetYaxis()->SetTitleSize(0.04);
  dh.plotOn(frame, DataError(RooAbsData::SumW2)) ;
  sum.plotOn(frame);


  frame->Draw();
  gPad->SetLeftMargin(0.15) ; frame->GetYaxis()->SetTitleOffset(1.5);
  gPad->SaveAs("dilepton_mass/dilepton_mass_y3s.eps");
  gPad->SaveAs("dilepton_mass/dilepton_mass_y3s.png");

  RooArgSet * params = sum.getParameters(x);
  params->printLatex();
 
  return 0;
}


I've narrowed the problematic bit of code to:
Code: Select allsum.fitTo(dh, Range(0.88,1.03), Extended(true));

If I changed Extended(true) to Extended(false), the macro runs and produces a fit. I'm unsure if this is a general problem with using the Extended(true) -- or if I'm just not doing the fit properly.

Cheers,

Greg

Institute for Theoretical and Experimental Physics (ITEP), Moscow

Posted: October 12, 2010 | Author: petrstepanov | Filed under: Daily Stuff |Leave a comment »

Hola!

My name is Petr. I am a student at the MEPhI university in Moscow. I stay extremely patient about data transfer security and I always take care of the software and hardware. This why I use only Linux-based operating systems on my ASUS eeePC 1000HA.

I’m running 6th course now and be sure I will graduate this winter. Our chair is called “The chair of Extreme Conditions of Substance”.

Of course, nowdays tons of useful articles, reference literature and other useful media is placed in the World Wide Web. So the styding process  is closely connected with the internet. There is only one problem – it’s a WEP-protected wall that divides me and the Internet. God Damn! I’ve tryed almost everything.

First of all there was just a dialogue. Then, later a serious talk with the chair heads… then a please… and finally, even a request letter.

Unfortunately, no answer. I have really came fed up facing such hopeless fails.

Today I’ve decided to follow these steps.

  1. Download BackTrack Linux.
  2. Crack all ITEP WEP-Protected Wi-Fi networks.
  3. Be afraid, Windows-users, here comes a tiny worm!

P.S.: keep in mind if knowing how to pick a lock doesn’t make you a thief. Consider this post educational, or an intellectual exercise.