Re: [Paraview] Error message: Not supported on OpenGL ES when I launch Paraview

2017-09-08 Thread Cory Quammen
Not seeing anything with Qt is a good thing in that it means some
other software installed on your system is not interfering with
ParaView's operation. That bad news is that I'm out of ideas on what
might be causing your problem.

Maybe a graphics card driver update would help?

Cory

On Fri, Sep 8, 2017 at 10:51 AM, Antonio Orlando
 wrote:
> Cory:
>
> I did what you were saying and there is no location listed with "Qt"
> in the Environment Variables.
>
> Is that the problem? If so, what should I then do?
>
> Many thanks again
> Regards
>
> Antonio
>
> 2017-09-08 10:42 GMT-03:00, Cory Quammen :
>> Antonio,
>>
>> No worries! We do run into issues from time to time on other Windows
>> machines, so we are happy to help you work through the kinks so that
>> we can understand the potential issues out there.
>>
>> One other thing to look for:
>>
>>  See if you have a different Qt installation on your system whose path
>> is in your PATH environment variable. To check, click on the
>> Start/Windows menu. Type in "environment" and select "Edit the system
>> environment variables". In the System Properties dialog that shows up,
>> click on the "Environment Variables..." button on the bottom right.
>> This brings up an Environment Variables dialog with user variables in
>> the top panel and system variables in the bottom panel. Look at the
>> Path variables and see if there is a location listed with "Qt" in the
>> name, or if you have a program that might use its own Qt.
>>
>> Also look to see if an environment variable named QT_PLUGIN_PATH is
>> set. If it is set, it will confuse ParaView as it loads Qt and it
>> might result in this error. We have seen this in one other Windows
>> machine.
>>
>> Best regards,
>> Cory
>>
>> On Fri, Sep 8, 2017 at 9:21 AM, Antonio Orlando
>>  wrote:
>>> Cory:
>>>
>>> I am sorry, but I am still getting the same error message.
>>>
>>> I fear that there might something wrong then with my system if other
>>> paraview user using windows do not have problems.
>>>
>>> I will try to download and install paraview on another computer and
>>> let you know.
>>> I am sorry for all the inconveniences I am causing.
>>>
>>> Many thanks for your time and attention.
>>>
>>> Kind regards
>>>
>>> Antonio
>>>
>>>
>>> 2017-09-08 10:00 GMT-03:00, Cory Quammen :
 Antonio,

 Do you happen to have an integrated graphics chip on your laptop? I
 wonder if ParaView is set to use integrated graphics rather than your
 NVIDIA card and isn't liking what it finds. You can try going to the
 NVIDIA control panel. Under 3D Settings in the panel on the left,
 click on "Manage 3D settings". On the right side, click on the "Global
 Settings" tab. Make sure "High-performance NVIDIA processor" is
 selected. Apply the changes, then run ParaView again to see if the
 problem is resolved.

 - Cory

 On Thu, Sep 7, 2017 at 6:50 PM, Antonio Orlando
  wrote:
> Thanks Cory for your prompt reply and sorry for not sending the
> message to the mailing list.
>
> I have the graphics card NVIDIA GeForce GT 750M 2GB DDR5
>
> I can run though Paraview 4.
>
> Thanks again for your attention to this matter.
>
> Cheers
> Antonio
>
>
> 2017-09-07 17:59 GMT-03:00, Cory Quammen :
>> Antonio,
>>
>> I'm adding back Utkarsh, who pointed you to the mesa libraries. Please
>> also reply to the mailing list so that others may benefit from and
>> contribute to the discussion.
>>
>> What kind of graphics hardware do you have on that machine?
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Thu, Sep 7, 2017 at 4:57 PM, Antonio Orlando
>>  wrote:
>>> Hi Cory:
>>>
>>> Thanks for your message and for the drivers.
>>>
>>> I am sorry but it is still not working!
>>>
>>> The error message I get is the following.
>>>
>>> ---
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
>>> line 819
>>> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
>>> initialized.
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
>>> line 819
>>> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
>>> initialized.
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
>>> line 453
>>> vtkShaderProgram (00214CB8B7A0): Shader object was not
>>> initialized, cannot attach it.
>>>
>>> ERROR: In

