<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear David, <div class=""> </div><div class="">You are right on the issue here. Somehow, on a latest Mac, I ended up having some very old libraries, which I have no idea how it happened. I plan on getting back to this in a few days and figure out what went wrong and possibly do a re-install of pretty much everything. <div class=""> <div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli <a href="mailto:raghavke@wayne.edu" class="">email: raghavke@wayne.edu</a> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** </div></div> </div> <div> <blockquote type="cite" class=""><div class="">On Jan 23, 2018, at 9:53 AM, David Grellscheid <<a href="mailto:david.grellscheid@durham.ac.uk" class="">david.grellscheid@durham.ac.uk</a>> wrote:</div> <div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Hi Raghav,<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I don't know how far you got, but I just noticed this line<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" 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-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">clang: warning: libstdc++ is deprecated; move to libc++ </blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">which I'm a bit worried about. This indicates that you have a really old<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">set of C++ libraries on your system, since Apple stopped using libstdc++<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">ages ago. This confusion of libraries could explain many of the symptoms<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">you're seeing. The default compilers on OS X should be CC=clang<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">CXX=clang++. For me, the Fortran compiler from Macports has always<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">worked without any problems.<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""> David<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">On 19/01/2018 14:53, Kunnawalkam Raghav wrote:<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" 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-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">Just FYI: I have the latest Mac osx 10.13.2 but if you see below, it says temp-macosx-10.6!? I just managed to get them installed a few days ago but now nothing seems to work/Install. Raghavs-MacBook-Pro:RIVET raghavke$ gcc -v Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 9.0.0 (clang-900.0.39.2) Target: x86_64-apple-darwin17.3.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin Raghavs-MacBook-Pro:RIVET raghavke$ And here is the full log from trying to install Yoda. Thanks a lot for any help guys! Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email: <a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 19, 2018, at 9:43 AM, Kunnawalkam Raghav <<a href="mailto:kunnawalkamraghav@gmail.com" class="">kunnawalkamraghav@gmail.com</a> <<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>>> wrote: Hi David and Andy, Yeah I understand how that works now. Unfortunately I think I totally messed up something on my Mac laptop and now I can’t get the rivet bootstrap to finish. It breaks at the Yoda step with something that I didn’t see before! I feel like my gcc and g++ are kinda totally messed up. I tried this with yoda1.6 and 1.7 with the same results. building 'yoda.util' extension creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7 creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0 creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda g++ -std=c++11 -fno-strict-aliasing -I/Users/raghavke/anaconda2/include -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DNDEBUG -I/usr/include -I/usr/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda -I/Users/raghavke/anaconda2/include/python2.7 -c /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/util.cpp -o /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/util.o -O3 -Wno-sign-compare -Wno-strict-prototypes g++ -std=c++11 -bundle -undefined dynamic_lookup -L/Users/raghavke/anaconda2/lib -DNDEBUG -I/usr/include -I/usr/include -arch x86_64 /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/util.o -L/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/src/.libs -L/Users/raghavke/anaconda2/lib -lstdc++ -lYODA -o /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/lib.macosx-10.6-x86_64-2.7/yoda/util.so -L/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/src/.libs clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 [-Wdeprecated] clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 [-Wdeprecated] building 'yoda.core' extension creating /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/yoda g++ -std=c++11 -fno-strict-aliasing -I/Users/raghavke/anaconda2/include -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DNDEBUG -I/usr/include -I/usr/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda -I/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda -I/Users/raghavke/anaconda2/include/python2.7 -c /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp -o /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/build/temp.macosx-10.6-x86_64-2.7/Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.o -O3 -Wno-sign-compare -Wno-strict-prototypes In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp:462: In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Point.h:9: /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/AnalysisObject.h:157:60: error: no member named 'max_digits10' in 'std::numeric_limits<double>'; did you mean 'digits10'? ss << std::setprecision(std::numeric_limits<double>::max_digits10) << std::scientific << value; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~ digits10 /usr/include/c++/4.2.1/limits:1049:24: note: 'digits10' declared here static const int digits10 = __DBL_DIG__; ^ In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp:462: In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Point.h:9: /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/AnalysisObject.h:166:60: error: no member named 'max_digits10' in 'std::numeric_limits<double>'; did you mean 'digits10'? ss << std::setprecision(std::numeric_limits<double>::max_digits10) << std::scientific << value; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~ digits10 /usr/include/c++/4.2.1/limits:1049:24: note: 'digits10' declared here static const int digits10 = __DBL_DIG__; ^ In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp:462: In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Point.h:9: /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/AnalysisObject.h:175:60: error: no member named 'max_digits10' in 'std::numeric_limits<double>'; did you mean 'digits10'? ss << std::setprecision(std::numeric_limits<double>::max_digits10) << std::scientific << value; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~ digits10 /usr/include/c++/4.2.1/limits:1049:24: note: 'digits10' declared here static const int digits10 = __DBL_DIG__; ^ In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp:476: In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Counter.h:11: /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Scatter1D.h:29:18: error: no type named 'shared_ptr' in namespace 'std' typedef std::shared_ptr<Scatter1D> Ptr; ~~~~~^ /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Scatter1D.h:29:28: error: expected member name or ';' after declaration specifiers typedef std::shared_ptr<Scatter1D> Ptr; ~~~~~~~~~~~~~~~~~~~~~~~^ In file included from /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/pyext/yoda/core.cpp:476: /Users/raghavke/WORK/UTILS/RIVET/YODA-1.7.0/include/YODA/Counter.h:16:10: fatal error: 'tuple' file not found #include <tuple> ^~~~~~~ 6 errors generated. error: command 'g++' failed with exit status 1 make[2]: *** [all-local] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Raghavs-MacBook-Pro:RIVET raghavke$ Raghavs-MacBook-Pro:RIVET raghavke$ Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email: <a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 19, 2018, at 8:19 AM, David Grellscheid <<a href="mailto:david.grellscheid@durham.ac.uk" class="">david.grellscheid@durham.ac.uk</a> <<a href="mailto:david.grellscheid@durham.ac.uk" class="">mailto:david.grellscheid@durham.ac.uk</a>>> wrote: Hi Raghav, you found it :) The handler() is not available in the constructor of an analysis, and I just realised that there's currently no way to set "ignore beams" from inside an analysis. You should use the --ignore-beams command line flag instead. I'll need to dicuss with the other Riveters how we can make this clearer programatically. See you, David On 18/01/2018 18:49, Kunnawalkam Raghav wrote: <blockquote type="cite" class="">Hey guys, Based on the stack trace, I commented out the line I had in my analysis constructor /// Constructor LUND_JETIMAGE(string name = "LUND_JETIMAGE") : Analysis(name) { _delRMin = 0.08; setNeedsCrossSection(true); // handler().setIgnoreBeams(true); } And then when I run rivet it works fine. I originally included that ignore beams because when we run PbPb with our JEWEL generator, we might end up having proton-neutron collisions based on the isospin probability. Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email: <a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 18, 2018, at 1:13 PM, Andy Buckley <<a href="mailto:andy.buckley@cern.ch" class="">andy.buckley@cern.ch</a> <<a href="mailto:andy.buckley@cern.ch" class="">mailto:andy.buckley@cern.ch</a>>> wrote: Hi Raghav, "rivet" is a Python script rather than a binary executable, which makes gdb unhappy. Replace "rivet" with "$(which python) $(which rivet)" in that command and I think it should work -- I use something like that. You will need a little gdb familiarity as well, but the most useful thing is probably just to send us the output you get from executing the "bt" command after the crash. Andy Dr Andy Buckley, Lecturer / Royal Society University Research Fellow Particle Physics Experiment Group, University of Glasgow On Jan 18 2018, at 6:08 pm, Kunnawalkam Raghav <<a href="mailto:kunnawalkamraghav@gmail.com" class="">kunnawalkamraghav@gmail.com</a> <<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>>> wrote: Hi David, I tried the first one and it still gave me a segmentation fault 11. For the second one, im not familiar with gdb but it doesn’t look like its running? Raghavs-MacBook-Pro:Analysis raghavke$ gdb --args rivet -a LUND_JETIMAGE Job_jewel_PPYQ_pp_1.hepmc -H test.yoda GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html%3Chttp://gnu.org/licenses/gpl.html%3E" class="">http://gnu.org/licenses/gpl.html<http://gnu.org/licenses/gpl.html></a>> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-apple-darwin17.0.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: <<a href="http://www.gnu.org/software/gdb/bugs/%3Chttp://www.gnu.org/software/gdb/bugs/%3E" class="">http://www.gnu.org/software/gdb/bugs/<http://www.gnu.org/software/gdb/bugs/></a>>. Find the GDB manual and other documentation resources online at: <<a href="http://www.gnu.org/software/gdb/documentation/%3Chttp://www.gnu.org/software/gdb/documentation/%3E" class="">http://www.gnu.org/software/gdb/documentation/<http://www.gnu.org/software/gdb/documentation/></a>>. For help, type "help". Type "apropos word" to search for commands related to "word"... "/Users/raghavke/WORK/UTILS/local/bin/rivet": not in executable format: File format not recognized (gdb) run Starting program: -a LUND_JETIMAGE Job_jewel_PPYQ_pp_1.hepmc -H test.yoda No executable file specified. Use the "file" or "exec-file" command. (gdb) It doesn’t like to run rivet? Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email:<a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 18, 2018, at 12:41 PM, David Grellscheid <<a href="mailto:david.grellscheid@durham.ac.uk" class="">david.grellscheid@durham.ac.uk</a> <<a href="mailto:david.grellscheid@durham.ac.uk" class="">mailto:david.grellscheid@durham.ac.uk</a>><<a href="mailto:david.grellscheid@durham.ac.uk" class="">mailto:david.grellscheid@durham.ac.uk</a>>> wrote: Hi, two things to try: (1) First, unset RIVET_ANALYSIS_PATH, then copy the .so file with your analysis into the working directory with the hepmc file. Then do sth like rivet --pwd -a LUND_IMAGE something.hepmc Please let me know if this works or not (2) In a setup where you get the segfault, run gdb --args rivet -a ....the usual command line... Inside gdb, type 'run'. When the segfault hits, type 'backtrace' and send the output Thanks, David On 18/01/2018 15:33, Kunnawalkam Raghav wrote: <blockquote type="cite" class="">Hi David, Yeah I recompiled all of my analyses and essentially im starting from the beginning in a new computer. I think the issue might be with python or the different versions of python that I have going around. Take a look at the setup below Raghavs-MacBook-Pro:~ raghavke$ which rivet /Users/raghavke/WORK/UTILS/local/bin/rivet Raghavs-MacBook-Pro:~ raghavke$ rivet --version rivet v2.5.4 Raghavs-MacBook-Pro:~ raghavke$ rivet --list-analyses Segmentation fault: 11 Raghavs-MacBook-Pro:~ raghavke$ echo $PYTHONPATH /Users/raghavke/WORK/UTILS/local/lib/python2.7/site-packages:/Users/raghavke/WORK/UTILS/local/lib/python2.7/site-packages:/usr/local/Cellar/root/6.10.08/lib/root Raghavs-MacBook-Pro:~ raghavke$ python Python 2.7.14 |Anaconda custom (64-bit)| (default, Oct 5 2017, 02:28:52) [GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin Type "help", "copyright", "credits" or "license" for more information. <blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">import rivet </blockquote></blockquote></blockquote>Raghavs-MacBook-Pro:~ raghavke$ echo $RIVET_ANALYSIS_PATH /Users/raghavke/WORK/MC/Analysis/ Raghavs-MacBook-Pro:~ raghavke$ cd $RIVET_ANALYSIS_PATH Raghavs-MacBook-Pro:Analysis raghavke$ rivet-buildplugin <a href="http://rivetlund_jetimage.solund_jetimage.cc/" class="">RivetLUND_JETIMAGE.soLUND_JETIMAGE.cc</a> <<a href="http://lund_jetimage.cc/" class="">http://lund_jetimage.cc/</a>><<a href="http://lund_jetimage.cc/" class="">http://lund_jetimage.cc/</a>> /usr/bin/g++ -std=c++11 -o "RivetLUND_JETIMAGE.so" -undefined dynamic_lookup -bundle -I/Users/raghavke/WORK/UTILS/local/include -I/Users/raghavke/WORK/UTILS/local/include -I/Users/raghavke/WORK/UTILS/local/include -I/Users/raghavke/WORK/UTILS/local/include -I/Users/raghavke/WORK/UTILS/local/include -Dunix -pedantic -Wall -Wno-long-long -Wno-format -Werror=uninitialized -Werror=delete-non-virtual-dtor -O2 -L/Users/raghavke/WORK/UTILS/local/lib -L/Users/raghavke/WORK/UTILS/local/lib -L/Users/raghavke/WORK/UTILS/local/lib -Wl,-rpath,/Users/raghavke/WORK/UTILS/local/lib -lm -L/Users/raghavke/WORK/UTILS/local/lib -lfastjettools -lfastjet -lfastjetplugins -lsiscone_spherical -<a href="http://lsisconelund_jetimage.cc/" class="">lsisconeLUND_JETIMAGE.cc</a> <<a href="http://lund_jetimage.cc/" class="">http://lund_jetimage.cc/</a>><<a href="http://lund_jetimage.cc/" class="">http://lund_jetimage.cc/</a>> -lRivet Raghavs-MacBook-Pro:Analysis raghavke$ rivet -a LUND_IMAGE #(tab complete doesnt work) Raghavs-MacBook-Pro:Analysis raghavke$ rivet -a LUND_IMAGE /Volumes/Storage/cernbox/JEWEL/PPYQ_2760/Job_jewel_PPYQ_pp_1.hepmc -H test.yoda Segmentation fault: 11 Raghavs-MacBook-Pro:Analysis raghavke$ rivet -a LUND_IMAGE --pwd /Volumes/Storage/cernbox/JEWEL/PPYQ_2760/Job_jewel_PPYQ_pp_1.hepmc -H test.yoda Segmentation fault: 11 Raghavs-MacBook-Pro:Analysis raghavke$ Even the list analyses doesn’t seem to work. But now if I unset the rivet analysis path variable then that command works but the analysis doesn’t even run. Like it doesn’t even show the beginning setup etc.. very weird! Raghavs-MacBook-Pro:~ raghavke$ which rivet /Users/raghavke/WORK/UTILS/local/bin/rivet Raghavs-MacBook-Pro:~ raghavke$ rivet --version rivet v2.5.4 Raghavs-MacBook-Pro:~ raghavke$ rivet --list-analyses ALEPH_1991_S2435284 Hadronic Z decay charged multiplicity measurement ALEPH_1995_I382179 Inclusive pi+-, K+- and (p, anti-p) differential cross-sections at the Z resonance ALEPH_1996_S3196992 Measurement of the quark to photon fragmentation function ALEPH_1996_S3486095 Studies of QCD with the ALEPH detector. ALEPH_1999_S4193598 Scaled energy distribution of D* at LEP ALEPH_2001_S4656318 Study of the fragmentation of b quarks into B mesons at the Z peak ALEPH_2002_S4823664 η and ω Production in Hadronic Z⁰ Decays … Raghavs-MacBook-Pro:Analysis raghavke$ rivet --pwd -a LUND_IMAGE /Volumes/Storage/cernbox/JEWEL/PPYQ_2760/Job_jewel_PPYQ_pp_1.hepmc -H test.yoda Segmentation fault: 11 Raghavs-MacBook-Pro:Analysis raghavke$ Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email:<a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 18, 2018, at 10:22 AM, David Grellscheid <<a href="mailto:david.grellscheid@durham.ac.uk" class="">david.grellscheid@durham.ac.uk</a> <<a href="mailto:david.grellscheid@durham.ac.uk" class="">mailto:david.grellscheid@durham.ac.uk</a>><<a href="mailto:david.grellscheid@durham.ac.uk" class="">mailto:david.grellscheid@durham.ac.uk</a>>> wrote: Hi Raghav, Please check that you have recompiled all of your analyses in the ANALYSIS_PATH with the new version of rivet-buildplugin. This is necessary whenever a major Rivet version change happens. Thanks, David On 17/01/2018 18:49, Kunnawalkam Raghav wrote: <blockquote type="cite" class="">So if I unset my RIVET_ANALYSIS_PATH, rivet —list-analyses works fine. Then when I try to run my own analysis with the —pwd, I get the same error Segmentation Fault 11, without any additional information. Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email:<a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 17, 2018, at 1:42 PM, Kunnawalkam Raghav <<a href="mailto:kunnawalkamraghav@gmail.com" class="">kunnawalkamraghav@gmail.com</a> <<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>><<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>>> wrote: So upon a bit of googling, I see that this seems to have been addressed in this thread <a href="https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html%3Chttps://www.hepforge.org/lists-archive/rivet/2016-July/007033.html%3E" class="">https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html<https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html></a> <<a href="https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html%3Chttps://www.hepforge.org/lists-archive/rivet/2016-July/007033.html%3E" class="">https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html<https://www.hepforge.org/lists-archive/rivet/2016-July/007033.html></a>> but im not sure I understand the solution here. And the issue being connected to the $RIVET_ANALYSIS_PATH. So what is the current acceptable procedure? Usually I have one directly where I have all my analysis and include that to my RIVET_ANALYSIS_PATH and things worked fine. Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email:<a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** <blockquote type="cite" class="">On Jan 17, 2018, at 1:36 PM, Kunnawalkam Raghav <<a href="mailto:kunnawalkamraghav@gmail.com" class="">kunnawalkamraghav@gmail.com</a> <<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>><<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>> <<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a><<a href="mailto:kunnawalkamraghav@gmail.com" class="">mailto:kunnawalkamraghav@gmail.com</a>>>> wrote: Hi Rivet Experts, I just tried a couple of fresh rivet install on my MacBook Pro, ubuntu machine and on our local grid here at WSU and in all places, it looks like the bootstrap script worked but when I try to run any analysis or even ask for the list of analysis, I just get a segmentation fault! I understand this is not much to go on but im not even sure where to search for errors about this issue? Any help would be much appreciated. Thanks a lot! Raghavs-MacBook-Pro:Analysis raghavke$ rivet --list-analyses Segmentation fault: 11 Cheers Raghav ************************************** Raghav Kunnawalkam Elayavalli email:<a href="mailto:raghavke@wayne.edu" class="">raghavke@wayne.edu</a> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>> <<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a><<a href="mailto:raghavke@wayne.edu" class="">mailto:raghavke@wayne.edu</a>>> Post Doctoral Fellow Wayne State University 666 W Hancock St. RM 314 Detroit MI. 48201 ************************************** </blockquote> </blockquote> _______________________________________________ Rivet mailing list <a href="mailto:Rivet@projects.hepforge.org" class="">Rivet@projects.hepforge.org</a> <<a href="mailto:Rivet@projects.hepforge.org" class="">mailto:Rivet@projects.hepforge.org</a>><<a href="mailto:Rivet@projects.hepforge.org" class="">mailto:Rivet@projects.hepforge.org</a>> <a href="https://www.hepforge.org/lists/listinfo/rivet" class="">https://www.hepforge.org/lists/listinfo/rivet</a> </blockquote></blockquote> </blockquote></blockquote> _______________________________________________ Rivet mailing list <a href="mailto:Rivet@projects.hepforge.org" class="">Rivet@projects.hepforge.org</a> <<a href="mailto:Rivet@projects.hepforge.org" class="">mailto:Rivet@projects.hepforge.org</a>> <a href="https://www.hepforge.org/lists/listinfo/rivet" class="">https://www.hepforge.org/lists/listinfo/rivet</a></blockquote></blockquote></blockquote></blockquote></blockquote></div></blockquote></div> </div></body></html>