Hi Hong, I've seen this issue but haven't had the time to fix it. If you can enter this issue in our bug tracker (http://www.paraview.org/Bug/my_view_page.php) and assign it to me, I'll try and fix it.
Regards, Andy On Thu, Jun 5, 2014 at 2:18 PM, Hong Yi <[email protected]> wrote: > In our in-situ run linking our simulation to ParaView Catalyst, I found > an empty line was always printed from each core during Catalyst > initialization (in coprocessorinitializewithpython() call). Although this > is not a big deal, it becomes annoying when running on large number of > cores. I traced the issue down some time ago and it appeared the empty line > was printed from the statement > "vtkPythonInterpreter::RunSimpleString(loadPythonModules.str().c_str());" > in InitializePython() function in vtkCPPythonScriptPipeline.cxx. This empty > line printout occurred in all ParaView versions we have tried including > versions 3.98, 4.0.1, and 4.1.0. I am wondering whether anybody else has > experienced this minor but sometimes annoying issue, and whether I can get > some suggestions/ideas to possibly remove the empty line printout during > Catalyst initialization. > > Thanks, > Hong > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