Re: [Paraview] Error message: Not supported on OpenGL ES when I launch Paraview

2017-09-08 Thread Cory Quammen
Antonio,

No worries! We do run into issues from time to time on other Windows
machines, so we are happy to help you work through the kinks so that
we can understand the potential issues out there.

One other thing to look for:

 See if you have a different Qt installation on your system whose path
is in your PATH environment variable. To check, click on the
Start/Windows menu. Type in "environment" and select "Edit the system
environment variables". In the System Properties dialog that shows up,
click on the "Environment Variables..." button on the bottom right.
This brings up an Environment Variables dialog with user variables in
the top panel and system variables in the bottom panel. Look at the
Path variables and see if there is a location listed with "Qt" in the
name, or if you have a program that might use its own Qt.

Also look to see if an environment variable named QT_PLUGIN_PATH is
set. If it is set, it will confuse ParaView as it loads Qt and it
might result in this error. We have seen this in one other Windows
machine.

Best regards,
Cory

On Fri, Sep 8, 2017 at 9:21 AM, Antonio Orlando
 wrote:
> Cory:
>
> I am sorry, but I am still getting the same error message.
>
> I fear that there might something wrong then with my system if other
> paraview user using windows do not have problems.
>
> I will try to download and install paraview on another computer and
> let you know.
> I am sorry for all the inconveniences I am causing.
>
> Many thanks for your time and attention.
>
> Kind regards
>
> Antonio
>
>
> 2017-09-08 10:00 GMT-03:00, Cory Quammen :
>> Antonio,
>>
>> Do you happen to have an integrated graphics chip on your laptop? I
>> wonder if ParaView is set to use integrated graphics rather than your
>> NVIDIA card and isn't liking what it finds. You can try going to the
>> NVIDIA control panel. Under 3D Settings in the panel on the left,
>> click on "Manage 3D settings". On the right side, click on the "Global
>> Settings" tab. Make sure "High-performance NVIDIA processor" is
>> selected. Apply the changes, then run ParaView again to see if the
>> problem is resolved.
>>
>> - Cory
>>
>> On Thu, Sep 7, 2017 at 6:50 PM, Antonio Orlando
>>  wrote:
>>> Thanks Cory for your prompt reply and sorry for not sending the
>>> message to the mailing list.
>>>
>>> I have the graphics card NVIDIA GeForce GT 750M 2GB DDR5
>>>
>>> I can run though Paraview 4.
>>>
>>> Thanks again for your attention to this matter.
>>>
>>> Cheers
>>> Antonio
>>>
>>>
>>> 2017-09-07 17:59 GMT-03:00, Cory Quammen :
 Antonio,

 I'm adding back Utkarsh, who pointed you to the mesa libraries. Please
 also reply to the mailing list so that others may benefit from and
 contribute to the discussion.

 What kind of graphics hardware do you have on that machine?

 Thanks,
 Cory



 On Thu, Sep 7, 2017 at 4:57 PM, Antonio Orlando
  wrote:
> Hi Cory:
>
> Thanks for your message and for the drivers.
>
> I am sorry but it is still not working!
>
> The error message I get is the following.
>
> ---
>
> ERROR: In
> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
> line 819
> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
> initialized.
>
> ERROR: In
> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
> line 819
> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
> initialized.
>
> ERROR: In
> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 453
> vtkShaderProgram (00214CB8B7A0): Shader object was not
> initialized, cannot attach it.
>
> ERROR: In
> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 408
> vtkShaderProgram (00214CB8B7A0): 1: #version 120
> 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 

Re: [Paraview] Error message: Not supported on OpenGL ES when I launch Paraview

