Thanks David. At runtime you can also set the RIVET_ANALYSIS_PATH to only find a subset of plugins: if you terminate the path variable with a double-colon (::) then it will *not* fall back to searching the $prefix/lib directory for Rivet*.so files.<div><div><br></div><div>Andy</div><br><signature><div><table cellpadding="0" cellspacing="0"><tbody><tr><td colspan="2"><div style="padding-bottom:15px;"><div><strong>Dr Andy Buckley, Lecturer / Royal Society University Research Fellow</strong></div><div>Particle Physics Experiment Group, University of Glasgow</div></div></td></tr><tr><td style="vertical-align:top;"></td><td><div style="font-size:0.9em;white-space:nowrap;border-left:2px solid gray;margin-left:20px;padding-left:20px;"><div><div></div><div></div></div></div></td></tr></tbody></table></div></signature></div>
<div class="gmail_quote nylas-quote nylas-quote-id-aee8372f-b013-075a-0f96-395610578709@durham.ac.uk">
<br>
On Jan 11 2018, at 4:04 pm, David Grellscheid <david.grellscheid@durham.ac.uk> wrote:
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<span></span><body><div style="padding-bottom: 20px;"></div><div>Hi Xavier,<br><br>you can rename some of the folders in "analyses/". If the name does not<br>start with "plugin", the compile will be skipped.<br><br>Are you compiling Rivet in a threaded environment with explicit TLS<br>choices?<br><br>Thanks,<br><br> David<br><br><br>On 11/01/18 15:41, Janssen Xavier wrote:<br><blockquote type="cite"><br>Hi Andy,<br><br>Is there a way I can compile only a few plugins for a quick test to be<br>sure this is a limit problem ?<br><br>Cheers, Xavier,<br><br><br><blockquote type="cite">On 11 Jan 2018, at 16:34, Andy Buckley <andy.buckley@cern.ch<br><mailto:andy.buckley@cern.ch>> wrote:<br><br>Hi Xavier,<br><br>*Very* strange. The analysis loading has not changed at all, but the<br>analysis compilation now uses the rivet-buildplugin script for all the<br>built-in analyses as well as any external ones. I wouldn't expect that<br>to change anything, and it's worked fine on my machine and others...<br>but it is a change.<br><br>I'm no expert on this static TLS thing -- a quick Google suggests that<br>the system is running out of memory due to loading plugins each with<br>their own static memory requirements. Maybe we just crossed some<br>threshold? My recollection is that we load all the lightweight<br>analysis *loader* objects into memory, but only instantiate the actual<br>analysis classes which are requested by the user. Any experts on the<br>list who can suggest diagnostics?<br><br>Andy<br><br>*Dr Andy Buckley, Lecturer / Royal Society University Research Fellow*<br>Particle Physics Experiment Group, University of Glasgow<br> <br><br><br>On Jan 11 2018, at 3:16 pm, Janssen Xavier<br><xavier.janssen@uantwerpen.be <mailto:xavier.janssen@uantwerpen.be>><br>wrote:<br><br><br>Hi,<br><br>I was testing the integration of the latest release in our CMS<br>software. The installation and compilation is working well.<br>However trying to run Rivet to produce some MC events for 1 test<br>analysis I use for validation is failing with the following error:<br><br>unable to load<br>/afs/cern.ch/work/x/xjanssen/cms/Rivet/10X_gcc630_Rivet260/CMSSW_10_0_0_pre3/lib/slc6_amd64_gcc630/pluginGeneratorInterfaceRivetInterface_plugins.so<br><http://cern.ch/work/x/xjanssen/cms/Rivet/10X_gcc630_Rivet260/CMSSW_10_0_0_pre3/lib/slc6_amd64_gcc630/pluginGeneratorInterfaceRivetInterface_plugins.so><br>because dlopen: cannot load any more object with static TLS<br><br>where pluginGeneratorInterfaceRivetInterface_plugins.so is our<br>standard interface to Rivet. Just to be sure I tested back Rivet<br>2.5.4 in the same CMS software release and I don’t get any such<br>problem. Not sure exactly what is happening but what did you<br>exactly changed in the compilation/loading of analysis in the<br>latest release ?<br><br>Cheers, Xavier.<br>_______________________________________________<br>Rivet mailing list<br>Rivet@projects.hepforge.org <mailto:Rivet@projects.hepforge.org><br>https://www.hepforge.org/lists/listinfo/rivet<br></blockquote><br><br><br>_______________________________________________<br>Rivet mailing list<br>Rivet@projects.hepforge.org<br>https://www.hepforge.org/lists/listinfo/rivet<br></blockquote>_______________________________________________<br>Rivet mailing list<br>Rivet@projects.hepforge.org<br>https://www.hepforge.org/lists/listinfo/rivet<br></div></body>
</blockquote>
</div>