[Paraview] OSPray rendering: ERROR: VolumeMapper's Input has no scalar array!

[Jiahui Luo]

Hi ,
I got an error message when trying to do volume rendering on the output 
of the ResampleToImage filter:


   ERROR: In
   
/home/user/apps/paraview5.2.0-build/superbuild/paraview/src/VTK/Rendering/OSPRay/vtkOSPRayVolumeMapperNode.cxx,
   line 107
   vtkOSPRayVolumeMapperNode (0x68c2ad0): VolumeMapper's Input has no
   scalar array!

Here is how it happened.
First, I added a ProgrammableSource with Output DataSet Type set to 
vtkRectilinearGrid and apply something like this,


   import numpy as np

   # Read x,y,z,th from file

   xCoords = vtk.vtkDoubleArray()
   for i in x:
xCoords.InsertNextValue(i)

   yCoords = vtk.vtkDoubleArray()
   for i in y:
yCoords.InsertNextValue(i)

   zCoords = vtk.vtkDoubleArray()
   for i in z:
zCoords.InsertNextValue(i)

   output.SetDimensions(len(x), len(y), len(z))
   output.SetXCoordinates(xCoords)
   output.SetYCoordinates(yCoords)
   output.SetZCoordinates(zCoords)

   thArray = vtk.vtkFloatArray()
   thArray.SetName("Temperature")
   thArray.SetNumberOfComponents(1)
   thArray.SetNumberOfTuples(nx*ny*nz)
   for k in range(nz):
for j in range(ny):
for i in range(nx):
index = i+j*nx+k*ny*nx
thArray.SetValue(index, th[k,j,i])
   output.GetCellData().SetScalars(thArray)
   return output

Since volume rendering can not be done on rectilinear grid. I added a 
ResampleToImage filter on this source.


Then I could do volume rendering using Ray cast or GPU based, but not 
OSPray and the above message popped up.


How to make this work? Thanks.

Jiahui Luo




___
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

[Paraview] Paraview 5.2.0: max time limit of 4095 for annotated .vtu file?

[David.Benn]

Upon loading an annotated .vtu file with TimeStep annotations such as this into 
Paraview 5.2.0 (under 64 bit SUSE Linux):



I see the following:

[cid:image001.png@01D27342.72FDFF10]

such that a maximum of 4095 time steps are available, as opposed to the 
expected 10,560 time steps.

When the non-annotated .vtu file is loaded, the expected number of frames are 
visible.

Is there some inherent limitation within Paraview that prevents more than 4095 
time steps from being loaded/visualised?

Thanks.

David
___
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

Re: [Paraview] ParaviewWeb on EC2

[Sebastien Jourdain]

Hi Claude,

I'm glad you like our doc and code. If you feel we are missing something
that is not obvious, please report it so we can fix it.

Regarding your issue, you had a good reflex in fixing apache and the
launcher config, as with PV5.2 we use a second ws connection for streaming
the images in binary format. But it has been forever since I setup that
ami, I have very little memory of what was setup.

I do know that we use 'sed' to dynamically replace some string so the
proper HOST for apache and the launcher get used, but I don't remember if
it was DNS_NAME or something else. But from what I understand, you've done
exactly what I would have done myself.

I'm wondering if when you edited your launcher config you managed to
produce an invalid JSON file. (You can paste it here http://jsonlint.com/
to be sure)

Moreover, seeing the network calls of the web page that don't even load
might be useful. I'd be curious to see the response of the POST on
/paraview.

Seb


On Thu, Jan 19, 2017 at 5:01 PM, claude  wrote:

> Hello!
>
> Following up one of the previous thread on setting up
> ParaviewWeb+Visualizer, I am trying to get it going on AWS EC2 with
> paraview-5.2. Maybe someone already went through it and know how to
> solve this little problem?
>
> * I launched the public AMI (ami-34f3f65e) on Ubuntu-14 with paraviewweb
> 4.4 which seemed like a good starting point.
> * I tested the visualizer on paraviewweb-4.4 and works perfectly.
> * I downloaded paraviewweb-5.2 and updated the 'pv' and 'www' symlinks
> under /data folder (see 'aws_data_dir' snapshot attached).
> * I also updated the paths in the start.sh, apache-TEMPLATE.conf and
> launcher-TEMPLATE.json files so that they reflect the correct path for
> paraview-5.2 (which are bit different than paraview-4.4). By the way,
> having start.sh running as a service at startup configuring properly the
> TEMPLATE files with the proper DNS name is admirable (each time I look
> at the doc, config files or code, I am amazed by the quality of it,
> thumb up!).
> * when I navigate to the EC2 DNS, the Visualizer comes up and I can
> browse for data files. The files seem to successfully load but nothing
> show up in the camera (see snapshot 'aws_ec2_visu'). Looking at the logs
> on the machine, they don't report any error (and look similar to what I
> can get locally on my machine). There is a couple of errors showing up
> in the web console though (in the snapshot attached).
>
> It looks like I am very close to make it work, I am probably missing
> something obvious.
> I tried the following to solve it by using my configuration on my local
> machine:
> 1. update the apache-TEMPLATE.conf with the following rules:
> RewriteCond %{QUERY_STRING} ^sessionId=(.*)&path=(.*)$ [NC]
> RewriteRule ^/proxy.*$ ws://${session-to-port:%1}/%2 [P]
>
> 2. update the launcher-TEMPLATE.json with the following line:
> "sessionURL" : "ws://DNS_NAME/proxy?sessionId=${id}&path=ws",
>
> 3. reboot (so that the files get updated)
>
> but this time the UI doesn't even load, meaning I made it worse.
>
> It seems just like a websocket connection issue, right?
>
> Thanks in advance for any ideas to try.
> cheers
> claude
>
> ___
> 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
>
>
___
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

Re: [Paraview] [EXTERNAL] size limit to loading annotated but file 4095 time steps

[Scott, W Alan]

Sounds like a bug?  Could you create a dataset that replicates the issue, that 
is reasonably small in size?  I.e., with one cell or point?   

Alan

> -Original Message-
> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of
> Adam Hill
> Sent: Wednesday, January 18, 2017 4:15 PM
> To: paraview@paraview.org
> Subject: [EXTERNAL] [Paraview] size limit to loading annotated but file 4095
> time steps
> 
> Hi all
> 
> We are using paraview to visualise a time series corresponding to
> propagation of a voltage waveform in a 2D domain.
> 
> Data is a .vtu file annotated with time points. Total series is >10,000 time
> steps. All confirmed as being annotated correctly
> 
> When we load into paraview (5.2), only the first 4095 time steps are
> imported.
> 
> Any ideas why this might be? Is there some sort of 12 bit limit being imposed
> somewhere? Any workarounds people can suggest?
> 
> Cheers
> 
> A
> 
> ___
> 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
___
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

Re: [Paraview] Strange error building paraview-superbuild als nightly build

[Fabian Wein]

