[Paraview] Viewing Delft3D output in ParaView

2017-11-15 Thread Ahmed Bilal 
Hello Everyone.
Is there a way to see Delft 3D output in ParaView. Delft 3D produces its
outout in  NFIES compliant (*.dat) format. Any plugin to directly view
these files. Or any way to convert these files into NetCDF for viewing in
ParaView.

Thanks in advance.

Best regards,


*Ahmed Bilal*
___
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] OpenGL inside VMWare virtual machine

2017-11-15 Thread Cornelis Bockemühl 
Question not any more relevant: setting an environment variable before
starting paraview does indeed the trick: it works now indeed as
expected!

Thanks and regards,
Cornelis

Am Mittwoch, den 15.11.2017, 18:54 +0100 schrieb Cornelis Bockemühl:
> Thanks for the hint: I will definitely try this!
> > > Only one question: you write environment which sounds like an
environment variable, but maybe you mean a variable ti be set in the
CMake configuration!?!
> 
> Regards, Cornelis
> 
> 
> > Am 15.11.2017 17:40 schrieb "Ken Martin" :
> > > > This could  be a PV Qt interaction. Try
setting MESA_GL_VERSION_OVERRIDE=3.2 in your environment
> > > > > > Basically there is a bug in Qt on windows where it refuses to see
the 3.2 context from Mesa because it is not a compatibility
context.
> > 
> > 
> > > > On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl  wrote:
> > > Dear all,
> > > > > > > > > > > > > > > > > > I know that I cannot go for any performance 
> > > > > > > > > > > > > > > > > > record with this
setup, but having both systems available without reboot has
advantages if it is about testing some new development. WOULD
have - if it fully worked! So far it looks like I am "almost
there" - however not knowing whether the last 10 meters will be
feasible at all...
> > > 
> > > This is my setup:
> > > 
> > > > > > Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting
the following in the About dialog:
> > > OpenGL Vendor: Intel Open Source Technology Center
> > > OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
> > > OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
> > > 
> > > > > > On this system Paraview (latest version, self compiled) runs just
fine.
> > > 
> > > > > > Guest system inside VMWare Player version 14: Windows 10, with
Paraview reporting the following:
> > > OpenGL Vendor: VMware, Inc.
> > > OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
> > > OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
> > > 
> > > > > > Here Paraview immediately complains on startup, reporting the
following in the message output dialog: see below.
> > > 
> > > > > > > > > > > > For me the version numbers look ok (OpenGL 3.3 is more 
> > > > > > > > > > > > than 3.2,
and Mesa 11.2.0 is more than 10.6.5), but there is some
"fineprint" about shader capabilities that are going a bit above
my understanding...
> > > 
> > > Anybody able to help with this?
> > > 
> > > > > > Any possibility to "cheat" somehow? Note that I am certainly not
going to render billions of data in this configuration!
> > > 
> > > Or should I abandon this tricky setup altogether?
> > > 
> > > Thanks and regards,
> > > Cornelis
> > > 
> > > > > > Here the error output from the Windows Paraview inside the VMWare
virtual machine:
> > > 
> > > > > > ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 831
> > > > > > > > > > > > > > > > > > vtkGenericOpenGLRenderWindow 
> > > > > > > > > > > > > > > > > > (02438C350630): GL version 2.1
with the gpu_shader4 extension is not supported by your graphics
driver but is required for the new OpenGL rendering backend.
Please update your OpenGL driver. If you are using Mesa please
make sure you have version 10.6.5 or later and make sure your
driver in Mesa supports OpenGL 3.2.
> > > 
> > > > > > ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 408
> > > vtkShaderProgram (02438C1B80C0): 1: #version 150
> > > 2: #ifdef GL_ES
> > > 3: #if __VERSION__ == 300
> > > 4: #define attribute in
> > > 5: #define varying out
> > > 6: #endif // 300
> > > 7: #else // GL_ES
> > > 8: #define highp
> > > 9: #define mediump
> > > 10: #define lowp
> > > 11: #if __VERSION__ == 150
> > > 12: #define attribute in
> > > 13: #define varying out
> > > 14: #endif
> > > 15: #endif // GL_ES
> > > 16: 
> > > 17: 
> > > > > > > > > 18:
/*===
==
> > > 19: 
> > > 20:   Program:   Visualization Toolkit
> > > 21:   Module:vtkPolyDataVS.glsl
> > > 22: 
> > > 23:   Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
> > > 24:   All rights reserved.
> > > > > > 25:   See Copyright.txt or http://www.kitware.com/Copyright.htm
for details.
> > > 26: 
> > > > > > 27:  This software is distributed WITHOUT ANY WARRANTY;
without even
> > > > > > 28:  the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR
> > > > > > 29:  PURPOSE.  See the above copyright notice for more
information.
> > > 30: 
> > > > > > > > > 31:
=
*/
> > > 32: 
> > > 33: attribute vec4 vertexMC;
> > > 34: 
> > > 35: // frag position in VC
> > > 36: //VTK::PositionVC::Dec
> > > 37: 
> > > 38: // optional normal declaration
> > > 39: //VTK::Normal::Dec
> > > 40: 
> > > 41: // extra lighting parameters
> > > 42: //VTK::Light::Dec
> > > 43: 
> > >

