<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 6/2/2013 1:15 PM, Biddiscombe, John
A. wrote:<br>
</div>
<blockquote
cite="mid:50320452A334BD42A5EC72BAD2145099085DF97D@MBX10.d.ethz.ch"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">The
reason that the multi-core option doesn’t work is because all
it does is internally spawn N pvservers and connect to them
silently - the client is still a serial process without mpi
enabled or initted (is that a word?).</span></p>
</blockquote>
John, I think you're wrong about that. here's why: when paraview is
running in client server mode, via its internal multicore startup or
otherwise, the reader is constructed on the pvserver not on the
client. and in the these cases pvserver has mpi initted... this is
not to say that you wont crash the client if you're not careful
about making mpi calls in client only mode when mpi is not initted.
so you'd need to avoid mpi calls when mpi is not initted if you want
your reader to place nice with standard pv ... I guess in your case
you need the threaded mpi init too... don't forget to load your
plugin...<br>
</body>
</html>