thank you very much for the hint. I solved it via
set(CTEST_BUILD_COMMAND „/usr/bin/make")
in the .ctest file.

Fabian

> Am 19.01.2017 um 17:26 schrieb Ben Boeckel :
> 
> On Thu, Jan 19, 2017 at 11:35:30 +0100, Fabian Wein wrote:
>> I have a strange error. The issue is not very important, just a nice 
>> to have.
> 
> I suspect this is CTest's fault. Could you see if there is a `-i` flag
> in your DartConfiguration.tcl (or anywhere else in the cache) associated
> with the `make` command? The fix is to pass
> `-DMAKE_COMMAND:STRING=/path/to/make` to CMake during the configure,
> otherwise it "helpfully" passes `-i` (act like errors don't happen)
> which causes these kinds of problems. I suspect that Qt's configure is
> passing things it should not be passing and then setting preprocessor
> definitions it should not be.
> 
> Note that it may be helpful to use an external Qt using the
> `standalone-qt` project in `superbuild/standalone-qt` so that you do not
> need to build it every night (it changes infrequently enough that this
> isn't too much of a hassle).
> 
> --Ben



Dr. Fabian Wein
ZISC - Zentralinstitut für wissenschaftliches Rechnen
Universität Erlangen-Nürnberg 
D-91052 Erlangen, Germany
fabian.w...@fau.de

___
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

Re: [Paraview] [EXTERNAL] Re: exodusII reader & writer in parallel

[Sjaardema, Gregory D]

It is legal to create an exodus file with no nodes and no elements.  If that 
file is part of a parallel set (using file-per-processor mode), then that 
“empty” file should have consistent metadata (block counts, sideset counts, …), 
but it is allowed to have zero nodes and elements.

..Greg

-- 
"A supercomputer is a device for turning compute-bound problems into I/O-bound 
problems”

On 1/13/17, 2:13 PM, "ParaView on behalf of David Thompson" 
 wrote:

Hi all,

> It's looking like there could be a decent amount of hacking in the 
ExodusII code to get the writer to work properly for this (as well as the 
reader to read it back in without issues). The main issue appears to be that 
NetCDF doesn't allow creating a dimension of 0 length/size. Thus the stuff in 
VTK/ThirdParty/exodusII/vtkexodusII would need to be changed. 
> 
> Both the reader and writer make the assumption that if the num_nodes 
dimension exists that there are points to be read in. 

Yes, that is a basic assumption of the Exodus file format: each rank is 
assigned a subset of the cells and nodes in the simulation domain, since 
otherwise there is no state to store. If rank 0 of a simulation has no nodes 
(and thus cannot have cells either), then it should probably not participate in 
writing the Exodus dataset. You could create an MPI subcontroller without the 
rank 0 process and have the writer use that.

> At this point I'm thinking it's better to modify the reader than the 
writer...

I would be very wary of this.

David

> 
> On Fri, Jan 13, 2017 at 2:59 PM, Andy Bauer  
wrote:
> Hi Ken,
> 
> Thanks for the input. 
> 
> There is an explicit check in the writer to see if there are any points 
before writing out point data. I took that check out and am hitting a NetCDF 
error that the "num_nodes" dimension isn't specified. It will probably take a 
bit of investigating to fix this but at least you've helped me go down the 
correct path.
> 
> Thanks,
> Andy
> 
> On Fri, Jan 13, 2017 at 2:44 PM, Moreland, Kenneth  
wrote:
> Andy,
> 
>  
> 
> That sounds like a bug in our Exodus writer to me. I’m not positive, but 
I’m pretty sure that you can specify in Exodus point and cell arrays if no grid 
points or cells exist. The writer is probably making a shortcut and skipping 
that if there is no actual data.
> 
>  
> 
> -Ken
> 
>  
> 
> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Andy 
Bauer
> Sent: Friday, January 13, 2017 12:00 PM
> To: paraview@paraview.org
> Subject: [EXTERNAL] [Paraview] exodusII reader & writer in parallel
> 
>  
> 
> Hi,
> 
> I'm trying out the ExodusII writer in parallel and had some questions 
about how it should work in general when there isn't any data on process 0. 
Currently what happens in ParaView is that a file for each process is written 
out but the file corresponding to process 0 doesn't have any grid information 
or field data (an example is attached). When I read this back into ParaView 
using the built-in server (i.e. in serial) the ExodusII reader gets the proper 
points and cells but no field data is read in.
> 
> So my question is this, does the ExodusII file format allow specifying 
point and cell arrays in a file if no grid points or cells exist?
> 
> I'm tempted to fix this issue by modifying the reader to properly pass 
the field data information to process 0 from another one that has data but 
wanted to get the community's thoughts on this before I go through the 
implementation. The alternative would be to modify the writer to include point 
and cell data information and that's probably a better solution, assuming that 
the ExodusII format allows for that.
> 
> Thanks,
> 
> Andy
> 
> ps. Attached is a sample set of ExodusII files that doesn't have any data 
on parallel.ex2.4.0 in case someone wants to play around with it.
> 
> 
> 
> ___
> 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

___
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/unsubsc

Re: [Paraview] combining in on-screen and off-screen in one build

[Mark Olesen]

That is rather unfortunate - I guess that I misunderstood what the commits were 
doing.
On the bright side: at least I have a definitive statement about what works and 
what doesn't.

Many thanks for the quick answer.
/mark


From: Utkarsh Ayachit 
Sent: Thursday, January 19, 2017 5:40:14 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] combining in on-screen and off-screen in one build

To the best of my knowledge, that's not possible, it's not possible to
have GPU accelerated OpenGL and OSMesa in the same build of ParaView.
You have to do separate builds. ParaView does support using osmesa and
libGL provided by Mesa itself in the same build, but that won't be
using GPU, in that case.



On Thu, Jan 19, 2017 at 11:15 AM, Mark Olesen  wrote:
> Hi Utkarsh,
>
> Yes we need an off-screen rendering for the server and X11/GPU accelerated 
> for the client.
> As per the FAQ: Can ParaView be built with X11/GPU accelerated OpenGL and 
> OSMesa in the same build?
>
> If I build with osmesa, it seems that I must use PARAVIEW_BUILD_QT_GUI=OFF 
> and VTK_USE_X=OFF to get a build (I'll need to re-verify, since I've tried so 
> many combination). But this seems to preclude building for both hardware and 
> software rendering in the same build?
>
> /mark
> 
> From: Utkarsh Ayachit 
> Sent: Thursday, January 19, 2017 4:44:08 PM
> To: Mark Olesen
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] combining in on-screen and off-screen in one build
>
> Mark,
>
> Can you elaborate? When you say opengl + osmesa, do you mean as in
> Mesa+X and OSMesa ?
>
> Utkarsh
>
> On Thu, Jan 19, 2017 at 10:34 AM, Mark Olesen  
> wrote:
>> From commits it looks like 
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
>> Can someone offer the cmake variable combinations that I need to compile a 
>> combined build with both opengl + osmesa? If this works well, I'd like to be 
>> using that sooner rather than later.
>>
>> Thanks,
>> /mark
>>
>> ___
>> 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
___
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

Re: [Paraview] combining in on-screen and off-screen in one build

[Utkarsh Ayachit]

To the best of my knowledge, that's not possible, it's not possible to
have GPU accelerated OpenGL and OSMesa in the same build of ParaView.
You have to do separate builds. ParaView does support using osmesa and
libGL provided by Mesa itself in the same build, but that won't be
using GPU, in that case.



On Thu, Jan 19, 2017 at 11:15 AM, Mark Olesen  wrote:
> Hi Utkarsh,
>
> Yes we need an off-screen rendering for the server and X11/GPU accelerated 
> for the client.
> As per the FAQ: Can ParaView be built with X11/GPU accelerated OpenGL and 
> OSMesa in the same build?
>
> If I build with osmesa, it seems that I must use PARAVIEW_BUILD_QT_GUI=OFF 
> and VTK_USE_X=OFF to get a build (I'll need to re-verify, since I've tried so 
> many combination). But this seems to preclude building for both hardware and 
> software rendering in the same build?
>
> /mark
> 
> From: Utkarsh Ayachit 
> Sent: Thursday, January 19, 2017 4:44:08 PM
> To: Mark Olesen
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] combining in on-screen and off-screen in one build
>
> Mark,
>
> Can you elaborate? When you say opengl + osmesa, do you mean as in
> Mesa+X and OSMesa ?
>
> Utkarsh
>
> On Thu, Jan 19, 2017 at 10:34 AM, Mark Olesen  
> wrote:
>> From commits it looks like 
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
>> Can someone offer the cmake variable combinations that I need to compile a 
>> combined build with both opengl + osmesa? If this works well, I'd like to be 
>> using that sooner rather than later.
>>
>> Thanks,
>> /mark
>>
>> ___
>> 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
___
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