2017-09-08 Thread Antonio Orlando
Cory:

I am sorry, but I am still getting the same error message.

I fear that there might something wrong then with my system if other
paraview user using windows do not have problems.

I will try to download and install paraview on another computer and
let you know.
I am sorry for all the inconveniences I am causing.

Many thanks for your time and attention.

Kind regards

Antonio


2017-09-08 10:00 GMT-03:00, Cory Quammen :
> Antonio,
>
> Do you happen to have an integrated graphics chip on your laptop? I
> wonder if ParaView is set to use integrated graphics rather than your
> NVIDIA card and isn't liking what it finds. You can try going to the
> NVIDIA control panel. Under 3D Settings in the panel on the left,
> click on "Manage 3D settings". On the right side, click on the "Global
> Settings" tab. Make sure "High-performance NVIDIA processor" is
> selected. Apply the changes, then run ParaView again to see if the
> problem is resolved.
>
> - Cory
>
> On Thu, Sep 7, 2017 at 6:50 PM, Antonio Orlando
>  wrote:
>> Thanks Cory for your prompt reply and sorry for not sending the
>> message to the mailing list.
>>
>> I have the graphics card NVIDIA GeForce GT 750M 2GB DDR5
>>
>> I can run though Paraview 4.
>>
>> Thanks again for your attention to this matter.
>>
>> Cheers
>> Antonio
>>
>>
>> 2017-09-07 17:59 GMT-03:00, Cory Quammen :
>>> Antonio,
>>>
>>> I'm adding back Utkarsh, who pointed you to the mesa libraries. Please
>>> also reply to the mailing list so that others may benefit from and
>>> contribute to the discussion.
>>>
>>> What kind of graphics hardware do you have on that machine?
>>>
>>> Thanks,
>>> Cory
>>>
>>>
>>>
>>> On Thu, Sep 7, 2017 at 4:57 PM, Antonio Orlando
>>>  wrote:
 Hi Cory:

 Thanks for your message and for the drivers.

 I am sorry but it is still not working!

 The error message I get is the following.

 ---

 ERROR: In
 C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
 line 819
 vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
 initialized.

 ERROR: In
 C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
 line 819
 vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
 initialized.

 ERROR: In
 C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
 line 453
 vtkShaderProgram (00214CB8B7A0): Shader object was not
 initialized, cannot attach it.

 ERROR: In
 C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
 line 408
 vtkShaderProgram (00214CB8B7A0): 1: #version 120
 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:   

Re: [Paraview] Error message: Not supported on OpenGL ES when I launch Paraview

2017-09-08 Thread Cory Quammen
Antonio,

Do you happen to have an integrated graphics chip on your laptop? I
wonder if ParaView is set to use integrated graphics rather than your
NVIDIA card and isn't liking what it finds. You can try going to the
NVIDIA control panel. Under 3D Settings in the panel on the left,
click on "Manage 3D settings". On the right side, click on the "Global
Settings" tab. Make sure "High-performance NVIDIA processor" is
selected. Apply the changes, then run ParaView again to see if the
problem is resolved.

- Cory

On Thu, Sep 7, 2017 at 6:50 PM, Antonio Orlando
 wrote:
