[Paraview] Volume Rendering Issues/Bugs

[Utkarsh Ayachit]

Mohamed,

If you can share the dataset, it will be easier to point you in the right
direction. Feel free to share the data off the mailing list, if needed.

Utkarsh

On Fri, Mar 30, 2018 at 10:31 AM, Mohamed Beshr <mbeshr1986 at gmail.com>
wrote:

> It is much better now. However, now the tube becomes one solid red color
> although the legend range is the same (see screenshot below for difference
> between original and re-sampled view). Please advise how can I fix this (I
> changed opacity scale shown in the figure between 0 and 1 and still the
> same).
>
>
>
>
>
> On Thu, Mar 29, 2018 at 5:43 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> You're getting an empty cubiod because it's showing as outline. Try
>> changing the "representation" type to Volume from Outline. Is that any
>> better? You may need to adjust your color/opactiy transfer function.
>>
>>
>>
>> On Thu, Mar 29, 2018 at 2:49 PM, Mohamed Beshr <mbeshr1986 at gmail.com>
>> wrote:
>> > Thank you for your reply. Yes I have an unstructured grid. Regarding the
>> > resample to image filter, when I select it in my case, I get an empty
>> > cuboid. Why is that? Is there a way to get the image matching my shape?
>> >
>> > On Mon, Mar 26, 2018 at 3:38 PM, Utkarsh Ayachit
>> > <utkarsh.ayachit at kitware.com> wrote:
>> >>
>> >> > a.      When I select “Real Time” option and increase the time, even
>> >> > though
>> >> > it  is cached, it still keeps reloading which prevents the VR from
>> >> > working.
>> >> > Is there any potential/possibility to fix this in the meantime or
>> >> > upcoming
>> >> > release?
>> >>
>> >> Caching cannot work in "real time"  mode since there's no guarantee
>> >> what time each frame will be rendered at.
>> >>
>> >> > b.      When I cache it as a volume (rather than surface, wireframe,
>> or
>> >> > points) on my laptop, it crashed the exe even when I increase the
>> cache
>> >> > memory maximum size. Any thoughts on that? I tested it on a bigger
>> and
>> >> > faster work station and it worked, however, it still has the issue
>> >> > mentioned
>> >> > in the point below.
>> >>
>> >> I suspect you're just running out of memory on the system, esp since
>> >> you say smaller mesh works.
>> >>
>> >> > 2.      When I get a smaller mesh (4x smaller), I am able to cache
>> it as
>> >> > a
>> >> > volume. However, when playing it back, it keeps reloading while
>> showing
>> >> > the
>> >> > green bar as below at each time step. Is that supposed to happen? Is
>> >> > that
>> >> > rendering? Is there a way to eliminate it or make it faster?
>> >>
>> >> Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems
>> >> to me you have unstructured grid which is using  the slow path for
>> >> volume rendering. Another option is to apply "Resample To Image"
>> >> filter to resample the dataset to an image and volume rendering the
>> >> result. Then rendering should be much faster. You can also resample
>> >> and generate the image as a processing stage and save the resampled
>> >> dataset out and then load and render it in the animation loop.
>> >
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Mohamed Beshr
>>
>
>
>
> --
> Best Regards,
> Mohamed Beshr
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180330/ff79e4a9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 140024 bytes
Desc: not available
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180330/ff79e4a9/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 105545 bytes
Desc: not available
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180330/ff79e4a9/attachment-0003.png>