Re: [Paraview] Strange error building paraview-superbuild als nightly build

[Ben Boeckel]

On Thu, Jan 19, 2017 at 11:35:30 +0100, Fabian Wein wrote:
> I have a strange error. The issue is not very important, just a nice 
> to have.

I suspect this is CTest's fault. Could you see if there is a `-i` flag
in your DartConfiguration.tcl (or anywhere else in the cache) associated
with the `make` command? The fix is to pass
`-DMAKE_COMMAND:STRING=/path/to/make` to CMake during the configure,
otherwise it "helpfully" passes `-i` (act like errors don't happen)
which causes these kinds of problems. I suspect that Qt's configure is
passing things it should not be passing and then setting preprocessor
definitions it should not be.

Note that it may be helpful to use an external Qt using the
`standalone-qt` project in `superbuild/standalone-qt` so that you do not
need to build it every night (it changes infrequently enough that this
isn't too much of a hassle).

--Ben
___
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

Re: [Paraview] Increase number of slices for volume rendering ...

[Niklas Röber]

Awesome, thank you very much!

Cheers, Niklas


Hi Niklas,

unfortunately sampling distance is currently not exposed as a UI 
setting.  You could make the

following changes in order to decrease the sampling distance,

VTK/Rendering/VolumeOpenGL2/vtkSmartVolumeMapper.cxx
ln. 91 -- comment 


//  this->GPUMapper->LockSampleDistanceToInputSpacingOn();

/ParaViewCore/ClientServerCore/Rendering/vtkImageVolumeRepresentation.cxx
ln. 350 -- add 


this->VolumeMapper->SetAutoAdjustSampleDistances(0);
this->VolumeMapper->SetInteractiveAdjustSampleDistances(0);
  const float dist = 1.0;
  this->VolumeMapper->SetSampleDistance(dist);  //<-- smaller dist for 
higher quality / worse performance


This is a hack, but it should improve the rendering quality.  Be 
careful however to not make 'dist'
too small as this hack has the disadvantage that the specified 
sampling distance would be also

used during interaction (you might notice some performance issues).

If you are trying to increase the sampling rate in order to reduce 
"wood grain" artifacts, you
could instead try enabling jittering, this might also help (without 
major performance concerns),


VTK/Rendering/VolumeOpenGL2/vtkSmartVolumeMapper.cxx

ln. 92 -- add 


  this->GPUMapper->UseJitteringOn();

We are planning to expose both settings in the future so that they can 
be controlled through

the UI in ParaView.

Hope that helps,
Álvaro


On Tue, Jan 17, 2017 at 11:58 AM, Niklas Röber > wrote:


Hi,

for GPU based volume rendering, is there a way to increase the
number of slices to enhance the overall quality of the rendering?
If this can not directly be done in the GUI, would it be possible
to adjust a scaling factor in the code?

Thanks and Cheers,
Niklas


___
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





--
Alvaro Sanchez
Kitware, Inc.
Senior R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4901



--
__

Dr. Niklas Röber
Visualisierung
Abteilung Anwendungen

Deutsches Klimarechenzentrum GmbH (DKRZ)
Bundesstraße 45 a • D-20146 Hamburg • Germany

email: roe...@dkrz.de
phone: +49 (0)40 460094 283
  fax: +49 (0)40 460094 270
  web: http://www.dkrz.de/

Geschäftsführer: Prof. Dr. Thomas Ludwig
Sitz der Gesellschaft: Hamburg
Amtsgericht Hamburg HRB 39784
__



smime.p7s
Description: S/MIME Cryptographic Signature
___
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

Re: [Paraview] combining in on-screen and off-screen in one build

[Mark Olesen]

Hi Utkarsh,

Yes we need an off-screen rendering for the server and X11/GPU accelerated for 
the client.
As per the FAQ: Can ParaView be built with X11/GPU accelerated OpenGL and 
OSMesa in the same build?

If I build with osmesa, it seems that I must use PARAVIEW_BUILD_QT_GUI=OFF and 
VTK_USE_X=OFF to get a build (I'll need to re-verify, since I've tried so many 
combination). But this seems to preclude building for both hardware and 
software rendering in the same build?

/mark

From: Utkarsh Ayachit 
Sent: Thursday, January 19, 2017 4:44:08 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] combining in on-screen and off-screen in one build

Mark,

Can you elaborate? When you say opengl + osmesa, do you mean as in
Mesa+X and OSMesa ?

Utkarsh

On Thu, Jan 19, 2017 at 10:34 AM, Mark Olesen  wrote:
> From commits it looks like 
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
> Can someone offer the cmake variable combinations that I need to compile a 
> combined build with both opengl + osmesa? If this works well, I'd like to be 
> using that sooner rather than later.
>
> Thanks,
> /mark
>
> ___
> 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
___
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

Re: [Paraview] Increase number of slices for volume rendering ...

[Alvaro Sanchez]

Hi Niklas,

unfortunately sampling distance is currently not exposed as a UI setting.
You could make the
following changes in order to decrease the sampling distance,

VTK/Rendering/VolumeOpenGL2/vtkSmartVolumeMapper.cxx
ln. 91 -- comment

//  this->GPUMapper->LockSampleDistanceToInputSpacingOn();

/ParaViewCore/ClientServerCore/Rendering/vtkImageVolumeRepresentation.cxx
ln. 350 -- add

  this->VolumeMapper->SetAutoAdjustSampleDistances(0);
  this->VolumeMapper->SetInteractiveAdjustSampleDistances(0);
  const float dist = 1.0;
  this->VolumeMapper->SetSampleDistance(dist);  //<-- smaller dist for
higher quality / worse performance

This is a hack, but it should improve the rendering quality.  Be careful
however to not make 'dist'
too small as this hack has the disadvantage that the specified sampling
distance would be also
used during interaction (you might notice some performance issues).

If you are trying to increase the sampling rate in order to reduce "wood
grain" artifacts, you
could instead try enabling jittering, this might also help (without major
performance concerns),

VTK/Rendering/VolumeOpenGL2/vtkSmartVolumeMapper.cxx

ln. 92 -- add

  this->GPUMapper->UseJitteringOn();

We are planning to expose both settings in the future so that they can be
controlled through
the UI in ParaView.

Hope that helps,
Álvaro


On Tue, Jan 17, 2017 at 11:58 AM, Niklas Röber  wrote:

> Hi,
>
> for GPU based volume rendering, is there a way to increase the number of
> slices to enhance the overall quality of the rendering? If this can not
> directly be done in the GUI, would it be possible to adjust a scaling
> factor in the code?
>
> Thanks and Cheers,
> Niklas
>
>
> ___
> 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
>
>


-- 
Alvaro Sanchez
Kitware, Inc.
Senior R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4901
___
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

Re: [Paraview] combining in on-screen and off-screen in one build

[Utkarsh Ayachit]

Mark,

Can you elaborate? When you say opengl + osmesa, do you mean as in
Mesa+X and OSMesa ?

Utkarsh

On Thu, Jan 19, 2017 at 10:34 AM, Mark Olesen  wrote:
> From commits it looks like 
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
> Can someone offer the cmake variable combinations that I need to compile a 
> combined build with both opengl + osmesa? If this works well, I'd like to be 
> using that sooner rather than later.
>
> Thanks,
> /mark
>
> ___
> 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
___
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

[Paraview] combining in on-screen and off-screen in one build

[Mark Olesen]

>From commits it looks like 
>http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
>Can someone offer the cmake variable combinations that I need to compile a 
>combined build with both opengl + osmesa? If this works well, I'd like to be 
>using that sooner rather than later.

Thanks,
/mark

___
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

[Paraview] Problems writing binary vtu file

[Aleksejs Fomins]

Dear Paraview,

I tried to extend my VTU writer to write into binary format. I have tried 
either writing floats using Float32 format and doubles using Float64 format, 
both fail the same way. I write into binary by using

file.write( (char*) &binarydata, sizeof(BinaryType));

In both cases, Paraview complains that there is an invalid token immediately at 
the beginning of binary output within the first DataArray clause.

Could someone please hint me as of what I am doing wrong.

Regards,
Aleksejs




ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/IO/XMLParser/vtkXMLParser.cxx,
 line 397
vtkXMLDataParser (0x49f23f0): Error parsing XML in stream at line 7, column 0, 
byte index 379: not well-formed (invalid token)


ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/IO/XML/vtkXMLReader.cxx, line 
456
vtkXMLUnstructuredGridReader (0x49ff7d0): Error parsing input file.  
ReadXMLInformation aborting.


ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
 line 784
vtkCompositeDataPipeline (0x4226820): Algorithm 
vtkXMLUnstructuredGridReader(0x49ff7d0) returned failure for request: 
vtkInformation (0x4c21eb0)
  Debug: Off
  Modified Time: 167613
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0




ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/IO/XMLParser/vtkXMLParser.cxx,
 line 397
vtkXMLDataParser (0x49aa790): Error parsing XML in stream at line 7, column 0, 
byte index 379: not well-formed (invalid token)


ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/IO/XML/vtkXMLReader.cxx, line 
456
vtkXMLUnstructuredGridReader (0x49ff7d0): Error parsing input file.  
ReadXMLInformation aborting.


ERROR: In 
/home/fomins/Downloads/ParaView-v5.0.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
 line 784
vtkCompositeDataPipeline (0x4226820): Algorithm 
vtkXMLUnstructuredGridReader(0x49ff7d0) returned failure for request: 
vtkInformation (0x4c21eb0)
  Debug: Off
  Modified Time: 167613
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0


___
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

Re: [Paraview] ParaView and Qt 5

[Mark Olesen]

Thanks, this solves the problem.

From: Shawn Waldon 
Sent: Wednesday, January 18, 2017 9:22:18 PM
To: Mark Olesen
Cc: Utkarsh Ayachit; ParaView Developers; ParaView
Subject: Re: [Paraview] ParaView and Qt 5

Hi Mark,

CMake uses different variables to find Qt4 vs Qt5.  QT_QMAKE_EXECUTABLE is the 
Qt4 variable and is ignored by the code to find Qt5.  The variable you want is: 
-DQt5_DIR=/software/path/qt-5.7.1/lib/cmake/Qt5

HTH,
Shawn

On Wed, Jan 18, 2017 at 3:16 PM, Mark Olesen 
mailto:mark.ole...@esi-group.com>> wrote:
I'm trying to compile a paraview using a Qt5 (5.7.1) that I've compiled with 
'-qt-xcb' to avoid too many dependencies. When compiling paraview (git 
version), I supposed that the following would be sufficient to convey which qt 
to use:

cmake -DPARAVIEW_BUILD_QT_GUI=ON 
-DQT_QMAKE_EXECUTABLE:FILEPATH=/software/path/qt-5.7.1/bin/qmake 
-DPARAVIEW_QT_VERSION:STRING=5  ...

However, the find_package(Qt5) locates the system Qt and its cmake file, which 
bombs out:

CMake Error at CMake/ParaViewQt.cmake:65 (find_package):
  Could not find a configuration file for package "Qt5" that is compatible
  with requested version "5.6".
  The following configuration files were considered but not accepted:
/usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
/usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
Call Stack (most recent call first):
  Qt/Widgets/CMakeLists.txt:200 (pv_find_package_qt)


Which config variables am I missing?

Thanks,
/mark

From: ParaView 
mailto:paraview-boun...@paraview.org>> on behalf 
of Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>
Sent: Monday, January 16, 2017 7:51:36 PM
To: ParaView Developers
Cc: ParaView
Subject: [Paraview] ParaView and Qt 5

Folks,

With upcoming release (5.3), we plan to move to using Qt 5 by default.
Qt 5 has been out since 2012 and it is well supported on modern
platforms. ParaView will continue to build with Qt 4 until further
notice, but we highly recommend custom application developers and
plugin developers to move to Qt 5 at the earliest since active
development and testing for ParaView will happen with Qt 5.

Changes [1] that landed in master earlier today update ParaView to now
use QOpenGLWidget for rendering which creates a frame buffer object to
do all the rendering in. If you have custom mapper or rendering code
that assumed it was rendering to the default onscreen frame buffer, it
will not work correctly and will need to be updated. Please use the
mailing, if you encounter any such issues. For everything else, the
changes should be fairly transparent except in exceptions documented
here [2].

In the upcoming weeks, we will update the superbuild and dashboards to
build and test using Qt 5.

Thanks,
Utkarsh


[1] https://gitlab.kitware.com/paraview/paraview/merge_requests/1279
[2] 
https://gitlab.kitware.com/paraview/paraview/blob/master/Utilities/Doxygen/pages/MajorAPIChanges.md#changes-in-53
___
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
___
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

___
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

[Paraview] Strange error building paraview-superbuild als nightly build

[Fabian Wein]

Hello,

I have a strange error. The issue is not very important, just a nice 
to have.


I have a simple project building paraview-superbuild as external 
project which includes applying two simple patches
(add building of the libs boost_filesystem and hdf5_cpp) and our 
external plugin.


When run the project manually (cmake ..) it works reproducible 
perfectly smooth on several Linux machines and Mac.


When I run the project via ctest for a nightly build I have errors 
building qt5. When I do 'make' in my project or
the paraview-superbuild project all runs without any notice of a 
error, simply in install/bin no paraview stuff built.


I diffed Testing/Temporary/LastBuild_20170118-1244.log with the output 
from my manual build.
All is more or less the same but sometimes differently ordered due to 
parallal building (which I don't trigger actively)


The real difference start in the ctest log in line ~36500
with
-
[ 88%] Performing install step for 'qt5'
In file included from 
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/corelib/tools/qlocale_tools.cpp:42:0:
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/corelib/tools/qdoublescanprint_p.h:151:53: 
fatal error: double-conversion/double-conversion.h: No such file or 
directory

 #include 
 ^
compilation terminated.
g++: error: .obj/qlocale_tools.o: No such file or directory
mv: cannot stat 'libQt5Core.so.5.7.1': No such file or directory
install: cannot stat '../../lib/libQt5Core.so.5.7.1': No such file or 
directory
strip: 
'/home/fwein/code/cfs_paraview_build/build/install/lib/libQt5Core.so.5.7.1': 
No such file
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/network/kernel/qnetworkproxy_libproxy.cpp:47:19: 
fatal error: proxy.h: No such file or directory

 #include 
   ^
compilation terminated.
g++: error: .obj/qnetworkproxy_libproxy.o: No such file or directory
mv: cannot stat 'libQt5Network.so.5.7.1': No such file or directory
...


In the manual built it is

[ 88%] Performing install step for 'qt5'
strip:/home/fwein/code/cfs_paraview_build/build/install/bin/fixqt4headers.pl: 
File format not recognized
strip:/home/fwein/code/cfs_paraview_build/build/install/bin/syncqt.pl: 
File format not recognized
Some of the required modules 
(android|ios|winrt|osx_webview_experimental|qtHaveModule(webengine)) 
are not available.

Skipped.
[ 90%] Completed 'qt5'
[ 90%] Built target qt5
Scanning dependencies of target paraview
[ 90%] Creating directories for 'paraview'
[ 91%] Performing download step (download, verify and extract) for 
'paraview'

-- verifying file...
...
--

I cannot see how this is caused by my ctest script
-
SET(CTEST_SOURCE_DIRECTORY "$ENV{HOME}/code/cfs_paraview")
SET(CTEST_BINARY_DIRECTORY "$ENV{HOME}/code/cfs_paraview_build")
SET(CTEST_CMAKE_GENERATOR "Unix Makefiles")
SET(CTEST_PROJECT_NAME "Paraview metabuild")

set(CTEST_SITE "eamc061")
set(CTEST_BUILD_NAME "Paraview 5.2 metabuild")
set(BUILDNAME "Paraview 5.2 metabuild Buildname what for?")

# somehow CTEST_START_WITH_EMPTY_BINARY_DIRECTORY does not work?! So 
do it also manually

file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}")
file(MAKE_DIRECTORY "${CTEST_BINARY_DIRECTORY}")
SET(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)

SET(BUILDTYPE "RELEASE")

message("Start dashboard...")
ctest_start(Experimental)

message("  Update")
find_program(CTEST_SVN_COMMAND NAMES svn)
set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")
ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE res)

message("  Configure")
ctest_configure(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)

message("  Build")
ctest_build(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)

message("  Test")
ctest_test(BUILD "${CTEST_BINARY_DIRECTORY}/build" RETURN_VALUE res)

message("  Submit")
-

The CMakeCache.txt in my build directory and the paraview-superbuild 
build directory are identical


Anyone has any idea? I can live without nightly builds but it would be 
nice for me to understand.


Fabian
___
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