Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Kai, You are welcome! Thanks for letting us know the problem is resolved for you. Cory On Thu, Oct 1, 2015 at 8:12 AM, kai liu wrote: > Cory, > > Yes. ParaView's master branch works fine with STL load issue now. Thank > you for your help! > > Kai L. > > > > On Wednesday,

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Kai, Thanks for filing these bug reports. I believe the STL load issue is already fixed in ParaView's master branch, but the bug fix did not make it into version 4.4. Best regards, Cory On Tue, Sep 29, 2015 at 7:13 PM, kai liu wrote: > Hi Scott, > > I have filed both bug

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Hello Kai, Now after doing a clean build of a recent ParaView master, it seems I can no longer see the Mitchel.stl file, and the server produces the error logs you have mentioned somewhere above about the being unable to read the reading point. So I would say at this point, there is perhaps a

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Hi Scott, I have filed both bug reports: STL file load issue and surface with edges issue in local rendering.  http://www.paraview.org/Bug/view.php?id=15747 http://www.paraview.org/Bug/view.php?id=15748 Please let me know if I need to make changes/corrections in the bug reports. Thank you for

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Dear Scott, Should I just wait for the next patch release for the local rendering (WebGL)  "Surface with edges" issue?  I just tried the following commands to obtain the source from the GitLab and rebuilt the ParaViewWeb 4.4 with OSMesa, but it still does not resolve my stl loading issue. Am I

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Hello Kai, Regarding the data files you shared, I did some testing and found some things out: 1) Regarding using local rendering on the cube data file: It seems that with local rendering, we may not properly handle coloring by arrays where the data range is 0 (e.g. the range of T in your case

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Dear Scott: I do not have problems setting the representation to "Surface" with color "T" in local deprecated rendering mode. However, I do get the same error message with representation set to  "Surface with edges" or "Wireframe" with color "T" in local deprecated rendering.  But "Surface with

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Hello Kai, So in doing some more testing it seems, that the problem may actually be with the webgl exporter when you set the representation to "Surface with edges". Can you try to see if you have the problem with just "Surface"? In that case, there is potentially a bug in the geometry

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

On Fri, Sep 25, 2015 at 3:24 PM, kai liu wrote: > Dear Scott: > > I do not have problems setting the representation to "Surface" with color > "T" in local deprecated rendering mode. However, I do get the same error > message with representation set to "Surface with edges" or

[Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Dear, I have deployed ParaViewWeb. Everything seems to work fine, but I am not able to visualize outputs, such as rendering the output fields such as T, V, etc.  I built and tried ParaViewWeb 4.1, 4.3 and 4.4 with offscreen OSMesa, and I have received the same issues. Currently I use Apache

Re: [Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

Hello Kai, Thanks for your questions, I have put my responses inline below: On Thu, Sep 24, 2015 at 5:45 AM, kai liu via ParaView wrote: > Dear, > > > I have deployed ParaViewWeb. Everything seems to work fine, but I am not > able to visualize outputs, such as