[Paraview] multiple visualization pipeline at a time with co-processing
Ufuk Utku Turuncoglu (BE)
u.utku.turuncoglu at be.itu.edu.tr
Fri Jul 7 07:30:17 EDT 2017
Hi Andy,
Strange! To test the idea and eliminate other problems i am using same
script twice with little mods (i just changed the name of the output png
file). So, if i pass script_1.py and script_2.py to the model, it gives
warning like before and creates output just for second script
(script_2.py). If i pass only one of them then the code is working
without any problem and produces desired output.
Thanks,
Regards,
--ufuk
On 06/07/2017 18:09, Andy Bauer wrote:
> Hi Ufuk,
>
> I'm guessing the issue is that the calls to Catalyst are not
> consistent. Could you share your Python scripts? Also, did you modify
> them manually?
>
> I tried with PV 5.3. with
> the ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/ example with
> the attached scripts simultaneously by running with "./CxxFullExample
> doubleoutputs.py output3.py image11.py" and got the correct output and
> no warnings.
>
> Cheers,
> Andy
>
> On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE)
> <u.utku.turuncoglu at be.itu.edu.tr
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
> Hi Andy,
>
> I tested you suggestion about using multiple script in
> co-processing. In this case, i used following code in the adaptor
> side to add multiple pipeline
>
> for (int i = 0; i < *nscript; i++) {
> pipeline->Initialize(pythonScriptNames[i]);
> g_coprocessor->AddPipeline(pipeline);
> }
>
> When i run the simulation, i am getting following warning
>
> Warning: In
> /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx,
> line 66
> vtkPVTrivialProducer (0x13816760): New time step is not after last
> time step.
>
> the output seems not correct and it is zoom out version of second
> pipeline (png file). The first pipeline is not even triggered. Do
> i missing something in here? BTW, i am using PV 5.3.
>
> Thanks,
>
> --ufuk
>
>
> On 16/05/2017 16:08, Andy Bauer wrote:
>> Hi Ufuk,
>>
>> If you create a vtkCPythonScriptPipeline, when you initialize it
>> with the script file name (which has to be done on each process)
>> everything will be taken care of with respect to broadcasting the
>> file contents from process 0 to the others. We aren't
>> sophisticated enough to parse the Python script to see if it
>> imports other scripts that are not part of ParaView (e.g.
>> paraview.simple) or Python (e.g. sys). That is why I recommended
>> the first approach as opposed to the second approach above.
>> Depending on the compute platform and how many MPI processes are
>> in the run the difference may be negligible but having 100K
>> processes or more trying to access the same file can seriously
>> slow down an HPC machine.
>>
>> Cheers,
>> Andy
>>
>> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE)
>> <u.utku.turuncoglu at be.itu.edu.tr
>> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>>
>> Thanks Andy. That is exactly what i am looking for. The
>> broadcasting mechanism is not clear to me yet. Do i need to
>> broadcast only the file names? Anyway, i will try to
>> implement it and see what is going on there.
>>
>> Thanks again,
>> Regards,
>>
>> --ufuk
>>
>>
>> On 16/05/2017 14:58, Andy Bauer wrote:
>>> Hi Ufuk,
>>>
>>> Unless I'm not understanding your question correctly, I
>>> think you can get what you want by adding in multiple
>>> vtkCPPythonScriptPipelines to your vtkCPProcessor object in
>>> your adaptor. Alternatively if you want to have a single,
>>> master Catalyst script handling other Catalyst scripts you
>>> can do something like the following:
>>> ================
>>> import script_a
>>> import script_b
>>> import script_c
>>>
>>> def RequestDataDescription(datadescription):
>>> script_a.RequestDataDescription(datadescription)
>>> script_b.RequestDataDescription(datadescription)
>>> script_c.RequestDataDescription(datadescription)
>>>
>>> def DoCoProcessing(datadescription):
>>> script_a.DoCoProcessing(datadescription)
>>> script_b.DoCoProcessing(datadescription)
>>> script_c.DoCoProcessing(datadescription)
>>> ===================
>>>
>>> The first way is the recommended way though as that should
>>> be more efficient by having process 0 read the scripts and
>>> broadcasting the script contents to the other processes for
>>> use. The second method will only do that for the master script.
>>>
>>> Please let me know if this doesn't answer your question.
>>>
>>> Cheers,
>>> Andy
>>>
>>> On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE)
>>> <u.utku.turuncoglu at be.itu.edu.tr
>>> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>>>
>>> Hi All,
>>>
>>> I just wonder that is it possible to trigger multiple
>>> visualization pipeline in the same time with
>>> co-processing. The co-processing script generator plugin
>>> mainly outputs only single pipeline at a time and that
>>> is fine but what about combining multiple Python script
>>> (generated by plugin) using higher level Python script
>>> to trigger multiple pipelines. So, i think that this
>>> will be much efficient way to look at different part of
>>> the data without writing to the disk. I am not sure but
>>> somebody else might do it before.
>>>
>>> Regards,
>>>
>>> --ufuk
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com>
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>> <http://www.kitware.com/opensource/opensource.html>
>>>
>>> Please keep messages on-topic and check the ParaView
>>> Wiki at: http://paraview.org/Wiki/ParaView
>>> <http://paraview.org/Wiki/ParaView>
>>>
>>> Search the list archives at:
>>> http://markmail.org/search/?q=ParaView
>>> <http://markmail.org/search/?q=ParaView>
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>> <http://public.kitware.com/mailman/listinfo/paraview>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: script_1.py
Type: text/x-python-script
Size: 6893 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: script_2.py
Type: text/x-python-script
Size: 6893 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment-0001.bin>
More information about the ParaView
mailing list