Re: [Paraview] How to read the file info in *pvd file

2017-11-15 Thread Ke Gao 
Actually, what I want to do is using python script to read *pvd file first
to get the name info of *pvtu files. Then use the *pvtu file name to read
through all of them one by one to extract the info I want. I'm not sure if
there is a better way to realize this.

Many thanks.

On Wed, Nov 15, 2017 at 11:05 AM, Cory Quammen 
wrote:

> The file names are embedded in the same XML element as the time step:
>
> 
>
> But I'll be that's not how you want to access them.
>
> Next question: From where do you want to access the file names? A Python
> script? In the UI?
>
> On Wed, Nov 15, 2017 at 12:35 PM, Ke Gao  wrote:
>
>> Hi,
>>
>> I mean how to get the file name info such as "Sout_1012.pvtu",
>> "Sout_1013.pvtu". Currently I can only read the timestep info such as
>> "+1.9880e+03".
>>
>> Many thanks.
>>
>>
>> 
>>   
>>   
>> > file="Sout_1012.pvtu"/>
>> > file="Sout_1013.pvtu"/>
>> > file="Sout_1014.pvtu"/>
>>
>> On Wed, Nov 15, 2017 at 10:33 AM, Cory Quammen 
>> wrote:
>>
>>> What do you mean by "file info"? File name? Size of the file? Data
>>> arrays in the file?
>>>
>>> - Cory
>>>
>>> On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao  wrote:
>>>
 Does anyone know how to read the file info from *pvd file? I know how
 to get the time step values, just using the keyword of “TimestepValues”,
 however, I tried different ways, still haven’t figured out how to read the
 file info.

 Thanks

 
   
   
 >>> file="Sout_1012.pvtu"/>
 >>> file="Sout_1013.pvtu"/>
 >>> file="Sout_1014.pvtu"/>
 --
 
 
 ..
 Ke Gao

 ___
 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


>>>
>>>
>>> --
>>> Cory Quammen
>>> Staff R Engineer
>>> Kitware, Inc.
>>>
>>
>>
>>
>> --
>> 
>> 
>> ..
>> Ke Gao
>>
>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>



-- 
..
Ke Gao
___
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] How to read the file info in *pvd file

2017-11-15 Thread Cory Quammen 
The file names are embedded in the same XML element as the time step:



But I'll be that's not how you want to access them.

Next question: From where do you want to access the file names? A Python
script? In the UI?

On Wed, Nov 15, 2017 at 12:35 PM, Ke Gao  wrote:

> Hi,
>
> I mean how to get the file name info such as "Sout_1012.pvtu",
> "Sout_1013.pvtu". Currently I can only read the timestep info such as
> "+1.9880e+03".
>
> Many thanks.
>
>
> 
>   
>   
> 
> 
> 
>
> On Wed, Nov 15, 2017 at 10:33 AM, Cory Quammen 
> wrote:
>
>> What do you mean by "file info"? File name? Size of the file? Data arrays
>> in the file?
>>
>> - Cory
>>
>> On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao  wrote:
>>
>>> Does anyone know how to read the file info from *pvd file? I know how to
>>> get the time step values, just using the keyword of “TimestepValues”,
>>> however, I tried different ways, still haven’t figured out how to read the
>>> file info.
>>>
>>> Thanks
>>>
>>> 
>>>   
>>>   
>>> >> file="Sout_1012.pvtu"/>
>>> >> file="Sout_1013.pvtu"/>
>>> >> file="Sout_1014.pvtu"/>
>>> --
>>> 
>>> 
>>> ..
>>> Ke Gao
>>>
>>> ___
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> Staff R Engineer
>> Kitware, Inc.
>>
>
>
>
> --
> 
> 
> ..
> Ke Gao
>



-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
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] GoCAD and Earth Vision grid files *.ts & *.evgd

2017-11-15 Thread Aashish Chaudhary 
the code I pointed to is based on a older version of the VTK and ParaView
and needs to be ported to newer VTK and ParaView. I do not expect it will
be lot of work but some work and we can help you over the email if needed.

Thanks


On Wed, Nov 15, 2017 at 12:56 PM Sonya Davydycheva  wrote:

> Thank you Aashish,
>
> But the link you provided includes:
>
>- GoCad ASCII Files (*.gp, *.ts, *.pl, *.vs, *.vts, *.vo, *.sg)
>
> (see Bottom of Supported Readers).
> Does it mean GoCAD files are doable already? Or, something still needs to
> be added to Paraview, to read them?
>
> Sonya Davydycheva 
> (713)498-6139
>
>
> On Wed, Nov 15, 2017 at 11:51 AM, Aashish Chaudhary <
> aashish.chaudh...@kitware.com> wrote:
>
>> the actual code location is here:
>> https://github.com/ObjectivitySRC/PVGPlugins/tree/master/Readers/GocadReader
>>
>>
>> Let us know if you decide to bring in this code into VTK / ParaView as we
>> will be very interested in it as well.
>>
>> Thanks,
>>
>>
>> On Wed, Nov 15, 2017 at 12:46 PM Aashish Chaudhary <
>> aashish.chaudh...@kitware.com> wrote:
>>
>>> I do not think that GoCAR ASCII (ts) files are directly readable in
>>> ParaView. Although there is a reader in this repo
>>> http://paraviewgeo.objectivity.ca/documentation/user-manual/supported-formats
>>>  that
>>> you could bring into ParaView / VTK. If that is the case, we would be happy
>>> to help bringing in the reader in VTK / ParaView.
>>>
>>> thanks
>>>
>>>
>>> On Wed, Nov 15, 2017 at 11:10 AM Sonya Davydycheva 
>>> wrote:
>>>
 Hello,

 1) Is it possible to read/import GoCAD file *.ts (triangulated
 surfaces) using ParaView, with a possibility to further read its data in
 ascii format, or convert to a 3D function of space point (x,y,z)?

 2) The same question about Earth Vision grid and the respective files
 *.evgd: can I read/import them and transfer to ascii or 3D function(x,y,z)
 using ParaView?

 Thank you,

 Sonya Davydycheva 
 (713)498-6139

 ___
 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] GoCAD and Earth Vision grid files *.ts & *.evgd

2017-11-15 Thread Sonya Davydycheva 
Thank you Aashish,

But the link you provided includes:

   - GoCad ASCII Files (*.gp, *.ts, *.pl, *.vs, *.vts, *.vo, *.sg)

(see Bottom of Supported Readers).
Does it mean GoCAD files are doable already? Or, something still needs to
be added to Paraview, to read them?

Sonya Davydycheva 
(713)498-6139


On Wed, Nov 15, 2017 at 11:51 AM, Aashish Chaudhary <
aashish.chaudh...@kitware.com> wrote:

> the actual code location is here: https://github.com/
> ObjectivitySRC/PVGPlugins/tree/master/Readers/GocadReader
>
> Let us know if you decide to bring in this code into VTK / ParaView as we
> will be very interested in it as well.
>
> Thanks,
>
>
> On Wed, Nov 15, 2017 at 12:46 PM Aashish Chaudhary <
> aashish.chaudh...@kitware.com> wrote:
>
>> I do not think that GoCAR ASCII (ts) files are directly readable in
>> ParaView. Although there is a reader in this repo http://paraviewgeo.
>> objectivity.ca/documentation/user-manual/supported-formats that you
>> could bring into ParaView / VTK. If that is the case, we would be happy to
>> help bringing in the reader in VTK / ParaView.
>>
>> thanks
>>
>>
>> On Wed, Nov 15, 2017 at 11:10 AM Sonya Davydycheva 
>> wrote:
>>
>>> Hello,
>>>
>>> 1) Is it possible to read/import GoCAD file *.ts (triangulated surfaces)
>>> using ParaView, with a possibility to further read its data in ascii
>>> format, or convert to a 3D function of space point (x,y,z)?
>>>
>>> 2) The same question about Earth Vision grid and the respective files
>>> *.evgd: can I read/import them and transfer to ascii or 3D function(x,y,z)
>>> using ParaView?
>>>
>>> Thank you,
>>>
>>> Sonya Davydycheva 
>>> (713)498-6139
>>>
>>> ___
>>> 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] Animation .avi output not working in v5.4.1, working in v4.4

2017-11-15 Thread Dennis Conklin 
Anyone else seeing this?

I'm getting the same msg I was getting in v4.4 (but in v4.4 it still produced a 
useable animation).


[avi @ 0x8ec35c0] Using AVStream.codec.time_base as a timebase hint to the 
muxer is deprecated. Set AVStream.time_base instead.
[avi @ 0x8ec35c0] Encoder did not produce proper pts, making some up.

Dennis
___
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] OpenGL inside VMWare virtual machine

2017-11-15 Thread Cornelis Bockemühl 
Thanks for the hint: I will definitely try this!

Only one question: you write environment which sounds like an environment
variable, but maybe you mean a variable ti be set in the CMake
configuration!?!

Regards, Cornelis

Am 15.11.2017 17:40 schrieb "Ken Martin" :

