nvm on the issue request: https://gitlab.kitware.com/paraview/paraview/issues/17258
looking into the crash with curve3d.silo... David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 9, 2017 at 12:06 PM, David E DeMarle <dave.dema...@kitware.com> wrote: > Just remembering now that OSPRay (currently) only has volume rendering > implemented for image data. > > Please try the resample to image filter and that should look OK in OSPRay. > > Also - please file an issue on gitlab to remind me to make the UI warn > whenever ParaView hands OSPRay something incompatible rather than just > rendering nothing. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Wed, Mar 8, 2017 at 5:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) <joseph.g.hennessey2....@mail.mil> wrote: > >> CLASSIFICATION: UNCLASSIFIED >> >> David, >> >> I can not send my data set, >> But I am experiencing similar problems >> With one of visit's sample data sets. >> >> curv3d.silo (A multi-block containing a structured curvilinear grid) >> >> I clip it and then render it with the default volume renderer >> >> and it works, but then when I turn on OSPRay it fails. (crashes) >> >> Strangely enough it also fails (does not renderer visibly) in the default >> renderer when I do not first clip it. >> >> >> My data which is failing is instead a large unstructured grid with >> cell/Point >> arrays >> >> They visualize ok with the default Volume renderer but are invisible with >> the >> >> OSPRay volume renderer. I have not yet found a sample I can share with you >> that has the same >> >> behavior. I will see if I can get you one though. Do you know of any >> similar >> publicly available samples? >> >> >> I have also tried the vtk analyze sample data >> >> S01_epi_r01_001.img >> S01_epi_r01_001.hdr >> >> Which are image (uniform rectangular grids) >> >> S01_epi_r01_001 renderers correctly with both the default volume renderer >> >> and the OSPRay one. >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -----Original Message----- >> From: David E DeMarle [mailto:dave.dema...@kitware.com] >> Sent: Wednesday, March 08, 2017 3:02 PM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> <joseph.g.hennessey2....@mail.mil> >> Cc: paraview@paraview.org >> Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay >> Renderer >> not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) >> >> All active links contained in this email were disabled. Please verify the >> identity of the sender, and confirm the authenticity of all links >> contained >> within the message prior to copying and pasting the address to a Web >> browser. >> >> >> ________________________________ >> >> >> >> Wavelet->Volume Works for me on Linux, builtin mode. >> >> >> Can you provide more details? >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL >> (US) >> <joseph.g.hennessey2....@mail.mil < >> Caution-mailto:joseph.g.hennessey2....@mail.mil > > wrote: >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> Hello, >> >> I am finding that the volume rendering is not working with >> >> OSPRay Renderer not working with ParaView 5.3.0-RC3. >> >> The volume render sample that I am testing looks fine >> >> when rendered with the default renderer, but when I switch to the >> >> OSPRay volume renderer, then nothing is shown. >> >> Has anyone managed to volume render data, using >> >> the OSPRay renderer with ParaView 5.3.0-RC3? >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> _______________________________________________ >> Powered by Caution-www.kitware.com < Caution- >> http://www.kitware.com > >> >> Visit other Kitware open-source projects at >> Caution-http://www.kitware.com/opensource/opensource.html < >> Caution-http://www.kitware.com/opensource/opensource.html > >> >> Please keep messages on-topic and check the ParaView Wiki at: >> Caution-http://paraview.org/Wiki/ParaView < >> Caution-http://paraview.org/Wiki/ParaView > >> >> Search the list archives at: Caution-http://markmail.org/se >> arch/?q=ParaView < >> Caution-http://markmail.org/search/?q=ParaView > >> >> Follow this link to subscribe/unsubscribe: >> Caution-http://public.kitware.com/mailman/listinfo/paraview < >> Caution-http://public.kitware.com/mailman/listinfo/paraview > >> >> >> >> >> >> CLASSIFICATION: UNCLASSIFIED >> > >
_______________________________________________ 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