> Thanks Cory for your prompt reply and sorry for not sending the
> message to the mailing list.
>
> I have the graphics card NVIDIA GeForce GT 750M 2GB DDR5
>
> I can run though Paraview 4.
>
> Thanks again for your attention to this matter.
>
> Cheers
> Antonio
>
>
> 2017-09-07 17:59 GMT-03:00, Cory Quammen :
>> Antonio,
>>
>> I'm adding back Utkarsh, who pointed you to the mesa libraries. Please
>> also reply to the mailing list so that others may benefit from and
>> contribute to the discussion.
>>
>> What kind of graphics hardware do you have on that machine?
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Thu, Sep 7, 2017 at 4:57 PM, Antonio Orlando
>>  wrote:
>>> Hi Cory:
>>>
>>> Thanks for your message and for the drivers.
>>>
>>> I am sorry but it is still not working!
>>>
>>> The error message I get is the following.
>>>
>>> ---
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
>>> line 819
>>> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
>>> initialized.
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx,
>>> line 819
>>> vtkGenericOpenGLRenderWindow (00214C5F3460): GLEW could not be
>>> initialized.
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
>>> line 453
>>> vtkShaderProgram (00214CB8B7A0): Shader object was not
>>> initialized, cannot attach it.
>>>
>>> ERROR: In
>>> C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
>>> line 408
>>> vtkShaderProgram (00214CB8B7A0): 1: #version 120
>>> 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:
>>>
>>> --
>>>
>>> Does this have something to do with my graphics card?
>>>
>>> Many thanks for your attention.
>>>
>>> Kind regards
>>>
>>> Antonio
>>>
>>>
>>>
>>>
>>>
>>> 2017-09-07 17:06 GMT-03:00, Cory Quammen :
 Hi Antonio,

 I have reported an issue for this so we can track the issue:
 

Re: [Paraview] Opacity editor with log scale

2017-09-08 Thread Utkarsh Ayachit
Steven,

That's done so because the opacity mapping doesn't support log scale yet.

Utkarsh

On Thu, Sep 7, 2017 at 6:28 PM, Hahn, Steven E.  wrote:
> Hi,
>
>
>
> I noticed that when “Use log scale when mapping data to colors” is selected,
> the color opacity editor isn’t being rescaled to reflect this. In the
> attached screenshot only the red portion of the color map is visible in the
> editor, suggesting the x axis remains linear. In contrast, the color legend
> rescales so that while the values change, colors stay the same.
>
>
>
> Would it be more intuitive for the opacity editor to behave more like the
> color legend? Or is keeping the color map linear in the opacity editor by
> design?
>
>
>
> Best,
>
> Steven
>
>
> ___
> 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] Question about animation background size

2017-09-08 Thread Utkarsh Ayachit
Does your current window size and target image size for the animation
differ in aspect ratio? That's one reason why animation view may not
match your expectation. With ParaView 5.5, there will be a "Preview"
mode which allow you to set up your viz to match the target aspect
(see https://gitlab.kitware.com/paraview/paraview/merge_requests/1733).
With 5.4 and earlier, you can use "Tools | Lock View Size Custom" to
lock the view size to an aspect ratio matching your target resolution
and then zoom in/out as needed to ensure a better fit.

Utkarsh

On Thu, Sep 7, 2017 at 6:42 PM, Li, Teng  wrote:
> Hi,
>
> I have a question about saving animation. I find that when I try to save the
> animation, the main model only occupies a small space. The background will
> occupy a large space. I wonder how can I save the animation to make sure not
> only the whole main body will show in the video, but also the background
> area is very small.
>
> Thanks!
>
> Best,
> Teng
>
> Teng Li
>
> Master Candidate in Structures
>
> Department of Civil and Environmental Engineering
>
> University of Illinois at Urbana-Champaign
>
> 205 North Mathews Ave, Urbana, IL. 61801
>
> Phone:(217)8196210, Email: teng...@illinois.edu
>
>
>
>
> ___
> 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] Read files in different folders at the same time

2017-09-08 Thread Utkarsh Ayachit
I am afraid that's not possible currently. A workaround is to create a
pvd file as follows:



  





  


Make sure that header matches the header in one of the vtu files.

Utkarsh

On Thu, Sep 7, 2017 at 7:04 PM, Ke Gao  wrote:
> Hi all,
>
> When I do the simulation, I restart the computation and as a result there
> are files generated in different folders but with sequential vtu file names.
> For example, in the first folder we have vtu files numbered from 0 to 100,
> and in the second folder we have vtu files from 101 to 200. I wonder if
> there is a convenient way to animate all these 200 files in one setup,
> without copy them into the same folder?
>
> 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
>
___
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