[Paraview] Multi-core custom applications

[Burlen Loring]

Hi Utkarsh,

I'm wondering what you think about the idea that multicore use the same 
mechanism as the normal connect to server? Is there a strong reason for 
it to be different? I'm think that when multicore featured is enabled a 
dialog defined by an internal pvsc with some basic options such as 
number of cores and perhaps pvserver location etc is used. This would 
allow the user to make some basic parameter changes and internally make 
the built in multicore runs look the same as any other pvserver run. We 
had discussed this before and you asked me to file a feature request. 
http://paraview.org/Bug/view.php?id=14312

Burlen

On 02/10/2014 06:40 AM, Utkarsh Ayachit wrote:
> Makes sense. May providing static API on the class so that custom
> application to change the location of pvserver may be helpful. What do
> you think? If you want to contribute a patch, I'll be more than happy
> to merge it in.
>
> Utkarsh
>
> On Mon, Feb 10, 2014 at 6:28 AM,  <mathieu.westphal at gmail.com> wrote:
>> Hello
>>
>> it appears, from vtkProcessModuleAutoMPI.cxx n taht pvserver MUST be in the binary dir to be able to use Multi-core option.
>>
>> Shouldn't it be configurable in cmake at least ? and even automatically found by cmake ?
>>
>> Mathieu
>> _______________________________________________
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140210/781ef842/attachment.html>