> This could  be a PV Qt interaction. Try setting MESA_GL_VERSION_OVERRIDE=3.2
> in your environment
>
> Basically there is a bug in Qt on windows where it refuses to see the 3.2
> context from Mesa because it is not a compatibility context.
>
> On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl <
> cornelis.bockemu...@gmail.com> wrote:
>
>> Dear all,
>>
>> I know that I cannot go for any performance record with this setup, but
>> having both systems available without reboot has advantages if it is about
>> testing some new development. WOULD have - if it fully worked! So far it
>> looks like I am "almost there" - however not knowing whether the last 10
>> meters will be feasible at all...
>>
>> This is my setup:
>>
>> Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
>> following in the About dialog:
>> OpenGL Vendor: Intel Open Source Technology Center
>> OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
>> OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
>>
>> On this system Paraview (latest version, self compiled) runs just fine.
>>
>> Guest system inside VMWare Player version 14: Windows 10, with Paraview
>> reporting the following:
>> OpenGL Vendor: VMware, Inc.
>> OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
>> OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
>>
>> Here Paraview immediately complains on startup, reporting the following
>> in the message output dialog: see below.
>>
>> For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and Mesa
>> 11.2.0 is more than 10.6.5), but there is some "fineprint" about shader
>> capabilities that are going a bit above my understanding...
>>
>> Anybody able to help with this?
>>
>> Any possibility to "cheat" somehow? Note that I am certainly not going to
>> render billions of data in this configuration!
>>
>> Or should I abandon this tricky setup altogether?
>>
>> Thanks and regards,
>> Cornelis
>>
>> Here the error output from the Windows Paraview inside the VMWare virtual
>> machine:
>>
>> ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\O
>> penGL2\vtkOpenGLRenderWindow.cxx, line 831
>> vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with the
>> gpu_shader4 extension is not supported by your graphics driver but is
>> required for the new OpenGL rendering backend. Please update your OpenGL
>> driver. If you are using Mesa please make sure you have version 10.6.5 or
>> later and make sure your driver in Mesa supports OpenGL 3.2.
>>
>> ERROR: In 
>> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
>> line 408
>> vtkShaderProgram (02438C1B80C0): 1: #version 150
>> 2: #ifdef GL_ES
>> 3: #if __VERSION__ == 300
>> 4: #define attribute in
>> 5: #define varying out
>> 6: #endif // 300
>> 7: #else // GL_ES
>> 8: #define highp
>> 9: #define mediump
>> 10: #define lowp
>> 11: #if __VERSION__ == 150
>> 12: #define attribute in
>> 13: #define varying out
>> 14: #endif
>> 15: #endif // GL_ES
>> 16:
>> 17:
>> 18: /*==
>> ===
>> 19:
>> 20:   Program:   Visualization Toolkit
>> 21:   Module:vtkPolyDataVS.glsl
>> 22:
>> 23:   Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
>> 24:   All rights reserved.
>> 25:   See Copyright.txt or http://www.kitware.com/Copyright.htm for
>> details.
>> 26:
>> 27:  This software is distributed WITHOUT ANY WARRANTY; without even
>> 28:  the implied warranty of MERCHANTABILITY or FITNESS FOR A
>> PARTICULAR
>> 29:  PURPOSE.  See the above copyright notice for more information.
>> 30:
>> 31: 
>> =*/
>> 32:
>> 33: attribute vec4 vertexMC;
>> 34:
>> 35: // frag position in VC
>> 36: //VTK::PositionVC::Dec
>> 37:
>> 38: // optional normal declaration
>> 39: //VTK::Normal::Dec
>> 40:
>> 41: // extra lighting parameters
>> 42: //VTK::Light::Dec
>> 43:
>> 44: // Texture coordinates
>> 45: //VTK::TCoord::Dec
>> 46:
>> 47: // material property values
>> 48: //VTK::Color::Dec
>> 49:
>> 50: // clipping plane vars
>> 51: //VTK::Clip::Dec
>> 52:
>> 53: // camera and actor matrix values
>> 54: uniform mat4 MCDCMatrix;
>> 55:
>> 56: // Apple Bug
>> 57: //VTK::PrimID::Dec
>> 58:
>> 59: // Value raster
>> 60: //VTK::ValuePass::Dec
>> 61:
>> 62: void main()
>> 63: {
>> 64:   //VTK::Color::Impl
>> 65:
>> 66:   //VTK::Normal::Impl
>> 67:
>> 68:   //VTK::TCoord::Impl
>> 69:
>> 70:   //VTK::Clip::Impl
>> 71:
>> 72:   //VTK::PrimID::Impl
>> 73:
>> 74: gl_Position = MCDCMatrix * vertexMC;
>> 75:
>> 76:
>> 77:   //VTK::ValuePass::Impl
>> 78:
>> 79:   //VTK::Light::Impl
>>

Re: [Paraview] GoCAD and Earth Vision grid files *.ts & *.evgd

2017-11-15 Thread Aashish Chaudhary 
the actual code location is here:
https://github.com/ObjectivitySRC/PVGPlugins/tree/master/Readers/GocadReader


Let us know if you decide to bring in this code into VTK / ParaView as we
will be very interested in it as well.

Thanks,


On Wed, Nov 15, 2017 at 12:46 PM Aashish Chaudhary <
aashish.chaudh...@kitware.com> wrote:

> I do not think that GoCAR ASCII (ts) files are directly readable in
> ParaView. Although there is a reader in this repo
> http://paraviewgeo.objectivity.ca/documentation/user-manual/supported-formats 
> that
> you could bring into ParaView / VTK. If that is the case, we would be happy
> to help bringing in the reader in VTK / ParaView.
>
> thanks
>
>
> On Wed, Nov 15, 2017 at 11:10 AM Sonya Davydycheva 
> wrote:
>
>> Hello,
>>
>> 1) Is it possible to read/import GoCAD file *.ts (triangulated surfaces)
>> using ParaView, with a possibility to further read its data in ascii
>> format, or convert to a 3D function of space point (x,y,z)?
>>
>> 2) The same question about Earth Vision grid and the respective files
>> *.evgd: can I read/import them and transfer to ascii or 3D function(x,y,z)
>> using ParaView?
>>
>> Thank you,
>>
>> Sonya Davydycheva 
>> (713)498-6139
>>
>> ___
>> 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] Re: pvbatch

