<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> </head> <body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <div><br class="webkit-block-placeholder"> </div> <div>Hello Frank, </div> <div><br> </div> <div>I didn't run this analysis before. However, I have been running some other analyses and add this one to the chain now to see if there is any difference. </div> <div><br> </div> <div>I've just run over 150K events (INEL Z2*) both the previous version and the new version in the trunk, but there is no event survive. Most of the events are rejected by the flightDistance cut of Kaon/Lambda which always returns as 1e+07. with hepmc 2.06.08 and unit is mm..</div> <div><br> </div> <div>Just for my curiosity, I debug a little bit and return the pdg id of the particle from getPerpFlightDistance function where it truly returns this before the "if (decV)" scope. Events never go inside decV scope and therefore the value of the flighttd which is 1e+07 is dummy in the current code. So, all events are failed... </div> <div><br> </div> <div>by the way, as expected we have more events after the correction on the MBTS cuts and I think this will not be only statistical effect. </div> <div><br> </div> <div>* ==================</div> <div><br> </div> <div>OLD VERSION</div> <div><br> </div> <div> <div>Cross-section = 7.130367e+10 pb</div> <div>Rivet.Analysis.Handler: INFO Finalising analyses</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Events that pass the trigger: 112103</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Kshort events: 0</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Lambda events: 0</div> <div>Rivet.Analysis.Handler: INFO Processed 150000 events</div> </div> <div><br> </div> <div>NEW VERSION</div> <div><br> </div> <div> <div>Cross-section = 7.130367e+10 pb</div> <div>Rivet.Analysis.Handler: INFO Finalising analyses</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Events that pass the trigger: 127174</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Kshort events: 0</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO Lambda events: 0</div> <div>Rivet.Analysis.ATLAS_2011_I944826: INFO This is the modified analysis, revision 3975</div> <div>Rivet.Analysis.Handler: INFO Processed 150000 events</div> </div> <div><br> </div> <div>Thanks, </div> <div>Sercan </div> <div><br class="webkit-block-placeholder"> </div> <div><br> </div> <div><br> </div> <div> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <font class="Apple-style-span" color="#7c7c7c"><br> </font></div> </div> </div> <br> <div> <div>On Oct 25, 2012, at 3:36 PM, Frank Siegert wrote:</div> <br class="Apple-interchange-newline"> <blockquote type="cite"> <div>Hi Sercan,<br> <br> Thanks again for the feedback. I have implemented the changes in changeset 3975:<br> <br> <a href="http://rivet.hepforge.org/trac/changeset/3975">http://rivet.hepforge.org/trac/changeset/3975</a><br> <br> I don't have any possibility to test whether this does something<br> significantly different from before though. Sercan or Holger, since<br> you are probably the only two on this list who have run this analysis<br> before, do you have any chance to check with these changes?<br> <br> Cheers,<br> Frank<br> <br> On 24 October 2012 11:31, Sercan Sen <<a href="mailto:Sercan.Sen@cern.ch">Sercan.Sen@cern.ch</a>> wrote:<br> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Hi Frank,<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">what about the "nstable" requirement... does that only look at<br> </blockquote> <blockquote type="cite">particles >100 MeV?<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">yes, this is what I understand from the paper -- and it's reasonable.<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">trigger cut is 2.09 < |\eta| < 3.84<br> </blockquote> <blockquote type="cite">analysis cuts: |\eta| < 2.5, 100*MeV, ....<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">I think the best way is to use another projection for the trigger<br> </blockquote> <blockquote type="cite">requirement.<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Cheers,<br> </blockquote> <blockquote type="cite">Sercan<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">On Oct 23, 2012, at 3:47 PM, Frank Siegert wrote:<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Hi Sercan,<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Right. "nstable" part should be in |\eta| < 2.5 . So, if we extend the<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">rapidity acceptance in the CFS projection, then we should apply a rapidity<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">cut in the "nstable" part..<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Thanks for the clarification.<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">By the way, I don't know if we need 100*MeV for ATLAS MBTS requirement (this<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">is applied in the current code) ? Probably, we don't need it but this should<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">be checked by someone from ATLAS..<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Then again the same follow-up question: If the 100 MeV is not<br> </blockquote> <blockquote type="cite">necessary for the MBTS trigger requirement (pending confirmation by<br> </blockquote> <blockquote type="cite">Emily), what about the "nstable" requirement... does that only look at<br> </blockquote> <blockquote type="cite">particles >100 MeV?<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite">Cheers,<br> </blockquote> <blockquote type="cite">Frank<br> </blockquote> <blockquote type="cite"><br> </blockquote> <blockquote type="cite"><br> </blockquote> </div> </blockquote> </div> <br> </body> </html>