[Paraview] Cataylst pipeline not updating
Andy Bauer
andy.bauer at kitware.com
Mon Feb 13 10:58:28 EST 2017
Oops, datadescription.GetTime() instead of datadescription.GetCurrentTime().
On Mon, Feb 13, 2017 at 10:56 AM, Andy Bauer <andy.bauer at kitware.com> wrote:
> Hi Tim,
>
> Try adding in the current time to the UpdatePipeline() calls, e.g.
> *.UpdatePipeline(datadescription.GetCurrentTime())
>
> It's tough to tell with RequestDataDescription() missing but I assume that
> DoCoProcessing() is getting called when you want, correct?
>
> Let me know if that doesn't solve the problem.
>
> Best,
> Andy
>
> On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P <
> tim.gallagher at gatech.edu> wrote:
>
>> Back with another question!
>>
>>
>> I have a pipeline that has 1 input and 4 outputs. The simplest is a
>> IntegrateVariables filter hooked up to the input. Another branch of the
>> pipeline goes through several PythonCalculator filters and a
>> CellDataToPointData filter and then arrives at the three outputs:
>>
>>
>> 1. The CD2PD filter is connected to a Contour filter with a single level,
>> X. This is then connected to an IntegrateVariables filter (used to compute
>> the area of the Contour) and a Writer.
>>
>> 2. The CD2PD filter is also connected to another Contour filter with a
>> single level Y. This is connected to an IntegrateVariables and Writer just
>> as in 1.
>>
>> 3. The CD2PD filter is sliced two times with each slice in a different
>> render view to save images.
>>
>>
>> I have the coprocessor running every delta_t seconds. The initial
>> IntegrateVariables filter is updated with UpdatePipeline and then the
>> values are saved to disk. This works every step, no issues.
>>
>>
>> I then call UpdatePipeline on both of the Contour and both of the
>> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the
>> IntegrateVariables exceeds a threshold, and if it does, I save the
>> Contour's to disk as a VTK file. This is not working correctly.
>>
>>
>> If I start the simulation from a point where the Contour's exist in the
>> flow already, then everything works great and the Area field changes in
>> time and it saves the Contour's.
>>
>>
>> However, if the simulation starts without the Contours already in the
>> flow, the Area fields stay zero forever. It's as if the pipeline isn't
>> updating or something. I have attached the DoCoProcessing function used. I
>> don't see anything immediately obvious that would prevent it from updating
>> or getting the correct values for the Area.
>>
>>
>> Am I missing something about how the pipeline or contour filters update?
>>
>>
>> Thanks,
>>
>>
>> Tim
>>
>> _______________________________________________
>> 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
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170213/37155373/attachment.html>
More information about the ParaView
mailing list