2017-11-15 Thread Cory Quammen 
Alan,

You should be able to run

pvpython --force-offscreen-rendering script.py

and no render window will appear. The help for --force-offscreen-rendering
says:

  "If supported by the build and platform, create headless (offscreen)
render windows for rendering results."

I believe this should work on linux systems, but you should try it out on
the system on which you want to force offscreen rendering just to be sure
before using it to produce classified images.

pvbatch running the same script will indeed not pop up a render window even
without the --force-offscreen-rendering option.

Let us know how it goes,
Cory

On Mon, Nov 13, 2017 at 5:04 PM, Scott, W Alan  wrote:

> Ben,
> I believe this is a change from the past.  Here is what I desire – how do
> I get it?
>
> I want to run pv(pythonScript).  I want it to produce output.  I want it
> to run off screen, not showing on the console display or current display.
> This is especially important on classified systems.  MPI is not available.
>
> Not too long ago, my understanding was this was pvbatch.  pvpython used
> either the console display or current display as it’s rendering space.
> This does not catch my needs.
>
> Alan
>
> On 11/13/17, 9:04 AM, "Ben Boeckel"  wrote:
>
> On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote:
> > What are the magic cmake switches, for superbuild, that are used to
> > build a non MPI, Mesa version of pvbatch?  Where is this documented?
>
> pvpython is the non-MPI version of pvbatch. The superbuild docs could
> probably be improved here. Currently, the mention is:
>
> ParaView supports multiple rendering engines including `egl`,
> `mesa`, `osmesa`, and `qt5`. All of these are incompatible with
> each
> other. If none of these are chosen, a UI-less ParaView will be
> built
> (basically just `pvpython`). On Windows and macOS, only the `qt5`
> rendering engine is available.
>
> --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
>



-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
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] GoCAD and Earth Vision grid files *.ts & *.evgd

2017-11-15 Thread Aashish Chaudhary 
I do not think that GoCAR ASCII (ts) files are directly readable in
ParaView. Although there is a reader in this repo
http://paraviewgeo.objectivity.ca/documentation/user-manual/supported-formats
that
you could bring into ParaView / VTK. If that is the case, we would be happy
to help bringing in the reader in VTK / ParaView.

thanks


On Wed, Nov 15, 2017 at 11:10 AM Sonya Davydycheva  wrote:

> Hello,
>
> 1) Is it possible to read/import GoCAD file *.ts (triangulated surfaces)
> using ParaView, with a possibility to further read its data in ascii
> format, or convert to a 3D function of space point (x,y,z)?
>
> 2) The same question about Earth Vision grid and the respective files
> *.evgd: can I read/import them and transfer to ascii or 3D function(x,y,z)
> using ParaView?
>
> Thank you,
>
> Sonya Davydycheva 
> (713)498-6139
>
> ___
> 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] How to read the file info in *pvd file

2017-11-15 Thread Ke Gao 
Hi,

I mean how to get the file name info such as "Sout_1012.pvtu",
"Sout_1013.pvtu". Currently I can only read the timestep info such as
"+1.9880e+03".

Many thanks.



  
  




On Wed, Nov 15, 2017 at 10:33 AM, Cory Quammen 
wrote:

> What do you mean by "file info"? File name? Size of the file? Data arrays
> in the file?
>
> - Cory
>
> On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao  wrote:
>
>> Does anyone know how to read the file info from *pvd file? I know how to
>> get the time step values, just using the keyword of “TimestepValues”,
>> however, I tried different ways, still haven’t figured out how to read the
>> file info.
>>
>> Thanks
>>
>> 
>>   
>>   
>> > file="Sout_1012.pvtu"/>
>> > file="Sout_1013.pvtu"/>
>> > file="Sout_1014.pvtu"/>
>> --
>> 
>> 
>> ..
>> Ke Gao
>>
>> ___
>> 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
>>
>>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>



-- 
..
Ke Gao
___
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] How to read the file info in *pvd file

2017-11-15 Thread Cory Quammen 
What do you mean by "file info"? File name? Size of the file? Data arrays
in the file?

- Cory

On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao  wrote:

> Does anyone know how to read the file info from *pvd file? I know how to
> get the time step values, just using the keyword of “TimestepValues”,
> however, I tried different ways, still haven’t figured out how to read the
> file info.
>
> Thanks
>
> 
>   
>   
> 
> 
> 
> --
> 
> 
> ..
> Ke Gao
>
> ___
> 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
>
>


