<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> Dear all, <div class=""><br class=""> </div> <div class="">Great! Thank you very much for your help!</div> <div class=""><br class=""> </div> <div class="">Cheers,</div> <div class="">Hans</div> <div class=""><br class=""> </div> <div class=""><br class=""> <div> <blockquote type="cite" class=""> <div class="">On 28 Feb 2017, at 18:06, Sercan Sen <<a href="mailto:Sercan.Sen@cern.ch" class="">Sercan.Sen@cern.ch</a>> wrote:</div> <br class="Apple-interchange-newline"> <div class=""> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div class=""><br class=""> </div> Hi Andy, Leif, <div class=""><br class=""> </div> <div class=""> <blockquote type="cite" class="">Let me know if this solves your problem, and if so I/we will apply it to the development version that'll become Rivet 2.5.4.<br class=""> </blockquote> <div class=""><br class=""> </div> <div class="">I use this patch with Rivet 2.5.3 and it solves the problem. Thanks for implementing the patch in the next release. </div> <div class=""><br class=""> </div> <div class="">Cheers, </div> <div class="">Sercan</div> <div class=""> <div class=""><br class="webkit-block-placeholder"> </div> <div class=""> <div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""> <div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""> <br class=""> </div> </div> </div> </div> </div> </div> <br class=""> <div class=""> <blockquote type="cite" class=""> <div class="">On Feb 28, 2017, at 6:36 PM, Andy Buckley <<a href="mailto:a.g.buckley@gmail.com" class="">a.g.buckley@gmail.com</a>> wrote:</div> <br class="Apple-interchange-newline"> <div class=""> <div class="">Hi Hans & Sercan,<br class=""> <br class=""> Actually, Leif understood this faster than I did, and has posted a patch below. Unfortunately his email only went to the Rivet list, so you didn't see it!<br class=""> <br class=""> Let me know if this solves your problem, and if so I/we will apply it to the development version that'll become Rivet 2.5.4.<br class=""> <br class=""> Andy<br class=""> <br class=""> <br class=""> -------- Forwarded Message --------<br class=""> Subject: Re: [Rivet] Use proton-lead MC generators with Rivet<br class=""> Date: Tue, 28 Feb 2017 12:43:36 +0100<br class=""> From: Leif Lönnblad <<a href="mailto:leif.lonnblad@thep.lu.se" class="">leif.lonnblad@thep.lu.se</a>><br class=""> Reply-To: <a href="mailto:leif.lonnblad@thep.lu.se" class="">leif.lonnblad@thep.lu.se</a><br class=""> Organisation: Theoretical Physics, Lund University<br class=""> To: <a href="mailto:rivet@projects.hepforge.org" class="">rivet@projects.hepforge.org</a><br class=""> <br class=""> Hi Hans,<br class=""> <br class=""> There is actually a flag for rivet to --ignore-beams, but it only prevents checks that the different analyses included requires the same beams. It doesn't seem unreasonable to me if the checking of beams in the code you pointed to was switched off if --ignore-beams is given, ie.<br class=""> <br class=""> if ( !_ignoreBeams ) {<br class=""> // Ensure that beam details match those from the first event<br class=""> const PdgIdPair beams = Rivet::beamIds(ge);<br class=""> const double sqrts = Rivet::sqrtS(ge);<br class=""> if (!compatible(beams, _beams) || !fuzzyEquals(sqrts, sqrtS())) {<br class=""> cerr << "Event beams mismatch: "<br class=""> << PID::toBeamsString(beams) << " @ " << sqrts/GeV<br class=""> << " GeV" << " vs. first beams "<br class=""> << this->beams() << " @ " << this->sqrtS()/GeV<br class=""> << " GeV" << endl;<br class=""> exit(1);<br class=""> }<br class=""> }<br class=""> <br class=""> Of course, individual analyses may still fail if they require specific beams.<br class=""> <br class=""> <br class=""> /Leif<br class=""> <br class=""> On 2017-02-28 12:10, Hans Jozef H Van Haevermaet wrote:<br class=""> <blockquote type="cite" class="">Dear Rivet authors,<br class=""> <br class=""> I am a member of CMS (forward and small-x community in fact), and I’m<br class=""> trying to get Rivet running with proton-lead events coming from the EPOS<br class=""> MC generator.<br class=""> It turns out however, that this is not possible (?).<br class=""> When executing Rivet, it stops because it detected that the incoming<br class=""> beams are different for each event:<br class=""> Event beams mismatch: [PROTON, PROTON] @ 1.87656 GeV vs. first beams<br class=""> [NEUTRON @ 2511.57 GeV, NEUTRON @ 2511.57 GeV] @ 1.87914 GeV<br class=""> <br class=""> This in turn, is caused by the fact that the EPOS generator writes out<br class=""> the interacting nucleon (p or n) in the HEPMC file, and not the particle<br class=""> id code of lead itself.<br class=""> <br class=""> Could you let us know if it is possible for Rivet to get compatible with<br class=""> these kind of situations?<br class=""> One direct option (for me) is to comment out this function:<br class=""> <a href="https://rivet.hepforge.org/code/dev/AnalysisHandler_8cc_source.html" class="">https://rivet.hepforge.org/code/dev/AnalysisHandler_8cc_source.html</a><br class=""> At line 95.<br class=""> <br class=""> But that can lead to unwanted behaviour in other cases, I guess. Maybe<br class=""> one can include a parameter to turn this check on/off? So that it is the<br class=""> user’s responsibility? i.e. by default the check is done, but the user<br class=""> can turn it off manually if needed.<br class=""> <br class=""> It would be very good to solve this incompatibility, since in CMS we try<br class=""> to get Rivet routines from all our analyses, and it would be nice to be<br class=""> able to extend this to proton-lead, or even lead-lead measurements. As<br class=""> far as I can see on the web, I did not find any Heavy Ion analysis<br class=""> implemented in Rivet?<br class=""> <br class=""> Thanks!<br class=""> Best Regards,<br class=""> Hans<br class=""> <br class=""> <br class=""> <br class=""> <br class=""> _______________________________________________<br class=""> Rivet mailing list<br class=""> <a href="mailto:Rivet@projects.hepforge.org" class="">Rivet@projects.hepforge.org</a><br class=""> <a href="https://www.hepforge.org/lists/listinfo/rivet" class="">https://www.hepforge.org/lists/listinfo/rivet</a><br class=""> <br class=""> </blockquote> <br class=""> <br class=""> _______________________________________________<br class=""> Rivet mailing list<br class=""> <a href="mailto:Rivet@projects.hepforge.org" class="">Rivet@projects.hepforge.org</a><br class=""> <a href="https://www.hepforge.org/lists/listinfo/rivet" class="">https://www.hepforge.org/lists/listinfo/rivet</a><br class=""> </div> </div> </blockquote> </div> <br class=""> </div> </div> </div> </div> </blockquote> </div> <br class=""> </div> </body> </html>