-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
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] OpenGL inside VMWare virtual machine

2017-11-15 Thread Ken Martin 
This could  be a PV Qt interaction. Try setting MESA_GL_VERSION_OVERRIDE=3.2
in your environment

Basically there is a bug in Qt on windows where it refuses to see the 3.2
context from Mesa because it is not a compatibility context.

On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl <
cornelis.bockemu...@gmail.com> wrote:

> Dear all,
>
> I know that I cannot go for any performance record with this setup, but
> having both systems available without reboot has advantages if it is about
> testing some new development. WOULD have - if it fully worked! So far it
> looks like I am "almost there" - however not knowing whether the last 10
> meters will be feasible at all...
>
> This is my setup:
>
> Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
> following in the About dialog:
> OpenGL Vendor: Intel Open Source Technology Center
> OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
> OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
>
> On this system Paraview (latest version, self compiled) runs just fine.
>
> Guest system inside VMWare Player version 14: Windows 10, with Paraview
> reporting the following:
> OpenGL Vendor: VMware, Inc.
> OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
> OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
>
> Here Paraview immediately complains on startup, reporting the following in
> the message output dialog: see below.
>
> For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and Mesa
> 11.2.0 is more than 10.6.5), but there is some "fineprint" about shader
> capabilities that are going a bit above my understanding...
>
> Anybody able to help with this?
>
> Any possibility to "cheat" somehow? Note that I am certainly not going to
> render billions of data in this configuration!
>
> Or should I abandon this tricky setup altogether?
>
> Thanks and regards,
> Cornelis
>
> Here the error output from the Windows Paraview inside the VMWare virtual
> machine:
>
> ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\
> OpenGL2\vtkOpenGLRenderWindow.cxx, line 831
> vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with the
> gpu_shader4 extension is not supported by your graphics driver but is
> required for the new OpenGL rendering backend. Please update your OpenGL
> driver. If you are using Mesa please make sure you have version 10.6.5 or
> later and make sure your driver in Mesa supports OpenGL 3.2.
>
> ERROR: In 
> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 408
> vtkShaderProgram (02438C1B80C0): 1: #version 150
> 2: #ifdef GL_ES
> 3: #if __VERSION__ == 300
> 4: #define attribute in
> 5: #define varying out
> 6: #endif // 300
> 7: #else // GL_ES
> 8: #define highp
> 9: #define mediump
> 10: #define lowp
> 11: #if __VERSION__ == 150
> 12: #define attribute in
> 13: #define varying out
> 14: #endif
> 15: #endif // GL_ES
> 16:
> 17:
> 18: /*==
> ===
> 19:
> 20:   Program:   Visualization Toolkit
> 21:   Module:vtkPolyDataVS.glsl
> 22:
> 23:   Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
> 24:   All rights reserved.
> 25:   See Copyright.txt or http://www.kitware.com/Copyright.htm for
> details.
> 26:
> 27:  This software is distributed WITHOUT ANY WARRANTY; without even
> 28:  the implied warranty of MERCHANTABILITY or FITNESS FOR A
> PARTICULAR
> 29:  PURPOSE.  See the above copyright notice for more information.
> 30:
> 31: 
> =*/
> 32:
> 33: attribute vec4 vertexMC;
> 34:
> 35: // frag position in VC
> 36: //VTK::PositionVC::Dec
> 37:
> 38: // optional normal declaration
> 39: //VTK::Normal::Dec
> 40:
> 41: // extra lighting parameters
> 42: //VTK::Light::Dec
> 43:
> 44: // Texture coordinates
> 45: //VTK::TCoord::Dec
> 46:
> 47: // material property values
> 48: //VTK::Color::Dec
> 49:
> 50: // clipping plane vars
> 51: //VTK::Clip::Dec
> 52:
> 53: // camera and actor matrix values
> 54: uniform mat4 MCDCMatrix;
> 55:
> 56: // Apple Bug
> 57: //VTK::PrimID::Dec
> 58:
> 59: // Value raster
> 60: //VTK::ValuePass::Dec
> 61:
> 62: void main()
> 63: {
> 64:   //VTK::Color::Impl
> 65:
> 66:   //VTK::Normal::Impl
> 67:
> 68:   //VTK::TCoord::Impl
> 69:
> 70:   //VTK::Clip::Impl
> 71:
> 72:   //VTK::PrimID::Impl
> 73:
> 74: gl_Position = MCDCMatrix * vertexMC;
> 75:
> 76:
> 77:   //VTK::ValuePass::Impl
> 78:
> 79:   //VTK::Light::Impl
> 80: }
> 81:
>
>
> ERROR: In 
> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 409
> vtkShaderProgram (02438C1B80C0): 0:1(10): error: GLSL 1.50 is not
> supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
>

Re: [Paraview] [EXT] Re: Exodus multiblock dataset block numbers vs block

2017-11-15 Thread Dennis Conklin 
Shawn,

I grok the origin of the non-intuitive, better omitted than displayed, highly 
confusing, should be replaced with block names, block numbers.However, in 
my Programmable filter I just have a single block and I need the index into the 
block name – I’m not sure it exists anywhere that I can access.

Dennis

From: Shawn Waldon [mailto:shawn.wal...@kitware.com]
Sent: Wednesday, November 15, 2017 10:01 AM
To: Dennis Conklin 
Cc: Paraview (paraview@paraview.org) 
Subject: [EXT] Re: [Paraview] Exodus multiblock dataset block numbers vs block

 WARNING - External email; exercise caution.



Hi Dennis,
I can answer part of your question.  The block number is the index in a 
pre-order traversal of the tree of blocks in the dataset.  The root is element 
0, its first child is 1, that block's first child (or if none, the root's 
second child) is 2 and so on.  Your blocks with data are likely two levels down 
since your index has that offset (and your code backs this up since you are 
asking for the metadata of a child of the root's block 0).
HTH,
Shawn

On Wed, Nov 15, 2017 at 9:51 AM, Dennis Conklin 
> wrote:
All,

Okay, maybe not the clearest email I’ve ever written!

See the attached image:  Here I have loaded a single block out of a multi-block 
dataset.

It is the 24th block in the dataset.
It was assigned the block_ID 101 at creation (we separate different blocks into 
different number ranges)
So, it is shown in the Spreadsheet view as Block Number 25 (24+1)

However, I need the Block_Name of this block.   The block name is stored under:
Input.GetBlock(0).GetMetaData(23).Get(vtk.vtkCompositeDataSet.NAME())
   (23=24-1)

In order to retrieve the name, I need to find the Block Number 25 (and subtract 
2 from it).

I have been unable to find this block_number.I can’t count blocks to find 
out the block_number, because my Programmable filter only has this 1 block in 
it.

So, does anyone know where this “Block Number” is stored?I’m wishing at 
this point that the Exodus reader had stored the block names in a dictionary 
with BlockID (ObjectID) as the key – then I could find  the name.

Any clues on how to determine the Block Number?

Thanks
Dennis

___
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] GoCAD and Earth Vision grid files *.ts & *.evgd

2017-11-15 Thread Sonya Davydycheva 
Hello,

1) Is it possible to read/import GoCAD file *.ts (triangulated surfaces)
using ParaView, with a possibility to further read its data in ascii
format, or convert to a 3D function of space point (x,y,z)?

2) The same question about Earth Vision grid and the respective files
*.evgd: can I read/import them and transfer to ascii or 3D function(x,y,z)
using ParaView?

Thank you,

Sonya Davydycheva 
(713)498-6139
___
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] OpenGL inside VMWare virtual machine

2017-11-15 Thread Cornelis Bockemühl 
Dear all,

I know that I cannot go for any performance record with this setup, but
having both systems available without reboot has advantages if it is
about testing some new development. WOULD have - if it fully worked! So
far it looks like I am "almost there" - however not knowing whether the
last 10 meters will be feasible at all...

This is my setup:

Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
following in the About dialog:
OpenGL Vendor: Intel Open Source Technology Center
OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile

On this system Paraview (latest version, self compiled) runs just fine.

Guest system inside VMWare Player version 14: Windows 10, with Paraview
reporting the following:
OpenGL Vendor: VMware, Inc.
OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;

Here Paraview immediately complains on startup, reporting the following
in the message output dialog: see below.

For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and
Mesa 11.2.0 is more than 10.6.5), but there is some "fineprint" about
shader capabilities that are going a bit above my understanding...

Anybody able to help with this?

Any possibility to "cheat" somehow? Note that I am certainly not going
to render billions of data in this configuration!

Or should I abandon this tricky setup altogether?

Thanks and regards,
Cornelis

Here the error output from the Windows Paraview inside the VMWare
virtual machine:

ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 831
vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with
the gpu_shader4 extension is not supported by your graphics driver but
is required for the new OpenGL rendering backend. Please update your
OpenGL driver. If you are using Mesa please make sure you have version
10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2.

ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 408
vtkShaderProgram (02438C1B80C0): 1: #version 150
2: #ifdef GL_ES
3: #if __VERSION__ == 300
4: #define attribute in
5: #define varying out
6: #endif // 300
7: #else // GL_ES
8: #define highp
9: #define mediump
10: #define lowp
11: #if __VERSION__ == 150
12: #define attribute in
13: #define varying out
14: #endif
15: #endif // GL_ES
16: 
17: 
18:
/*=

19: 
20:   Program:   Visualization Toolkit
21:   Module:vtkPolyDataVS.glsl
22: 
23:   Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
24:   All rights reserved.
25:   See Copyright.txt or http://www.kitware.com/Copyright.htm for
details.
26: 
27:  This software is distributed WITHOUT ANY WARRANTY; without
even
28:  the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR
29:  PURPOSE.  See the above copyright notice for more information.
30: 
31:
===
==*/
32: 
33: attribute vec4 vertexMC;
34: 
35: // frag position in VC
36: //VTK::PositionVC::Dec
37: 
38: // optional normal declaration
39: //VTK::Normal::Dec
40: 
41: // extra lighting parameters
42: //VTK::Light::Dec
43: 
44: // Texture coordinates
45: //VTK::TCoord::Dec
46: 
47: // material property values
48: //VTK::Color::Dec
49: 
50: // clipping plane vars
51: //VTK::Clip::Dec
52: 
53: // camera and actor matrix values
54: uniform mat4 MCDCMatrix;
55: 
56: // Apple Bug
57: //VTK::PrimID::Dec
58: 
59: // Value raster
60: //VTK::ValuePass::Dec
61: 
62: void main()
63: {
64:   //VTK::Color::Impl
65: 
66:   //VTK::Normal::Impl
67: 
68:   //VTK::TCoord::Impl
69: 
70:   //VTK::Clip::Impl
71: 
72:   //VTK::PrimID::Impl
73: 
74: gl_Position = MCDCMatrix * vertexMC;
75: 
76: 
77:   //VTK::ValuePass::Impl
78: 
79:   //VTK::Light::Impl
80: }
81: 


ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 409
vtkShaderProgram (02438C1B80C0): 0:1(10): error: GLSL 1.50 is not
supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00
ES___
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] Exodus multiblock dataset block numbers vs block

2017-11-15 Thread Shawn Waldon 
Hi Dennis,

I can answer part of your question.  The block number is the index in a
pre-order traversal of the tree of blocks in the dataset.  The root is
element 0, its first child is 1, that block's first child (or if none, the
root's second child) is 2 and so on.  Your blocks with data are likely two
levels down since your index has that offset (and your code backs this up
since you are asking for the metadata of a child of the root's block 0).

HTH,
Shawn

On Wed, Nov 15, 2017 at 9:51 AM, Dennis Conklin  wrote:

> All,
>
>
>
> Okay, maybe not the clearest email I’ve ever written!
>
>
>
> See the attached image:  Here I have loaded a single block out of a
> multi-block dataset.
>
>
>
> It is the 24th block in the dataset.
>
> It was assigned the block_ID 101 at creation (we separate different blocks
> into different number ranges)
>
> So, it is shown in the Spreadsheet view as Block Number 25 (24+1)
>
>
>
> However, I need the Block_Name of this block.   The block name is stored
> under:
>
> Input.GetBlock(0).GetMetaData(23).Get(vtk.vtkCompositeDataSet.NAME())
> (23=24-1)
>
>
>
> In order to retrieve the name, I need to find the Block Number 25 (and
> subtract 2 from it).
>
>
>
> I have been unable to find this block_number.I can’t count blocks to
> find out the block_number, because my Programmable filter only has this 1
> block in it.
>
>
>
> So, does anyone know where this “Block Number” is stored?I’m wishing
> at this point that the Exodus reader had stored the block names in a
> dictionary with BlockID (ObjectID) as the key – then I could find  the name.
>
>
>
> Any clues on how to determine the Block Number?
>
>
>
> Thanks
>
> Dennis
>
> ___
> 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] Exodus multiblock dataset block numbers vs block

2017-11-15 Thread Dennis Conklin 
All,

Okay, maybe not the clearest email I've ever written!

See the attached image:  Here I have loaded a single block out of a multi-block 
dataset.

It is the 24th block in the dataset.
It was assigned the block_ID 101 at creation (we separate different blocks into 
different number ranges)
So, it is shown in the Spreadsheet view as Block Number 25 (24+1)

However, I need the Block_Name of this block.   The block name is stored under:
Input.GetBlock(0).GetMetaData(23).Get(vtk.vtkCompositeDataSet.NAME())   
(23=24-1)

In order to retrieve the name, I need to find the Block Number 25 (and subtract 
2 from it).

I have been unable to find this block_number.I can't count blocks to find 
out the block_number, because my Programmable filter only has this 1 block in 
it.

So, does anyone know where this "Block Number" is stored?I'm wishing at 
this point that the Exodus reader had stored the block names in a dictionary 
with BlockID (ObjectID) as the key - then I could find  the name.

Any clues on how to determine the Block Number?

Thanks
Dennis
___
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: pvbatch

2017-11-15 Thread Ben Boeckel 
On Mon, Nov 13, 2017 at 22:04:19 +, Scott, W Alan wrote:
> I believe this is a change from the past.  Here is what I desire – how
> do I get it?
> 
> I want to run pv(pythonScript).  I want it to produce output.  I want
> it to run off screen, not showing on the console display or current
> display.  This is especially important on classified systems.  MPI is
> not available.
> 
> Not too long ago, my understanding was this was pvbatch.  pvpython
> used either the console display or current display as it’s rendering
> space.  This does not catch my needs.

Yeah, it seems I was mistaken. pvbatch is not conditional on MPI. If the
superbuild is built with mesa and Python and without MPI, pvbatch should
be there. I've filed an MR to fix the packaging/install step in the
superbuild:

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/388

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