From dave.demarle at kitware.com  Sun Jul  2 07:09:43 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sun, 2 Jul 2017 07:09:43 -0400
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
Message-ID: <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>

These are most likely caused by a known bug in 5.4.0 with some graphics
hardware that we are trying to fix in 5.4.1. Can you let us know what your
gpu is? Also try 5.3 and let us know if both problems work there.

Thanks

On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com> wrote:

> Hi,
>
>
>
> I downloaded the ParaView Binary Installers (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe)
> from https://www.paraview.org/download/ and installed it on my Thinkpad
> T430 which is running Windows 10. I was using ParaView for the first time
> and found two things puzzling:
>
> 1.       When I open ParaView, the default window looks like the
> following. There is a small black square on the bottom left corner in
> RenderView1 (circled in red). I couldn?t figure out why it showed up there.
>
> 2.       Then I opened the first Example Visualization and selected Clip2
> under can.ex2. When I tried to adjust the Opacity under Styling in the
> Properties tab, any value other than 1 will make the object in the
> RenderView1 window disappear like the following:
>
> I tried other examples, and similar things happened. I couldn?t figure out
> why.
>
>
>
> Does anybody know what might be going on and how I can fix it?
>
>
>
> Thanks,
>
> Yu
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/812afeb1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/812afeb1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/812afeb1/attachment-0003.png>

From ezhkr601 at student.liu.se  Sun Jul  2 07:37:37 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Sun, 2 Jul 2017 13:37:37 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
Message-ID: <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>

Hi,

I have followed these instructions. I am trying to install it where I am
not a root user.
Can someone help to fix this issue.

 git clone --recursive
https://gitlab.kitware.com/paraview/paraview-superbuild.git
 cd paraview-superbuild
 git fetch origin # ensure you have the latest state from the main repo
 git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
 git submodule update

 cd ..
 mkdir build
 cd build
 ccmake ../paraview-superbuild

Kind regards,
Mathi


On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
wrote:

> Hi Thanks!
>
> When I try to install Paraview,  I am getting the following error.
> Could some one please tell me how to fix this issue.
> I am trying to install the Paraview on a super computer to use it
> for remote rendering without using the GUI,  like with mesa support.
>
> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> git
> clone --recursive https://gitlab.kitware.com/paraview/paraview-superbuild.
> git
> Cloning into 'paraview-superbuild'...
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> remote: Counting objects: 6723, done.
> remote: Compressing objects: 100% (2459/2459), done.
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
> Resolving deltas: 100% (4451/4451), done.
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> Checking out files: 100% (196/196), done.
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> Submodule 'superbuild' (https://gitlab.kitware.com/
> paraview/common-superbuild.git) registered for path 'superbuild'
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> Cloning into 'superbuild'...
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> remote: Counting objects: 6752, done.
> remote: Compressing objects: 100% (2235/2235), done.
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
> Resolving deltas: 100% (4505/4505), done.
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> Submodule path 'superbuild': checked out '8f357bb5bf35419c210b3f9e0adbc9
> df08f565f2'
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> Permission denied
>
>
> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
> cmake .
> -- The C compiler identification is Intel 14.0.4.20140805
> -- The CXX compiler identification is Intel 14.0.4.20140805
> -- Cray Programming Environment 2.2.1 C
> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Cray Programming Environment 2.2.1 CXX
> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>   Failed to determine if the common superbuild is an old checkout.  The
>   common superbuild may be out of date, but cannot be verified.: warning:
>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig': Permission
>   denied
>
>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>   Permission denied
>
>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>   Permission denied
>
>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>   Permission denied
>
>   error: unknown option `is-ancestor'
>
>   usage: git merge-base [-a|--all] <commit> <commit>...
>
>      or: git merge-base [-a|--all] --octopus <commit>...
>      or: git merge-base --independent <commit>...
>
>
>
>       -a, --all             output all common ancestors
>       --octopus             find ancestors for a single n-way merge
>       --independent         list revs not reachable from others
> Call Stack (most recent call first):
>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>
>
> -- Check size of void*
> -- Check size of void* - done
> -- Found Git: /usr/bin/git (found version "1.7.12.4")
> -- Determined source version for paraview: 5.4.0
> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>   The build tree appears to be inside of the git repository located at
>   /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild.
>   This interferes with the way the superbuild applies patches to projects
> and
>   is not supported.  Please relocate the build tree to a directory which is
>   not under a git repository.
> Call Stack (most recent call first):
>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>
>
> -- Configuring incomplete, errors occurred!
> See also "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-
> superbuild/CMakeFiles/CMakeOutput.log".
>
>
> Kind regards,
> Mathi
>
>
>
>
>
> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com> wrote:
>
>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>> <ezhkr601 at student.liu.se> wrote:
>> > Hi,
>> >
>> > Can anyone please give me some instructions how to Paraview Superbuid
>> > to install and use them with out using the GUI (using the python script
>> to
>> > render the images on the cluster or super computer).
>> >
>> > I see there are some instructions in here:
>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>> >
>> > But I could not find any build instructions.
>>
>> Take a look again, that page includes the README.md file contents
>> which includes build instructions.
>>
>> To build without the GUI, you should just need to set the options
>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>> ENABLE_python to ON.
>>
>> Best regards,
>> Cory
>>
>> >
>> > Kind regards,
>> > Mathi
>> >
>> > _______________________________________________
>> > 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&D Engineer
>> Kitware, Inc.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/2f742f5d/attachment.html>
-------------- next part --------------

 I have followed these instrunctions 

 git clone --recursive https://gitlab.kitware.com/paraview/paraview-superbuild.git
 cd paraview-superbuild
 git fetch origin # ensure you have the latest state from the main repo
 git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
 git submodule update

 cd ..
 mkdir build
 cmmake ../paraview-superbuild


 after this I am getting this error.


 CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
   Failed to determine if the common superbuild is an old checkout.  The
   common superbuild may be out of date, but cannot be verified.: error:
   unknown option `is-ancestor'

   usage: git merge-base [-a|--all] <commit> <commit>...

      or: git merge-base [-a|--all] --octopus <commit>...
      or: git merge-base --independent <commit>...



       -a, --all             output all common ancestors
       --octopus             find ancestors for a single n-way merge
       --independent         list revs not reachable from others
 Call Stack (most recent call first):
   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)



 CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
   The build tree appears to be inside of the git repository located at
   /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD.  This interferes with
   the way the superbuild applies patches to projects and is not supported.
   Please relocate the build tree to a directory which is not under a git
   repository.
 Call Stack (most recent call first):
   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
   superbuild/cmake/SuperbuildMacros.cmake:477 (include)


                                                     Page 1 of 1
 BUILD_SHARED_LIBS                ON                                                                                                                   
 CMAKE_INSTALL_PREFIX             /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD                                                                 
 ENABLE_boost                     OFF                                                                                                                  
 ENABLE_bzip2                     OFF                                                                                                                  
 ENABLE_cxx11                     OFF                                                                                                                  
 ENABLE_paraview                  OFF                                                                                                                  
 ENABLE_paraviewpluginsexternal   ON                                                                                                                   
 ENABLE_python                    ON                                                                                                                   
 PARAVIEW_BUILD_WEB_DOCUMENTATI   OFF                                                                                                                  
 PARAVIEW_DEFAULT_SYSTEM_GL       ON                                                                                                                   
 PARAVIEW_FREEZE_PYTHON           OFF                                                                                                                  
 PARAVIEW_RENDERING_BACKEND       OpenGL2                                                                                                              
 SUPERBUILD_OFFLINE_BUILD         ON                                                                                                                   
 paraview_PLUGINS_EXTERNAL                                                                                                                             
 paraview_SOURCE_SELECTION        5.4.0                                                                                                                
 vtkm_SOURCE_SELECTION            git-stable                                                                                                           





From Patrick.Begou at legi.grenoble-inp.fr  Sun Jul  2 08:03:20 2017
From: Patrick.Begou at legi.grenoble-inp.fr (=?UTF-8?Q?Patrick_B=c3=a9gou?=)
Date: Sun, 2 Jul 2017 14:03:20 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
Message-ID: <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>

Like you, I got this error some months ago when trying to build paraview 
superbuild:

/error: unknown option `is-ancestor'//
/
It was my git version wich was too old. May be try to compile a more up 
to date version of git in your home and set the path to access it.

I have installed git from 
https://www.kernel.org/pub/software/scm/git/git-2.12.2.tar.xz

Patrick

Ezhilmathi Krishnasamy a ?crit :
> Hi,
>
> I have followed these instructions. I am trying to install it where I 
> am not a root user.
> Can someone help to fix this issue.
>
>  git clone --recursive 
> https://gitlab.kitware.com/paraview/paraview-superbuild.git
>  cd paraview-superbuild
>  git fetch origin # ensure you have the latest state from the main repo
>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>  git submodule update
>
>  cd ..
>  mkdir build
>  cd build
>  ccmake ../paraview-superbuild
>
> Kind regards,
> Mathi
>
>
> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy 
> <ezhkr601 at student.liu.se <mailto:ezhkr601 at student.liu.se>> wrote:
>
>     Hi Thanks!
>
>     When I try to install Paraview,  I am getting the following error.
>     Could some one please tell me how to fix this issue.
>     I am trying to install the Paraview on a super computer to use it
>     for remote rendering without using the GUI,  like with mesa support.
>
>     kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD>
>     git clone --recursive
>     https://gitlab.kitware.com/paraview/paraview-superbuild.git
>     <https://gitlab.kitware.com/paraview/paraview-superbuild.git>
>     Cloning into 'paraview-superbuild'...
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     remote: Counting objects: 6723, done.
>     remote: Compressing objects: 100% (2459/2459), done.
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>     Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>     Resolving deltas: 100% (4451/4451), done.
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     Checking out files: 100% (196/196), done.
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     Submodule 'superbuild'
>     (https://gitlab.kitware.com/paraview/common-superbuild.git
>     <https://gitlab.kitware.com/paraview/common-superbuild.git>)
>     registered for path 'superbuild'
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     Cloning into 'superbuild'...
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     remote: Counting objects: 6752, done.
>     remote: Compressing objects: 100% (2235/2235), done.
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>     Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>     Resolving deltas: 100% (4505/4505), done.
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     Submodule path 'superbuild': checked out
>     '8f357bb5bf35419c210b3f9e0adbc9df08f565f2'
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>     warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission denied
>
>
>     kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>     cmake .
>     -- The C compiler identification is Intel 14.0.4.20140805
>     -- The CXX compiler identification is Intel 14.0.4.20140805
>     -- Cray Programming Environment 2.2.1 C
>     -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>     -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc --
>     works
>     -- Detecting C compiler ABI info
>     -- Detecting C compiler ABI info - done
>     -- Detecting C compile features
>     -- Detecting C compile features - done
>     -- Cray Programming Environment 2.2.1 CXX
>     -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>     -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>     -- works
>     -- Detecting CXX compiler ABI info
>     -- Detecting CXX compiler ABI info - done
>     -- Detecting CXX compile features
>     -- Detecting CXX compile features - done
>     CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>       Failed to determine if the common superbuild is an old
>     checkout.  The
>       common superbuild may be out of date, but cannot be verified.:
>     warning:
>       unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>': Permission
>       denied
>
>       warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>':
>       Permission denied
>
>       warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>':
>       Permission denied
>
>       warning: unable to access
>     '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
>     <http://pdc.kth.se/home/k/kriezh/.gitconfig>':
>       Permission denied
>
>       error: unknown option `is-ancestor'
>
>       usage: git merge-base [-a|--all] <commit> <commit>...
>
>          or: git merge-base [-a|--all] --octopus <commit>...
>          or: git merge-base --independent <commit>...
>
>
>
>           -a, --all             output all common ancestors
>           --octopus             find ancestors for a single n-way merge
>           --independent         list revs not reachable from others
>     Call Stack (most recent call first):
>       superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>
>
>     -- Check size of void*
>     -- Check size of void* - done
>     -- Found Git: /usr/bin/git (found version "1.7.12.4")
>     -- Determined source version for paraview: 5.4.0
>     CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>       The build tree appears to be inside of the git repository located at
>      
>     /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild.
>       This interferes with the way the superbuild applies patches to
>     projects and
>       is not supported.  Please relocate the build tree to a directory
>     which is
>       not under a git repository.
>     Call Stack (most recent call first):
>       superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>       superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>       superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>
>
>     -- Configuring incomplete, errors occurred!
>     See also
>     "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild/CMakeFiles/CMakeOutput.log".
>
>
>     Kind regards,
>     Mathi
>
>
>
>
>
>     On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com
>     <mailto:cory.quammen at kitware.com>> wrote:
>
>         On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>         <ezhkr601 at student.liu.se <mailto:ezhkr601 at student.liu.se>> wrote:
>         > Hi,
>         >
>         > Can anyone please give me some instructions how to Paraview
>         Superbuid
>         > to install and use them with out using the GUI (using the
>         python script to
>         > render the images on the cluster or super computer).
>         >
>         > I see there are some instructions in here:
>         > https://gitlab.kitware.com/paraview/paraview-superbuild/
>         <https://gitlab.kitware.com/paraview/paraview-superbuild/>
>         >
>         > But I could not find any build instructions.
>
>         Take a look again, that page includes the README.md file contents
>         which includes build instructions.
>
>         To build without the GUI, you should just need to set the options
>         ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>         ENABLE_python to ON.
>
>         Best regards,
>         Cory
>
>         >
>         > Kind regards,
>         > Mathi
>         >
>         > _______________________________________________
>         > Powered by www.kitware.com <http://www.kitware.com>
>         >
>         > Visit other Kitware open-source projects at
>         > http://www.kitware.com/opensource/opensource.html
>         <http://www.kitware.com/opensource/opensource.html>
>         >
>         > Please keep messages on-topic and check the ParaView Wiki at:
>         > http://paraview.org/Wiki/ParaView
>         <http://paraview.org/Wiki/ParaView>
>         >
>         > Search the list archives at:
>         http://markmail.org/search/?q=ParaView
>         <http://markmail.org/search/?q=ParaView>
>         >
>         > Follow this link to subscribe/unsubscribe:
>         > http://public.kitware.com/mailman/listinfo/paraview
>         <http://public.kitware.com/mailman/listinfo/paraview>
>         >
>
>
>
>         --
>         Cory Quammen
>         Staff R&D 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/56f969eb/attachment.html>

From ezhkr601 at student.liu.se  Sun Jul  2 08:17:33 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Sun, 2 Jul 2017 14:17:33 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
Message-ID: <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>

Thanks!

Now it shows this kind of error

/cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
git fetch origin
/cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
git checkout v5.4.0
HEAD is now at 7c510fe... Update to 5.4.0
/cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
git submodule update
/cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
cd ..
/cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
/cfs/klemming/nobackup/k/kriezh> cd build/
/cfs/klemming/nobackup/k/kriezh/build> ccmake
../PARAVIEW_SUPER_BUILD/paraview-superbuild/


 CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
   The build tree appears to be inside of the git repository located at
   /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
   superbuild applies patches to projects and is not supported.  Please
   relocate the build tree to a directory which is not under a git
repository.
 Call Stack (most recent call first):
   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)




On 2 July 2017 at 14:03, Patrick B?gou <Patrick.Begou at legi.grenoble-inp.fr>
wrote:

> Like you, I got this error some months ago when trying to build paraview
> superbuild:
>
> *error: unknown option `is-ancestor'*
>
> It was my git version wich was too old. May be try to compile a more up to
> date version of git in your home and set the path to access it.
>
> I have installed git from https://www.kernel.org/pub/
> software/scm/git/git-2.12.2.tar.xz
>
> Patrick
>
> Ezhilmathi Krishnasamy a ?crit :
>
> Hi,
>
> I have followed these instructions. I am trying to install it where I am
> not a root user.
> Can someone help to fix this issue.
>
>  git clone --recursive https://gitlab.kitware.com/
> paraview/paraview-superbuild.git
>  cd paraview-superbuild
>  git fetch origin # ensure you have the latest state from the main repo
>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>  git submodule update
>
>  cd ..
>  mkdir build
>  cd build
>  ccmake ../paraview-superbuild
>
> Kind regards,
> Mathi
>
>
> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
> wrote:
>
>> Hi Thanks!
>>
>> When I try to install Paraview,  I am getting the following error.
>> Could some one please tell me how to fix this issue.
>> I am trying to install the Paraview on a super computer to use it
>> for remote rendering without using the GUI,  like with mesa support.
>>
>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> git
>> clone --recursive https://gitlab.kitware.com/par
>> aview/paraview-superbuild.git
>> Cloning into 'paraview-superbuild'...
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> remote: Counting objects: 6723, done.
>> remote: Compressing objects: 100% (2459/2459), done.
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>> Resolving deltas: 100% (4451/4451), done.
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> Checking out files: 100% (196/196), done.
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> Submodule 'superbuild' (https://gitlab.kitware.com/pa
>> raview/common-superbuild.git) registered for path 'superbuild'
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> Cloning into 'superbuild'...
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> remote: Counting objects: 6752, done.
>> remote: Compressing objects: 100% (2235/2235), done.
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>> Resolving deltas: 100% (4505/4505), done.
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> Submodule path 'superbuild': checked out '8f357bb5bf35419c210b3f9e0adbc
>> 9df08f565f2'
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> Permission denied
>>
>>
>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> cmake .
>> -- The C compiler identification is Intel 14.0.4.20140805
>> -- The CXX compiler identification is Intel 14.0.4.20140805
>> -- Cray Programming Environment 2.2.1 C
>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- works
>> -- Detecting C compiler ABI info
>> -- Detecting C compiler ABI info - done
>> -- Detecting C compile features
>> -- Detecting C compile features - done
>> -- Cray Programming Environment 2.2.1 CXX
>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC -- works
>> -- Detecting CXX compiler ABI info
>> -- Detecting CXX compiler ABI info - done
>> -- Detecting CXX compile features
>> -- Detecting CXX compile features - done
>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>>   Failed to determine if the common superbuild is an old checkout.  The
>>   common superbuild may be out of date, but cannot be verified.: warning:
>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig': Permission
>>   denied
>>
>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>   Permission denied
>>
>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>   Permission denied
>>
>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>   Permission denied
>>
>>   error: unknown option `is-ancestor'
>>
>>   usage: git merge-base [-a|--all] <commit> <commit>...
>>
>>      or: git merge-base [-a|--all] --octopus <commit>...
>>      or: git merge-base --independent <commit>...
>>
>>
>>
>>       -a, --all             output all common ancestors
>>       --octopus             find ancestors for a single n-way merge
>>       --independent         list revs not reachable from others
>> Call Stack (most recent call first):
>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>>
>>
>> -- Check size of void*
>> -- Check size of void* - done
>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
>> -- Determined source version for paraview: 5.4.0
>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>   The build tree appears to be inside of the git repository located at
>>   /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
>> w-superbuild.
>>   This interferes with the way the superbuild applies patches to projects
>> and
>>   is not supported.  Please relocate the build tree to a directory which
>> is
>>   not under a git repository.
>> Call Stack (most recent call first):
>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>
>>
>> -- Configuring incomplete, errors occurred!
>> See also "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superb
>> uild/CMakeFiles/CMakeOutput.log".
>>
>>
>> Kind regards,
>> Mathi
>>
>>
>>
>>
>>
>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com> wrote:
>>
>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>>> <ezhkr601 at student.liu.se> wrote:
>>> > Hi,
>>> >
>>> > Can anyone please give me some instructions how to Paraview Superbuid
>>> > to install and use them with out using the GUI (using the python
>>> script to
>>> > render the images on the cluster or super computer).
>>> >
>>> > I see there are some instructions in here:
>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>>> >
>>> > But I could not find any build instructions.
>>>
>>> Take a look again, that page includes the README.md file contents
>>> which includes build instructions.
>>>
>>> To build without the GUI, you should just need to set the options
>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>>> ENABLE_python to ON.
>>>
>>> Best regards,
>>> Cory
>>>
>>> >
>>> > Kind regards,
>>> > Mathi
>>> >
>>> > _______________________________________________
>>> > 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&D 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/acd48b0b/attachment.html>

From ezhkr601 at student.liu.se  Sun Jul  2 08:54:05 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Sun, 2 Jul 2017 14:54:05 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
Message-ID: <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>

Hi,

I have almost build it, but getting this error:

 CMake Warning (dev) at
/pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
(add_library):
   ADD_LIBRARY called with SHARED option but the target platform does not
   support dynamic linking.  Building a STATIC library instead.  This may
lead
   to problems.
 Call Stack (most recent call first):
   /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
(find_package)
   superbuild/projects/qt5.system.cmake:1 (find_package)
   superbuild/cmake/SuperbuildMacros.cmake:640 (include)
   superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
 This warning is for project developers.  Use -Wno-dev to suppress it.



On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
wrote:

> Thanks!
>
> Now it shows this kind of error
>
> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
> git fetch origin
> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
> git checkout v5.4.0
> HEAD is now at 7c510fe... Update to 5.4.0
> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
> git submodule update
> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
> cd ..
> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
> /cfs/klemming/nobackup/k/kriezh> cd build/
> /cfs/klemming/nobackup/k/kriezh/build> ccmake ../PARAVIEW_SUPER_BUILD/
> paraview-superbuild/
>
>
>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>    The build tree appears to be inside of the git repository located at
>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
>    superbuild applies patches to projects and is not supported.  Please
>    relocate the build tree to a directory which is not under a git
> repository.
>  Call Stack (most recent call first):
>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>
>
>
>
> On 2 July 2017 at 14:03, Patrick B?gou <Patrick.Begou at legi.grenoble-inp.fr
> > wrote:
>
>> Like you, I got this error some months ago when trying to build paraview
>> superbuild:
>>
>> *error: unknown option `is-ancestor'*
>>
>> It was my git version wich was too old. May be try to compile a more up
>> to date version of git in your home and set the path to access it.
>>
>> I have installed git from https://www.kernel.org/pub/sof
>> tware/scm/git/git-2.12.2.tar.xz
>>
>> Patrick
>>
>> Ezhilmathi Krishnasamy a ?crit :
>>
>> Hi,
>>
>> I have followed these instructions. I am trying to install it where I am
>> not a root user.
>> Can someone help to fix this issue.
>>
>>  git clone --recursive https://gitlab.kitware.com/par
>> aview/paraview-superbuild.git
>>  cd paraview-superbuild
>>  git fetch origin # ensure you have the latest state from the main repo
>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>>  git submodule update
>>
>>  cd ..
>>  mkdir build
>>  cd build
>>  ccmake ../paraview-superbuild
>>
>> Kind regards,
>> Mathi
>>
>>
>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se
>> > wrote:
>>
>>> Hi Thanks!
>>>
>>> When I try to install Paraview,  I am getting the following error.
>>> Could some one please tell me how to fix this issue.
>>> I am trying to install the Paraview on a super computer to use it
>>> for remote rendering without using the GUI,  like with mesa support.
>>>
>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> git
>>> clone --recursive https://gitlab.kitware.com/par
>>> aview/paraview-superbuild.git
>>> Cloning into 'paraview-superbuild'...
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> remote: Counting objects: 6723, done.
>>> remote: Compressing objects: 100% (2459/2459), done.
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>>> Resolving deltas: 100% (4451/4451), done.
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> Checking out files: 100% (196/196), done.
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> Submodule 'superbuild' (https://gitlab.kitware.com/pa
>>> raview/common-superbuild.git) registered for path 'superbuild'
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> Cloning into 'superbuild'...
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> remote: Counting objects: 6752, done.
>>> remote: Compressing objects: 100% (2235/2235), done.
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>>> Resolving deltas: 100% (4505/4505), done.
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> Submodule path 'superbuild': checked out '8f357bb5bf35419c210b3f9e0adbc
>>> 9df08f565f2'
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission denied
>>>
>>>
>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>> cmake .
>>> -- The C compiler identification is Intel 14.0.4.20140805
>>> -- The CXX compiler identification is Intel 14.0.4.20140805
>>> -- Cray Programming Environment 2.2.1 C
>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- works
>>> -- Detecting C compiler ABI info
>>> -- Detecting C compiler ABI info - done
>>> -- Detecting C compile features
>>> -- Detecting C compile features - done
>>> -- Cray Programming Environment 2.2.1 CXX
>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC -- works
>>> -- Detecting CXX compiler ABI info
>>> -- Detecting CXX compiler ABI info - done
>>> -- Detecting CXX compile features
>>> -- Detecting CXX compile features - done
>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>>>   Failed to determine if the common superbuild is an old checkout.  The
>>>   common superbuild may be out of date, but cannot be verified.: warning:
>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>> Permission
>>>   denied
>>>
>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>   Permission denied
>>>
>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>   Permission denied
>>>
>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>   Permission denied
>>>
>>>   error: unknown option `is-ancestor'
>>>
>>>   usage: git merge-base [-a|--all] <commit> <commit>...
>>>
>>>      or: git merge-base [-a|--all] --octopus <commit>...
>>>      or: git merge-base --independent <commit>...
>>>
>>>
>>>
>>>       -a, --all             output all common ancestors
>>>       --octopus             find ancestors for a single n-way merge
>>>       --independent         list revs not reachable from others
>>> Call Stack (most recent call first):
>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>>>
>>>
>>> -- Check size of void*
>>> -- Check size of void* - done
>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
>>> -- Determined source version for paraview: 5.4.0
>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>>   The build tree appears to be inside of the git repository located at
>>>   /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
>>> w-superbuild.
>>>   This interferes with the way the superbuild applies patches to
>>> projects and
>>>   is not supported.  Please relocate the build tree to a directory which
>>> is
>>>   not under a git repository.
>>> Call Stack (most recent call first):
>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>>
>>>
>>> -- Configuring incomplete, errors occurred!
>>> See also "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superb
>>> uild/CMakeFiles/CMakeOutput.log".
>>>
>>>
>>> Kind regards,
>>> Mathi
>>>
>>>
>>>
>>>
>>>
>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com> wrote:
>>>
>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>>>> <ezhkr601 at student.liu.se> wrote:
>>>> > Hi,
>>>> >
>>>> > Can anyone please give me some instructions how to Paraview Superbuid
>>>> > to install and use them with out using the GUI (using the python
>>>> script to
>>>> > render the images on the cluster or super computer).
>>>> >
>>>> > I see there are some instructions in here:
>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>>>> >
>>>> > But I could not find any build instructions.
>>>>
>>>> Take a look again, that page includes the README.md file contents
>>>> which includes build instructions.
>>>>
>>>> To build without the GUI, you should just need to set the options
>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>>>> ENABLE_python to ON.
>>>>
>>>> Best regards,
>>>> Cory
>>>>
>>>> >
>>>> > Kind regards,
>>>> > Mathi
>>>> >
>>>> > _______________________________________________
>>>> > 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&D 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
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/d0066b92/attachment.html>

From ezhkr601 at student.liu.se  Sun Jul  2 11:56:34 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Sun, 2 Jul 2017 17:56:34 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
 <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
Message-ID: <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>

Hi,

I am still having some problem with enabling the
build shared libs. I am trying to install it on a Cray machine.
I have already locally installed cmake and anaconda on their latest version.

I am attaching here the image.
Could any one tell me how to fix this issue

Kind regards,
Mathi

On 2 July 2017 at 14:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
wrote:

> Hi,
>
> I have almost build it, but getting this error:
>
>  CMake Warning (dev) at /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
> (add_library):
>    ADD_LIBRARY called with SHARED option but the target platform does not
>    support dynamic linking.  Building a STATIC library instead.  This may
> lead
>    to problems.
>  Call Stack (most recent call first):
>    /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
> (find_package)
>    superbuild/projects/qt5.system.cmake:1 (find_package)
>    superbuild/cmake/SuperbuildMacros.cmake:640 (include)
>    superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
>  This warning is for project developers.  Use -Wno-dev to suppress it.
>
>
>
> On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
> wrote:
>
>> Thanks!
>>
>> Now it shows this kind of error
>>
>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> git fetch origin
>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> git checkout v5.4.0
>> HEAD is now at 7c510fe... Update to 5.4.0
>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> git submodule update
>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> cd ..
>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
>> /cfs/klemming/nobackup/k/kriezh> cd build/
>> /cfs/klemming/nobackup/k/kriezh/build> ccmake
>> ../PARAVIEW_SUPER_BUILD/paraview-superbuild/
>>
>>
>>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>    The build tree appears to be inside of the git repository located at
>>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
>>    superbuild applies patches to projects and is not supported.  Please
>>    relocate the build tree to a directory which is not under a git
>> repository.
>>  Call Stack (most recent call first):
>>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>
>>
>>
>>
>> On 2 July 2017 at 14:03, Patrick B?gou <Patrick.Begou at legi.grenoble-i
>> np.fr> wrote:
>>
>>> Like you, I got this error some months ago when trying to build paraview
>>> superbuild:
>>>
>>> *error: unknown option `is-ancestor'*
>>>
>>> It was my git version wich was too old. May be try to compile a more up
>>> to date version of git in your home and set the path to access it.
>>>
>>> I have installed git from https://www.kernel.org/pub/sof
>>> tware/scm/git/git-2.12.2.tar.xz
>>>
>>> Patrick
>>>
>>> Ezhilmathi Krishnasamy a ?crit :
>>>
>>> Hi,
>>>
>>> I have followed these instructions. I am trying to install it where I am
>>> not a root user.
>>> Can someone help to fix this issue.
>>>
>>>  git clone --recursive https://gitlab.kitware.com/par
>>> aview/paraview-superbuild.git
>>>  cd paraview-superbuild
>>>  git fetch origin # ensure you have the latest state from the main repo
>>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>>>  git submodule update
>>>
>>>  cd ..
>>>  mkdir build
>>>  cd build
>>>  ccmake ../paraview-superbuild
>>>
>>> Kind regards,
>>> Mathi
>>>
>>>
>>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy <
>>> ezhkr601 at student.liu.se> wrote:
>>>
>>>> Hi Thanks!
>>>>
>>>> When I try to install Paraview,  I am getting the following error.
>>>> Could some one please tell me how to fix this issue.
>>>> I am trying to install the Paraview on a super computer to use it
>>>> for remote rendering without using the GUI,  like with mesa support.
>>>>
>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> git
>>>> clone --recursive https://gitlab.kitware.com/par
>>>> aview/paraview-superbuild.git
>>>> Cloning into 'paraview-superbuild'...
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> remote: Counting objects: 6723, done.
>>>> remote: Compressing objects: 100% (2459/2459), done.
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>>>> Resolving deltas: 100% (4451/4451), done.
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> Checking out files: 100% (196/196), done.
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> Submodule 'superbuild' (https://gitlab.kitware.com/pa
>>>> raview/common-superbuild.git) registered for path 'superbuild'
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> Cloning into 'superbuild'...
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> remote: Counting objects: 6752, done.
>>>> remote: Compressing objects: 100% (2235/2235), done.
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>>>> Resolving deltas: 100% (4505/4505), done.
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> Submodule path 'superbuild': checked out '8f357bb5bf35419c210b3f9e0adbc
>>>> 9df08f565f2'
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission denied
>>>>
>>>>
>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>>> cmake .
>>>> -- The C compiler identification is Intel 14.0.4.20140805
>>>> -- The CXX compiler identification is Intel 14.0.4.20140805
>>>> -- Cray Programming Environment 2.2.1 C
>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- works
>>>> -- Detecting C compiler ABI info
>>>> -- Detecting C compiler ABI info - done
>>>> -- Detecting C compile features
>>>> -- Detecting C compile features - done
>>>> -- Cray Programming Environment 2.2.1 CXX
>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC --
>>>> works
>>>> -- Detecting CXX compiler ABI info
>>>> -- Detecting CXX compiler ABI info - done
>>>> -- Detecting CXX compile features
>>>> -- Detecting CXX compile features - done
>>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>>>>   Failed to determine if the common superbuild is an old checkout.  The
>>>>   common superbuild may be out of date, but cannot be verified.:
>>>> warning:
>>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>> Permission
>>>>   denied
>>>>
>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>   Permission denied
>>>>
>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>   Permission denied
>>>>
>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>   Permission denied
>>>>
>>>>   error: unknown option `is-ancestor'
>>>>
>>>>   usage: git merge-base [-a|--all] <commit> <commit>...
>>>>
>>>>      or: git merge-base [-a|--all] --octopus <commit>...
>>>>      or: git merge-base --independent <commit>...
>>>>
>>>>
>>>>
>>>>       -a, --all             output all common ancestors
>>>>       --octopus             find ancestors for a single n-way merge
>>>>       --independent         list revs not reachable from others
>>>> Call Stack (most recent call first):
>>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>>>>
>>>>
>>>> -- Check size of void*
>>>> -- Check size of void* - done
>>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
>>>> -- Determined source version for paraview: 5.4.0
>>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>>>   The build tree appears to be inside of the git repository located at
>>>>   /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
>>>> w-superbuild.
>>>>   This interferes with the way the superbuild applies patches to
>>>> projects and
>>>>   is not supported.  Please relocate the build tree to a directory
>>>> which is
>>>>   not under a git repository.
>>>> Call Stack (most recent call first):
>>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>>>
>>>>
>>>> -- Configuring incomplete, errors occurred!
>>>> See also "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superb
>>>> uild/CMakeFiles/CMakeOutput.log".
>>>>
>>>>
>>>> Kind regards,
>>>> Mathi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com>
>>>> wrote:
>>>>
>>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>>>>> <ezhkr601 at student.liu.se> wrote:
>>>>> > Hi,
>>>>> >
>>>>> > Can anyone please give me some instructions how to Paraview Superbuid
>>>>> > to install and use them with out using the GUI (using the python
>>>>> script to
>>>>> > render the images on the cluster or super computer).
>>>>> >
>>>>> > I see there are some instructions in here:
>>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>>>>> >
>>>>> > But I could not find any build instructions.
>>>>>
>>>>> Take a look again, that page includes the README.md file contents
>>>>> which includes build instructions.
>>>>>
>>>>> To build without the GUI, you should just need to set the options
>>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>>>>> ENABLE_python to ON.
>>>>>
>>>>> Best regards,
>>>>> Cory
>>>>>
>>>>> >
>>>>> > Kind regards,
>>>>> > Mathi
>>>>> >
>>>>> > _______________________________________________
>>>>> > 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&D 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
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/67e39b6b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BUILD_SHARED_LIBS.png
Type: image/png
Size: 186294 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/67e39b6b/attachment-0001.png>

From quang.t.ha.20 at gmail.com  Sun Jul  2 14:36:25 2017
From: quang.t.ha.20 at gmail.com (Quang Ha)
Date: Sun, 2 Jul 2017 14:36:25 -0400
Subject: [Paraview] Trouble compilng Paraview
Message-ID: <CAGfE9+M-yrYaTHFchzfrSPmYdJS3UdH=O0R6Z3UGiO5FAe8Lcg@mail.gmail.com>

Hi all,

I have managed to compile Paraview with ffmpeg and Qt5. However, when I
tried running the program the following error appears:

ibprotobuf FATAL /home/qth20/Utils/paraview/ThirdParty/protobuf/
vtkprotobuf/src/google/protobuf/stubs/common.cc:62] This program requires
version 2.6.0 of the Protocol Buffer runtime library, but the installed
version is 2.3.0.  Please update your library.  If you compiled the program
yourself, make sure that your headers are from the same version of Protocol
Buffers as your link-time library.  (Version verification failed in
"/build/mir-ui6vjS/mir-0.26.3+16.04.20170605/obj-x86_64-
linux-gnu/src/protobuf/mir_protobuf.pb.cc".)
[1]    29939 abort (core dumped)  paraview

Since I have libprotoc-dev version 2.6.1 on Ubuntu 16.04.2 LTS, I don't
know where the installed version of 2.3.0 comes from. Is this something I
need to configure with Paraview?

Thanks,
Quang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/d9dac697/attachment.html>

From yux1991 at gmail.com  Sun Jul  2 17:41:18 2017
From: yux1991 at gmail.com (Yu Xiang)
Date: Sun, 2 Jul 2017 17:41:18 -0400
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
 <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
Message-ID: <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>

Thanks very much for your reply. My computer has two graphic cards: Intel HD Graphics 4000 and NVIDA NVS 5400M, respectively. I switch to 5.3 and no longer have those two problems. 

 

Yu

 

From: David E DeMarle [mailto:dave.demarle at kitware.com] 
Sent: Sunday, July 2, 2017 7:10 AM
To: Yu Xiang <yux1991 at gmail.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] ParaView unable to adjust object opacity

 

These are most likely caused by a known bug in 5.4.0 with some graphics hardware that we are trying to fix in 5.4.1. Can you let us know what your gpu is? Also try 5.3 and let us know if both problems work there.

 

Thanks

 

On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com <mailto:yux1991 at gmail.com> > wrote:

Hi,

 

I downloaded the ParaView Binary Installers (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe) from https://www.paraview.org/download/ and installed it on my Thinkpad T430 which is running Windows 10. I was using ParaView for the first time and found two things puzzling:

1.       When I open ParaView, the default window looks like the following. There is a small black square on the bottom left corner in RenderView1 (circled in red). I couldn?t figure out why it showed up there.



2.       Then I opened the first Example Visualization and selected Clip2 under can.ex2. When I tried to adjust the Opacity under Styling in the Properties tab, any value other than 1 will make the object in the RenderView1 window disappear like the following:



I tried other examples, and similar things happened. I couldn?t figure out why.

 

Does anybody know what might be going on and how I can fix it?

 

Thanks,

Yu


_______________________________________________
Powered by www.kitware.com <http://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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/7b213039/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/7b213039/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170702/7b213039/attachment-0003.png>

From yves.rogez at univ-grenoble-alpes.fr  Mon Jul  3 03:28:25 2017
From: yves.rogez at univ-grenoble-alpes.fr (Yves Rogez)
Date: Mon, 3 Jul 2017 09:28:25 +0200
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
 <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
 <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>
Message-ID: <16d4989e-b612-0e6f-356c-a48b85489b14@univ-grenoble-alpes.fr>

Hi all,

I've noticed that the black box problem can come from the FXAA enabled 
in the render settings (I have the same problem with my computer & 5.4) 
but it does not explain the problem with opacity. (my graphics card is a 
GeForce GTX770M)

Yves


Le 02/07/2017 ? 23:41, Yu Xiang a ?crit :
>
> Thanks very much for your reply. My computer has two graphic cards: 
> Intel HD Graphics 4000 and NVIDA NVS 5400M, respectively. I switch to 
> 5.3 and no longer have those two problems.
>
> Yu
>
> *From:*David E DeMarle [mailto:dave.demarle at kitware.com]
> *Sent:* Sunday, July 2, 2017 7:10 AM
> *To:* Yu Xiang <yux1991 at gmail.com>
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] ParaView unable to adjust object opacity
>
> These are most likely caused by a known bug in 5.4.0 with some 
> graphics hardware that we are trying to fix in 5.4.1. Can you let us 
> know what your gpu is? Also try 5.3 and let us know if both problems 
> work there.
>
> Thanks
>
> On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com 
> <mailto:yux1991 at gmail.com>> wrote:
>
>     Hi,
>
>     I downloaded the ParaView Binary Installers
>     (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe) from
>     https://www.paraview.org/download/ and installed it on my Thinkpad
>     T430 which is running Windows 10. I was using ParaView for the
>     first time and found two things puzzling:
>
>     1.When I open ParaView, the default window looks like the
>     following. There is a small black square on the bottom left corner
>     in RenderView1 (circled in red). I couldn?t figure out why it
>     showed up there.
>
>     imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.2&filename=image001.png
>
>     2.Then I opened the first Example Visualization and selected Clip2
>     under can.ex2. When I tried to adjust the Opacity under Styling in
>     the Properties tab, any value other than 1 will make the object in
>     the RenderView1 window disappear like the following:
>
>     imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.3&filename=image002.png
>
>     I tried other examples, and similar things happened. I couldn?t
>     figure out why.
>
>     Does anybody know what might be going on and how I can fix it?
>
>     Thanks,
>
>     Yu
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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

-- 
Yves Rogez

*IPAG*
/Institut de Plan?tologie et d'Astrophysique de Grenoble /
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE

tel : +33 (0)4 76 63 52 80
lab : +33 (0)4 76 63 57 60
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/5770b2cd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/5770b2cd/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/5770b2cd/attachment-0003.png>

From lukas.kresta at gmail.com  Mon Jul  3 05:39:27 2017
From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=)
Date: Mon, 3 Jul 2017 11:39:27 +0200
Subject: [Paraview] Saving png images in Catalyst-live
Message-ID: <CAN4WRTzSt7FVxSrQiYYKb-QJaAoioZ4uf5W978nRpOO8XYGYKA@mail.gmail.com>

Hi,

i would like to save image with my ParaView Catalyst. But I use live
visualization(no render view) and I send to Catalyst unstructured grid. Can
I somehow generate png image?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/9480d416/attachment.html>

From cory.quammen at kitware.com  Mon Jul  3 09:37:31 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 3 Jul 2017 08:37:31 -0500
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <16d4989e-b612-0e6f-356c-a48b85489b14@univ-grenoble-alpes.fr>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
 <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
 <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>
 <16d4989e-b612-0e6f-356c-a48b85489b14@univ-grenoble-alpes.fr>
Message-ID: <CAB5Fpx5As4r6n-h-COiRdH6XYBE3fc-NfS=Ko7Vz9psdTQ6FFw@mail.gmail.com>

Yu and Yves,

Clearly we need to fix the issue with Intel graphics, but are you sure your
NVIDIA card is being used for rendering? You can check in ParaView by going
to Help -> About and see which OpenGL Vendor is listed. It should say
"NVIDIA Corporation."

If it is not being used for ParaView, you can go to the NVIDIA Control
Panel and under Manage 3D Settings, set your "Preferred graphics processor"
to "High-performance NVIDIA processor".

HTH,
Cory

On Mon, Jul 3, 2017 at 2:28 AM, Yves Rogez <
yves.rogez at univ-grenoble-alpes.fr> wrote:

> Hi all,
>
> I've noticed that the black box problem can come from the FXAA enabled in
> the render settings (I have the same problem with my computer & 5.4) but it
> does not explain the problem with opacity. (my graphics card is a GeForce
> GTX770M)
>
> Yves
>
> Le 02/07/2017 ? 23:41, Yu Xiang a ?crit :
>
> Thanks very much for your reply. My computer has two graphic cards: Intel
> HD Graphics 4000 and NVIDA NVS 5400M, respectively. I switch to 5.3 and no
> longer have those two problems.
>
>
>
> Yu
>
>
>
> *From:* David E DeMarle [mailto:dave.demarle at kitware.com
> <dave.demarle at kitware.com>]
> *Sent:* Sunday, July 2, 2017 7:10 AM
> *To:* Yu Xiang <yux1991 at gmail.com> <yux1991 at gmail.com>
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] ParaView unable to adjust object opacity
>
>
>
> These are most likely caused by a known bug in 5.4.0 with some graphics
> hardware that we are trying to fix in 5.4.1. Can you let us know what your
> gpu is? Also try 5.3 and let us know if both problems work there.
>
>
>
> Thanks
>
>
>
> On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com> wrote:
>
> Hi,
>
>
>
> I downloaded the ParaView Binary Installers (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe)
> from https://www.paraview.org/download/ and installed it on my Thinkpad
> T430 which is running Windows 10. I was using ParaView for the first time
> and found two things puzzling:
>
> 1.       When I open ParaView, the default window looks like the
> following. There is a small black square on the bottom left corner in
> RenderView1 (circled in red). I couldn?t figure out why it showed up there.
>
> [image:
> imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.2&filename=image001.png]
>
> 2.       Then I opened the first Example Visualization and selected Clip2
> under can.ex2. When I tried to adjust the Opacity under Styling in the
> Properties tab, any value other than 1 will make the object in the
> RenderView1 window disappear like the following:
>
> [image:
> imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.3&filename=image002.png]
>
> I tried other examples, and similar things happened. I couldn?t figure out
> why.
>
>
>
> Does anybody know what might be going on and how I can fix it?
>
>
>
> Thanks,
>
> Yu
>
>
> _______________________________________________
> 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
>
>
> --
> Yves Rogez
>
> *IPAG*
> *Institut de Plan?tologie et d'Astrophysique de Grenoble *
> Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE
>
> tel : +33 (0)4 76 63 52 80 <+33%204%2076%2063%2052%2080>
> lab : +33 (0)4 76 63 57 60 <+33%204%2076%2063%2057%2060>
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/3c236e3a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/3c236e3a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/3c236e3a/attachment-0003.png>

From cory.quammen at kitware.com  Mon Jul  3 10:03:16 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 3 Jul 2017 09:03:16 -0500
Subject: [Paraview] Coloring isocontour by the coordinates outputted
 from a Transform filter and some other questions
In-Reply-To: <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
References: <d5d624cc-e171-f153-b1b6-47ee0a9b8068@shuhaowu.com>
 <CAB5Fpx4aKwctsmYnb+yhFyxtRok_c1CGt1shrTbTRF4iOrE+iw@mail.gmail.com>
 <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
Message-ID: <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>

On Tue, Jun 20, 2017 at 9:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:

> Hello Cory,
>
> I've been playing around a little bit more and followed your suggestion
> with using the calculator to "expose" the transformed coordinates. However,
> my understanding is that this Calculator will duplicate the memory usage
> for that coordinate and be an additional step in the filtering process,
> slowing it down.


Yes, that's true unfortunately. By the way, if you need X, Y, and Z, you
can use one Calculator filter to produce all three with the expression

iHat*coordsX + jHat*coordsY + kHat*coordsZ

This produces a 3-component array - you can then color your isosurface by
just one of the components or by the magnitude.

I have to use the Calculator filter to expose all 3 coordinates before
> using a threshold to filter for only a subset region that I want to plt,
> which results in a filtering chain as follows:
>
> ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) ->
> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ (Threshold).


>
This is 6 filters, which is very slow with my data set (>29M nodes in a
> rectlinear grid). Is there a way to speed this up?
>
>
You could instead use a Clip filter with Clip Type set to Box. You have to
do a little math to convert from your threshold values to the box Scale and
Position properties, but it shouldn't be too bad, and will make your
pipeline simpler and faster.

Cory


> Thanks,
> Shuhao
>
>
> On 2017-06-07 03:29 PM, Cory Quammen wrote:
>
>> Shuhao,
>>
>> Welcome to ParaView!
>>
>> On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>
>>> Hello all,
>>>
>>> Is there a way to color an isocontour via the coordinates outputted from
>>> a
>>> Transform filter? I'm using the Transform filter to "normalize" my
>>> coordinate systems and I want to display the isocontour colored by the
>>> normalized Y coordinates. Do I have to create yet another Calculator
>>> filter
>>> to recalculate the normalized Y value that is already calculated by the
>>> Transform filter?
>>>
>>
>> There is currently no direct way to color surfaces by coordinate
>> value. You can, however, add a Calculator after the Transform filter
>> and simply set the expression to coordsY - no recomputation of the
>> normalization is needed. This will copy your normalized Y coordinate
>> values to a new array named "Result", and you can then color the
>> isosurface by "Result". "Result" is just the default name - you can
>> change it however you wish.
>>
>> Also: is there a way to turn off one axis on the axis grid (so turn off
>>> the
>>> Y axis display and leave only X and Z)?
>>>
>>
>> Click the Edit button next to the Axes Grid option. Click the gear
>> icon in the top right of the dialog that appears. Under Face
>> Properties, click on the "Faces to Render" combo box. Turn off the
>> sides you do not wish to see by selecting them in the combo box.
>>
>> What about changing the interval on
>>> the axis itself (instead of incrementing by 100 as it chooses, increment
>>> by
>>> 250).
>>>
>>
>> In the same dialog described above, check the "X Axis Use Custom
>> Labels", and you can specify exactly the labels you want. There is no
>> property to directly change the increment.
>>
>> Best,
>> Cory
>>
>> I'm pretty new to Paraview (coming from Tecplot). Please bear with me as I
>>> likely will have more question.
>>>
>>> Thanks,
>>> Shuhao
>>> _______________________________________________
>>> 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&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/e6ec55d6/attachment.html>

From yves.rogez at univ-grenoble-alpes.fr  Mon Jul  3 10:46:24 2017
From: yves.rogez at univ-grenoble-alpes.fr (Yves Rogez)
Date: Mon, 3 Jul 2017 16:46:24 +0200
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <CAB5Fpx5As4r6n-h-COiRdH6XYBE3fc-NfS=Ko7Vz9psdTQ6FFw@mail.gmail.com>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
 <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
 <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>
 <16d4989e-b612-0e6f-356c-a48b85489b14@univ-grenoble-alpes.fr>
 <CAB5Fpx5As4r6n-h-COiRdH6XYBE3fc-NfS=Ko7Vz9psdTQ6FFw@mail.gmail.com>
Message-ID: <e2328463-93e1-580d-15ee-5a5c74847096@univ-grenoble-alpes.fr>

Hi Cory,

thanks for your answer, indeed that solved the problem. That's weird 
that the graphics processor was the wrong one. As far as I remembered 
the graphics processor was the good one before. It solved the FXAA 
(black box) and opacity issues.

Cheers,

Yves


Le 03/07/2017 ? 15:37, Cory Quammen a ?crit :
> Yu and Yves,
>
> Clearly we need to fix the issue with Intel graphics, but are you sure 
> your NVIDIA card is being used for rendering? You can check in 
> ParaView by going to Help -> About and see which OpenGL Vendor is 
> listed. It should say "NVIDIA Corporation."
>
> If it is not being used for ParaView, you can go to the NVIDIA Control 
> Panel and under Manage 3D Settings, set your "Preferred graphics 
> processor" to "High-performance NVIDIA processor".
>
> HTH,
> Cory
>
> On Mon, Jul 3, 2017 at 2:28 AM, Yves Rogez 
> <yves.rogez at univ-grenoble-alpes.fr 
> <mailto:yves.rogez at univ-grenoble-alpes.fr>> wrote:
>
>     Hi all,
>
>     I've noticed that the black box problem can come from the FXAA
>     enabled in the render settings (I have the same problem with my
>     computer & 5.4) but it does not explain the problem with opacity.
>     (my graphics card is a GeForce GTX770M)
>
>     Yves
>
>
>     Le 02/07/2017 ? 23:41, Yu Xiang a ?crit :
>>
>>     Thanks very much for your reply. My computer has two graphic
>>     cards: Intel HD Graphics 4000 and NVIDA NVS 5400M, respectively.
>>     I switch to 5.3 and no longer have those two problems.
>>
>>     Yu
>>
>>     *From:*David E DeMarle [mailto:dave.demarle at kitware.com
>>     <mailto:dave.demarle at kitware.com>]
>>     *Sent:* Sunday, July 2, 2017 7:10 AM
>>     *To:* Yu Xiang <yux1991 at gmail.com> <mailto:yux1991 at gmail.com>
>>     *Cc:* paraview at paraview.org <mailto:paraview at paraview.org>
>>     *Subject:* Re: [Paraview] ParaView unable to adjust object opacity
>>
>>     These are most likely caused by a known bug in 5.4.0 with some
>>     graphics hardware that we are trying to fix in 5.4.1. Can you let
>>     us know what your gpu is? Also try 5.3 and let us know if both
>>     problems work there.
>>
>>     Thanks
>>
>>     On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com
>>     <mailto:yux1991 at gmail.com>> wrote:
>>
>>         Hi,
>>
>>         I downloaded the ParaView Binary Installers
>>         (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe) from
>>         https://www.paraview.org/download/
>>         <https://www.paraview.org/download/> and installed it on my
>>         Thinkpad T430 which is running Windows 10. I was using
>>         ParaView for the first time and found two things puzzling:
>>
>>         1.When I open ParaView, the default window looks like the
>>         following. There is a small black square on the bottom left
>>         corner in RenderView1 (circled in red). I couldn?t figure out
>>         why it showed up there.
>>
>>         imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.2&filename=image001.png
>>
>>         2.Then I opened the first Example Visualization and selected
>>         Clip2 under can.ex2. When I tried to adjust the Opacity under
>>         Styling in the Properties tab, any value other than 1 will
>>         make the object in the RenderView1 window disappear like the
>>         following:
>>
>>         imap://rogezy at hermes.obs.ujf-grenoble.fr:993/fetch%3EUID%3E/aaLists/03_Paraview%3E831190?header=quotebody&part=1.1.3&filename=image002.png
>>
>>         I tried other examples, and similar things happened. I
>>         couldn?t figure out why.
>>
>>         Does anybody know what might be going on and how I can fix it?
>>
>>         Thanks,
>>
>>         Yu
>>
>>
>>         _______________________________________________
>>         Powered by www.kitware.com <http://www.kitware.com>
>>
>>         Visit other Kitware open-source projects at
>>         http://www.kitware.com/opensource/opensource.html
>>         <http://www.kitware.com/opensource/opensource.html>
>>
>>         Please keep messages on-topic and check the ParaView Wiki at:
>>         http://paraview.org/Wiki/ParaView
>>         <http://paraview.org/Wiki/ParaView>
>>
>>         Search the list archives at:
>>         http://markmail.org/search/?q=ParaView
>>         <http://markmail.org/search/?q=ParaView>
>>
>>         Follow this link to subscribe/unsubscribe:
>>         http://public.kitware.com/mailman/listinfo/paraview
>>         <http://public.kitware.com/mailman/listinfo/paraview>
>>
>>
>>
>>     _______________________________________________
>>     Powered bywww.kitware.com <http://www.kitware.com>
>>
>>     Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html
>>     <http://www.kitware.com/opensource/opensource.html>
>>
>>     Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>
>>     Search the list archives at:http://markmail.org/search/?q=ParaView
>>     <http://markmail.org/search/?q=ParaView>
>>
>>     Follow this link to subscribe/unsubscribe:
>>     http://public.kitware.com/mailman/listinfo/paraview
>>     <http://public.kitware.com/mailman/listinfo/paraview>
>     -- Yves Rogez *IPAG* /Institut de Plan?tologie et d'Astrophysique
>     de Grenoble / Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE
>     tel : +33 (0)4 76 63 52 80 <tel:+33%204%2076%2063%2052%2080> lab :
>     +33 (0)4 76 63 57 60 <tel:+33%204%2076%2063%2057%2060>
>     _______________________________________________ Powered by
>     www.kitware.com <http://www.kitware.com> Visit other Kitware
>     open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html> Please keep
>     messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>     <http://paraview.org/Wiki/ParaView> Search the list archives at:
>     http://markmail.org/search/?q=ParaView
>     <http://markmail.org/search/?q=ParaView> Follow this link to
>     subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>     <http://public.kitware.com/mailman/listinfo/paraview> 
>
> -- 
> Cory Quammen Staff R&D Engineer Kitware, Inc.
-- Yves Rogez *IPAG* /Institut de Plan?tologie et d'Astrophysique de 
Grenoble / Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE tel : 
+33 (0)4 76 63 52 80 lab : +33 (0)4 76 63 57 60
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/e195413c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/e195413c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/e195413c/attachment-0003.png>

From kriolog at gmail.com  Mon Jul  3 11:36:25 2017
From: kriolog at gmail.com (Maxim Torgonskiy)
Date: Mon, 3 Jul 2017 11:36:25 -0400
Subject: [Paraview] pvbatch rendering issue
Message-ID: <CAHXhkntoT2SUYbWQbpt8g3rHWHues0afG_VV=RTtLEJMCBZgDw@mail.gmail.com>

Hello,

I need to load a heavy pvsm state with pvbatch and render multiple
output views for my regression tests. The python script which I use is
quite straightforward:

import paraview.simple as ParaViewSimple
import os
...
ParaViewSimple.servermanager.LoadState(pvsm_file)
for view in ParaViewSimple.GetRenderViews():
  pxm = ParaViewSimple.servermanager.ProxyManager()
  view_name = pxm.GetProxyName("views", view)
  ParaViewSimple.SaveScreenshot(os.path.join(baseline_path, "%s.png" %
view_name), view)

If I launch it with pvbatch it returns multiple warnings "Warning: In
/home/kriolog/projects/caboma/SpecifX/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx,
line 1080
vtkXOpenGLRenderWindow (0x556adac32720): warning window did not resize in
the allotted time" and generates wrong images (10 identical images of one
of the views and one different instead 11 different images). However, when
I launch the same script from ParaView it generates correct images. When I
launch pvbatch  in my docker container (osmesa, no Qt) it silently
generates the same wrong images. Could you please me give me some advice
about how to debug it?

The version of VTK which I use is 7.1.1 (slightly modified).

Thanks,
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/521cbdb2/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul  3 11:38:30 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 3 Jul 2017 11:38:30 -0400
Subject: [Paraview] pvbatch rendering issue
In-Reply-To: <CAHXhkntoT2SUYbWQbpt8g3rHWHues0afG_VV=RTtLEJMCBZgDw@mail.gmail.com>
References: <CAHXhkntoT2SUYbWQbpt8g3rHWHues0afG_VV=RTtLEJMCBZgDw@mail.gmail.com>
Message-ID: <CADHSJjAUWeAtBkwxa44Wjexty_oF3QTCJhpSTNuFgOQp+yN-rg@mail.gmail.com>

Maxim,

Can you try passing `--use-offscreen-rendering` flag to pvbatch. Does
that help? I am not sure how you're getting incorrect sizes with
osmesa too, but let's focus of the X error to begin with.

Utkarsh

On Mon, Jul 3, 2017 at 11:36 AM, Maxim Torgonskiy <kriolog at gmail.com> wrote:
> Hello,
>
> I need to load a heavy pvsm state with pvbatch and render multiple output
> views for my regression tests. The python script which I use is quite
> straightforward:
>
> import paraview.simple as ParaViewSimple
> import os
> ...
> ParaViewSimple.servermanager.LoadState(pvsm_file)
> for view in ParaViewSimple.GetRenderViews():
>   pxm = ParaViewSimple.servermanager.ProxyManager()
>   view_name = pxm.GetProxyName("views", view)
>   ParaViewSimple.SaveScreenshot(os.path.join(baseline_path, "%s.png" %
> view_name), view)
>
> If I launch it with pvbatch it returns multiple warnings "Warning: In
> /home/kriolog/projects/caboma/SpecifX/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx,
> line 1080
> vtkXOpenGLRenderWindow (0x556adac32720): warning window did not resize in
> the allotted time" and generates wrong images (10 identical images of one of
> the views and one different instead 11 different images). However, when I
> launch the same script from ParaView it generates correct images. When I
> launch pvbatch  in my docker container (osmesa, no Qt) it silently generates
> the same wrong images. Could you please me give me some advice about how to
> debug it?
>
> The version of VTK which I use is 7.1.1 (slightly modified).
>
> Thanks,
> Maxim
>
> _______________________________________________
> 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
>

From yux1991 at gmail.com  Mon Jul  3 12:00:48 2017
From: yux1991 at gmail.com (Yu Xiang)
Date: Mon, 3 Jul 2017 12:00:48 -0400
Subject: [Paraview] ParaView unable to adjust object opacity
In-Reply-To: <CAB5Fpx5As4r6n-h-COiRdH6XYBE3fc-NfS=Ko7Vz9psdTQ6FFw@mail.gmail.com>
References: <006201d2f214$dfee9bb0$9fcbd310$@gmail.com>
 <CANjZAi8zMSS5Oet5J55Qvq8T9gieO4MXK0TKtGg7fevMbdhb_A@mail.gmail.com>
 <005901d2f37b$f16f0ec0$d44d2c40$@gmail.com>
 <16d4989e-b612-0e6f-356c-a48b85489b14@univ-grenoble-alpes.fr>
 <CAB5Fpx5As4r6n-h-COiRdH6XYBE3fc-NfS=Ko7Vz9psdTQ6FFw@mail.gmail.com>
Message-ID: <011001d2f415$8a3782b0$9ea68810$@gmail.com>

Hi Cory,

 

My NVIDIA card was indeed not being used for rendering. Switching to NVIDIA perfectly solved my problems on ParaView v5.4. Thanks very much for your answer!

 

Yu

 

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cory Quammen
Sent: Monday, July 3, 2017 9:38 AM
To: Yves Rogez <yves.rogez at univ-grenoble-alpes.fr>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] ParaView unable to adjust object opacity

 

Yu and Yves,

 

Clearly we need to fix the issue with Intel graphics, but are you sure your NVIDIA card is being used for rendering? You can check in ParaView by going to Help -> About and see which OpenGL Vendor is listed. It should say "NVIDIA Corporation."

 

If it is not being used for ParaView, you can go to the NVIDIA Control Panel and under Manage 3D Settings, set your "Preferred graphics processor" to "High-performance NVIDIA processor".

 

HTH,

Cory

 

On Mon, Jul 3, 2017 at 2:28 AM, Yves Rogez <yves.rogez at univ-grenoble-alpes.fr <mailto:yves.rogez at univ-grenoble-alpes.fr> > wrote:

Hi all,

I've noticed that the black box problem can come from the FXAA enabled in the render settings (I have the same problem with my computer & 5.4) but it does not explain the problem with opacity. (my graphics card is a GeForce GTX770M)

Yves

 

Le 02/07/2017 ? 23:41, Yu Xiang a ?crit :

Thanks very much for your reply. My computer has two graphic cards: Intel HD Graphics 4000 and NVIDA NVS 5400M, respectively. I switch to 5.3 and no longer have those two problems. 

 

Yu

 

From: David E DeMarle [ <mailto:dave.demarle at kitware.com> mailto:dave.demarle at kitware.com] 
Sent: Sunday, July 2, 2017 7:10 AM
To: Yu Xiang  <mailto:yux1991 at gmail.com> <yux1991 at gmail.com>
Cc:  <mailto:paraview at paraview.org> paraview at paraview.org
Subject: Re: [Paraview] ParaView unable to adjust object opacity

 

These are most likely caused by a known bug in 5.4.0 with some graphics hardware that we are trying to fix in 5.4.1. Can you let us know what your gpu is? Also try 5.3 and let us know if both problems work there.

 

Thanks

 

On Jun 30, 2017 10:51 PM, "Yu Xiang" <yux1991 at gmail.com <mailto:yux1991 at gmail.com> > wrote:

Hi,

 

I downloaded the ParaView Binary Installers (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe) from https://www.paraview.org/download/ and installed it on my Thinkpad T430 which is running Windows 10. I was using ParaView for the first time and found two things puzzling:

1.       When I open ParaView, the default window looks like the following. There is a small black square on the bottom left corner in RenderView1 (circled in red). I couldn?t figure out why it showed up there.



2.       Then I opened the first Example Visualization and selected Clip2 under can.ex2. When I tried to adjust the Opacity under Styling in the Properties tab, any value other than 1 will make the object in the RenderView1 window disappear like the following:



I tried other examples, and similar things happened. I couldn?t figure out why.

 

Does anybody know what might be going on and how I can fix it?

 

Thanks,

Yu


_______________________________________________
Powered by www.kitware.com <http://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 <http://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

 

-- 
Yves Rogez

IPAG
Institut de Plan?tologie et d'Astrophysique de Grenoble 
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE

tel : +33 (0)4 76 63 52 80 <tel:+33%204%2076%2063%2052%2080> 
lab : +33 (0)4 76 63 57 60 <tel:+33%204%2076%2063%2057%2060> 


_______________________________________________
Powered by www.kitware.com <http://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&D Engineer
Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/b95cbb4f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 120842 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/b95cbb4f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 206013 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/b95cbb4f/attachment-0003.png>

From kriolog at gmail.com  Mon Jul  3 13:55:03 2017
From: kriolog at gmail.com (Maxim Torgonskiy)
Date: Mon, 3 Jul 2017 13:55:03 -0400
Subject: [Paraview] Fwd:  pvbatch rendering issue
In-Reply-To: <CAHXhknvGrzd=C32Fm-fk=nE5wdzBAVYVt8pWO_y=V_2+dFDfzA@mail.gmail.com>
References: <CAHXhkntoT2SUYbWQbpt8g3rHWHues0afG_VV=RTtLEJMCBZgDw@mail.gmail.com>
 <CADHSJjAUWeAtBkwxa44Wjexty_oF3QTCJhpSTNuFgOQp+yN-rg@mail.gmail.com>
 <CAHXhkntVb9G=yBydS3o42xGSQBmPjmVWMVDKAa-Fm_drAQM8CQ@mail.gmail.com>
 <CADHSJjCQQ+Pazt-fz=zy5kyN5n75fW8erygLHCK=P_cjdsCSGw@mail.gmail.com>
 <CAHXhknvGrzd=C32Fm-fk=nE5wdzBAVYVt8pWO_y=V_2+dFDfzA@mail.gmail.com>
Message-ID: <CAHXhknvkDO_7eDvudYRw5j=24W3OrzUpzqJGOv6NYJ3t3S0KmQ@mail.gmail.com>

---------- Forwarded message ----------
From: Maxim Torgonskiy <kriolog at gmail.com>
Date: 2017-07-03 13:54 GMT-04:00
Subject: Re: [Paraview] pvbatch rendering issue
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>


Ok, I've found the source of the problem. The state has links between views
'<CameraLink name=' which somehow cause rendering of everything when I
touch a view and the view image I want to write is almost never the right
one. I removed these links and now everything works fine. Thank you for
your help!

Ps. The python script is that I've posted above (just with two hardcoded
pathes 'pvsm_file' and 'baseline_path'). The pvsm state won't be
reproducible with paraview since it uses many custom plugins.

2017-07-03 12:44 GMT-04:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Mind sending me the script? Not sure what's going on.
>
> On Mon, Jul 3, 2017 at 11:49 AM, Maxim Torgonskiy <kriolog at gmail.com>
> wrote:
> > Hello Utkarsh,
> >
> > Thank you for your quick reply. Yes, I tried with and without
> > `--use-offscreen-rendering`, the result is the same.
> >
> > 2017-07-03 11:38 GMT-04:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> >:
> >>
> >> Maxim,
> >>
> >> Can you try passing `--use-offscreen-rendering` flag to pvbatch. Does
> >> that help? I am not sure how you're getting incorrect sizes with
> >> osmesa too, but let's focus of the X error to begin with.
> >>
> >> Utkarsh
> >>
> >> On Mon, Jul 3, 2017 at 11:36 AM, Maxim Torgonskiy <kriolog at gmail.com>
> >> wrote:
> >> > Hello,
> >> >
> >> > I need to load a heavy pvsm state with pvbatch and render multiple
> >> > output
> >> > views for my regression tests. The python script which I use is quite
> >> > straightforward:
> >> >
> >> > import paraview.simple as ParaViewSimple
> >> > import os
> >> > ...
> >> > ParaViewSimple.servermanager.LoadState(pvsm_file)
> >> > for view in ParaViewSimple.GetRenderViews():
> >> >   pxm = ParaViewSimple.servermanager.ProxyManager()
> >> >   view_name = pxm.GetProxyName("views", view)
> >> >   ParaViewSimple.SaveScreenshot(os.path.join(baseline_path, "%s.png"
> %
> >> > view_name), view)
> >> >
> >> > If I launch it with pvbatch it returns multiple warnings "Warning: In
> >> >
> >> > /home/kriolog/projects/caboma/SpecifX/VTK/Rendering/OpenGL2/
> vtkXOpenGLRenderWindow.cxx,
> >> > line 1080
> >> > vtkXOpenGLRenderWindow (0x556adac32720): warning window did not resize
> >> > in
> >> > the allotted time" and generates wrong images (10 identical images of
> >> > one of
> >> > the views and one different instead 11 different images). However,
> when
> >> > I
> >> > launch the same script from ParaView it generates correct images.
> When I
> >> > launch pvbatch  in my docker container (osmesa, no Qt) it silently
> >> > generates
> >> > the same wrong images. Could you please me give me some advice about
> how
> >> > to
> >> > debug it?
> >> >
> >> > The version of VTK which I use is 7.1.1 (slightly modified).
> >> >
> >> > Thanks,
> >> > Maxim
> >> >
> >> > _______________________________________________
> >> > 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
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170703/981e44fa/attachment.html>

From jgonzalez49 at ucmerced.edu  Mon Jul  3 21:01:47 2017
From: jgonzalez49 at ucmerced.edu (Jeremias Gonzalez)
Date: Mon, 3 Jul 2017 18:01:47 -0700
Subject: [Paraview] Using Value of Variable At Point in Calculator Filter
Message-ID: <8cb746b3-e456-a1eb-1194-038f51269a48@ucmerced.edu>

Hi, I've been trying to figure out, in Paraview, how to use the value of 
a variable at a point in the calculator filter over a geometry. So, for 
example, I have 3 vtk files of a cube geometry with a scalar and vector 
field (x,y,z components) as data sets. I create a gradient filter for 
each one of the vector components, then use the append attributes filter 
to combine the gradients into one object, then use the calculator filter 
to compute some quantity using the gradients as well as {the value of a 
vector field component of each vtk in the middle of the cube} and plot 
the result over the cubic geometry, maybe take a slice of that cube at 
the end. I have some roadblocks that prevent me from doing this in a 
less manual, straightforward fashion:

1. I do not see a command in the calculator filter like 
EvaluateAtPoint(myvectorfieldxcomponentvtk1,(x=0,y=0,z=0.5)) to grab the 
value of the x component of the vector field from vtk1 at point 
(0,0,0.5) in Cartesian coordinates and use it in some quantity like 
gradientx*5*EvaluateAtPoint(...) which would be evaluated over the 
entire cubic geometry, but always use the value of that point in the 
middle. I have used this sort of thing before in a program called 
COMSOL, which possesses such a feature in the Scoped Evaluation list 
called at3_geometry, among many other variations.

2. Even if there was a command like in #1, the append attributes command 
doesn't seem to respect the different sources of the vector field, so I 
see only one vector field in the resulting array (by contrast, I can 
name the gradients of the vector field components uniquely in each of 
the filters that outputs them, and the append attributes filter shows 
three distinct batches of gradients from each filter I applied to each vtk).

3. I tried to create a probe at the location I need, but the geometry it 
produces is a single point and thus using it either {directly with 
append attributes to the other gradient results} or {with a calculator 
filter first to get only the quantity I want instead of the scalar field 
and the vector fields evaluated at that point and then use the append 
attributes command} doesn't work because the append attributes 
apparently uses only the overlapping geometry, which of course is only 
the one point.

4. I tried to use group datasets instead, thinking maybe it would just 
take the value I make in the calculator filter from the probe location 
filter and use it in the final calculator filter, but it just throws a 
bunch of errors which I assume again stem from the mismatch of geometry.

5. I had an idea to maybe just clone each of the original vtks to get 
the geometry I need in a new array, and then somehow set all the 
datapoints in each one to the value I get from the probe location 
filter, but this would not only again encounter the problem in #2 with 
the nonunique naming, but I also do not know how to edit the individual 
data points in the file (I see an inkling of this idea in the blog post 
here: https://blog.kitware.com/zero-copy-arrays/ but it's quite beyond 
my current level of understanding of Paraview).

The current alternative (that definitely works) is to just manually copy 
the value I get from {the probe location filter or plot over line filter 
or something like that } into the final calculator filter, but I'd have 
to do that for every one of the batches of 3 vtk files I get, which is 
going to get very large when I start varying my more complicated 
geometry with parametric sweeps (I also need to figure out how to 
automate the process of outputting the slice I take at the end, but one 
problem at a time! I welcome any suggestions on this front).


From sebastien.jourdain at kitware.com  Tue Jul  4 05:45:17 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 4 Jul 2017 03:45:17 -0600
Subject: [Paraview] ParaviewWeb OSMesa build
In-Reply-To: <59556572.d4931c0a.53696.5630@mx.google.com>
References: <59556572.d4931c0a.53696.5630@mx.google.com>
Message-ID: <CABObKxdx+DKhjbAEp_4xW-t4dM+_Q774djaGfYM6=BhpEgTOAw@mail.gmail.com>

Yes, but you will need to build ParaView with either OSMesa or EGL (if you
have a compatible NVidia GPU).

When you do so, you won't need to build the Qt UI.

Seb

On Thu, Jun 29, 2017 at 2:39 PM, <hayk.grigoryan.a at gmail.com> wrote:

> Hi,
>
>
>
> I'm trying to build ParaViewWeb with OSMesa. I need help with my question.
>
>
>
> I've ubuntu 14.04 server without desktop and X. Can I install and make
> ParaViewWeb to work as a web service on my server?
>
>
>
> Thank in advance,
>
> Hayk
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/18028f16/attachment.html>

From sebastien.jourdain at kitware.com  Tue Jul  4 05:48:10 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 4 Jul 2017 03:48:10 -0600
Subject: [Paraview] ParaViewWeb Error - vtkweb-loader.js
In-Reply-To: <C2E3BCEF-5189-4C45-BB27-81BE9D7CC8FD@gmail.com>
References: <C2E3BCEF-5189-4C45-BB27-81BE9D7CC8FD@gmail.com>
Message-ID: <CABObKxe+wp-LYcLm4ptb7tAQo2WFo3GKnyYyxQJ9XVtWSu3CQQ@mail.gmail.com>

This is strange, it seems that you have the Web code of ParaView 4.

How did you get/build ParaView? Are you sure it is ParaView 5.2?

On Thu, Jun 29, 2017 at 4:31 AM, Mariam <mbahameish at gmail.com> wrote:

> Hi,
>
> I am trying to run ParaViewWeb using the following command:
>
> ./pvpython -dr ../Resources/web/visualizer/server/pvw-visualizer.py
> --content ../Resources/web/visualizer/www
>
>
>
> The connection is established, however, when accessing
> http://localhost:8080, I receive the following error in the browser
> (checked from Chrome Developer Tools):
>
> vtkweb-loader.js Failed to load resource: the server responded with a
> status of 404 (Not Found)
>
> localhost/:15 Uncaught ReferenceError: vtkWeb is not defined at
> localhost/:15
>
>
>
> From the command line, I receive the following:
>
> [HTTPChannel,0,127.0.0.1] "127.0.0.1" - - [29/Jun/2017:10:23:14 +0000]
> "GET /lib/core/vtkweb-loader.js HTTP/1.1" 404 145 "http://localhost:8080/"
> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/59.0.3071.104 Safari/537.36"
>
>
>
> ParaView version: 5.2
>
> OS: Mac
>
>
>
> I tried to look for /lib/core/vtkweb-loader.js, but this location doesn?t
> exist in the current version. It seems to be existed in older versions such
> as 5.1, so I tried to install 5.1 as well but I got the same error.
>
>
>
> Any idea on how to resolve the issue?
>
>
>
> Thanks,
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/2692dca0/attachment.html>

From mbahameish at gmail.com  Tue Jul  4 06:04:05 2017
From: mbahameish at gmail.com (Mariam Bahameish)
Date: Tue, 4 Jul 2017 11:04:05 +0100
Subject: [Paraview] ParaViewWeb Error - vtkweb-loader.js
In-Reply-To: <CABObKxe+wp-LYcLm4ptb7tAQo2WFo3GKnyYyxQJ9XVtWSu3CQQ@mail.gmail.com>
References: <C2E3BCEF-5189-4C45-BB27-81BE9D7CC8FD@gmail.com>
 <CABObKxe+wp-LYcLm4ptb7tAQo2WFo3GKnyYyxQJ9XVtWSu3CQQ@mail.gmail.com>
Message-ID: <A7FB3A43-9BAC-4BDF-A2B0-9B5A87E59E58@gmail.com>

I have installed the binary installation from the download page.

Sent from my iPhone

> On Jul 4, 2017, at 10:48 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
> 
> This is strange, it seems that you have the Web code of ParaView 4.
> 
> How did you get/build ParaView? Are you sure it is ParaView 5.2?
> 
>> On Thu, Jun 29, 2017 at 4:31 AM, Mariam <mbahameish at gmail.com> wrote:
>> Hi,
>> 
>> I am trying to run ParaViewWeb using the following command:
>> 
>> ./pvpython -dr ../Resources/web/visualizer/server/pvw-visualizer.py --content ../Resources/web/visualizer/www
>> 
>>  
>> 
>> The connection is established, however, when accessing http://localhost:8080, I receive the following error in the browser (checked from Chrome Developer Tools):
>> 
>> vtkweb-loader.js Failed to load resource: the server responded with a status of 404 (Not Found)
>> 
>> localhost/:15 Uncaught ReferenceError: vtkWeb is not defined at localhost/:15
>> 
>>  
>> 
>> From the command line, I receive the following:
>> 
>> [HTTPChannel,0,127.0.0.1] "127.0.0.1" - - [29/Jun/2017:10:23:14 +0000] "GET /lib/core/vtkweb-loader.js HTTP/1.1" 404 145 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36"
>> 
>>  
>> 
>> ParaView version: 5.2
>> 
>> OS: Mac
>> 
>>  
>> 
>> I tried to look for /lib/core/vtkweb-loader.js, but this location doesn?t exist in the current version. It seems to be existed in older versions such as 5.1, so I tried to install 5.1 as well but I got the same error.
>> 
>>  
>> 
>> Any idea on how to resolve the issue?
>> 
>>  
>> 
>> Thanks,
>> 
>> 
>> _______________________________________________
>> 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
>> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/36dabdbd/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Tue Jul  4 07:04:32 2017
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Tue, 4 Jul 2017 14:04:32 +0300
Subject: [Paraview] multiple visualization pipeline at a time with
 co-processing
In-Reply-To: <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
Message-ID: <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>

Hi Andy,

I tested you suggestion about using multiple script in co-processing. In 
this case, i used following code in the adaptor side to add multiple 
pipeline

       for (int i = 0; i < *nscript; i++) {
         pipeline->Initialize(pythonScriptNames[i]);
         g_coprocessor->AddPipeline(pipeline);
       }

When i run the simulation, i am getting following warning

Warning: In 
/okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, 
line 66
vtkPVTrivialProducer (0x13816760): New time step is not after last time 
step.

the output seems not correct and it is zoom out version of second 
pipeline (png file). The first pipeline is not even triggered. Do i 
missing something in here? BTW, i am using PV 5.3.

Thanks,

--ufuk

On 16/05/2017 16:08, Andy Bauer wrote:
> Hi Ufuk,
>
> If you create a vtkCPythonScriptPipeline, when you initialize it with 
> the script file name (which has to be done on each process) everything 
> will be taken care of with respect to broadcasting the file contents 
> from process 0 to the others. We aren't sophisticated enough to parse 
> the Python script to see if it imports other scripts that are not part 
> of ParaView (e.g. paraview.simple) or Python (e.g. sys). That is why I 
> recommended the first approach as opposed to the second approach 
> above. Depending on the compute platform and how many MPI processes 
> are in the run the difference may be negligible but having 100K 
> processes or more trying to access the same file can seriously slow 
> down an HPC machine.
>
> Cheers,
> Andy
>
> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Thanks Andy. That is exactly what i am looking for. The
>     broadcasting mechanism is not clear to me yet. Do i need to
>     broadcast only the file names? Anyway, i will try to implement it
>     and see what is going on there.
>
>     Thanks again,
>     Regards,
>
>     --ufuk
>
>
>     On 16/05/2017 14:58, Andy Bauer wrote:
>>     Hi Ufuk,
>>
>>     Unless I'm not understanding your question correctly, I think you
>>     can get what you want by adding in multiple
>>     vtkCPPythonScriptPipelines to your vtkCPProcessor object in your
>>     adaptor. Alternatively if you want to have a single, master
>>     Catalyst script handling other Catalyst scripts you can do
>>     something like the following:
>>     ================
>>     import script_a
>>     import script_b
>>     import script_c
>>
>>     def RequestDataDescription(datadescription):
>>       script_a.RequestDataDescription(datadescription)
>>       script_b.RequestDataDescription(datadescription)
>>       script_c.RequestDataDescription(datadescription)
>>
>>     def DoCoProcessing(datadescription):
>>       script_a.DoCoProcessing(datadescription)
>>       script_b.DoCoProcessing(datadescription)
>>       script_c.DoCoProcessing(datadescription)
>>     ===================
>>
>>     The first way is the recommended way though as that should be
>>     more efficient by having process 0 read the scripts and
>>     broadcasting the script contents to the other  processes for use.
>>     The second method will only do that for the master script.
>>
>>     Please let me know if this doesn't answer your question.
>>
>>     Cheers,
>>     Andy
>>
>>     On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE)
>>     <u.utku.turuncoglu at be.itu.edu.tr
>>     <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>>
>>         Hi All,
>>
>>         I just wonder that is it possible to trigger multiple
>>         visualization pipeline in the same time with co-processing.
>>         The co-processing script generator plugin mainly outputs only
>>         single pipeline at a time and that is fine but what about
>>         combining multiple Python script (generated by plugin) using
>>         higher level Python script to trigger multiple pipelines. So,
>>         i think that this will be much efficient way to look at
>>         different part of the data without writing to the disk. I am
>>         not sure but somebody else might do it before.
>>
>>         Regards,
>>
>>         --ufuk
>>
>>         _______________________________________________
>>         Powered by www.kitware.com <http://www.kitware.com>
>>
>>         Visit other Kitware open-source projects at
>>         http://www.kitware.com/opensource/opensource.html
>>         <http://www.kitware.com/opensource/opensource.html>
>>
>>         Please keep messages on-topic and check the ParaView Wiki at:
>>         http://paraview.org/Wiki/ParaView
>>         <http://paraview.org/Wiki/ParaView>
>>
>>         Search the list archives at:
>>         http://markmail.org/search/?q=ParaView
>>         <http://markmail.org/search/?q=ParaView>
>>
>>         Follow this link to subscribe/unsubscribe:
>>         http://public.kitware.com/mailman/listinfo/paraview
>>         <http://public.kitware.com/mailman/listinfo/paraview>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/81f67ff3/attachment.html>

From nabil.ghodbane at gmail.com  Tue Jul  4 09:02:08 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Tue, 4 Jul 2017 15:02:08 +0200
Subject: [Paraview] superbuild: configure: error swr requires C++14 support
Message-ID: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>

dear experts
I am trying to compile Paraview with the latest superbuild using gcc 4.8.5
the compilation fails with the error message that C++14 is needed...
*configure: error swr requires C++14 support*

This raises two questions:
1/ Can one switch to c++11  and if yes, how ?
2/ what is the minimal configuration for gcc one needs to setup in order to
be able to compile Paraview with superbuild.
thanks


Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/5296c2d2/attachment.html>

From dave.demarle at kitware.com  Tue Jul  4 09:54:29 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 4 Jul 2017 09:54:29 -0400
Subject: [Paraview] superbuild: configure: error swr requires C++14
	support
In-Reply-To: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>
References: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>
Message-ID: <CANjZAi9cpQ7gcWxttJ1MoCeaaWR2s+fLu1g4fu2ab1mtndhe8w@mail.gmail.com>

Hi Nabil,

That was a regression that snuck in just before the 5.4.0 tag. Apologies.

One commit beyond the tag fixes it by patching mesa 17.1.1 to remove the
c++14 dependency.
https://gitlab.kitware.com/paraview/paraview-superbuild/commit/aa8a66b270fb481e39b9919f9ea68017a3a1543b

The patch is also now in mesa 17.1.3. ParaView 5.4.1 will address this by
bumping mesa and removing the patch.

hth




David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, Jul 4, 2017 at 9:02 AM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
wrote:

> dear experts
> I am trying to compile Paraview with the latest superbuild using gcc 4.8.5
> the compilation fails with the error message that C++14 is needed...
> *configure: error swr requires C++14 support*
>
> This raises two questions:
> 1/ Can one switch to c++11  and if yes, how ?
> 2/ what is the minimal configuration for gcc one needs to setup in order
> to be able to compile Paraview with superbuild.
> thanks
>
>
> Nabil Ghodbane (Ph. D. Habil*.*)
> Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043>
> Mailto: nabil.ghodbane at gmail.com
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170704/bdb900c4/attachment.html>

From brantosaurus at hotmail.com  Wed Jul  5 07:52:17 2017
From: brantosaurus at hotmail.com (David Brant)
Date: Wed, 5 Jul 2017 11:52:17 +0000
Subject: [Paraview] Help - What is the difference between the windows
In-Reply-To: <CAB5Fpx5KyNOKpuHHousZGz5gTQjd-+g1gtTzkhJ3gpvaC7Ahvw@mail.gmail.com>
References: <DB6P189MB0293F8E0EACDD1C3F78184AED8D30@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>,
 <CAB5Fpx5KyNOKpuHHousZGz5gTQjd-+g1gtTzkhJ3gpvaC7Ahvw@mail.gmail.com>
Message-ID: <DB6P189MB02935055CB50F479E6286D1CD8D40@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>

Many thanks for that Cory.

Another related question if I may.
Does the Linux version have self-contained MPI support or do I need to install that too?
It runs without complaining about it.
Dave
________________________________
From: Cory Quammen <cory.quammen at kitware.com>
Sent: 30 June 2017 16:10
To: David Brant
Cc: paraview at paraview.org
Subject: Re: [Paraview] Help - What is the difference between the windows


1  Is the zip version essentially a standalone app that can be installed simply by extracting and a shortcut to the exe?

 Yes, the paraview.exe will work right out of the unzipped directory.

2  What is the difference between the MPI-windows and -windows versions of the app?

I appreciate MPI is for parallel working, but does one version (which?) come with self contained MPI support, while the other requires MPI support to be independently installed.

Neither version comes with self-contained MPI support. The MPI version on Windows requires that you install Microsoft's MPI, which you can obtain here: https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx. The non-MPI version simply does not make use of MPI, even if you have Microsoft's MPI installed.

Microsoft MPI<https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx>
msdn.microsoft.com
Microsoft MPI (MS-MPI) is a Microsoft implementation of the Message Passing Interface standard for developing and running parallel applications on the Windows ...



Cory


Thanks, Dave



_______________________________________________
Powered by www.kitware.com<http://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 Info Page - Kitware<http://public.kitware.com/mailman/listinfo/paraview>
public.kitware.com
To see the collection of prior postings to the list, visit the ParaView Archives. Using ParaView: To post a message to all the list members, send ...







--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/225f02d7/attachment.html>

From super_achie at hotmail.com  Wed Jul  5 08:08:37 2017
From: super_achie at hotmail.com (A .)
Date: Wed, 5 Jul 2017 12:08:37 +0000
Subject: [Paraview] Integrating precompiled Catalyst into external projects
Message-ID: <HE1P194MB02340F861DEA0FC3B90DEF7D97D40@HE1P194MB0234.EURP194.PROD.OUTLOOK.COM>

Dear members,


I would like to have Catalyst precompiled and ready for use for developers that want to work on my project. In this way they don't need to go through the procedure of installing dependencies and building Catalyst themselves (which currently takes longer than building my project...).


The problem is the absolute paths that are used in all the .cmake files, such as ParaViewConfig.cmake and UseParaView.cmake (and all .cmake files they call on).


I thought a "make install" would do the trick as normally it will copy all the essential files (system independent) to the CMAKE_INSTALL_PREFIX directory. But I cannot use the contents of the installation folder as the directory to point to when linking to Catalyst in my project (since there are no configuration files copied).


I was doubtful to ask this question, because if it were possible, I would expect a precompiled Catalyst to be hosted on the ParaView download page. But out of curiosity I ask nonetheless; is it possible?


Best,

Jimmy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/2a9dbb2c/attachment.html>

From treem22 at gatech.edu  Wed Jul  5 09:57:00 2017
From: treem22 at gatech.edu (Mike Tree)
Date: Wed, 5 Jul 2017 09:57:00 -0400
Subject: [Paraview] Force Programmable Filter to Run in Serial
Message-ID: <CAOO6v06RDdU34Y3ykcB=tf6-ou77HVJJJ0hz7oGGtvok3eEEdg@mail.gmail.com>

All,

I currently have a python script that uses a programmable filter to pull
values (scalars) from one block of a data set and add them to a different
block:

output = self.GetOutputDataObject(0)

output.DeepCopy(grids)


numofcells = grids.GetNumberOfCells()

Pinf = farfield.GetCellData().GetArray('Pinf').GetValue(0)

Minf = farfield.GetCellData().GetArray('Minf').GetValue(0)

Vinf = farfield.GetCellData().GetArray('Vinf').GetValue(0)


PinfArray = vtk.vtkDoubleArray()

PinfArray.SetName('Pinf')

MinfArray = vtk.vtkDoubleArray()

MinfArray.SetName('Minf')

VinfArray = vtk.vtkDoubleArray()

VinfArray.SetName('Vinf')\


for i in range(numofcells):

    PinfArray.InsertNextValue(Pinf)

    MinfArray.InsertNextValue(Minf)

    VinfArray.InsertNextValue(Vinf)


output.GetCellData().AddArray(PinfArray)

output.GetCellData().AddArray(MinfArray)

output.GetCellData().AddArray(VinfArray)


I wrote the script using a small data set, employing only one processor.
With much larger data sets the other parts of the script benefit from
parallel execution, but my programmable filter is no longer working well.
The programmable script appears to execute on each processor, and each
processor is holding a portion of the data. The programmable filter output
shows partial Pinf, Minf, and Vinf arrays.

So, I have two options. I can either add the necessary commands to this
programmable filter script to allow it to correctly run across multiple
processors, or I can possibly force all the data back onto one processor
for this step, and run this programmable filter on only one node.

Which is easier, and how would I go about doing it?

Please note, both my Request Information and Request Update Extent scripts
are currently blank, and both input data types are unstructured grids.

Any help will be much appreciated!

Thanks,
Mike Tree

-- 
Mike Tree, PhD
Cardiovascular Fluid Mechanics Laboratory
Georgia Institute of Technology
Atlanta, GA
treem22 at gatech.edu
678-249-0922
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/2a8e3c8f/attachment.html>

From klarmann at mechanik.tu-darmstadt.de  Wed Jul  5 10:11:50 2017
From: klarmann at mechanik.tu-darmstadt.de (Simon Klarmann)
Date: Wed, 5 Jul 2017 16:11:50 +0200
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows
Message-ID: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>

Dear Members,

 

I wanted to get rid of the dependency on Python. The connection by pure C++
works just fine.

 

The problem occurs when establishing the live connection to Paraview,
closing Paraview and then try to send some data again.

I tracked it down to the vtkSocket class inside the method Receive. After
the connection is terminated on the Paraview side, e.g. by closing Paraview,
the call of vtkLiveInsituLink::InsituUpdate gets stuck in the
vtkSocket::Receive method. Even though I get a message that the connection
was terminated.

 

A temporary fix for my case was to replace in Line 609 of the vtkSocket.cxx
if (nRecvd == 0) with if (nRecvd <= 0), because on disconnection the return
value of nRecvd is -1. Then everything works well.

 

I only used the following methods in the given order to transfer the data:

 

vtkLiveInsituLink::InsituUpdate

vtkSMSourceProxy::UpdatePipeline

vtkLiveInsituLink::InsituPostProcess

 

 

Are there further steps to perform or is there a way to check if the
connection is still alive?

 

 

Operating System: Windows 7, Visual Studio 2017

 

Thanks,

Simon

 

 

 

 

Dipl.-Ing. Simon Klarmann

 

Bau- und Umweltingenieurwissenschaften
Technische Universit?t Darmstadt

Fachgebiet Festk?rpermechanik

 

Tel.: +49 6151 16 ? 22642

Mail: klarmann at mechanik.tu-darmstadt.de

Franziska-Braun-Stra?e 7

Geb?ude L5|01, Raum 542

64287 Darmstadt

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/70a568b2/attachment.html>

From roeber at dkrz.de  Wed Jul  5 11:04:47 2017
From: roeber at dkrz.de (=?UTF-8?Q?Niklas_R=c3=b6ber?=)
Date: Wed, 5 Jul 2017 17:04:47 +0200
Subject: [Paraview] Dilation Operation ...
In-Reply-To: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>
References: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>
Message-ID: <b6bb2ff4-f800-ed4a-42ed-d716a44d32d0@dkrz.de>

Dear All,

I have a very low resolution netCDF that I would like to visualize as 
cell data using lon/lat projection. Reading the data using lon/lat 
projection, the variables are represented as point data (image1). If the 
data is read in spherical, the variables are represented as cell data 
(image2). Comparing both, shows that some features are missing in the 
lon/lat projection, see for example central America and Spain. Applying 
a PointDataToCellData filter to the point data in lon/lat smoothes these 
features away completely (image3).
Is there a possibility to visualize the data correctly, as shown with 
spherical projection, but in lon/lat? Or can the point data somehow be 
dilated so that central America and half of Europe are not "filtered" out?

Thanks for any help!
Cheers, Niklas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1.png
Type: image/png
Size: 16525 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/f32d3d89/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image2.png
Type: image/png
Size: 43154 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/f32d3d89/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image3.png
Type: image/png
Size: 12148 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/f32d3d89/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5339 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/f32d3d89/attachment.bin>

From brantosaurus at hotmail.com  Wed Jul  5 12:32:50 2017
From: brantosaurus at hotmail.com (David Brant)
Date: Wed, 5 Jul 2017 16:32:50 +0000
Subject: [Paraview] Help - What is the difference between the windows
In-Reply-To: <CAB5Fpx5KyNOKpuHHousZGz5gTQjd-+g1gtTzkhJ3gpvaC7Ahvw@mail.gmail.com>
References: <DB6P189MB0293F8E0EACDD1C3F78184AED8D30@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>,
 <CAB5Fpx5KyNOKpuHHousZGz5gTQjd-+g1gtTzkhJ3gpvaC7Ahvw@mail.gmail.com>
Message-ID: <DB6P189MB029376F75D577EDDF22611C6D8D40@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>

Many thanks for that Cory.


Does the Linux version have self-contained MPI support or do I need to install that too?

Dave

________________________________
From: Cory Quammen <cory.quammen at kitware.com>
Sent: 30 June 2017 16:10
To: David Brant
Cc: paraview at paraview.org
Subject: Re: [Paraview] Help - What is the difference between the windows


1  Is the zip version essentially a standalone app that can be installed simply by extracting and a shortcut to the exe?

 Yes, the paraview.exe will work right out of the unzipped directory.

2  What is the difference between the MPI-windows and -windows versions of the app?

I appreciate MPI is for parallel working, but does one version (which?) come with self contained MPI support, while the other requires MPI support to be independently installed.

Neither version comes with self-contained MPI support. The MPI version on Windows requires that you install Microsoft's MPI, which you can obtain here: https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx. The non-MPI version simply does not make use of MPI, even if you have Microsoft's MPI installed.

Microsoft MPI<https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx>
msdn.microsoft.com
Microsoft MPI (MS-MPI) is a Microsoft implementation of the Message Passing Interface standard for developing and running parallel applications on the Windows ...



Cory


Thanks, Dave



_______________________________________________
Powered by www.kitware.com<http://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

ParaView - KitwarePublic<http://paraview.org/Wiki/ParaView>
paraview.org
ParaView is an open-source, multi-platform application designed to visualize data sets of varying sizes from small to very large. The goals of the ParaView project ...




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 Info Page - Kitware<http://public.kitware.com/mailman/listinfo/paraview>
public.kitware.com
To see the collection of prior postings to the list, visit the ParaView Archives. Using ParaView: To post a message to all the list members, send ...







--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/9169b93b/attachment.html>

From Patrick.Begou at legi.grenoble-inp.fr  Wed Jul  5 13:08:24 2017
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Wed, 5 Jul 2017 19:08:24 +0200
Subject: [Paraview] gpu_shader4 extension is not supported
In-Reply-To: <8a36609c-066d-de70-b9a1-d7cdb235445d@lbl.gov>
References: <58292800-ab8a-c729-4dfe-63bb9fef8a03@legi.grenoble-inp.fr>
 <CAOXZzG4gnqHjRLTN2r4jtZmOFpx6b6KvY5oEFYhNfT6BvQWn1A@mail.gmail.com>
 <f84e18ff-61bc-709b-a6a7-81070e94183e@legi.grenoble-inp.fr>
 <f480dd2e-a5a9-dfba-26e2-c5658b3768d8@lbl.gov>
 <2adedaae-8ee6-b3e5-250b-a3c00c1e1580@legi.grenoble-inp.fr>
 <8329b261-8387-fd31-4b63-a14ca125e007@gmail.com>
 <71fe5007-fc1b-874d-81dc-0685b2354c44@legi.grenoble-inp.fr>
 <361eef80-2d07-c501-b480-f3bb824334b1@gmail.com>
 <9271f3bc-6d9b-0a2d-7bfa-81f60c4ada44@legi.grenoble-inp.fr>
 <8a36609c-066d-de70-b9a1-d7cdb235445d@lbl.gov>
Message-ID: <21f2e374-19ae-982a-adbb-bbb636896865@legi.grenoble-inp.fr>

I'm starting again this thread as I still have a problem with mesa (and so all 
mesa advices will be in the same discussion).

Now it is on a server with an AMD Firepro GPU. The Centos6.9 mesa version is too 
old (mesa-libGL-10.4.3-1.el6.x86_64). Installing a new el6 mesa rpm 
(mesa-libGL-11.0.7-4.el6.x86_64) breaks other software so I had to compile mesa 
in paraview tree. All run fine (no error when building mesa or paraview 5.4 or 
5.3) but I discover that glyph are not working. No message output in the 
terminal to provide any help.

I've several setup of paraview 5.4 (with osmesa on cluster nodes, with nvidia 
libraries on workstations... ) and glyph is running fine so it is not a paraview 
5.4 internal problem.

On the server with the AMD Firepro GPU I use mesa-17.0.4.tar.gz with the 
following prerequisites:
- llvm-4.0.0.src.tar.xz
- libdrm-2.4.70.tar.gz
- xcb-proto-1.12.tar.gz
-  pthread-stubs-0.3.tar.gz
- libXau-1.0.8.tar.gz
- libxcb-1.12.tar.gz
- libxshmfence-1.2.tar.gz

all builded basicaly with
PKG_CONFIG_PATH=/opt/paraview-5.4.0/lib/pkgconfig  ./configure 
--prefix=/opt/paraview-5.4.0
make
make install

To build mesa-17.0.4 I use:
export LD_LIBRARY_PATH=/opt/paraview-5.4.0/lib:$LD_LIBRARY_PATH
export PATH=/opt/paraview-5.4.0/bin:$PATH
./configure \
PKG_CONFIG_PATH=/opt/paraview-5.4.0/lib/pkgconfig \
--prefix=/opt/paraview-5.4.0 \
--enable-texture-float \
--with-llvm-prefix=/opt/paraview-5.4.0

Of course I set LD_LIBRARY_PATH to load mesa in the Paraview tree and I check 
with strace it is used.

Any idea of what could be wrong ?

Patrick

-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================


From cory.quammen at kitware.com  Wed Jul  5 13:11:51 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 5 Jul 2017 13:11:51 -0400
Subject: [Paraview] Help - What is the difference between the windows
In-Reply-To: <DB6P189MB02935055CB50F479E6286D1CD8D40@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>
References: <DB6P189MB0293F8E0EACDD1C3F78184AED8D30@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>
 <CAB5Fpx5KyNOKpuHHousZGz5gTQjd-+g1gtTzkhJ3gpvaC7Ahvw@mail.gmail.com>
 <DB6P189MB02935055CB50F479E6286D1CD8D40@DB6P189MB0293.EURP189.PROD.OUTLOOK.COM>
Message-ID: <CAB5Fpx4hbXnEjcUHW142p3gZ_PrmVHNHUUkhbpgt6DapVnPZMg@mail.gmail.com>

The Linux binary does indeed include a self-contained MPI implementation
with mpiexec.

Cory

On Wed, Jul 5, 2017 at 7:52 AM, David Brant <brantosaurus at hotmail.com>
wrote:

> Many thanks for that Cory.
> Another related question if I may.
> Does the Linux version have self-contained MPI support or do I need to
> install that too?
> It runs without complaining about it.
> Dave
> ------------------------------
> *From:* Cory Quammen <cory.quammen at kitware.com>
> *Sent:* 30 June 2017 16:10
> *To:* David Brant
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Help - What is the difference between the
> windows
>
>
>> 1  Is the zip version essentially a standalone app that can be installed
>> simply by extracting and a shortcut to the exe?
>>
>  Yes, the paraview.exe will work right out of the unzipped directory.
>
>> 2  What is the difference between the MPI-windows and -windows versions
>> of the app?
>>
>> I appreciate MPI is for parallel working, but does one version
>> (which?) come with self contained MPI support, while the other requires MPI
>> support to be independently installed.
>>
> Neither version comes with self-contained MPI support. The MPI version on
> Windows requires that you install Microsoft's MPI, which you can obtain
> here: https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx.
> The non-MPI version simply does not make use of MPI, even if you have
> Microsoft's MPI installed.
>
> Microsoft MPI
> <https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx>
> msdn.microsoft.com
> Microsoft MPI (MS-MPI) is a Microsoft implementation of the Message
> Passing Interface standard for developing and running parallel applications
> on the Windows ...
>
>
>
> Cory
>
>
>> Thanks, Dave
>>
>>
>>
>>
>> _______________________________________________
>> 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 Info Page - Kitware
>> <http://public.kitware.com/mailman/listinfo/paraview>
>> public.kitware.com
>> To see the collection of prior postings to the list, visit the ParaView
>> Archives. Using ParaView: To post a message to all the list members, send
>> ...
>>
>>
>>
>>
>>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/3a47a8ab/attachment.html>

From nico.vancleemput at gmail.com  Wed Jul  5 16:30:25 2017
From: nico.vancleemput at gmail.com (Nico Van Cleemput)
Date: Wed, 5 Jul 2017 22:30:25 +0200
Subject: [Paraview] Adding arrow to 3D plot
Message-ID: <CADXCEk8woF2++dCsAvGUAJj26FnXK-63vWeaQaaxmgA9Owc0LQ@mail.gmail.com>

Dear all

I'm sure that the following is a simple question, and I found it a few
times, but didn't see any solution anywhere.

I'm plotting a 3D model loaded from a file, e.g., the cube in the following
file:

====
# vtk DataFile Version 3.0
vtk output
ASCII
DATASET STRUCTURED_GRID
DIMENSIONS 2 2 2
POINTS 8 float
0 0 0 0 0 1 0 1 0
0 1 1 1 0 0 1 0 1
1 1 0 1 1 1

CELL_DATA 1
====

Next I want to add an arrow that starts at (x1,y1,z1) and ends at
(x2,y2,z2). How can I add this arrow?

I can add an arrow using Sources > Arrow. In Display I can then specify
translation, scale, orientation and origin, but it's not clear to me which
values I need to enter to get the arrow I want.

I'm using ParaView 5.4.0.

Cheers
Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170705/3e9bfa10/attachment.html>

From kmorel at sandia.gov  Thu Jul  6 02:48:22 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 6 Jul 2017 06:48:22 +0000
Subject: [Paraview] Dilation Operation ...
In-Reply-To: <b6bb2ff4-f800-ed4a-42ed-d716a44d32d0@dkrz.de>
References: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>,
 <b6bb2ff4-f800-ed4a-42ed-d716a44d32d0@dkrz.de>
Message-ID: <22C1A4D1-22EA-49C7-B0D7-934174AE52AE@sandia.gov>

Niklas,

My first question is, are the data actually being read in as a point data field or a cell data field? If you go to the Information panel, what does it say the data are?

I'm not at my computer to check this, but I believe that if you read data as a lon/lat projection, the mesh is most likely read as a 2D "image", and if so, that is rendered with the "slice" representation. If that's the case, can you try changing the representation to "surface"?

-Ken

Sent from my iPad

> On Jul 5, 2017, at 7:10 AM, Niklas R?ber <roeber at dkrz.de> wrote:
> 
> Dear All,
> 
> I have a very low resolution netCDF that I would like to visualize as cell data using lon/lat projection. Reading the data using lon/lat projection, the variables are represented as point data (image1). If the data is read in spherical, the variables are represented as cell data (image2). Comparing both, shows that some features are missing in the lon/lat projection, see for example central America and Spain. Applying a PointDataToCellData filter to the point data in lon/lat smoothes these features away completely (image3).
> Is there a possibility to visualize the data correctly, as shown with spherical projection, but in lon/lat? Or can the point data somehow be dilated so that central America and half of Europe are not "filtered" out?
> 
> Thanks for any help!
> Cheers, Niklas
> <image1.png>
> <image2.png>
> <image3.png>
> _______________________________________________
> 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

From roeber at dkrz.de  Thu Jul  6 03:59:15 2017
From: roeber at dkrz.de (=?UTF-8?Q?Niklas_R=c3=b6ber?=)
Date: Thu, 6 Jul 2017 09:59:15 +0200
Subject: [Paraview] Dilation Operation ...
In-Reply-To: <22C1A4D1-22EA-49C7-B0D7-934174AE52AE@sandia.gov>
References: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>
 <b6bb2ff4-f800-ed4a-42ed-d716a44d32d0@dkrz.de>
 <22C1A4D1-22EA-49C7-B0D7-934174AE52AE@sandia.gov>
Message-ID: <6d9112bd-8673-126b-ea31-1208fe8dfaef@dkrz.de>

Hi Ken,

thanks for the reply. From your suggestion, I was playing more with the 
different output types available, and I am not sure why, but it works 
now. If I read the data using spherical coordinates checked and the 
output type set to image, the data is actually read in as 2D lon/lat 
representation, but with the data represented as cells and not as 
points. I always believed that with the spherical coordinate settings 
checked, the output would be represented on a sphere, but its obviously 
not. Good for me. Thanks again.

Cheers,
Niklas

> Niklas,
>
> My first question is, are the data actually being read in as a point data field or a cell data field? If you go to the Information panel, what does it say the data are?
>
> I'm not at my computer to check this, but I believe that if you read data as a lon/lat projection, the mesh is most likely read as a 2D "image", and if so, that is rendered with the "slice" representation. If that's the case, can you try changing the representation to "surface"?
>
> -Ken
>
> Sent from my iPad
>
>> On Jul 5, 2017, at 7:10 AM, Niklas R?ber <roeber at dkrz.de> wrote:
>>
>> Dear All,
>>
>> I have a very low resolution netCDF that I would like to visualize as cell data using lon/lat projection. Reading the data using lon/lat projection, the variables are represented as point data (image1). If the data is read in spherical, the variables are represented as cell data (image2). Comparing both, shows that some features are missing in the lon/lat projection, see for example central America and Spain. Applying a PointDataToCellData filter to the point data in lon/lat smoothes these features away completely (image3).
>> Is there a possibility to visualize the data correctly, as shown with spherical projection, but in lon/lat? Or can the point data somehow be dilated so that central America and half of Europe are not "filtered" out?
>>
>> Thanks for any help!
>> Cheers, Niklas
>> <image1.png>
>> <image2.png>
>> <image3.png>
>> _______________________________________________
>> 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


-- 
______________________________________________

Dr. Niklas R?ber
Visualisierung
Abteilung Anwendungen

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

email: roeber at 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
______________________________________________


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5339 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/468c4d78/attachment.bin>

From utkarsh.ayachit at kitware.com  Thu Jul  6 10:14:47 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 6 Jul 2017 10:14:47 -0400
Subject: [Paraview] [EXTERNAL] Re: long animations are freezing halfway
	through
In-Reply-To: <CADHSJjA1=xKJvAE2ixxJ_UWgR-fmzrf_Fv3L5WLn3C-gFRs45w@mail.gmail.com>
References: <CA+Y385yiZmpvOg_KUzdRzjwpuGka-xDqv1YZrkuEakv2CTLWbA@mail.gmail.com>
 <CADHSJjA2H=mfE48w05TXOSzKfs912gsz2CL7E=mvhOxPNyq5FA@mail.gmail.com>
 <575e4d66cec04221a06d846344dd5e6d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjA1=xKJvAE2ixxJ_UWgR-fmzrf_Fv3L5WLn3C-gFRs45w@mail.gmail.com>
Message-ID: <CADHSJjBKvXkhD+BGi=ggGQti-dvoi_NzZ3LFDw20D5310HBTUg@mail.gmail.com>

Just to give an update, while I couldn't reproduce the issue with Giles
example, I was able to do it with another customer. It's quite a curious
thing indeed! Still figuring out where to begin to debug this -- the fact
that it's a Windows only thing makes it even more tedious -- but will keep
you posted.

Utkarsh

On Fri, Jun 23, 2017 at 12:08 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Alan,
>
> I am discussing with Giles off line. Will keep you posted.
>
> Utkarsh
>
> On Fri, Jun 23, 2017 at 12:05 PM, Scott, W Alan <wascott at sandia.gov>
> wrote:
> > I have another user with this complaint.  I have not been able to
> replicate it.
> >
> > Are you using either opacity or volume rendering?
> >
> > Would you be able to pass the data files to Kitware?
> >
> > Alan
> >
> >> -----Original Message-----
> >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
> >> Utkarsh Ayachit
> >> Sent: Friday, June 23, 2017 7:07 AM
> >> To: Richardson CFD <garcfd at gmail.com>
> >> Cc: ParaView <paraview at paraview.org>
> >> Subject: [EXTERNAL] Re: [Paraview] long animations are freezing halfway
> >> through
> >>
> >> Giles,
> >>
> >> What OS is this on?
> >>
> >> Utkarsh
> >>
> >> On Fri, Jun 23, 2017 at 8:59 AM, Richardson CFD <garcfd at gmail.com>
> wrote:
> >> > I have been having trouble creating longer animations (150 frames)
> >> > from larger data files (1million cells). The animation works fine
> >> > initially but then freezes up about half way through the avi file -
> >> > displaying just a constant unchanging image. Streamlines seems to work
> >> > fine, but velocity contours (attached) is the one causing problems. I
> >> > am having to create the animation in 2 parts, creating 2 seperate avi
> >> > file and then join them after.
> >> >
> >> > Any suggestions or similar experience please let me know. Regards
> Giles.
> >> >
> >> > --
> >> > Richardson CFD
> >> > http://richardsoncfd.weebly.com
> >> >
> >> > _______________________________________________
> >> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/f0221890/attachment.html>

From andy.bauer at kitware.com  Thu Jul  6 10:30:52 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 6 Jul 2017 10:30:52 -0400
Subject: [Paraview] Saving png images in Catalyst-live
In-Reply-To: <CAN4WRTzSt7FVxSrQiYYKb-QJaAoioZ4uf5W978nRpOO8XYGYKA@mail.gmail.com>
References: <CAN4WRTzSt7FVxSrQiYYKb-QJaAoioZ4uf5W978nRpOO8XYGYKA@mail.gmail.com>
Message-ID: <CAMaOp+EJ_FzbxTASHLdyfuMTc=oOB_YKHugW_pqcnWX=GMzKAA@mail.gmail.com>

Hi,

Currently you will need to save the images in the PV GUI during the Live
connection. If you need images at specific time steps you will need to set
Live breakpoints. I hope to be able to modify Catalyst image output through
the Live connection but there are a lot of options that aren't always easy
to capture so it will take quite a bit of design work to get right.

Cheers,
Andy

On Mon, Jul 3, 2017 at 5:39 AM, Luk?? Kresta <lukas.kresta at gmail.com> wrote:

> Hi,
>
> i would like to save image with my ParaView Catalyst. But I use live
> visualization(no render view) and I send to Catalyst unstructured grid. Can
> I somehow generate png image?
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/e6aa81bc/attachment.html>

From andy.bauer at kitware.com  Thu Jul  6 11:09:50 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 6 Jul 2017 11:09:50 -0400
Subject: [Paraview] multiple visualization pipeline at a time with
	co-processing
In-Reply-To: <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
 <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
Message-ID: <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>

Hi Ufuk,

I'm guessing the issue is that the calls to Catalyst are not consistent.
Could you share your Python scripts? Also, did you modify them manually?

I tried with PV 5.3. with
the ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/ example with the
attached scripts simultaneously by running with "./CxxFullExample
doubleoutputs.py output3.py image11.py" and got the correct output and no
warnings.

Cheers,
Andy

On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Andy,
>
> I tested you suggestion about using multiple script in co-processing. In
> this case, i used following code in the adaptor side to add multiple
> pipeline
>
>       for (int i = 0; i < *nscript; i++) {
>         pipeline->Initialize(pythonScriptNames[i]);
>         g_coprocessor->AddPipeline(pipeline);
>       }
>
> When i run the simulation, i am getting following warning
>
> Warning: In /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/
> ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 66
> vtkPVTrivialProducer (0x13816760): New time step is not after last time
> step.
>
> the output seems not correct and it is zoom out version of second pipeline
> (png file). The first pipeline is not even triggered. Do i missing
> something in here? BTW, i am using PV 5.3.
>
> Thanks,
>
> --ufuk
>
>
> On 16/05/2017 16:08, Andy Bauer wrote:
>
> Hi Ufuk,
>
> If you create a vtkCPythonScriptPipeline, when you initialize it with the
> script file name (which has to be done on each process) everything will be
> taken care of with respect to broadcasting the file contents from process 0
> to the others. We aren't sophisticated enough to parse the Python script to
> see if it imports other scripts that are not part of ParaView (e.g.
> paraview.simple) or Python (e.g. sys). That is why I recommended the first
> approach as opposed to the second approach above. Depending on the compute
> platform and how many MPI processes are in the run the difference may be
> negligible but having 100K processes or more trying to access the same file
> can seriously slow down an HPC machine.
>
> Cheers,
> Andy
>
> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE) <
> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Thanks Andy. That is exactly what i am looking for. The broadcasting
>> mechanism is not clear to me yet. Do i need to broadcast only the file
>> names? Anyway, i will try to implement it and see what is going on there.
>>
>> Thanks again,
>> Regards,
>>
>> --ufuk
>>
>>
>> On 16/05/2017 14:58, Andy Bauer wrote:
>>
>> Hi Ufuk,
>>
>> Unless I'm not understanding your question correctly, I think you can get
>> what you want by adding in multiple vtkCPPythonScriptPipelines to your
>> vtkCPProcessor object in your adaptor. Alternatively if you want to have a
>> single, master Catalyst script handling other Catalyst scripts you can do
>> something like the following:
>> ================
>> import script_a
>> import script_b
>> import script_c
>>
>> def RequestDataDescription(datadescription):
>>   script_a.RequestDataDescription(datadescription)
>>   script_b.RequestDataDescription(datadescription)
>>   script_c.RequestDataDescription(datadescription)
>>
>> def DoCoProcessing(datadescription):
>>   script_a.DoCoProcessing(datadescription)
>>   script_b.DoCoProcessing(datadescription)
>>   script_c.DoCoProcessing(datadescription)
>> ===================
>>
>> The first way is the recommended way though as that should be more
>> efficient by having process 0 read the scripts and broadcasting the script
>> contents to the other  processes for use. The second method will only do
>> that for the master script.
>>
>> Please let me know if this doesn't answer your question.
>>
>> Cheers,
>> Andy
>>
>> On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE) <
>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>
>>> Hi All,
>>>
>>> I just wonder that is it possible to trigger multiple visualization
>>> pipeline in the same time with co-processing. The co-processing script
>>> generator plugin mainly outputs only single pipeline at a time and that is
>>> fine but what about combining multiple Python script (generated by plugin)
>>> using higher level Python script to trigger multiple pipelines. So, i think
>>> that this will be much efficient way to look at different part of the data
>>> without writing to the disk. I am not sure but somebody else might do it
>>> before.
>>>
>>> Regards,
>>>
>>> --ufuk
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/1f1fa9c8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: doubleoutputs.py
Type: text/x-python
Size: 4817 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/1f1fa9c8/attachment.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: output3.py
Type: text/x-python
Size: 4124 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/1f1fa9c8/attachment-0001.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image11.py
Type: text/x-python
Size: 7942 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/1f1fa9c8/attachment-0002.py>

From andy.bauer at kitware.com  Thu Jul  6 11:14:00 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 6 Jul 2017 11:14:00 -0400
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
In-Reply-To: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>
References: <00ba01d2f598$a5554a30$efffde90$@mechanik.tu-darmstadt.de>
Message-ID: <CAMaOp+FXm5riQxzHkrRNng6oTtMBQWFeeZi-V9aU4dmcUD4ixQ@mail.gmail.com>

Hi Simon,

Is the Python dependency that you're trying to get rid of on the Catalyst
side or on the pvserver/GUI side? If I remember correctly on the Catalyst
side Python was required for the Live connection.

Cheers,
Andy

On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann <
klarmann at mechanik.tu-darmstadt.de> wrote:

> Dear Members,
>
>
>
> I wanted to get rid of the dependency on Python. The connection by pure
> C++ works just fine.
>
>
>
> The problem occurs when establishing the live connection to Paraview,
> closing Paraview and then try to send some data again.
>
> I tracked it down to the vtkSocket class inside the method Receive. After
> the connection is terminated on the Paraview side, e.g. by closing
> Paraview, the call of vtkLiveInsituLink::InsituUpdate gets stuck in the
> vtkSocket::Receive method. Even though I get a message that the connection
> was terminated.
>
>
>
> A temporary fix for my case was to replace in Line 609 of the
> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
> disconnection the return value of nRecvd is -1. Then everything works well.
>
>
>
> I only used the following methods in the given order to transfer the data:
>
>
>
> vtkLiveInsituLink::InsituUpdate
>
> vtkSMSourceProxy::UpdatePipeline
>
> vtkLiveInsituLink::InsituPostProcess
>
>
>
>
>
> Are there further steps to perform or is there a way to check if the
> connection is still alive?
>
>
>
>
>
> Operating System: Windows 7, Visual Studio 2017
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
> Dipl.-Ing. Simon Klarmann
>
>
>
> *Bau- und Umweltingenieurwissenschaften*
> Technische Universit?t Darmstadt
>
> Fachgebiet Festk?rpermechanik
>
>
>
> Tel.: +49 6151 16 ? 22642 <+49%206151%201622642>
>
> Mail: klarmann at mechanik.tu-darmstadt.de
>
> Franziska-Braun-Stra?e 7
>
> Geb?ude L5|01, Raum 542
>
> 64287 Darmstadt
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/116e7866/attachment.html>

From andy.bauer at kitware.com  Thu Jul  6 11:18:59 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 6 Jul 2017 11:18:59 -0400
Subject: [Paraview] Integrating precompiled Catalyst into external
	projects
In-Reply-To: <HE1P194MB02340F861DEA0FC3B90DEF7D97D40@HE1P194MB0234.EURP194.PROD.OUTLOOK.COM>
References: <HE1P194MB02340F861DEA0FC3B90DEF7D97D40@HE1P194MB0234.EURP194.PROD.OUTLOOK.COM>
Message-ID: <CAMaOp+H8rT+h_MbctvvRj7M0i8wUA9XXd9SSzp2yF6ZHPjXNXw@mail.gmail.com>

Hi Jimmy,

If you're building Catalyst and want to install for others to link against
you will want to enable the PARAVIEW_INSTALL_DEVELOPMENT_FILES CMake option
when configuring.

It may be possible to have precompiled Catalyst installs with development
files available but there hasn't been a strong call for that to be done.

Cheers,
Andy

On Wed, Jul 5, 2017 at 8:08 AM, A . <super_achie at hotmail.com> wrote:

> Dear members,
>
>
> I would like to have Catalyst precompiled and ready for use for developers
> that want to work on my project. In this way they don't need to go through
> the procedure of installing dependencies and building Catalyst themselves
> (which currently takes longer than building my project...).
>
>
> The problem is the absolute paths that are used in all the .cmake files,
> such as ParaViewConfig.cmake and UseParaView.cmake (and all .cmake files
> they call on).
>
>
> I thought a "make install" would do the trick as normally it will copy all
> the essential files (system independent) to the CMAKE_INSTALL_PREFIX
> directory. But I cannot use the contents of the installation folder as the
> directory to point to when linking to Catalyst in my project (since there
> are no configuration files copied).
>
>
> I was doubtful to ask this question, because if it were possible, I would
> expect a precompiled Catalyst to be hosted on the ParaView download page.
> But out of curiosity I ask nonetheless; is it possible?
>
>
> Best,
>
> Jimmy
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/a72165f1/attachment.html>

From cory.quammen at kitware.com  Thu Jul  6 14:51:08 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 6 Jul 2017 14:51:08 -0400
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
 <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
 <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>
Message-ID: <CAB5Fpx5nueW1mznb=ftvmuARSnkpwXcrN9RaLnCy4BzWqeNg8w@mail.gmail.com>

Set the BUILD_SHARED_LIBS option to OFF.

HTH,
Cory

On Sun, Jul 2, 2017 at 11:56 AM, Ezhilmathi Krishnasamy
<ezhkr601 at student.liu.se> wrote:
> Hi,
>
> I am still having some problem with enabling the
> build shared libs. I am trying to install it on a Cray machine.
> I have already locally installed cmake and anaconda on their latest version.
>
> I am attaching here the image.
> Could any one tell me how to fix this issue
>
> Kind regards,
> Mathi
>
> On 2 July 2017 at 14:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
> wrote:
>>
>> Hi,
>>
>> I have almost build it, but getting this error:
>>
>>  CMake Warning (dev) at
>> /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
>> (add_library):
>>    ADD_LIBRARY called with SHARED option but the target platform does not
>>    support dynamic linking.  Building a STATIC library instead.  This may
>> lead
>>    to problems.
>>  Call Stack (most recent call first):
>>    /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
>> (find_package)
>>    superbuild/projects/qt5.system.cmake:1 (find_package)
>>    superbuild/cmake/SuperbuildMacros.cmake:640 (include)
>>    superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
>>  This warning is for project developers.  Use -Wno-dev to suppress it.
>>
>>
>>
>> On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se>
>> wrote:
>>>
>>> Thanks!
>>>
>>> Now it shows this kind of error
>>>
>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>> git fetch origin
>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>> git checkout v5.4.0
>>> HEAD is now at 7c510fe... Update to 5.4.0
>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>> git submodule update
>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>> cd ..
>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
>>> /cfs/klemming/nobackup/k/kriezh> cd build/
>>> /cfs/klemming/nobackup/k/kriezh/build> ccmake
>>> ../PARAVIEW_SUPER_BUILD/paraview-superbuild/
>>>
>>>
>>>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>>    The build tree appears to be inside of the git repository located at
>>>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
>>>    superbuild applies patches to projects and is not supported.  Please
>>>    relocate the build tree to a directory which is not under a git
>>> repository.
>>>  Call Stack (most recent call first):
>>>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>>
>>>
>>>
>>>
>>> On 2 July 2017 at 14:03, Patrick B?gou
>>> <Patrick.Begou at legi.grenoble-inp.fr> wrote:
>>>>
>>>> Like you, I got this error some months ago when trying to build paraview
>>>> superbuild:
>>>>
>>>> error: unknown option `is-ancestor'
>>>>
>>>> It was my git version wich was too old. May be try to compile a more up
>>>> to date version of git in your home and set the path to access it.
>>>>
>>>> I have installed git from
>>>> https://www.kernel.org/pub/software/scm/git/git-2.12.2.tar.xz
>>>>
>>>> Patrick
>>>>
>>>> Ezhilmathi Krishnasamy a ?crit :
>>>>
>>>> Hi,
>>>>
>>>> I have followed these instructions. I am trying to install it where I am
>>>> not a root user.
>>>> Can someone help to fix this issue.
>>>>
>>>>  git clone --recursive
>>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
>>>>  cd paraview-superbuild
>>>>  git fetch origin # ensure you have the latest state from the main repo
>>>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>>>>  git submodule update
>>>>
>>>>  cd ..
>>>>  mkdir build
>>>>  cd build
>>>>  ccmake ../paraview-superbuild
>>>>
>>>> Kind regards,
>>>> Mathi
>>>>
>>>>
>>>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy
>>>> <ezhkr601 at student.liu.se> wrote:
>>>>>
>>>>> Hi Thanks!
>>>>>
>>>>> When I try to install Paraview,  I am getting the following error.
>>>>> Could some one please tell me how to fix this issue.
>>>>> I am trying to install the Paraview on a super computer to use it
>>>>> for remote rendering without using the GUI,  like with mesa support.
>>>>>
>>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> git
>>>>> clone --recursive
>>>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
>>>>> Cloning into 'paraview-superbuild'...
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> remote: Counting objects: 6723, done.
>>>>> remote: Compressing objects: 100% (2459/2459), done.
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>>>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>>>>> Resolving deltas: 100% (4451/4451), done.
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> Checking out files: 100% (196/196), done.
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> Submodule 'superbuild'
>>>>> (https://gitlab.kitware.com/paraview/common-superbuild.git) registered for
>>>>> path 'superbuild'
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> Cloning into 'superbuild'...
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> remote: Counting objects: 6752, done.
>>>>> remote: Compressing objects: 100% (2235/2235), done.
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>>>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>>>>> Resolving deltas: 100% (4505/4505), done.
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> Submodule path 'superbuild': checked out
>>>>> '8f357bb5bf35419c210b3f9e0adbc9df08f565f2'
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission denied
>>>>>
>>>>>
>>>>>
>>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>>>>> cmake .
>>>>> -- The C compiler identification is Intel 14.0.4.20140805
>>>>> -- The CXX compiler identification is Intel 14.0.4.20140805
>>>>> -- Cray Programming Environment 2.2.1 C
>>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- works
>>>>> -- Detecting C compiler ABI info
>>>>> -- Detecting C compiler ABI info - done
>>>>> -- Detecting C compile features
>>>>> -- Detecting C compile features - done
>>>>> -- Cray Programming Environment 2.2.1 CXX
>>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC --
>>>>> works
>>>>> -- Detecting CXX compiler ABI info
>>>>> -- Detecting CXX compiler ABI info - done
>>>>> -- Detecting CXX compile features
>>>>> -- Detecting CXX compile features - done
>>>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242 (message):
>>>>>   Failed to determine if the common superbuild is an old checkout.  The
>>>>>   common superbuild may be out of date, but cannot be verified.:
>>>>> warning:
>>>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>> Permission
>>>>>   denied
>>>>>
>>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>>   Permission denied
>>>>>
>>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>>   Permission denied
>>>>>
>>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>>>>>   Permission denied
>>>>>
>>>>>   error: unknown option `is-ancestor'
>>>>>
>>>>>   usage: git merge-base [-a|--all] <commit> <commit>...
>>>>>
>>>>>      or: git merge-base [-a|--all] --octopus <commit>...
>>>>>      or: git merge-base --independent <commit>...
>>>>>
>>>>>
>>>>>
>>>>>       -a, --all             output all common ancestors
>>>>>       --octopus             find ancestors for a single n-way merge
>>>>>       --independent         list revs not reachable from others
>>>>> Call Stack (most recent call first):
>>>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>>>>>
>>>>>
>>>>> -- Check size of void*
>>>>> -- Check size of void* - done
>>>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
>>>>> -- Determined source version for paraview: 5.4.0
>>>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>>>>>   The build tree appears to be inside of the git repository located at
>>>>>
>>>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild.
>>>>>   This interferes with the way the superbuild applies patches to
>>>>> projects and
>>>>>   is not supported.  Please relocate the build tree to a directory
>>>>> which is
>>>>>   not under a git repository.
>>>>> Call Stack (most recent call first):
>>>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>>>>>
>>>>>
>>>>> -- Configuring incomplete, errors occurred!
>>>>> See also
>>>>> "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild/CMakeFiles/CMakeOutput.log".
>>>>>
>>>>>
>>>>> Kind regards,
>>>>> Mathi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com>
>>>>> wrote:
>>>>>>
>>>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>>>>>> <ezhkr601 at student.liu.se> wrote:
>>>>>> > Hi,
>>>>>> >
>>>>>> > Can anyone please give me some instructions how to Paraview
>>>>>> > Superbuid
>>>>>> > to install and use them with out using the GUI (using the python
>>>>>> > script to
>>>>>> > render the images on the cluster or super computer).
>>>>>> >
>>>>>> > I see there are some instructions in here:
>>>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>>>>>> >
>>>>>> > But I could not find any build instructions.
>>>>>>
>>>>>> Take a look again, that page includes the README.md file contents
>>>>>> which includes build instructions.
>>>>>>
>>>>>> To build without the GUI, you should just need to set the options
>>>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>>>>>> ENABLE_python to ON.
>>>>>>
>>>>>> Best regards,
>>>>>> Cory
>>>>>>
>>>>>> >
>>>>>> > Kind regards,
>>>>>> > Mathi
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > 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&D 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
>>>>
>>>>
>>>
>>
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Thu Jul  6 15:38:03 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 6 Jul 2017 15:38:03 -0400
Subject: [Paraview] Using Value of Variable At Point in Calculator Filter
In-Reply-To: <8cb746b3-e456-a1eb-1194-038f51269a48@ucmerced.edu>
References: <8cb746b3-e456-a1eb-1194-038f51269a48@ucmerced.edu>
Message-ID: <CAB5Fpx6hvCvcq=UU3_6P3DJHdBa3rv7qOdqzDZRs+51CwG4P=Q@mail.gmail.com>

On Mon, Jul 3, 2017 at 9:01 PM, Jeremias Gonzalez
<jgonzalez49 at ucmerced.edu> wrote:
> Hi, I've been trying to figure out, in Paraview, how to use the value of a
> variable at a point in the calculator filter over a geometry. So, for
> example, I have 3 vtk files of a cube geometry with a scalar and vector
> field (x,y,z components) as data sets. I create a gradient filter for each
> one of the vector components, then use the append attributes filter to
> combine the gradients into one object, then use the calculator filter to
> compute some quantity using the gradients as well as {the value of a vector
> field component of each vtk in the middle of the cube} and plot the result
> over the cubic geometry, maybe take a slice of that cube at the end. I have
> some roadblocks that prevent me from doing this in a less manual,
> straightforward fashion:
>
> 1. I do not see a command in the calculator filter like
> EvaluateAtPoint(myvectorfieldxcomponentvtk1,(x=0,y=0,z=0.5)) to grab the
> value of the x component of the vector field from vtk1 at point (0,0,0.5) in
> Cartesian coordinates and use it in some quantity like
> gradientx*5*EvaluateAtPoint(...) which would be evaluated over the entire
> cubic geometry, but always use the value of that point in the middle. I have
> used this sort of thing before in a program called COMSOL, which possesses
> such a feature in the Scoped Evaluation list called at3_geometry, among many
> other variations.

Indeed, ParaView does not have such a command in the Calculator filter.

> 2. Even if there was a command like in #1, the append attributes command
> doesn't seem to respect the different sources of the vector field, so I see
> only one vector field in the resulting array (by contrast, I can name the
> gradients of the vector field components uniquely in each of the filters
> that outputs them, and the append attributes filter shows three distinct
> batches of gradients from each filter I applied to each vtk).

If I understand you correctly, you are describing how only one of the
data arrays from the inputs with the same name is copied to the
output. That is unfortunately the behavior in ParaView 5.4 and prior.
The good news is that the next version of ParaView should instead copy
all the data arrays and mangle the names of the vector field so that
you can have all three distinct vector arrays in the output of the
Append Attribute filter when you do this. See

https://gitlab.kitware.com/paraview/paraview/merge_requests/1639

which added this feature.

> 3. I tried to create a probe at the location I need, but the geometry it
> produces is a single point and thus using it either {directly with append
> attributes to the other gradient results} or {with a calculator filter first
> to get only the quantity I want instead of the scalar field and the vector
> fields evaluated at that point and then use the append attributes command}
> doesn't work because the append attributes apparently uses only the
> overlapping geometry, which of course is only the one point.

Good thinking using the Probe filter (see below), but yep, this won't
quite work.

> 4. I tried to use group datasets instead, thinking maybe it would just take
> the value I make in the calculator filter from the probe location filter and
> use it in the final calculator filter, but it just throws a bunch of errors
> which I assume again stem from the mismatch of geometry.

The Group datasets filter will create a multi block data set, which
won't exactly help you.

> 5. I had an idea to maybe just clone each of the original vtks to get the
> geometry I need in a new array, and then somehow set all the datapoints in
> each one to the value I get from the probe location filter, but this would
> not only again encounter the problem in #2 with the nonunique naming, but I
> also do not know how to edit the individual data points in the file (I see
> an inkling of this idea in the blog post here:
> https://blog.kitware.com/zero-copy-arrays/ but it's quite beyond my current
> level of understanding of Paraview).

This would also be wasteful in terms of memory usage.

> The current alternative (that definitely works) is to just manually copy the
> value I get from {the probe location filter or plot over line filter or
> something like that } into the final calculator filter, but I'd have to do
> that for every one of the batches of 3 vtk files I get, which is going to
> get very large when I start varying my more complicated geometry with
> parametric sweeps (I also need to figure out how to automate the process of
> outputting the slice I take at the end, but one problem at a time! I welcome
> any suggestions on this front).

I would look at using the Python scripting capabilities within
ParaView for this. You can write a Python script and run it with
pvpython - this is especially useful for running an analysis in a
batch fashion. Within your script you use the Probe filter to get the
data value at a particular location and add that value to some
Calculator expression as needed. Here's a quick example:

from paraview.simple import *

data = FindSource('MyDataSource')
probe = ProbeLocation(Input=data, ProbeType='Fixed Radius Point Source')
probe.ProbeType.Center = [1.0, 0.0, 0.0]
probe.UpdatePipeline()
probePoint = paraview.servermanager.Fetch(probe)
value_at_probe = probePoint.GetPointData().GetArray('my array name').GetValue(0)

calculator_expression = #... value_at_probe + other expression
c1 = Calculator(Input=appendedData)
c1.Function = calculator_expression
...


I hope that helps get you started. Let us know if you have other
questions about the scripting.

Thanks,
Cory

> _______________________________________________
> 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&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Thu Jul  6 15:53:45 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 6 Jul 2017 15:53:45 -0400
Subject: [Paraview] Two issues with time-dependent data
In-Reply-To: <5ea6aa0d2a6e48d38a75f2d62c3d5d3b@rwthex-s1-b.rwth-ad.de>
References: <5ea6aa0d2a6e48d38a75f2d62c3d5d3b@rwthex-s1-b.rwth-ad.de>
Message-ID: <CAB5Fpx6Oh7d5gGYYhFrZZ5_NkmwHY+4nohVdzpeQgrNKpGnRdQ@mail.gmail.com>

[snip]
> 1.       In RequestInformation of the filter, we provide the pipeline just
> with a TIME_RANGE. This is so far working without problem, we can go through
> the range by Sequence or Real Time. When running the Animation as a loop
> though, we encounter the issue that the beginning and the end of the time
> range are both displayed. Since our data is periodic and the TIME_RANGE is a
> cycle duration, these two steps are identical. As you can guess, it is not
> desired to see the same step two times right behind each other. Is there a
> way to prevent this behaviour?

Can you just set the upper end of the TIME_RANGE to one timestep
before what you have now? In other words, instead of having the first
and last timesteps provide the same data, end the TIME_RANGE earlier
by one timestep. That will prevent the doubling of the timestep when
the animation resets.

> 2.       When we save the filter in a state file and load it afterwards with
> a different dataset, the displayed time range in ParaView shows the wrong
> data. Although in RequestInformation the correct TIME_RANGE of the new
> dataset is set to the pipeline, ParaView/the Animation View still shows the
> time data of the state file. It only changes, if after loading the state
> file, a different TIME_RANGE with different values is set in
> RequestInformation. We can live with this issue, but maybe it is a bug that
> is easy to fix.

I'm not sure about this one. Maybe someone else can chime in.

Thanks,
Cory

>
>
> We will be grateful for any advice or suggestion!
>
>
>
> Thanks in advance and cheers,
>
> Heinrich
>
>
>
> --
>
> Dipl.-Ing. Heinrich Schuld
>
> Institute of Jet Propulsion and Turbomachinery
>
> RWTH Aachen
>
> Templergraben 55
>
> 52062 Aachen
>
> Germany
>
>
>
> Tel:         +49 241 80 99652
>
> Fax:        +49 241 80 92229
>
> E-Mail:   schuld at ist.rwth-aachen.de
>
> www:     http://www.ist.rwth-aachen.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
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Thu Jul  6 16:22:36 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 6 Jul 2017 16:22:36 -0400
Subject: [Paraview] Animation and Filter Help with CSV/VTP XYZ Data
In-Reply-To: <b842808a-75bd-4606-9833-09d34a88318d@Spark>
References: <b842808a-75bd-4606-9833-09d34a88318d@Spark>
Message-ID: <CAB5Fpx40aJdb-vTjkD0v6CFMC3K0p3UdRw4rUxUnYtXRQn3dkw@mail.gmail.com>

On Thu, Jun 29, 2017 at 6:21 PM, Maxwell Dausch <mdausc2 at uic.edu> wrote:
> Hello,
>  I am very new to using paraview and have had a couple questions that I am
> having trouble finding the resources needed to help my situation. I've been
> searching the mailing list and other forums for the past week or so and have
> not had much progress.
>
> I am trying to figure out how to
> 1) Animate a series of points that were obtained by tracking a person's
> movement, and animate it in a way that would play back the moment path, I
> would like to animate it by the order the points are in with a set time
> interval in-between each point if possible. In this situation there are
> multiple different trackers which is why I also need a bit of guidance on
> part 2, so the data just doesn?t get all mixed up together.

First thing first: you'll want to split your points up into several
CSV files, one for each time step. In each of the CSV files, you will
list the point positions and the ID, e.g.

path1.csv contains the first time step:

"ID","X","Y","Z"
1,0.0,1.0,0.0
2,1.0,1.1,1.2


path2.csv contains the second time step:

"ID","X","Y","Z"
1,0.0,1.0,0.0
2,1.0,1.2,1.3

and so one.

To animate these files, you will load the entire list of CSV files
through the Open File dialog by navigating to the location of these
files and selecting the group of files labeled "path..csv". Because
the data you are loading is tabular, it will open up a SpreadSheet
view showing you the raw tables. You can close this view as you won't
be needing it. Click back on the default 3D RenderView and then select
the path* source in the Pipeline Browser. To turn these into points,
use the TableToPoints filter, setting the "X Column" property to "X",
the "Y Column" to "Y", and the "Z Column" to "Z".

Now, you'll need to show the points, which aren't visible at this
point. You can add a Glyph filter to display the points with some
geometry. The "Glyph Type" will default to "Arrow", but you can change
that to "Sphere" or whatever your favorite shape is.

> 2) Color points by a source id for the movement tracker assigned to the
> point, i.e. id?s 1-5 would be blue, 6-10 would be red and so on, I've only
> been able to color the whole table of points one color and not sure how to
> proceed.

Coloring by ID is pretty easy. In the tool bar, color the glyphs by
the "ID" array. Open up the "Color Map Editor" and check the
"Interpret Values As Categories" box. Under "Annotations", click on
the icon with the folder and heart ("Choose preset"). Pick one of the
color map presets for categorical data. Next, click on the toolbutton
just above that with the red, yellow, and blue rectangles ("Add active
values from selected source"). This will assign the ID values to the
colors in the color map.

I hope that gets you going,
Cory

> Currently I am working with a csv (that I also have been able to convert to
> an .vtp file if that is able to help the situation at all) that contains a
> source Id for the tracker as well as the points xyz.
>
> Ive been trying to mess around with the programmable filters ( I don?t have
> too much experience with python though ), but I am unsure on how to access
> the other attributes of the data(the source id) and thus when I try link the
> points with a line, it jumps from one path to another and in return it mixes
> the movement paths.
>
> I?d appreciate any guidance with this, as I am at wits ends trying to figure
> everything out. Especially when Ive only been able to find solid objects
> being animated and not too much point data being worked with when searching
> for any possible solutions to the problem. If it might be of any help I
> could upload one of the csv files that we have generated.
>
> Thanks again
> -Max
>
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Thu Jul  6 16:54:47 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 6 Jul 2017 16:54:47 -0400
Subject: [Paraview] Paraview segfault on (orthographic) slice view
In-Reply-To: <6810150.cDZEUX3Ych@mu15am33074-linux>
References: <6810150.cDZEUX3Ych@mu15am33074-linux>
Message-ID: <CAB5Fpx4ZbeTiRpWi7GOouULCmJpT1+ZVcJpVz0qz9Riunf6Vxw@mail.gmail.com>

On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:
> Hi all,
>
> I've had a serious issue since last week now:
>
> Whenever I visualize a polygonal Mesh in the Slice View or orthogonal slice
> view:
>
> - in slice view: Paraview crashes as soon as I click on any of the slice
> cursors to grab it to another position.
>
> - in orthographic slice view: I can scroll in one direction on each of the
> slice views, however, when I scroll in the second direction, Paraview
> crashes.

I could not reproduce either the "Slice View" crash or "Orthographic
Slice View" crash you report in ParaView 5.4 on macOS.

> Version 5.3 compiled from source was working fine until I hit this error, I
> suspected a package upgrade to be the source of the problem, and downgraded
> Mesa (17.1.2-1 -> 17.1.1-1) and the Intel driver on laptop (17.1.2-1 ->
> 17.1.1-1) however, this did not help, and I am sure Paraview 5.3 used to
> work on those versions of mesa and Intel driver.

Judging by the stack traces you included (very helpful, by the way)
this looks more like a memory access problem within ParaView. That
problem seems to have been fixed in ParaView 5.4, though.

HTH,
Cory

> Systems:
>
> -laptop (Archlinux) using Intel IGP or Nvidia discrete GPU using open-source
> driver (DRI_PRIME). Crash can be reproduced on both GPU.
>
> -desktop (Majaro, Arch based): using Nvidia GPU, proprietary driver.
>
>
>
> Please find attached the gdb traces. I just started Paraview with each GPU,
> created a box, created a orthographic slice view, and tried to scroll.
>
>
>
> Did anyone else observe that ?
>
>
>
> Best regards,
> --
>
> Dorian Vogel
>
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.

From stephane at fujielectric.com  Thu Jul  6 20:35:13 2017
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg5LiA5L+h?=)
Date: Fri, 7 Jul 2017 09:35:13 +0900
Subject: [Paraview] [EXTERNAL] Re: long animations are freezing halfway
	through
In-Reply-To: <CADHSJjBKvXkhD+BGi=ggGQti-dvoi_NzZ3LFDw20D5310HBTUg@mail.gmail.com>
References: <CA+Y385yiZmpvOg_KUzdRzjwpuGka-xDqv1YZrkuEakv2CTLWbA@mail.gmail.com>
 <CADHSJjA2H=mfE48w05TXOSzKfs912gsz2CL7E=mvhOxPNyq5FA@mail.gmail.com>
 <575e4d66cec04221a06d846344dd5e6d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjA1=xKJvAE2ixxJ_UWgR-fmzrf_Fv3L5WLn3C-gFRs45w@mail.gmail.com>
 <CADHSJjBKvXkhD+BGi=ggGQti-dvoi_NzZ3LFDw20D5310HBTUg@mail.gmail.com>
Message-ID: <CADLMsL63gxoCOh80Q+B4yQ18JmyZU51M5A4MN-ygr_e5vaNioA@mail.gmail.com>

Hello,

I just want to  add that it's happening in both 5.3 and 5.4

Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394


On Thu, Jul 6, 2017 at 11:14 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Just to give an update, while I couldn't reproduce the issue with Giles
> example, I was able to do it with another customer. It's quite a curious
> thing indeed! Still figuring out where to begin to debug this -- the fact
> that it's a Windows only thing makes it even more tedious -- but will keep
> you posted.
>
> Utkarsh
>
> On Fri, Jun 23, 2017 at 12:08 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Alan,
>>
>> I am discussing with Giles off line. Will keep you posted.
>>
>> Utkarsh
>>
>> On Fri, Jun 23, 2017 at 12:05 PM, Scott, W Alan <wascott at sandia.gov>
>> wrote:
>> > I have another user with this complaint.  I have not been able to
>> replicate it.
>> >
>> > Are you using either opacity or volume rendering?
>> >
>> > Would you be able to pass the data files to Kitware?
>> >
>> > Alan
>> >
>> >> -----Original Message-----
>> >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
>> >> Utkarsh Ayachit
>> >> Sent: Friday, June 23, 2017 7:07 AM
>> >> To: Richardson CFD <garcfd at gmail.com>
>> >> Cc: ParaView <paraview at paraview.org>
>> >> Subject: [EXTERNAL] Re: [Paraview] long animations are freezing halfway
>> >> through
>> >>
>> >> Giles,
>> >>
>> >> What OS is this on?
>> >>
>> >> Utkarsh
>> >>
>> >> On Fri, Jun 23, 2017 at 8:59 AM, Richardson CFD <garcfd at gmail.com>
>> wrote:
>> >> > I have been having trouble creating longer animations (150 frames)
>> >> > from larger data files (1million cells). The animation works fine
>> >> > initially but then freezes up about half way through the avi file -
>> >> > displaying just a constant unchanging image. Streamlines seems to
>> work
>> >> > fine, but velocity contours (attached) is the one causing problems. I
>> >> > am having to create the animation in 2 parts, creating 2 seperate avi
>> >> > file and then join them after.
>> >> >
>> >> > Any suggestions or similar experience please let me know. Regards
>> Giles.
>> >> >
>> >> > --
>> >> > Richardson CFD
>> >> > http://richardsoncfd.weebly.com
>> >> >
>> >> > _______________________________________________
>> >> > 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/opensou
> rce/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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/bf0e4efc/attachment.html>

From Schuld at ist.rwth-aachen.de  Fri Jul  7 03:34:38 2017
From: Schuld at ist.rwth-aachen.de (Schuld, Heinrich)
Date: Fri, 7 Jul 2017 07:34:38 +0000
Subject: [Paraview] Two issues with time-dependent data
In-Reply-To: <CAB5Fpx6Oh7d5gGYYhFrZZ5_NkmwHY+4nohVdzpeQgrNKpGnRdQ@mail.gmail.com>
References: <5ea6aa0d2a6e48d38a75f2d62c3d5d3b@rwthex-s1-b.rwth-ad.de>
 <CAB5Fpx6Oh7d5gGYYhFrZZ5_NkmwHY+4nohVdzpeQgrNKpGnRdQ@mail.gmail.com>
Message-ID: <27d4fb8d5d2c4004b78b164ee43b08d8@rwthex-s1-b.rwth-ad.de>

Thanks Cory for your idea. The problem is, that I would have to set the end of the TIME_RANGE dependently on the timesteps requested by ParaView. Otherwise the delta t between timesteps will not be equal. I could modify my filter so that the user has to select the number of timesteps in it. But I was hoping to use the already present functionalities of ParaView.

Cheers,
Heinrich


-----Urspr?ngliche Nachricht-----
Von: Cory Quammen [mailto:cory.quammen at kitware.com] 
Gesendet: Donnerstag, 6. Juli 2017 21:54
An: Schuld, Heinrich <Schuld at ist.rwth-aachen.de>
Cc: paraview at paraview.org
Betreff: Re: [Paraview] Two issues with time-dependent data

[snip]
> 1.       In RequestInformation of the filter, we provide the pipeline just
> with a TIME_RANGE. This is so far working without problem, we can go through
> the range by Sequence or Real Time. When running the Animation as a loop
> though, we encounter the issue that the beginning and the end of the time
> range are both displayed. Since our data is periodic and the TIME_RANGE is a
> cycle duration, these two steps are identical. As you can guess, it is not
> desired to see the same step two times right behind each other. Is there a
> way to prevent this behaviour?

Can you just set the upper end of the TIME_RANGE to one timestep
before what you have now? In other words, instead of having the first
and last timesteps provide the same data, end the TIME_RANGE earlier
by one timestep. That will prevent the doubling of the timestep when
the animation resets.

> 2.       When we save the filter in a state file and load it afterwards with
> a different dataset, the displayed time range in ParaView shows the wrong
> data. Although in RequestInformation the correct TIME_RANGE of the new
> dataset is set to the pipeline, ParaView/the Animation View still shows the
> time data of the state file. It only changes, if after loading the state
> file, a different TIME_RANGE with different values is set in
> RequestInformation. We can live with this issue, but maybe it is a bug that
> is easy to fix.

I'm not sure about this one. Maybe someone else can chime in.

Thanks,
Cory

>
>
> We will be grateful for any advice or suggestion!
>
>
>
> Thanks in advance and cheers,
>
> Heinrich
>
>
>
> --
>
> Dipl.-Ing. Heinrich Schuld
>
> Institute of Jet Propulsion and Turbomachinery
>
> RWTH Aachen
>
> Templergraben 55
>
> 52062 Aachen
>
> Germany
>
>
>
> Tel:         +49 241 80 99652
>
> Fax:        +49 241 80 92229
>
> E-Mail:   schuld at ist.rwth-aachen.de
>
> www:     http://www.ist.rwth-aachen.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
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.

From dorian.vogel at fhnw.ch  Fri Jul  7 04:33:30 2017
From: dorian.vogel at fhnw.ch (Vogel Dorian)
Date: Fri, 7 Jul 2017 08:33:30 +0000
Subject: [Paraview] Paraview segfault on (orthographic) slice view
In-Reply-To: <CAB5Fpx4ZbeTiRpWi7GOouULCmJpT1+ZVcJpVz0qz9Riunf6Vxw@mail.gmail.com>
References: <6810150.cDZEUX3Ych@mu15am33074-linux>
 <CAB5Fpx4ZbeTiRpWi7GOouULCmJpT1+ZVcJpVz0qz9Riunf6Vxw@mail.gmail.com>
Message-ID: <2896024.Mug0BS0NRY@mu15am33074-linux>

Hello Cory,

Thanks for the follow-up.



Unfortunately I do still experience this issue, I gathered a bit more information on the behavior of the issue:

Still using a 1x1x1 @(0,0,0) box:

-open second layout as tab

-open orthographic sliceview

-I can scroll on all slice views but ONLY in one direction. As soon as I scroll in the other direction on any of the views, Paraview crashes.



==> this only appends on Polygonal Meshes: If I apply the AppendDatasets filter (outputting an Unstructured Grid) to the same box, everything seems to work as expected.

This is pretty much the Hack I used for my data, convert all the object that I wanted to slice to unstructured grid. While not optimal it does the job.



Best,

--

Dorian Vogel

On Thursday, July 6, 2017 10:54:47 PM CEST Cory Quammen wrote:

> On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:

> > Hi all,

> >

> > I've had a serious issue since last week now:

> >

> > Whenever I visualize a polygonal Mesh in the Slice View or orthogonal

> > slice

> > view:

> >

> > - in slice view: Paraview crashes as soon as I click on any of the slice

> > cursors to grab it to another position.

> >

> > - in orthographic slice view: I can scroll in one direction on each of the

> > slice views, however, when I scroll in the second direction, Paraview

> > crashes.

>

> I could not reproduce either the "Slice View" crash or "Orthographic

> Slice View" crash you report in ParaView 5.4 on macOS.

>

> > Version 5.3 compiled from source was working fine until I hit this error,

> > I

> > suspected a package upgrade to be the source of the problem, and

> > downgraded

> > Mesa (17.1.2-1 -> 17.1.1-1) and the Intel driver on laptop (17.1.2-1 ->

> > 17.1.1-1) however, this did not help, and I am sure Paraview 5.3 used to

> > work on those versions of mesa and Intel driver.

>

> Judging by the stack traces you included (very helpful, by the way)

> this looks more like a memory access problem within ParaView. That

> problem seems to have been fixed in ParaView 5.4, though.

>

> HTH,

> Cory

>

> > Systems:

> >

> > -laptop (Archlinux) using Intel IGP or Nvidia discrete GPU using

> > open-source driver (DRI_PRIME). Crash can be reproduced on both GPU.

> >

> > -desktop (Majaro, Arch based): using Nvidia GPU, proprietary driver.

> >

> >

> >

> > Please find attached the gdb traces. I just started Paraview with each

> > GPU,

> > created a box, created a orthographic slice view, and tried to scroll.

> >

> >

> >

> > Did anyone else observe that ?

> >

> >

> >

> > Best regards,

> > --

> >

> > Dorian Vogel

> >

> >

> > _______________________________________________

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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/98699a68/attachment.html>

From lapham1996 at gmail.com  Fri Jul  7 06:51:20 2017
From: lapham1996 at gmail.com (Rebekah L)
Date: Fri, 7 Jul 2017 11:51:20 +0100
Subject: [Paraview] Paraview python - loop to run through multiple files
Message-ID: <CA+h7E46rD6xXFCM6JgN_ydrdnrM_w2421UGbpwHY8WLP_jYPXQ@mail.gmail.com>

Hey :)
I'm trying to script some code so that I can load a file in and then
WriteImage and then I want this to loop through multiple files so I don't
have to change the code each time for the new path. My problem is that
paraview won't recognise a path unless it is the exact path, so I can't get
it to change automatically. Any help would be greatly appreciated. Here is
my current code:

sso2_load_python
from paraview.simple import *
fname = '/home/sophy/Desktop'
#I put the files on the desktop so the path was shorter
filenames = ["c1", "c2"]
for x in filenames:
             Loadstate("/home/sophy/Desktop/x.pvsm")
      WriteImage("/home/sophy/Desktop/image.png")

#the previous two lines have the four space indent but my phone won't let
me type it like that



Thanks - Rebekah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/81bd3db9/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Fri Jul  7 07:30:17 2017
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Fri, 7 Jul 2017 14:30:17 +0300
Subject: [Paraview] multiple visualization pipeline at a time with
 co-processing
In-Reply-To: <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
 <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
 <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>
Message-ID: <e707d3dd-870b-bc30-6e80-7922a6c0b70a@be.itu.edu.tr>

Hi Andy,

Strange! To test the idea and eliminate other problems i am using same 
script twice with little mods (i just changed the name of the output png 
file). So, if i pass script_1.py and script_2.py to the model, it gives 
warning like before and creates output just for second script 
(script_2.py). If i pass only one of them then the code is working 
without any problem and produces desired output.

Thanks,
Regards,

--ufuk


On 06/07/2017 18:09, Andy Bauer wrote:
> Hi Ufuk,
>
> I'm guessing the issue is that the calls to Catalyst are not 
> consistent. Could you share your Python scripts? Also, did you modify 
> them manually?
>
> I tried with PV 5.3. with 
> the ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/ example with 
> the attached scripts simultaneously by running with "./CxxFullExample 
> doubleoutputs.py output3.py image11.py" and got the correct output and 
> no warnings.
>
> Cheers,
> Andy
>
> On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Hi Andy,
>
>     I tested you suggestion about using multiple script in
>     co-processing. In this case, i used following code in the adaptor
>     side to add multiple pipeline
>
>           for (int i = 0; i < *nscript; i++) {
>             pipeline->Initialize(pythonScriptNames[i]);
>             g_coprocessor->AddPipeline(pipeline);
>           }
>
>     When i run the simulation, i am getting following warning
>
>     Warning: In
>     /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx,
>     line 66
>     vtkPVTrivialProducer (0x13816760): New time step is not after last
>     time step.
>
>     the output seems not correct and it is zoom out version of second
>     pipeline (png file). The first pipeline is not even triggered. Do
>     i missing something in here? BTW, i am using PV 5.3.
>
>     Thanks,
>
>     --ufuk
>
>
>     On 16/05/2017 16:08, Andy Bauer wrote:
>>     Hi Ufuk,
>>
>>     If you create a vtkCPythonScriptPipeline, when you initialize it
>>     with the script file name (which has to be done on each process)
>>     everything will be taken care of with respect to broadcasting the
>>     file contents from process 0 to the others. We aren't
>>     sophisticated enough to parse the Python script to see if it
>>     imports other scripts that are not part of ParaView (e.g.
>>     paraview.simple) or Python (e.g. sys). That is why I recommended
>>     the first approach as opposed to the second approach above.
>>     Depending on the compute platform and how many MPI processes are
>>     in the run the difference may be negligible but having 100K
>>     processes or more trying to access the same file can seriously
>>     slow down an HPC machine.
>>
>>     Cheers,
>>     Andy
>>
>>     On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE)
>>     <u.utku.turuncoglu at be.itu.edu.tr
>>     <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>>
>>         Thanks Andy. That is exactly what i am looking for. The
>>         broadcasting mechanism is not clear to me yet. Do i need to
>>         broadcast only the file names? Anyway, i will try to
>>         implement it and see what is going on there.
>>
>>         Thanks again,
>>         Regards,
>>
>>         --ufuk
>>
>>
>>         On 16/05/2017 14:58, Andy Bauer wrote:
>>>         Hi Ufuk,
>>>
>>>         Unless I'm not understanding your question correctly, I
>>>         think you can get what you want by adding in multiple
>>>         vtkCPPythonScriptPipelines to your vtkCPProcessor object in
>>>         your adaptor. Alternatively if you want to have a single,
>>>         master Catalyst script handling other Catalyst scripts you
>>>         can do something like the following:
>>>         ================
>>>         import script_a
>>>         import script_b
>>>         import script_c
>>>
>>>         def RequestDataDescription(datadescription):
>>>         script_a.RequestDataDescription(datadescription)
>>>         script_b.RequestDataDescription(datadescription)
>>>         script_c.RequestDataDescription(datadescription)
>>>
>>>         def DoCoProcessing(datadescription):
>>>         script_a.DoCoProcessing(datadescription)
>>>         script_b.DoCoProcessing(datadescription)
>>>         script_c.DoCoProcessing(datadescription)
>>>         ===================
>>>
>>>         The first way is the recommended way though as that should
>>>         be more efficient by having process 0 read the scripts and
>>>         broadcasting the script contents to the other  processes for
>>>         use. The second method will only do that for the master script.
>>>
>>>         Please let me know if this doesn't answer your question.
>>>
>>>         Cheers,
>>>         Andy
>>>
>>>         On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE)
>>>         <u.utku.turuncoglu at be.itu.edu.tr
>>>         <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>>>
>>>             Hi All,
>>>
>>>             I just wonder that is it possible to trigger multiple
>>>             visualization pipeline in the same time with
>>>             co-processing. The co-processing script generator plugin
>>>             mainly outputs only single pipeline at a time and that
>>>             is fine but what about combining multiple Python script
>>>             (generated by plugin) using higher level Python script
>>>             to trigger multiple pipelines. So, i think that this
>>>             will be much efficient way to look at different part of
>>>             the data without writing to the disk. I am not sure but
>>>             somebody else might do it before.
>>>
>>>             Regards,
>>>
>>>             --ufuk
>>>
>>>             _______________________________________________
>>>             Powered by www.kitware.com <http://www.kitware.com>
>>>
>>>             Visit other Kitware open-source projects at
>>>             http://www.kitware.com/opensource/opensource.html
>>>             <http://www.kitware.com/opensource/opensource.html>
>>>
>>>             Please keep messages on-topic and check the ParaView
>>>             Wiki at: http://paraview.org/Wiki/ParaView
>>>             <http://paraview.org/Wiki/ParaView>
>>>
>>>             Search the list archives at:
>>>             http://markmail.org/search/?q=ParaView
>>>             <http://markmail.org/search/?q=ParaView>
>>>
>>>             Follow this link to subscribe/unsubscribe:
>>>             http://public.kitware.com/mailman/listinfo/paraview
>>>             <http://public.kitware.com/mailman/listinfo/paraview>
>>>
>>>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: script_1.py
Type: text/x-python-script
Size: 6893 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: script_2.py
Type: text/x-python-script
Size: 6893 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/467cfd26/attachment-0001.bin>

From cory.quammen at kitware.com  Fri Jul  7 09:16:55 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 7 Jul 2017 09:16:55 -0400
Subject: [Paraview] Paraview segfault on (orthographic) slice view
In-Reply-To: <2896024.Mug0BS0NRY@mu15am33074-linux>
References: <6810150.cDZEUX3Ych@mu15am33074-linux>
 <CAB5Fpx4ZbeTiRpWi7GOouULCmJpT1+ZVcJpVz0qz9Riunf6Vxw@mail.gmail.com>
 <2896024.Mug0BS0NRY@mu15am33074-linux>
Message-ID: <CAB5Fpx5LgiUP+mOLz6O3q=M5SV0tK9FEh878-KrkoRyGab6CRw@mail.gmail.com>

Dorian,

Thanks for the followup and workaround. If you could share the data
set with me or tell me how to create it with a ParaView source, I can
take a closer look.

Thanks,
Cory

On Fri, Jul 7, 2017 at 4:33 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:
> Hello Cory,
>
> Thanks for the follow-up.
>
>
>
> Unfortunately I do still experience this issue, I gathered a bit more
> information on the behavior of the issue:
>
> Still using a 1x1x1 @(0,0,0) box:
>
> -open second layout as tab
>
> -open orthographic sliceview
>
> -I can scroll on all slice views but ONLY in one direction. As soon as I
> scroll in the other direction on any of the views, Paraview crashes.
>
>
>
> ==> this only appends on Polygonal Meshes: If I apply the AppendDatasets
> filter (outputting an Unstructured Grid) to the same box, everything seems
> to work as expected.
>
> This is pretty much the Hack I used for my data, convert all the object that
> I wanted to slice to unstructured grid. While not optimal it does the job.
>
>
>
> Best,
>
>
> --
>
> Dorian Vogel
>
>
> On Thursday, July 6, 2017 10:54:47 PM CEST Cory Quammen wrote:
>
>> On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian <dorian.vogel at fhnw.ch>
>> wrote:
>
>> > Hi all,
>
>> >
>
>> > I've had a serious issue since last week now:
>
>> >
>
>> > Whenever I visualize a polygonal Mesh in the Slice View or orthogonal
>
>> > slice
>
>> > view:
>
>> >
>
>> > - in slice view: Paraview crashes as soon as I click on any of the slice
>
>> > cursors to grab it to another position.
>
>> >
>
>> > - in orthographic slice view: I can scroll in one direction on each of
>> > the
>
>> > slice views, however, when I scroll in the second direction, Paraview
>
>> > crashes.
>
>>
>
>> I could not reproduce either the "Slice View" crash or "Orthographic
>
>> Slice View" crash you report in ParaView 5.4 on macOS.
>
>>
>
>> > Version 5.3 compiled from source was working fine until I hit this
>> > error,
>
>> > I
>
>> > suspected a package upgrade to be the source of the problem, and
>
>> > downgraded
>
>> > Mesa (17.1.2-1 -> 17.1.1-1) and the Intel driver on laptop (17.1.2-1 ->
>
>> > 17.1.1-1) however, this did not help, and I am sure Paraview 5.3 used to
>
>> > work on those versions of mesa and Intel driver.
>
>>
>
>> Judging by the stack traces you included (very helpful, by the way)
>
>> this looks more like a memory access problem within ParaView. That
>
>> problem seems to have been fixed in ParaView 5.4, though.
>
>>
>
>> HTH,
>
>> Cory
>
>>
>
>> > Systems:
>
>> >
>
>> > -laptop (Archlinux) using Intel IGP or Nvidia discrete GPU using
>
>> > open-source driver (DRI_PRIME). Crash can be reproduced on both GPU.
>
>> >
>
>> > -desktop (Majaro, Arch based): using Nvidia GPU, proprietary driver.
>
>> >
>
>> >
>
>> >
>
>> > Please find attached the gdb traces. I just started Paraview with each
>
>> > GPU,
>
>> > created a box, created a orthographic slice view, and tried to scroll.
>
>> >
>
>> >
>
>> >
>
>> > Did anyone else observe that ?
>
>> >
>
>> >
>
>> >
>
>> > Best regards,
>
>> > --
>
>> >
>
>> > Dorian Vogel
>
>> >
>
>> >
>
>> > _______________________________________________
>
>> > 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&D Engineer
Kitware, Inc.

From jonathan.borduas at caboma.com  Fri Jul  7 09:20:06 2017
From: jonathan.borduas at caboma.com (Jonathan Borduas)
Date: Fri, 7 Jul 2017 13:20:06 +0000
Subject: [Paraview] Error handling  in a programmable filter.
Message-ID: <CY4PR15MB12885D405B059C83E0328006FDAA0@CY4PR15MB1288.namprd15.prod.outlook.com>

Hi Everybody,

Is there a equivalent of "Return 1" in the python programmable filter ?

We would like to block the updating of the pipeline upon an error in the programmable filter (just like a C++ filter).

Jonathan Borduas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/443d3716/attachment.html>

From dorian.vogel at fhnw.ch  Fri Jul  7 09:23:30 2017
From: dorian.vogel at fhnw.ch (Vogel Dorian)
Date: Fri, 7 Jul 2017 13:23:30 +0000
Subject: [Paraview] Paraview segfault on (orthographic) slice view
In-Reply-To: <CAB5Fpx5LgiUP+mOLz6O3q=M5SV0tK9FEh878-KrkoRyGab6CRw@mail.gmail.com>
References: <6810150.cDZEUX3Ych@mu15am33074-linux>
 <2896024.Mug0BS0NRY@mu15am33074-linux>
 <CAB5Fpx5LgiUP+mOLz6O3q=M5SV0tK9FEh878-KrkoRyGab6CRw@mail.gmail.com>
Message-ID: <3409224.4rrhyjXSKX@mu15am33074-linux>

Hi Cory,



I am actually using the "Box" source, and just let the default settings for it: X/Y/Z length = 1, center = (0,0,0).

Btw: It still occurs on a freshly compiled Paraview v5.4.0 with up-to-date mesa.



Best,

--

Dorian Vogel

On Friday, July 7, 2017 3:17:00 PM CEST Cory Quammen wrote:

> Dorian,

>

> Thanks for the followup and workaround. If you could share the data

> set with me or tell me how to create it with a ParaView source, I can

> take a closer look.

>

> Thanks,

> Cory

>

> On Fri, Jul 7, 2017 at 4:33 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:

> > Hello Cory,

> >

> > Thanks for the follow-up.

> >

> >

> >

> > Unfortunately I do still experience this issue, I gathered a bit more

> > information on the behavior of the issue:

> >

> > Still using a 1x1x1 @(0,0,0) box:

> >

> > -open second layout as tab

> >

> > -open orthographic sliceview

> >

> > -I can scroll on all slice views but ONLY in one direction. As soon as I

> > scroll in the other direction on any of the views, Paraview crashes.

> >

> >

> >

> > ==> this only appends on Polygonal Meshes: If I apply the AppendDatasets

> > filter (outputting an Unstructured Grid) to the same box, everything seems

> > to work as expected.

> >

> > This is pretty much the Hack I used for my data, convert all the object

> > that I wanted to slice to unstructured grid. While not optimal it does

> > the job.

> >

> >

> >

> > Best,

> >

> >

> > --

> >

> > Dorian Vogel

> >

> > On Thursday, July 6, 2017 10:54:47 PM CEST Cory Quammen wrote:

> >> On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian <dorian.vogel at fhnw.ch>

> >>

> >> wrote:

> >> > Hi all,

> >> >

> >> >

> >> >

> >> > I've had a serious issue since last week now:

> >> >

> >> >

> >> >

> >> > Whenever I visualize a polygonal Mesh in the Slice View or orthogonal

> >> >

> >> > slice

> >> >

> >> > view:

> >> >

> >> >

> >> >

> >> > - in slice view: Paraview crashes as soon as I click on any of the

> >> > slice

> >> >

> >> > cursors to grab it to another position.

> >> >

> >> >

> >> >

> >> > - in orthographic slice view: I can scroll in one direction on each of

> >> > the

> >> >

> >> > slice views, however, when I scroll in the second direction, Paraview

> >> >

> >> > crashes.

> >>

> >> I could not reproduce either the "Slice View" crash or "Orthographic

> >>

> >> Slice View" crash you report in ParaView 5.4 on macOS.

> >>

> >> > Version 5.3 compiled from source was working fine until I hit this

> >> > error,

> >> >

> >> > I

> >> >

> >> > suspected a package upgrade to be the source of the problem, and

> >> >

> >> > downgraded

> >> >

> >> > Mesa (17.1.2-1 -> 17.1.1-1) and the Intel driver on laptop (17.1.2-1 ->

> >> >

> >> > 17.1.1-1) however, this did not help, and I am sure Paraview 5.3 used

> >> > to

> >> >

> >> > work on those versions of mesa and Intel driver.

> >>

> >> Judging by the stack traces you included (very helpful, by the way)

> >>

> >> this looks more like a memory access problem within ParaView. That

> >>

> >> problem seems to have been fixed in ParaView 5.4, though.

> >>

> >>

> >>

> >> HTH,

> >>

> >> Cory

> >>

> >> > Systems:

> >> >

> >> >

> >> >

> >> > -laptop (Archlinux) using Intel IGP or Nvidia discrete GPU using

> >> >

> >> > open-source driver (DRI_PRIME). Crash can be reproduced on both GPU.

> >> >

> >> >

> >> >

> >> > -desktop (Majaro, Arch based): using Nvidia GPU, proprietary driver.

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> > Please find attached the gdb traces. I just started Paraview with each

> >> >

> >> > GPU,

> >> >

> >> > created a box, created a orthographic slice view, and tried to scroll.

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> > Did anyone else observe that ?

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> >

> >> > Best regards,

> >> >

> >> > --

> >> >

> >> >

> >> >

> >> > Dorian Vogel

> >> >

> >> >

> >> >

> >> >

> >> >

> >> > _______________________________________________

> >> >

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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/d412f0ba/attachment.html>

From cory.quammen at kitware.com  Fri Jul  7 09:27:00 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 7 Jul 2017 09:27:00 -0400
Subject: [Paraview] Paraview python - loop to run through multiple files
In-Reply-To: <CA+h7E46rD6xXFCM6JgN_ydrdnrM_w2421UGbpwHY8WLP_jYPXQ@mail.gmail.com>
References: <CA+h7E46rD6xXFCM6JgN_ydrdnrM_w2421UGbpwHY8WLP_jYPXQ@mail.gmail.com>
Message-ID: <CAB5Fpx6-qyd8Whv7oyte+f27Z3GSDqc_EK9J5Jtf7=8CBOJzqg@mail.gmail.com>

Rebekah,

I think you want to write

LoadState("/home/sophy/Desktop/%s.pvsm" % x)

to properly substitute your filename held in x into the path.

Also, you may want to clear out the loaded state after saving the
image, which you can do by calling

Disconnect()
Connect()

HTH,
Cory


On Fri, Jul 7, 2017 at 6:51 AM, Rebekah L <lapham1996 at gmail.com> wrote:
> Hey :)
> I'm trying to script some code so that I can load a file in and then
> WriteImage and then I want this to loop through multiple files so I don't
> have to change the code each time for the new path. My problem is that
> paraview won't recognise a path unless it is the exact path, so I can't get
> it to change automatically. Any help would be greatly appreciated. Here is
> my current code:
>
> sso2_load_python
> from paraview.simple import *
> fname = '/home/sophy/Desktop'
> #I put the files on the desktop so the path was shorter
> filenames = ["c1", "c2"]
> for x in filenames:
>              Loadstate("/home/sophy/Desktop/x.pvsm")
>       WriteImage("/home/sophy/Desktop/image.png")
>
> #the previous two lines have the four space indent but my phone won't let me
> type it like that
>
>
>
> Thanks - Rebekah
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Fri Jul  7 09:36:32 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 7 Jul 2017 09:36:32 -0400
Subject: [Paraview] Paraview segfault on (orthographic) slice view
In-Reply-To: <3409224.4rrhyjXSKX@mu15am33074-linux>
References: <6810150.cDZEUX3Ych@mu15am33074-linux>
 <2896024.Mug0BS0NRY@mu15am33074-linux>
 <CAB5Fpx5LgiUP+mOLz6O3q=M5SV0tK9FEh878-KrkoRyGab6CRw@mail.gmail.com>
 <3409224.4rrhyjXSKX@mu15am33074-linux>
Message-ID: <CAB5Fpx6JANB18gF3_VEnTfEWk3u7OUybKp4GJdqk6ghJeX6qDQ@mail.gmail.com>

Dorian,

Thanks for clarifying the source. Sorry I didn't understand from your
earlier email.

I just tried again with the official ParaView 5.4.0 binary and was
able to reproduce your crash.

I'll write up a bug report.

Thanks!
Cory

On Fri, Jul 7, 2017 at 9:23 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:
> Hi Cory,
>
>
>
> I am actually using the "Box" source, and just let the default settings for
> it: X/Y/Z length = 1, center = (0,0,0).
>
> Btw: It still occurs on a freshly compiled Paraview v5.4.0 with up-to-date
> mesa.
>
>
>
> Best,
>
>
> --
>
> Dorian Vogel
>
>
> On Friday, July 7, 2017 3:17:00 PM CEST Cory Quammen wrote:
>
>> Dorian,
>
>>
>
>> Thanks for the followup and workaround. If you could share the data
>
>> set with me or tell me how to create it with a ParaView source, I can
>
>> take a closer look.
>
>>
>
>> Thanks,
>
>> Cory
>
>>
>
>> On Fri, Jul 7, 2017 at 4:33 AM, Vogel Dorian <dorian.vogel at fhnw.ch> wrote:
>
>> > Hello Cory,
>
>> >
>
>> > Thanks for the follow-up.
>
>> >
>
>> >
>
>> >
>
>> > Unfortunately I do still experience this issue, I gathered a bit more
>
>> > information on the behavior of the issue:
>
>> >
>
>> > Still using a 1x1x1 @(0,0,0) box:
>
>> >
>
>> > -open second layout as tab
>
>> >
>
>> > -open orthographic sliceview
>
>> >
>
>> > -I can scroll on all slice views but ONLY in one direction. As soon as I
>
>> > scroll in the other direction on any of the views, Paraview crashes.
>
>> >
>
>> >
>
>> >
>
>> > ==> this only appends on Polygonal Meshes: If I apply the AppendDatasets
>
>> > filter (outputting an Unstructured Grid) to the same box, everything
>> > seems
>
>> > to work as expected.
>
>> >
>
>> > This is pretty much the Hack I used for my data, convert all the object
>
>> > that I wanted to slice to unstructured grid. While not optimal it does
>
>> > the job.
>
>> >
>
>> >
>
>> >
>
>> > Best,
>
>> >
>
>> >
>
>> > --
>
>> >
>
>> > Dorian Vogel
>
>> >
>
>> > On Thursday, July 6, 2017 10:54:47 PM CEST Cory Quammen wrote:
>
>> >> On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian <dorian.vogel at fhnw.ch>
>
>> >>
>
>> >> wrote:
>
>> >> > Hi all,
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > I've had a serious issue since last week now:
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > Whenever I visualize a polygonal Mesh in the Slice View or orthogonal
>
>> >> >
>
>> >> > slice
>
>> >> >
>
>> >> > view:
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > - in slice view: Paraview crashes as soon as I click on any of the
>
>> >> > slice
>
>> >> >
>
>> >> > cursors to grab it to another position.
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > - in orthographic slice view: I can scroll in one direction on each
>> >> > of
>
>> >> > the
>
>> >> >
>
>> >> > slice views, however, when I scroll in the second direction, Paraview
>
>> >> >
>
>> >> > crashes.
>
>> >>
>
>> >> I could not reproduce either the "Slice View" crash or "Orthographic
>
>> >>
>
>> >> Slice View" crash you report in ParaView 5.4 on macOS.
>
>> >>
>
>> >> > Version 5.3 compiled from source was working fine until I hit this
>
>> >> > error,
>
>> >> >
>
>> >> > I
>
>> >> >
>
>> >> > suspected a package upgrade to be the source of the problem, and
>
>> >> >
>
>> >> > downgraded
>
>> >> >
>
>> >> > Mesa (17.1.2-1 -> 17.1.1-1) and the Intel driver on laptop (17.1.2-1
>> >> > ->
>
>> >> >
>
>> >> > 17.1.1-1) however, this did not help, and I am sure Paraview 5.3 used
>
>> >> > to
>
>> >> >
>
>> >> > work on those versions of mesa and Intel driver.
>
>> >>
>
>> >> Judging by the stack traces you included (very helpful, by the way)
>
>> >>
>
>> >> this looks more like a memory access problem within ParaView. That
>
>> >>
>
>> >> problem seems to have been fixed in ParaView 5.4, though.
>
>> >>
>
>> >>
>
>> >>
>
>> >> HTH,
>
>> >>
>
>> >> Cory
>
>> >>
>
>> >> > Systems:
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > -laptop (Archlinux) using Intel IGP or Nvidia discrete GPU using
>
>> >> >
>
>> >> > open-source driver (DRI_PRIME). Crash can be reproduced on both GPU.
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > -desktop (Majaro, Arch based): using Nvidia GPU, proprietary driver.
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > Please find attached the gdb traces. I just started Paraview with
>> >> > each
>
>> >> >
>
>> >> > GPU,
>
>> >> >
>
>> >> > created a box, created a orthographic slice view, and tried to
>> >> > scroll.
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > Did anyone else observe that ?
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > Best regards,
>
>> >> >
>
>> >> > --
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > Dorian Vogel
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > _______________________________________________
>
>> >> >
>
>> >> > 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&D Engineer
Kitware, Inc.

From andy.bauer at kitware.com  Fri Jul  7 10:07:12 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 7 Jul 2017 10:07:12 -0400
Subject: [Paraview] multiple visualization pipeline at a time with
	co-processing
In-Reply-To: <e707d3dd-870b-bc30-6e80-7922a6c0b70a@be.itu.edu.tr>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
 <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
 <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>
 <e707d3dd-870b-bc30-6e80-7922a6c0b70a@be.itu.edu.tr>
Message-ID: <CAMaOp+HZkAq-sWP+dWWg5Wy3w7s38Y=0RQkLLNUPHpBsZLz9xQ@mail.gmail.com>

Hi Ufuk,

It's looking to me like the issue is in the adaptor some place. I tried
running your scripts (modified slightly) with the CxxFullExample
(./CxxFullExample script_1.py script_2.py) and was able to get image_s1*
and image_s2* files out of it and did not see the warning you mention. I
also modified that example to use atm_input2d instead of input for the
input/grid identifier to make sure that wasn't the case. I've attached this
example with the scripts modified to print out some debug information.

Some questions (these are pretty basic things that you've probably already
gotten working properly but maybe there's some small thing that was
forgotten):

   - Does your g_coprocessor only get created in your initialization
   routine and deleted in the finalization step? That should not be created
   and deleted during each in situ processing step.
   - Do the vtkCPPythonScriptPipelines only get added during
   initialization? They should not be added and removed from g_coprocessor
   every time step.

Also, could you try running with the scripts that I included in the cat.tgz
tarball? The print statements there will print out the time and time steps
during the simulation run to help me diagnose (both need to be increasing
between calls to Catalyst). Also, if you share your adaptor code with me I
can take a quick look.

Cheers,
Andy



On Fri, Jul 7, 2017 at 7:30 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Andy,
>
> Strange! To test the idea and eliminate other problems i am using same
> script twice with little mods (i just changed the name of the output png
> file). So, if i pass script_1.py and script_2.py to the model, it gives
> warning like before and creates output just for second script
> (script_2.py). If i pass only one of them then the code is working without
> any problem and produces desired output.
>
> Thanks,
> Regards,
>
> --ufuk
>
>
>
> On 06/07/2017 18:09, Andy Bauer wrote:
>
> Hi Ufuk,
>
> I'm guessing the issue is that the calls to Catalyst are not consistent.
> Could you share your Python scripts? Also, did you modify them manually?
>
> I tried with PV 5.3. with the ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/
> example with the attached scripts simultaneously by running with
> "./CxxFullExample doubleoutputs.py output3.py image11.py" and got the
> correct output and no warnings.
>
> Cheers,
> Andy
>
> On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE) <
> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Hi Andy,
>>
>> I tested you suggestion about using multiple script in co-processing. In
>> this case, i used following code in the adaptor side to add multiple
>> pipeline
>>
>>       for (int i = 0; i < *nscript; i++) {
>>         pipeline->Initialize(pythonScriptNames[i]);
>>         g_coprocessor->AddPipeline(pipeline);
>>       }
>>
>> When i run the simulation, i am getting following warning
>>
>> Warning: In /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaView
>> Core/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 66
>> vtkPVTrivialProducer (0x13816760): New time step is not after last time
>> step.
>>
>> the output seems not correct and it is zoom out version of second
>> pipeline (png file). The first pipeline is not even triggered. Do i missing
>> something in here? BTW, i am using PV 5.3.
>>
>> Thanks,
>>
>> --ufuk
>>
>>
>> On 16/05/2017 16:08, Andy Bauer wrote:
>>
>> Hi Ufuk,
>>
>> If you create a vtkCPythonScriptPipeline, when you initialize it with the
>> script file name (which has to be done on each process) everything will be
>> taken care of with respect to broadcasting the file contents from process 0
>> to the others. We aren't sophisticated enough to parse the Python script to
>> see if it imports other scripts that are not part of ParaView (e.g.
>> paraview.simple) or Python (e.g. sys). That is why I recommended the first
>> approach as opposed to the second approach above. Depending on the compute
>> platform and how many MPI processes are in the run the difference may be
>> negligible but having 100K processes or more trying to access the same file
>> can seriously slow down an HPC machine.
>>
>> Cheers,
>> Andy
>>
>> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE) <
>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>
>>> Thanks Andy. That is exactly what i am looking for. The broadcasting
>>> mechanism is not clear to me yet. Do i need to broadcast only the file
>>> names? Anyway, i will try to implement it and see what is going on there.
>>>
>>> Thanks again,
>>> Regards,
>>>
>>> --ufuk
>>>
>>>
>>> On 16/05/2017 14:58, Andy Bauer wrote:
>>>
>>> Hi Ufuk,
>>>
>>> Unless I'm not understanding your question correctly, I think you can
>>> get what you want by adding in multiple vtkCPPythonScriptPipelines to your
>>> vtkCPProcessor object in your adaptor. Alternatively if you want to have a
>>> single, master Catalyst script handling other Catalyst scripts you can do
>>> something like the following:
>>> ================
>>> import script_a
>>> import script_b
>>> import script_c
>>>
>>> def RequestDataDescription(datadescription):
>>>   script_a.RequestDataDescription(datadescription)
>>>   script_b.RequestDataDescription(datadescription)
>>>   script_c.RequestDataDescription(datadescription)
>>>
>>> def DoCoProcessing(datadescription):
>>>   script_a.DoCoProcessing(datadescription)
>>>   script_b.DoCoProcessing(datadescription)
>>>   script_c.DoCoProcessing(datadescription)
>>> ===================
>>>
>>> The first way is the recommended way though as that should be more
>>> efficient by having process 0 read the scripts and broadcasting the script
>>> contents to the other  processes for use. The second method will only do
>>> that for the master script.
>>>
>>> Please let me know if this doesn't answer your question.
>>>
>>> Cheers,
>>> Andy
>>>
>>> On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE) <
>>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I just wonder that is it possible to trigger multiple visualization
>>>> pipeline in the same time with co-processing. The co-processing script
>>>> generator plugin mainly outputs only single pipeline at a time and that is
>>>> fine but what about combining multiple Python script (generated by plugin)
>>>> using higher level Python script to trigger multiple pipelines. So, i think
>>>> that this will be much efficient way to look at different part of the data
>>>> without writing to the disk. I am not sure but somebody else might do it
>>>> before.
>>>>
>>>> Regards,
>>>>
>>>> --ufuk
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/7dc31c51/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cat.tgz
Type: application/x-gzip
Size: 7576 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/7dc31c51/attachment.bin>

From utkarsh.ayachit at kitware.com  Fri Jul  7 10:18:50 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 7 Jul 2017 10:18:50 -0400
Subject: [Paraview] Error handling in a programmable filter.
In-Reply-To: <CY4PR15MB12885D405B059C83E0328006FDAA0@CY4PR15MB1288.namprd15.prod.outlook.com>
References: <CY4PR15MB12885D405B059C83E0328006FDAA0@CY4PR15MB1288.namprd15.prod.outlook.com>
Message-ID: <CADHSJjDXNdLDRgw8eDhwuBavPXi=SgjD5mEvUWLHL6kQpWX=5Q@mail.gmail.com>

>
> We would like to block the updating of the pipeline upon an error in the
> programmable filter (just like a C++ filter).
>
>
>
Raising an exception in the Python script should a interupt your script,
however from the code I see that that wouln't exactly do what `return 0` in
RequestData for C++ filter would. Please feel to report a bug on the issue
tracker. Should be fairly easy to address in  a future release of ParaView.

Utkarsh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/b9ce1a4b/attachment.html>

From jonathan.borduas at caboma.com  Fri Jul  7 10:50:40 2017
From: jonathan.borduas at caboma.com (Jonathan Borduas)
Date: Fri, 7 Jul 2017 14:50:40 +0000
Subject: [Paraview] Error handling in a programmable filter.
In-Reply-To: <CADHSJjDXNdLDRgw8eDhwuBavPXi=SgjD5mEvUWLHL6kQpWX=5Q@mail.gmail.com>
References: <CY4PR15MB12885D405B059C83E0328006FDAA0@CY4PR15MB1288.namprd15.prod.outlook.com>
 <CADHSJjDXNdLDRgw8eDhwuBavPXi=SgjD5mEvUWLHL6kQpWX=5Q@mail.gmail.com>
Message-ID: <CY4PR15MB128890847C1B1172C201D221FDAA0@CY4PR15MB1288.namprd15.prod.outlook.com>

Added as Issue #17591<https://gitlab.kitware.com/paraview/paraview/issues/17591>

Thanks

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Friday, July 7, 2017 10:19 AM
To: Jonathan Borduas <jonathan.borduas at caboma.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Error handling in a programmable filter.

We would like to block the updating of the pipeline upon an error in the programmable filter (just like a C++ filter).


Raising an exception in the Python script should a interupt your script, however from the code I see that that wouln't exactly do what `return 0` in RequestData for C++ filter would. Please feel to report a bug on the issue tracker. Should be fairly easy to address in  a future release of ParaView.

Utkarsh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/0e53731b/attachment.html>

From shuhao at shuhaowu.com  Fri Jul  7 10:51:14 2017
From: shuhao at shuhaowu.com (Shuhao Wu)
Date: Fri, 7 Jul 2017 10:51:14 -0400
Subject: [Paraview] Coloring isocontour by the coordinates outputted
 from a Transform filter and some other questions
In-Reply-To: <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>
References: <d5d624cc-e171-f153-b1b6-47ee0a9b8068@shuhaowu.com>
 <CAB5Fpx4aKwctsmYnb+yhFyxtRok_c1CGt1shrTbTRF4iOrE+iw@mail.gmail.com>
 <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
 <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>
Message-ID: <1e93335f-ae07-3c53-2836-c69dbfafc4b9@shuhaowu.com>

Is there documentation on how the Box clip type work? I'm not quite sure 
how to do the math to convert the threshold values to the position/scale 
values.

Thanks,
Shuhao

On 2017-07-03 10:03 AM, Cory Quammen wrote:
> On Tue, Jun 20, 2017 at 9:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
> 
>> Hello Cory,
>>
>> I've been playing around a little bit more and followed your suggestion
>> with using the calculator to "expose" the transformed coordinates. However,
>> my understanding is that this Calculator will duplicate the memory usage
>> for that coordinate and be an additional step in the filtering process,
>> slowing it down.
> 
> 
> Yes, that's true unfortunately. By the way, if you need X, Y, and Z, you
> can use one Calculator filter to produce all three with the expression
> 
> iHat*coordsX + jHat*coordsY + kHat*coordsZ
> 
> This produces a 3-component array - you can then color your isosurface by
> just one of the components or by the magnitude.
> 
> I have to use the Calculator filter to expose all 3 coordinates before
>> using a threshold to filter for only a subset region that I want to plt,
>> which results in a filtering chain as follows:
>>
>> ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) ->
>> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ (Threshold).
> 
> 
>>
> This is 6 filters, which is very slow with my data set (>29M nodes in a
>> rectlinear grid). Is there a way to speed this up?
>>
>>
> You could instead use a Clip filter with Clip Type set to Box. You have to
> do a little math to convert from your threshold values to the box Scale and
> Position properties, but it shouldn't be too bad, and will make your
> pipeline simpler and faster.
> 
> Cory
> 
> 
>> Thanks,
>> Shuhao
>>
>>
>> On 2017-06-07 03:29 PM, Cory Quammen wrote:
>>
>>> Shuhao,
>>>
>>> Welcome to ParaView!
>>>
>>> On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>
>>>> Hello all,
>>>>
>>>> Is there a way to color an isocontour via the coordinates outputted from
>>>> a
>>>> Transform filter? I'm using the Transform filter to "normalize" my
>>>> coordinate systems and I want to display the isocontour colored by the
>>>> normalized Y coordinates. Do I have to create yet another Calculator
>>>> filter
>>>> to recalculate the normalized Y value that is already calculated by the
>>>> Transform filter?
>>>>
>>>
>>> There is currently no direct way to color surfaces by coordinate
>>> value. You can, however, add a Calculator after the Transform filter
>>> and simply set the expression to coordsY - no recomputation of the
>>> normalization is needed. This will copy your normalized Y coordinate
>>> values to a new array named "Result", and you can then color the
>>> isosurface by "Result". "Result" is just the default name - you can
>>> change it however you wish.
>>>
>>> Also: is there a way to turn off one axis on the axis grid (so turn off
>>>> the
>>>> Y axis display and leave only X and Z)?
>>>>
>>>
>>> Click the Edit button next to the Axes Grid option. Click the gear
>>> icon in the top right of the dialog that appears. Under Face
>>> Properties, click on the "Faces to Render" combo box. Turn off the
>>> sides you do not wish to see by selecting them in the combo box.
>>>
>>> What about changing the interval on
>>>> the axis itself (instead of incrementing by 100 as it chooses, increment
>>>> by
>>>> 250).
>>>>
>>>
>>> In the same dialog described above, check the "X Axis Use Custom
>>> Labels", and you can specify exactly the labels you want. There is no
>>> property to directly change the increment.
>>>
>>> Best,
>>> Cory
>>>
>>> I'm pretty new to Paraview (coming from Tecplot). Please bear with me as I
>>>> likely will have more question.
>>>>
>>>> Thanks,
>>>> Shuhao
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>>
>>>
>>>
> 
> 

From gregory.zaccaro at caboma.com  Fri Jul  7 13:43:26 2017
From: gregory.zaccaro at caboma.com (Gregory Zaccaro)
Date: Fri, 7 Jul 2017 17:43:26 +0000
Subject: [Paraview] Compute animation in parallel using pvbatch
Message-ID: <BLUPR15MB01451617DC5B06488849D3578CAA0@BLUPR15MB0145.namprd15.prod.outlook.com>

Hi all,

Currently I have a .pvsm being loaded on pvbacth with python.

Each time step of the animation is independant and generate a single file for that time step.

Now, my goal is to run multiple time steps of this state file in parallel with pvbatch.

Is it possible ?

I built Paraview 5.3 from sources on Windows 10.
I enabled some useful options that I think could help :
- PARAVIEW_ENABLE_PYTHON
- PARAVIEW_USE_MPI

Gregory Zaccaro

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/00704b84/attachment.html>

From mbahameish at gmail.com  Fri Jul  7 14:44:50 2017
From: mbahameish at gmail.com (Mariam)
Date: Fri, 07 Jul 2017 19:44:50 +0100
Subject: [Paraview] [Camera Control] - Clipping Range
Message-ID: <8E720A6F-84A1-4646-8D77-2F3B1964DF77@gmail.com>

Hi,

I am trying to control the camera attributes from pvpython, I noticed that if I modified Clipping Range & Thickness then called Render() the values are reset to the original values. However, changes in camera position, focal point, view up and viewing angle take effect after Render().

 

Here is a snippet of the code:

from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

sphere = Sphere()
Show()
Render()

camera = GetActiveCamera()
camera.GetFocalPoint()
(0.0, 0.0, 0.0)

camera.GetPosition()
(0.0, 0.0, 6.69)

camera.GetClippingRange()
(5.628100000000001, 8.042850000000001)

camera.SetPosition(0,0,3)
Render()


camera.GetPosition()
(0.0, 0.0, 3.0)


camera.GetClippingRange()
(1.975, 4.2975)

camera.SetClippingRange(3,8)
camera.GetClippingRange()
(3.0, 8.0)

Render()

camera.GetClippingRange()
(1.975, 4.2975)

 

 

How can I force changes on Clipping Range & Thickness values?

 

Regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/eb326cb4/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul  7 14:51:47 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 7 Jul 2017 14:51:47 -0400
Subject: [Paraview] [Camera Control] - Clipping Range
In-Reply-To: <8E720A6F-84A1-4646-8D77-2F3B1964DF77@gmail.com>
References: <8E720A6F-84A1-4646-8D77-2F3B1964DF77@gmail.com>
Message-ID: <CADHSJjAYTzn+Bk+Zov+mdNsFVyKj=KV7RAY8CAcRbBJTj1yfpg@mail.gmail.com>

Currently, you can't. ParaView doesn't let user change ClippingRange. It
resets it internally before each render.

On Fri, Jul 7, 2017 at 2:44 PM, Mariam <mbahameish at gmail.com> wrote:

> Hi,
>
> I am trying to control the camera attributes from pvpython, I noticed that
> if I modified Clipping Range & Thickness then called Render() the values
> are reset to the original values. However, changes in camera position,
> focal point, view up and viewing angle take effect after Render().
>
>
>
> Here is a snippet of the code:
>
> *from *paraview.simple *import **
> paraview.simple._DisableFirstRenderCameraReset()
>
> sphere = Sphere()
> Show()
> Render()
>
> camera = GetActiveCamera()
> camera.GetFocalPoint()
> (0.0, 0.0, 0.0)
>
> camera.GetPosition()
> (0.0, 0.0, 6.69)
>
> camera.GetClippingRange()
> (5.628100000000001, 8.042850000000001)
>
> camera.SetPosition(0,0,3)
> Render()
>
>
> camera.GetPosition()
> (0.0, 0.0, 3.0)
>
>
> camera.GetClippingRange()
> (1.975, 4.2975)
>
> camera.SetClippingRange(3,8)
> camera.GetClippingRange()
> (3.0, 8.0)
>
> Render()
>
>
> *camera.GetClippingRange()(1.975, 4.2975)*
>
>
>
>
>
> How can I force changes on Clipping Range & Thickness values?
>
>
>
> Regards,
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/56361d19/attachment.html>

From dave.demarle at kitware.com  Fri Jul  7 14:57:14 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 7 Jul 2017 14:57:14 -0400
Subject: [Paraview] [Camera Control] - Clipping Range
In-Reply-To: <CADHSJjAYTzn+Bk+Zov+mdNsFVyKj=KV7RAY8CAcRbBJTj1yfpg@mail.gmail.com>
References: <8E720A6F-84A1-4646-8D77-2F3B1964DF77@gmail.com>
 <CADHSJjAYTzn+Bk+Zov+mdNsFVyKj=KV7RAY8CAcRbBJTj1yfpg@mail.gmail.com>
Message-ID: <CANjZAi9xSpCwYbHMoHM12w=hqtetmGOanM1MQvQZKUtQ9FwPng@mail.gmail.com>

Try LockBounds.

For example:
view = GetActiveView()
view.MaxClipBounds = [x0,x1,y0,y1,z0,z1]
view.LockBounds = 1

David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Jul 7, 2017 at 2:51 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> wrote:

> Currently, you can't. ParaView doesn't let user change ClippingRange. It
> resets it internally before each render.
>
> On Fri, Jul 7, 2017 at 2:44 PM, Mariam <mbahameish at gmail.com> wrote:
>
>> Hi,
>>
>> I am trying to control the camera attributes from pvpython, I noticed
>> that if I modified Clipping Range & Thickness then called Render() the
>> values are reset to the original values. However, changes in camera
>> position, focal point, view up and viewing angle take effect after Render().
>>
>>
>>
>> Here is a snippet of the code:
>>
>> *from *paraview.simple *import **
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> sphere = Sphere()
>> Show()
>> Render()
>>
>> camera = GetActiveCamera()
>> camera.GetFocalPoint()
>> (0.0, 0.0, 0.0)
>>
>> camera.GetPosition()
>> (0.0, 0.0, 6.69)
>>
>> camera.GetClippingRange()
>> (5.628100000000001, 8.042850000000001)
>>
>> camera.SetPosition(0,0,3)
>> Render()
>>
>>
>> camera.GetPosition()
>> (0.0, 0.0, 3.0)
>>
>>
>> camera.GetClippingRange()
>> (1.975, 4.2975)
>>
>> camera.SetClippingRange(3,8)
>> camera.GetClippingRange()
>> (3.0, 8.0)
>>
>> Render()
>>
>>
>> *camera.GetClippingRange()(1.975, 4.2975)*
>>
>>
>>
>>
>>
>> How can I force changes on Clipping Range & Thickness values?
>>
>>
>>
>> Regards,
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170707/f6ca6913/attachment.html>

From ezhkr601 at student.liu.se  Sat Jul  8 12:26:12 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Sat, 8 Jul 2017 18:26:12 +0200
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CAB5Fpx5nueW1mznb=ftvmuARSnkpwXcrN9RaLnCy4BzWqeNg8w@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
 <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
 <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>
 <CAB5Fpx5nueW1mznb=ftvmuARSnkpwXcrN9RaLnCy4BzWqeNg8w@mail.gmail.com>
Message-ID: <CACrYMsK6zc1mwZ1B4x13mKAXeJgKDOuj6rSKSZGxKokd7Xk57A@mail.gmail.com>

Hi Cory,

Could you please give me  some more information.
It will not build if I turn it OFF.

Kind regards,
Mathi

On 6 July 2017 at 20:51, Cory Quammen <cory.quammen at kitware.com> wrote:

> Set the BUILD_SHARED_LIBS option to OFF.
>
> HTH,
> Cory
>
> On Sun, Jul 2, 2017 at 11:56 AM, Ezhilmathi Krishnasamy
> <ezhkr601 at student.liu.se> wrote:
> > Hi,
> >
> > I am still having some problem with enabling the
> > build shared libs. I am trying to install it on a Cray machine.
> > I have already locally installed cmake and anaconda on their latest
> version.
> >
> > I am attaching here the image.
> > Could any one tell me how to fix this issue
> >
> > Kind regards,
> > Mathi
> >
> > On 2 July 2017 at 14:54, Ezhilmathi Krishnasamy <ezhkr601 at student.liu.se
> >
> > wrote:
> >>
> >> Hi,
> >>
> >> I have almost build it, but getting this error:
> >>
> >>  CMake Warning (dev) at
> >> /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
> >> (add_library):
> >>    ADD_LIBRARY called with SHARED option but the target platform does
> not
> >>    support dynamic linking.  Building a STATIC library instead.  This
> may
> >> lead
> >>    to problems.
> >>  Call Stack (most recent call first):
> >>    /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
> >> (find_package)
> >>    superbuild/projects/qt5.system.cmake:1 (find_package)
> >>    superbuild/cmake/SuperbuildMacros.cmake:640 (include)
> >>    superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
> >>  This warning is for project developers.  Use -Wno-dev to suppress it.
> >>
> >>
> >>
> >> On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy <
> ezhkr601 at student.liu.se>
> >> wrote:
> >>>
> >>> Thanks!
> >>>
> >>> Now it shows this kind of error
> >>>
> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild>
> >>> git fetch origin
> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild>
> >>> git checkout v5.4.0
> >>> HEAD is now at 7c510fe... Update to 5.4.0
> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild>
> >>> git submodule update
> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild>
> >>> cd ..
> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
> >>> /cfs/klemming/nobackup/k/kriezh> cd build/
> >>> /cfs/klemming/nobackup/k/kriezh/build> ccmake
> >>> ../PARAVIEW_SUPER_BUILD/paraview-superbuild/
> >>>
> >>>
> >>>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
> >>>    The build tree appears to be inside of the git repository located at
> >>>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
> >>>    superbuild applies patches to projects and is not supported.  Please
> >>>    relocate the build tree to a directory which is not under a git
> >>> repository.
> >>>  Call Stack (most recent call first):
> >>>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
> >>>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
> >>>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
> >>>
> >>>
> >>>
> >>>
> >>> On 2 July 2017 at 14:03, Patrick B?gou
> >>> <Patrick.Begou at legi.grenoble-inp.fr> wrote:
> >>>>
> >>>> Like you, I got this error some months ago when trying to build
> paraview
> >>>> superbuild:
> >>>>
> >>>> error: unknown option `is-ancestor'
> >>>>
> >>>> It was my git version wich was too old. May be try to compile a more
> up
> >>>> to date version of git in your home and set the path to access it.
> >>>>
> >>>> I have installed git from
> >>>> https://www.kernel.org/pub/software/scm/git/git-2.12.2.tar.xz
> >>>>
> >>>> Patrick
> >>>>
> >>>> Ezhilmathi Krishnasamy a ?crit :
> >>>>
> >>>> Hi,
> >>>>
> >>>> I have followed these instructions. I am trying to install it where I
> am
> >>>> not a root user.
> >>>> Can someone help to fix this issue.
> >>>>
> >>>>  git clone --recursive
> >>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
> >>>>  cd paraview-superbuild
> >>>>  git fetch origin # ensure you have the latest state from the main
> repo
> >>>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
> >>>>  git submodule update
> >>>>
> >>>>  cd ..
> >>>>  mkdir build
> >>>>  cd build
> >>>>  ccmake ../paraview-superbuild
> >>>>
> >>>> Kind regards,
> >>>> Mathi
> >>>>
> >>>>
> >>>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy
> >>>> <ezhkr601 at student.liu.se> wrote:
> >>>>>
> >>>>> Hi Thanks!
> >>>>>
> >>>>> When I try to install Paraview,  I am getting the following error.
> >>>>> Could some one please tell me how to fix this issue.
> >>>>> I am trying to install the Paraview on a super computer to use it
> >>>>> for remote rendering without using the GUI,  like with mesa support.
> >>>>>
> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD>
> git
> >>>>> clone --recursive
> >>>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
> >>>>> Cloning into 'paraview-superbuild'...
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> remote: Counting objects: 6723, done.
> >>>>> remote: Compressing objects: 100% (2459/2459), done.
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
> >>>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
> >>>>> Resolving deltas: 100% (4451/4451), done.
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> Checking out files: 100% (196/196), done.
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> Submodule 'superbuild'
> >>>>> (https://gitlab.kitware.com/paraview/common-superbuild.git)
> registered for
> >>>>> path 'superbuild'
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> Cloning into 'superbuild'...
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> remote: Counting objects: 6752, done.
> >>>>> remote: Compressing objects: 100% (2235/2235), done.
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
> >>>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
> >>>>> Resolving deltas: 100% (4505/4505), done.
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> Submodule path 'superbuild': checked out
> >>>>> '8f357bb5bf35419c210b3f9e0adbc9df08f565f2'
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>> warning: unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig
> ':
> >>>>> Permission denied
> >>>>>
> >>>>>
> >>>>>
> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_
> SUPER_BUILD/paraview-superbuild>
> >>>>> cmake .
> >>>>> -- The C compiler identification is Intel 14.0.4.20140805
> >>>>> -- The CXX compiler identification is Intel 14.0.4.20140805
> >>>>> -- Cray Programming Environment 2.2.1 C
> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc --
> works
> >>>>> -- Detecting C compiler ABI info
> >>>>> -- Detecting C compiler ABI info - done
> >>>>> -- Detecting C compile features
> >>>>> -- Detecting C compile features - done
> >>>>> -- Cray Programming Environment 2.2.1 CXX
> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC --
> >>>>> works
> >>>>> -- Detecting CXX compiler ABI info
> >>>>> -- Detecting CXX compiler ABI info - done
> >>>>> -- Detecting CXX compile features
> >>>>> -- Detecting CXX compile features - done
> >>>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242
> (message):
> >>>>>   Failed to determine if the common superbuild is an old checkout.
> The
> >>>>>   common superbuild may be out of date, but cannot be verified.:
> >>>>> warning:
> >>>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >>>>> Permission
> >>>>>   denied
> >>>>>
> >>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/
> kriezh/.gitconfig':
> >>>>>   Permission denied
> >>>>>
> >>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/
> kriezh/.gitconfig':
> >>>>>   Permission denied
> >>>>>
> >>>>>   warning: unable to access '/afs/pdc.kth.se/home/k/
> kriezh/.gitconfig':
> >>>>>   Permission denied
> >>>>>
> >>>>>   error: unknown option `is-ancestor'
> >>>>>
> >>>>>   usage: git merge-base [-a|--all] <commit> <commit>...
> >>>>>
> >>>>>      or: git merge-base [-a|--all] --octopus <commit>...
> >>>>>      or: git merge-base --independent <commit>...
> >>>>>
> >>>>>
> >>>>>
> >>>>>       -a, --all             output all common ancestors
> >>>>>       --octopus             find ancestors for a single n-way merge
> >>>>>       --independent         list revs not reachable from others
> >>>>> Call Stack (most recent call first):
> >>>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
> >>>>>
> >>>>>
> >>>>> -- Check size of void*
> >>>>> -- Check size of void* - done
> >>>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
> >>>>> -- Determined source version for paraview: 5.4.0
> >>>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289
> (message):
> >>>>>   The build tree appears to be inside of the git repository located
> at
> >>>>>
> >>>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/
> paraview-superbuild.
> >>>>>   This interferes with the way the superbuild applies patches to
> >>>>> projects and
> >>>>>   is not supported.  Please relocate the build tree to a directory
> >>>>> which is
> >>>>>   not under a git repository.
> >>>>> Call Stack (most recent call first):
> >>>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
> >>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
> >>>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
> >>>>>
> >>>>>
> >>>>> -- Configuring incomplete, errors occurred!
> >>>>> See also
> >>>>> "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-
> superbuild/CMakeFiles/CMakeOutput.log".
> >>>>>
> >>>>>
> >>>>> Kind regards,
> >>>>> Mathi
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
> >>>>>> <ezhkr601 at student.liu.se> wrote:
> >>>>>> > Hi,
> >>>>>> >
> >>>>>> > Can anyone please give me some instructions how to Paraview
> >>>>>> > Superbuid
> >>>>>> > to install and use them with out using the GUI (using the python
> >>>>>> > script to
> >>>>>> > render the images on the cluster or super computer).
> >>>>>> >
> >>>>>> > I see there are some instructions in here:
> >>>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
> >>>>>> >
> >>>>>> > But I could not find any build instructions.
> >>>>>>
> >>>>>> Take a look again, that page includes the README.md file contents
> >>>>>> which includes build instructions.
> >>>>>>
> >>>>>> To build without the GUI, you should just need to set the options
> >>>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
> >>>>>> ENABLE_python to ON.
> >>>>>>
> >>>>>> Best regards,
> >>>>>> Cory
> >>>>>>
> >>>>>> >
> >>>>>> > Kind regards,
> >>>>>> > Mathi
> >>>>>> >
> >>>>>> > _______________________________________________
> >>>>>> > 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&D 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
> >>>>
> >>>>
> >>>
> >>
> >
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170708/577709fa/attachment.html>

From cory.quammen at kitware.com  Sun Jul  9 18:56:37 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 9 Jul 2017 18:56:37 -0400
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CACrYMsK6zc1mwZ1B4x13mKAXeJgKDOuj6rSKSZGxKokd7Xk57A@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
 <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
 <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>
 <CAB5Fpx5nueW1mznb=ftvmuARSnkpwXcrN9RaLnCy4BzWqeNg8w@mail.gmail.com>
 <CACrYMsK6zc1mwZ1B4x13mKAXeJgKDOuj6rSKSZGxKokd7Xk57A@mail.gmail.com>
Message-ID: <CAB5Fpx42BSZb5TXLQzJKDf4qHAFep3MTGB2NGo3k6bXE_wLK0g@mail.gmail.com>

Mathi,

Chuck Atkins is the guru when it comes to compiling ParaView on Cray
systems (along with many other systems). He may have some more helpful
tips to get you building on your system.

Best,
Cory

On Sat, Jul 8, 2017 at 12:26 PM, Ezhilmathi Krishnasamy
<ezhkr601 at student.liu.se> wrote:
> Hi Cory,
>
> Could you please give me  some more information.
> It will not build if I turn it OFF.
>
> Kind regards,
> Mathi
>
> On 6 July 2017 at 20:51, Cory Quammen <cory.quammen at kitware.com> wrote:
>>
>> Set the BUILD_SHARED_LIBS option to OFF.
>>
>> HTH,
>> Cory
>>
>> On Sun, Jul 2, 2017 at 11:56 AM, Ezhilmathi Krishnasamy
>> <ezhkr601 at student.liu.se> wrote:
>> > Hi,
>> >
>> > I am still having some problem with enabling the
>> > build shared libs. I am trying to install it on a Cray machine.
>> > I have already locally installed cmake and anaconda on their latest
>> > version.
>> >
>> > I am attaching here the image.
>> > Could any one tell me how to fix this issue
>> >
>> > Kind regards,
>> > Mathi
>> >
>> > On 2 July 2017 at 14:54, Ezhilmathi Krishnasamy
>> > <ezhkr601 at student.liu.se>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> I have almost build it, but getting this error:
>> >>
>> >>  CMake Warning (dev) at
>> >> /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
>> >> (add_library):
>> >>    ADD_LIBRARY called with SHARED option but the target platform does
>> >> not
>> >>    support dynamic linking.  Building a STATIC library instead.  This
>> >> may
>> >> lead
>> >>    to problems.
>> >>  Call Stack (most recent call first):
>> >>    /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
>> >> (find_package)
>> >>    superbuild/projects/qt5.system.cmake:1 (find_package)
>> >>    superbuild/cmake/SuperbuildMacros.cmake:640 (include)
>> >>    superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
>> >>  This warning is for project developers.  Use -Wno-dev to suppress it.
>> >>
>> >>
>> >>
>> >> On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy
>> >> <ezhkr601 at student.liu.se>
>> >> wrote:
>> >>>
>> >>> Thanks!
>> >>>
>> >>> Now it shows this kind of error
>> >>>
>> >>>
>> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> >>> git fetch origin
>> >>>
>> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> >>> git checkout v5.4.0
>> >>> HEAD is now at 7c510fe... Update to 5.4.0
>> >>>
>> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> >>> git submodule update
>> >>>
>> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> >>> cd ..
>> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
>> >>> /cfs/klemming/nobackup/k/kriezh> cd build/
>> >>> /cfs/klemming/nobackup/k/kriezh/build> ccmake
>> >>> ../PARAVIEW_SUPER_BUILD/paraview-superbuild/
>> >>>
>> >>>
>> >>>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289 (message):
>> >>>    The build tree appears to be inside of the git repository located
>> >>> at
>> >>>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way the
>> >>>    superbuild applies patches to projects and is not supported.
>> >>> Please
>> >>>    relocate the build tree to a directory which is not under a git
>> >>> repository.
>> >>>  Call Stack (most recent call first):
>> >>>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>> >>>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>> >>>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On 2 July 2017 at 14:03, Patrick B?gou
>> >>> <Patrick.Begou at legi.grenoble-inp.fr> wrote:
>> >>>>
>> >>>> Like you, I got this error some months ago when trying to build
>> >>>> paraview
>> >>>> superbuild:
>> >>>>
>> >>>> error: unknown option `is-ancestor'
>> >>>>
>> >>>> It was my git version wich was too old. May be try to compile a more
>> >>>> up
>> >>>> to date version of git in your home and set the path to access it.
>> >>>>
>> >>>> I have installed git from
>> >>>> https://www.kernel.org/pub/software/scm/git/git-2.12.2.tar.xz
>> >>>>
>> >>>> Patrick
>> >>>>
>> >>>> Ezhilmathi Krishnasamy a ?crit :
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> I have followed these instructions. I am trying to install it where I
>> >>>> am
>> >>>> not a root user.
>> >>>> Can someone help to fix this issue.
>> >>>>
>> >>>>  git clone --recursive
>> >>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
>> >>>>  cd paraview-superbuild
>> >>>>  git fetch origin # ensure you have the latest state from the main
>> >>>> repo
>> >>>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your choice
>> >>>>  git submodule update
>> >>>>
>> >>>>  cd ..
>> >>>>  mkdir build
>> >>>>  cd build
>> >>>>  ccmake ../paraview-superbuild
>> >>>>
>> >>>> Kind regards,
>> >>>> Mathi
>> >>>>
>> >>>>
>> >>>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy
>> >>>> <ezhkr601 at student.liu.se> wrote:
>> >>>>>
>> >>>>> Hi Thanks!
>> >>>>>
>> >>>>> When I try to install Paraview,  I am getting the following error.
>> >>>>> Could some one please tell me how to fix this issue.
>> >>>>> I am trying to install the Paraview on a super computer to use it
>> >>>>> for remote rendering without using the GUI,  like with mesa support.
>> >>>>>
>> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD>
>> >>>>> git
>> >>>>> clone --recursive
>> >>>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
>> >>>>> Cloning into 'paraview-superbuild'...
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> remote: Counting objects: 6723, done.
>> >>>>> remote: Compressing objects: 100% (2459/2459), done.
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
>> >>>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
>> >>>>> Resolving deltas: 100% (4451/4451), done.
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> Checking out files: 100% (196/196), done.
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> Submodule 'superbuild'
>> >>>>> (https://gitlab.kitware.com/paraview/common-superbuild.git)
>> >>>>> registered for
>> >>>>> path 'superbuild'
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> Cloning into 'superbuild'...
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> remote: Counting objects: 6752, done.
>> >>>>> remote: Compressing objects: 100% (2235/2235), done.
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
>> >>>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
>> >>>>> Resolving deltas: 100% (4505/4505), done.
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> Submodule path 'superbuild': checked out
>> >>>>> '8f357bb5bf35419c210b3f9e0adbc9df08f565f2'
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>> warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission denied
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild>
>> >>>>> cmake .
>> >>>>> -- The C compiler identification is Intel 14.0.4.20140805
>> >>>>> -- The CXX compiler identification is Intel 14.0.4.20140805
>> >>>>> -- Cray Programming Environment 2.2.1 C
>> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
>> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc --
>> >>>>> works
>> >>>>> -- Detecting C compiler ABI info
>> >>>>> -- Detecting C compiler ABI info - done
>> >>>>> -- Detecting C compile features
>> >>>>> -- Detecting C compile features - done
>> >>>>> -- Cray Programming Environment 2.2.1 CXX
>> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
>> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC --
>> >>>>> works
>> >>>>> -- Detecting CXX compiler ABI info
>> >>>>> -- Detecting CXX compiler ABI info - done
>> >>>>> -- Detecting CXX compile features
>> >>>>> -- Detecting CXX compile features - done
>> >>>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242
>> >>>>> (message):
>> >>>>>   Failed to determine if the common superbuild is an old checkout.
>> >>>>> The
>> >>>>>   common superbuild may be out of date, but cannot be verified.:
>> >>>>> warning:
>> >>>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>> Permission
>> >>>>>   denied
>> >>>>>
>> >>>>>   warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>>   Permission denied
>> >>>>>
>> >>>>>   warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>>   Permission denied
>> >>>>>
>> >>>>>   warning: unable to access
>> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
>> >>>>>   Permission denied
>> >>>>>
>> >>>>>   error: unknown option `is-ancestor'
>> >>>>>
>> >>>>>   usage: git merge-base [-a|--all] <commit> <commit>...
>> >>>>>
>> >>>>>      or: git merge-base [-a|--all] --octopus <commit>...
>> >>>>>      or: git merge-base --independent <commit>...
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>       -a, --all             output all common ancestors
>> >>>>>       --octopus             find ancestors for a single n-way merge
>> >>>>>       --independent         list revs not reachable from others
>> >>>>> Call Stack (most recent call first):
>> >>>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
>> >>>>>
>> >>>>>
>> >>>>> -- Check size of void*
>> >>>>> -- Check size of void* - done
>> >>>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
>> >>>>> -- Determined source version for paraview: 5.4.0
>> >>>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289
>> >>>>> (message):
>> >>>>>   The build tree appears to be inside of the git repository located
>> >>>>> at
>> >>>>>
>> >>>>>
>> >>>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild.
>> >>>>>   This interferes with the way the superbuild applies patches to
>> >>>>> projects and
>> >>>>>   is not supported.  Please relocate the build tree to a directory
>> >>>>> which is
>> >>>>>   not under a git repository.
>> >>>>> Call Stack (most recent call first):
>> >>>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
>> >>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>> >>>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>> >>>>>
>> >>>>>
>> >>>>> -- Configuring incomplete, errors occurred!
>> >>>>> See also
>> >>>>>
>> >>>>> "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superbuild/CMakeFiles/CMakeOutput.log".
>> >>>>>
>> >>>>>
>> >>>>> Kind regards,
>> >>>>> Mathi
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
>> >>>>>> <ezhkr601 at student.liu.se> wrote:
>> >>>>>> > Hi,
>> >>>>>> >
>> >>>>>> > Can anyone please give me some instructions how to Paraview
>> >>>>>> > Superbuid
>> >>>>>> > to install and use them with out using the GUI (using the python
>> >>>>>> > script to
>> >>>>>> > render the images on the cluster or super computer).
>> >>>>>> >
>> >>>>>> > I see there are some instructions in here:
>> >>>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
>> >>>>>> >
>> >>>>>> > But I could not find any build instructions.
>> >>>>>>
>> >>>>>> Take a look again, that page includes the README.md file contents
>> >>>>>> which includes build instructions.
>> >>>>>>
>> >>>>>> To build without the GUI, you should just need to set the options
>> >>>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
>> >>>>>> ENABLE_python to ON.
>> >>>>>>
>> >>>>>> Best regards,
>> >>>>>> Cory
>> >>>>>>
>> >>>>>> >
>> >>>>>> > Kind regards,
>> >>>>>> > Mathi
>> >>>>>> >
>> >>>>>> > _______________________________________________
>> >>>>>> > 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&D 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
>> >>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Sun Jul  9 21:11:48 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 9 Jul 2017 21:11:48 -0400
Subject: [Paraview] Coloring isocontour by the coordinates outputted
 from a Transform filter and some other questions
In-Reply-To: <1e93335f-ae07-3c53-2836-c69dbfafc4b9@shuhaowu.com>
References: <d5d624cc-e171-f153-b1b6-47ee0a9b8068@shuhaowu.com>
 <CAB5Fpx4aKwctsmYnb+yhFyxtRok_c1CGt1shrTbTRF4iOrE+iw@mail.gmail.com>
 <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
 <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>
 <1e93335f-ae07-3c53-2836-c69dbfafc4b9@shuhaowu.com>
Message-ID: <CAB5Fpx66sawmJAGjE24RBh9=+vEubiW-x1QUUXHEALC7=AiKhg@mail.gmail.com>

Shuhao,

Unfortunately, the tooltips for the clip function parameters do not
appear to be working (I filed bug
https://gitlab.kitware.com/paraview/paraview/issues/17593 describing
the problem).

It turns out the properties for the Box clip type are defined in a way
that is a bit trickier than I thought. They are relative to the
bounding box of the input data:

* Position - center of the box function relative to the center of the
input dataset bounding box
* Rotation - Eulerian angles about the X, Y, and Z axes describing the
rotation of the bounding box
* Scale - non-uniform scale factor applied in x, y, and z relative to
the input dataset bounding box

Given how these items are defined, it will actually really be a pain
to compute the properties for an arbitrary x-, y-, and z-range.

The way you described earlier with a cascade of Calculator and
Threshold filters will work. Another way would be to use a single
Python Calculator with the expression

numpy.all((xmin <= inputs[0].Points[:,0], inputs[0].Points[:,0] <=
xmax, ymin <= inputs[0].Points[:,1], inputs[0].Points[:,1] <= ymax,
zmin <= inputs[0].Points[:,2], inputs[0].Points[:,2] <= zmax),
axis=0).astype('int')

and then Threshold by the result, which will be 0 outside [xmin, xmax,
ymin, ymax, zmin, zmax] and 1 inside it.

Thanks,
Cory



On Fri, Jul 7, 2017 at 10:51 AM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
> Is there documentation on how the Box clip type work? I'm not quite sure how
> to do the math to convert the threshold values to the position/scale values.
>
> Thanks,
> Shuhao
>
>
> On 2017-07-03 10:03 AM, Cory Quammen wrote:
>>
>> On Tue, Jun 20, 2017 at 9:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>
>>> Hello Cory,
>>>
>>> I've been playing around a little bit more and followed your suggestion
>>> with using the calculator to "expose" the transformed coordinates.
>>> However,
>>> my understanding is that this Calculator will duplicate the memory usage
>>> for that coordinate and be an additional step in the filtering process,
>>> slowing it down.
>>
>>
>>
>> Yes, that's true unfortunately. By the way, if you need X, Y, and Z, you
>> can use one Calculator filter to produce all three with the expression
>>
>> iHat*coordsX + jHat*coordsY + kHat*coordsZ
>>
>> This produces a 3-component array - you can then color your isosurface by
>> just one of the components or by the magnitude.
>>
>> I have to use the Calculator filter to expose all 3 coordinates before
>>>
>>> using a threshold to filter for only a subset region that I want to plt,
>>> which results in a filtering chain as follows:
>>>
>>> ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) ->
>>> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ
>>> (Threshold).
>>
>>
>>
>>>
>> This is 6 filters, which is very slow with my data set (>29M nodes in a
>>>
>>> rectlinear grid). Is there a way to speed this up?
>>>
>>>
>> You could instead use a Clip filter with Clip Type set to Box. You have to
>> do a little math to convert from your threshold values to the box Scale
>> and
>> Position properties, but it shouldn't be too bad, and will make your
>> pipeline simpler and faster.
>>
>> Cory
>>
>>
>>> Thanks,
>>> Shuhao
>>>
>>>
>>> On 2017-06-07 03:29 PM, Cory Quammen wrote:
>>>
>>>> Shuhao,
>>>>
>>>> Welcome to ParaView!
>>>>
>>>> On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> Is there a way to color an isocontour via the coordinates outputted
>>>>> from
>>>>> a
>>>>> Transform filter? I'm using the Transform filter to "normalize" my
>>>>> coordinate systems and I want to display the isocontour colored by the
>>>>> normalized Y coordinates. Do I have to create yet another Calculator
>>>>> filter
>>>>> to recalculate the normalized Y value that is already calculated by the
>>>>> Transform filter?
>>>>>
>>>>
>>>> There is currently no direct way to color surfaces by coordinate
>>>> value. You can, however, add a Calculator after the Transform filter
>>>> and simply set the expression to coordsY - no recomputation of the
>>>> normalization is needed. This will copy your normalized Y coordinate
>>>> values to a new array named "Result", and you can then color the
>>>> isosurface by "Result". "Result" is just the default name - you can
>>>> change it however you wish.
>>>>
>>>> Also: is there a way to turn off one axis on the axis grid (so turn off
>>>>>
>>>>> the
>>>>> Y axis display and leave only X and Z)?
>>>>>
>>>>
>>>> Click the Edit button next to the Axes Grid option. Click the gear
>>>> icon in the top right of the dialog that appears. Under Face
>>>> Properties, click on the "Faces to Render" combo box. Turn off the
>>>> sides you do not wish to see by selecting them in the combo box.
>>>>
>>>> What about changing the interval on
>>>>>
>>>>> the axis itself (instead of incrementing by 100 as it chooses,
>>>>> increment
>>>>> by
>>>>> 250).
>>>>>
>>>>
>>>> In the same dialog described above, check the "X Axis Use Custom
>>>> Labels", and you can specify exactly the labels you want. There is no
>>>> property to directly change the increment.
>>>>
>>>> Best,
>>>> Cory
>>>>
>>>> I'm pretty new to Paraview (coming from Tecplot). Please bear with me as
>>>> I
>>>>>
>>>>> likely will have more question.
>>>>>
>>>>> Thanks,
>>>>> Shuhao
>>>>> _______________________________________________
>>>>> 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&D Engineer
Kitware, Inc.

From shuhao at shuhaowu.com  Sun Jul  9 23:40:48 2017
From: shuhao at shuhaowu.com (Shuhao Wu)
Date: Sun, 9 Jul 2017 23:40:48 -0400
Subject: [Paraview] Coloring isocontour by the coordinates outputted
 from a Transform filter and some other questions
In-Reply-To: <CAB5Fpx66sawmJAGjE24RBh9=+vEubiW-x1QUUXHEALC7=AiKhg@mail.gmail.com>
References: <d5d624cc-e171-f153-b1b6-47ee0a9b8068@shuhaowu.com>
 <CAB5Fpx4aKwctsmYnb+yhFyxtRok_c1CGt1shrTbTRF4iOrE+iw@mail.gmail.com>
 <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
 <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>
 <1e93335f-ae07-3c53-2836-c69dbfafc4b9@shuhaowu.com>
 <CAB5Fpx66sawmJAGjE24RBh9=+vEubiW-x1QUUXHEALC7=AiKhg@mail.gmail.com>
Message-ID: <f8ace424-d1a1-4be0-6efd-fbef09a8b08d@shuhaowu.com>

Hello Cory,

Thanks for the advice. I will give this a shot. Are there also 
documentations to create custom filters? Not just ProgrammableFilters, 
but full on filters in something like a .py file (or any other language) 
that can be easily reused?

This will allow me to perform the transformation, expose the 
coordinates, and perform the clipping operations all in one step, which 
in theory should reduce the computational time and memory required as 
there would not be excessive amount copying between each stage of the 
pipeline.

I am only asking this because my dataset consists of ~30million nodes 
each time step and paraview runs somewhat slowly on my computer, taking 
about 30-70s to process a single timestamp in order to generate an image.

Thanks,
Shuhao

On 07/09/2017 09:11 PM, Cory Quammen wrote:
> Shuhao,
> 
> Unfortunately, the tooltips for the clip function parameters do not
> appear to be working (I filed bug
> https://gitlab.kitware.com/paraview/paraview/issues/17593 describing
> the problem).
> 
> It turns out the properties for the Box clip type are defined in a way
> that is a bit trickier than I thought. They are relative to the
> bounding box of the input data:
> 
> * Position - center of the box function relative to the center of the
> input dataset bounding box
> * Rotation - Eulerian angles about the X, Y, and Z axes describing the
> rotation of the bounding box
> * Scale - non-uniform scale factor applied in x, y, and z relative to
> the input dataset bounding box
> 
> Given how these items are defined, it will actually really be a pain
> to compute the properties for an arbitrary x-, y-, and z-range.
> 
> The way you described earlier with a cascade of Calculator and
> Threshold filters will work. Another way would be to use a single
> Python Calculator with the expression
> 
> numpy.all((xmin <= inputs[0].Points[:,0], inputs[0].Points[:,0] <=
> xmax, ymin <= inputs[0].Points[:,1], inputs[0].Points[:,1] <= ymax,
> zmin <= inputs[0].Points[:,2], inputs[0].Points[:,2] <= zmax),
> axis=0).astype('int')
> 
> and then Threshold by the result, which will be 0 outside [xmin, xmax,
> ymin, ymax, zmin, zmax] and 1 inside it.
> 
> Thanks,
> Cory
> 
> 
> 
> On Fri, Jul 7, 2017 at 10:51 AM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>> Is there documentation on how the Box clip type work? I'm not quite sure how
>> to do the math to convert the threshold values to the position/scale values.
>>
>> Thanks,
>> Shuhao
>>
>>
>> On 2017-07-03 10:03 AM, Cory Quammen wrote:
>>>
>>> On Tue, Jun 20, 2017 at 9:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>
>>>> Hello Cory,
>>>>
>>>> I've been playing around a little bit more and followed your suggestion
>>>> with using the calculator to "expose" the transformed coordinates.
>>>> However,
>>>> my understanding is that this Calculator will duplicate the memory usage
>>>> for that coordinate and be an additional step in the filtering process,
>>>> slowing it down.
>>>
>>>
>>>
>>> Yes, that's true unfortunately. By the way, if you need X, Y, and Z, you
>>> can use one Calculator filter to produce all three with the expression
>>>
>>> iHat*coordsX + jHat*coordsY + kHat*coordsZ
>>>
>>> This produces a 3-component array - you can then color your isosurface by
>>> just one of the components or by the magnitude.
>>>
>>> I have to use the Calculator filter to expose all 3 coordinates before
>>>>
>>>> using a threshold to filter for only a subset region that I want to plt,
>>>> which results in a filtering chain as follows:
>>>>
>>>> ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) ->
>>>> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ
>>>> (Threshold).
>>>
>>>
>>>
>>>>
>>> This is 6 filters, which is very slow with my data set (>29M nodes in a
>>>>
>>>> rectlinear grid). Is there a way to speed this up?
>>>>
>>>>
>>> You could instead use a Clip filter with Clip Type set to Box. You have to
>>> do a little math to convert from your threshold values to the box Scale
>>> and
>>> Position properties, but it shouldn't be too bad, and will make your
>>> pipeline simpler and faster.
>>>
>>> Cory
>>>
>>>
>>>> Thanks,
>>>> Shuhao
>>>>
>>>>
>>>> On 2017-06-07 03:29 PM, Cory Quammen wrote:
>>>>
>>>>> Shuhao,
>>>>>
>>>>> Welcome to ParaView!
>>>>>
>>>>> On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> Is there a way to color an isocontour via the coordinates outputted
>>>>>> from
>>>>>> a
>>>>>> Transform filter? I'm using the Transform filter to "normalize" my
>>>>>> coordinate systems and I want to display the isocontour colored by the
>>>>>> normalized Y coordinates. Do I have to create yet another Calculator
>>>>>> filter
>>>>>> to recalculate the normalized Y value that is already calculated by the
>>>>>> Transform filter?
>>>>>>
>>>>>
>>>>> There is currently no direct way to color surfaces by coordinate
>>>>> value. You can, however, add a Calculator after the Transform filter
>>>>> and simply set the expression to coordsY - no recomputation of the
>>>>> normalization is needed. This will copy your normalized Y coordinate
>>>>> values to a new array named "Result", and you can then color the
>>>>> isosurface by "Result". "Result" is just the default name - you can
>>>>> change it however you wish.
>>>>>
>>>>> Also: is there a way to turn off one axis on the axis grid (so turn off
>>>>>>
>>>>>> the
>>>>>> Y axis display and leave only X and Z)?
>>>>>>
>>>>>
>>>>> Click the Edit button next to the Axes Grid option. Click the gear
>>>>> icon in the top right of the dialog that appears. Under Face
>>>>> Properties, click on the "Faces to Render" combo box. Turn off the
>>>>> sides you do not wish to see by selecting them in the combo box.
>>>>>
>>>>> What about changing the interval on
>>>>>>
>>>>>> the axis itself (instead of incrementing by 100 as it chooses,
>>>>>> increment
>>>>>> by
>>>>>> 250).
>>>>>>
>>>>>
>>>>> In the same dialog described above, check the "X Axis Use Custom
>>>>> Labels", and you can specify exactly the labels you want. There is no
>>>>> property to directly change the increment.
>>>>>
>>>>> Best,
>>>>> Cory
>>>>>
>>>>> I'm pretty new to Paraview (coming from Tecplot). Please bear with me as
>>>>> I
>>>>>>
>>>>>> likely will have more question.
>>>>>>
>>>>>> Thanks,
>>>>>> Shuhao
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

From u.utku.turuncoglu at be.itu.edu.tr  Mon Jul 10 02:28:54 2017
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Mon, 10 Jul 2017 09:28:54 +0300 (EEST)
Subject: [Paraview] multiple visualization pipeline at a time with
 co-processing
In-Reply-To: <CAMaOp+HZkAq-sWP+dWWg5Wy3w7s38Y=0RQkLLNUPHpBsZLz9xQ@mail.gmail.com>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
 <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
 <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>
 <e707d3dd-870b-bc30-6e80-7922a6c0b70a@be.itu.edu.tr>
 <CAMaOp+HZkAq-sWP+dWWg5Wy3w7s38Y=0RQkLLNUPHpBsZLz9xQ@mail.gmail.com>
Message-ID: <63158.78.182.144.186.1499668134.squirrel@webmail.be.itu.edu.tr>

Hi Andy,

Thanks for your help. I think i found the problem. In my case, the
initialization code was something like following,

...
      vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
      for (int i = 0; i < *nscript; i++) {
        pipeline->Initialize(pythonScriptNames[i]);
        g_coprocessor->AddPipeline(pipeline);
      }
...

when i look at your test code i found that the pipeline variable is
created inside of the loop, which is the correct one. So, i change it like

...
      for (int i = 0; i < *nscript; i++) {
        vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
        pipeline->Initialize(pythonScriptNames[i]);
        g_coprocessor->AddPipeline(pipeline);
      }
...

and now it works without any problem. So, it was wrong usage of the
pointer (my mistake). Anyway, thanks again. BTW, the output of your test
script as follows,

--- OUTPUT ---
('SCRIPT1 RDD time ', 0.0, ' time step ', 0L)
('SCRIPT2 RDD time ', 0.0, ' time step ', 0L)
('SCRIPT1 RDD time ', 0.0, ' time step ', 0L)
('SCRIPT1 DCP time ', 0.0, ' time step ', 0L)
('SCRIPT2 RDD time ', 0.0, ' time step ', 0L)
('SCRIPT2 DCP time ', 0.0, ' time step ', 0L)
('SCRIPT1 RDD time ', 0.1, ' time step ', 1L)
('SCRIPT2 RDD time ', 0.1, ' time step ', 1L)
('SCRIPT1 RDD time ', 0.1, ' time step ', 1L)
('SCRIPT1 DCP time ', 0.1, ' time step ', 1L)
('SCRIPT2 RDD time ', 0.1, ' time step ', 1L)
('SCRIPT2 DCP time ', 0.1, ' time step ', 1L)
('SCRIPT1 RDD time ', 0.2, ' time step ', 2L)
('SCRIPT2 RDD time ', 0.2, ' time step ', 2L)
('SCRIPT1 RDD time ', 0.2, ' time step ', 2L)
('SCRIPT1 DCP time ', 0.2, ' time step ', 2L)
('SCRIPT2 RDD time ', 0.2, ' time step ', 2L)
('SCRIPT2 DCP time ', 0.2, ' time step ', 2L)
('SCRIPT1 RDD time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT2 RDD time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT1 RDD time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT1 DCP time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT2 RDD time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT2 DCP time ', 0.30000000000000004, ' time step ', 3L)
('SCRIPT1 RDD time ', 0.4, ' time step ', 4L)
('SCRIPT2 RDD time ', 0.4, ' time step ', 4L)
('SCRIPT1 RDD time ', 0.4, ' time step ', 4L)
('SCRIPT1 DCP time ', 0.4, ' time step ', 4L)
('SCRIPT2 RDD time ', 0.4, ' time step ', 4L)
('SCRIPT2 DCP time ', 0.4, ' time step ', 4L)
('SCRIPT1 RDD time ', 0.5, ' time step ', 5L)
('SCRIPT2 RDD time ', 0.5, ' time step ', 5L)
('SCRIPT1 RDD time ', 0.5, ' time step ', 5L)
('SCRIPT1 DCP time ', 0.5, ' time step ', 5L)
('SCRIPT2 RDD time ', 0.5, ' time step ', 5L)
('SCRIPT2 DCP time ', 0.5, ' time step ', 5L)
('SCRIPT1 RDD time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT2 RDD time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT1 RDD time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT1 DCP time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT2 RDD time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT2 DCP time ', 0.6000000000000001, ' time step ', 6L)
('SCRIPT1 RDD time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT2 RDD time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT1 RDD time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT1 DCP time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT2 RDD time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT2 DCP time ', 0.7000000000000001, ' time step ', 7L)
('SCRIPT1 RDD time ', 0.8, ' time step ', 8L)
('SCRIPT2 RDD time ', 0.8, ' time step ', 8L)
('SCRIPT1 RDD time ', 0.8, ' time step ', 8L)
('SCRIPT1 DCP time ', 0.8, ' time step ', 8L)
('SCRIPT2 RDD time ', 0.8, ' time step ', 8L)
('SCRIPT2 DCP time ', 0.8, ' time step ', 8L)
('SCRIPT1 RDD time ', 0.9, ' time step ', 9L)
('SCRIPT2 RDD time ', 0.9, ' time step ', 9L)
('SCRIPT1 RDD time ', 0.9, ' time step ', 9L)
('SCRIPT1 DCP time ', 0.9, ' time step ', 9L)
('SCRIPT2 RDD time ', 0.9, ' time step ', 9L)
('SCRIPT2 DCP time ', 0.9, ' time step ', 9L)
('SCRIPT1 RDD time ', 1.0, ' time step ', 10L)
('SCRIPT2 RDD time ', 1.0, ' time step ', 10L)
('SCRIPT1 RDD time ', 1.0, ' time step ', 10L)
('SCRIPT1 DCP time ', 1.0, ' time step ', 10L)
('SCRIPT2 RDD time ', 1.0, ' time step ', 10L)
('SCRIPT2 DCP time ', 1.0, ' time step ', 10L)
('SCRIPT1 RDD time ', 1.1, ' time step ', 11L)
('SCRIPT2 RDD time ', 1.1, ' time step ', 11L)
('SCRIPT1 RDD time ', 1.1, ' time step ', 11L)
('SCRIPT1 DCP time ', 1.1, ' time step ', 11L)
('SCRIPT2 RDD time ', 1.1, ' time step ', 11L)
('SCRIPT2 DCP time ', 1.1, ' time step ', 11L)
('SCRIPT1 RDD time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT2 RDD time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT1 RDD time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT1 DCP time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT2 RDD time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT2 DCP time ', 1.2000000000000002, ' time step ', 12L)
('SCRIPT1 RDD time ', 1.3, ' time step ', 13L)
('SCRIPT2 RDD time ', 1.3, ' time step ', 13L)
('SCRIPT1 RDD time ', 1.3, ' time step ', 13L)
('SCRIPT1 DCP time ', 1.3, ' time step ', 13L)
('SCRIPT2 RDD time ', 1.3, ' time step ', 13L)
('SCRIPT2 DCP time ', 1.3, ' time step ', 13L)
('SCRIPT1 RDD time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT2 RDD time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT1 RDD time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT1 DCP time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT2 RDD time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT2 DCP time ', 1.4000000000000001, ' time step ', 14L)
('SCRIPT1 RDD time ', 1.5, ' time step ', 15L)
('SCRIPT2 RDD time ', 1.5, ' time step ', 15L)
('SCRIPT1 RDD time ', 1.5, ' time step ', 15L)
('SCRIPT1 DCP time ', 1.5, ' time step ', 15L)
('SCRIPT2 RDD time ', 1.5, ' time step ', 15L)
('SCRIPT2 DCP time ', 1.5, ' time step ', 15L)
('SCRIPT1 RDD time ', 1.6, ' time step ', 16L)
('SCRIPT2 RDD time ', 1.6, ' time step ', 16L)
('SCRIPT1 RDD time ', 1.6, ' time step ', 16L)
('SCRIPT1 DCP time ', 1.6, ' time step ', 16L)
('SCRIPT2 RDD time ', 1.6, ' time step ', 16L)
('SCRIPT2 DCP time ', 1.6, ' time step ', 16L)
('SCRIPT1 RDD time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT2 RDD time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT1 RDD time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT1 DCP time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT2 RDD time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT2 DCP time ', 1.7000000000000002, ' time step ', 17L)
('SCRIPT1 RDD time ', 1.8, ' time step ', 18L)
('SCRIPT2 RDD time ', 1.8, ' time step ', 18L)
('SCRIPT1 RDD time ', 1.8, ' time step ', 18L)
('SCRIPT1 DCP time ', 1.8, ' time step ', 18L)
('SCRIPT2 RDD time ', 1.8, ' time step ', 18L)
('SCRIPT2 DCP time ', 1.8, ' time step ', 18L)
('SCRIPT1 RDD time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT2 RDD time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT1 RDD time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT1 DCP time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT2 RDD time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT2 DCP time ', 1.9000000000000001, ' time step ', 19L)
('SCRIPT1 RDD time ', 2.0, ' time step ', 20L)
('SCRIPT2 RDD time ', 2.0, ' time step ', 20L)
('SCRIPT1 RDD time ', 2.0, ' time step ', 20L)
('SCRIPT1 DCP time ', 2.0, ' time step ', 20L)
('SCRIPT2 RDD time ', 2.0, ' time step ', 20L)
('SCRIPT2 DCP time ', 2.0, ' time step ', 20L)
('SCRIPT1 RDD time ', 2.1, ' time step ', 21L)
('SCRIPT2 RDD time ', 2.1, ' time step ', 21L)
('SCRIPT1 RDD time ', 2.1, ' time step ', 21L)
('SCRIPT1 DCP time ', 2.1, ' time step ', 21L)
('SCRIPT2 RDD time ', 2.1, ' time step ', 21L)
('SCRIPT2 DCP time ', 2.1, ' time step ', 21L)
('SCRIPT1 RDD time ', 2.2, ' time step ', 22L)
('SCRIPT2 RDD time ', 2.2, ' time step ', 22L)
('SCRIPT1 RDD time ', 2.2, ' time step ', 22L)
('SCRIPT1 DCP time ', 2.2, ' time step ', 22L)
('SCRIPT2 RDD time ', 2.2, ' time step ', 22L)
('SCRIPT2 DCP time ', 2.2, ' time step ', 22L)
('SCRIPT1 RDD time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT2 RDD time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT1 RDD time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT1 DCP time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT2 RDD time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT2 DCP time ', 2.3000000000000003, ' time step ', 23L)
('SCRIPT1 RDD time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT2 RDD time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT1 RDD time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT1 DCP time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT2 RDD time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT2 DCP time ', 2.4000000000000004, ' time step ', 24L)
('SCRIPT1 RDD time ', 2.5, ' time step ', 25L)
('SCRIPT2 RDD time ', 2.5, ' time step ', 25L)
('SCRIPT1 RDD time ', 2.5, ' time step ', 25L)
('SCRIPT1 DCP time ', 2.5, ' time step ', 25L)
('SCRIPT2 RDD time ', 2.5, ' time step ', 25L)
('SCRIPT2 DCP time ', 2.5, ' time step ', 25L)
('SCRIPT1 RDD time ', 2.6, ' time step ', 26L)
('SCRIPT2 RDD time ', 2.6, ' time step ', 26L)
('SCRIPT1 RDD time ', 2.6, ' time step ', 26L)
('SCRIPT1 DCP time ', 2.6, ' time step ', 26L)
('SCRIPT2 RDD time ', 2.6, ' time step ', 26L)
('SCRIPT2 DCP time ', 2.6, ' time step ', 26L)
('SCRIPT1 RDD time ', 2.7, ' time step ', 27L)
('SCRIPT2 RDD time ', 2.7, ' time step ', 27L)
('SCRIPT1 RDD time ', 2.7, ' time step ', 27L)
('SCRIPT1 DCP time ', 2.7, ' time step ', 27L)
('SCRIPT2 RDD time ', 2.7, ' time step ', 27L)
('SCRIPT2 DCP time ', 2.7, ' time step ', 27L)
('SCRIPT1 RDD time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT2 RDD time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT1 RDD time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT1 DCP time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT2 RDD time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT2 DCP time ', 2.8000000000000003, ' time step ', 28L)
('SCRIPT1 RDD time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT2 RDD time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT1 RDD time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT1 DCP time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT2 RDD time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT2 DCP time ', 2.9000000000000004, ' time step ', 29L)
('SCRIPT1 RDD time ', 3.0, ' time step ', 30L)
('SCRIPT2 RDD time ', 3.0, ' time step ', 30L)
('SCRIPT1 RDD time ', 3.0, ' time step ', 30L)
('SCRIPT1 DCP time ', 3.0, ' time step ', 30L)
('SCRIPT2 RDD time ', 3.0, ' time step ', 30L)
('SCRIPT2 DCP time ', 3.0, ' time step ', 30L)
('SCRIPT1 RDD time ', 3.1, ' time step ', 31L)
('SCRIPT2 RDD time ', 3.1, ' time step ', 31L)
('SCRIPT1 RDD time ', 3.1, ' time step ', 31L)
('SCRIPT1 DCP time ', 3.1, ' time step ', 31L)
('SCRIPT2 RDD time ', 3.1, ' time step ', 31L)
('SCRIPT2 DCP time ', 3.1, ' time step ', 31L)
('SCRIPT1 RDD time ', 3.2, ' time step ', 32L)
('SCRIPT2 RDD time ', 3.2, ' time step ', 32L)
('SCRIPT1 RDD time ', 3.2, ' time step ', 32L)
('SCRIPT1 DCP time ', 3.2, ' time step ', 32L)
('SCRIPT2 RDD time ', 3.2, ' time step ', 32L)
('SCRIPT2 DCP time ', 3.2, ' time step ', 32L)
('SCRIPT1 RDD time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT2 RDD time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT1 RDD time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT1 DCP time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT2 RDD time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT2 DCP time ', 3.3000000000000003, ' time step ', 33L)
('SCRIPT1 RDD time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT2 RDD time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT1 RDD time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT1 DCP time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT2 RDD time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT2 DCP time ', 3.4000000000000004, ' time step ', 34L)
('SCRIPT1 RDD time ', 3.5, ' time step ', 35L)
('SCRIPT2 RDD time ', 3.5, ' time step ', 35L)
('SCRIPT1 RDD time ', 3.5, ' time step ', 35L)
('SCRIPT1 DCP time ', 3.5, ' time step ', 35L)
('SCRIPT2 RDD time ', 3.5, ' time step ', 35L)
('SCRIPT2 DCP time ', 3.5, ' time step ', 35L)
('SCRIPT1 RDD time ', 3.6, ' time step ', 36L)
('SCRIPT2 RDD time ', 3.6, ' time step ', 36L)
('SCRIPT1 RDD time ', 3.6, ' time step ', 36L)
('SCRIPT1 DCP time ', 3.6, ' time step ', 36L)
('SCRIPT2 RDD time ', 3.6, ' time step ', 36L)
('SCRIPT2 DCP time ', 3.6, ' time step ', 36L)
('SCRIPT1 RDD time ', 3.7, ' time step ', 37L)
('SCRIPT2 RDD time ', 3.7, ' time step ', 37L)
('SCRIPT1 RDD time ', 3.7, ' time step ', 37L)
('SCRIPT1 DCP time ', 3.7, ' time step ', 37L)
('SCRIPT2 RDD time ', 3.7, ' time step ', 37L)
('SCRIPT2 DCP time ', 3.7, ' time step ', 37L)
('SCRIPT1 RDD time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT2 RDD time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT1 RDD time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT1 DCP time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT2 RDD time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT2 DCP time ', 3.8000000000000003, ' time step ', 38L)
('SCRIPT1 RDD time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT2 RDD time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT1 RDD time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT1 DCP time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT2 RDD time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT2 DCP time ', 3.9000000000000004, ' time step ', 39L)
('SCRIPT1 RDD time ', 4.0, ' time step ', 40L)
('SCRIPT2 RDD time ', 4.0, ' time step ', 40L)
('SCRIPT1 RDD time ', 4.0, ' time step ', 40L)
('SCRIPT1 DCP time ', 4.0, ' time step ', 40L)
('SCRIPT2 RDD time ', 4.0, ' time step ', 40L)
('SCRIPT2 DCP time ', 4.0, ' time step ', 40L)
('SCRIPT1 RDD time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT2 RDD time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT1 RDD time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT1 DCP time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT2 RDD time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT2 DCP time ', 4.1000000000000005, ' time step ', 41L)
('SCRIPT1 RDD time ', 4.2, ' time step ', 42L)
('SCRIPT2 RDD time ', 4.2, ' time step ', 42L)
('SCRIPT1 RDD time ', 4.2, ' time step ', 42L)
('SCRIPT1 DCP time ', 4.2, ' time step ', 42L)
('SCRIPT2 RDD time ', 4.2, ' time step ', 42L)
('SCRIPT2 DCP time ', 4.2, ' time step ', 42L)
('SCRIPT1 RDD time ', 4.3, ' time step ', 43L)
('SCRIPT2 RDD time ', 4.3, ' time step ', 43L)
('SCRIPT1 RDD time ', 4.3, ' time step ', 43L)
('SCRIPT1 DCP time ', 4.3, ' time step ', 43L)
('SCRIPT2 RDD time ', 4.3, ' time step ', 43L)
('SCRIPT2 DCP time ', 4.3, ' time step ', 43L)
('SCRIPT1 RDD time ', 4.4, ' time step ', 44L)
('SCRIPT2 RDD time ', 4.4, ' time step ', 44L)
('SCRIPT1 RDD time ', 4.4, ' time step ', 44L)
('SCRIPT1 DCP time ', 4.4, ' time step ', 44L)
('SCRIPT2 RDD time ', 4.4, ' time step ', 44L)
('SCRIPT2 DCP time ', 4.4, ' time step ', 44L)
('SCRIPT1 RDD time ', 4.5, ' time step ', 45L)
('SCRIPT2 RDD time ', 4.5, ' time step ', 45L)
('SCRIPT1 RDD time ', 4.5, ' time step ', 45L)
('SCRIPT1 DCP time ', 4.5, ' time step ', 45L)
('SCRIPT2 RDD time ', 4.5, ' time step ', 45L)
('SCRIPT2 DCP time ', 4.5, ' time step ', 45L)
('SCRIPT1 RDD time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT2 RDD time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT1 RDD time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT1 DCP time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT2 RDD time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT2 DCP time ', 4.6000000000000005, ' time step ', 46L)
('SCRIPT1 RDD time ', 4.7, ' time step ', 47L)
('SCRIPT2 RDD time ', 4.7, ' time step ', 47L)
('SCRIPT1 RDD time ', 4.7, ' time step ', 47L)
('SCRIPT1 DCP time ', 4.7, ' time step ', 47L)
('SCRIPT2 RDD time ', 4.7, ' time step ', 47L)
('SCRIPT2 DCP time ', 4.7, ' time step ', 47L)
('SCRIPT1 RDD time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT2 RDD time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT1 RDD time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT1 DCP time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT2 RDD time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT2 DCP time ', 4.800000000000001, ' time step ', 48L)
('SCRIPT1 RDD time ', 4.9, ' time step ', 49L)
('SCRIPT2 RDD time ', 4.9, ' time step ', 49L)
('SCRIPT1 RDD time ', 4.9, ' time step ', 49L)
('SCRIPT1 DCP time ', 4.9, ' time step ', 49L)
('SCRIPT2 RDD time ', 4.9, ' time step ', 49L)
('SCRIPT2 DCP time ', 4.9, ' time step ', 49L)
('SCRIPT1 RDD time ', 5.0, ' time step ', 50L)
('SCRIPT2 RDD time ', 5.0, ' time step ', 50L)
('SCRIPT1 RDD time ', 5.0, ' time step ', 50L)
('SCRIPT1 DCP time ', 5.0, ' time step ', 50L)
('SCRIPT2 RDD time ', 5.0, ' time step ', 50L)
('SCRIPT2 DCP time ', 5.0, ' time step ', 50L)
('SCRIPT1 RDD time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT2 RDD time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT1 RDD time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT1 DCP time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT2 RDD time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT2 DCP time ', 5.1000000000000005, ' time step ', 51L)
('SCRIPT1 RDD time ', 5.2, ' time step ', 52L)
('SCRIPT2 RDD time ', 5.2, ' time step ', 52L)
('SCRIPT1 RDD time ', 5.2, ' time step ', 52L)
('SCRIPT1 DCP time ', 5.2, ' time step ', 52L)
('SCRIPT2 RDD time ', 5.2, ' time step ', 52L)
('SCRIPT2 DCP time ', 5.2, ' time step ', 52L)
('SCRIPT1 RDD time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT2 RDD time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT1 RDD time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT1 DCP time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT2 RDD time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT2 DCP time ', 5.300000000000001, ' time step ', 53L)
('SCRIPT1 RDD time ', 5.4, ' time step ', 54L)
('SCRIPT2 RDD time ', 5.4, ' time step ', 54L)
('SCRIPT1 RDD time ', 5.4, ' time step ', 54L)
('SCRIPT1 DCP time ', 5.4, ' time step ', 54L)
('SCRIPT2 RDD time ', 5.4, ' time step ', 54L)
('SCRIPT2 DCP time ', 5.4, ' time step ', 54L)
('SCRIPT1 RDD time ', 5.5, ' time step ', 55L)
('SCRIPT2 RDD time ', 5.5, ' time step ', 55L)
('SCRIPT1 RDD time ', 5.5, ' time step ', 55L)
('SCRIPT1 DCP time ', 5.5, ' time step ', 55L)
('SCRIPT2 RDD time ', 5.5, ' time step ', 55L)
('SCRIPT2 DCP time ', 5.5, ' time step ', 55L)
('SCRIPT1 RDD time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT2 RDD time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT1 RDD time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT1 DCP time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT2 RDD time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT2 DCP time ', 5.6000000000000005, ' time step ', 56L)
('SCRIPT1 RDD time ', 5.7, ' time step ', 57L)
('SCRIPT2 RDD time ', 5.7, ' time step ', 57L)
('SCRIPT1 RDD time ', 5.7, ' time step ', 57L)
('SCRIPT1 DCP time ', 5.7, ' time step ', 57L)
('SCRIPT2 RDD time ', 5.7, ' time step ', 57L)
('SCRIPT2 DCP time ', 5.7, ' time step ', 57L)
('SCRIPT1 RDD time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT2 RDD time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT1 RDD time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT1 DCP time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT2 RDD time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT2 DCP time ', 5.800000000000001, ' time step ', 58L)
('SCRIPT1 RDD time ', 5.9, ' time step ', 59L)
('SCRIPT2 RDD time ', 5.9, ' time step ', 59L)
('SCRIPT1 RDD time ', 5.9, ' time step ', 59L)
('SCRIPT1 DCP time ', 5.9, ' time step ', 59L)
('SCRIPT2 RDD time ', 5.9, ' time step ', 59L)
('SCRIPT2 DCP time ', 5.9, ' time step ', 59L)
('SCRIPT1 RDD time ', 6.0, ' time step ', 60L)
('SCRIPT2 RDD time ', 6.0, ' time step ', 60L)
('SCRIPT1 RDD time ', 6.0, ' time step ', 60L)
('SCRIPT1 DCP time ', 6.0, ' time step ', 60L)
('SCRIPT2 RDD time ', 6.0, ' time step ', 60L)
('SCRIPT2 DCP time ', 6.0, ' time step ', 60L)
('SCRIPT1 RDD time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT2 RDD time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT1 RDD time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT1 DCP time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT2 RDD time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT2 DCP time ', 6.1000000000000005, ' time step ', 61L)
('SCRIPT1 RDD time ', 6.2, ' time step ', 62L)
('SCRIPT2 RDD time ', 6.2, ' time step ', 62L)
('SCRIPT1 RDD time ', 6.2, ' time step ', 62L)
('SCRIPT1 DCP time ', 6.2, ' time step ', 62L)
('SCRIPT2 RDD time ', 6.2, ' time step ', 62L)
('SCRIPT2 DCP time ', 6.2, ' time step ', 62L)
('SCRIPT1 RDD time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT2 RDD time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT1 RDD time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT1 DCP time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT2 RDD time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT2 DCP time ', 6.300000000000001, ' time step ', 63L)
('SCRIPT1 RDD time ', 6.4, ' time step ', 64L)
('SCRIPT2 RDD time ', 6.4, ' time step ', 64L)
('SCRIPT1 RDD time ', 6.4, ' time step ', 64L)
('SCRIPT1 DCP time ', 6.4, ' time step ', 64L)
('SCRIPT2 RDD time ', 6.4, ' time step ', 64L)
('SCRIPT2 DCP time ', 6.4, ' time step ', 64L)
('SCRIPT1 RDD time ', 6.5, ' time step ', 65L)
('SCRIPT2 RDD time ', 6.5, ' time step ', 65L)
('SCRIPT1 RDD time ', 6.5, ' time step ', 65L)
('SCRIPT1 DCP time ', 6.5, ' time step ', 65L)
('SCRIPT2 RDD time ', 6.5, ' time step ', 65L)
('SCRIPT2 DCP time ', 6.5, ' time step ', 65L)
('SCRIPT1 RDD time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT2 RDD time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT1 RDD time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT1 DCP time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT2 RDD time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT2 DCP time ', 6.6000000000000005, ' time step ', 66L)
('SCRIPT1 RDD time ', 6.7, ' time step ', 67L)
('SCRIPT2 RDD time ', 6.7, ' time step ', 67L)
('SCRIPT1 RDD time ', 6.7, ' time step ', 67L)
('SCRIPT1 DCP time ', 6.7, ' time step ', 67L)
('SCRIPT2 RDD time ', 6.7, ' time step ', 67L)
('SCRIPT2 DCP time ', 6.7, ' time step ', 67L)
('SCRIPT1 RDD time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT2 RDD time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT1 RDD time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT1 DCP time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT2 RDD time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT2 DCP time ', 6.800000000000001, ' time step ', 68L)
('SCRIPT1 RDD time ', 6.9, ' time step ', 69L)
('SCRIPT2 RDD time ', 6.9, ' time step ', 69L)
('SCRIPT1 RDD time ', 6.9, ' time step ', 69L)
('SCRIPT1 DCP time ', 6.9, ' time step ', 69L)
('SCRIPT2 RDD time ', 6.9, ' time step ', 69L)
('SCRIPT2 DCP time ', 6.9, ' time step ', 69L)
('SCRIPT1 RDD time ', 7.0, ' time step ', 70L)
('SCRIPT2 RDD time ', 7.0, ' time step ', 70L)
('SCRIPT1 RDD time ', 7.0, ' time step ', 70L)
('SCRIPT1 DCP time ', 7.0, ' time step ', 70L)
('SCRIPT2 RDD time ', 7.0, ' time step ', 70L)
('SCRIPT2 DCP time ', 7.0, ' time step ', 70L)
('SCRIPT1 RDD time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT2 RDD time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT1 RDD time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT1 DCP time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT2 RDD time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT2 DCP time ', 7.1000000000000005, ' time step ', 71L)
('SCRIPT1 RDD time ', 7.2, ' time step ', 72L)
('SCRIPT2 RDD time ', 7.2, ' time step ', 72L)
('SCRIPT1 RDD time ', 7.2, ' time step ', 72L)
('SCRIPT1 DCP time ', 7.2, ' time step ', 72L)
('SCRIPT2 RDD time ', 7.2, ' time step ', 72L)
('SCRIPT2 DCP time ', 7.2, ' time step ', 72L)
('SCRIPT1 RDD time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT2 RDD time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT1 RDD time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT1 DCP time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT2 RDD time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT2 DCP time ', 7.300000000000001, ' time step ', 73L)
('SCRIPT1 RDD time ', 7.4, ' time step ', 74L)
('SCRIPT2 RDD time ', 7.4, ' time step ', 74L)
('SCRIPT1 RDD time ', 7.4, ' time step ', 74L)
('SCRIPT1 DCP time ', 7.4, ' time step ', 74L)
('SCRIPT2 RDD time ', 7.4, ' time step ', 74L)
('SCRIPT2 DCP time ', 7.4, ' time step ', 74L)
('SCRIPT1 RDD time ', 7.5, ' time step ', 75L)
('SCRIPT2 RDD time ', 7.5, ' time step ', 75L)
('SCRIPT1 RDD time ', 7.5, ' time step ', 75L)
('SCRIPT1 DCP time ', 7.5, ' time step ', 75L)
('SCRIPT2 RDD time ', 7.5, ' time step ', 75L)
('SCRIPT2 DCP time ', 7.5, ' time step ', 75L)
('SCRIPT1 RDD time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT2 RDD time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT1 RDD time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT1 DCP time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT2 RDD time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT2 DCP time ', 7.6000000000000005, ' time step ', 76L)
('SCRIPT1 RDD time ', 7.7, ' time step ', 77L)
('SCRIPT2 RDD time ', 7.7, ' time step ', 77L)
('SCRIPT1 RDD time ', 7.7, ' time step ', 77L)
('SCRIPT1 DCP time ', 7.7, ' time step ', 77L)
('SCRIPT2 RDD time ', 7.7, ' time step ', 77L)
('SCRIPT2 DCP time ', 7.7, ' time step ', 77L)
('SCRIPT1 RDD time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT2 RDD time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT1 RDD time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT1 DCP time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT2 RDD time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT2 DCP time ', 7.800000000000001, ' time step ', 78L)
('SCRIPT1 RDD time ', 7.9, ' time step ', 79L)
('SCRIPT2 RDD time ', 7.9, ' time step ', 79L)
('SCRIPT1 RDD time ', 7.9, ' time step ', 79L)
('SCRIPT1 DCP time ', 7.9, ' time step ', 79L)
('SCRIPT2 RDD time ', 7.9, ' time step ', 79L)
('SCRIPT2 DCP time ', 7.9, ' time step ', 79L)
('SCRIPT1 RDD time ', 8.0, ' time step ', 80L)
('SCRIPT2 RDD time ', 8.0, ' time step ', 80L)
('SCRIPT1 RDD time ', 8.0, ' time step ', 80L)
('SCRIPT1 DCP time ', 8.0, ' time step ', 80L)
('SCRIPT2 RDD time ', 8.0, ' time step ', 80L)
('SCRIPT2 DCP time ', 8.0, ' time step ', 80L)
('SCRIPT1 RDD time ', 8.1, ' time step ', 81L)
('SCRIPT2 RDD time ', 8.1, ' time step ', 81L)
('SCRIPT1 RDD time ', 8.1, ' time step ', 81L)
('SCRIPT1 DCP time ', 8.1, ' time step ', 81L)
('SCRIPT2 RDD time ', 8.1, ' time step ', 81L)
('SCRIPT2 DCP time ', 8.1, ' time step ', 81L)
('SCRIPT1 RDD time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT2 RDD time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT1 RDD time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT1 DCP time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT2 RDD time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT2 DCP time ', 8.200000000000001, ' time step ', 82L)
('SCRIPT1 RDD time ', 8.3, ' time step ', 83L)
('SCRIPT2 RDD time ', 8.3, ' time step ', 83L)
('SCRIPT1 RDD time ', 8.3, ' time step ', 83L)
('SCRIPT1 DCP time ', 8.3, ' time step ', 83L)
('SCRIPT2 RDD time ', 8.3, ' time step ', 83L)
('SCRIPT2 DCP time ', 8.3, ' time step ', 83L)
('SCRIPT1 RDD time ', 8.4, ' time step ', 84L)
('SCRIPT2 RDD time ', 8.4, ' time step ', 84L)
('SCRIPT1 RDD time ', 8.4, ' time step ', 84L)
('SCRIPT1 DCP time ', 8.4, ' time step ', 84L)
('SCRIPT2 RDD time ', 8.4, ' time step ', 84L)
('SCRIPT2 DCP time ', 8.4, ' time step ', 84L)
('SCRIPT1 RDD time ', 8.5, ' time step ', 85L)
('SCRIPT2 RDD time ', 8.5, ' time step ', 85L)
('SCRIPT1 RDD time ', 8.5, ' time step ', 85L)
('SCRIPT1 DCP time ', 8.5, ' time step ', 85L)
('SCRIPT2 RDD time ', 8.5, ' time step ', 85L)
('SCRIPT2 DCP time ', 8.5, ' time step ', 85L)
('SCRIPT1 RDD time ', 8.6, ' time step ', 86L)
('SCRIPT2 RDD time ', 8.6, ' time step ', 86L)
('SCRIPT1 RDD time ', 8.6, ' time step ', 86L)
('SCRIPT1 DCP time ', 8.6, ' time step ', 86L)
('SCRIPT2 RDD time ', 8.6, ' time step ', 86L)
('SCRIPT2 DCP time ', 8.6, ' time step ', 86L)
('SCRIPT1 RDD time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT2 RDD time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT1 RDD time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT1 DCP time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT2 RDD time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT2 DCP time ', 8.700000000000001, ' time step ', 87L)
('SCRIPT1 RDD time ', 8.8, ' time step ', 88L)
('SCRIPT2 RDD time ', 8.8, ' time step ', 88L)
('SCRIPT1 RDD time ', 8.8, ' time step ', 88L)
('SCRIPT1 DCP time ', 8.8, ' time step ', 88L)
('SCRIPT2 RDD time ', 8.8, ' time step ', 88L)
('SCRIPT2 DCP time ', 8.8, ' time step ', 88L)
('SCRIPT1 RDD time ', 8.9, ' time step ', 89L)
('SCRIPT2 RDD time ', 8.9, ' time step ', 89L)
('SCRIPT1 RDD time ', 8.9, ' time step ', 89L)
('SCRIPT1 DCP time ', 8.9, ' time step ', 89L)
('SCRIPT2 RDD time ', 8.9, ' time step ', 89L)
('SCRIPT2 DCP time ', 8.9, ' time step ', 89L)
('SCRIPT1 RDD time ', 9.0, ' time step ', 90L)
('SCRIPT2 RDD time ', 9.0, ' time step ', 90L)
('SCRIPT1 RDD time ', 9.0, ' time step ', 90L)
('SCRIPT1 DCP time ', 9.0, ' time step ', 90L)
('SCRIPT2 RDD time ', 9.0, ' time step ', 90L)
('SCRIPT2 DCP time ', 9.0, ' time step ', 90L)
('SCRIPT1 RDD time ', 9.1, ' time step ', 91L)
('SCRIPT2 RDD time ', 9.1, ' time step ', 91L)
('SCRIPT1 RDD time ', 9.1, ' time step ', 91L)
('SCRIPT1 DCP time ', 9.1, ' time step ', 91L)
('SCRIPT2 RDD time ', 9.1, ' time step ', 91L)
('SCRIPT2 DCP time ', 9.1, ' time step ', 91L)
('SCRIPT1 RDD time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT2 RDD time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT1 RDD time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT1 DCP time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT2 RDD time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT2 DCP time ', 9.200000000000001, ' time step ', 92L)
('SCRIPT1 RDD time ', 9.3, ' time step ', 93L)
('SCRIPT2 RDD time ', 9.3, ' time step ', 93L)
('SCRIPT1 RDD time ', 9.3, ' time step ', 93L)
('SCRIPT1 DCP time ', 9.3, ' time step ', 93L)
('SCRIPT2 RDD time ', 9.3, ' time step ', 93L)
('SCRIPT2 DCP time ', 9.3, ' time step ', 93L)
('SCRIPT1 RDD time ', 9.4, ' time step ', 94L)
('SCRIPT2 RDD time ', 9.4, ' time step ', 94L)
('SCRIPT1 RDD time ', 9.4, ' time step ', 94L)
('SCRIPT1 DCP time ', 9.4, ' time step ', 94L)
('SCRIPT2 RDD time ', 9.4, ' time step ', 94L)
('SCRIPT2 DCP time ', 9.4, ' time step ', 94L)
('SCRIPT1 RDD time ', 9.5, ' time step ', 95L)
('SCRIPT2 RDD time ', 9.5, ' time step ', 95L)
('SCRIPT1 RDD time ', 9.5, ' time step ', 95L)
('SCRIPT1 DCP time ', 9.5, ' time step ', 95L)
('SCRIPT2 RDD time ', 9.5, ' time step ', 95L)
('SCRIPT2 DCP time ', 9.5, ' time step ', 95L)
('SCRIPT1 RDD time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT2 RDD time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT1 RDD time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT1 DCP time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT2 RDD time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT2 DCP time ', 9.600000000000001, ' time step ', 96L)
('SCRIPT1 RDD time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT2 RDD time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT1 RDD time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT1 DCP time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT2 RDD time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT2 DCP time ', 9.700000000000001, ' time step ', 97L)
('SCRIPT1 RDD time ', 9.8, ' time step ', 98L)
('SCRIPT2 RDD time ', 9.8, ' time step ', 98L)
('SCRIPT1 RDD time ', 9.8, ' time step ', 98L)
('SCRIPT1 DCP time ', 9.8, ' time step ', 98L)
('SCRIPT2 RDD time ', 9.8, ' time step ', 98L)
('SCRIPT2 DCP time ', 9.8, ' time step ', 98L)
('SCRIPT1 DCP time ', 9.9, ' time step ', 99L)
('SCRIPT2 DCP time ', 9.9, ' time step ', 99L)


> Hi Ufuk,
>
> It's looking to me like the issue is in the adaptor some place. I tried
> running your scripts (modified slightly) with the CxxFullExample
> (./CxxFullExample script_1.py script_2.py) and was able to get image_s1*
> and image_s2* files out of it and did not see the warning you mention. I
> also modified that example to use atm_input2d instead of input for the
> input/grid identifier to make sure that wasn't the case. I've attached
> this
> example with the scripts modified to print out some debug information.
>
> Some questions (these are pretty basic things that you've probably already
> gotten working properly but maybe there's some small thing that was
> forgotten):
>
>    - Does your g_coprocessor only get created in your initialization
>    routine and deleted in the finalization step? That should not be
> created
>    and deleted during each in situ processing step.
>    - Do the vtkCPPythonScriptPipelines only get added during
>    initialization? They should not be added and removed from g_coprocessor
>    every time step.
>
> Also, could you try running with the scripts that I included in the
> cat.tgz
> tarball? The print statements there will print out the time and time steps
> during the simulation run to help me diagnose (both need to be increasing
> between calls to Catalyst). Also, if you share your adaptor code with me I
> can take a quick look.
>
> Cheers,
> Andy
>
>
>
> On Fri, Jul 7, 2017 at 7:30 AM, Ufuk Utku Turuncoglu (BE) <
> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Hi Andy,
>>
>> Strange! To test the idea and eliminate other problems i am using same
>> script twice with little mods (i just changed the name of the output png
>> file). So, if i pass script_1.py and script_2.py to the model, it gives
>> warning like before and creates output just for second script
>> (script_2.py). If i pass only one of them then the code is working
>> without
>> any problem and produces desired output.
>>
>> Thanks,
>> Regards,
>>
>> --ufuk
>>
>>
>>
>> On 06/07/2017 18:09, Andy Bauer wrote:
>>
>> Hi Ufuk,
>>
>> I'm guessing the issue is that the calls to Catalyst are not consistent.
>> Could you share your Python scripts? Also, did you modify them manually?
>>
>> I tried with PV 5.3. with the
>> ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/
>> example with the attached scripts simultaneously by running with
>> "./CxxFullExample doubleoutputs.py output3.py image11.py" and got the
>> correct output and no warnings.
>>
>> Cheers,
>> Andy
>>
>> On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE) <
>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>
>>> Hi Andy,
>>>
>>> I tested you suggestion about using multiple script in co-processing.
>>> In
>>> this case, i used following code in the adaptor side to add multiple
>>> pipeline
>>>
>>>       for (int i = 0; i < *nscript; i++) {
>>>         pipeline->Initialize(pythonScriptNames[i]);
>>>         g_coprocessor->AddPipeline(pipeline);
>>>       }
>>>
>>> When i run the simulation, i am getting following warning
>>>
>>> Warning: In
>>> /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaView
>>> Core/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 66
>>> vtkPVTrivialProducer (0x13816760): New time step is not after last time
>>> step.
>>>
>>> the output seems not correct and it is zoom out version of second
>>> pipeline (png file). The first pipeline is not even triggered. Do i
>>> missing
>>> something in here? BTW, i am using PV 5.3.
>>>
>>> Thanks,
>>>
>>> --ufuk
>>>
>>>
>>> On 16/05/2017 16:08, Andy Bauer wrote:
>>>
>>> Hi Ufuk,
>>>
>>> If you create a vtkCPythonScriptPipeline, when you initialize it with
>>> the
>>> script file name (which has to be done on each process) everything will
>>> be
>>> taken care of with respect to broadcasting the file contents from
>>> process 0
>>> to the others. We aren't sophisticated enough to parse the Python
>>> script to
>>> see if it imports other scripts that are not part of ParaView (e.g.
>>> paraview.simple) or Python (e.g. sys). That is why I recommended the
>>> first
>>> approach as opposed to the second approach above. Depending on the
>>> compute
>>> platform and how many MPI processes are in the run the difference may
>>> be
>>> negligible but having 100K processes or more trying to access the same
>>> file
>>> can seriously slow down an HPC machine.
>>>
>>> Cheers,
>>> Andy
>>>
>>> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE) <
>>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>>
>>>> Thanks Andy. That is exactly what i am looking for. The broadcasting
>>>> mechanism is not clear to me yet. Do i need to broadcast only the file
>>>> names? Anyway, i will try to implement it and see what is going on
>>>> there.
>>>>
>>>> Thanks again,
>>>> Regards,
>>>>
>>>> --ufuk
>>>>
>>>>
>>>> On 16/05/2017 14:58, Andy Bauer wrote:
>>>>
>>>> Hi Ufuk,
>>>>
>>>> Unless I'm not understanding your question correctly, I think you can
>>>> get what you want by adding in multiple vtkCPPythonScriptPipelines to
>>>> your
>>>> vtkCPProcessor object in your adaptor. Alternatively if you want to
>>>> have a
>>>> single, master Catalyst script handling other Catalyst scripts you can
>>>> do
>>>> something like the following:
>>>> ================
>>>> import script_a
>>>> import script_b
>>>> import script_c
>>>>
>>>> def RequestDataDescription(datadescription):
>>>>   script_a.RequestDataDescription(datadescription)
>>>>   script_b.RequestDataDescription(datadescription)
>>>>   script_c.RequestDataDescription(datadescription)
>>>>
>>>> def DoCoProcessing(datadescription):
>>>>   script_a.DoCoProcessing(datadescription)
>>>>   script_b.DoCoProcessing(datadescription)
>>>>   script_c.DoCoProcessing(datadescription)
>>>> ===================
>>>>
>>>> The first way is the recommended way though as that should be more
>>>> efficient by having process 0 read the scripts and broadcasting the
>>>> script
>>>> contents to the other  processes for use. The second method will only
>>>> do
>>>> that for the master script.
>>>>
>>>> Please let me know if this doesn't answer your question.
>>>>
>>>> Cheers,
>>>> Andy
>>>>
>>>> On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE) <
>>>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I just wonder that is it possible to trigger multiple visualization
>>>>> pipeline in the same time with co-processing. The co-processing
>>>>> script
>>>>> generator plugin mainly outputs only single pipeline at a time and
>>>>> that is
>>>>> fine but what about combining multiple Python script (generated by
>>>>> plugin)
>>>>> using higher level Python script to trigger multiple pipelines. So, i
>>>>> think
>>>>> that this will be much efficient way to look at different part of the
>>>>> data
>>>>> without writing to the disk. I am not sure but somebody else might do
>>>>> it
>>>>> before.
>>>>>
>>>>> Regards,
>>>>>
>>>>> --ufuk
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>


From darcy.beurle at ibnm.uni-hannover.de  Mon Jul 10 08:40:23 2017
From: darcy.beurle at ibnm.uni-hannover.de (Darcy Beurle)
Date: Mon, 10 Jul 2017 14:40:23 +0200
Subject: [Paraview]  Quadrature point data contours
In-Reply-To: <529F796D.6020400@lbl.gov>
Message-ID: <1499690423.29869.0.camel@ibnm.uni-hannover.de>

Hi,

Sorry if this has been covered before (I have attempted to read as much
as I can on this), but I am still having difficulties getting what I
want done.

I have a finite element model with data at the quadrature points, and I
wish to visualise these on a mesh (similar to nodal point values)
without having to extrapolate and average.????However the supplied
examples from other questions on this list do not seem to work properly
for my imagined use case.??There are no contours drawn for the
quadrature point data but the data is available in the spreadsheet
view.

The code to generate a file is attached.??My current method is to
import the data into Paraview and select 'Filters->Quadrature Points-
>Generate Quadrature Points.

Are there any restrictions to visualising quadrature point data???Will
there be contours shown if working correctly?

Suggestions on what is wrong here are appreciated.

Thanks in advance,
Darcy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/f2f6177e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: QuadTest.vtu
Type: application/x-paraview
Size: 2536 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/f2f6177e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Writer.cpp
Type: text/x-c++src
Size: 6601 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/f2f6177e/attachment.cpp>

From cory.quammen at kitware.com  Mon Jul 10 09:27:26 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 10 Jul 2017 09:27:26 -0400
Subject: [Paraview] Coloring isocontour by the coordinates outputted
 from a Transform filter and some other questions
In-Reply-To: <f8ace424-d1a1-4be0-6efd-fbef09a8b08d@shuhaowu.com>
References: <d5d624cc-e171-f153-b1b6-47ee0a9b8068@shuhaowu.com>
 <CAB5Fpx4aKwctsmYnb+yhFyxtRok_c1CGt1shrTbTRF4iOrE+iw@mail.gmail.com>
 <91a59f4c-54ab-6661-9252-25c50f30f1e6@shuhaowu.com>
 <CAB5Fpx59CFp74xqcG0yJhuX7g0Hee5rHANTE5DywwY89DzvP8w@mail.gmail.com>
 <1e93335f-ae07-3c53-2836-c69dbfafc4b9@shuhaowu.com>
 <CAB5Fpx66sawmJAGjE24RBh9=+vEubiW-x1QUUXHEALC7=AiKhg@mail.gmail.com>
 <f8ace424-d1a1-4be0-6efd-fbef09a8b08d@shuhaowu.com>
Message-ID: <CAB5Fpx7wHm07a_gBaD_LSL2Zfa==dFWRJ5Z0TMVkLwKb40S9Aw@mail.gmail.com>

Shuhao,

If you don't want to use the Programmable Filter, which is actually
pretty powerful and gives you access to just about all filters in VTK
(at least those that are compiled for ParaView), then your second-best
bet for what you want to do is to create a custom VTK filter and
include that as a ParaView plugin. The documentation for ParaView
plugins [1] should get you pretty far. Note that it is usually
necessary to compile ParaView first and then build your plugin against
that local ParaView build so that the compiler and ParaView build
options match between your ParaView executable and your plugin.

As for writing a custom VTK filter, often the best guide for writing a
VTK filter is looking at other existing VTK filters, especially those
that do things similar to what you want to do. It may take some
digging and questions on the mailing list, but that's actually a
fairly reasonable way to proceed. Kitware also offers courses on
demand if you want to get up to speed in a day or so.

Hope that helps,
Cory

[1] https://www.paraview.org/Wiki/ParaView/Plugin_HowTo

On Sun, Jul 9, 2017 at 11:40 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
> Hello Cory,
>
> Thanks for the advice. I will give this a shot. Are there also
> documentations to create custom filters? Not just ProgrammableFilters, but
> full on filters in something like a .py file (or any other language) that
> can be easily reused?
>
> This will allow me to perform the transformation, expose the coordinates,
> and perform the clipping operations all in one step, which in theory should
> reduce the computational time and memory required as there would not be
> excessive amount copying between each stage of the pipeline.
>
> I am only asking this because my dataset consists of ~30million nodes each
> time step and paraview runs somewhat slowly on my computer, taking about
> 30-70s to process a single timestamp in order to generate an image.
>
> Thanks,
> Shuhao
>
>
> On 07/09/2017 09:11 PM, Cory Quammen wrote:
>>
>> Shuhao,
>>
>> Unfortunately, the tooltips for the clip function parameters do not
>> appear to be working (I filed bug
>> https://gitlab.kitware.com/paraview/paraview/issues/17593 describing
>> the problem).
>>
>> It turns out the properties for the Box clip type are defined in a way
>> that is a bit trickier than I thought. They are relative to the
>> bounding box of the input data:
>>
>> * Position - center of the box function relative to the center of the
>> input dataset bounding box
>> * Rotation - Eulerian angles about the X, Y, and Z axes describing the
>> rotation of the bounding box
>> * Scale - non-uniform scale factor applied in x, y, and z relative to
>> the input dataset bounding box
>>
>> Given how these items are defined, it will actually really be a pain
>> to compute the properties for an arbitrary x-, y-, and z-range.
>>
>> The way you described earlier with a cascade of Calculator and
>> Threshold filters will work. Another way would be to use a single
>> Python Calculator with the expression
>>
>> numpy.all((xmin <= inputs[0].Points[:,0], inputs[0].Points[:,0] <=
>> xmax, ymin <= inputs[0].Points[:,1], inputs[0].Points[:,1] <= ymax,
>> zmin <= inputs[0].Points[:,2], inputs[0].Points[:,2] <= zmax),
>> axis=0).astype('int')
>>
>> and then Threshold by the result, which will be 0 outside [xmin, xmax,
>> ymin, ymax, zmin, zmax] and 1 inside it.
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Fri, Jul 7, 2017 at 10:51 AM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>
>>> Is there documentation on how the Box clip type work? I'm not quite sure
>>> how
>>> to do the math to convert the threshold values to the position/scale
>>> values.
>>>
>>> Thanks,
>>> Shuhao
>>>
>>>
>>> On 2017-07-03 10:03 AM, Cory Quammen wrote:
>>>>
>>>>
>>>> On Tue, Jun 20, 2017 at 9:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>>
>>>>> Hello Cory,
>>>>>
>>>>> I've been playing around a little bit more and followed your suggestion
>>>>> with using the calculator to "expose" the transformed coordinates.
>>>>> However,
>>>>> my understanding is that this Calculator will duplicate the memory
>>>>> usage
>>>>> for that coordinate and be an additional step in the filtering process,
>>>>> slowing it down.
>>>>
>>>>
>>>>
>>>>
>>>> Yes, that's true unfortunately. By the way, if you need X, Y, and Z, you
>>>> can use one Calculator filter to produce all three with the expression
>>>>
>>>> iHat*coordsX + jHat*coordsY + kHat*coordsZ
>>>>
>>>> This produces a 3-component array - you can then color your isosurface
>>>> by
>>>> just one of the components or by the magnitude.
>>>>
>>>> I have to use the Calculator filter to expose all 3 coordinates before
>>>>>
>>>>>
>>>>> using a threshold to filter for only a subset region that I want to
>>>>> plt,
>>>>> which results in a filtering chain as follows:
>>>>>
>>>>> ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) ->
>>>>> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ
>>>>> (Threshold).
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>> This is 6 filters, which is very slow with my data set (>29M nodes in a
>>>>>
>>>>>
>>>>> rectlinear grid). Is there a way to speed this up?
>>>>>
>>>>>
>>>> You could instead use a Clip filter with Clip Type set to Box. You have
>>>> to
>>>> do a little math to convert from your threshold values to the box Scale
>>>> and
>>>> Position properties, but it shouldn't be too bad, and will make your
>>>> pipeline simpler and faster.
>>>>
>>>> Cory
>>>>
>>>>
>>>>> Thanks,
>>>>> Shuhao
>>>>>
>>>>>
>>>>> On 2017-06-07 03:29 PM, Cory Quammen wrote:
>>>>>
>>>>>> Shuhao,
>>>>>>
>>>>>> Welcome to ParaView!
>>>>>>
>>>>>> On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu <shuhao at shuhaowu.com> wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>> Is there a way to color an isocontour via the coordinates outputted
>>>>>>> from
>>>>>>> a
>>>>>>> Transform filter? I'm using the Transform filter to "normalize" my
>>>>>>> coordinate systems and I want to display the isocontour colored by
>>>>>>> the
>>>>>>> normalized Y coordinates. Do I have to create yet another Calculator
>>>>>>> filter
>>>>>>> to recalculate the normalized Y value that is already calculated by
>>>>>>> the
>>>>>>> Transform filter?
>>>>>>>
>>>>>>
>>>>>> There is currently no direct way to color surfaces by coordinate
>>>>>> value. You can, however, add a Calculator after the Transform filter
>>>>>> and simply set the expression to coordsY - no recomputation of the
>>>>>> normalization is needed. This will copy your normalized Y coordinate
>>>>>> values to a new array named "Result", and you can then color the
>>>>>> isosurface by "Result". "Result" is just the default name - you can
>>>>>> change it however you wish.
>>>>>>
>>>>>> Also: is there a way to turn off one axis on the axis grid (so turn
>>>>>> off
>>>>>>>
>>>>>>>
>>>>>>> the
>>>>>>> Y axis display and leave only X and Z)?
>>>>>>>
>>>>>>
>>>>>> Click the Edit button next to the Axes Grid option. Click the gear
>>>>>> icon in the top right of the dialog that appears. Under Face
>>>>>> Properties, click on the "Faces to Render" combo box. Turn off the
>>>>>> sides you do not wish to see by selecting them in the combo box.
>>>>>>
>>>>>> What about changing the interval on
>>>>>>>
>>>>>>>
>>>>>>> the axis itself (instead of incrementing by 100 as it chooses,
>>>>>>> increment
>>>>>>> by
>>>>>>> 250).
>>>>>>>
>>>>>>
>>>>>> In the same dialog described above, check the "X Axis Use Custom
>>>>>> Labels", and you can specify exactly the labels you want. There is no
>>>>>> property to directly change the increment.
>>>>>>
>>>>>> Best,
>>>>>> Cory
>>>>>>
>>>>>> I'm pretty new to Paraview (coming from Tecplot). Please bear with me
>>>>>> as
>>>>>> I
>>>>>>>
>>>>>>>
>>>>>>> likely will have more question.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Shuhao
>>>>>>> _______________________________________________
>>>>>>> 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&D Engineer
Kitware, Inc.

From manuel.schoelling at dzne.de  Mon Jul 10 09:57:28 2017
From: manuel.schoelling at dzne.de (Manuel =?ISO-8859-1?Q?Sch=F6lling?=)
Date: Mon, 10 Jul 2017 15:57:28 +0200
Subject: [Paraview] Clipping using a Surface
Message-ID: <1499695048.5139.64.camel@dzne.de>

Hi,

I have a surface surrounding a volume and I have polygonal mesh (.vtk
files).

Now I would like to cut off the part of the polygonal mesh that is
outside of this volume. I tried to play around a bit with the clipping
tools but I could not figure out how to do this.

Your help would be very much appreciated!

Thanks,

Manuel



From andy.bauer at kitware.com  Mon Jul 10 10:13:16 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 10 Jul 2017 10:13:16 -0400
Subject: [Paraview] multiple visualization pipeline at a time with
	co-processing
In-Reply-To: <63158.78.182.144.186.1499668134.squirrel@webmail.be.itu.edu.tr>
References: <b2424dbb-5ede-27d5-4598-3542dad959c9@be.itu.edu.tr>
 <CAMaOp+ETKOv4obxnETCg2JE=2OfofHK+PO1BFWiG+Sv+97p+vA@mail.gmail.com>
 <83062745-e4b9-34f6-3941-82b22aaca2a8@be.itu.edu.tr>
 <CAMaOp+FC4K8xirZMie3M5_J5S1w=CcBmzBjAzdNXN7s+Tweb8Q@mail.gmail.com>
 <f6c02c17-91aa-ff75-a9c5-c6eec559d4f7@be.itu.edu.tr>
 <CAMaOp+GjHPpkR+Oprifa0bn3Rv29zW4uyHtUx6zv_DHMrKFfpg@mail.gmail.com>
 <e707d3dd-870b-bc30-6e80-7922a6c0b70a@be.itu.edu.tr>
 <CAMaOp+HZkAq-sWP+dWWg5Wy3w7s38Y=0RQkLLNUPHpBsZLz9xQ@mail.gmail.com>
 <63158.78.182.144.186.1499668134.squirrel@webmail.be.itu.edu.tr>
Message-ID: <CAMaOp+EfKSyOtf+x+WBFUUxRpke44TrWDdW8OHr+7zDrwZKATw@mail.gmail.com>

Glad to hear it's working properly now! I figured it was something quite
subtle but not overly complex to fix once the issue was found.

On Mon, Jul 10, 2017 at 2:28 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Andy,
>
> Thanks for your help. I think i found the problem. In my case, the
> initialization code was something like following,
>
> ...
>       vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
>       for (int i = 0; i < *nscript; i++) {
>         pipeline->Initialize(pythonScriptNames[i]);
>         g_coprocessor->AddPipeline(pipeline);
>       }
> ...
>
> when i look at your test code i found that the pipeline variable is
> created inside of the loop, which is the correct one. So, i change it like
>
> ...
>       for (int i = 0; i < *nscript; i++) {
>         vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
>         pipeline->Initialize(pythonScriptNames[i]);
>         g_coprocessor->AddPipeline(pipeline);
>       }
> ...
>
> and now it works without any problem. So, it was wrong usage of the
> pointer (my mistake). Anyway, thanks again. BTW, the output of your test
> script as follows,
>
> --- OUTPUT ---
> ('SCRIPT1 RDD time ', 0.0, ' time step ', 0L)
> ('SCRIPT2 RDD time ', 0.0, ' time step ', 0L)
> ('SCRIPT1 RDD time ', 0.0, ' time step ', 0L)
> ('SCRIPT1 DCP time ', 0.0, ' time step ', 0L)
> ('SCRIPT2 RDD time ', 0.0, ' time step ', 0L)
> ('SCRIPT2 DCP time ', 0.0, ' time step ', 0L)
> ('SCRIPT1 RDD time ', 0.1, ' time step ', 1L)
> ('SCRIPT2 RDD time ', 0.1, ' time step ', 1L)
> ('SCRIPT1 RDD time ', 0.1, ' time step ', 1L)
> ('SCRIPT1 DCP time ', 0.1, ' time step ', 1L)
> ('SCRIPT2 RDD time ', 0.1, ' time step ', 1L)
> ('SCRIPT2 DCP time ', 0.1, ' time step ', 1L)
> ('SCRIPT1 RDD time ', 0.2, ' time step ', 2L)
> ('SCRIPT2 RDD time ', 0.2, ' time step ', 2L)
> ('SCRIPT1 RDD time ', 0.2, ' time step ', 2L)
> ('SCRIPT1 DCP time ', 0.2, ' time step ', 2L)
> ('SCRIPT2 RDD time ', 0.2, ' time step ', 2L)
> ('SCRIPT2 DCP time ', 0.2, ' time step ', 2L)
> ('SCRIPT1 RDD time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT2 RDD time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT1 RDD time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT1 DCP time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT2 RDD time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT2 DCP time ', 0.30000000000000004, ' time step ', 3L)
> ('SCRIPT1 RDD time ', 0.4, ' time step ', 4L)
> ('SCRIPT2 RDD time ', 0.4, ' time step ', 4L)
> ('SCRIPT1 RDD time ', 0.4, ' time step ', 4L)
> ('SCRIPT1 DCP time ', 0.4, ' time step ', 4L)
> ('SCRIPT2 RDD time ', 0.4, ' time step ', 4L)
> ('SCRIPT2 DCP time ', 0.4, ' time step ', 4L)
> ('SCRIPT1 RDD time ', 0.5, ' time step ', 5L)
> ('SCRIPT2 RDD time ', 0.5, ' time step ', 5L)
> ('SCRIPT1 RDD time ', 0.5, ' time step ', 5L)
> ('SCRIPT1 DCP time ', 0.5, ' time step ', 5L)
> ('SCRIPT2 RDD time ', 0.5, ' time step ', 5L)
> ('SCRIPT2 DCP time ', 0.5, ' time step ', 5L)
> ('SCRIPT1 RDD time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT2 RDD time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT1 RDD time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT1 DCP time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT2 RDD time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT2 DCP time ', 0.6000000000000001, ' time step ', 6L)
> ('SCRIPT1 RDD time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT2 RDD time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT1 RDD time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT1 DCP time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT2 RDD time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT2 DCP time ', 0.7000000000000001, ' time step ', 7L)
> ('SCRIPT1 RDD time ', 0.8, ' time step ', 8L)
> ('SCRIPT2 RDD time ', 0.8, ' time step ', 8L)
> ('SCRIPT1 RDD time ', 0.8, ' time step ', 8L)
> ('SCRIPT1 DCP time ', 0.8, ' time step ', 8L)
> ('SCRIPT2 RDD time ', 0.8, ' time step ', 8L)
> ('SCRIPT2 DCP time ', 0.8, ' time step ', 8L)
> ('SCRIPT1 RDD time ', 0.9, ' time step ', 9L)
> ('SCRIPT2 RDD time ', 0.9, ' time step ', 9L)
> ('SCRIPT1 RDD time ', 0.9, ' time step ', 9L)
> ('SCRIPT1 DCP time ', 0.9, ' time step ', 9L)
> ('SCRIPT2 RDD time ', 0.9, ' time step ', 9L)
> ('SCRIPT2 DCP time ', 0.9, ' time step ', 9L)
> ('SCRIPT1 RDD time ', 1.0, ' time step ', 10L)
> ('SCRIPT2 RDD time ', 1.0, ' time step ', 10L)
> ('SCRIPT1 RDD time ', 1.0, ' time step ', 10L)
> ('SCRIPT1 DCP time ', 1.0, ' time step ', 10L)
> ('SCRIPT2 RDD time ', 1.0, ' time step ', 10L)
> ('SCRIPT2 DCP time ', 1.0, ' time step ', 10L)
> ('SCRIPT1 RDD time ', 1.1, ' time step ', 11L)
> ('SCRIPT2 RDD time ', 1.1, ' time step ', 11L)
> ('SCRIPT1 RDD time ', 1.1, ' time step ', 11L)
> ('SCRIPT1 DCP time ', 1.1, ' time step ', 11L)
> ('SCRIPT2 RDD time ', 1.1, ' time step ', 11L)
> ('SCRIPT2 DCP time ', 1.1, ' time step ', 11L)
> ('SCRIPT1 RDD time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT2 RDD time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT1 RDD time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT1 DCP time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT2 RDD time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT2 DCP time ', 1.2000000000000002, ' time step ', 12L)
> ('SCRIPT1 RDD time ', 1.3, ' time step ', 13L)
> ('SCRIPT2 RDD time ', 1.3, ' time step ', 13L)
> ('SCRIPT1 RDD time ', 1.3, ' time step ', 13L)
> ('SCRIPT1 DCP time ', 1.3, ' time step ', 13L)
> ('SCRIPT2 RDD time ', 1.3, ' time step ', 13L)
> ('SCRIPT2 DCP time ', 1.3, ' time step ', 13L)
> ('SCRIPT1 RDD time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT2 RDD time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT1 RDD time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT1 DCP time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT2 RDD time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT2 DCP time ', 1.4000000000000001, ' time step ', 14L)
> ('SCRIPT1 RDD time ', 1.5, ' time step ', 15L)
> ('SCRIPT2 RDD time ', 1.5, ' time step ', 15L)
> ('SCRIPT1 RDD time ', 1.5, ' time step ', 15L)
> ('SCRIPT1 DCP time ', 1.5, ' time step ', 15L)
> ('SCRIPT2 RDD time ', 1.5, ' time step ', 15L)
> ('SCRIPT2 DCP time ', 1.5, ' time step ', 15L)
> ('SCRIPT1 RDD time ', 1.6, ' time step ', 16L)
> ('SCRIPT2 RDD time ', 1.6, ' time step ', 16L)
> ('SCRIPT1 RDD time ', 1.6, ' time step ', 16L)
> ('SCRIPT1 DCP time ', 1.6, ' time step ', 16L)
> ('SCRIPT2 RDD time ', 1.6, ' time step ', 16L)
> ('SCRIPT2 DCP time ', 1.6, ' time step ', 16L)
> ('SCRIPT1 RDD time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT2 RDD time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT1 RDD time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT1 DCP time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT2 RDD time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT2 DCP time ', 1.7000000000000002, ' time step ', 17L)
> ('SCRIPT1 RDD time ', 1.8, ' time step ', 18L)
> ('SCRIPT2 RDD time ', 1.8, ' time step ', 18L)
> ('SCRIPT1 RDD time ', 1.8, ' time step ', 18L)
> ('SCRIPT1 DCP time ', 1.8, ' time step ', 18L)
> ('SCRIPT2 RDD time ', 1.8, ' time step ', 18L)
> ('SCRIPT2 DCP time ', 1.8, ' time step ', 18L)
> ('SCRIPT1 RDD time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT2 RDD time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT1 RDD time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT1 DCP time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT2 RDD time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT2 DCP time ', 1.9000000000000001, ' time step ', 19L)
> ('SCRIPT1 RDD time ', 2.0, ' time step ', 20L)
> ('SCRIPT2 RDD time ', 2.0, ' time step ', 20L)
> ('SCRIPT1 RDD time ', 2.0, ' time step ', 20L)
> ('SCRIPT1 DCP time ', 2.0, ' time step ', 20L)
> ('SCRIPT2 RDD time ', 2.0, ' time step ', 20L)
> ('SCRIPT2 DCP time ', 2.0, ' time step ', 20L)
> ('SCRIPT1 RDD time ', 2.1, ' time step ', 21L)
> ('SCRIPT2 RDD time ', 2.1, ' time step ', 21L)
> ('SCRIPT1 RDD time ', 2.1, ' time step ', 21L)
> ('SCRIPT1 DCP time ', 2.1, ' time step ', 21L)
> ('SCRIPT2 RDD time ', 2.1, ' time step ', 21L)
> ('SCRIPT2 DCP time ', 2.1, ' time step ', 21L)
> ('SCRIPT1 RDD time ', 2.2, ' time step ', 22L)
> ('SCRIPT2 RDD time ', 2.2, ' time step ', 22L)
> ('SCRIPT1 RDD time ', 2.2, ' time step ', 22L)
> ('SCRIPT1 DCP time ', 2.2, ' time step ', 22L)
> ('SCRIPT2 RDD time ', 2.2, ' time step ', 22L)
> ('SCRIPT2 DCP time ', 2.2, ' time step ', 22L)
> ('SCRIPT1 RDD time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT2 RDD time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT1 RDD time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT1 DCP time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT2 RDD time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT2 DCP time ', 2.3000000000000003, ' time step ', 23L)
> ('SCRIPT1 RDD time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT2 RDD time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT1 RDD time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT1 DCP time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT2 RDD time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT2 DCP time ', 2.4000000000000004, ' time step ', 24L)
> ('SCRIPT1 RDD time ', 2.5, ' time step ', 25L)
> ('SCRIPT2 RDD time ', 2.5, ' time step ', 25L)
> ('SCRIPT1 RDD time ', 2.5, ' time step ', 25L)
> ('SCRIPT1 DCP time ', 2.5, ' time step ', 25L)
> ('SCRIPT2 RDD time ', 2.5, ' time step ', 25L)
> ('SCRIPT2 DCP time ', 2.5, ' time step ', 25L)
> ('SCRIPT1 RDD time ', 2.6, ' time step ', 26L)
> ('SCRIPT2 RDD time ', 2.6, ' time step ', 26L)
> ('SCRIPT1 RDD time ', 2.6, ' time step ', 26L)
> ('SCRIPT1 DCP time ', 2.6, ' time step ', 26L)
> ('SCRIPT2 RDD time ', 2.6, ' time step ', 26L)
> ('SCRIPT2 DCP time ', 2.6, ' time step ', 26L)
> ('SCRIPT1 RDD time ', 2.7, ' time step ', 27L)
> ('SCRIPT2 RDD time ', 2.7, ' time step ', 27L)
> ('SCRIPT1 RDD time ', 2.7, ' time step ', 27L)
> ('SCRIPT1 DCP time ', 2.7, ' time step ', 27L)
> ('SCRIPT2 RDD time ', 2.7, ' time step ', 27L)
> ('SCRIPT2 DCP time ', 2.7, ' time step ', 27L)
> ('SCRIPT1 RDD time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT2 RDD time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT1 RDD time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT1 DCP time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT2 RDD time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT2 DCP time ', 2.8000000000000003, ' time step ', 28L)
> ('SCRIPT1 RDD time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT2 RDD time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT1 RDD time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT1 DCP time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT2 RDD time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT2 DCP time ', 2.9000000000000004, ' time step ', 29L)
> ('SCRIPT1 RDD time ', 3.0, ' time step ', 30L)
> ('SCRIPT2 RDD time ', 3.0, ' time step ', 30L)
> ('SCRIPT1 RDD time ', 3.0, ' time step ', 30L)
> ('SCRIPT1 DCP time ', 3.0, ' time step ', 30L)
> ('SCRIPT2 RDD time ', 3.0, ' time step ', 30L)
> ('SCRIPT2 DCP time ', 3.0, ' time step ', 30L)
> ('SCRIPT1 RDD time ', 3.1, ' time step ', 31L)
> ('SCRIPT2 RDD time ', 3.1, ' time step ', 31L)
> ('SCRIPT1 RDD time ', 3.1, ' time step ', 31L)
> ('SCRIPT1 DCP time ', 3.1, ' time step ', 31L)
> ('SCRIPT2 RDD time ', 3.1, ' time step ', 31L)
> ('SCRIPT2 DCP time ', 3.1, ' time step ', 31L)
> ('SCRIPT1 RDD time ', 3.2, ' time step ', 32L)
> ('SCRIPT2 RDD time ', 3.2, ' time step ', 32L)
> ('SCRIPT1 RDD time ', 3.2, ' time step ', 32L)
> ('SCRIPT1 DCP time ', 3.2, ' time step ', 32L)
> ('SCRIPT2 RDD time ', 3.2, ' time step ', 32L)
> ('SCRIPT2 DCP time ', 3.2, ' time step ', 32L)
> ('SCRIPT1 RDD time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT2 RDD time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT1 RDD time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT1 DCP time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT2 RDD time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT2 DCP time ', 3.3000000000000003, ' time step ', 33L)
> ('SCRIPT1 RDD time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT2 RDD time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT1 RDD time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT1 DCP time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT2 RDD time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT2 DCP time ', 3.4000000000000004, ' time step ', 34L)
> ('SCRIPT1 RDD time ', 3.5, ' time step ', 35L)
> ('SCRIPT2 RDD time ', 3.5, ' time step ', 35L)
> ('SCRIPT1 RDD time ', 3.5, ' time step ', 35L)
> ('SCRIPT1 DCP time ', 3.5, ' time step ', 35L)
> ('SCRIPT2 RDD time ', 3.5, ' time step ', 35L)
> ('SCRIPT2 DCP time ', 3.5, ' time step ', 35L)
> ('SCRIPT1 RDD time ', 3.6, ' time step ', 36L)
> ('SCRIPT2 RDD time ', 3.6, ' time step ', 36L)
> ('SCRIPT1 RDD time ', 3.6, ' time step ', 36L)
> ('SCRIPT1 DCP time ', 3.6, ' time step ', 36L)
> ('SCRIPT2 RDD time ', 3.6, ' time step ', 36L)
> ('SCRIPT2 DCP time ', 3.6, ' time step ', 36L)
> ('SCRIPT1 RDD time ', 3.7, ' time step ', 37L)
> ('SCRIPT2 RDD time ', 3.7, ' time step ', 37L)
> ('SCRIPT1 RDD time ', 3.7, ' time step ', 37L)
> ('SCRIPT1 DCP time ', 3.7, ' time step ', 37L)
> ('SCRIPT2 RDD time ', 3.7, ' time step ', 37L)
> ('SCRIPT2 DCP time ', 3.7, ' time step ', 37L)
> ('SCRIPT1 RDD time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT2 RDD time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT1 RDD time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT1 DCP time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT2 RDD time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT2 DCP time ', 3.8000000000000003, ' time step ', 38L)
> ('SCRIPT1 RDD time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT2 RDD time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT1 RDD time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT1 DCP time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT2 RDD time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT2 DCP time ', 3.9000000000000004, ' time step ', 39L)
> ('SCRIPT1 RDD time ', 4.0, ' time step ', 40L)
> ('SCRIPT2 RDD time ', 4.0, ' time step ', 40L)
> ('SCRIPT1 RDD time ', 4.0, ' time step ', 40L)
> ('SCRIPT1 DCP time ', 4.0, ' time step ', 40L)
> ('SCRIPT2 RDD time ', 4.0, ' time step ', 40L)
> ('SCRIPT2 DCP time ', 4.0, ' time step ', 40L)
> ('SCRIPT1 RDD time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT2 RDD time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT1 RDD time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT1 DCP time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT2 RDD time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT2 DCP time ', 4.1000000000000005, ' time step ', 41L)
> ('SCRIPT1 RDD time ', 4.2, ' time step ', 42L)
> ('SCRIPT2 RDD time ', 4.2, ' time step ', 42L)
> ('SCRIPT1 RDD time ', 4.2, ' time step ', 42L)
> ('SCRIPT1 DCP time ', 4.2, ' time step ', 42L)
> ('SCRIPT2 RDD time ', 4.2, ' time step ', 42L)
> ('SCRIPT2 DCP time ', 4.2, ' time step ', 42L)
> ('SCRIPT1 RDD time ', 4.3, ' time step ', 43L)
> ('SCRIPT2 RDD time ', 4.3, ' time step ', 43L)
> ('SCRIPT1 RDD time ', 4.3, ' time step ', 43L)
> ('SCRIPT1 DCP time ', 4.3, ' time step ', 43L)
> ('SCRIPT2 RDD time ', 4.3, ' time step ', 43L)
> ('SCRIPT2 DCP time ', 4.3, ' time step ', 43L)
> ('SCRIPT1 RDD time ', 4.4, ' time step ', 44L)
> ('SCRIPT2 RDD time ', 4.4, ' time step ', 44L)
> ('SCRIPT1 RDD time ', 4.4, ' time step ', 44L)
> ('SCRIPT1 DCP time ', 4.4, ' time step ', 44L)
> ('SCRIPT2 RDD time ', 4.4, ' time step ', 44L)
> ('SCRIPT2 DCP time ', 4.4, ' time step ', 44L)
> ('SCRIPT1 RDD time ', 4.5, ' time step ', 45L)
> ('SCRIPT2 RDD time ', 4.5, ' time step ', 45L)
> ('SCRIPT1 RDD time ', 4.5, ' time step ', 45L)
> ('SCRIPT1 DCP time ', 4.5, ' time step ', 45L)
> ('SCRIPT2 RDD time ', 4.5, ' time step ', 45L)
> ('SCRIPT2 DCP time ', 4.5, ' time step ', 45L)
> ('SCRIPT1 RDD time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT2 RDD time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT1 RDD time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT1 DCP time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT2 RDD time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT2 DCP time ', 4.6000000000000005, ' time step ', 46L)
> ('SCRIPT1 RDD time ', 4.7, ' time step ', 47L)
> ('SCRIPT2 RDD time ', 4.7, ' time step ', 47L)
> ('SCRIPT1 RDD time ', 4.7, ' time step ', 47L)
> ('SCRIPT1 DCP time ', 4.7, ' time step ', 47L)
> ('SCRIPT2 RDD time ', 4.7, ' time step ', 47L)
> ('SCRIPT2 DCP time ', 4.7, ' time step ', 47L)
> ('SCRIPT1 RDD time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT2 RDD time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT1 RDD time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT1 DCP time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT2 RDD time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT2 DCP time ', 4.800000000000001, ' time step ', 48L)
> ('SCRIPT1 RDD time ', 4.9, ' time step ', 49L)
> ('SCRIPT2 RDD time ', 4.9, ' time step ', 49L)
> ('SCRIPT1 RDD time ', 4.9, ' time step ', 49L)
> ('SCRIPT1 DCP time ', 4.9, ' time step ', 49L)
> ('SCRIPT2 RDD time ', 4.9, ' time step ', 49L)
> ('SCRIPT2 DCP time ', 4.9, ' time step ', 49L)
> ('SCRIPT1 RDD time ', 5.0, ' time step ', 50L)
> ('SCRIPT2 RDD time ', 5.0, ' time step ', 50L)
> ('SCRIPT1 RDD time ', 5.0, ' time step ', 50L)
> ('SCRIPT1 DCP time ', 5.0, ' time step ', 50L)
> ('SCRIPT2 RDD time ', 5.0, ' time step ', 50L)
> ('SCRIPT2 DCP time ', 5.0, ' time step ', 50L)
> ('SCRIPT1 RDD time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT2 RDD time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT1 RDD time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT1 DCP time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT2 RDD time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT2 DCP time ', 5.1000000000000005, ' time step ', 51L)
> ('SCRIPT1 RDD time ', 5.2, ' time step ', 52L)
> ('SCRIPT2 RDD time ', 5.2, ' time step ', 52L)
> ('SCRIPT1 RDD time ', 5.2, ' time step ', 52L)
> ('SCRIPT1 DCP time ', 5.2, ' time step ', 52L)
> ('SCRIPT2 RDD time ', 5.2, ' time step ', 52L)
> ('SCRIPT2 DCP time ', 5.2, ' time step ', 52L)
> ('SCRIPT1 RDD time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT2 RDD time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT1 RDD time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT1 DCP time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT2 RDD time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT2 DCP time ', 5.300000000000001, ' time step ', 53L)
> ('SCRIPT1 RDD time ', 5.4, ' time step ', 54L)
> ('SCRIPT2 RDD time ', 5.4, ' time step ', 54L)
> ('SCRIPT1 RDD time ', 5.4, ' time step ', 54L)
> ('SCRIPT1 DCP time ', 5.4, ' time step ', 54L)
> ('SCRIPT2 RDD time ', 5.4, ' time step ', 54L)
> ('SCRIPT2 DCP time ', 5.4, ' time step ', 54L)
> ('SCRIPT1 RDD time ', 5.5, ' time step ', 55L)
> ('SCRIPT2 RDD time ', 5.5, ' time step ', 55L)
> ('SCRIPT1 RDD time ', 5.5, ' time step ', 55L)
> ('SCRIPT1 DCP time ', 5.5, ' time step ', 55L)
> ('SCRIPT2 RDD time ', 5.5, ' time step ', 55L)
> ('SCRIPT2 DCP time ', 5.5, ' time step ', 55L)
> ('SCRIPT1 RDD time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT2 RDD time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT1 RDD time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT1 DCP time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT2 RDD time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT2 DCP time ', 5.6000000000000005, ' time step ', 56L)
> ('SCRIPT1 RDD time ', 5.7, ' time step ', 57L)
> ('SCRIPT2 RDD time ', 5.7, ' time step ', 57L)
> ('SCRIPT1 RDD time ', 5.7, ' time step ', 57L)
> ('SCRIPT1 DCP time ', 5.7, ' time step ', 57L)
> ('SCRIPT2 RDD time ', 5.7, ' time step ', 57L)
> ('SCRIPT2 DCP time ', 5.7, ' time step ', 57L)
> ('SCRIPT1 RDD time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT2 RDD time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT1 RDD time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT1 DCP time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT2 RDD time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT2 DCP time ', 5.800000000000001, ' time step ', 58L)
> ('SCRIPT1 RDD time ', 5.9, ' time step ', 59L)
> ('SCRIPT2 RDD time ', 5.9, ' time step ', 59L)
> ('SCRIPT1 RDD time ', 5.9, ' time step ', 59L)
> ('SCRIPT1 DCP time ', 5.9, ' time step ', 59L)
> ('SCRIPT2 RDD time ', 5.9, ' time step ', 59L)
> ('SCRIPT2 DCP time ', 5.9, ' time step ', 59L)
> ('SCRIPT1 RDD time ', 6.0, ' time step ', 60L)
> ('SCRIPT2 RDD time ', 6.0, ' time step ', 60L)
> ('SCRIPT1 RDD time ', 6.0, ' time step ', 60L)
> ('SCRIPT1 DCP time ', 6.0, ' time step ', 60L)
> ('SCRIPT2 RDD time ', 6.0, ' time step ', 60L)
> ('SCRIPT2 DCP time ', 6.0, ' time step ', 60L)
> ('SCRIPT1 RDD time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT2 RDD time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT1 RDD time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT1 DCP time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT2 RDD time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT2 DCP time ', 6.1000000000000005, ' time step ', 61L)
> ('SCRIPT1 RDD time ', 6.2, ' time step ', 62L)
> ('SCRIPT2 RDD time ', 6.2, ' time step ', 62L)
> ('SCRIPT1 RDD time ', 6.2, ' time step ', 62L)
> ('SCRIPT1 DCP time ', 6.2, ' time step ', 62L)
> ('SCRIPT2 RDD time ', 6.2, ' time step ', 62L)
> ('SCRIPT2 DCP time ', 6.2, ' time step ', 62L)
> ('SCRIPT1 RDD time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT2 RDD time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT1 RDD time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT1 DCP time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT2 RDD time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT2 DCP time ', 6.300000000000001, ' time step ', 63L)
> ('SCRIPT1 RDD time ', 6.4, ' time step ', 64L)
> ('SCRIPT2 RDD time ', 6.4, ' time step ', 64L)
> ('SCRIPT1 RDD time ', 6.4, ' time step ', 64L)
> ('SCRIPT1 DCP time ', 6.4, ' time step ', 64L)
> ('SCRIPT2 RDD time ', 6.4, ' time step ', 64L)
> ('SCRIPT2 DCP time ', 6.4, ' time step ', 64L)
> ('SCRIPT1 RDD time ', 6.5, ' time step ', 65L)
> ('SCRIPT2 RDD time ', 6.5, ' time step ', 65L)
> ('SCRIPT1 RDD time ', 6.5, ' time step ', 65L)
> ('SCRIPT1 DCP time ', 6.5, ' time step ', 65L)
> ('SCRIPT2 RDD time ', 6.5, ' time step ', 65L)
> ('SCRIPT2 DCP time ', 6.5, ' time step ', 65L)
> ('SCRIPT1 RDD time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT2 RDD time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT1 RDD time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT1 DCP time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT2 RDD time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT2 DCP time ', 6.6000000000000005, ' time step ', 66L)
> ('SCRIPT1 RDD time ', 6.7, ' time step ', 67L)
> ('SCRIPT2 RDD time ', 6.7, ' time step ', 67L)
> ('SCRIPT1 RDD time ', 6.7, ' time step ', 67L)
> ('SCRIPT1 DCP time ', 6.7, ' time step ', 67L)
> ('SCRIPT2 RDD time ', 6.7, ' time step ', 67L)
> ('SCRIPT2 DCP time ', 6.7, ' time step ', 67L)
> ('SCRIPT1 RDD time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT2 RDD time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT1 RDD time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT1 DCP time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT2 RDD time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT2 DCP time ', 6.800000000000001, ' time step ', 68L)
> ('SCRIPT1 RDD time ', 6.9, ' time step ', 69L)
> ('SCRIPT2 RDD time ', 6.9, ' time step ', 69L)
> ('SCRIPT1 RDD time ', 6.9, ' time step ', 69L)
> ('SCRIPT1 DCP time ', 6.9, ' time step ', 69L)
> ('SCRIPT2 RDD time ', 6.9, ' time step ', 69L)
> ('SCRIPT2 DCP time ', 6.9, ' time step ', 69L)
> ('SCRIPT1 RDD time ', 7.0, ' time step ', 70L)
> ('SCRIPT2 RDD time ', 7.0, ' time step ', 70L)
> ('SCRIPT1 RDD time ', 7.0, ' time step ', 70L)
> ('SCRIPT1 DCP time ', 7.0, ' time step ', 70L)
> ('SCRIPT2 RDD time ', 7.0, ' time step ', 70L)
> ('SCRIPT2 DCP time ', 7.0, ' time step ', 70L)
> ('SCRIPT1 RDD time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT2 RDD time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT1 RDD time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT1 DCP time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT2 RDD time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT2 DCP time ', 7.1000000000000005, ' time step ', 71L)
> ('SCRIPT1 RDD time ', 7.2, ' time step ', 72L)
> ('SCRIPT2 RDD time ', 7.2, ' time step ', 72L)
> ('SCRIPT1 RDD time ', 7.2, ' time step ', 72L)
> ('SCRIPT1 DCP time ', 7.2, ' time step ', 72L)
> ('SCRIPT2 RDD time ', 7.2, ' time step ', 72L)
> ('SCRIPT2 DCP time ', 7.2, ' time step ', 72L)
> ('SCRIPT1 RDD time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT2 RDD time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT1 RDD time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT1 DCP time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT2 RDD time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT2 DCP time ', 7.300000000000001, ' time step ', 73L)
> ('SCRIPT1 RDD time ', 7.4, ' time step ', 74L)
> ('SCRIPT2 RDD time ', 7.4, ' time step ', 74L)
> ('SCRIPT1 RDD time ', 7.4, ' time step ', 74L)
> ('SCRIPT1 DCP time ', 7.4, ' time step ', 74L)
> ('SCRIPT2 RDD time ', 7.4, ' time step ', 74L)
> ('SCRIPT2 DCP time ', 7.4, ' time step ', 74L)
> ('SCRIPT1 RDD time ', 7.5, ' time step ', 75L)
> ('SCRIPT2 RDD time ', 7.5, ' time step ', 75L)
> ('SCRIPT1 RDD time ', 7.5, ' time step ', 75L)
> ('SCRIPT1 DCP time ', 7.5, ' time step ', 75L)
> ('SCRIPT2 RDD time ', 7.5, ' time step ', 75L)
> ('SCRIPT2 DCP time ', 7.5, ' time step ', 75L)
> ('SCRIPT1 RDD time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT2 RDD time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT1 RDD time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT1 DCP time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT2 RDD time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT2 DCP time ', 7.6000000000000005, ' time step ', 76L)
> ('SCRIPT1 RDD time ', 7.7, ' time step ', 77L)
> ('SCRIPT2 RDD time ', 7.7, ' time step ', 77L)
> ('SCRIPT1 RDD time ', 7.7, ' time step ', 77L)
> ('SCRIPT1 DCP time ', 7.7, ' time step ', 77L)
> ('SCRIPT2 RDD time ', 7.7, ' time step ', 77L)
> ('SCRIPT2 DCP time ', 7.7, ' time step ', 77L)
> ('SCRIPT1 RDD time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT2 RDD time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT1 RDD time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT1 DCP time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT2 RDD time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT2 DCP time ', 7.800000000000001, ' time step ', 78L)
> ('SCRIPT1 RDD time ', 7.9, ' time step ', 79L)
> ('SCRIPT2 RDD time ', 7.9, ' time step ', 79L)
> ('SCRIPT1 RDD time ', 7.9, ' time step ', 79L)
> ('SCRIPT1 DCP time ', 7.9, ' time step ', 79L)
> ('SCRIPT2 RDD time ', 7.9, ' time step ', 79L)
> ('SCRIPT2 DCP time ', 7.9, ' time step ', 79L)
> ('SCRIPT1 RDD time ', 8.0, ' time step ', 80L)
> ('SCRIPT2 RDD time ', 8.0, ' time step ', 80L)
> ('SCRIPT1 RDD time ', 8.0, ' time step ', 80L)
> ('SCRIPT1 DCP time ', 8.0, ' time step ', 80L)
> ('SCRIPT2 RDD time ', 8.0, ' time step ', 80L)
> ('SCRIPT2 DCP time ', 8.0, ' time step ', 80L)
> ('SCRIPT1 RDD time ', 8.1, ' time step ', 81L)
> ('SCRIPT2 RDD time ', 8.1, ' time step ', 81L)
> ('SCRIPT1 RDD time ', 8.1, ' time step ', 81L)
> ('SCRIPT1 DCP time ', 8.1, ' time step ', 81L)
> ('SCRIPT2 RDD time ', 8.1, ' time step ', 81L)
> ('SCRIPT2 DCP time ', 8.1, ' time step ', 81L)
> ('SCRIPT1 RDD time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT2 RDD time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT1 RDD time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT1 DCP time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT2 RDD time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT2 DCP time ', 8.200000000000001, ' time step ', 82L)
> ('SCRIPT1 RDD time ', 8.3, ' time step ', 83L)
> ('SCRIPT2 RDD time ', 8.3, ' time step ', 83L)
> ('SCRIPT1 RDD time ', 8.3, ' time step ', 83L)
> ('SCRIPT1 DCP time ', 8.3, ' time step ', 83L)
> ('SCRIPT2 RDD time ', 8.3, ' time step ', 83L)
> ('SCRIPT2 DCP time ', 8.3, ' time step ', 83L)
> ('SCRIPT1 RDD time ', 8.4, ' time step ', 84L)
> ('SCRIPT2 RDD time ', 8.4, ' time step ', 84L)
> ('SCRIPT1 RDD time ', 8.4, ' time step ', 84L)
> ('SCRIPT1 DCP time ', 8.4, ' time step ', 84L)
> ('SCRIPT2 RDD time ', 8.4, ' time step ', 84L)
> ('SCRIPT2 DCP time ', 8.4, ' time step ', 84L)
> ('SCRIPT1 RDD time ', 8.5, ' time step ', 85L)
> ('SCRIPT2 RDD time ', 8.5, ' time step ', 85L)
> ('SCRIPT1 RDD time ', 8.5, ' time step ', 85L)
> ('SCRIPT1 DCP time ', 8.5, ' time step ', 85L)
> ('SCRIPT2 RDD time ', 8.5, ' time step ', 85L)
> ('SCRIPT2 DCP time ', 8.5, ' time step ', 85L)
> ('SCRIPT1 RDD time ', 8.6, ' time step ', 86L)
> ('SCRIPT2 RDD time ', 8.6, ' time step ', 86L)
> ('SCRIPT1 RDD time ', 8.6, ' time step ', 86L)
> ('SCRIPT1 DCP time ', 8.6, ' time step ', 86L)
> ('SCRIPT2 RDD time ', 8.6, ' time step ', 86L)
> ('SCRIPT2 DCP time ', 8.6, ' time step ', 86L)
> ('SCRIPT1 RDD time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT2 RDD time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT1 RDD time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT1 DCP time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT2 RDD time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT2 DCP time ', 8.700000000000001, ' time step ', 87L)
> ('SCRIPT1 RDD time ', 8.8, ' time step ', 88L)
> ('SCRIPT2 RDD time ', 8.8, ' time step ', 88L)
> ('SCRIPT1 RDD time ', 8.8, ' time step ', 88L)
> ('SCRIPT1 DCP time ', 8.8, ' time step ', 88L)
> ('SCRIPT2 RDD time ', 8.8, ' time step ', 88L)
> ('SCRIPT2 DCP time ', 8.8, ' time step ', 88L)
> ('SCRIPT1 RDD time ', 8.9, ' time step ', 89L)
> ('SCRIPT2 RDD time ', 8.9, ' time step ', 89L)
> ('SCRIPT1 RDD time ', 8.9, ' time step ', 89L)
> ('SCRIPT1 DCP time ', 8.9, ' time step ', 89L)
> ('SCRIPT2 RDD time ', 8.9, ' time step ', 89L)
> ('SCRIPT2 DCP time ', 8.9, ' time step ', 89L)
> ('SCRIPT1 RDD time ', 9.0, ' time step ', 90L)
> ('SCRIPT2 RDD time ', 9.0, ' time step ', 90L)
> ('SCRIPT1 RDD time ', 9.0, ' time step ', 90L)
> ('SCRIPT1 DCP time ', 9.0, ' time step ', 90L)
> ('SCRIPT2 RDD time ', 9.0, ' time step ', 90L)
> ('SCRIPT2 DCP time ', 9.0, ' time step ', 90L)
> ('SCRIPT1 RDD time ', 9.1, ' time step ', 91L)
> ('SCRIPT2 RDD time ', 9.1, ' time step ', 91L)
> ('SCRIPT1 RDD time ', 9.1, ' time step ', 91L)
> ('SCRIPT1 DCP time ', 9.1, ' time step ', 91L)
> ('SCRIPT2 RDD time ', 9.1, ' time step ', 91L)
> ('SCRIPT2 DCP time ', 9.1, ' time step ', 91L)
> ('SCRIPT1 RDD time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT2 RDD time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT1 RDD time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT1 DCP time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT2 RDD time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT2 DCP time ', 9.200000000000001, ' time step ', 92L)
> ('SCRIPT1 RDD time ', 9.3, ' time step ', 93L)
> ('SCRIPT2 RDD time ', 9.3, ' time step ', 93L)
> ('SCRIPT1 RDD time ', 9.3, ' time step ', 93L)
> ('SCRIPT1 DCP time ', 9.3, ' time step ', 93L)
> ('SCRIPT2 RDD time ', 9.3, ' time step ', 93L)
> ('SCRIPT2 DCP time ', 9.3, ' time step ', 93L)
> ('SCRIPT1 RDD time ', 9.4, ' time step ', 94L)
> ('SCRIPT2 RDD time ', 9.4, ' time step ', 94L)
> ('SCRIPT1 RDD time ', 9.4, ' time step ', 94L)
> ('SCRIPT1 DCP time ', 9.4, ' time step ', 94L)
> ('SCRIPT2 RDD time ', 9.4, ' time step ', 94L)
> ('SCRIPT2 DCP time ', 9.4, ' time step ', 94L)
> ('SCRIPT1 RDD time ', 9.5, ' time step ', 95L)
> ('SCRIPT2 RDD time ', 9.5, ' time step ', 95L)
> ('SCRIPT1 RDD time ', 9.5, ' time step ', 95L)
> ('SCRIPT1 DCP time ', 9.5, ' time step ', 95L)
> ('SCRIPT2 RDD time ', 9.5, ' time step ', 95L)
> ('SCRIPT2 DCP time ', 9.5, ' time step ', 95L)
> ('SCRIPT1 RDD time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT2 RDD time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT1 RDD time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT1 DCP time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT2 RDD time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT2 DCP time ', 9.600000000000001, ' time step ', 96L)
> ('SCRIPT1 RDD time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT2 RDD time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT1 RDD time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT1 DCP time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT2 RDD time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT2 DCP time ', 9.700000000000001, ' time step ', 97L)
> ('SCRIPT1 RDD time ', 9.8, ' time step ', 98L)
> ('SCRIPT2 RDD time ', 9.8, ' time step ', 98L)
> ('SCRIPT1 RDD time ', 9.8, ' time step ', 98L)
> ('SCRIPT1 DCP time ', 9.8, ' time step ', 98L)
> ('SCRIPT2 RDD time ', 9.8, ' time step ', 98L)
> ('SCRIPT2 DCP time ', 9.8, ' time step ', 98L)
> ('SCRIPT1 DCP time ', 9.9, ' time step ', 99L)
> ('SCRIPT2 DCP time ', 9.9, ' time step ', 99L)
>
>
> > Hi Ufuk,
> >
> > It's looking to me like the issue is in the adaptor some place. I tried
> > running your scripts (modified slightly) with the CxxFullExample
> > (./CxxFullExample script_1.py script_2.py) and was able to get image_s1*
> > and image_s2* files out of it and did not see the warning you mention. I
> > also modified that example to use atm_input2d instead of input for the
> > input/grid identifier to make sure that wasn't the case. I've attached
> > this
> > example with the scripts modified to print out some debug information.
> >
> > Some questions (these are pretty basic things that you've probably
> already
> > gotten working properly but maybe there's some small thing that was
> > forgotten):
> >
> >    - Does your g_coprocessor only get created in your initialization
> >    routine and deleted in the finalization step? That should not be
> > created
> >    and deleted during each in situ processing step.
> >    - Do the vtkCPPythonScriptPipelines only get added during
> >    initialization? They should not be added and removed from
> g_coprocessor
> >    every time step.
> >
> > Also, could you try running with the scripts that I included in the
> > cat.tgz
> > tarball? The print statements there will print out the time and time
> steps
> > during the simulation run to help me diagnose (both need to be increasing
> > between calls to Catalyst). Also, if you share your adaptor code with me
> I
> > can take a quick look.
> >
> > Cheers,
> > Andy
> >
> >
> >
> > On Fri, Jul 7, 2017 at 7:30 AM, Ufuk Utku Turuncoglu (BE) <
> > u.utku.turuncoglu at be.itu.edu.tr> wrote:
> >
> >> Hi Andy,
> >>
> >> Strange! To test the idea and eliminate other problems i am using same
> >> script twice with little mods (i just changed the name of the output png
> >> file). So, if i pass script_1.py and script_2.py to the model, it gives
> >> warning like before and creates output just for second script
> >> (script_2.py). If i pass only one of them then the code is working
> >> without
> >> any problem and produces desired output.
> >>
> >> Thanks,
> >> Regards,
> >>
> >> --ufuk
> >>
> >>
> >>
> >> On 06/07/2017 18:09, Andy Bauer wrote:
> >>
> >> Hi Ufuk,
> >>
> >> I'm guessing the issue is that the calls to Catalyst are not consistent.
> >> Could you share your Python scripts? Also, did you modify them manually?
> >>
> >> I tried with PV 5.3. with the
> >> ../ParaView-v5.3.0/Examples/Catalyst/CxxFullExample/
> >> example with the attached scripts simultaneously by running with
> >> "./CxxFullExample doubleoutputs.py output3.py image11.py" and got the
> >> correct output and no warnings.
> >>
> >> Cheers,
> >> Andy
> >>
> >> On Tue, Jul 4, 2017 at 7:04 AM, Ufuk Utku Turuncoglu (BE) <
> >> u.utku.turuncoglu at be.itu.edu.tr> wrote:
> >>
> >>> Hi Andy,
> >>>
> >>> I tested you suggestion about using multiple script in co-processing.
> >>> In
> >>> this case, i used following code in the adaptor side to add multiple
> >>> pipeline
> >>>
> >>>       for (int i = 0; i < *nscript; i++) {
> >>>         pipeline->Initialize(pythonScriptNames[i]);
> >>>         g_coprocessor->AddPipeline(pipeline);
> >>>       }
> >>>
> >>> When i run the simulation, i am getting following warning
> >>>
> >>> Warning: In
> >>> /okyanus/users/uturuncoglu/progs/paraview-5.3.0/src/ParaView
> >>> Core/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 66
> >>> vtkPVTrivialProducer (0x13816760): New time step is not after last time
> >>> step.
> >>>
> >>> the output seems not correct and it is zoom out version of second
> >>> pipeline (png file). The first pipeline is not even triggered. Do i
> >>> missing
> >>> something in here? BTW, i am using PV 5.3.
> >>>
> >>> Thanks,
> >>>
> >>> --ufuk
> >>>
> >>>
> >>> On 16/05/2017 16:08, Andy Bauer wrote:
> >>>
> >>> Hi Ufuk,
> >>>
> >>> If you create a vtkCPythonScriptPipeline, when you initialize it with
> >>> the
> >>> script file name (which has to be done on each process) everything will
> >>> be
> >>> taken care of with respect to broadcasting the file contents from
> >>> process 0
> >>> to the others. We aren't sophisticated enough to parse the Python
> >>> script to
> >>> see if it imports other scripts that are not part of ParaView (e.g.
> >>> paraview.simple) or Python (e.g. sys). That is why I recommended the
> >>> first
> >>> approach as opposed to the second approach above. Depending on the
> >>> compute
> >>> platform and how many MPI processes are in the run the difference may
> >>> be
> >>> negligible but having 100K processes or more trying to access the same
> >>> file
> >>> can seriously slow down an HPC machine.
> >>>
> >>> Cheers,
> >>> Andy
> >>>
> >>> On Tue, May 16, 2017 at 8:24 AM, Ufuk Utku Turuncoglu (BE) <
> >>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
> >>>
> >>>> Thanks Andy. That is exactly what i am looking for. The broadcasting
> >>>> mechanism is not clear to me yet. Do i need to broadcast only the file
> >>>> names? Anyway, i will try to implement it and see what is going on
> >>>> there.
> >>>>
> >>>> Thanks again,
> >>>> Regards,
> >>>>
> >>>> --ufuk
> >>>>
> >>>>
> >>>> On 16/05/2017 14:58, Andy Bauer wrote:
> >>>>
> >>>> Hi Ufuk,
> >>>>
> >>>> Unless I'm not understanding your question correctly, I think you can
> >>>> get what you want by adding in multiple vtkCPPythonScriptPipelines to
> >>>> your
> >>>> vtkCPProcessor object in your adaptor. Alternatively if you want to
> >>>> have a
> >>>> single, master Catalyst script handling other Catalyst scripts you can
> >>>> do
> >>>> something like the following:
> >>>> ================
> >>>> import script_a
> >>>> import script_b
> >>>> import script_c
> >>>>
> >>>> def RequestDataDescription(datadescription):
> >>>>   script_a.RequestDataDescription(datadescription)
> >>>>   script_b.RequestDataDescription(datadescription)
> >>>>   script_c.RequestDataDescription(datadescription)
> >>>>
> >>>> def DoCoProcessing(datadescription):
> >>>>   script_a.DoCoProcessing(datadescription)
> >>>>   script_b.DoCoProcessing(datadescription)
> >>>>   script_c.DoCoProcessing(datadescription)
> >>>> ===================
> >>>>
> >>>> The first way is the recommended way though as that should be more
> >>>> efficient by having process 0 read the scripts and broadcasting the
> >>>> script
> >>>> contents to the other  processes for use. The second method will only
> >>>> do
> >>>> that for the master script.
> >>>>
> >>>> Please let me know if this doesn't answer your question.
> >>>>
> >>>> Cheers,
> >>>> Andy
> >>>>
> >>>> On Tue, May 16, 2017 at 5:46 AM, Ufuk Utku Turuncoglu (BE) <
> >>>> u.utku.turuncoglu at be.itu.edu.tr> wrote:
> >>>>
> >>>>> Hi All,
> >>>>>
> >>>>> I just wonder that is it possible to trigger multiple visualization
> >>>>> pipeline in the same time with co-processing. The co-processing
> >>>>> script
> >>>>> generator plugin mainly outputs only single pipeline at a time and
> >>>>> that is
> >>>>> fine but what about combining multiple Python script (generated by
> >>>>> plugin)
> >>>>> using higher level Python script to trigger multiple pipelines. So, i
> >>>>> think
> >>>>> that this will be much efficient way to look at different part of the
> >>>>> data
> >>>>> without writing to the disk. I am not sure but somebody else might do
> >>>>> it
> >>>>> before.
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> --ufuk
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/9bd5252b/attachment.html>

From klarmann at mechanik.tu-darmstadt.de  Mon Jul 10 10:34:25 2017
From: klarmann at mechanik.tu-darmstadt.de (Simon Klarmann)
Date: Mon, 10 Jul 2017 16:34:25 +0200
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
Message-ID: <01ad01d2f989$a120c1c0$e3624540$@mechanik.tu-darmstadt.de>

Sorry I think I have chosen the wrong reply method.

 

Hi Andy,

 

I already got rid of Python on both sides. CoProcessing with Live connection is working by directly using the vtkLiveInsituLink (pure C++ implementation).

 

Working with both Paraview 5.2  and 5.4.

 

My problem is closing the connection on the Live side (e.g. closing Paraview). Doing so, my Insitu side hangs (when trying again to send data, m_link->InsituUpdate, see below) in the receive method of the vtkSocket class until at some point an integer underflow happens.

 

Closing the connection from the Insitu side everything works as expected. 

 

Are there any methods to directly check if the connection is still alive?

Or is it a Windows specific problem?

 

 

 

Additionally the steps for the live connection in C++, for sure there may be more elegant ways:

 

// Initialization

 

vtkCPProcessor  *m_proc = vtkCPProcessor::New();

                m_proc->Initialize();

 

                vtkLiveInsituLink  *m_link = vtkLiveInsituLink::New();

                m_link->SetInsituPort(22222);

                m_link->SetHostname("localhost");

                m_link->SetProcessType(vtkLiveInsituLink::INSITU);

 

                vtkSMProxyManager  *m_spxm = vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();

                vtkSMProxy *m_px = m_spxm->NewProxy("sources", "PVTrivialProducer");

                vtkSMSourceProxy *m_spx = vtkSMSourceProxy::SafeDownCast(m_px);

                m_spxm->RegisterProxy("sources", m_spx);

 

                vtkObjectBase *obase = m_spx->GetClientSideObject();

                vtkPVTrivialProducer *prod =

                               vtkPVTrivialProducer::SafeDownCast(obase);

                prod->SetOutput(m_toplot, m_time);    // m_toplot is a vtkMultiBlockDataSet

 

                m_link->Initialize(m_spxm);

 

                

                //Update the live side

                m_link->InsituUpdate(m_time, m_tstep);

m_spx->UpdatePipeline(m_time);

m_link->InsituPostProcess(m_time,m_tstep);

 

 

Thanks,

Simon

 

 

 

 

 

Von: Andy Bauer [mailto:andy.bauer at kitware.com] 
Gesendet: Donnerstag, 6. Juli 2017 17:14
An: Simon Klarmann
Cc: paraview at paraview.org
Betreff: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows

 

Hi Simon,

 

Is the Python dependency that you're trying to get rid of on the Catalyst side or on the pvserver/GUI side? If I remember correctly on the Catalyst side Python was required for the Live connection. 

 

Cheers,

Andy

 

On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann <klarmann at mechanik.tu-darmstadt.de> wrote:

Dear Members,

 

I wanted to get rid of the dependency on Python. The connection by pure C++ works just fine.

 

The problem occurs when establishing the live connection to Paraview, closing Paraview and then try to send some data again.

I tracked it down to the vtkSocket class inside the method Receive. After the connection is terminated on the Paraview side, e.g. by closing Paraview, the call of vtkLiveInsituLink::InsituUpdate gets stuck in the vtkSocket::Receive method. Even though I get a message that the connection was terminated.

 

A temporary fix for my case was to replace in Line 609 of the vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on disconnection the return value of nRecvd is -1. Then everything works well.

 

I only used the following methods in the given order to transfer the data:

 

vtkLiveInsituLink::InsituUpdate

vtkSMSourceProxy::UpdatePipeline

vtkLiveInsituLink::InsituPostProcess

 

 

Are there further steps to perform or is there a way to check if the connection is still alive?

 

 

Operating System: Windows 7, Visual Studio 2017

 

Thanks,

Simon

 

 

 

 

Dipl.-Ing. Simon Klarmann

 

Bau- und Umweltingenieurwissenschaften
Technische Universit?t Darmstadt

Fachgebiet Festk?rpermechanik

 

Tel.: +49 6151 16 ? 22642 <tel:+49%206151%201622642> 

Mail: klarmann at mechanik.tu-darmstadt.de

Franziska-Braun-Stra?e 7

Geb?ude L5|01, Raum 542

64287 Darmstadt

 


_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/47ca33ce/attachment.html>

From jake.a.gerard at gmail.com  Mon Jul 10 11:46:54 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Mon, 10 Jul 2017 10:46:54 -0500
Subject: [Paraview] How to properly visualize data in Paraview using HDF5?
Message-ID: <CAES0UenpTsJrajaenVnPhGB1z353_QQJ_OzYn4ysW=2Ja18SQQ@mail.gmail.com>

Good Morning,

I am trying to update the visualization portion of an HPC fluid model. Used
to use legacy VTK but its starting to reach its limits. I read that HDF5
was good for large data sets and that it could be viewed in Paraview with
XDMF. However, it seems there are so few examples online. I got a long
rectangular channel to show up but the pressure data in it is wrong.
Hopefully if I can solve this, then it will help me update my code along
with anybody else who might be struggling with the same problem.

Is the formatting for this XDMF file incorrect, or is there some other
problem I'm not considering?  I can attach the HDF5 file too if its
necessary.

<?xml version="1.0" ?><!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []><Xdmf>
  <Domain>
    <Grid Name="my_Grid" GridType="Uniform">
      <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
      </Topology>
      <Geometry GeometryType="Origin_DxDyDz">
        <DataItem Dimensions="3" NumberType="Float" Format="XML">
          0 0 0
        </DataItem>
        <DataItem Dimensions="3" NumberType="Float" Format="XML">
          1 1 1
        </DataItem>
      </Geometry>
      <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
        <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
          output.h5:/pres_group/presmag
        </DataItem>
      </Attribute>
    </Grid>
  </Domain></Xdmf>

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/0f1d45cd/attachment.html>

From dave.demarle at kitware.com  Mon Jul 10 14:58:48 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 10 Jul 2017 14:58:48 -0400
Subject: [Paraview] How to properly visualize data in Paraview using
	HDF5?
In-Reply-To: <CAES0UenpTsJrajaenVnPhGB1z353_QQJ_OzYn4ysW=2Ja18SQQ@mail.gmail.com>
References: <CAES0UenpTsJrajaenVnPhGB1z353_QQJ_OzYn4ysW=2Ja18SQQ@mail.gmail.com>
Message-ID: <CANjZAi8egEAsqXLp4hfWqK6W+Pbx_9Y3V-SR6Mat-1gTY6_CKw@mail.gmail.com>

Does 19 19 91 work?


David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Jul 10, 2017 at 11:46 AM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> Good Morning,
>
> I am trying to update the visualization portion of an HPC fluid model.
> Used to use legacy VTK but its starting to reach its limits. I read that
> HDF5 was good for large data sets and that it could be viewed in Paraview
> with XDMF. However, it seems there are so few examples online. I got a long
> rectangular channel to show up but the pressure data in it is wrong.
> Hopefully if I can solve this, then it will help me update my code along
> with anybody else who might be struggling with the same problem.
>
> Is the formatting for this XDMF file incorrect, or is there some other
> problem I'm not considering?  I can attach the HDF5 file too if its
> necessary.
>
> <?xml version="1.0" ?><!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []><Xdmf>
>   <Domain>
>     <Grid Name="my_Grid" GridType="Uniform">
>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>       </Topology>
>       <Geometry GeometryType="Origin_DxDyDz">
>         <DataItem Dimensions="3" NumberType="Float" Format="XML">
>           0 0 0
>         </DataItem>
>         <DataItem Dimensions="3" NumberType="Float" Format="XML">
>           1 1 1
>         </DataItem>
>       </Geometry>
>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>           output.h5:/pres_group/presmag
>         </DataItem>
>       </Attribute>
>     </Grid>
>   </Domain></Xdmf>
>
> Thanks
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/dc165674/attachment.html>

From dave.demarle at kitware.com  Mon Jul 10 16:11:31 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 10 Jul 2017 16:11:31 -0400
Subject: [Paraview] How to properly visualize data in Paraview using
	HDF5?
In-Reply-To: <CAES0Uen7JKCn03YAH4Hk8PPn4=t0ypuXw2gHsK6gL65sL58A+Q@mail.gmail.com>
References: <CAES0UenpTsJrajaenVnPhGB1z353_QQJ_OzYn4ysW=2Ja18SQQ@mail.gmail.com>
 <CANjZAi8egEAsqXLp4hfWqK6W+Pbx_9Y3V-SR6Mat-1gTY6_CKw@mail.gmail.com>
 <CAES0Uen7JKCn03YAH4Hk8PPn4=t0ypuXw2gHsK6gL65sL58A+Q@mail.gmail.com>
Message-ID: <CANjZAi8SaTH+nqjxraVy7tRxSQgyJ=_-4p_coa9zsCdthpVRmw@mail.gmail.com>

cc'ing the list back in

xdmf has join for this purpose, but I typically use python filter in
paraview to join the scalars together into a vector instead. That route is
more widely traveled.





David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Jul 10, 2017 at 3:53 PM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> No, it shows the length properly down the z-axis when I have it as 91 19
> 19, but the data is not correct for either of these. I think that the data
> may actually be stored improperly in the HDF5 because I created dummy files
> and they worked fine.  However, if I were to add vectors in using 3
> seperate arrays (1 for x y and z) then how would I alter the current
> format?
>
> On Mon, Jul 10, 2017 at 1:58 PM, David E DeMarle <dave.demarle at kitware.com
> > wrote:
>
>> Does 19 19 91 work?
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> Principal Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909 <(518)%20881-4909>
>>
>> On Mon, Jul 10, 2017 at 11:46 AM, Jake Gerard <jake.a.gerard at gmail.com>
>> wrote:
>>
>>> Good Morning,
>>>
>>> I am trying to update the visualization portion of an HPC fluid model.
>>> Used to use legacy VTK but its starting to reach its limits. I read that
>>> HDF5 was good for large data sets and that it could be viewed in Paraview
>>> with XDMF. However, it seems there are so few examples online. I got a long
>>> rectangular channel to show up but the pressure data in it is wrong.
>>> Hopefully if I can solve this, then it will help me update my code along
>>> with anybody else who might be struggling with the same problem.
>>>
>>> Is the formatting for this XDMF file incorrect, or is there some other
>>> problem I'm not considering?  I can attach the HDF5 file too if its
>>> necessary.
>>>
>>> <?xml version="1.0" ?><!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []><Xdmf>
>>>   <Domain>
>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>       </Topology>
>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>         <DataItem Dimensions="3" NumberType="Float" Format="XML">
>>>           0 0 0
>>>         </DataItem>
>>>         <DataItem Dimensions="3" NumberType="Float" Format="XML">
>>>           1 1 1
>>>         </DataItem>
>>>       </Geometry>
>>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>>           output.h5:/pres_group/presmag
>>>         </DataItem>
>>>       </Attribute>
>>>     </Grid>
>>>   </Domain></Xdmf>
>>>
>>> Thanks
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/afa676a8/attachment.html>

From andy.bauer at kitware.com  Mon Jul 10 16:20:47 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 10 Jul 2017 16:20:47 -0400
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
In-Reply-To: <01ad01d2f989$a120c1c0$e3624540$@mechanik.tu-darmstadt.de>
References: <01ad01d2f989$a120c1c0$e3624540$@mechanik.tu-darmstadt.de>
Message-ID: <CAMaOp+Gq3bR_WG_Rcxb54-u60HEwik8cS1XrGsROHssW_XwWKw@mail.gmail.com>

Hi,

Are you trying to close the connection from the in situ side? The design
was for the connection to be close through the GUI.

It's difficult to say what exactly is going on here without getting fairly
deep into the problem. Theoretically though it should be possible to do the
Live link in C++ as most of the Python routines call wrapped C++ routines.

There should be some way to figure out the status of the connection on the
PV server (the builtin server if you're not connected to a separate
pvserver process) either the NotifyClientDisconnected() method,
or vtkLiveInsituLink::OnConnectionClosedEvent()
or vtkLiveInsituLink::DropLiveInsituConnection() member functions.

Cheers,
Andy

On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann <
klarmann at mechanik.tu-darmstadt.de> wrote:

> Sorry I think I have chosen the wrong reply method.
>
>
>
> Hi Andy,
>
>
>
> I already got rid of Python on both sides. CoProcessing with Live
> connection is working by directly using the vtkLiveInsituLink (pure C++
> implementation).
>
>
>
> Working with both Paraview 5.2  and 5.4.
>
>
>
> My problem is closing the connection on the Live side (e.g. closing
> Paraview). Doing so, my Insitu side hangs (when trying again to send data,
> m_link->InsituUpdate, see below) in the receive method of the vtkSocket
> class until at some point an integer underflow happens.
>
>
>
> Closing the connection from the Insitu side everything works as expected.
>
>
>
> Are there any methods to directly check if the connection is still alive?
>
> Or is it a Windows specific problem?
>
>
>
>
>
>
>
> Additionally the steps for the live connection in C++, for sure there may
> be more elegant ways:
>
>
>
> // Initialization
>
>
>
> vtkCPProcessor  *m_proc = vtkCPProcessor::New();
>
>                 m_proc->Initialize();
>
>
>
>                 vtkLiveInsituLink  *m_link = vtkLiveInsituLink::New();
>
>                 m_link->SetInsituPort(22222);
>
>                 m_link->SetHostname("localhost");
>
>                 m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>
>
>
>                 vtkSMProxyManager  *m_spxm = vtkSMProxyManager::
> GetProxyManager()->GetActiveSessionProxyManager();
>
>                 vtkSMProxy *m_px = m_spxm->NewProxy("sources",
> "PVTrivialProducer");
>
>                 vtkSMSourceProxy *m_spx = vtkSMSourceProxy::
> SafeDownCast(m_px);
>
>                 m_spxm->RegisterProxy("sources", m_spx);
>
>
>
>                 vtkObjectBase *obase = m_spx->GetClientSideObject();
>
>                 vtkPVTrivialProducer *prod =
>
>                                vtkPVTrivialProducer::SafeDownCast(obase);
>
>                 prod->SetOutput(m_toplot, m_time);    // m_toplot is a
> vtkMultiBlockDataSet
>
>
>
>                 m_link->Initialize(m_spxm);
>
>
>
>
>
>                 //Update the live side
>
>                 m_link->InsituUpdate(m_time, m_tstep);
>
> m_spx->UpdatePipeline(m_time);
>
> m_link->InsituPostProcess(m_time,m_tstep);
>
>
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Gesendet:* Donnerstag, 6. Juli 2017 17:14
> *An:* Simon Klarmann
> *Cc:* paraview at paraview.org
> *Betreff:* Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop
> on Windows
>
>
>
> Hi Simon,
>
>
>
> Is the Python dependency that you're trying to get rid of on the Catalyst
> side or on the pvserver/GUI side? If I remember correctly on the Catalyst
> side Python was required for the Live connection.
>
>
>
> Cheers,
>
> Andy
>
>
>
> On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann <klarmann at mechanik.tu-
> darmstadt.de> wrote:
>
> Dear Members,
>
>
>
> I wanted to get rid of the dependency on Python. The connection by pure
> C++ works just fine.
>
>
>
> The problem occurs when establishing the live connection to Paraview,
> closing Paraview and then try to send some data again.
>
> I tracked it down to the vtkSocket class inside the method Receive. After
> the connection is terminated on the Paraview side, e.g. by closing
> Paraview, the call of vtkLiveInsituLink::InsituUpdate gets stuck in the
> vtkSocket::Receive method. Even though I get a message that the connection
> was terminated.
>
>
>
> A temporary fix for my case was to replace in Line 609 of the
> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
> disconnection the return value of nRecvd is -1. Then everything works well.
>
>
>
> I only used the following methods in the given order to transfer the data:
>
>
>
> vtkLiveInsituLink::InsituUpdate
>
> vtkSMSourceProxy::UpdatePipeline
>
> vtkLiveInsituLink::InsituPostProcess
>
>
>
>
>
> Are there further steps to perform or is there a way to check if the
> connection is still alive?
>
>
>
>
>
> Operating System: Windows 7, Visual Studio 2017
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
> Dipl.-Ing. Simon Klarmann
>
>
>
> *Bau- und Umweltingenieurwissenschaften*
> Technische Universit?t Darmstadt
>
> Fachgebiet Festk?rpermechanik
>
>
>
> Tel.: +49 6151 16 ? 22642 <+49%206151%201622642>
>
> Mail: klarmann at mechanik.tu-darmstadt.de
>
> Franziska-Braun-Stra?e 7
>
> Geb?ude L5|01, Raum 542
>
> 64287 Darmstadt
>
>
>
>
> _______________________________________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170710/6a9d4934/attachment.html>

From klarmann at mechanik.tu-darmstadt.de  Tue Jul 11 08:04:30 2017
From: klarmann at mechanik.tu-darmstadt.de (Simon Klarmann)
Date: Tue, 11 Jul 2017 14:04:30 +0200
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
Message-ID: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>

Hi Andy,

 

I want to be able to close the connection from both sides. Closing the connection from the Insitu side works by calling vtkLiveInsituLink::DropLiveInsituConnection().

Closing the connection from the Live side, e.g. by closing the GUI, causes my application to hang in the vtkSocket::Receive() method.

 

After enabling the Debug mode I get the following Error on the Insitu side:

?ERROR: In D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572

vtkClientSocket (0000000008BFFC00): Socket error in call to send. Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen.?

 

?Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen? 

This seems to be a windows specific message notifying about a software controlled termination of the connection. So the information of the termination of the connection is somewhere available. The method throwing this error is the vtkSocket::Send() method. 

 

This error shows up as soon as I close the connection from the Live side (GUI) and then perform an InsituUpdate on the Insitu side. Still after this message, my Insitu side runs into vtkSocket::Receive() and get stuck there, trying to receive data.

 

 

Additional Info: 

Performing the live visualization with the vtkCPPythonAdapter leads to the same error message and a crash of the Insitu application.

 

Attached is a minimalistic working example. In both cases the error happens.

 

Steps to reproduce:

1.       Start Paraview ->Catalyst->Connect

2.       Start the application, choose either 0 for python or 1 for cpp, then the PVTrivialproducer should show up in Paraview

3.       Close Paraview

4.       Continue the application ->crash

 

 

I hope this helps a little bit to get an insight on what I did.

 

Thanks,

Simon

 

 

 

 

Von: Andy Bauer [mailto:andy.bauer at kitware.com] 
Gesendet: Montag, 10. Juli 2017 22:21
An: Simon Klarmann
Cc: paraview at paraview.org
Betreff: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows

 

Hi,

 

Are you trying to close the connection from the in situ side? The design was for the connection to be close through the GUI.

 

It's difficult to say what exactly is going on here without getting fairly deep into the problem. Theoretically though it should be possible to do the Live link in C++ as most of the Python routines call wrapped C++ routines. 

 

There should be some way to figure out the status of the connection on the PV server (the builtin server if you're not connected to a separate pvserver process) either the NotifyClientDisconnected() method, or vtkLiveInsituLink::OnConnectionClosedEvent() or vtkLiveInsituLink::DropLiveInsituConnection() member functions. 

 

Cheers,

Andy

 

On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann <klarmann at mechanik.tu-darmstadt.de> wrote:

Sorry I think I have chosen the wrong reply method.

 

Hi Andy,

 

I already got rid of Python on both sides. CoProcessing with Live connection is working by directly using the vtkLiveInsituLink (pure C++ implementation).

 

Working with both Paraview 5.2  and 5.4.

 

My problem is closing the connection on the Live side (e.g. closing Paraview). Doing so, my Insitu side hangs (when trying again to send data, m_link->InsituUpdate, see below) in the receive method of the vtkSocket class until at some point an integer underflow happens.

 

Closing the connection from the Insitu side everything works as expected. 

 

Are there any methods to directly check if the connection is still alive?

Or is it a Windows specific problem?

 

 

 

Additionally the steps for the live connection in C++, for sure there may be more elegant ways:

 

// Initialization

 

vtkCPProcessor  *m_proc = vtkCPProcessor::New();

                m_proc->Initialize();

 

                vtkLiveInsituLink  *m_link = vtkLiveInsituLink::New();

                m_link->SetInsituPort(22222);

                m_link->SetHostname("localhost");

                m_link->SetProcessType(vtkLiveInsituLink::INSITU);

 

                vtkSMProxyManager  *m_spxm = vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();

                vtkSMProxy *m_px = m_spxm->NewProxy("sources", "PVTrivialProducer");

                vtkSMSourceProxy *m_spx = vtkSMSourceProxy::SafeDownCast(m_px);

                m_spxm->RegisterProxy("sources", m_spx);

 

                vtkObjectBase *obase = m_spx->GetClientSideObject();

                vtkPVTrivialProducer *prod =

                               vtkPVTrivialProducer::SafeDownCast(obase);

                prod->SetOutput(m_toplot, m_time);    // m_toplot is a vtkMultiBlockDataSet

 

                m_link->Initialize(m_spxm);

 

                

                //Update the live side

                m_link->InsituUpdate(m_time, m_tstep);

m_spx->UpdatePipeline(m_time);

m_link->InsituPostProcess(m_time,m_tstep);

 

 

Thanks,

Simon

 

 

 

 

 

Von: Andy Bauer [mailto:andy.bauer at kitware.com] 
Gesendet: Donnerstag, 6. Juli 2017 17:14
An: Simon Klarmann
Cc: paraview at paraview.org
Betreff: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows

 

Hi Simon,

 

Is the Python dependency that you're trying to get rid of on the Catalyst side or on the pvserver/GUI side? If I remember correctly on the Catalyst side Python was required for the Live connection. 

 

Cheers,

Andy

 

On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann <klarmann at mechanik.tu-darmstadt.de> wrote:

Dear Members,

 

I wanted to get rid of the dependency on Python. The connection by pure C++ works just fine.

 

The problem occurs when establishing the live connection to Paraview, closing Paraview and then try to send some data again.

I tracked it down to the vtkSocket class inside the method Receive. After the connection is terminated on the Paraview side, e.g. by closing Paraview, the call of vtkLiveInsituLink::InsituUpdate gets stuck in the vtkSocket::Receive method. Even though I get a message that the connection was terminated.

 

A temporary fix for my case was to replace in Line 609 of the vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on disconnection the return value of nRecvd is -1. Then everything works well.

 

I only used the following methods in the given order to transfer the data:

 

vtkLiveInsituLink::InsituUpdate

vtkSMSourceProxy::UpdatePipeline

vtkLiveInsituLink::InsituPostProcess

 

 

Are there further steps to perform or is there a way to check if the connection is still alive?

 

 

Operating System: Windows 7, Visual Studio 2017

 

Thanks,

Simon

 

 

 

 

Dipl.-Ing. Simon Klarmann

 

Bau- und Umweltingenieurwissenschaften
Technische Universit?t Darmstadt

Fachgebiet Festk?rpermechanik

 

Tel.: +49 6151 16 ? 22642 <tel:+49%206151%201622642> 

Mail: klarmann at mechanik.tu-darmstadt.de

Franziska-Braun-Stra?e 7

Geb?ude L5|01, Raum 542

64287 Darmstadt

 


_______________________________________________
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

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/f76afcbb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CatalystTest.zip
Type: application/x-zip-compressed
Size: 2830 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/f76afcbb/attachment.bin>

From utkarsh.ayachit at kitware.com  Tue Jul 11 10:42:20 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 11 Jul 2017 10:42:20 -0400
Subject: [Paraview] [EXTERNAL] Re: long animations are freezing halfway
	through
In-Reply-To: <CADLMsL63gxoCOh80Q+B4yQ18JmyZU51M5A4MN-ygr_e5vaNioA@mail.gmail.com>
References: <CA+Y385yiZmpvOg_KUzdRzjwpuGka-xDqv1YZrkuEakv2CTLWbA@mail.gmail.com>
 <CADHSJjA2H=mfE48w05TXOSzKfs912gsz2CL7E=mvhOxPNyq5FA@mail.gmail.com>
 <575e4d66cec04221a06d846344dd5e6d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjA1=xKJvAE2ixxJ_UWgR-fmzrf_Fv3L5WLn3C-gFRs45w@mail.gmail.com>
 <CADHSJjBKvXkhD+BGi=ggGQti-dvoi_NzZ3LFDw20D5310HBTUg@mail.gmail.com>
 <CADLMsL63gxoCOh80Q+B4yQ18JmyZU51M5A4MN-ygr_e5vaNioA@mail.gmail.com>
Message-ID: <CADHSJjAUD+=-jzY2g-UWTc_Y91EVqffztM3DDnz4EjpEsSpj7A@mail.gmail.com>

So far, all indicators point to a driver bug. To confirm, is everyone
reporting this issue encountering it on NVIDIA GPUs with Windows?

Utkarsh

On Thu, Jul 6, 2017 at 8:35 PM, stephane???? ?? <stephane at fujielectric.com>
wrote:

> Hello,
>
> I just want to  add that it's happening in both 5.3 and 5.4
>
> Ndong-Mefane Stephane, Dr.Eng
> Basic Design Sec.
> Steam Turbine Dept.
> Kawasaki Factory
>
> Fuji Electric Co., Ltd
> 1-1, Tanabeshinden, Kawasaki-ku,
> Kawasaki-city 210-9530, Japan
> Phone: +81-44-329-2155 <+81%2044-329-2155>
> Fax: +81-44-329-2394 <+81%2044-329-2394>
>
>
> On Thu, Jul 6, 2017 at 11:14 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Just to give an update, while I couldn't reproduce the issue with Giles
>> example, I was able to do it with another customer. It's quite a curious
>> thing indeed! Still figuring out where to begin to debug this -- the fact
>> that it's a Windows only thing makes it even more tedious -- but will keep
>> you posted.
>>
>> Utkarsh
>>
>> On Fri, Jun 23, 2017 at 12:08 PM, Utkarsh Ayachit <
>> utkarsh.ayachit at kitware.com> wrote:
>>
>>> Alan,
>>>
>>> I am discussing with Giles off line. Will keep you posted.
>>>
>>> Utkarsh
>>>
>>> On Fri, Jun 23, 2017 at 12:05 PM, Scott, W Alan <wascott at sandia.gov>
>>> wrote:
>>> > I have another user with this complaint.  I have not been able to
>>> replicate it.
>>> >
>>> > Are you using either opacity or volume rendering?
>>> >
>>> > Would you be able to pass the data files to Kitware?
>>> >
>>> > Alan
>>> >
>>> >> -----Original Message-----
>>> >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
>>> >> Utkarsh Ayachit
>>> >> Sent: Friday, June 23, 2017 7:07 AM
>>> >> To: Richardson CFD <garcfd at gmail.com>
>>> >> Cc: ParaView <paraview at paraview.org>
>>> >> Subject: [EXTERNAL] Re: [Paraview] long animations are freezing
>>> halfway
>>> >> through
>>> >>
>>> >> Giles,
>>> >>
>>> >> What OS is this on?
>>> >>
>>> >> Utkarsh
>>> >>
>>> >> On Fri, Jun 23, 2017 at 8:59 AM, Richardson CFD <garcfd at gmail.com>
>>> wrote:
>>> >> > I have been having trouble creating longer animations (150 frames)
>>> >> > from larger data files (1million cells). The animation works fine
>>> >> > initially but then freezes up about half way through the avi file -
>>> >> > displaying just a constant unchanging image. Streamlines seems to
>>> work
>>> >> > fine, but velocity contours (attached) is the one causing problems.
>>> I
>>> >> > am having to create the animation in 2 parts, creating 2 seperate
>>> avi
>>> >> > file and then join them after.
>>> >> >
>>> >> > Any suggestions or similar experience please let me know. Regards
>>> Giles.
>>> >> >
>>> >> > --
>>> >> > Richardson CFD
>>> >> > http://richardsoncfd.weebly.com
>>> >> >
>>> >> > _______________________________________________
>>> >> > 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/8caa7f81/attachment.html>

From andy.bauer at kitware.com  Tue Jul 11 11:02:28 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 11 Jul 2017 11:02:28 -0400
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
In-Reply-To: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>
References: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>
Message-ID: <CAMaOp+FTJV-QoLafw8gXMNO-+SgWQ5aReJtvKTWO5G3UYC_xOg@mail.gmail.com>

Hi Simon,

I tried with PV master (84f6e514) and couldn't replicate the crash. I was
able to get the connection between the GUI and the CatalystTest executable
though since I saw the PVTrivialProducer come up in the GUI.

Maybe you could try PV master and see if it works for you. Beyond that I
think figuring out your issue would take a non-trivial amount of effort to
figure out.

Cheers,
Andy

On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann <
klarmann at mechanik.tu-darmstadt.de> wrote:

> Hi Andy,
>
>
>
> I want to be able to close the connection from both sides. Closing the
> connection from the Insitu side works by calling vtkLiveInsituLink::
> DropLiveInsituConnection().
>
> Closing the connection from the Live side, e.g. by closing the GUI, causes
> my application to hang in the vtkSocket::Receive() method.
>
>
>
> After enabling the Debug mode I get the following Error on the Insitu side:
>
> ?ERROR: In D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line
> 572
>
> vtkClientSocket (0000000008BFFC00): Socket error in call to send. Eine
> bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer
> abgebrochen.?
>
>
>
> ?Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer
> abgebrochen?
>
> This seems to be a windows specific message notifying about a software
> controlled termination of the connection. So the information of the
> termination of the connection is somewhere available. The method throwing
> this error is the vtkSocket::Send() method.
>
>
>
> This error shows up as soon as I close the connection from the Live side
> (GUI) and then perform an InsituUpdate on the Insitu side. Still after this
> message, my Insitu side runs into vtkSocket::Receive() and get stuck there,
> trying to receive data.
>
>
>
>
>
> Additional Info:
>
> Performing the live visualization with the vtkCPPythonAdapter leads to the
> same error message and a crash of the Insitu application.
>
>
>
> Attached is a minimalistic working example. In both cases the error
> happens.
>
>
>
> Steps to reproduce:
>
> 1.       Start Paraview ->Catalyst->Connect
>
> 2.       Start the application, choose either 0 for python or 1 for cpp,
> then the PVTrivialproducer should show up in Paraview
>
> 3.       Close Paraview
>
> 4.       Continue the application ->crash
>
>
>
>
>
> I hope this helps a little bit to get an insight on what I did.
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
> *Von:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Gesendet:* Montag, 10. Juli 2017 22:21
>
> *An:* Simon Klarmann
> *Cc:* paraview at paraview.org
> *Betreff:* Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop
> on Windows
>
>
>
> Hi,
>
>
>
> Are you trying to close the connection from the in situ side? The design
> was for the connection to be close through the GUI.
>
>
>
> It's difficult to say what exactly is going on here without getting fairly
> deep into the problem. Theoretically though it should be possible to do the
> Live link in C++ as most of the Python routines call wrapped C++ routines.
>
>
>
> There should be some way to figure out the status of the connection on the
> PV server (the builtin server if you're not connected to a separate
> pvserver process) either the NotifyClientDisconnected() method,
> or vtkLiveInsituLink::OnConnectionClosedEvent() or vtkLiveInsituLink::DropLiveInsituConnection()
> member functions.
>
>
>
> Cheers,
>
> Andy
>
>
>
> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann <klarmann at mechanik.tu-
> darmstadt.de> wrote:
>
> Sorry I think I have chosen the wrong reply method.
>
>
>
> Hi Andy,
>
>
>
> I already got rid of Python on both sides. CoProcessing with Live
> connection is working by directly using the vtkLiveInsituLink (pure C++
> implementation).
>
>
>
> Working with both Paraview 5.2  and 5.4.
>
>
>
> My problem is closing the connection on the Live side (e.g. closing
> Paraview). Doing so, my Insitu side hangs (when trying again to send data,
> m_link->InsituUpdate, see below) in the receive method of the vtkSocket
> class until at some point an integer underflow happens.
>
>
>
> Closing the connection from the Insitu side everything works as expected.
>
>
>
> Are there any methods to directly check if the connection is still alive?
>
> Or is it a Windows specific problem?
>
>
>
>
>
>
>
> Additionally the steps for the live connection in C++, for sure there may
> be more elegant ways:
>
>
>
> // Initialization
>
>
>
> vtkCPProcessor  *m_proc = vtkCPProcessor::New();
>
>                 m_proc->Initialize();
>
>
>
>                 vtkLiveInsituLink  *m_link = vtkLiveInsituLink::New();
>
>                 m_link->SetInsituPort(22222);
>
>                 m_link->SetHostname("localhost");
>
>                 m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>
>
>
>                 vtkSMProxyManager  *m_spxm = vtkSMProxyManager::
> GetProxyManager()->GetActiveSessionProxyManager();
>
>                 vtkSMProxy *m_px = m_spxm->NewProxy("sources",
> "PVTrivialProducer");
>
>                 vtkSMSourceProxy *m_spx = vtkSMSourceProxy::
> SafeDownCast(m_px);
>
>                 m_spxm->RegisterProxy("sources", m_spx);
>
>
>
>                 vtkObjectBase *obase = m_spx->GetClientSideObject();
>
>                 vtkPVTrivialProducer *prod =
>
>                                vtkPVTrivialProducer::SafeDownCast(obase);
>
>                 prod->SetOutput(m_toplot, m_time);    // m_toplot is a
> vtkMultiBlockDataSet
>
>
>
>                 m_link->Initialize(m_spxm);
>
>
>
>
>
>                 //Update the live side
>
>                 m_link->InsituUpdate(m_time, m_tstep);
>
> m_spx->UpdatePipeline(m_time);
>
> m_link->InsituPostProcess(m_time,m_tstep);
>
>
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Gesendet:* Donnerstag, 6. Juli 2017 17:14
> *An:* Simon Klarmann
> *Cc:* paraview at paraview.org
> *Betreff:* Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop
> on Windows
>
>
>
> Hi Simon,
>
>
>
> Is the Python dependency that you're trying to get rid of on the Catalyst
> side or on the pvserver/GUI side? If I remember correctly on the Catalyst
> side Python was required for the Live connection.
>
>
>
> Cheers,
>
> Andy
>
>
>
> On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann <klarmann at mechanik.tu-
> darmstadt.de> wrote:
>
> Dear Members,
>
>
>
> I wanted to get rid of the dependency on Python. The connection by pure
> C++ works just fine.
>
>
>
> The problem occurs when establishing the live connection to Paraview,
> closing Paraview and then try to send some data again.
>
> I tracked it down to the vtkSocket class inside the method Receive. After
> the connection is terminated on the Paraview side, e.g. by closing
> Paraview, the call of vtkLiveInsituLink::InsituUpdate gets stuck in the
> vtkSocket::Receive method. Even though I get a message that the connection
> was terminated.
>
>
>
> A temporary fix for my case was to replace in Line 609 of the
> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
> disconnection the return value of nRecvd is -1. Then everything works well.
>
>
>
> I only used the following methods in the given order to transfer the data:
>
>
>
> vtkLiveInsituLink::InsituUpdate
>
> vtkSMSourceProxy::UpdatePipeline
>
> vtkLiveInsituLink::InsituPostProcess
>
>
>
>
>
> Are there further steps to perform or is there a way to check if the
> connection is still alive?
>
>
>
>
>
> Operating System: Windows 7, Visual Studio 2017
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
> Dipl.-Ing. Simon Klarmann
>
>
>
> *Bau- und Umweltingenieurwissenschaften*
> Technische Universit?t Darmstadt
>
> Fachgebiet Festk?rpermechanik
>
>
>
> Tel.: +49 6151 16 ? 22642 <+49%206151%201622642>
>
> Mail: klarmann at mechanik.tu-darmstadt.de
>
> Franziska-Braun-Stra?e 7
>
> Geb?ude L5|01, Raum 542
>
> 64287 Darmstadt
>
>
>
>
> _______________________________________________
> 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
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/d85c7159/attachment.html>

From nhibbar2 at illinois.edu  Tue Jul 11 11:12:06 2017
From: nhibbar2 at illinois.edu (Nathan Hibbard)
Date: Tue, 11 Jul 2017 10:12:06 -0500
Subject: [Paraview] Extracting actual time data
Message-ID: <CAJ80vbzhYGsRsVe51zCFR4cxx77mTVJS4F=D-qv1_VJ_P5ygOw@mail.gmail.com>

So when extracting data into a .csv file and including all time steps, is
it possible to get the actual time extracted to along with the time step?
In this particular "Plot over line" simulation that I am running, the time
steps are dynamic and not neccesarily the same length. Any help is greatly
appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/93e820e9/attachment.html>

From dennis_conklin at goodyear.com  Tue Jul 11 13:11:38 2017
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Tue, 11 Jul 2017 17:11:38 +0000
Subject: [Paraview] Extracting actual time data
Message-ID: <SN2PR0701MB78478C9B97D5B4C6608CEAD9FAE0@SN2PR0701MB784.namprd07.prod.outlook.com>

Nathan,

When we export data over timesteps from an Exodus file, we run a time-plot filter first, such as Plot Global Variables Over Time.   This creates a variable which contains the length of each timestep.   If you then export to .csv, that time variable is  included.

I suppose Plot Selection Over Time would probably also work.

Hope this helps.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/60ede7c5/attachment.html>

From klarmann at mechanik.tu-darmstadt.de  Tue Jul 11 13:58:31 2017
From: klarmann at mechanik.tu-darmstadt.de (klarmann at mechanik.tu-darmstadt.de)
Date: Tue, 11 Jul 2017 19:58:31 +0200
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
 Windows
In-Reply-To: <CAMaOp+FTJV-QoLafw8gXMNO-+SgWQ5aReJtvKTWO5G3UYC_xOg@mail.gmail.com>
References: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>
 <CAMaOp+FTJV-QoLafw8gXMNO-+SgWQ5aReJtvKTWO5G3UYC_xOg@mail.gmail.com>
Message-ID: <1a3f0a0d03bbfd0d89863f6443897e1d@mechanik.tu-darmstadt.de>

Hi Andy,

I just tried my example on arch linux and it works as expected. 
(ParaView 5.4.0-RC1)

Somehow I got the feeling it is an issue related to Windows. Just to be 
sure, which OS did you choose to test the example code?

Thank you very much for your time and support,
Simon



Am 2017-07-11 17:02, schrieb Andy Bauer:
> Hi Simon,
> 
> I tried with PV master (84f6e514) and couldn't replicate the crash. I
> was able to get the connection between the GUI and the CatalystTest
> executable though since I saw the PVTrivialProducer come up in the
> GUI.
> 
> Maybe you could try PV master and see if it works for you. Beyond that
> I think figuring out your issue would take a non-trivial amount of
> effort to figure out.
> 
> Cheers,
> Andy
> 
> On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann
> <klarmann at mechanik.tu-darmstadt.de> wrote:
> 
>> Hi Andy,
>> 
>> I want to be able to close the connection from both sides. Closing
>> the connection from the Insitu side works by calling
>> vtkLiveInsituLink::DropLiveInsituConnection().
>> 
>> Closing the connection from the Live side, e.g. by closing the GUI,
>> causes my application to hang in the vtkSocket::Receive() method.
>> 
>> After enabling the Debug mode I get the following Error on the
>> Insitu side:
>> 
>> ?ERROR: In
>> D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572
>> 
>> vtkClientSocket (0000000008BFFC00): Socket error in call to send.
>> Eine bestehende Verbindung wurde softwaregesteuert durch den
>> Hostcomputer abgebrochen.?
>> 
>> ?Eine bestehende Verbindung wurde softwaregesteuert durch den
>> Hostcomputer abgebrochen?
>> 
>> This seems to be a windows specific message notifying about a
>> software controlled termination of the connection. So the
>> information of the termination of the connection is somewhere
>> available. The method throwing this error is the vtkSocket::Send()
>> method.
>> 
>> This error shows up as soon as I close the connection from the Live
>> side (GUI) and then perform an InsituUpdate on the Insitu side.
>> Still after this message, my Insitu side runs into
>> vtkSocket::Receive() and get stuck there, trying to receive data.
>> 
>> Additional Info:
>> 
>> Performing the live visualization with the vtkCPPythonAdapter leads
>> to the same error message and a crash of the Insitu application.
>> 
>> Attached is a minimalistic working example. In both cases the error
>> happens.
>> 
>> Steps to reproduce:
>> 
>> 1.       Start Paraview ->Catalyst->Connect
>> 
>> 2.       Start the application, choose either 0 for python or 1 for
>> cpp, then the PVTrivialproducer should show up in Paraview
>> 
>> 3.       Close Paraview
>> 
>> 4.       Continue the application ->crash
>> 
>> I hope this helps a little bit to get an insight on what I did.
>> 
>> Thanks,
>> 
>> Simon
>> 
>> VON: Andy Bauer [mailto:andy.bauer at kitware.com [1]]
>> GESENDET: Montag, 10. Juli 2017 22:21
>> 
>> AN: Simon Klarmann
>> CC: paraview at paraview.org
>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>> loop on Windows
>> 
>> Hi,
>> 
>> Are you trying to close the connection from the in situ side? The
>> design was for the connection to be close through the GUI.
>> 
>> It's difficult to say what exactly is going on here without getting
>> fairly deep into the problem. Theoretically though it should be
>> possible to do the Live link in C++ as most of the Python routines
>> call wrapped C++ routines.
>> 
>> There should be some way to figure out the status of the connection
>> on the PV server (the builtin server if you're not connected to a
>> separate pvserver process) either the NotifyClientDisconnected()
>> method, or vtkLiveInsituLink::OnConnectionClosedEvent() or
>> vtkLiveInsituLink::DropLiveInsituConnection() member functions.
>> 
>> Cheers,
>> 
>> Andy
>> 
>> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>> 
>> Sorry I think I have chosen the wrong reply method.
>> 
>> Hi Andy,
>> 
>> I already got rid of Python on both sides. CoProcessing with Live
>> connection is working by directly using the vtkLiveInsituLink (pure
>> C++ implementation).
>> 
>> Working with both Paraview 5.2  and 5.4.
>> 
>> My problem is closing the connection on the Live side (e.g. closing
>> Paraview). Doing so, my Insitu side hangs (when trying again to send
>> data, m_link->InsituUpdate, see below) in the receive method of the
>> vtkSocket class until at some point an integer underflow happens.
>> 
>> Closing the connection from the Insitu side everything works as
>> expected.
>> 
>> Are there any methods to directly check if the connection is still
>> alive?
>> 
>> Or is it a Windows specific problem?
>> 
>> Additionally the steps for the live connection in C++, for sure
>> there may be more elegant ways:
>> 
>> // Initialization
>> 
>> vtkCPProcessor  *m_proc = vtkCPProcessor::New();
>> 
>> m_proc->Initialize();
>> 
>> vtkLiveInsituLink  *m_link =
>> vtkLiveInsituLink::New();
>> 
>> m_link->SetInsituPort(22222);
>> 
>> m_link->SetHostname("localhost");
>> 
>> m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>> 
>> vtkSMProxyManager  *m_spxm =
>> 
> vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();
>> 
>> vtkSMProxy *m_px = m_spxm->NewProxy("sources",
>> "PVTrivialProducer");
>> 
>> vtkSMSourceProxy *m_spx =
>> vtkSMSourceProxy::SafeDownCast(m_px);
>> 
>> m_spxm->RegisterProxy("sources", m_spx);
>> 
>> vtkObjectBase *obase = m_spx->GetClientSideObject();
>> 
>> vtkPVTrivialProducer *prod =
>> 
>> 
>> vtkPVTrivialProducer::SafeDownCast(obase);
>> 
>> prod->SetOutput(m_toplot, m_time);    // m_toplot is
>> a vtkMultiBlockDataSet
>> 
>> m_link->Initialize(m_spxm);
>> 
>> //Update the live side
>> 
>> m_link->InsituUpdate(m_time, m_tstep);
>> 
>> m_spx->UpdatePipeline(m_time);
>> 
>> m_link->InsituPostProcess(m_time,m_tstep);
>> 
>> Thanks,
>> 
>> Simon
>> 
>> VON: Andy Bauer [mailto:andy.bauer at kitware.com]
>> GESENDET: Donnerstag, 6. Juli 2017 17:14
>> AN: Simon Klarmann
>> CC: paraview at paraview.org
>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>> loop on Windows
>> 
>> Hi Simon,
>> 
>> Is the Python dependency that you're trying to get rid of on the
>> Catalyst side or on the pvserver/GUI side? If I remember correctly
>> on the Catalyst side Python was required for the Live connection.
>> 
>> Cheers,
>> 
>> Andy
>> 
>> On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>> 
>> Dear Members,
>> 
>> I wanted to get rid of the dependency on Python. The connection by
>> pure C++ works just fine.
>> 
>> The problem occurs when establishing the live connection to
>> Paraview, closing Paraview and then try to send some data again.
>> 
>> I tracked it down to the vtkSocket class inside the method Receive.
>> After the connection is terminated on the Paraview side, e.g. by
>> closing Paraview, the call of vtkLiveInsituLink::InsituUpdate gets
>> stuck in the vtkSocket::Receive method. Even though I get a message
>> that the connection was terminated.
>> 
>> A temporary fix for my case was to replace in Line 609 of the
>> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
>> disconnection the return value of nRecvd is -1. Then everything
>> works well.
>> 
>> I only used the following methods in the given order to transfer the
>> data:
>> 
>> vtkLiveInsituLink::InsituUpdate
>> 
>> vtkSMSourceProxy::UpdatePipeline
>> 
>> vtkLiveInsituLink::InsituPostProcess
>> 
>> Are there further steps to perform or is there a way to check if the
>> connection is still alive?
>> 
>> Operating System: Windows 7, Visual Studio 2017
>> 
>> Thanks,
>> 
>> Simon
>> 
>> Dipl.-Ing. Simon Klarmann
>> 
>> BAU- UND UMWELTINGENIEURWISSENSCHAFTEN
>> Technische Universit?t Darmstadt
>> 
>> Fachgebiet Festk?rpermechanik
>> 
>> Tel.: +49 6151 16 ? 22642 [2]
>> 
>> Mail: klarmann at mechanik.tu-darmstadt.de
>> 
>> Franziska-Braun-Stra?e 7
>> 
>> Geb?ude L5|01, Raum 542
>> 
>> 64287 Darmstadt
>> 
>> _______________________________________________
>> Powered by www.kitware.com [3]
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [4]
>> 
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [5]
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> [6]
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [7]
> 
> 
> 
> Links:
> ------
> [1] http://re.com
> [2] tel:+49%206151%201622642
> [3] http://www.kitware.com
> [4] http://www.kitware.com/opensource/opensource.html
> [5] http://paraview.org/Wiki/ParaView
> [6] http://markmail.org/search/?q=ParaView
> [7] http://public.kitware.com/mailman/listinfo/paraview

From andy.bauer at kitware.com  Tue Jul 11 14:17:32 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 11 Jul 2017 14:17:32 -0400
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
	Windows
In-Reply-To: <1a3f0a0d03bbfd0d89863f6443897e1d@mechanik.tu-darmstadt.de>
References: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>
 <CAMaOp+FTJV-QoLafw8gXMNO-+SgWQ5aReJtvKTWO5G3UYC_xOg@mail.gmail.com>
 <1a3f0a0d03bbfd0d89863f6443897e1d@mechanik.tu-darmstadt.de>
Message-ID: <CAMaOp+HAYTG__ZBL-ZAuhMosJwrOfRZZmi4YeueaEkoLnfdm-Q@mail.gmail.com>

Hi,

I tested on Linux (Ubuntu 16.04).

Best,
Andy

On Tue, Jul 11, 2017 at 1:58 PM, <klarmann at mechanik.tu-darmstadt.de> wrote:

> Hi Andy,
>
> I just tried my example on arch linux and it works as expected. (ParaView
> 5.4.0-RC1)
>
> Somehow I got the feeling it is an issue related to Windows. Just to be
> sure, which OS did you choose to test the example code?
>
> Thank you very much for your time and support,
> Simon
>
>
>
>
> Am 2017-07-11 17:02, schrieb Andy Bauer:
>
>> Hi Simon,
>>
>> I tried with PV master (84f6e514) and couldn't replicate the crash. I
>> was able to get the connection between the GUI and the CatalystTest
>> executable though since I saw the PVTrivialProducer come up in the
>> GUI.
>>
>> Maybe you could try PV master and see if it works for you. Beyond that
>> I think figuring out your issue would take a non-trivial amount of
>> effort to figure out.
>>
>> Cheers,
>> Andy
>>
>> On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>>
>> Hi Andy,
>>>
>>> I want to be able to close the connection from both sides. Closing
>>> the connection from the Insitu side works by calling
>>> vtkLiveInsituLink::DropLiveInsituConnection().
>>>
>>> Closing the connection from the Live side, e.g. by closing the GUI,
>>> causes my application to hang in the vtkSocket::Receive() method.
>>>
>>> After enabling the Debug mode I get the following Error on the
>>> Insitu side:
>>>
>>> ?ERROR: In
>>> D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572
>>>
>>> vtkClientSocket (0000000008BFFC00): Socket error in call to send.
>>> Eine bestehende Verbindung wurde softwaregesteuert durch den
>>> Hostcomputer abgebrochen.?
>>>
>>> ?Eine bestehende Verbindung wurde softwaregesteuert durch den
>>> Hostcomputer abgebrochen?
>>>
>>> This seems to be a windows specific message notifying about a
>>> software controlled termination of the connection. So the
>>> information of the termination of the connection is somewhere
>>> available. The method throwing this error is the vtkSocket::Send()
>>> method.
>>>
>>> This error shows up as soon as I close the connection from the Live
>>> side (GUI) and then perform an InsituUpdate on the Insitu side.
>>> Still after this message, my Insitu side runs into
>>> vtkSocket::Receive() and get stuck there, trying to receive data.
>>>
>>> Additional Info:
>>>
>>> Performing the live visualization with the vtkCPPythonAdapter leads
>>> to the same error message and a crash of the Insitu application.
>>>
>>> Attached is a minimalistic working example. In both cases the error
>>> happens.
>>>
>>> Steps to reproduce:
>>>
>>> 1.       Start Paraview ->Catalyst->Connect
>>>
>>> 2.       Start the application, choose either 0 for python or 1 for
>>> cpp, then the PVTrivialproducer should show up in Paraview
>>>
>>> 3.       Close Paraview
>>>
>>> 4.       Continue the application ->crash
>>>
>>> I hope this helps a little bit to get an insight on what I did.
>>>
>>> Thanks,
>>>
>>> Simon
>>>
>>> VON: Andy Bauer [mailto:andy.bauer at kitware.com [1]]
>>> GESENDET: Montag, 10. Juli 2017 22:21
>>>
>>> AN: Simon Klarmann
>>> CC: paraview at paraview.org
>>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>>>
>>> loop on Windows
>>>
>>> Hi,
>>>
>>> Are you trying to close the connection from the in situ side? The
>>> design was for the connection to be close through the GUI.
>>>
>>> It's difficult to say what exactly is going on here without getting
>>> fairly deep into the problem. Theoretically though it should be
>>> possible to do the Live link in C++ as most of the Python routines
>>> call wrapped C++ routines.
>>>
>>> There should be some way to figure out the status of the connection
>>> on the PV server (the builtin server if you're not connected to a
>>> separate pvserver process) either the NotifyClientDisconnected()
>>> method, or vtkLiveInsituLink::OnConnectionClosedEvent() or
>>> vtkLiveInsituLink::DropLiveInsituConnection() member functions.
>>>
>>> Cheers,
>>>
>>> Andy
>>>
>>> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann
>>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>>>
>>> Sorry I think I have chosen the wrong reply method.
>>>
>>> Hi Andy,
>>>
>>> I already got rid of Python on both sides. CoProcessing with Live
>>> connection is working by directly using the vtkLiveInsituLink (pure
>>> C++ implementation).
>>>
>>> Working with both Paraview 5.2  and 5.4.
>>>
>>> My problem is closing the connection on the Live side (e.g. closing
>>> Paraview). Doing so, my Insitu side hangs (when trying again to send
>>> data, m_link->InsituUpdate, see below) in the receive method of the
>>> vtkSocket class until at some point an integer underflow happens.
>>>
>>> Closing the connection from the Insitu side everything works as
>>> expected.
>>>
>>> Are there any methods to directly check if the connection is still
>>> alive?
>>>
>>> Or is it a Windows specific problem?
>>>
>>> Additionally the steps for the live connection in C++, for sure
>>> there may be more elegant ways:
>>>
>>> // Initialization
>>>
>>> vtkCPProcessor  *m_proc = vtkCPProcessor::New();
>>>
>>> m_proc->Initialize();
>>>
>>> vtkLiveInsituLink  *m_link =
>>> vtkLiveInsituLink::New();
>>>
>>> m_link->SetInsituPort(22222);
>>>
>>> m_link->SetHostname("localhost");
>>>
>>> m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>>>
>>> vtkSMProxyManager  *m_spxm =
>>>
>>> vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();
>>
>>>
>>> vtkSMProxy *m_px = m_spxm->NewProxy("sources",
>>> "PVTrivialProducer");
>>>
>>> vtkSMSourceProxy *m_spx =
>>> vtkSMSourceProxy::SafeDownCast(m_px);
>>>
>>> m_spxm->RegisterProxy("sources", m_spx);
>>>
>>> vtkObjectBase *obase = m_spx->GetClientSideObject();
>>>
>>> vtkPVTrivialProducer *prod =
>>>
>>>
>>> vtkPVTrivialProducer::SafeDownCast(obase);
>>>
>>> prod->SetOutput(m_toplot, m_time);    // m_toplot is
>>> a vtkMultiBlockDataSet
>>>
>>> m_link->Initialize(m_spxm);
>>>
>>> //Update the live side
>>>
>>> m_link->InsituUpdate(m_time, m_tstep);
>>>
>>> m_spx->UpdatePipeline(m_time);
>>>
>>> m_link->InsituPostProcess(m_time,m_tstep);
>>>
>>> Thanks,
>>>
>>> Simon
>>>
>>> VON: Andy Bauer [mailto:andy.bauer at kitware.com]
>>> GESENDET: Donnerstag, 6. Juli 2017 17:14
>>> AN: Simon Klarmann
>>> CC: paraview at paraview.org
>>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>>>
>>> loop on Windows
>>>
>>> Hi Simon,
>>>
>>> Is the Python dependency that you're trying to get rid of on the
>>> Catalyst side or on the pvserver/GUI side? If I remember correctly
>>> on the Catalyst side Python was required for the Live connection.
>>>
>>> Cheers,
>>>
>>> Andy
>>>
>>> On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann
>>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>>>
>>> Dear Members,
>>>
>>> I wanted to get rid of the dependency on Python. The connection by
>>> pure C++ works just fine.
>>>
>>> The problem occurs when establishing the live connection to
>>> Paraview, closing Paraview and then try to send some data again.
>>>
>>> I tracked it down to the vtkSocket class inside the method Receive.
>>> After the connection is terminated on the Paraview side, e.g. by
>>> closing Paraview, the call of vtkLiveInsituLink::InsituUpdate gets
>>> stuck in the vtkSocket::Receive method. Even though I get a message
>>> that the connection was terminated.
>>>
>>> A temporary fix for my case was to replace in Line 609 of the
>>> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
>>> disconnection the return value of nRecvd is -1. Then everything
>>> works well.
>>>
>>> I only used the following methods in the given order to transfer the
>>> data:
>>>
>>> vtkLiveInsituLink::InsituUpdate
>>>
>>> vtkSMSourceProxy::UpdatePipeline
>>>
>>> vtkLiveInsituLink::InsituPostProcess
>>>
>>> Are there further steps to perform or is there a way to check if the
>>> connection is still alive?
>>>
>>> Operating System: Windows 7, Visual Studio 2017
>>>
>>> Thanks,
>>>
>>> Simon
>>>
>>> Dipl.-Ing. Simon Klarmann
>>>
>>> BAU- UND UMWELTINGENIEURWISSENSCHAFTEN
>>> Technische Universit?t Darmstadt
>>>
>>> Fachgebiet Festk?rpermechanik
>>>
>>> Tel.: +49 6151 16 ? 22642 [2]
>>>
>>> Mail: klarmann at mechanik.tu-darmstadt.de
>>>
>>> Franziska-Braun-Stra?e 7
>>>
>>> Geb?ude L5|01, Raum 542
>>>
>>> 64287 Darmstadt
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com [3]
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html [4]
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView [5]
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>> [6]
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview [7]
>>>
>>
>>
>>
>> Links:
>> ------
>> [1] http://re.com
>> [2] tel:+49%206151%201622642
>> [3] http://www.kitware.com
>> [4] http://www.kitware.com/opensource/opensource.html
>> [5] http://paraview.org/Wiki/ParaView
>> [6] http://markmail.org/search/?q=ParaView
>> [7] http://public.kitware.com/mailman/listinfo/paraview
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/ddb2d226/attachment.html>

From jake.a.gerard at gmail.com  Tue Jul 11 15:37:34 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Tue, 11 Jul 2017 14:37:34 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
Message-ID: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>

Good Afternoon,

I have been moving to an HDF5/XDMF system for analyzing big data from a
computational fluid model. I finally got all the basic components working
on my local machine but have run into problems when trying to run on an HPC
system. Here is the XDMF file:

<?xml version="1.0" ?>
<!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
<Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
  <Domain>
    <Grid Name="my_Grid" GridType="Uniform">
      <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
      </Topology>
      <Geometry GeometryType="Origin_DxDyDz">
        <DataItem Dimensions="3" NumberType="Integer" Format="XML">
          0 0 0
        </DataItem>
        <DataItem Dimensions="3" NumberType="Integer" Format="XML">
          1 1 1
        </DataItem>
      </Geometry>
      <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
        <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
          out.h5:/pres_group/presmag
        </DataItem>
      </Attribute>
      <Attribute Name="velocity" AttributeType="Vector" Center="Node">
        <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
Dimensions="91 19 19 3">
          <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
            out.h5:/velo_group/x_velo
          </DataItem>
          <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
            out.h5:/velo_group/y_velo
          </DataItem>
          <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
            out.h5:/velo_group/z_velo
          </DataItem>
        </DataItem>
      </Attribute>
    </Grid>
  </Domain>
</Xdmf>

This has worked properly on my machine. However, when I was getting an
error of failing to read the pressure data when I tried this on multiple
processes. The vector data for velocity was fine, but the pressure data
could not be read. I narrowed the problem down to something regarding the
number of processes because the pressure data worked fine on the HPC
machine if I only ran it on 1 process. Is there anything that sticks out
that could be causing this problem? For instance, is there a different
format for these files when they are run on multiple processes?

Respectfully,

Jacob Gerard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/00ff7dd4/attachment.html>

From nabil.ghodbane at gmail.com  Tue Jul 11 18:49:52 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Wed, 12 Jul 2017 00:49:52 +0200
Subject: [Paraview] superbuild: configure: error swr requires C++14
	support
In-Reply-To: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>
References: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>
Message-ID: <CAPd7EPrmRjBDw_PBK3B5_yCx1Ha_rq4gQUp9pb7fMXqmi6PQXQ@mail.gmail.com>

dear experts,
the superbuild currently supports mpich (
http://www.paraview.org/files/dependencies/mpich-3.2.tar.gz). Did someone
by chance try to use openmpi (which version can be used in this case?) and
if so, is there some feedback one could benefit from ?
thanks.

Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com


On Tue, Jul 4, 2017 at 3:02 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
wrote:

> dear experts
> I am trying to compile Paraview with the latest superbuild using gcc 4.8.5
> the compilation fails with the error message that C++14 is needed...
> *configure: error swr requires C++14 support*
>
> This raises two questions:
> 1/ Can one switch to c++11  and if yes, how ?
> 2/ what is the minimal configuration for gcc one needs to setup in order
> to be able to compile Paraview with superbuild.
> thanks
>
>
> Nabil Ghodbane (Ph. D. Habil*.*)
> Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043>
> Mailto: nabil.ghodbane at gmail.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/fa62554f/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 11 20:19:56 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 11 Jul 2017 20:19:56 -0400
Subject: [Paraview] superbuild: configure: error swr requires C++14
	support
In-Reply-To: <CAPd7EPrmRjBDw_PBK3B5_yCx1Ha_rq4gQUp9pb7fMXqmi6PQXQ@mail.gmail.com>
References: <CAPd7EPpKxSK6QhxRGQNi-VSE6dna1rtYzHConJywd1C6SAe3kA@mail.gmail.com>
 <CAPd7EPrmRjBDw_PBK3B5_yCx1Ha_rq4gQUp9pb7fMXqmi6PQXQ@mail.gmail.com>
Message-ID: <CADHSJjD412Bw4XnkGqJ2-pQ_MSoOjYK1dGkd6+K7n67jCH32ag@mail.gmail.com>

Nabil,

OpenMPI would work just fine too. Use can make the superbuild use an
externally built MPI implementation very easily. As documented here (
https://gitlab.kitware.com/paraview/paraview-superbuild/), just set
the USE_SYSTEM_xxx (in this case, USE_SYSTEM_mpi) Cmake flag to ON and then
point to the MPI libs, if not in default path.

Utkarsh

On Tue, Jul 11, 2017 at 6:49 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
wrote:

> dear experts,
> the superbuild currently supports mpich (http://www.paraview.org/
> files/dependencies/mpich-3.2.tar.gz). Did someone by chance try to use
> openmpi (which version can be used in this case?) and if so, is there some
> feedback one could benefit from ?
> thanks.
>
> Nabil Ghodbane (Ph. D. Habil*.*)
> Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043>
> Mailto: nabil.ghodbane at gmail.com
>
>
> On Tue, Jul 4, 2017 at 3:02 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
> wrote:
>
>> dear experts
>> I am trying to compile Paraview with the latest superbuild using gcc 4.8.5
>> the compilation fails with the error message that C++14 is needed...
>> *configure: error swr requires C++14 support*
>>
>> This raises two questions:
>> 1/ Can one switch to c++11  and if yes, how ?
>> 2/ what is the minimal configuration for gcc one needs to setup in order
>> to be able to compile Paraview with superbuild.
>> thanks
>>
>>
>> Nabil Ghodbane (Ph. D. Habil*.*)
>> Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043>
>> Mailto: nabil.ghodbane at gmail.com
>>
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170711/34bb1eb7/attachment.html>

From klarmann at mechanik.tu-darmstadt.de  Wed Jul 12 05:38:46 2017
From: klarmann at mechanik.tu-darmstadt.de (klarmann at mechanik.tu-darmstadt.de)
Date: Wed, 12 Jul 2017 11:38:46 +0200
Subject: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on
 Windows
In-Reply-To: <CAMaOp+HAYTG__ZBL-ZAuhMosJwrOfRZZmi4YeueaEkoLnfdm-Q@mail.gmail.com>
References: <020701d2fa3d$da1c6a10$8e553e30$@mechanik.tu-darmstadt.de>
 <CAMaOp+FTJV-QoLafw8gXMNO-+SgWQ5aReJtvKTWO5G3UYC_xOg@mail.gmail.com>
 <1a3f0a0d03bbfd0d89863f6443897e1d@mechanik.tu-darmstadt.de>
 <CAMaOp+HAYTG__ZBL-ZAuhMosJwrOfRZZmi4YeueaEkoLnfdm-Q@mail.gmail.com>
Message-ID: <835f1ac78f767b5c5e2eaba3cb899a7e@mechanik.tu-darmstadt.de>

Hi,

I tested the PV master build now. Same thing happens as with PV 5.4 and 
5.2.
The example code works on linux but leads to a crash on windows.

In my opinion it is a bug in the vtkSocket regarding the windows 
specific code. I further investigated the problem and compared what 
happens. On linux an windows the method vtkSocket::Receive() gets called 
even after the connection is dropped by the Live side, so the call 
history should be the same.

The difference between linux and windows is that the function recv in 
line 606 of vtkSocket.cxx returns (if the connection is closed by the 
GUI) nRecvd=0 on linux and nRecvd=-1 (error code) on windows.

To fix the problem on windows I inserted the  following code at line 616 
of vtkSocket.cxx:

if ((nRecvd == vtkSocketErrorReturnMacro
	&& WSAGetLastError() == WSAECONNABORTED))
{
	return 0;
}


Maybe you can look into it.


Thanks,
Simon





Am 2017-07-11 20:17, schrieb Andy Bauer:
> Hi,
> 
> I tested on Linux (Ubuntu 16.04).
> 
> Best,
> Andy
> 
> On Tue, Jul 11, 2017 at 1:58 PM, <klarmann at mechanik.tu-darmstadt.de>
> wrote:
> 
>> Hi Andy,
>> 
>> I just tried my example on arch linux and it works as expected.
>> (ParaView 5.4.0-RC1)
>> 
>> Somehow I got the feeling it is an issue related to Windows. Just to
>> be sure, which OS did you choose to test the example code?
>> 
>> Thank you very much for your time and support,
>> Simon
>> 
>> Am 2017-07-11 17:02, schrieb Andy Bauer:
>> 
>> Hi Simon,
>> 
>> I tried with PV master (84f6e514) and couldn't replicate the crash.
>> I
>> was able to get the connection between the GUI and the CatalystTest
>> executable though since I saw the PVTrivialProducer come up in the
>> GUI.
>> 
>> Maybe you could try PV master and see if it works for you. Beyond
>> that
>> I think figuring out your issue would take a non-trivial amount of
>> effort to figure out.
>> 
>> Cheers,
>> Andy
>> 
>> On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>> 
>> Hi Andy,
>> 
>> I want to be able to close the connection from both sides. Closing
>> the connection from the Insitu side works by calling
>> vtkLiveInsituLink::DropLiveInsituConnection().
>> 
>> Closing the connection from the Live side, e.g. by closing the GUI,
>> causes my application to hang in the vtkSocket::Receive() method.
>> 
>> After enabling the Debug mode I get the following Error on the
>> Insitu side:
>> 
>> ?ERROR: In
>> D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572
>> 
>> vtkClientSocket (0000000008BFFC00): Socket error in call to send.
>> Eine bestehende Verbindung wurde softwaregesteuert durch den
>> Hostcomputer abgebrochen.?
>> 
>> ?Eine bestehende Verbindung wurde softwaregesteuert durch den
>> Hostcomputer abgebrochen?
>> 
>> This seems to be a windows specific message notifying about a
>> software controlled termination of the connection. So the
>> information of the termination of the connection is somewhere
>> available. The method throwing this error is the vtkSocket::Send()
>> method.
>> 
>> This error shows up as soon as I close the connection from the Live
>> side (GUI) and then perform an InsituUpdate on the Insitu side.
>> Still after this message, my Insitu side runs into
>> vtkSocket::Receive() and get stuck there, trying to receive data.
>> 
>> Additional Info:
>> 
>> Performing the live visualization with the vtkCPPythonAdapter leads
>> to the same error message and a crash of the Insitu application.
>> 
>> Attached is a minimalistic working example. In both cases the error
>> happens.
>> 
>> Steps to reproduce:
>> 
>> 1.       Start Paraview ->Catalyst->Connect
>> 
>> 2.       Start the application, choose either 0 for python or 1 for
>> cpp, then the PVTrivialproducer should show up in Paraview
>> 
>> 3.       Close Paraview
>> 
>> 4.       Continue the application ->crash
>> 
>> I hope this helps a little bit to get an insight on what I did.
>> 
>> Thanks,
>> 
>> Simon
>> 
>> VON: Andy Bauer [mailto:andy.bauer at kitware.com [1]]
>> GESENDET: Montag, 10. Juli 2017 22:21
>> 
>> AN: Simon Klarmann
>> CC: paraview at paraview.org
>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>> 
>> loop on Windows
>> 
>> Hi,
>> 
>> Are you trying to close the connection from the in situ side? The
>> design was for the connection to be close through the GUI.
>> 
>> It's difficult to say what exactly is going on here without getting
>> fairly deep into the problem. Theoretically though it should be
>> possible to do the Live link in C++ as most of the Python routines
>> call wrapped C++ routines.
>> 
>> There should be some way to figure out the status of the connection
>> on the PV server (the builtin server if you're not connected to a
>> separate pvserver process) either the NotifyClientDisconnected()
>> method, or vtkLiveInsituLink::OnConnectionClosedEvent() or
>> vtkLiveInsituLink::DropLiveInsituConnection() member functions.
>> 
>> Cheers,
>> 
>> Andy
>> 
>> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>> 
>> Sorry I think I have chosen the wrong reply method.
>> 
>> Hi Andy,
>> 
>> I already got rid of Python on both sides. CoProcessing with Live
>> connection is working by directly using the vtkLiveInsituLink (pure
>> C++ implementation).
>> 
>> Working with both Paraview 5.2  and 5.4.
>> 
>> My problem is closing the connection on the Live side (e.g. closing
>> Paraview). Doing so, my Insitu side hangs (when trying again to send
>> data, m_link->InsituUpdate, see below) in the receive method of the
>> vtkSocket class until at some point an integer underflow happens.
>> 
>> Closing the connection from the Insitu side everything works as
>> expected.
>> 
>> Are there any methods to directly check if the connection is still
>> alive?
>> 
>> Or is it a Windows specific problem?
>> 
>> Additionally the steps for the live connection in C++, for sure
>> there may be more elegant ways:
>> 
>> // Initialization
>> 
>> vtkCPProcessor  *m_proc = vtkCPProcessor::New();
>> 
>> m_proc->Initialize();
>> 
>> vtkLiveInsituLink  *m_link =
>> vtkLiveInsituLink::New();
>> 
>> m_link->SetInsituPort(22222);
>> 
>> m_link->SetHostname("localhost");
>> 
>> m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>> 
>> vtkSMProxyManager  *m_spxm =
>> 
>> 
> vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();
>> 
>> vtkSMProxy *m_px = m_spxm->NewProxy("sources",
>> "PVTrivialProducer");
>> 
>> vtkSMSourceProxy *m_spx =
>> vtkSMSourceProxy::SafeDownCast(m_px);
>> 
>> m_spxm->RegisterProxy("sources", m_spx);
>> 
>> vtkObjectBase *obase = m_spx->GetClientSideObject();
>> 
>> vtkPVTrivialProducer *prod =
>> 
>> vtkPVTrivialProducer::SafeDownCast(obase);
>> 
>> prod->SetOutput(m_toplot, m_time);    // m_toplot is
>> a vtkMultiBlockDataSet
>> 
>> m_link->Initialize(m_spxm);
>> 
>> //Update the live side
>> 
>> m_link->InsituUpdate(m_time, m_tstep);
>> 
>> m_spx->UpdatePipeline(m_time);
>> 
>> m_link->InsituPostProcess(m_time,m_tstep);
>> 
>> Thanks,
>> 
>> Simon
>> 
>> VON: Andy Bauer [mailto:andy.bauer at kitware.com]
>> GESENDET: Donnerstag, 6. Juli 2017 17:14
>> AN: Simon Klarmann
>> CC: paraview at paraview.org
>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
>> 
>> loop on Windows
>> 
>> Hi Simon,
>> 
>> Is the Python dependency that you're trying to get rid of on the
>> Catalyst side or on the pvserver/GUI side? If I remember correctly
>> on the Catalyst side Python was required for the Live connection.
>> 
>> Cheers,
>> 
>> Andy
>> 
>> On Wed, Jul 5, 2017 at 10:11 AM, Simon Klarmann
>> <klarmann at mechanik.tu-darmstadt.de> wrote:
>> 
>> Dear Members,
>> 
>> I wanted to get rid of the dependency on Python. The connection by
>> pure C++ works just fine.
>> 
>> The problem occurs when establishing the live connection to
>> Paraview, closing Paraview and then try to send some data again.
>> 
>> I tracked it down to the vtkSocket class inside the method Receive.
>> After the connection is terminated on the Paraview side, e.g. by
>> closing Paraview, the call of vtkLiveInsituLink::InsituUpdate gets
>> stuck in the vtkSocket::Receive method. Even though I get a message
>> that the connection was terminated.
>> 
>> A temporary fix for my case was to replace in Line 609 of the
>> vtkSocket.cxx if (nRecvd == 0) with if (nRecvd <= 0), because on
>> disconnection the return value of nRecvd is -1. Then everything
>> works well.
>> 
>> I only used the following methods in the given order to transfer the
>> data:
>> 
>> vtkLiveInsituLink::InsituUpdate
>> 
>> vtkSMSourceProxy::UpdatePipeline
>> 
>> vtkLiveInsituLink::InsituPostProcess
>> 
>> Are there further steps to perform or is there a way to check if the
>> connection is still alive?
>> 
>> Operating System: Windows 7, Visual Studio 2017
>> 
>> Thanks,
>> 
>> Simon
>> 
>> Dipl.-Ing. Simon Klarmann
>> 
>> BAU- UND UMWELTINGENIEURWISSENSCHAFTEN
>> Technische Universit?t Darmstadt
>> 
>> Fachgebiet Festk?rpermechanik
>> 
>> Tel.: +49 6151 16 [1] ? 22642 [2]
>> 
>> Mail: klarmann at mechanik.tu-darmstadt.de
>> 
>> Franziska-Braun-Stra?e 7
>> 
>> Geb?ude L5|01, Raum 542
>> 
>> 64287 Darmstadt
>> 
>> _______________________________________________
>> Powered by www.kitware.com [2] [3]
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [3] [4]
>> 
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [4] [5]
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> [5]
>> [6]
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [6] [7]
>> 
>> Links:
>> ------
>> [1] http://re.com
>> [2] tel:+49%206151%201622642
>> [3] http://www.kitware.com
>> [4] http://www.kitware.com/opensource/opensource.html [3]
>> [5] http://paraview.org/Wiki/ParaView [4]
>> [6] http://markmail.org/search/?q=ParaView [5]
>> [7] http://public.kitware.com/mailman/listinfo/paraview [6]
> 
> 
> 
> Links:
> ------
> [1] tel:%2B49%206151%2016
> [2] http://www.kitware.com
> [3] http://www.kitware.com/opensource/opensource.html
> [4] http://paraview.org/Wiki/ParaView
> [5] http://markmail.org/search/?q=ParaView
> [6] http://public.kitware.com/mailman/listinfo/paraview

From jake.a.gerard at gmail.com  Wed Jul 12 11:28:35 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Wed, 12 Jul 2017 10:28:35 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
Message-ID: <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>

Any help here would be greatly appreciated.

On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> Good Afternoon,
>
> I have been moving to an HDF5/XDMF system for analyzing big data from a
> computational fluid model. I finally got all the basic components working
> on my local machine but have run into problems when trying to run on an HPC
> system. Here is the XDMF file:
>
> <?xml version="1.0" ?>
> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>   <Domain>
>     <Grid Name="my_Grid" GridType="Uniform">
>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>       </Topology>
>       <Geometry GeometryType="Origin_DxDyDz">
>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>           0 0 0
>         </DataItem>
>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>           1 1 1
>         </DataItem>
>       </Geometry>
>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>           out.h5:/pres_group/presmag
>         </DataItem>
>       </Attribute>
>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
> Dimensions="91 19 19 3">
>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>             out.h5:/velo_group/x_velo
>           </DataItem>
>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>             out.h5:/velo_group/y_velo
>           </DataItem>
>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>             out.h5:/velo_group/z_velo
>           </DataItem>
>         </DataItem>
>       </Attribute>
>     </Grid>
>   </Domain>
> </Xdmf>
>
> This has worked properly on my machine. However, when I was getting an
> error of failing to read the pressure data when I tried this on multiple
> processes. The vector data for velocity was fine, but the pressure data
> could not be read. I narrowed the problem down to something regarding the
> number of processes because the pressure data worked fine on the HPC
> machine if I only ran it on 1 process. Is there anything that sticks out
> that could be causing this problem? For instance, is there a different
> format for these files when they are run on multiple processes?
>
> Respectfully,
>
> Jacob Gerard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/fd3a9faf/attachment.html>

From demaio.a at gmail.com  Wed Jul 12 12:00:53 2017
From: demaio.a at gmail.com (Alessandro De Maio)
Date: Wed, 12 Jul 2017 18:00:53 +0200
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
Message-ID: <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>

Hi Jake,
     when you talk about running in multi-processing are you talking about
the solver that produces the data or about running Paraview in mpi-mode?
Which is the error you get?

Alessandro

On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> Any help here would be greatly appreciated.
>
> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
> wrote:
>
>> Good Afternoon,
>>
>> I have been moving to an HDF5/XDMF system for analyzing big data from a
>> computational fluid model. I finally got all the basic components working
>> on my local machine but have run into problems when trying to run on an HPC
>> system. Here is the XDMF file:
>>
>> <?xml version="1.0" ?>
>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>   <Domain>
>>     <Grid Name="my_Grid" GridType="Uniform">
>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>       </Topology>
>>       <Geometry GeometryType="Origin_DxDyDz">
>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>           0 0 0
>>         </DataItem>
>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>           1 1 1
>>         </DataItem>
>>       </Geometry>
>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>           out.h5:/pres_group/presmag
>>         </DataItem>
>>       </Attribute>
>>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>> Dimensions="91 19 19 3">
>>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>             out.h5:/velo_group/x_velo
>>           </DataItem>
>>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>             out.h5:/velo_group/y_velo
>>           </DataItem>
>>           <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>             out.h5:/velo_group/z_velo
>>           </DataItem>
>>         </DataItem>
>>       </Attribute>
>>     </Grid>
>>   </Domain>
>> </Xdmf>
>>
>> This has worked properly on my machine. However, when I was getting an
>> error of failing to read the pressure data when I tried this on multiple
>> processes. The vector data for velocity was fine, but the pressure data
>> could not be read. I narrowed the problem down to something regarding the
>> number of processes because the pressure data worked fine on the HPC
>> machine if I only ran it on 1 process. Is there anything that sticks out
>> that could be causing this problem? For instance, is there a different
>> format for these files when they are run on multiple processes?
>>
>> Respectfully,
>>
>> Jacob Gerard
>>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/ccd975d2/attachment.html>

From jake.a.gerard at gmail.com  Wed Jul 12 13:31:53 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Wed, 12 Jul 2017 12:31:53 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
Message-ID: <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>

Alessandro,

Paraview says that it failed to read the attribute data. I just mean that
when I connect Paraview to the machine, the pressure data does not load if
I select more than 1 node or process/node.

Jake

On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <demaio.a at gmail.com>
wrote:

> Hi Jake,
>      when you talk about running in multi-processing are you talking about
> the solver that produces the data or about running Paraview in mpi-mode?
> Which is the error you get?
>
> Alessandro
>
> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
> wrote:
>
>> Any help here would be greatly appreciated.
>>
>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
>> wrote:
>>
>>> Good Afternoon,
>>>
>>> I have been moving to an HDF5/XDMF system for analyzing big data from a
>>> computational fluid model. I finally got all the basic components working
>>> on my local machine but have run into problems when trying to run on an HPC
>>> system. Here is the XDMF file:
>>>
>>> <?xml version="1.0" ?>
>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>   <Domain>
>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>       </Topology>
>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>           0 0 0
>>>         </DataItem>
>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>           1 1 1
>>>         </DataItem>
>>>       </Geometry>
>>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>>           out.h5:/pres_group/presmag
>>>         </DataItem>
>>>       </Attribute>
>>>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>> Dimensions="91 19 19 3">
>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>> Format="HDF">
>>>             out.h5:/velo_group/x_velo
>>>           </DataItem>
>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>> Format="HDF">
>>>             out.h5:/velo_group/y_velo
>>>           </DataItem>
>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>> Format="HDF">
>>>             out.h5:/velo_group/z_velo
>>>           </DataItem>
>>>         </DataItem>
>>>       </Attribute>
>>>     </Grid>
>>>   </Domain>
>>> </Xdmf>
>>>
>>> This has worked properly on my machine. However, when I was getting an
>>> error of failing to read the pressure data when I tried this on multiple
>>> processes. The vector data for velocity was fine, but the pressure data
>>> could not be read. I narrowed the problem down to something regarding the
>>> number of processes because the pressure data worked fine on the HPC
>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>> that could be causing this problem? For instance, is there a different
>>> format for these files when they are run on multiple processes?
>>>
>>> Respectfully,
>>>
>>> Jacob Gerard
>>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/c5a02ba4/attachment.html>

From agsmith424 at gmail.com  Wed Jul 12 14:48:00 2017
From: agsmith424 at gmail.com (Andy Smith)
Date: Wed, 12 Jul 2017 14:48:00 -0400
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
 <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
Message-ID: <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>

Jake,

If I start up the remote server in parallel using something like:
mpiexec.hydra -n 8 pvserver -sp=11111

and then connect from my workstation I am able to read an XDMF file like
the one you posted using ParaView 5.4.0.  Can you post how you are starting
your server and the exact error that you receive?

I've attached the .xmf file and a Python script to generate dummy data in a
.h5 file that corresponds to your data structure.

Note that I am using the xdmf2 reader for my testing.  The xdmf3 reader
fails to read the file (even locally in serial) with the following error:

Type not one of accepted values: INTEGER in XdmfArrayType::New
terminate called after throwing an instance of 'XdmfError'
  what():  Type not one of accepted values: INTEGER in XdmfArrayType::New
Aborted


-Andy

On Wed, Jul 12, 2017 at 1:31 PM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> Alessandro,
>
> Paraview says that it failed to read the attribute data. I just mean that
> when I connect Paraview to the machine, the pressure data does not load if
> I select more than 1 node or process/node.
>
> Jake
>
> On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <demaio.a at gmail.com>
> wrote:
>
>> Hi Jake,
>>      when you talk about running in multi-processing are you talking
>> about the solver that produces the data or about running Paraview in
>> mpi-mode?
>> Which is the error you get?
>>
>> Alessandro
>>
>> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
>> wrote:
>>
>>> Any help here would be greatly appreciated.
>>>
>>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>> wrote:
>>>
>>>> Good Afternoon,
>>>>
>>>> I have been moving to an HDF5/XDMF system for analyzing big data from a
>>>> computational fluid model. I finally got all the basic components working
>>>> on my local machine but have run into problems when trying to run on an HPC
>>>> system. Here is the XDMF file:
>>>>
>>>> <?xml version="1.0" ?>
>>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>>   <Domain>
>>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>>       </Topology>
>>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>           0 0 0
>>>>         </DataItem>
>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>           1 1 1
>>>>         </DataItem>
>>>>       </Geometry>
>>>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>>>         <DataItem Dimensions="91 19 19" NumberType="Float" Format="HDF">
>>>>           out.h5:/pres_group/presmag
>>>>         </DataItem>
>>>>       </Attribute>
>>>>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>>> Dimensions="91 19 19 3">
>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>> Format="HDF">
>>>>             out.h5:/velo_group/x_velo
>>>>           </DataItem>
>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>> Format="HDF">
>>>>             out.h5:/velo_group/y_velo
>>>>           </DataItem>
>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>> Format="HDF">
>>>>             out.h5:/velo_group/z_velo
>>>>           </DataItem>
>>>>         </DataItem>
>>>>       </Attribute>
>>>>     </Grid>
>>>>   </Domain>
>>>> </Xdmf>
>>>>
>>>> This has worked properly on my machine. However, when I was getting an
>>>> error of failing to read the pressure data when I tried this on multiple
>>>> processes. The vector data for velocity was fine, but the pressure data
>>>> could not be read. I narrowed the problem down to something regarding the
>>>> number of processes because the pressure data worked fine on the HPC
>>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>>> that could be causing this problem? For instance, is there a different
>>>> format for these files when they are run on multiple processes?
>>>>
>>>> Respectfully,
>>>>
>>>> Jacob Gerard
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/0166597e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testing.xmf
Type: application/octet-stream
Size: 1395 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/0166597e/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: create_testing_hdf5.py
Type: text/x-python
Size: 459 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/0166597e/attachment.py>

From wascott at sandia.gov  Wed Jul 12 15:23:20 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 12 Jul 2017 19:23:20 +0000
Subject: [Paraview] pvserver and mpi
Message-ID: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>

I remember a thread from a few weeks ago that the current Linux distribution has built in MPI.  Is this correct?  Does this mean a user can use the Kitware binaries on a cluster, without rebuilding?

Thanks,

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/2805f7f8/attachment.html>

From jake.a.gerard at gmail.com  Wed Jul 12 15:33:49 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Wed, 12 Jul 2017 14:33:49 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
 <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
 <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>
Message-ID: <CAES0UenfBX_t7ggwebdOHiGQ_N4aZTbR+bAsQ0Ky6VMm56Cg8A@mail.gmail.com>

Andy,

I wasn't setting up the server or anything. I have just been connecting to
one of my preset configurations. The velocity data shows up fine but for
some reason when there is more than one processor working on the
visualization Paraview can't read it.

Here is the error:

ERROR: In
/p/home/angel/PV/4.3.1/Build_4.3.1_osmesa/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx,
line 1128

vtkXdmfReader (0x104ae20): Failed to read attribute data


The setup has just been clicking the connect icon, the system, and choosing
the number of nodes and processors per node. If it helps I'm on Paraview
4.3.1 64-bit. Sorry I am pretty new to all of this stuff. Slowly getting
the hang of things.


Jake

On Wed, Jul 12, 2017 at 1:48 PM, Andy Smith <agsmith424 at gmail.com> wrote:

> Jake,
>
> If I start up the remote server in parallel using something like:
> mpiexec.hydra -n 8 pvserver -sp=11111
>
> and then connect from my workstation I am able to read an XDMF file like
> the one you posted using ParaView 5.4.0.  Can you post how you are starting
> your server and the exact error that you receive?
>
> I've attached the .xmf file and a Python script to generate dummy data in
> a .h5 file that corresponds to your data structure.
>
> Note that I am using the xdmf2 reader for my testing.  The xdmf3 reader
> fails to read the file (even locally in serial) with the following error:
>
> Type not one of accepted values: INTEGER in XdmfArrayType::New
> terminate called after throwing an instance of 'XdmfError'
>   what():  Type not one of accepted values: INTEGER in XdmfArrayType::New
> Aborted
>
>
> -Andy
>
> On Wed, Jul 12, 2017 at 1:31 PM, Jake Gerard <jake.a.gerard at gmail.com>
> wrote:
>
>> Alessandro,
>>
>> Paraview says that it failed to read the attribute data. I just mean that
>> when I connect Paraview to the machine, the pressure data does not load if
>> I select more than 1 node or process/node.
>>
>> Jake
>>
>> On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <demaio.a at gmail.com>
>> wrote:
>>
>>> Hi Jake,
>>>      when you talk about running in multi-processing are you talking
>>> about the solver that produces the data or about running Paraview in
>>> mpi-mode?
>>> Which is the error you get?
>>>
>>> Alessandro
>>>
>>> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>> wrote:
>>>
>>>> Any help here would be greatly appreciated.
>>>>
>>>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>>> wrote:
>>>>
>>>>> Good Afternoon,
>>>>>
>>>>> I have been moving to an HDF5/XDMF system for analyzing big data from
>>>>> a computational fluid model. I finally got all the basic components working
>>>>> on my local machine but have run into problems when trying to run on an HPC
>>>>> system. Here is the XDMF file:
>>>>>
>>>>> <?xml version="1.0" ?>
>>>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>>>   <Domain>
>>>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>>>       </Topology>
>>>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>           0 0 0
>>>>>         </DataItem>
>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>           1 1 1
>>>>>         </DataItem>
>>>>>       </Geometry>
>>>>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>>>>         <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>> Format="HDF">
>>>>>           out.h5:/pres_group/presmag
>>>>>         </DataItem>
>>>>>       </Attribute>
>>>>>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>>>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>>>> Dimensions="91 19 19 3">
>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>> Format="HDF">
>>>>>             out.h5:/velo_group/x_velo
>>>>>           </DataItem>
>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>> Format="HDF">
>>>>>             out.h5:/velo_group/y_velo
>>>>>           </DataItem>
>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>> Format="HDF">
>>>>>             out.h5:/velo_group/z_velo
>>>>>           </DataItem>
>>>>>         </DataItem>
>>>>>       </Attribute>
>>>>>     </Grid>
>>>>>   </Domain>
>>>>> </Xdmf>
>>>>>
>>>>> This has worked properly on my machine. However, when I was getting an
>>>>> error of failing to read the pressure data when I tried this on multiple
>>>>> processes. The vector data for velocity was fine, but the pressure data
>>>>> could not be read. I narrowed the problem down to something regarding the
>>>>> number of processes because the pressure data worked fine on the HPC
>>>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>>>> that could be causing this problem? For instance, is there a different
>>>>> format for these files when they are run on multiple processes?
>>>>>
>>>>> Respectfully,
>>>>>
>>>>> Jacob Gerard
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/d8fae9d8/attachment.html>

From agsmith424 at gmail.com  Wed Jul 12 16:16:20 2017
From: agsmith424 at gmail.com (Andy Smith)
Date: Wed, 12 Jul 2017 16:16:20 -0400
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAES0UenfBX_t7ggwebdOHiGQ_N4aZTbR+bAsQ0Ky6VMm56Cg8A@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
 <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
 <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>
 <CAES0UenfBX_t7ggwebdOHiGQ_N4aZTbR+bAsQ0Ky6VMm56Cg8A@mail.gmail.com>
Message-ID: <CA+yV-vA=b0OYpoErh-wAk85ao+yBH8rB-35cPbcRpaT77wfeFw@mail.gmail.com>

How many processors are you attempting to run on?
Is it possible to try a newer version of ParaView?  The oldest that I have
on my system is 4.4.0.

On Wed, Jul 12, 2017 at 3:33 PM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> Andy,
>
> I wasn't setting up the server or anything. I have just been connecting to
> one of my preset configurations. The velocity data shows up fine but for
> some reason when there is more than one processor working on the
> visualization Paraview can't read it.
>
> Here is the error:
>
> ERROR: In /p/home/angel/PV/4.3.1/Build_4.3.1_osmesa/paraview/src/
> paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1128
>
> vtkXdmfReader (0x104ae20): Failed to read attribute data
>
>
> The setup has just been clicking the connect icon, the system, and
> choosing the number of nodes and processors per node. If it helps I'm on
> Paraview 4.3.1 64-bit. Sorry I am pretty new to all of this stuff. Slowly
> getting the hang of things.
>
>
> Jake
>
> On Wed, Jul 12, 2017 at 1:48 PM, Andy Smith <agsmith424 at gmail.com> wrote:
>
>> Jake,
>>
>> If I start up the remote server in parallel using something like:
>> mpiexec.hydra -n 8 pvserver -sp=11111
>>
>> and then connect from my workstation I am able to read an XDMF file like
>> the one you posted using ParaView 5.4.0.  Can you post how you are starting
>> your server and the exact error that you receive?
>>
>> I've attached the .xmf file and a Python script to generate dummy data
>> in a .h5 file that corresponds to your data structure.
>>
>> Note that I am using the xdmf2 reader for my testing.  The xdmf3 reader
>> fails to read the file (even locally in serial) with the following error:
>>
>> Type not one of accepted values: INTEGER in XdmfArrayType::New
>> terminate called after throwing an instance of 'XdmfError'
>>   what():  Type not one of accepted values: INTEGER in XdmfArrayType::New
>> Aborted
>>
>>
>> -Andy
>>
>> On Wed, Jul 12, 2017 at 1:31 PM, Jake Gerard <jake.a.gerard at gmail.com>
>> wrote:
>>
>>> Alessandro,
>>>
>>> Paraview says that it failed to read the attribute data. I just mean
>>> that when I connect Paraview to the machine, the pressure data does not
>>> load if I select more than 1 node or process/node.
>>>
>>> Jake
>>>
>>> On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <demaio.a at gmail.com
>>> > wrote:
>>>
>>>> Hi Jake,
>>>>      when you talk about running in multi-processing are you talking
>>>> about the solver that produces the data or about running Paraview in
>>>> mpi-mode?
>>>> Which is the error you get?
>>>>
>>>> Alessandro
>>>>
>>>> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>>> wrote:
>>>>
>>>>> Any help here would be greatly appreciated.
>>>>>
>>>>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Good Afternoon,
>>>>>>
>>>>>> I have been moving to an HDF5/XDMF system for analyzing big data from
>>>>>> a computational fluid model. I finally got all the basic components working
>>>>>> on my local machine but have run into problems when trying to run on an HPC
>>>>>> system. Here is the XDMF file:
>>>>>>
>>>>>> <?xml version="1.0" ?>
>>>>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>>>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>>>>   <Domain>
>>>>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>>>>       </Topology>
>>>>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>           0 0 0
>>>>>>         </DataItem>
>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>           1 1 1
>>>>>>         </DataItem>
>>>>>>       </Geometry>
>>>>>>       <Attribute Name="pressure" AttributeType="Scalar" Center="Node">
>>>>>>         <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>> Format="HDF">
>>>>>>           out.h5:/pres_group/presmag
>>>>>>         </DataItem>
>>>>>>       </Attribute>
>>>>>>       <Attribute Name="velocity" AttributeType="Vector" Center="Node">
>>>>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>>>>> Dimensions="91 19 19 3">
>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>> Format="HDF">
>>>>>>             out.h5:/velo_group/x_velo
>>>>>>           </DataItem>
>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>> Format="HDF">
>>>>>>             out.h5:/velo_group/y_velo
>>>>>>           </DataItem>
>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>> Format="HDF">
>>>>>>             out.h5:/velo_group/z_velo
>>>>>>           </DataItem>
>>>>>>         </DataItem>
>>>>>>       </Attribute>
>>>>>>     </Grid>
>>>>>>   </Domain>
>>>>>> </Xdmf>
>>>>>>
>>>>>> This has worked properly on my machine. However, when I was getting
>>>>>> an error of failing to read the pressure data when I tried this on multiple
>>>>>> processes. The vector data for velocity was fine, but the pressure data
>>>>>> could not be read. I narrowed the problem down to something regarding the
>>>>>> number of processes because the pressure data worked fine on the HPC
>>>>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>>>>> that could be causing this problem? For instance, is there a different
>>>>>> format for these files when they are run on multiple processes?
>>>>>>
>>>>>> Respectfully,
>>>>>>
>>>>>> Jacob Gerard
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170712/4d846780/attachment.html>

From nabil.ghodbane at gmail.com  Thu Jul 13 08:54:11 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Thu, 13 Jul 2017 14:54:11 +0200
Subject: [Paraview] COMPILE AND RUN pvBatch with h5py support errors
Message-ID: <CAPd7EPrgS9rf8qKQTK+e5NozdA39Nnq_kNxtZP2wHzc+fbaoGw@mail.gmail.com>

dear experts,
on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
5.3.0-1 with dev tool 4 (which provides gcc 5.3 )

As shown on the attached screen captures, In the CCMAKE configuration, I
enabled Python with Matplot, Scipy, Numpy.

Once the compilation finished, I successfully added the h5py package
but if I start pvBatch or pvpython, i can see some error messages about the
hashlib module.


*ValueError: unsupported hash type sha384ERROR   : code for hash sha512 was
not found.*

This issue seems to be more a Python bug, than a Paraview issue. But maybe
someone on this mailing list did experience the issue. In case, I will be
grateful, if he or she could share his experience on how he/she solved this
issue.
thanks

Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/31bd4bce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture.PNG
Type: image/png
Size: 88328 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/31bd4bce/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture2.PNG
Type: image/png
Size: 73262 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/31bd4bce/attachment-0003.png>

From ben.boeckel at kitware.com  Thu Jul 13 09:06:13 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 13 Jul 2017 09:06:13 -0400
Subject: [Paraview] COMPILE AND RUN pvBatch with h5py support errors
In-Reply-To: <CAPd7EPrgS9rf8qKQTK+e5NozdA39Nnq_kNxtZP2wHzc+fbaoGw@mail.gmail.com>
References: <CAPd7EPrgS9rf8qKQTK+e5NozdA39Nnq_kNxtZP2wHzc+fbaoGw@mail.gmail.com>
Message-ID: <20170713130613.GA26914@megas.kitware.com>

On Thu, Jul 13, 2017 at 14:54:11 +0200, Nabil Ghodbane wrote:
> dear experts,
> on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
> 5.3.0-1 with dev tool 4 (which provides gcc 5.3 )
> 
> As shown on the attached screen captures, In the CCMAKE configuration, I
> enabled Python with Matplot, Scipy, Numpy.
> 
> Once the compilation finished, I successfully added the h5py package
> but if I start pvBatch or pvpython, i can see some error messages about the
> hashlib module.
> 
> 
> *ValueError: unsupported hash type sha384ERROR   : code for hash sha512 was
> not found.*
> 
> This issue seems to be more a Python bug, than a Paraview issue. But maybe
> someone on this mailing list did experience the issue. In case, I will be
> grateful, if he or she could share his experience on how he/she solved this
> issue.

I think this is usually an issue with openssl headers not being
available when compiling Python. Does installing openssl-devel and
forcing a rebuild of Python (cd $builddir; rm -rf superbuild/python) fix
the issue?

--Ben

From jake.a.gerard at gmail.com  Thu Jul 13 09:49:23 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Thu, 13 Jul 2017 08:49:23 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CA+yV-vA=b0OYpoErh-wAk85ao+yBH8rB-35cPbcRpaT77wfeFw@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
 <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
 <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>
 <CAES0UenfBX_t7ggwebdOHiGQ_N4aZTbR+bAsQ0Ky6VMm56Cg8A@mail.gmail.com>
 <CA+yV-vA=b0OYpoErh-wAk85ao+yBH8rB-35cPbcRpaT77wfeFw@mail.gmail.com>
Message-ID: <CAES0UekaTXv-_idXrDBesqtqVC3TfRK0KW4=quztGRXm_zR2zg@mail.gmail.com>

I will download a newer version and try again this morning.  Will let you
know how it goes.

On Wed, Jul 12, 2017 at 3:16 PM, Andy Smith <agsmith424 at gmail.com> wrote:

> How many processors are you attempting to run on?
> Is it possible to try a newer version of ParaView?  The oldest that I have
> on my system is 4.4.0.
>
> On Wed, Jul 12, 2017 at 3:33 PM, Jake Gerard <jake.a.gerard at gmail.com>
> wrote:
>
>> Andy,
>>
>> I wasn't setting up the server or anything. I have just been connecting
>> to one of my preset configurations. The velocity data shows up fine but for
>> some reason when there is more than one processor working on the
>> visualization Paraview can't read it.
>>
>> Here is the error:
>>
>> ERROR: In /p/home/angel/PV/4.3.1/Build_4.3.1_osmesa/paraview/src/parav
>> iew/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1128
>>
>> vtkXdmfReader (0x104ae20): Failed to read attribute data
>>
>>
>> The setup has just been clicking the connect icon, the system, and
>> choosing the number of nodes and processors per node. If it helps I'm on
>> Paraview 4.3.1 64-bit. Sorry I am pretty new to all of this stuff. Slowly
>> getting the hang of things.
>>
>>
>> Jake
>>
>> On Wed, Jul 12, 2017 at 1:48 PM, Andy Smith <agsmith424 at gmail.com> wrote:
>>
>>> Jake,
>>>
>>> If I start up the remote server in parallel using something like:
>>> mpiexec.hydra -n 8 pvserver -sp=11111
>>>
>>> and then connect from my workstation I am able to read an XDMF file like
>>> the one you posted using ParaView 5.4.0.  Can you post how you are starting
>>> your server and the exact error that you receive?
>>>
>>> I've attached the .xmf file and a Python script to generate dummy data
>>> in a .h5 file that corresponds to your data structure.
>>>
>>> Note that I am using the xdmf2 reader for my testing.  The xdmf3 reader
>>> fails to read the file (even locally in serial) with the following error:
>>>
>>> Type not one of accepted values: INTEGER in XdmfArrayType::New
>>> terminate called after throwing an instance of 'XdmfError'
>>>   what():  Type not one of accepted values: INTEGER in XdmfArrayType::New
>>> Aborted
>>>
>>>
>>> -Andy
>>>
>>> On Wed, Jul 12, 2017 at 1:31 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>> wrote:
>>>
>>>> Alessandro,
>>>>
>>>> Paraview says that it failed to read the attribute data. I just mean
>>>> that when I connect Paraview to the machine, the pressure data does not
>>>> load if I select more than 1 node or process/node.
>>>>
>>>> Jake
>>>>
>>>> On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <
>>>> demaio.a at gmail.com> wrote:
>>>>
>>>>> Hi Jake,
>>>>>      when you talk about running in multi-processing are you talking
>>>>> about the solver that produces the data or about running Paraview in
>>>>> mpi-mode?
>>>>> Which is the error you get?
>>>>>
>>>>> Alessandro
>>>>>
>>>>> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Any help here would be greatly appreciated.
>>>>>>
>>>>>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <jake.a.gerard at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Good Afternoon,
>>>>>>>
>>>>>>> I have been moving to an HDF5/XDMF system for analyzing big data
>>>>>>> from a computational fluid model. I finally got all the basic components
>>>>>>> working on my local machine but have run into problems when trying to run
>>>>>>> on an HPC system. Here is the XDMF file:
>>>>>>>
>>>>>>> <?xml version="1.0" ?>
>>>>>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>>>>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>>>>>   <Domain>
>>>>>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>>>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>>>>>       </Topology>
>>>>>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>>           0 0 0
>>>>>>>         </DataItem>
>>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>>           1 1 1
>>>>>>>         </DataItem>
>>>>>>>       </Geometry>
>>>>>>>       <Attribute Name="pressure" AttributeType="Scalar"
>>>>>>> Center="Node">
>>>>>>>         <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>> Format="HDF">
>>>>>>>           out.h5:/pres_group/presmag
>>>>>>>         </DataItem>
>>>>>>>       </Attribute>
>>>>>>>       <Attribute Name="velocity" AttributeType="Vector"
>>>>>>> Center="Node">
>>>>>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>>>>>> Dimensions="91 19 19 3">
>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>> Format="HDF">
>>>>>>>             out.h5:/velo_group/x_velo
>>>>>>>           </DataItem>
>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>> Format="HDF">
>>>>>>>             out.h5:/velo_group/y_velo
>>>>>>>           </DataItem>
>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>> Format="HDF">
>>>>>>>             out.h5:/velo_group/z_velo
>>>>>>>           </DataItem>
>>>>>>>         </DataItem>
>>>>>>>       </Attribute>
>>>>>>>     </Grid>
>>>>>>>   </Domain>
>>>>>>> </Xdmf>
>>>>>>>
>>>>>>> This has worked properly on my machine. However, when I was getting
>>>>>>> an error of failing to read the pressure data when I tried this on multiple
>>>>>>> processes. The vector data for velocity was fine, but the pressure data
>>>>>>> could not be read. I narrowed the problem down to something regarding the
>>>>>>> number of processes because the pressure data worked fine on the HPC
>>>>>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>>>>>> that could be causing this problem? For instance, is there a different
>>>>>>> format for these files when they are run on multiple processes?
>>>>>>>
>>>>>>> Respectfully,
>>>>>>>
>>>>>>> Jacob Gerard
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/c2082f04/attachment.html>

From wascott at sandia.gov  Thu Jul 13 13:04:26 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 13 Jul 2017 17:04:26 +0000
Subject: [Paraview] [EXTERNAL]  pvserver and mpi
In-Reply-To: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
References: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <eba56d75d6c54b47a84ad6830d569665@ES01AMSNLNT.srn.sandia.gov>

Ping?

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan
Sent: Wednesday, July 12, 2017 1:23 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] pvserver and mpi

I remember a thread from a few weeks ago that the current Linux distribution has built in MPI.  Is this correct?  Does this mean a user can use the Kitware binaries on a cluster, without rebuilding?

Thanks,

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/d78bfad9/attachment.html>

From ben.boeckel at kitware.com  Thu Jul 13 13:38:11 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 13 Jul 2017 13:38:11 -0400
Subject: [Paraview] pvserver and mpi
In-Reply-To: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
References: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <20170713173811.GA29572@megas.kitware.com>

On Wed, Jul 12, 2017 at 19:23:20 +0000, Scott, W Alan wrote:
> I remember a thread from a few weeks ago that the current Linux
> distribution has built in MPI.  Is this correct?  Does this mean a
> user can use the Kitware binaries on a cluster, without rebuilding?

Theoretically, yes? Though I'd expect most clusters to have their own,
better-tuned MPI builds you'd want to prefer to a stock mpich build.

--Ben

From jake.a.gerard at gmail.com  Thu Jul 13 14:15:39 2017
From: jake.a.gerard at gmail.com (Jake Gerard)
Date: Thu, 13 Jul 2017 13:15:39 -0500
Subject: [Paraview] Running Paraview on an HPC machine with multiple
	processes?
In-Reply-To: <CAES0UekaTXv-_idXrDBesqtqVC3TfRK0KW4=quztGRXm_zR2zg@mail.gmail.com>
References: <CAES0UekOE=xwwuijz58dDKQ6HVwfhH30YYXJOcLkwxdL8VnftA@mail.gmail.com>
 <CAES0Uen3xAZCasiRc89UxzFfhwEqM8SUgdyBYrpd_H9M33Up4Q@mail.gmail.com>
 <CAKQvD9S_jLuT9S9GJZoQEKr-w6Wx0VxoRGTgPbfkvvFy6tbedQ@mail.gmail.com>
 <CAES0Ue=5QR9bwMh9_kJRJEgxAvu4k676CfQfmWmtC4-Gp8Oj-A@mail.gmail.com>
 <CA+yV-vCqRMeOdOss9EaGLJ8sa0XhLCQokOFHH3A0W0heYDm7UA@mail.gmail.com>
 <CAES0UenfBX_t7ggwebdOHiGQ_N4aZTbR+bAsQ0Ky6VMm56Cg8A@mail.gmail.com>
 <CA+yV-vA=b0OYpoErh-wAk85ao+yBH8rB-35cPbcRpaT77wfeFw@mail.gmail.com>
 <CAES0UekaTXv-_idXrDBesqtqVC3TfRK0KW4=quztGRXm_zR2zg@mail.gmail.com>
Message-ID: <CAES0UenvjQT84iOHoWgzDY6080mZkwwRNH36S0StA5zToo1Tiw@mail.gmail.com>

I tried a newer version of Paraview (5.2.0) and still had the same problem.
Why would this be able to run on one process but not on multiple? The
velocity still shows up and can be split based on process id. Should I put
the scalar data into the xmf in a different format?

On Thu, Jul 13, 2017 at 8:49 AM, Jake Gerard <jake.a.gerard at gmail.com>
wrote:

> I will download a newer version and try again this morning.  Will let you
> know how it goes.
>
> On Wed, Jul 12, 2017 at 3:16 PM, Andy Smith <agsmith424 at gmail.com> wrote:
>
>> How many processors are you attempting to run on?
>> Is it possible to try a newer version of ParaView?  The oldest that I
>> have on my system is 4.4.0.
>>
>> On Wed, Jul 12, 2017 at 3:33 PM, Jake Gerard <jake.a.gerard at gmail.com>
>> wrote:
>>
>>> Andy,
>>>
>>> I wasn't setting up the server or anything. I have just been connecting
>>> to one of my preset configurations. The velocity data shows up fine but for
>>> some reason when there is more than one processor working on the
>>> visualization Paraview can't read it.
>>>
>>> Here is the error:
>>>
>>> ERROR: In /p/home/angel/PV/4.3.1/Build_4.3.1_osmesa/paraview/src/parav
>>> iew/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1128
>>>
>>> vtkXdmfReader (0x104ae20): Failed to read attribute data
>>>
>>>
>>> The setup has just been clicking the connect icon, the system, and
>>> choosing the number of nodes and processors per node. If it helps I'm on
>>> Paraview 4.3.1 64-bit. Sorry I am pretty new to all of this stuff. Slowly
>>> getting the hang of things.
>>>
>>>
>>> Jake
>>>
>>> On Wed, Jul 12, 2017 at 1:48 PM, Andy Smith <agsmith424 at gmail.com>
>>> wrote:
>>>
>>>> Jake,
>>>>
>>>> If I start up the remote server in parallel using something like:
>>>> mpiexec.hydra -n 8 pvserver -sp=11111
>>>>
>>>> and then connect from my workstation I am able to read an XDMF file
>>>> like the one you posted using ParaView 5.4.0.  Can you post how you are
>>>> starting your server and the exact error that you receive?
>>>>
>>>> I've attached the .xmf file and a Python script to generate dummy data
>>>> in a .h5 file that corresponds to your data structure.
>>>>
>>>> Note that I am using the xdmf2 reader for my testing.  The xdmf3 reader
>>>> fails to read the file (even locally in serial) with the following error:
>>>>
>>>> Type not one of accepted values: INTEGER in XdmfArrayType::New
>>>> terminate called after throwing an instance of 'XdmfError'
>>>>   what():  Type not one of accepted values: INTEGER in
>>>> XdmfArrayType::New
>>>> Aborted
>>>>
>>>>
>>>> -Andy
>>>>
>>>> On Wed, Jul 12, 2017 at 1:31 PM, Jake Gerard <jake.a.gerard at gmail.com>
>>>> wrote:
>>>>
>>>>> Alessandro,
>>>>>
>>>>> Paraview says that it failed to read the attribute data. I just mean
>>>>> that when I connect Paraview to the machine, the pressure data does not
>>>>> load if I select more than 1 node or process/node.
>>>>>
>>>>> Jake
>>>>>
>>>>> On Wed, Jul 12, 2017 at 11:00 AM, Alessandro De Maio <
>>>>> demaio.a at gmail.com> wrote:
>>>>>
>>>>>> Hi Jake,
>>>>>>      when you talk about running in multi-processing are you talking
>>>>>> about the solver that produces the data or about running Paraview in
>>>>>> mpi-mode?
>>>>>> Which is the error you get?
>>>>>>
>>>>>> Alessandro
>>>>>>
>>>>>> On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard <jake.a.gerard at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Any help here would be greatly appreciated.
>>>>>>>
>>>>>>> On Tue, Jul 11, 2017 at 2:37 PM, Jake Gerard <
>>>>>>> jake.a.gerard at gmail.com> wrote:
>>>>>>>
>>>>>>>> Good Afternoon,
>>>>>>>>
>>>>>>>> I have been moving to an HDF5/XDMF system for analyzing big data
>>>>>>>> from a computational fluid model. I finally got all the basic components
>>>>>>>> working on my local machine but have run into problems when trying to run
>>>>>>>> on an HPC system. Here is the XDMF file:
>>>>>>>>
>>>>>>>> <?xml version="1.0" ?>
>>>>>>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>>>>>>> <Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.1">
>>>>>>>>   <Domain>
>>>>>>>>     <Grid Name="my_Grid" GridType="Uniform">
>>>>>>>>       <Topology TopologyType="3DCoRectMesh" Dimensions="91 19 19">
>>>>>>>>       </Topology>
>>>>>>>>       <Geometry GeometryType="Origin_DxDyDz">
>>>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>>>           0 0 0
>>>>>>>>         </DataItem>
>>>>>>>>         <DataItem Dimensions="3" NumberType="Integer" Format="XML">
>>>>>>>>           1 1 1
>>>>>>>>         </DataItem>
>>>>>>>>       </Geometry>
>>>>>>>>       <Attribute Name="pressure" AttributeType="Scalar"
>>>>>>>> Center="Node">
>>>>>>>>         <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>>> Format="HDF">
>>>>>>>>           out.h5:/pres_group/presmag
>>>>>>>>         </DataItem>
>>>>>>>>       </Attribute>
>>>>>>>>       <Attribute Name="velocity" AttributeType="Vector"
>>>>>>>> Center="Node">
>>>>>>>>         <DataItem ItemType="Function" Function="JOIN($0, $1, $2)"
>>>>>>>> Dimensions="91 19 19 3">
>>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>>> Format="HDF">
>>>>>>>>             out.h5:/velo_group/x_velo
>>>>>>>>           </DataItem>
>>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>>> Format="HDF">
>>>>>>>>             out.h5:/velo_group/y_velo
>>>>>>>>           </DataItem>
>>>>>>>>           <DataItem Dimensions="91 19 19" NumberType="Float"
>>>>>>>> Format="HDF">
>>>>>>>>             out.h5:/velo_group/z_velo
>>>>>>>>           </DataItem>
>>>>>>>>         </DataItem>
>>>>>>>>       </Attribute>
>>>>>>>>     </Grid>
>>>>>>>>   </Domain>
>>>>>>>> </Xdmf>
>>>>>>>>
>>>>>>>> This has worked properly on my machine. However, when I was getting
>>>>>>>> an error of failing to read the pressure data when I tried this on multiple
>>>>>>>> processes. The vector data for velocity was fine, but the pressure data
>>>>>>>> could not be read. I narrowed the problem down to something regarding the
>>>>>>>> number of processes because the pressure data worked fine on the HPC
>>>>>>>> machine if I only ran it on 1 process. Is there anything that sticks out
>>>>>>>> that could be causing this problem? For instance, is there a different
>>>>>>>> format for these files when they are run on multiple processes?
>>>>>>>>
>>>>>>>> Respectfully,
>>>>>>>>
>>>>>>>> Jacob Gerard
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/d222fdec/attachment.html>

From martin.cuma at utah.edu  Thu Jul 13 16:38:08 2017
From: martin.cuma at utah.edu (Martin Cuma)
Date: Thu, 13 Jul 2017 14:38:08 -0600 (MDT)
Subject: [Paraview] Paraview segfaults on CentOS 7.2
Message-ID: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>

I have been having trouble running the release binary of Paraview on 
relatively stock CentOS 7.2 using
the OpenGL. It segfaults before it loads up the GUI window.. If I start 
Paraview with the --mesa option,
it works fine.

This happens with the 2.3 and 2.4 Paraview binaries, i.e. 
ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit and
ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit, as well as the latest build,
ParaView-5.4.0-233-g9952b9f-Qt5-MPI-Linux-64bit.

The same executables start fine both in CentOS6, and in an Ubuntu 16.10 
Singularity container that runs
on the CentOS7 host.

Before I dig further, I am wondering what is the experience on running 
Paraview on CentOS7.

Thanks,
-- 
Martin Cuma
Center for High Performance Computing
Department of Geology and Geophysics
University of Utah

From nabil.ghodbane at gmail.com  Thu Jul 13 16:40:20 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Thu, 13 Jul 2017 22:40:20 +0200
Subject: [Paraview] COMPILE AND RUN pvBatch with h5py support errors
In-Reply-To: <20170713130613.GA26914@megas.kitware.com>
References: <CAPd7EPrgS9rf8qKQTK+e5NozdA39Nnq_kNxtZP2wHzc+fbaoGw@mail.gmail.com>
 <20170713130613.GA26914@megas.kitware.com>
Message-ID: <CAPd7EPqiL40Z1+_G-kRu1LM=YWYwxsvG4W+YDmfm1itmvwOC_Q@mail.gmail.com>

many thanks for the suggestion. Unfortunately this did not help . Does
someone have some hint which could help?
thanks.

Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com


On Thu, Jul 13, 2017 at 3:06 PM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Thu, Jul 13, 2017 at 14:54:11 +0200, Nabil Ghodbane wrote:
> > dear experts,
> > on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
> > 5.3.0-1 with dev tool 4 (which provides gcc 5.3 )
> >
> > As shown on the attached screen captures, In the CCMAKE configuration, I
> > enabled Python with Matplot, Scipy, Numpy.
> >
> > Once the compilation finished, I successfully added the h5py package
> > but if I start pvBatch or pvpython, i can see some error messages about
> the
> > hashlib module.
> >
> >
> > *ValueError: unsupported hash type sha384ERROR   : code for hash sha512
> was
> > not found.*
> >
> > This issue seems to be more a Python bug, than a Paraview issue. But
> maybe
> > someone on this mailing list did experience the issue. In case, I will be
> > grateful, if he or she could share his experience on how he/she solved
> this
> > issue.
>
> I think this is usually an issue with openssl headers not being
> available when compiling Python. Does installing openssl-devel and
> forcing a rebuild of Python (cd $builddir; rm -rf superbuild/python) fix
> the issue?
>
> --Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170713/55e4939a/attachment.html>

From jcmendez at aggies.ncat.edu  Thu Jul 13 18:46:41 2017
From: jcmendez at aggies.ncat.edu (Julio Mendez)
Date: Thu, 13 Jul 2017 18:46:41 -0400
Subject: [Paraview] Problem visualizing the data in 5.4
Message-ID: <8C62AF5C-43CA-43EF-8018-110C1AA19BF1@aggies.ncat.edu>

Dear Community; 
 
I am trying to visualize my data, which is quite big. Nonetheless, I have enough RAM memory. By looking at the task manager I see that Paraview is using close to 20 GB of RAM, I have 60 GB Ram. 
In order to see the data I need to click the right button and move the mouse. When I release the mouse I only see the background. AS you can imagine I can do nothing since I cannot apply filters and so forth. 
Any suggestions? 

Thanks before Hand
Julio

From jgonzalez49 at ucmerced.edu  Fri Jul 14 01:15:38 2017
From: jgonzalez49 at ucmerced.edu (Jeremias Gonzalez)
Date: Thu, 13 Jul 2017 22:15:38 -0700
Subject: [Paraview] Using Value of Variable At Point in Calculator Filter
In-Reply-To: <CAB5Fpx6hvCvcq=UU3_6P3DJHdBa3rv7qOdqzDZRs+51CwG4P=Q@mail.gmail.com>
References: <8cb746b3-e456-a1eb-1194-038f51269a48@ucmerced.edu>
 <CAB5Fpx6hvCvcq=UU3_6P3DJHdBa3rv7qOdqzDZRs+51CwG4P=Q@mail.gmail.com>
Message-ID: <517b3143-1a7b-7b6d-4c81-70b4c12f1c9c@ucmerced.edu>

On 7/6/2017 12:38 PM, Cory Quammen wrote:
> I would look at using the Python scripting capabilities within
> ParaView for this. You can write a Python script and run it with
> pvpython - this is especially useful for running an analysis in a
> batch fashion. Within your script you use the Probe filter to get the
> data value at a particular location and add that value to some
> Calculator expression as needed. Here's a quick example:
>
> from paraview.simple import *
>
> data = FindSource('MyDataSource')
> probe = ProbeLocation(Input=data, ProbeType='Fixed Radius Point Source')
> probe.ProbeType.Center = [1.0, 0.0, 0.0]
> probe.UpdatePipeline()
> probePoint = paraview.servermanager.Fetch(probe)
> value_at_probe = probePoint.GetPointData().GetArray('my array name').GetValue(0)
>
> calculator_expression = #... value_at_probe + other expression
> c1 = Calculator(Input=appendedData)
> c1.Function = calculator_expression
> ...
>
>
> I hope that helps get you started. Let us know if you have other
> questions about the scripting.
Thank you very much for your help, that helped a lot! Some notes for 
anyone else finding this and needing some help: Using the Trace feature 
is extremely useful for getting the majority of a script written, and 
then the above code can be inserted. However, two changes had to be made 
in at least my case:

 1. probePoint.GetPointData().GetArray('my array name').GetValue(0) had
    to be changed to probePoint.GetPointData().GetVectors('my vector
    name').GetValue(0) as the data type being probed was a vector.
 2. When using value_at_probe in my calculator_expression variable, it
    couldn't just be dropped in. Since my expression was a string like
    calcexp='(gradient_x*2/value_at_probe)^(1/2)', it needed to be
    changed to calcexp='(gradient_x*2/{})^(1/2)'.format(value_at_probe)
    so that the numerical value was passed in as a string, and then
    passed to the calculator filter.


From lukas.kresta at gmail.com  Fri Jul 14 03:31:30 2017
From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=)
Date: Fri, 14 Jul 2017 09:31:30 +0200
Subject: [Paraview] Paraview Catalyst offscreen rendering
Message-ID: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>

Hi,

I would like to ask, which Paraview Catalyst (python) script use(with
render view or live visualization). If i want save images with offscreen
rendering on HPC.  On cluster is no gpu. And how to properly use it?

Thank you for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/c1bd0675/attachment.html>

From kriolog at gmail.com  Fri Jul 14 08:01:35 2017
From: kriolog at gmail.com (Maxim Torgonskiy)
Date: Fri, 14 Jul 2017 08:01:35 -0400
Subject: [Paraview] CTest and offscreen rendering
Message-ID: <CAHXhknvdDQYRD7KzhVk9Qg3SOKB7BR8a6xgi-jtT4a+NMZQj6g@mail.gmail.com>

Hello,

I am trying to run my paraview python regression tests with ctest on a
platform without X server. I've compiled paraview with osmesa and with
opengl (VTK_USE_X is ON; sounds strange but there is a reason for that :)
). When I run 'pvbatch --use-offscreen-rendering' my test passes. However,
ctest gives me the same error (bad X server connection. DISPLAY=) which I
have if I run pvbatch without use-offscreen-rendering. Is it possible to
forward this argument to the ctest command?

Regards,
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/29312b99/attachment.html>

From ben.boeckel at kitware.com  Fri Jul 14 10:01:56 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 14 Jul 2017 10:01:56 -0400
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
Message-ID: <20170714140156.GA25876@megas.kitware.com>

On Thu, Jul 13, 2017 at 14:38:08 -0600, Martin Cuma wrote:
> I have been having trouble running the release binary of Paraview on 
> relatively stock CentOS 7.2 using
> the OpenGL. It segfaults before it loads up the GUI window.. If I start 
> Paraview with the --mesa option,
> it works fine.
> 
> This happens with the 2.3 and 2.4 Paraview binaries, i.e. 
> ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit and
> ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit, as well as the latest build,
> ParaView-5.4.0-233-g9952b9f-Qt5-MPI-Linux-64bit.
> 
> The same executables start fine both in CentOS6, and in an Ubuntu 16.10 
> Singularity container that runs
> on the CentOS7 host.
> 
> Before I dig further, I am wondering what is the experience on running 
> Paraview on CentOS7.

The binaries are built in a CentOS 6 container, but CentOS 7 should
still work. Is there any other output? Can you get a backtrace from
running paraview under gdb?

--Ben

From andy.bauer at kitware.com  Fri Jul 14 10:24:20 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 14 Jul 2017 10:24:20 -0400
Subject: [Paraview] Paraview Catalyst offscreen rendering
In-Reply-To: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
References: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
Message-ID: <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>

Hi,

If you're not memory constrained I suggest just doing a full ParaView build
with OSMesa and X11 disabled. There are quite a few discussions on the PV
mailing list on how to do that.

If you're memory constrained then I would suggest building with all of the
Catalyst editions enabled and see if that works for you.

Best,
Andy

On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta <lukas.kresta at gmail.com>
wrote:

> Hi,
>
> I would like to ask, which Paraview Catalyst (python) script use(with
> render view or live visualization). If i want save images with offscreen
> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>
> Thank you for your help.
>
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/d0ffb469/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 14 10:25:44 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 14 Jul 2017 10:25:44 -0400
Subject: [Paraview] CTest and offscreen rendering
In-Reply-To: <CAHXhknvdDQYRD7KzhVk9Qg3SOKB7BR8a6xgi-jtT4a+NMZQj6g@mail.gmail.com>
References: <CAHXhknvdDQYRD7KzhVk9Qg3SOKB7BR8a6xgi-jtT4a+NMZQj6g@mail.gmail.com>
Message-ID: <CADHSJjD2g-aUSX1RVwMvSScO4Ta3-ctb5XTkvxcV3ta+fzT_Cw@mail.gmail.com>

Alas, there's no option to do that currently. It should be doable, but
would need some tweaking of the Cmake code. If you're interested, a good
starting point would be CMake/ParaViewTestingMacros.cmake.


On Fri, Jul 14, 2017 at 8:01 AM, Maxim Torgonskiy <kriolog at gmail.com> wrote:

> Hello,
>
> I am trying to run my paraview python regression tests with ctest on a
> platform without X server. I've compiled paraview with osmesa and with
> opengl (VTK_USE_X is ON; sounds strange but there is a reason for that :)
> ). When I run 'pvbatch --use-offscreen-rendering' my test passes.
> However, ctest gives me the same error (bad X server connection. DISPLAY=)
> which I have if I run pvbatch without use-offscreen-rendering. Is it
> possible to forward this argument to the ctest command?
>
> Regards,
> Maxim
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/e60b6c9d/attachment.html>

From cory.quammen at kitware.com  Fri Jul 14 10:43:51 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 14 Jul 2017 10:43:51 -0400
Subject: [Paraview] Problem visualizing the data in 5.4
In-Reply-To: <8C62AF5C-43CA-43EF-8018-110C1AA19BF1@aggies.ncat.edu>
References: <8C62AF5C-43CA-43EF-8018-110C1AA19BF1@aggies.ncat.edu>
Message-ID: <CAB5Fpx6zHje3NXU+PLqKOEKQogEumPVZykVtc47wOUEe===FBg@mail.gmail.com>

Julio,

If your data is large enough, perhaps you are running out of RAM on
your GPU. Do you get any error messages? Also, can you visualize
something simple like a Sphere source or Wavelet source?

Thanks,
Cory

On Thu, Jul 13, 2017 at 6:46 PM, Julio Mendez <jcmendez at aggies.ncat.edu> wrote:
> Dear Community;
>
> I am trying to visualize my data, which is quite big. Nonetheless, I have enough RAM memory. By looking at the task manager I see that Paraview is using close to 20 GB of RAM, I have 60 GB Ram.
> In order to see the data I need to click the right button and move the mouse. When I release the mouse I only see the background. AS you can imagine I can do nothing since I cannot apply filters and so forth.
> Any suggestions?
>
> Thanks before Hand
> Julio
> _______________________________________________
> 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&D Engineer
Kitware, Inc.

From kriolog at gmail.com  Fri Jul 14 11:09:31 2017
From: kriolog at gmail.com (Maxim Torgonskiy)
Date: Fri, 14 Jul 2017 11:09:31 -0400
Subject: [Paraview] CTest and offscreen rendering
In-Reply-To: <CADHSJjD2g-aUSX1RVwMvSScO4Ta3-ctb5XTkvxcV3ta+fzT_Cw@mail.gmail.com>
References: <CAHXhknvdDQYRD7KzhVk9Qg3SOKB7BR8a6xgi-jtT4a+NMZQj6g@mail.gmail.com>
 <CADHSJjD2g-aUSX1RVwMvSScO4Ta3-ctb5XTkvxcV3ta+fzT_Cw@mail.gmail.com>
Message-ID: <CAHXhknuxkaOgTk5w1gMGDkWxaCHYu_ei=R4mtRoH0mdV5n5FAQ@mail.gmail.com>

Thanks Utkarsh,

Ok, I'll just modify PARAVIEW_PVBATCH_ARGS in my test CMakeLists:

if(VTK_OPENGL_HAS_OSMESA AND PARAVIEW_BUILD_QT_GUI AND VTK_USE_X)
set(PARAVIEW_PVBATCH_ARGS --use-offscreen-rendering) endif()


2017-07-14 10:25 GMT-04:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Alas, there's no option to do that currently. It should be doable, but
> would need some tweaking of the Cmake code. If you're interested, a good
> starting point would be CMake/ParaViewTestingMacros.cmake.
>
>
> On Fri, Jul 14, 2017 at 8:01 AM, Maxim Torgonskiy <kriolog at gmail.com>
> wrote:
>
>> Hello,
>>
>> I am trying to run my paraview python regression tests with ctest on a
>> platform without X server. I've compiled paraview with osmesa and with
>> opengl (VTK_USE_X is ON; sounds strange but there is a reason for that :)
>> ). When I run 'pvbatch --use-offscreen-rendering' my test passes.
>> However, ctest gives me the same error (bad X server connection. DISPLAY=)
>> which I have if I run pvbatch without use-offscreen-rendering. Is it
>> possible to forward this argument to the ctest command?
>>
>> Regards,
>> Maxim
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/aaacaa58/attachment.html>

From martin.cuma at utah.edu  Fri Jul 14 14:11:38 2017
From: martin.cuma at utah.edu (Martin Cuma)
Date: Fri, 14 Jul 2017 12:11:38 -0600 (MDT)
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <20170714140156.GA25876@megas.kitware.com>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
Message-ID: <alpine.LRH.2.20.1707141210080.29075@marastik.chpc.utah.edu>

> The binaries are built in a CentOS 6 container, but CentOS 7 should
> still work. Is there any other output? Can you get a backtrace from
> running paraview under gdb?

Hi Ben, thanks for the reply.

I tried the backtrace but it does not show anything useful since there are 
no symbols in the binary. Do you have a binary build that includes symbols 
that I could download and try to run?

Thanks,
MC

From ben.boeckel at kitware.com  Fri Jul 14 14:52:13 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 14 Jul 2017 14:52:13 -0400
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <alpine.LRH.2.20.1707141210080.29075@marastik.chpc.utah.edu>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
 <alpine.LRH.2.20.1707141210080.29075@marastik.chpc.utah.edu>
Message-ID: <20170714185213.GA3085@megas.kitware.com>

On Fri, Jul 14, 2017 at 12:11:38 -0600, Martin Cuma wrote:
> I tried the backtrace but it does not show anything useful since there are 
> no symbols in the binary. Do you have a binary build that includes symbols 
> that I could download and try to run?

Not on hand, sorry. The backtrace might help a bit since it would at
least show the libraries involved in the traceback.

--ben

From martin.cuma at utah.edu  Fri Jul 14 14:57:18 2017
From: martin.cuma at utah.edu (Martin Cuma)
Date: Fri, 14 Jul 2017 18:57:18 +0000
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <20170714185213.GA3085@megas.kitware.com>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
 <alpine.LRH.2.20.1707141210080.29075@marastik.chpc.utah.edu>,
 <20170714185213.GA3085@megas.kitware.com>
Message-ID: <E7C7E78DB35B5F4D9409612D45B203FA9E5CF3A8@X-MB8.xds.umail.utah.edu>

OK, here's the gdb output:
$ gdb paraview
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
....
Reading symbols from /uufs/chpc.utah.edu/sys/installdir/paraview/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview...(no debugging symbols found)...done.
(gdb) r
Starting program: /uufs/chpc.utah.edu/sys/installdir/paraview/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview 
process 8756 is executing new program: /uufs/chpc.utah.edu/sys/installdir/paraview/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/paraview
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffc7dff700 (LWP 8911)]
Fontconfig warning: line 146: blank doesn't take any effect anymore. please remove it from your fonts.conf

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()

So, as you can see, not much of use. We did do a source build of 5.3 as well which also crashes (though I was not the one who did it), so, let me see if I can do something with that and get back to you.

Thanks,
MC

From nabil.ghodbane at gmail.com  Fri Jul 14 15:07:21 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Fri, 14 Jul 2017 21:07:21 +0200
Subject: [Paraview] COMPILE AND RUN pvBatch with h5py support errors
In-Reply-To: <CAPd7EPqiL40Z1+_G-kRu1LM=YWYwxsvG4W+YDmfm1itmvwOC_Q@mail.gmail.com>
References: <CAPd7EPrgS9rf8qKQTK+e5NozdA39Nnq_kNxtZP2wHzc+fbaoGw@mail.gmail.com>
 <20170713130613.GA26914@megas.kitware.com>
 <CAPd7EPqiL40Z1+_G-kRu1LM=YWYwxsvG4W+YDmfm1itmvwOC_Q@mail.gmail.com>
Message-ID: <CAPd7EPpfT0wd-Dc8w+ud1CZZmTP55PjNs7Kaaj_whp7a5RvtuA@mail.gmail.com>

hi,
in the end, I solved my issue by adding to LD_LIBRARY_PATH the missing
libraries which are needed by _hashlib.so located in python2.7/lib-dynload
hth.


Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com


On Thu, Jul 13, 2017 at 10:40 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
wrote:

> many thanks for the suggestion. Unfortunately this did not help . Does
> someone have some hint which could help?
> thanks.
>
> Nabil Ghodbane (Ph. D. Habil*.*)
> Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043>
> Mailto: nabil.ghodbane at gmail.com
>
>
> On Thu, Jul 13, 2017 at 3:06 PM, Ben Boeckel <ben.boeckel at kitware.com>
> wrote:
>
>> On Thu, Jul 13, 2017 at 14:54:11 +0200, Nabil Ghodbane wrote:
>> > dear experts,
>> > on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
>> > 5.3.0-1 with dev tool 4 (which provides gcc 5.3 )
>> >
>> > As shown on the attached screen captures, In the CCMAKE configuration, I
>> > enabled Python with Matplot, Scipy, Numpy.
>> >
>> > Once the compilation finished, I successfully added the h5py package
>> > but if I start pvBatch or pvpython, i can see some error messages about
>> the
>> > hashlib module.
>> >
>> >
>> > *ValueError: unsupported hash type sha384ERROR   : code for hash sha512
>> was
>> > not found.*
>> >
>> > This issue seems to be more a Python bug, than a Paraview issue. But
>> maybe
>> > someone on this mailing list did experience the issue. In case, I will
>> be
>> > grateful, if he or she could share his experience on how he/she solved
>> this
>> > issue.
>>
>> I think this is usually an issue with openssl headers not being
>> available when compiling Python. Does installing openssl-devel and
>> forcing a rebuild of Python (cd $builddir; rm -rf superbuild/python) fix
>> the issue?
>>
>> --Ben
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/c8ec24b2/attachment.html>

From ben.boeckel at kitware.com  Fri Jul 14 15:20:56 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 14 Jul 2017 15:20:56 -0400
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <E7C7E78DB35B5F4D9409612D45B203FA9E5CF3A8@X-MB8.xds.umail.utah.edu>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
 <alpine.LRH.2.20.1707141210080.29075@marastik.chpc.utah.edu>
 <20170714185213.GA3085@megas.kitware.com>
 <E7C7E78DB35B5F4D9409612D45B203FA9E5CF3A8@X-MB8.xds.umail.utah.edu>
Message-ID: <20170714192056.GA4194@megas.kitware.com>

On Fri, Jul 14, 2017 at 18:57:18 +0000, Martin Cuma wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()

Run `bt` (short for `backtrace`) to get a trace. Though if this frame is
`NULL`, I suspect something went really badly somewhere :/ .

> So, as you can see, not much of use. We did do a source build of 5.3
> as well which also crashes (though I was not the one who did it), so,
> let me see if I can do something with that and get back to you.

OK.

--Ben

From nabil.ghodbane at gmail.com  Fri Jul 14 15:31:36 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Fri, 14 Jul 2017 21:31:36 +0200
Subject: [Paraview] GetLookupTableForArray: LockScalarRange
Message-ID: <CAPd7EPoLe4eMcA_rtppuDkFHW9-e95tXk1AkC88MOe2X4xQSjw@mail.gmail.com>

dear experts,
I recently moved a software from PV 4.3 to PV 5.2.0 and the software I am
running uses  the GetLookupTableForArray LockScalarRange property
Was it simply removed ?
thanks.


pvpython
from paraview import *
>>> from paraview.simple import *
paraview version 5.2.0
>>> help(GetLookupTableForArray)
Help on function GetLookupTableForArray in module paraview.simple:

GetLookupTableForArray(arrayname, num_components, **params)
    Used to get an existing lookuptable for a array or to create one if none
    exists. Keyword arguments can be passed in to initialize the LUT if a
new
    one is created.
    *** DEPRECATED ***: Use GetColorTransferFunction instead




Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/479b09b9/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 14 15:54:09 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 14 Jul 2017 15:54:09 -0400
Subject: [Paraview] GetLookupTableForArray: LockScalarRange
In-Reply-To: <CAPd7EPoLe4eMcA_rtppuDkFHW9-e95tXk1AkC88MOe2X4xQSjw@mail.gmail.com>
References: <CAPd7EPoLe4eMcA_rtppuDkFHW9-e95tXk1AkC88MOe2X4xQSjw@mail.gmail.com>
Message-ID: <CADHSJjBqy1T08GY17X1uCVjaAzxFMKxnoZTHS+tLX9P7bL0muA@mail.gmail.com>

Nabil,

As the doc suggests, it's been replaced by `GetColorTransferFunction`.  The
params are quite comparable except that it does not  need the number of
components any more.

Utkarsh

On Fri, Jul 14, 2017 at 3:31 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
wrote:

> dear experts,
> I recently moved a software from PV 4.3 to PV 5.2.0 and the software I am
> running uses  the GetLookupTableForArray LockScalarRange property
> Was it simply removed ?
> thanks.
>
>
> pvpython
> from paraview import *
> >>> from paraview.simple import *
> paraview version 5.2.0
> >>> help(GetLookupTableForArray)
> Help on function GetLookupTableForArray in module paraview.simple:
>
> GetLookupTableForArray(arrayname, num_components, **params)
>     Used to get an existing lookuptable for a array or to create one if
> none
>     exists. Keyword arguments can be passed in to initialize the LUT if a
> new
>     one is created.
>     *** DEPRECATED ***: Use GetColorTransferFunction instead
>
>
>
>
> Nabil Ghodbane (Ph. D. Habil*.*)
> Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043>
> Mailto: nabil.ghodbane at gmail.com
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/55678c25/attachment.html>

From nabil.ghodbane at gmail.com  Fri Jul 14 15:55:56 2017
From: nabil.ghodbane at gmail.com (Nabil Ghodbane)
Date: Fri, 14 Jul 2017 21:55:56 +0200
Subject: [Paraview] GetLookupTableForArray: LockScalarRange
In-Reply-To: <CADHSJjBqy1T08GY17X1uCVjaAzxFMKxnoZTHS+tLX9P7bL0muA@mail.gmail.com>
References: <CAPd7EPoLe4eMcA_rtppuDkFHW9-e95tXk1AkC88MOe2X4xQSjw@mail.gmail.com>
 <CADHSJjBqy1T08GY17X1uCVjaAzxFMKxnoZTHS+tLX9P7bL0muA@mail.gmail.com>
Message-ID: <CAPd7EPrmvXuphW4BfYya1mnHX+5h-G-9vCE6=feQnvk1RG-ewg@mail.gmail.com>

thanks for the confirmation. I will ping the library developers then.


Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodbane at gmail.com


On Fri, Jul 14, 2017 at 9:54 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Nabil,
>
> As the doc suggests, it's been replaced by `GetColorTransferFunction`.
> The params are quite comparable except that it does not  need the number of
> components any more.
>
> Utkarsh
>
> On Fri, Jul 14, 2017 at 3:31 PM, Nabil Ghodbane <nabil.ghodbane at gmail.com>
> wrote:
>
>> dear experts,
>> I recently moved a software from PV 4.3 to PV 5.2.0 and the software I am
>> running uses  the GetLookupTableForArray LockScalarRange property
>> Was it simply removed ?
>> thanks.
>>
>>
>> pvpython
>> from paraview import *
>> >>> from paraview.simple import *
>> paraview version 5.2.0
>> >>> help(GetLookupTableForArray)
>> Help on function GetLookupTableForArray in module paraview.simple:
>>
>> GetLookupTableForArray(arrayname, num_components, **params)
>>     Used to get an existing lookuptable for a array or to create one if
>> none
>>     exists. Keyword arguments can be passed in to initialize the LUT if a
>> new
>>     one is created.
>>     *** DEPRECATED ***: Use GetColorTransferFunction instead
>>
>>
>>
>>
>> Nabil Ghodbane (Ph. D. Habil*.*)
>> Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043>
>> Mailto: nabil.ghodbane at gmail.com
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/72810654/attachment.html>

From wascott at sandia.gov  Fri Jul 14 21:07:50 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Sat, 15 Jul 2017 01:07:50 +0000
Subject: [Paraview] [EXTERNAL] Re:  pvserver and mpi
In-Reply-To: <20170713173811.GA29572@megas.kitware.com>
References: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
 <20170713173811.GA29572@megas.kitware.com>
Message-ID: <69eefb2d6efc44e78f426dd07a3a85a2@ES01AMSNLNT.srn.sandia.gov>

The more I think about this, I wonder if the answer is no?  After all, you would want the sbatch and srun to come from the same version of MPI that is linked into the application, would't you?


> -----Original Message-----
> From: Ben Boeckel [mailto:ben.boeckel at kitware.com]
> Sent: Thursday, July 13, 2017 11:38 AM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: paraview at paraview.org
> Subject: [EXTERNAL] Re: [Paraview] pvserver and mpi
> 
> On Wed, Jul 12, 2017 at 19:23:20 +0000, Scott, W Alan wrote:
> > I remember a thread from a few weeks ago that the current Linux
> > distribution has built in MPI.  Is this correct?  Does this mean a
> > user can use the Kitware binaries on a cluster, without rebuilding?
> 
> Theoretically, yes? Though I'd expect most clusters to have their own,
> better-tuned MPI builds you'd want to prefer to a stock mpich build.
> 
> --Ben

From utkarsh.ayachit at kitware.com  Fri Jul 14 21:13:55 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 14 Jul 2017 21:13:55 -0400
Subject: [Paraview] [EXTERNAL] Re: long animations are freezing halfway
	through
In-Reply-To: <CADHSJjAUD+=-jzY2g-UWTc_Y91EVqffztM3DDnz4EjpEsSpj7A@mail.gmail.com>
References: <CA+Y385yiZmpvOg_KUzdRzjwpuGka-xDqv1YZrkuEakv2CTLWbA@mail.gmail.com>
 <CADHSJjA2H=mfE48w05TXOSzKfs912gsz2CL7E=mvhOxPNyq5FA@mail.gmail.com>
 <575e4d66cec04221a06d846344dd5e6d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjA1=xKJvAE2ixxJ_UWgR-fmzrf_Fv3L5WLn3C-gFRs45w@mail.gmail.com>
 <CADHSJjBKvXkhD+BGi=ggGQti-dvoi_NzZ3LFDw20D5310HBTUg@mail.gmail.com>
 <CADLMsL63gxoCOh80Q+B4yQ18JmyZU51M5A4MN-ygr_e5vaNioA@mail.gmail.com>
 <CADHSJjAUD+=-jzY2g-UWTc_Y91EVqffztM3DDnz4EjpEsSpj7A@mail.gmail.com>
Message-ID: <CADHSJjDcjH=__-yTiBeWVEj6CToe-WtE7OtZP6meymxuZAfZ+w@mail.gmail.com>

Giles et al.

We finally have fix for this. Together with Ben, we tracked it down to
being a MTime wrap-around issue. It's fixed here:
https://gitlab.kitware.com/paraview/paraview/merge_requests/1777

It will be included in upcoming 5.4.1.

Thanks for your help with reproducing this bug.

Utkarsh

On Tue, Jul 11, 2017 at 10:42 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> So far, all indicators point to a driver bug. To confirm, is everyone
> reporting this issue encountering it on NVIDIA GPUs with Windows?
>
> Utkarsh
>
> On Thu, Jul 6, 2017 at 8:35 PM, stephane???? ?? <stephane at fujielectric.com
> > wrote:
>
>> Hello,
>>
>> I just want to  add that it's happening in both 5.3 and 5.4
>>
>> Ndong-Mefane Stephane, Dr.Eng
>> Basic Design Sec.
>> Steam Turbine Dept.
>> Kawasaki Factory
>>
>> Fuji Electric Co., Ltd
>> 1-1, Tanabeshinden, Kawasaki-ku,
>> Kawasaki-city 210-9530, Japan
>> Phone: +81-44-329-2155 <+81%2044-329-2155>
>> Fax: +81-44-329-2394 <+81%2044-329-2394>
>>
>>
>> On Thu, Jul 6, 2017 at 11:14 PM, Utkarsh Ayachit <
>> utkarsh.ayachit at kitware.com> wrote:
>>
>>> Just to give an update, while I couldn't reproduce the issue with Giles
>>> example, I was able to do it with another customer. It's quite a curious
>>> thing indeed! Still figuring out where to begin to debug this -- the fact
>>> that it's a Windows only thing makes it even more tedious -- but will keep
>>> you posted.
>>>
>>> Utkarsh
>>>
>>> On Fri, Jun 23, 2017 at 12:08 PM, Utkarsh Ayachit <
>>> utkarsh.ayachit at kitware.com> wrote:
>>>
>>>> Alan,
>>>>
>>>> I am discussing with Giles off line. Will keep you posted.
>>>>
>>>> Utkarsh
>>>>
>>>> On Fri, Jun 23, 2017 at 12:05 PM, Scott, W Alan <wascott at sandia.gov>
>>>> wrote:
>>>> > I have another user with this complaint.  I have not been able to
>>>> replicate it.
>>>> >
>>>> > Are you using either opacity or volume rendering?
>>>> >
>>>> > Would you be able to pass the data files to Kitware?
>>>> >
>>>> > Alan
>>>> >
>>>> >> -----Original Message-----
>>>> >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
>>>> >> Utkarsh Ayachit
>>>> >> Sent: Friday, June 23, 2017 7:07 AM
>>>> >> To: Richardson CFD <garcfd at gmail.com>
>>>> >> Cc: ParaView <paraview at paraview.org>
>>>> >> Subject: [EXTERNAL] Re: [Paraview] long animations are freezing
>>>> halfway
>>>> >> through
>>>> >>
>>>> >> Giles,
>>>> >>
>>>> >> What OS is this on?
>>>> >>
>>>> >> Utkarsh
>>>> >>
>>>> >> On Fri, Jun 23, 2017 at 8:59 AM, Richardson CFD <garcfd at gmail.com>
>>>> wrote:
>>>> >> > I have been having trouble creating longer animations (150 frames)
>>>> >> > from larger data files (1million cells). The animation works fine
>>>> >> > initially but then freezes up about half way through the avi file -
>>>> >> > displaying just a constant unchanging image. Streamlines seems to
>>>> work
>>>> >> > fine, but velocity contours (attached) is the one causing
>>>> problems. I
>>>> >> > am having to create the animation in 2 parts, creating 2 seperate
>>>> avi
>>>> >> > file and then join them after.
>>>> >> >
>>>> >> > Any suggestions or similar experience please let me know. Regards
>>>> Giles.
>>>> >> >
>>>> >> > --
>>>> >> > Richardson CFD
>>>> >> > http://richardsoncfd.weebly.com
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170714/aaf17da0/attachment.html>

From cory.quammen at kitware.com  Sat Jul 15 11:19:23 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sat, 15 Jul 2017 11:19:23 -0400
Subject: [Paraview] [EXTERNAL] Re: pvserver and mpi
In-Reply-To: <69eefb2d6efc44e78f426dd07a3a85a2@ES01AMSNLNT.srn.sandia.gov>
References: <d2098d5439ac4693aaddde7ec1f6c880@ES01AMSNLNT.srn.sandia.gov>
 <20170713173811.GA29572@megas.kitware.com>
 <69eefb2d6efc44e78f426dd07a3a85a2@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CAB5Fpx4MmQJf6NjogtjiocNBp9oASUMZPYE_MztRdFNPJJrZDA@mail.gmail.com>

On Fri, Jul 14, 2017 at 9:07 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> The more I think about this, I wonder if the answer is no?  After all, you would want the sbatch and srun to come from the same version of MPI that is linked into the application, would't you?

I am assuming the sbin and srun you mention come from Slurm. This
documentation [1] for MPICH2 with Slurm suggests that you really
should build it against your Slurm installation. Towards the end,
however, it includes an example that *may* work for launching the
current ParaView linux binaries with Slurm using:

salloc -N 2 mpiexec my_application

It could looks like it would be fast to try out if you want to give it
a shot. Just sub out "my_application" with "pvserver".

Cory

[1] https://slurm.schedmd.com/mpi_guide.html#mpich2

>
>
>> -----Original Message-----
>> From: Ben Boeckel [mailto:ben.boeckel at kitware.com]
>> Sent: Thursday, July 13, 2017 11:38 AM
>> To: Scott, W Alan <wascott at sandia.gov>
>> Cc: paraview at paraview.org
>> Subject: [EXTERNAL] Re: [Paraview] pvserver and mpi
>>
>> On Wed, Jul 12, 2017 at 19:23:20 +0000, Scott, W Alan wrote:
>> > I remember a thread from a few weeks ago that the current Linux
>> > distribution has built in MPI.  Is this correct?  Does this mean a
>> > user can use the Kitware binaries on a cluster, without rebuilding?
>>
>> Theoretically, yes? Though I'd expect most clusters to have their own,
>> better-tuned MPI builds you'd want to prefer to a stock mpich build.
>>
>> --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&D Engineer
Kitware, Inc.

From mbahameish at gmail.com  Sat Jul 15 17:18:18 2017
From: mbahameish at gmail.com (Mariam)
Date: Sat, 15 Jul 2017 22:18:18 +0100
Subject: [Paraview] ParaViewWeb Error - vtkweb-loader.js
In-Reply-To: <A7FB3A43-9BAC-4BDF-A2B0-9B5A87E59E58@gmail.com>
References: <C2E3BCEF-5189-4C45-BB27-81BE9D7CC8FD@gmail.com>
 <CABObKxe+wp-LYcLm4ptb7tAQo2WFo3GKnyYyxQJ9XVtWSu3CQQ@mail.gmail.com>
 <A7FB3A43-9BAC-4BDF-A2B0-9B5A87E59E58@gmail.com>
Message-ID: <5B910C9B-962B-4846-849A-476DCBDB0D2C@gmail.com>

Any idea on how to resolve the issue?

Thanks,

 

From: Mariam Bahameish <mbahameish at gmail.com>
Date: Tuesday, July 4, 2017 at 11:04 AM
To: Sebastien Jourdain <sebastien.jourdain at kitware.com>
Cc: "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [Paraview] ParaViewWeb Error - vtkweb-loader.js

 

I have installed the binary installation from the download page.


Sent from my iPhone


On Jul 4, 2017, at 10:48 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:

This is strange, it seems that you have the Web code of ParaView 4.

 

How did you get/build ParaView? Are you sure it is ParaView 5.2?

 

On Thu, Jun 29, 2017 at 4:31 AM, Mariam <mbahameish at gmail.com> wrote:

Hi,

I am trying to run ParaViewWeb using the following command:

./pvpython -dr ../Resources/web/visualizer/server/pvw-visualizer.py --content ../Resources/web/visualizer/www

 

The connection is established, however, when accessing http://localhost:8080, I receive the following error in the browser (checked from Chrome Developer Tools):

vtkweb-loader.js Failed to load resource: the server responded with a status of 404 (Not Found)

localhost/:15 Uncaught ReferenceError: vtkWeb is not defined at localhost/:15

 

>From the command line, I receive the following:

[HTTPChannel,0,127.0.0.1] "127.0.0.1" - - [29/Jun/2017:10:23:14 +0000] "GET /lib/core/vtkweb-loader.js HTTP/1.1" 404 145 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36"

 

ParaView version: 5.2

OS: Mac

 

I tried to look for /lib/core/vtkweb-loader.js, but this location doesn?t exist in the current version. It seems to be existed in older versions such as 5.1, so I tried to install 5.1 as well but I got the same error.

 

Any idea on how to resolve the issue? 

 

Thanks,


_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170715/cc69d795/attachment.html>

From mbahameish at gmail.com  Sat Jul 15 17:20:06 2017
From: mbahameish at gmail.com (Mariam)
Date: Sat, 15 Jul 2017 22:20:06 +0100
Subject: [Paraview] [Camera Control] - Clipping Range
In-Reply-To: <CANjZAi9xSpCwYbHMoHM12w=hqtetmGOanM1MQvQZKUtQ9FwPng@mail.gmail.com>
References: <8E720A6F-84A1-4646-8D77-2F3B1964DF77@gmail.com>
 <CADHSJjAYTzn+Bk+Zov+mdNsFVyKj=KV7RAY8CAcRbBJTj1yfpg@mail.gmail.com>
 <CANjZAi9xSpCwYbHMoHM12w=hqtetmGOanM1MQvQZKUtQ9FwPng@mail.gmail.com>
Message-ID: <51A01D09-A6F5-49C3-8639-21D352B56596@gmail.com>

Thanks for your replies.

 

From: David E DeMarle <dave.demarle at kitware.com>
Date: Friday, July 7, 2017 at 7:57 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: Mariam <mbahameish at gmail.com>, ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Camera Control] - Clipping Range

 

Try LockBounds.

 

For example:

view = GetActiveView()

view.MaxClipBounds = [x0,x1,y0,y1,z0,z1]

view.LockBounds = 1


David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

 

On Fri, Jul 7, 2017 at 2:51 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:

Currently, you can't. ParaView doesn't let user change ClippingRange. It resets it internally before each render.

 

On Fri, Jul 7, 2017 at 2:44 PM, Mariam <mbahameish at gmail.com> wrote:

Hi,

I am trying to control the camera attributes from pvpython, I noticed that if I modified Clipping Range & Thickness then called Render() the values are reset to the original values. However, changes in camera position, focal point, view up and viewing angle take effect after Render().

 

Here is a snippet of the code:

from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

sphere = Sphere()
Show()
Render()

camera = GetActiveCamera()
camera.GetFocalPoint()
(0.0, 0.0, 0.0)

camera.GetPosition()
(0.0, 0.0, 6.69)

camera.GetClippingRange()
(5.628100000000001, 8.042850000000001)

camera.SetPosition(0,0,3)
Render()


camera.GetPosition()
(0.0, 0.0, 3.0)


camera.GetClippingRange()
(1.975, 4.2975)

camera.SetClippingRange(3,8)
camera.GetClippingRange()
(3.0, 8.0)

Render()

camera.GetClippingRange()
(1.975, 4.2975)

 

 

How can I force changes on Clipping Range & Thickness values?

 

Regards,

 

_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170715/a41e63c0/attachment.html>

From Amine.Aboufirass at deltares.nl  Mon Jul 17 07:31:17 2017
From: Amine.Aboufirass at deltares.nl (Amine Aboufirass)
Date: Mon, 17 Jul 2017 11:31:17 +0000
Subject: [Paraview] LegacyVTKReader command
Message-ID: <DEA101B66315B941B487EAE03CFFF44346437A99@V-EXC-C02.DIRECTORY.INTRA>

I am trying to use the LegacyVTKReader command in paraview.simple to create pipelines for vtk timeseries. The following command:

TEST_FEM_MeshData = LegacyVTKReader(FileNames = MeshDataList)

Works well but does results in pipelines with generic names like "LegacyVTKReader1" and "LegacyVTKReader2". How do I get this command to allow me to control the resulting pipeline name? I want the name to be "TEST_FEM_MeshData" for example.

Regards,

Amine


DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/2395e896/attachment.html>

From chuck.atkins at kitware.com  Mon Jul 17 09:22:21 2017
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Mon, 17 Jul 2017 09:22:21 -0400
Subject: [Paraview] how to build the paraview superbuild with mesa on a
 cluster (where user is not a root user)
In-Reply-To: <CAB5Fpx42BSZb5TXLQzJKDf4qHAFep3MTGB2NGo3k6bXE_wLK0g@mail.gmail.com>
References: <CACrYMsJUOXp5fzTd48ktUcug6qWMK6NYu7qwWJFSt2b2q5pVAg@mail.gmail.com>
 <CAB5Fpx7kHBmi_XrWDC9pdEHcjgW_gAoykjLbHoRU16qYvCz=OQ@mail.gmail.com>
 <CACrYMsKSPSPudq0CmN6_A339xvfOnasdaNs1m_mQH3-AOFmU1A@mail.gmail.com>
 <CACrYMs+_8H4QGCc9gFkO5XHbYWf0i5kao53Prz=V70asueToDA@mail.gmail.com>
 <052c8ff1-c0e1-88b7-e11c-84631c1f5e23@legi.grenoble-inp.fr>
 <CACrYMsLiv7rAzzf+NO=Z3KojOUaJUT08_tknE6bGB2Hb5E=K6w@mail.gmail.com>
 <CACrYMsJ8VCUghm58-Sv0SO0iu-opn5nmU8vRvsFyY-xOyK4UBA@mail.gmail.com>
 <CACrYMsKtHZQmJkSKU0p8ZK-9n0oogLruQ3Y3+T6b0BvVhy8ZOA@mail.gmail.com>
 <CAB5Fpx5nueW1mznb=ftvmuARSnkpwXcrN9RaLnCy4BzWqeNg8w@mail.gmail.com>
 <CACrYMsK6zc1mwZ1B4x13mKAXeJgKDOuj6rSKSZGxKokd7Xk57A@mail.gmail.com>
 <CAB5Fpx42BSZb5TXLQzJKDf4qHAFep3MTGB2NGo3k6bXE_wLK0g@mail.gmail.com>
Message-ID: <CAOXZzG5cZ2K2v4bagsu7-3jCwyn7LGriophc+g=xrRJL9tCSUA@mail.gmail.com>

Hi Mathi,

The default build environment on Cray systems is to only build static
libraries.  Try setting the environment variable CRAYPE_LINK_TYPE=dynamic
and then starting from a clean build directory.  A word of caution when
using Anaconda python, be sure to remove anaconda's MPI package; it
conflicts with the cray-mpich module, which is what you need to use, since
they're both MPICH variants and end up getting mixed up by the runtime
linker and cause segfaults.  If you have the latest Cray programming
environment installed, a better Python option would be to use the newly
released cray-python module instead of anaconda.

- Chuck


On Sun, Jul 9, 2017 at 6:56 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Mathi,
>
> Chuck Atkins is the guru when it comes to compiling ParaView on Cray
> systems (along with many other systems). He may have some more helpful
> tips to get you building on your system.
>
> Best,
> Cory
>
> On Sat, Jul 8, 2017 at 12:26 PM, Ezhilmathi Krishnasamy
> <ezhkr601 at student.liu.se> wrote:
> > Hi Cory,
> >
> > Could you please give me  some more information.
> > It will not build if I turn it OFF.
> >
> > Kind regards,
> > Mathi
> >
> > On 6 July 2017 at 20:51, Cory Quammen <cory.quammen at kitware.com> wrote:
> >>
> >> Set the BUILD_SHARED_LIBS option to OFF.
> >>
> >> HTH,
> >> Cory
> >>
> >> On Sun, Jul 2, 2017 at 11:56 AM, Ezhilmathi Krishnasamy
> >> <ezhkr601 at student.liu.se> wrote:
> >> > Hi,
> >> >
> >> > I am still having some problem with enabling the
> >> > build shared libs. I am trying to install it on a Cray machine.
> >> > I have already locally installed cmake and anaconda on their latest
> >> > version.
> >> >
> >> > I am attaching here the image.
> >> > Could any one tell me how to fix this issue
> >> >
> >> > Kind regards,
> >> > Mathi
> >> >
> >> > On 2 July 2017 at 14:54, Ezhilmathi Krishnasamy
> >> > <ezhkr601 at student.liu.se>
> >> > wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I have almost build it, but getting this error:
> >> >>
> >> >>  CMake Warning (dev) at
> >> >> /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:115
> >> >> (add_library):
> >> >>    ADD_LIBRARY called with SHARED option but the target platform does
> >> >> not
> >> >>    support dynamic linking.  Building a STATIC library instead.  This
> >> >> may
> >> >> lead
> >> >>    to problems.
> >> >>  Call Stack (most recent call first):
> >> >>    /pdc/vol/anaconda/4.3/py36/lib/cmake/Qt5/Qt5Config.cmake:26
> >> >> (find_package)
> >> >>    superbuild/projects/qt5.system.cmake:1 (find_package)
> >> >>    superbuild/cmake/SuperbuildMacros.cmake:640 (include)
> >> >>    superbuild/CMakeLists.txt:115 (superbuild_process_dependencies)
> >> >>  This warning is for project developers.  Use -Wno-dev to suppress
> it.
> >> >>
> >> >>
> >> >>
> >> >> On 2 July 2017 at 14:17, Ezhilmathi Krishnasamy
> >> >> <ezhkr601 at student.liu.se>
> >> >> wrote:
> >> >>>
> >> >>> Thanks!
> >> >>>
> >> >>> Now it shows this kind of error
> >> >>>
> >> >>>
> >> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
> w-superbuild>
> >> >>> git fetch origin
> >> >>>
> >> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
> w-superbuild>
> >> >>> git checkout v5.4.0
> >> >>> HEAD is now at 7c510fe... Update to 5.4.0
> >> >>>
> >> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
> w-superbuild>
> >> >>> git submodule update
> >> >>>
> >> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
> w-superbuild>
> >> >>> cd ..
> >> >>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD> cd ..
> >> >>> /cfs/klemming/nobackup/k/kriezh> cd build/
> >> >>> /cfs/klemming/nobackup/k/kriezh/build> ccmake
> >> >>> ../PARAVIEW_SUPER_BUILD/paraview-superbuild/
> >> >>>
> >> >>>
> >> >>>  CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289
> (message):
> >> >>>    The build tree appears to be inside of the git repository located
> >> >>> at
> >> >>>    /cfs/klemming/nobackup/k/kriezh.  This interferes with the way
> the
> >> >>>    superbuild applies patches to projects and is not supported.
> >> >>> Please
> >> >>>    relocate the build tree to a directory which is not under a git
> >> >>> repository.
> >> >>>  Call Stack (most recent call first):
> >> >>>    superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
> >> >>>    superbuild/cmake/SuperbuildMacros.cmake:477 (include)
> >> >>>    superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On 2 July 2017 at 14:03, Patrick B?gou
> >> >>> <Patrick.Begou at legi.grenoble-inp.fr> wrote:
> >> >>>>
> >> >>>> Like you, I got this error some months ago when trying to build
> >> >>>> paraview
> >> >>>> superbuild:
> >> >>>>
> >> >>>> error: unknown option `is-ancestor'
> >> >>>>
> >> >>>> It was my git version wich was too old. May be try to compile a
> more
> >> >>>> up
> >> >>>> to date version of git in your home and set the path to access it.
> >> >>>>
> >> >>>> I have installed git from
> >> >>>> https://www.kernel.org/pub/software/scm/git/git-2.12.2.tar.xz
> >> >>>>
> >> >>>> Patrick
> >> >>>>
> >> >>>> Ezhilmathi Krishnasamy a ?crit :
> >> >>>>
> >> >>>> Hi,
> >> >>>>
> >> >>>> I have followed these instructions. I am trying to install it
> where I
> >> >>>> am
> >> >>>> not a root user.
> >> >>>> Can someone help to fix this issue.
> >> >>>>
> >> >>>>  git clone --recursive
> >> >>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
> >> >>>>  cd paraview-superbuild
> >> >>>>  git fetch origin # ensure you have the latest state from the main
> >> >>>> repo
> >> >>>>  git checkout v5.2.0 # replace `v5.2.0` with tag name of your
> choice
> >> >>>>  git submodule update
> >> >>>>
> >> >>>>  cd ..
> >> >>>>  mkdir build
> >> >>>>  cd build
> >> >>>>  ccmake ../paraview-superbuild
> >> >>>>
> >> >>>> Kind regards,
> >> >>>> Mathi
> >> >>>>
> >> >>>>
> >> >>>> On 30 June 2017 at 18:54, Ezhilmathi Krishnasamy
> >> >>>> <ezhkr601 at student.liu.se> wrote:
> >> >>>>>
> >> >>>>> Hi Thanks!
> >> >>>>>
> >> >>>>> When I try to install Paraview,  I am getting the following error.
> >> >>>>> Could some one please tell me how to fix this issue.
> >> >>>>> I am trying to install the Paraview on a super computer to use it
> >> >>>>> for remote rendering without using the GUI,  like with mesa
> support.
> >> >>>>>
> >> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD>
> >> >>>>> git
> >> >>>>> clone --recursive
> >> >>>>> https://gitlab.kitware.com/paraview/paraview-superbuild.git
> >> >>>>> Cloning into 'paraview-superbuild'...
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> remote: Counting objects: 6723, done.
> >> >>>>> remote: Compressing objects: 100% (2459/2459), done.
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> remote: Total 6723 (delta 4451), reused 6342 (delta 4201)
> >> >>>>> Receiving objects: 100% (6723/6723), 2.05 MiB | 741 KiB/s, done.
> >> >>>>> Resolving deltas: 100% (4451/4451), done.
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> Checking out files: 100% (196/196), done.
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> Submodule 'superbuild'
> >> >>>>> (https://gitlab.kitware.com/paraview/common-superbuild.git)
> >> >>>>> registered for
> >> >>>>> path 'superbuild'
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> Cloning into 'superbuild'...
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> remote: Counting objects: 6752, done.
> >> >>>>> remote: Compressing objects: 100% (2235/2235), done.
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> remote: Total 6752 (delta 4505), reused 6574 (delta 4395)
> >> >>>>> Receiving objects: 100% (6752/6752), 1.59 MiB | 592 KiB/s, done.
> >> >>>>> Resolving deltas: 100% (4505/4505), done.
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> Submodule path 'superbuild': checked out
> >> >>>>> '8f357bb5bf35419c210b3f9e0adbc9df08f565f2'
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>> warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission denied
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> kriezh at beskow-login2:/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_
> BUILD/paraview-superbuild>
> >> >>>>> cmake .
> >> >>>>> -- The C compiler identification is Intel 14.0.4.20140805
> >> >>>>> -- The CXX compiler identification is Intel 14.0.4.20140805
> >> >>>>> -- Cray Programming Environment 2.2.1 C
> >> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc
> >> >>>>> -- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc --
> >> >>>>> works
> >> >>>>> -- Detecting C compiler ABI info
> >> >>>>> -- Detecting C compiler ABI info - done
> >> >>>>> -- Detecting C compile features
> >> >>>>> -- Detecting C compile features - done
> >> >>>>> -- Cray Programming Environment 2.2.1 CXX
> >> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
> >> >>>>> -- Check for working CXX compiler: /opt/cray/craype/2.2.1/bin/CC
> --
> >> >>>>> works
> >> >>>>> -- Detecting CXX compiler ABI info
> >> >>>>> -- Detecting CXX compiler ABI info - done
> >> >>>>> -- Detecting CXX compile features
> >> >>>>> -- Detecting CXX compile features - done
> >> >>>>> CMake Warning at superbuild/cmake/SuperbuildUtils.cmake:242
> >> >>>>> (message):
> >> >>>>>   Failed to determine if the common superbuild is an old checkout.
> >> >>>>> The
> >> >>>>>   common superbuild may be out of date, but cannot be verified.:
> >> >>>>> warning:
> >> >>>>>   unable to access '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>> Permission
> >> >>>>>   denied
> >> >>>>>
> >> >>>>>   warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>>   Permission denied
> >> >>>>>
> >> >>>>>   warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>>   Permission denied
> >> >>>>>
> >> >>>>>   warning: unable to access
> >> >>>>> '/afs/pdc.kth.se/home/k/kriezh/.gitconfig':
> >> >>>>>   Permission denied
> >> >>>>>
> >> >>>>>   error: unknown option `is-ancestor'
> >> >>>>>
> >> >>>>>   usage: git merge-base [-a|--all] <commit> <commit>...
> >> >>>>>
> >> >>>>>      or: git merge-base [-a|--all] --octopus <commit>...
> >> >>>>>      or: git merge-base --independent <commit>...
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>       -a, --all             output all common ancestors
> >> >>>>>       --octopus             find ancestors for a single n-way
> merge
> >> >>>>>       --independent         list revs not reachable from others
> >> >>>>> Call Stack (most recent call first):
> >> >>>>>   superbuild/CMakeLists.txt:28 (_superbuild_check_up_to_date)
> >> >>>>>
> >> >>>>>
> >> >>>>> -- Check size of void*
> >> >>>>> -- Check size of void* - done
> >> >>>>> -- Found Git: /usr/bin/git (found version "1.7.12.4")
> >> >>>>> -- Determined source version for paraview: 5.4.0
> >> >>>>> CMake Error at superbuild/cmake/SuperbuildMacros.cmake:289
> >> >>>>> (message):
> >> >>>>>   The build tree appears to be inside of the git repository
> located
> >> >>>>> at
> >> >>>>>
> >> >>>>>
> >> >>>>> /cfs/klemming/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paravie
> w-superbuild.
> >> >>>>>   This interferes with the way the superbuild applies patches to
> >> >>>>> projects and
> >> >>>>>   is not supported.  Please relocate the build tree to a directory
> >> >>>>> which is
> >> >>>>>   not under a git repository.
> >> >>>>> Call Stack (most recent call first):
> >> >>>>>   superbuild/projects/bzip2.cmake:7 (superbuild_apply_patch)
> >> >>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
> >> >>>>>   superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
> >> >>>>>
> >> >>>>>
> >> >>>>> -- Configuring incomplete, errors occurred!
> >> >>>>> See also
> >> >>>>>
> >> >>>>> "/cfs/nobackup/k/kriezh/PARAVIEW_SUPER_BUILD/paraview-superb
> uild/CMakeFiles/CMakeOutput.log".
> >> >>>>>
> >> >>>>>
> >> >>>>> Kind regards,
> >> >>>>> Mathi
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On 30 June 2017 at 04:13, Cory Quammen <cory.quammen at kitware.com>
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> On Wed, Jun 28, 2017 at 1:14 PM, Ezhilmathi Krishnasamy
> >> >>>>>> <ezhkr601 at student.liu.se> wrote:
> >> >>>>>> > Hi,
> >> >>>>>> >
> >> >>>>>> > Can anyone please give me some instructions how to Paraview
> >> >>>>>> > Superbuid
> >> >>>>>> > to install and use them with out using the GUI (using the
> python
> >> >>>>>> > script to
> >> >>>>>> > render the images on the cluster or super computer).
> >> >>>>>> >
> >> >>>>>> > I see there are some instructions in here:
> >> >>>>>> > https://gitlab.kitware.com/paraview/paraview-superbuild/
> >> >>>>>> >
> >> >>>>>> > But I could not find any build instructions.
> >> >>>>>>
> >> >>>>>> Take a look again, that page includes the README.md file contents
> >> >>>>>> which includes build instructions.
> >> >>>>>>
> >> >>>>>> To build without the GUI, you should just need to set the options
> >> >>>>>> ENABLE_qt4 and ENABLE_qt5 to OFF. To build with Python, set
> >> >>>>>> ENABLE_python to ON.
> >> >>>>>>
> >> >>>>>> Best regards,
> >> >>>>>> Cory
> >> >>>>>>
> >> >>>>>> >
> >> >>>>>> > Kind regards,
> >> >>>>>> > Mathi
> >> >>>>>> >
> >> >>>>>> > _______________________________________________
> >> >>>>>> > 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&D 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
> >> >>>>
> >> >>>>
> >> >>>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Cory Quammen
> >> Staff R&D Engineer
> >> Kitware, Inc.
> >
> >
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/7505e51b/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul 17 10:13:15 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 17 Jul 2017 10:13:15 -0400
Subject: [Paraview] LegacyVTKReader command
In-Reply-To: <DEA101B66315B941B487EAE03CFFF44346437A99@V-EXC-C02.DIRECTORY.INTRA>
References: <DEA101B66315B941B487EAE03CFFF44346437A99@V-EXC-C02.DIRECTORY.INTRA>
Message-ID: <CADHSJjB0ndsEYGdRY2ST9YxT9mTXHQRn_1SvHXZRLan2Cr-UyA@mail.gmail.com>

Try the following:

TEST_FEM_MeshData = LegacyVTKReader(FileNames = MeshDataList,
registrationName="MyName")


You can also use `RenameSource` to rename it after the fact.

e.g.


RenameSource("NewName",  TEST_FEM_MeshData)


Utkarsh


On Mon, Jul 17, 2017 at 7:31 AM, Amine Aboufirass <
Amine.Aboufirass at deltares.nl> wrote:

> I am trying to use the LegacyVTKReader command in paraview.simple to
> create pipelines for vtk timeseries. The following command:
>
>
>
> TEST_FEM_MeshData = LegacyVTKReader(FileNames = MeshDataList)
>
>
>
> Works well but does results in pipelines with generic names like
> ?LegacyVTKReader1? and ?LegacyVTKReader2?. How do I get this command to
> allow me to control the resulting pipeline name? I want the name to be
> ?TEST_FEM_MeshData? for example.
>
>
>
> Regards,
>
>
> Amine
>
>
>
>
> DISCLAIMER: This message is intended exclusively for the addressee(s) and
> may contain confidential and privileged information. If you are not the
> intended recipient please notify the sender immediately and destroy this
> message. Unauthorized use, disclosure or copying of this message is
> strictly prohibited. The foundation 'Stichting Deltares', which has its
> seat at Delft, The Netherlands, Commercial Registration Number 41146461, is
> not liable in any way whatsoever for consequences and/or damages resulting
> from the improper, incomplete and untimely dispatch, receipt and/or content
> of this e-mail.
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/2a5ee5ef/attachment.html>

From Amine.Aboufirass at deltares.nl  Mon Jul 17 10:43:22 2017
From: Amine.Aboufirass at deltares.nl (Amine Aboufirass)
Date: Mon, 17 Jul 2017 14:43:22 +0000
Subject: [Paraview] Referring to render views without creating a separate
 variable for each one
Message-ID: <DEA101B66315B941B487EAE03CFFF44346437B17@V-EXC-C02.DIRECTORY.INTRA>

Hello,
How do I select a render view within a layout without necessarily having to declare a new variable to hold it? In the python stack trace I am getting something like this:
SetActiveView(renderView1_2)
Where renderView1_2 is previously defined as:
renderView1_2 = CreateView('RenderView')
I am planning to develop something that can create multiple Render views and jump from one to another in a loopwise fashion. This would only be possible for a method where the views can be referred to by list number for example. It would be tedious or not possible for the above construct.
Any ideas most welcome. Thanks for your help.
Regards,

Amine

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/7ac470e0/attachment.html>

From scott.wittenburg at kitware.com  Mon Jul 17 11:56:37 2017
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Mon, 17 Jul 2017 09:56:37 -0600
Subject: [Paraview] ParaViewWeb Error - vtkweb-loader.js
In-Reply-To: <5B910C9B-962B-4846-849A-476DCBDB0D2C@gmail.com>
References: <C2E3BCEF-5189-4C45-BB27-81BE9D7CC8FD@gmail.com>
 <CABObKxe+wp-LYcLm4ptb7tAQo2WFo3GKnyYyxQJ9XVtWSu3CQQ@mail.gmail.com>
 <A7FB3A43-9BAC-4BDF-A2B0-9B5A87E59E58@gmail.com>
 <5B910C9B-962B-4846-849A-476DCBDB0D2C@gmail.com>
Message-ID: <CAPiw4fCmoRK3Zzq7shz+iCCQM8YUG_J2N2kMnCrXW033e1H7HQ@mail.gmail.com>

As Seb mentioned, it seems like you're still getting some older version of
the javascript code.  Perhaps it could help if you clear your browser cache
and reload the page?  Or maybe somehow you didn't get the version of
ParaView you intended?

Hope this helps,
Scott

On Sat, Jul 15, 2017 at 3:18 PM, Mariam <mbahameish at gmail.com> wrote:

> Any idea on how to resolve the issue?
>
> Thanks,
>
>
>
> *From: *Mariam Bahameish <mbahameish at gmail.com>
> *Date: *Tuesday, July 4, 2017 at 11:04 AM
> *To: *Sebastien Jourdain <sebastien.jourdain at kitware.com>
> *Cc: *"paraview at paraview.org" <paraview at paraview.org>
> *Subject: *Re: [Paraview] ParaViewWeb Error - vtkweb-loader.js
>
>
>
> I have installed the binary installation from the download page.
>
>
> Sent from my iPhone
>
>
> On Jul 4, 2017, at 10:48 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
> This is strange, it seems that you have the Web code of ParaView 4.
>
>
>
> How did you get/build ParaView? Are you sure it is ParaView 5.2?
>
>
>
> On Thu, Jun 29, 2017 at 4:31 AM, Mariam <mbahameish at gmail.com> wrote:
>
> Hi,
>
> I am trying to run ParaViewWeb using the following command:
>
> ./pvpython -dr ../Resources/web/visualizer/server/pvw-visualizer.py
> --content ../Resources/web/visualizer/www
>
>
>
> The connection is established, however, when accessing
> http://localhost:8080, I receive the following error in the browser
> (checked from Chrome Developer Tools):
>
> vtkweb-loader.js Failed to load resource: the server responded with a
> status of 404 (Not Found)
>
> localhost/:15 Uncaught ReferenceError: vtkWeb is not defined at
> localhost/:15
>
>
>
> From the command line, I receive the following:
>
> [HTTPChannel,0,127.0.0.1] "127.0.0.1" - - [29/Jun/2017:10:23:14 +0000]
> "GET /lib/core/vtkweb-loader.js HTTP/1.1" 404 145 "http://localhost:8080/"
> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/59.0.3071.104 Safari/537.36"
>
>
>
> ParaView version: 5.2
>
> OS: Mac
>
>
>
> I tried to look for /lib/core/vtkweb-loader.js, but this location doesn?t
> exist in the current version. It seems to be existed in older versions such
> as 5.1, so I tried to install 5.1 as well but I got the same error.
>
>
>
> Any idea on how to resolve the issue?
>
>
>
> Thanks,
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/7e5ac30f/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul 17 11:59:43 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 17 Jul 2017 11:59:43 -0400
Subject: [Paraview] Referring to render views without creating a
 separate variable for each one
In-Reply-To: <DEA101B66315B941B487EAE03CFFF44346437B17@V-EXC-C02.DIRECTORY.INTRA>
References: <DEA101B66315B941B487EAE03CFFF44346437B17@V-EXC-C02.DIRECTORY.INTRA>
Message-ID: <CADHSJjBJ4NwpVHhcvH3QcG7biDVcr+cTfhScqA4tsVBVbt8pKw@mail.gmail.com>

You have access to a function called `GetViews` which will return a list of
all views currently present. If that what you're looking for?

On Mon, Jul 17, 2017 at 10:43 AM, Amine Aboufirass <
Amine.Aboufirass at deltares.nl> wrote:

> Hello,
>
> How do I select a render view within a layout without necessarily having
> to declare a new variable to hold it? In the python stack trace I am
> getting something like this:
>
> SetActiveView(renderView1_2)
>
> Where renderView1_2 is previously defined as:
>
> renderView1_2 = CreateView(?RenderView?)
>
> I am planning to develop something that can create multiple Render views
> and jump from one to another in a loopwise fashion. This would only be
> possible for a method where the views can be referred to by list number for
> example. It would be tedious or not possible for the above construct.
>
> Any ideas most welcome. Thanks for your help.
>
> Regards,
>
>
>
> Amine
>
>
> DISCLAIMER: This message is intended exclusively for the addressee(s) and
> may contain confidential and privileged information. If you are not the
> intended recipient please notify the sender immediately and destroy this
> message. Unauthorized use, disclosure or copying of this message is
> strictly prohibited. The foundation 'Stichting Deltares', which has its
> seat at Delft, The Netherlands, Commercial Registration Number 41146461, is
> not liable in any way whatsoever for consequences and/or damages resulting
> from the improper, incomplete and untimely dispatch, receipt and/or content
> of this e-mail.
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170717/2024a781/attachment.html>

From kmorel at sandia.gov  Mon Jul 17 18:16:46 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 17 Jul 2017 22:16:46 +0000
Subject: [Paraview] **Deadline Extended** CFP: 3rd Annual Workshop on In
 Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization
 (ISAV 2017)
Message-ID: <90f94fc56fbd4681aba0148db3b84203@ES08AMSNLNT.srn.sandia.gov>

Sorry for the spam, but ParaView/Catalyst users may be interested in this workshop.


Update: paper submission due date extended to 15 Aug 2017 23:59 AoE

ISAV 2017: In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization

In cooperation with SIGHPC and held in conjunction with SC17: The International Conference on High Performance Computing, Networking, Storage and Analysis, Denver, Colorado, U.S.A.

            ISAV 2017 - http://vis.lbl.gov/Events/ISAV-2017/

         Full-day 9:00 AM - 5:30 PM Sunday November 12th, 2017

Workshop Theme

The considerable interest in the HPC community regarding in situ analysis and visualization is  due to several factors. First is an I/O cost savings, where data is analyzed/visualized while  being generated, without first storing to a file system. Second is the potential for increased  accuracy, where fine temporal sampling of transient analysis might expose some complex behavior missed in coarse temporal sampling. Third is the ability to use all available resources, CPUs and accelerators, in the computation of analysis products.

The workshop brings together researchers, developers and practitioners from industry, academia, and government laboratories developing, applying, and deploying in situ methods in extreme-scale, high performance computing. The goal is to present research findings, lessons learned, and insights related to developing and applying in situ methods and infrastructure across a range of science and engineering applications in HPC environments; to discuss topics like opportunities presented by new architectures, existing infrastructure needs, requirements, and gaps, and experiences to foster and enable in situ analysis and visualization; to serve as a "center of gravity" for researchers, practitioners, and users/consumers of in situ methods and infrastructure in the HPC space.

Participation/Call for Papers and Oral Presentations

We invite two types of submissions to ISAV 2017: (1) short, 4-page papers that present research results, that identify opportunities or challenges, and that present case studies/best practices for in situ methods/infrastructure in the areas of data management, analysis and visualization; (2) lightning presentation submission, consisting of a 1- or 2-page submission, for a brief oral presentation at the workshop. 
Short papers will appear in the workshop proceedings and will be invited to give an oral presentation of 15 to 20 minutes; lightning round submissions that are invited to present at the workshop will have author names and titles included as part of the proceedings. Submissions of both types are welcome that fall within one or more areas of interest, as follows:

Areas of interest for ISAV, include, but are not limited to:

    In situ infrastructures

       * Current Systems: production quality, research prototypes
       * Opportunities
       * Gaps

    System resources, hardware, and emerging architectures

       * Enabling Hardware
       * Hardware and architectures that provide opportunities for in situ processing, such as burst buffers, staging computations on I/O nodes, sharing cores within a node for both simulation and in situ processing

    Methods/algorithms/applications/Case studies

       * Best practices
       * Analysis: feature detection, statistical methods, temporal methods, geometric methods
       * Visualization: information visualization, scientific visualization, time-varying methods
       * Data reduction/compression
       * Examples/case studies of solving a specific science challenge with in situ methods/infrastructure.

    Simulation

       * Integration: data modeling, software-engineering
       * Resilience: error detection, fault recovery
       * Workflows for supporting complex in situ processing pipelines

    Requirements

       * Preserve important elements
       * Significantly reduce the data size
       * Flexibility for post-processing exploration


Review Process

All submissions will undergo a peer-review process consisting of three reviews by experts in the field, and evaluated according to relevance to the workshop theme, technical soundness, creativity, originality, and impactfulness of method/results. Lightning round submissions will be evaluated primarily for relevance to the workshop.

Submission Process

Authors are invited to submit papers of at most 4 pages in PDF format, excluding references, and lightning presentations of at most 2 pages in PDF format, excluding references. Papers must be submitted in PDF format (readable by Adobe Acrobat Reader 5.0 and higher) and formatted for 8.5" x 11" (U.S. Letter). Submissions are required in the ACM format (http://www.acm.org/sigs/publications/proceedings-templates) using the sample-sigconf template and submitted via EasyChair (https://easychair.org/conferences/?conf=isav17). No changes to the margins, spacing, or font sizes as specified by the style file are allowed.

Papers must be self-contained and provide the technical substance required for the program committee to evaluate their contributions. Submitted papers must be original work that has not appeared in and is not under consideration for another conference or a journal. See the ACM Prior Publication Policy for more details (http://www.acm.org/publications/policies/). Papers can be submitted at https://easychair.org/conferences/?conf=isav17.

Publication in proceedings, presentation at the workshop

All paper submissions that receive favorable reviews will be included as part of the workshop proceedings, which will be published through SIGHPC along with other SC17 workshop proceedings in the ACM Digital Library and IEEE Xplore. Lightning round submissions will not be included as part of the proceedings.

Subject to the constraints of workshop length, some subset of the accepted publications will be invited to give a brief oral presentation at the workshop. The exact number of such presentations and their length will be determined after the review process has been completed.

Timeline/Important Dates

   15 August 2017      Paper submission deadline
   15 September 2017   Author notification
   30 September 2017   Camera ready copy due
   15 October 2017     Final program posted to ISAV web page
   12 November 2017    ISAV 2017 workshop at SC17



From super_achie at hotmail.com  Tue Jul 18 03:35:50 2017
From: super_achie at hotmail.com (A .)
Date: Tue, 18 Jul 2017 07:35:50 +0000
Subject: [Paraview] Selecting a glyph object entirely and retrieving it's
	attribute data
Message-ID: <HE1P194MB01858D10B09172D2F4F0030B97A10@HE1P194MB0185.EURP194.PROD.OUTLOOK.COM>

Dear community,


For a simulation I am running, I would like to visualize a bunch of spheres in ParaView (PV). At the moment I do that by sending point data to PV and creating a Glyph filter (Sphere type) on all the points, where the radius is determined by attribute data I pass along the point data.


Now for my project I would like the user to be able to select each sphere (i.e. Glyph object), such that it's attribute data can be displayed (like the Hover On functionality); and in the best case I would like to have this attribute data (such as radius) to be modifiable (for now I just a programmable filter in which the user manually fills in the ID of the sphere to change it's corresponding attribute data).


So my two questions are:

1) Can I select the Glyph as a whole? All the selection options will only select the cells of which the glyph is made of, not the actually sphere.

2) In the Python shell will I be able to see the selected (spheres /glyphs) in order to do some attribute data modifications?


Best,

Jimmy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/4985d129/attachment.html>

From 253295860 at qq.com  Tue Jul 18 12:40:41 2017
From: 253295860 at qq.com (=?gb18030?B?qWfL5tDUtvjOqqGi?=)
Date: Wed, 19 Jul 2017 00:40:41 +0800
Subject: [Paraview]  The problem in tiled-display
Message-ID: <tencent_4F3D5E9B5C8601A160F858BA@qq.com>

Environment:6 servers(Ubuntu 16.04)  each server has 1 GPU and 2 monitors      Paraview 5.4.0 MPI Binary Install version
                    1 client(windows 10)  Paraview 5.4.0 Binary Install version
                     
After I succeed in configuring MPI, I run the command "mpirun -np 6 -machinefile ./machinefile pvserver -display :0 -tdx=3 -tdy=2"
The image can be successfully displayed on the screen.  The axes is displayed correctly.
But now, there is the problem.
After I create a sphere, it is displayed as an ellipsoid.
I 'd like to know what should I do to solve this problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/8d6ccbd5/attachment.html>

From jairaj.mathur at wustl.edu  Tue Jul 18 13:05:32 2017
From: jairaj.mathur at wustl.edu (Mathur, Jairaj)
Date: Tue, 18 Jul 2017 17:05:32 +0000
Subject: [Paraview] Using results from multiple plots/data to get average
Message-ID: <DM2PR0201MB105513F7527D7126B43ED8B9EBA10@DM2PR0201MB1055.namprd02.prod.outlook.com>

Hello all


I have 2 sets of data, and I have a plot of x1 vs time and x2 vs time from the 2 data sets. Is there a way to average out the data and plot the average x vs time within paraview?


Thanks!


Jairaj Mathur

Mechanical Engineering

Washington University at St Louis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/4d96c6e6/attachment.html>

From steytle1 at illinois.edu  Tue Jul 18 12:45:21 2017
From: steytle1 at illinois.edu (Steytler, Louis Louw)
Date: Tue, 18 Jul 2017 16:45:21 +0000
Subject: [Paraview] Importing time dependent, but not space dependent,
 data into ParaView
Message-ID: <2F8BA25CC0B82C4DB6756F8F663E6DB35BF3E570@CITESMBX3.ad.uillinois.edu>

Hi All,

I am doing some ALE multiphase fluid computations utilizing a moving mesh, and I am reading an Exodus database into ParaView. The database contains many time steps and multiple blocks.

The database contains a 3D mesh, and the usual quantities such as velocities and pressure, and mesh displacements.

Using my CFD code I compute an integral quantity at each time step. This quantity is not written to the Exodus file, it is available in a separate text file. I would like to read this quantity into ParaView for each time step, and use it in a computation together with point data.

Basically I am computing the centre of mass of an Exodus block, so that I could subtract that quantity from all the mesh displacements to get the mesh to be in the reference frame of a specific Exodus block. Because the centre of mass is a function of time only (not of space), I am guessing I would either import this as field data or as point data by setting the variable's value to be the same at every node in the mesh for a specific time step. I would like to use the ParaView calculator to subtract the time dependent data from the space and time dependent mesh displacements.

Any ideas?

Any advice would be very much appreciated!

Thanks very much,

Louis Steytler
Department of Mechanical Science and Engineering
University of Illinois at Urbana-Champaign
1206 West Green Street
Urbana, Il 61801
steytle1 at illinois.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/0173e909/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 18 13:23:39 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 18 Jul 2017 13:23:39 -0400
Subject: [Paraview] The problem in tiled-display
In-Reply-To: <tencent_4F3D5E9B5C8601A160F858BA@qq.com>
References: <tencent_4F3D5E9B5C8601A160F858BA@qq.com>
Message-ID: <CADHSJjDkKzs=8Dn4Lmy-rEMjN4YoZ1_AG9p8NpXRj2MKCCzRog@mail.gmail.com>

Yup, that's indeed a bug. I've reported it here:
https://gitlab.kitware.com/paraview/paraview/issues/17611

On Tue, Jul 18, 2017 at 12:40 PM, ?????? <253295860 at qq.com> wrote:

> Environment:6 servers(Ubuntu 16.04)  each server has 1 GPU and 2 monitors
>      Paraview 5.4.0 MPI Binary Install version
>                     1 client(windows 10)  Paraview 5.4.0 Binary Install
> version
>
> After I succeed in configuring MPI, I run the command "mpirun -np 6
> -machinefile ./machinefile pvserver -display :0 -tdx=3 -tdy=2"
> The image can be successfully displayed on the screen.  The axes is
> displayed correctly.
> But now, there is the problem.
> After I create a sphere, it is displayed as an ellipsoid.
> I 'd like to know what should I do to solve this problem.
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/3e5fd930/attachment.html>

From jkulesza at umich.edu  Tue Jul 18 13:48:40 2017
From: jkulesza at umich.edu (Joel Kulesza)
Date: Tue, 18 Jul 2017 11:48:40 -0600
Subject: [Paraview] Using results from multiple plots/data to get average
In-Reply-To: <DM2PR0201MB105513F7527D7126B43ED8B9EBA10@DM2PR0201MB1055.namprd02.prod.outlook.com>
References: <DM2PR0201MB105513F7527D7126B43ED8B9EBA10@DM2PR0201MB1055.namprd02.prod.outlook.com>
Message-ID: <CAAGOGw_E-NZ97DvOHKb6-2S_VF-B4o5JwomHNv+36GOBFtuFDQ@mail.gmail.com>

Jairaj,

My first thought would be to use a Programmable Filter:

https://www.paraview.org/Wiki/Python_calculator_and_programmable_filter#Programmable_Filter

The examples are for PointData, but it also works for CellData.

I hope this helps.  Please contact me with any comments, questions, or
concerns.

Thank you,
Joel

Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher
 University of Michigan, College of EngineeringNuclear Engineering &
Radiological Sciences Dept.2355 Bonisteel Boulevard
Ann Arbor, MI 48109-2104, USAMobile:  +1 (734) 223-7312Email:
jkulesza at umich.eduHome Page:  http://www.engin.umich.edu/ners/

On Tue, Jul 18, 2017 at 11:05 AM, Mathur, Jairaj <jairaj.mathur at wustl.edu>
wrote:

> Hello all
>
>
> I have 2 sets of data, and I have a plot of x1 vs time and x2 vs time from
> the 2 data sets. Is there a way to average out the data and plot the
> average x vs time within paraview?
>
>
> Thanks!
>
>
> Jairaj Mathur
>
> Mechanical Engineering
>
> Washington University at St Louis
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/8e269e18/attachment.html>

From joseph.g.hennessey2.ctr at mail.mil  Tue Jul 18 14:50:01 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Tue, 18 Jul 2017 18:50:01 +0000
Subject: [Paraview] [Non-DoD Source] Eye separation has been wrong since
 Immersive ParaView 5.2 - here's how to fix it
References: <D572E2C6.5E36%Mark.Stock@nrel.gov> 
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91F149F0@UCOLHPUD.easf.csd.disa.mil>

Mark,

I have discussed the changes I made with my colleagues.
We do not want to harm your work with the Cave,
so we would be okay with backing out our changes.

We can scale our data to be of size greater than 1 
by using the transform data inside of ParaView
and our data will still work. My changes were only
necessary when working with data of size less than or 
a lot less than zero.

Please let me know what I can do to assist, my changes
are found in the ParaView 5.x versions, ParaView 4.4.0
still has your code in it without my changes for visualizing
small data in stereo with devices such as the zSpace.

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Email:  joseph.g.hennessey2.ctr at mail.mil


-----Original Message-----
From: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
Sent: Monday, June 26, 2017 11:42 AM
To: 'Stock, Mark' <Mark.Stock at nrel.gov>; Gena Bug via ParaView
<paraview at paraview.org>
Subject: RE: [Non-DoD Source] [Paraview] Eye separation has been wrong since
Immersive ParaView 5.2 - here's how to fix it

Hello,

I am the one who requested the changes,
they were made to correct the stereo separation with working with zSpace
hardware
for data that was small in size (floating point values of coordinates, >> 1,
for example data that ranged from 0.0000000 to  0.0000001
I checked its use with data across 13 orders of magnitude from data of size
1,000,000 to data of scale 1/1,000,000.
I admit my fix is an approximation, but I am attempting to get a reasonable
agreement of size with  the non stereo operation

  double eyeSeparationCorrectionFactor = 10.0;
  double shiftDistance = this->EyeSeparation / (2.0 *
eyeSeparationCorrectionFactor);
  if(this->Distance < 1.0)
  {
    shiftDistance *= this->Distance;
  }

  // Front (aka near)
  double F = E[2] - (this->Distance + this->Thickness);//E[2] -
10000.0;//this->ClippingRange[1];
  // Back (aka far)
  double nearDistanceCorrectionFactor  = 1000.0;
  double B = E[2] - (this->Distance / nearDistanceCorrectionFactor);//E[2]
- .1;//this->ClippingRange[0];

Without these changes with small data the stereo separation is incorrect,
(too large)
also small data will not even show up in the render window as the clipping
planes will be wrong.

This change

"  if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) {
normalVCVSOutput = -1.0*normalVCVSOutput; }"

I did not make and do not know its purpose.

I think we  need a solution that works for both caves and planar display
hardware,
and I think the underlying issue is that there is different render code
being used,
that is a subset of the full normal rendering solution, which is creating
these issues.
I think the correct solution is to remove  the separate render code and use
the primary
code for both client and server rendering of mono and stereo. I do not have
a cave to
test with, but I do not see why we can not find a solution that works for
everyone.

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Stock,
Mark
Sent: Friday, June 23, 2017 5:23 PM
To: Gena Bug via ParaView <paraview at paraview.org>
Subject: [Non-DoD Source] [Paraview] Eye separation has been wrong since
Immersive ParaView 5.2 - here's how to fix it

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links contained
within the message prior to copying and pasting the address to a Web
browser.  




----

Hello,

If you're an Immersive ParaView user, you may have noticed that 5.x versions
don't work as well in your CAVE. Specifically, I've noticed the following
differences when compared with ParaView 4.4.0:

1) I can place an object in space properly but it seems to move 10x as fast
when I move my head.
2) If I move the object just a little farther away from its initial
position, it clips out (vanishes).
3) When I am viewing a triangle mesh, some triangles seem to flip normals
(and get dark) when I move the object around.

The first two problems are caused by a change in the VTK source code from
March 2016 which arbitrarily multiples the eye separation distance by 10,
and also tightens the near and far clipping planes. The third can be
corrected by adding a single comment (which will help CAVE and Immersive
users, but probably nobody else). Both fixes will require you to build
ParaView from source - which you're probably doing anyway. I can't comment
on how these changes will affect HMD VR users.


The first and second problems are caused by a single commit to the VTK
repository that began to appear in ParaView with version 5.2.0. The problem
code is in VTK/Rendering/Core/vtkCamera.cxx starting at line 452 in versions
5.3 and 5.4. This problem can be fixed by replacing

  double eyeSeparationCorrectionFactor = 10.0;
  double shiftDistance = this->EyeSeparation / (2.0 *
eyeSeparationCorrectionFactor);
  if(this->Distance < 1.0)
  {
    shiftDistance *= this->Distance;
  }



with simply

  double shiftDistance = this->EyeSeparation;


The second problem (clipping planes) is just a few lines down. I fixed it by
replacing

  // Front (aka near)
  double F = E[2] - (this->Distance + this->Thickness);//E[2] -
10000.0;//this->ClippingRange[1];
  // Back (aka far)
  double nearDistanceCorrectionFactor  = 1000.0;
  double B = E[2] - (this->Distance / nearDistanceCorrectionFactor);//E[2]
- .1;//this->ClippingRange[0];



with

  // Front (aka near)
  double F = E[2] - 10000.0;//this->ClippingRange[1];
  // Back (aka far)
  double B = E[2] - .1;//this->ClippingRange[0];



The third problem can be fixed by commenting out this line in
VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx (around line 1198 in 5.1,
1416 in 5.2 to 5.4):

"  if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) {
normalVCVSOutput = -1.0*normalVCVSOutput; }"


I hope these fixes help some of you out there get your CAVE updated to the
latest ParaView.

Mark

Mark.Stock at nrel.gov

_______________________________________________
Powered by Caution-www.kitware.com

Visit other Kitware open-source projects at
Caution-http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
Caution-http://paraview.org/Wiki/ParaView

Search the list archives at: Caution-http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
Caution-http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170718/a8422a32/attachment.bin>

From gabrielrezendenahas at gmail.com  Wed Jul 19 05:51:27 2017
From: gabrielrezendenahas at gmail.com (Gabriel Nahas)
Date: Wed, 19 Jul 2017 11:51:27 +0200
Subject: [Paraview] Paraview crashes when using point gaussian
Message-ID: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>

Dear all,

I am uploading 2 cases files to paraview that are correctly uploaded as far
as I can see. I can see the data and apply any filters I want, however when
I choose a Point Gaussian representation, paraview crashes and it closes.

Anyone has an idea what might cause it?

I send attached the case files, but I have already done simulations where
the exit case files are the same and no problem is seen.

Best regards,

Gabriel Nahas

-- 

[image: photo]
*Gabriel Nahas*
Master Student at ?cole Polytechnique
+33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
<https://webapp.wisestamp.com/#>
<http://www.facebook.com/gabriel.nahas.9>
<http://in.linkedin.com/in/gabriel-nahas-2566b892>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/9e664aea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: siphon.case
Type: application/octet-stream
Size: 25870 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/9e664aea/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: particle.case
Type: application/octet-stream
Size: 6707 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/9e664aea/attachment-0001.obj>

From mathieu.westphal at kitware.com  Wed Jul 19 05:53:43 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 19 Jul 2017 11:53:43 +0200
Subject: [Paraview] Paraview crashes when using point gaussian
In-Reply-To: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
References: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
Message-ID: <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>

Dear Gabriel

Could you send the associated .geo files please ?

Regards,

Mathieu Westphal

On Wed, Jul 19, 2017 at 11:51 AM, Gabriel Nahas <
gabrielrezendenahas at gmail.com> wrote:

> Dear all,
>
> I am uploading 2 cases files to paraview that are correctly uploaded as
> far as I can see. I can see the data and apply any filters I want, however
> when I choose a Point Gaussian representation, paraview crashes and it
> closes.
>
> Anyone has an idea what might cause it?
>
> I send attached the case files, but I have already done simulations where
> the exit case files are the same and no problem is seen.
>
> Best regards,
>
> Gabriel Nahas
>
> --
>
> [image: photo]
> *Gabriel Nahas*
> Master Student at ?cole Polytechnique
> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
> <https://webapp.wisestamp.com/#>
> <http://www.facebook.com/gabriel.nahas.9>
> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/6594c387/attachment.html>

From gabrielrezendenahas at gmail.com  Wed Jul 19 05:57:45 2017
From: gabrielrezendenahas at gmail.com (Gabriel Nahas)
Date: Wed, 19 Jul 2017 11:57:45 +0200
Subject: [Paraview] Paraview crashes when using point gaussian
In-Reply-To: <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>
References: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
 <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>
Message-ID: <CAN1ry7ucGx2izmp0oriCCmPVCB4jdMa+9MyqL1b6x4RRn8pWtw@mail.gmail.com>

?
 particle.00000.geo
<https://drive.google.com/file/d/0B82TKdvFoURGazk0U2N2S242TDQ/view?usp=drive_web>
??
 particle.01050.geo
<https://drive.google.com/file/d/0B82TKdvFoURGOU5hNDlreDF6VVE/view?usp=drive_web>
??
 siphon.geo
<https://drive.google.com/file/d/0B82TKdvFoURGR2VpTWtNUmZsVjQ/view?usp=drive_web>
?The geo file is here attached, Mathieu

Best regards,

Gabriel

On 19 July 2017 at 11:53, Mathieu Westphal <mathieu.westphal at kitware.com>
wrote:

> Dear Gabriel
>
> Could you send the associated .geo files please ?
>
> Regards,
>
> Mathieu Westphal
>
> On Wed, Jul 19, 2017 at 11:51 AM, Gabriel Nahas <
> gabrielrezendenahas at gmail.com> wrote:
>
>> Dear all,
>>
>> I am uploading 2 cases files to paraview that are correctly uploaded as
>> far as I can see. I can see the data and apply any filters I want, however
>> when I choose a Point Gaussian representation, paraview crashes and it
>> closes.
>>
>> Anyone has an idea what might cause it?
>>
>> I send attached the case files, but I have already done simulations where
>> the exit case files are the same and no problem is seen.
>>
>> Best regards,
>>
>> Gabriel Nahas
>>
>> --
>>
>> [image: photo]
>> *Gabriel Nahas*
>> Master Student at ?cole Polytechnique
>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>> <https://webapp.wisestamp.com/#>
>> <http://www.facebook.com/gabriel.nahas.9>
>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 

[image: photo]
*Gabriel Nahas*
Master Student at ?cole Polytechnique
+33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
<https://webapp.wisestamp.com/#>
<http://www.facebook.com/gabriel.nahas.9>
<http://in.linkedin.com/in/gabriel-nahas-2566b892>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/ab2075e0/attachment.html>

From mathieu.westphal at kitware.com  Wed Jul 19 07:14:36 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 19 Jul 2017 13:14:36 +0200
Subject: [Paraview] Paraview crashes when using point gaussian
In-Reply-To: <CAN1ry7ucGx2izmp0oriCCmPVCB4jdMa+9MyqL1b6x4RRn8pWtw@mail.gmail.com>
References: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
 <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>
 <CAN1ry7ucGx2izmp0oriCCmPVCB4jdMa+9MyqL1b6x4RRn8pWtw@mail.gmail.com>
Message-ID: <CAC2t4UTQnXPC8XT+EqNhSVVQ-z+dsTt7hr-6=PX0BdEeCN2rKQ@mail.gmail.com>

Dear Gabriel

I can't access the files :
"
The page isn?t redirecting properly

Firefox has detected that the server is redirecting the request for this
address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept
cookies.
"

Regards,



Mathieu Westphal

On Wed, Jul 19, 2017 at 11:57 AM, Gabriel Nahas <
gabrielrezendenahas at gmail.com> wrote:

> ?
>  particle.00000.geo
> <https://drive.google.com/file/d/0B82TKdvFoURGazk0U2N2S242TDQ/view?usp=drive_web>
> ??
>  particle.01050.geo
> <https://drive.google.com/file/d/0B82TKdvFoURGOU5hNDlreDF6VVE/view?usp=drive_web>
> ??
>  siphon.geo
> <https://drive.google.com/file/d/0B82TKdvFoURGR2VpTWtNUmZsVjQ/view?usp=drive_web>
> ?The geo file is here attached, Mathieu
>
> Best regards,
>
> Gabriel
>
> On 19 July 2017 at 11:53, Mathieu Westphal <mathieu.westphal at kitware.com>
> wrote:
>
>> Dear Gabriel
>>
>> Could you send the associated .geo files please ?
>>
>> Regards,
>>
>> Mathieu Westphal
>>
>> On Wed, Jul 19, 2017 at 11:51 AM, Gabriel Nahas <
>> gabrielrezendenahas at gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I am uploading 2 cases files to paraview that are correctly uploaded as
>>> far as I can see. I can see the data and apply any filters I want, however
>>> when I choose a Point Gaussian representation, paraview crashes and it
>>> closes.
>>>
>>> Anyone has an idea what might cause it?
>>>
>>> I send attached the case files, but I have already done simulations
>>> where the exit case files are the same and no problem is seen.
>>>
>>> Best regards,
>>>
>>> Gabriel Nahas
>>>
>>> --
>>>
>>> [image: photo]
>>> *Gabriel Nahas*
>>> Master Student at ?cole Polytechnique
>>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>>> <https://webapp.wisestamp.com/#>
>>> <http://www.facebook.com/gabriel.nahas.9>
>>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
> --
>
> [image: photo]
> *Gabriel Nahas*
> Master Student at ?cole Polytechnique
> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
> <https://webapp.wisestamp.com/#>
> <http://www.facebook.com/gabriel.nahas.9>
> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/5d3e6ada/attachment.html>

From smikhaylov_2011 at mail.ru  Wed Jul 19 02:26:36 2017
From: smikhaylov_2011 at mail.ru (=?UTF-8?B?0KHQtdGA0LPQtdC5INCc0LjRhdCw0LnQu9C+0LI=?=)
Date: Wed, 19 Jul 2017 09:26:36 +0300
Subject: [Paraview] =?utf-8?q?question_about_using_ParaView?=
Message-ID: <1500445596.678406259@f393.i.mail.ru>


Hello !
We have the following ?3D object: ?

I want to? left cylinder in the center of the object and delete another part of the object. The result of such operation is cylinder.
How can I do it?
?
?
Best regards, Mikhaylov Sergey
Company JSC " RN - UfaNIPIneft "
Tel: (347) 293-60-10 ex. 2734
?
----------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/bf146d17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 143984 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/bf146d17/attachment-0001.png>

From mathieu.westphal at kitware.com  Wed Jul 19 07:50:00 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 19 Jul 2017 13:50:00 +0200
Subject: [Paraview] question about using ParaView
In-Reply-To: <1500445596.678406259@f393.i.mail.ru>
References: <1500445596.678406259@f393.i.mail.ru>
Message-ID: <CAC2t4USqkizUfK1ZLc0THik59uWhLgR8vu214Cxr07=UDfSd1w@mail.gmail.com>

Dear Mikhaylov

Could you share your dataset ?
In any case a finely tuned Cylindrical Clip could do the trick.

Regards,

Mathieu Westphal

On Wed, Jul 19, 2017 at 8:26 AM, ?????? ???????? via ParaView <
paraview at paraview.org> wrote:

> Hello!
>
> We have the following  3D object:
>
> I want to  left cylinder in the center of the object and delete another
> part of the object. The result of such operation is cylinder.
>
> How can I do it?
>
>
>
>
>
> Best regards, Mikhaylov Sergey
>
> Company JSC "RN-UfaNIPIneft"
>
> Tel: (347) 293-60-10 ex. 2734
>
>
>
> ------------------------------
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/cc6b2638/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 143984 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/cc6b2638/attachment.png>

From hayk.grigoryan.a at gmail.com  Wed Jul 19 08:34:26 2017
From: hayk.grigoryan.a at gmail.com (Hayk Grigoryan)
Date: Wed, 19 Jul 2017 16:34:26 +0400
Subject: [Paraview] Fwd:  ParaviewWeb OSMesa build
In-Reply-To: <CAABzCAyV4_U=Z2QTk6gD+FQBp1qcjEUdG2-PVm0gRf3NxUXZ9g@mail.gmail.com>
References: <59556572.d4931c0a.53696.5630@mx.google.com>
 <CABObKxdx+DKhjbAEp_4xW-t4dM+_Q774djaGfYM6=BhpEgTOAw@mail.gmail.com>
 <CAABzCAyV4_U=Z2QTk6gD+FQBp1qcjEUdG2-PVm0gRf3NxUXZ9g@mail.gmail.com>
Message-ID: <CAABzCAytxMjadpQ+Ko8fM5Mo7kM9UbO0znv4W6uO6cqy74PDjg@mail.gmail.com>

---------- Forwarded message ----------
From: Hayk Grigoryan <hayk.grigoryan.a at gmail.com>
Date: Wed, Jul 19, 2017 at 4:33 PM
Subject: Re: [Paraview] ParaviewWeb OSMesa build
To: Sebastien Jourdain <sebastien.jourdain at kitware.com>


Dear Sebastien,

Thanks for you response.

I'm trying a different ways for configuring paraviewweb as a web service.

Now I have Ubuntu Desktop 16.04 and followed the tutorial link
https://kitware.github.io/paraviewweb/docs/ubuntu_14_04.html .

Following the steps I end up with error about WebSockets -> WebSocket
connect to 'ws://localhost/ws' failed.

I've used Paraview 5.2 and 5.4 versions.

After long hours research I didn't find any answer for me.

Could you please help to understand what cause this problem: Ubuntu
version, Paraview version or configurations.

Thanks in advance,
Hayk

On Tue, Jul 4, 2017 at 1:45 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Yes, but you will need to build ParaView with either OSMesa or EGL (if you
> have a compatible NVidia GPU).
>
> When you do so, you won't need to build the Qt UI.
>
> Seb
>
> On Thu, Jun 29, 2017 at 2:39 PM, <hayk.grigoryan.a at gmail.com> wrote:
>
>> Hi,
>>
>>
>>
>> I'm trying to build ParaViewWeb with OSMesa. I need help with my question.
>>
>>
>>
>> I've ubuntu 14.04 server without desktop and X. Can I install and make
>> ParaViewWeb to work as a web service on my server?
>>
>>
>>
>> Thank in advance,
>>
>> Hayk
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/d27b7b21/attachment.html>

From joachim.pouderoux at kitware.com  Wed Jul 19 08:41:05 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Wed, 19 Jul 2017 08:41:05 -0400
Subject: [Paraview] Paraview crashes when using point gaussian
In-Reply-To: <CAC2t4UTQnXPC8XT+EqNhSVVQ-z+dsTt7hr-6=PX0BdEeCN2rKQ@mail.gmail.com>
References: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
 <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>
 <CAN1ry7ucGx2izmp0oriCCmPVCB4jdMa+9MyqL1b6x4RRn8pWtw@mail.gmail.com>
 <CAC2t4UTQnXPC8XT+EqNhSVVQ-z+dsTt7hr-6=PX0BdEeCN2rKQ@mail.gmail.com>
Message-ID: <CACJ=gTg8c4vRK0x+iPqK4e40U4x+KxOAhgEbF+-xrm8mA_Hz8g@mail.gmail.com>

Dear Gabril,

I can open the case file you sent but it looks like there are some missing
files to open the full dataset.
With the loaded data, the Point Gaussian representation works well on my
computer.
Does the representation crash only for this dataset? Does it crash with
another source?

Best regards,

*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS <http://www.kitware.fr>*


2017-07-19 7:14 GMT-04:00 Mathieu Westphal <mathieu.westphal at kitware.com>:

> Dear Gabriel
>
> I can't access the files :
> "
> The page isn?t redirecting properly
>
> Firefox has detected that the server is redirecting the request for this
> address in a way that will never complete.
>
>     This problem can sometimes be caused by disabling or refusing to
> accept cookies.
> "
>
> Regards,
>
>
>
> Mathieu Westphal
>
> On Wed, Jul 19, 2017 at 11:57 AM, Gabriel Nahas <
> gabrielrezendenahas at gmail.com> wrote:
>
>> ?
>>  particle.00000.geo
>> <https://drive.google.com/file/d/0B82TKdvFoURGazk0U2N2S242TDQ/view?usp=drive_web>
>> ??
>>  particle.01050.geo
>> <https://drive.google.com/file/d/0B82TKdvFoURGOU5hNDlreDF6VVE/view?usp=drive_web>
>> ??
>>  siphon.geo
>> <https://drive.google.com/file/d/0B82TKdvFoURGR2VpTWtNUmZsVjQ/view?usp=drive_web>
>> ?The geo file is here attached, Mathieu
>>
>> Best regards,
>>
>> Gabriel
>>
>> On 19 July 2017 at 11:53, Mathieu Westphal <mathieu.westphal at kitware.com>
>> wrote:
>>
>>> Dear Gabriel
>>>
>>> Could you send the associated .geo files please ?
>>>
>>> Regards,
>>>
>>> Mathieu Westphal
>>>
>>> On Wed, Jul 19, 2017 at 11:51 AM, Gabriel Nahas <
>>> gabrielrezendenahas at gmail.com> wrote:
>>>
>>>> Dear all,
>>>>
>>>> I am uploading 2 cases files to paraview that are correctly uploaded as
>>>> far as I can see. I can see the data and apply any filters I want, however
>>>> when I choose a Point Gaussian representation, paraview crashes and it
>>>> closes.
>>>>
>>>> Anyone has an idea what might cause it?
>>>>
>>>> I send attached the case files, but I have already done simulations
>>>> where the exit case files are the same and no problem is seen.
>>>>
>>>> Best regards,
>>>>
>>>> Gabriel Nahas
>>>>
>>>> --
>>>>
>>>> [image: photo]
>>>> *Gabriel Nahas*
>>>> Master Student at ?cole Polytechnique
>>>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>>>> <https://webapp.wisestamp.com/#>
>>>> <http://www.facebook.com/gabriel.nahas.9>
>>>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>>
>> --
>>
>> [image: photo]
>> *Gabriel Nahas*
>> Master Student at ?cole Polytechnique
>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>> <https://webapp.wisestamp.com/#>
>> <http://www.facebook.com/gabriel.nahas.9>
>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/11260664/attachment.html>

From joachim.pouderoux at kitware.com  Wed Jul 19 08:41:37 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Wed, 19 Jul 2017 08:41:37 -0400
Subject: [Paraview] Paraview crashes when using point gaussian
In-Reply-To: <CACJ=gTg8c4vRK0x+iPqK4e40U4x+KxOAhgEbF+-xrm8mA_Hz8g@mail.gmail.com>
References: <CAN1ry7umgnD=+r9TmUzQZaGP4NuqpQMCC4iB=VQpvE60HkiThg@mail.gmail.com>
 <CAC2t4USRb6A2R1OJ8_t50mcrfD34cQ83eXcNH4DxJ8mZLENWxA@mail.gmail.com>
 <CAN1ry7ucGx2izmp0oriCCmPVCB4jdMa+9MyqL1b6x4RRn8pWtw@mail.gmail.com>
 <CAC2t4UTQnXPC8XT+EqNhSVVQ-z+dsTt7hr-6=PX0BdEeCN2rKQ@mail.gmail.com>
 <CACJ=gTg8c4vRK0x+iPqK4e40U4x+KxOAhgEbF+-xrm8mA_Hz8g@mail.gmail.com>
Message-ID: <CACJ=gTh_1sGJ_OYuFq7MSSm4NCTA5mRPJT_deoe77b2-rZxFsw@mail.gmail.com>

Attached is the screenshot of what I get on my box.

Best,

*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS <http://www.kitware.fr>*


2017-07-19 8:41 GMT-04:00 Joachim Pouderoux <joachim.pouderoux at kitware.com>:

> Dear Gabril,
>
> I can open the case file you sent but it looks like there are some missing
> files to open the full dataset.
> With the loaded data, the Point Gaussian representation works well on my
> computer.
> Does the representation crash only for this dataset? Does it crash with
> another source?
>
> Best regards,
>
> *Joachim Pouderoux*, PhD
>
> *Technical Expert - Scientific Computing Team*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2017-07-19 7:14 GMT-04:00 Mathieu Westphal <mathieu.westphal at kitware.com>:
>
>> Dear Gabriel
>>
>> I can't access the files :
>> "
>> The page isn?t redirecting properly
>>
>> Firefox has detected that the server is redirecting the request for this
>> address in a way that will never complete.
>>
>>     This problem can sometimes be caused by disabling or refusing to
>> accept cookies.
>> "
>>
>> Regards,
>>
>>
>>
>> Mathieu Westphal
>>
>> On Wed, Jul 19, 2017 at 11:57 AM, Gabriel Nahas <
>> gabrielrezendenahas at gmail.com> wrote:
>>
>>> ?
>>>  particle.00000.geo
>>> <https://drive.google.com/file/d/0B82TKdvFoURGazk0U2N2S242TDQ/view?usp=drive_web>
>>> ??
>>>  particle.01050.geo
>>> <https://drive.google.com/file/d/0B82TKdvFoURGOU5hNDlreDF6VVE/view?usp=drive_web>
>>> ??
>>>  siphon.geo
>>> <https://drive.google.com/file/d/0B82TKdvFoURGR2VpTWtNUmZsVjQ/view?usp=drive_web>
>>> ?The geo file is here attached, Mathieu
>>>
>>> Best regards,
>>>
>>> Gabriel
>>>
>>> On 19 July 2017 at 11:53, Mathieu Westphal <mathieu.westphal at kitware.com
>>> > wrote:
>>>
>>>> Dear Gabriel
>>>>
>>>> Could you send the associated .geo files please ?
>>>>
>>>> Regards,
>>>>
>>>> Mathieu Westphal
>>>>
>>>> On Wed, Jul 19, 2017 at 11:51 AM, Gabriel Nahas <
>>>> gabrielrezendenahas at gmail.com> wrote:
>>>>
>>>>> Dear all,
>>>>>
>>>>> I am uploading 2 cases files to paraview that are correctly uploaded
>>>>> as far as I can see. I can see the data and apply any filters I want,
>>>>> however when I choose a Point Gaussian representation, paraview crashes and
>>>>> it closes.
>>>>>
>>>>> Anyone has an idea what might cause it?
>>>>>
>>>>> I send attached the case files, but I have already done simulations
>>>>> where the exit case files are the same and no problem is seen.
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Gabriel Nahas
>>>>>
>>>>> --
>>>>>
>>>>> [image: photo]
>>>>> *Gabriel Nahas*
>>>>> Master Student at ?cole Polytechnique
>>>>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>>>>> <https://webapp.wisestamp.com/#>
>>>>> <http://www.facebook.com/gabriel.nahas.9>
>>>>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> [image: photo]
>>> *Gabriel Nahas*
>>> Master Student at ?cole Polytechnique
>>> +33 6 38 28 29 92 <+33+6+38+28+29+92> | Skype: gabrielrezendenahas
>>> <https://webapp.wisestamp.com/#>
>>> <http://www.facebook.com/gabriel.nahas.9>
>>> <http://in.linkedin.com/in/gabriel-nahas-2566b892>
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/733873ff/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pointgauss.PNG
Type: image/png
Size: 511937 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/733873ff/attachment-0001.png>

From sebastien.jourdain at kitware.com  Wed Jul 19 10:28:44 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 19 Jul 2017 08:28:44 -0600
Subject: [Paraview] Fwd: ParaviewWeb OSMesa build
In-Reply-To: <CAABzCAytxMjadpQ+Ko8fM5Mo7kM9UbO0znv4W6uO6cqy74PDjg@mail.gmail.com>
References: <59556572.d4931c0a.53696.5630@mx.google.com>
 <CABObKxdx+DKhjbAEp_4xW-t4dM+_Q774djaGfYM6=BhpEgTOAw@mail.gmail.com>
 <CAABzCAyV4_U=Z2QTk6gD+FQBp1qcjEUdG2-PVm0gRf3NxUXZ9g@mail.gmail.com>
 <CAABzCAytxMjadpQ+Ko8fM5Mo7kM9UbO0znv4W6uO6cqy74PDjg@mail.gmail.com>
Message-ID: <CABObKxf4VpF+jpga-QVwq3TMgdqWua1nYZzNzOdYv93GLQheDA@mail.gmail.com>

Did you get any error or feedback in the various logs? Moreover, which URL
did you use to connect and what launcher and apache configuration did you
use?

On Wed, Jul 19, 2017 at 6:34 AM, Hayk Grigoryan <hayk.grigoryan.a at gmail.com>
wrote:

>
> ---------- Forwarded message ----------
> From: Hayk Grigoryan <hayk.grigoryan.a at gmail.com>
> Date: Wed, Jul 19, 2017 at 4:33 PM
> Subject: Re: [Paraview] ParaviewWeb OSMesa build
> To: Sebastien Jourdain <sebastien.jourdain at kitware.com>
>
>
> Dear Sebastien,
>
> Thanks for you response.
>
> I'm trying a different ways for configuring paraviewweb as a web service.
>
> Now I have Ubuntu Desktop 16.04 and followed the tutorial link
> https://kitware.github.io/paraviewweb/docs/ubuntu_14_04.html .
>
> Following the steps I end up with error about WebSockets -> WebSocket
> connect to 'ws://localhost/ws' failed.
>
> I've used Paraview 5.2 and 5.4 versions.
>
> After long hours research I didn't find any answer for me.
>
> Could you please help to understand what cause this problem: Ubuntu
> version, Paraview version or configurations.
>
> Thanks in advance,
> Hayk
>
> On Tue, Jul 4, 2017 at 1:45 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Yes, but you will need to build ParaView with either OSMesa or EGL (if
>> you have a compatible NVidia GPU).
>>
>> When you do so, you won't need to build the Qt UI.
>>
>> Seb
>>
>> On Thu, Jun 29, 2017 at 2:39 PM, <hayk.grigoryan.a at gmail.com> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> I'm trying to build ParaViewWeb with OSMesa. I need help with my
>>> question.
>>>
>>>
>>>
>>> I've ubuntu 14.04 server without desktop and X. Can I install and make
>>> ParaViewWeb to work as a web service on my server?
>>>
>>>
>>>
>>> Thank in advance,
>>>
>>> Hayk
>>>
>>> _______________________________________________
>>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/f7253467/attachment.html>

From hayk.grigoryan.a at gmail.com  Wed Jul 19 12:23:18 2017
From: hayk.grigoryan.a at gmail.com (Hayk Grigoryan)
Date: Wed, 19 Jul 2017 20:23:18 +0400
Subject: [Paraview] Fwd: ParaviewWeb OSMesa build
In-Reply-To: <CABObKxf4VpF+jpga-QVwq3TMgdqWua1nYZzNzOdYv93GLQheDA@mail.gmail.com>
References: <59556572.d4931c0a.53696.5630@mx.google.com>
 <CABObKxdx+DKhjbAEp_4xW-t4dM+_Q774djaGfYM6=BhpEgTOAw@mail.gmail.com>
 <CAABzCAyV4_U=Z2QTk6gD+FQBp1qcjEUdG2-PVm0gRf3NxUXZ9g@mail.gmail.com>
 <CAABzCAytxMjadpQ+Ko8fM5Mo7kM9UbO0znv4W6uO6cqy74PDjg@mail.gmail.com>
 <CABObKxf4VpF+jpga-QVwq3TMgdqWua1nYZzNzOdYv93GLQheDA@mail.gmail.com>
Message-ID: <CAABzCAwHZNDofXR2evMk7SsLuoqU=5Ab0ix02hpuuuihjUJiyQ@mail.gmail.com>

No, there is not any error logs in log files, just one that I wrote I see
in the browser console. Please find in attachments the config files.

I'm using http://localhost/visualizer or http://localhost/lightviz. BTW
lightviz is showing a black page with 2 icons in the top left, and there is
not errors. The error appears on visualizer.

Thanks,
Hayk

On Wed, Jul 19, 2017 at 6:28 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Did you get any error or feedback in the various logs? Moreover, which URL
> did you use to connect and what launcher and apache configuration did you
> use?
>
> On Wed, Jul 19, 2017 at 6:34 AM, Hayk Grigoryan <
> hayk.grigoryan.a at gmail.com> wrote:
>
>>
>> ---------- Forwarded message ----------
>> From: Hayk Grigoryan <hayk.grigoryan.a at gmail.com>
>> Date: Wed, Jul 19, 2017 at 4:33 PM
>> Subject: Re: [Paraview] ParaviewWeb OSMesa build
>> To: Sebastien Jourdain <sebastien.jourdain at kitware.com>
>>
>>
>> Dear Sebastien,
>>
>> Thanks for you response.
>>
>> I'm trying a different ways for configuring paraviewweb as a web service.
>>
>> Now I have Ubuntu Desktop 16.04 and followed the tutorial link
>> https://kitware.github.io/paraviewweb/docs/ubuntu_14_04.html .
>>
>> Following the steps I end up with error about WebSockets -> WebSocket
>> connect to 'ws://localhost/ws' failed.
>>
>> I've used Paraview 5.2 and 5.4 versions.
>>
>> After long hours research I didn't find any answer for me.
>>
>> Could you please help to understand what cause this problem: Ubuntu
>> version, Paraview version or configurations.
>>
>> Thanks in advance,
>> Hayk
>>
>> On Tue, Jul 4, 2017 at 1:45 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Yes, but you will need to build ParaView with either OSMesa or EGL (if
>>> you have a compatible NVidia GPU).
>>>
>>> When you do so, you won't need to build the Qt UI.
>>>
>>> Seb
>>>
>>> On Thu, Jun 29, 2017 at 2:39 PM, <hayk.grigoryan.a at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I'm trying to build ParaViewWeb with OSMesa. I need help with my
>>>> question.
>>>>
>>>>
>>>>
>>>> I've ubuntu 14.04 server without desktop and X. Can I install and make
>>>> ParaViewWeb to work as a web service on my server?
>>>>
>>>>
>>>>
>>>> Thank in advance,
>>>>
>>>> Hayk
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/fe0cdd8f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: launcher.json
Type: application/json
Size: 1387 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/fe0cdd8f/attachment.json>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pvw.conf
Type: application/octet-stream
Size: 782 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170719/fe0cdd8f/attachment.obj>

From bastil2001 at yahoo.de  Wed Jul 19 14:21:16 2017
From: bastil2001 at yahoo.de (bastil2001)
Date: Wed, 19 Jul 2017 20:21:16 +0200
Subject: [Paraview] Extract by ID
Message-ID: <7ed0e1fc-a128-90ba-ee74-b2f2452ae422@yahoo.de>

Hello all,

short question: I have an unstructured grid where I want to extract
cells from. I know the IDs of the cells. Is there an easy way to do and
script that? Thanks.


From martin.cuma at utah.edu  Wed Jul 19 15:19:35 2017
From: martin.cuma at utah.edu (Martin Cuma)
Date: Wed, 19 Jul 2017 13:19:35 -0600 (MDT)
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <20170714140156.GA25876@megas.kitware.com>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
Message-ID: <alpine.LRH.2.20.1707191312100.1837@marastik.chpc.utah.edu>

Hi Ben,

I finally got all the dependencies in and built Paraview from the source 
with the debug options on our CentOS 7 machine. Paraview still segfaults, 
and, loading the core file in gdb, below is the backtrace. If you see 
anything of interest, I'd be keen to know it.

Program terminated with signal 11, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb)
(gdb) bt
#0  0x0000000000000000 in  ()
#1  0x00007f4acb27fcd6 in 
vtkOpenGLRenderWindow::CreateHardwareOffScreenBuffers(int, int, bool) 
(this=0x372fe10, width=300, height=300, bind=false)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2004
#2  0x00007f4acb27f971 in 
vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int, int) 
(this=0x372fe10, width=300, height=300)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:1917
#3  0x00007f4acb31ae10 in 
vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int) (this=0x372fe10, 
width=300, height=300)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:814
#4  0x00007f4acb31b222 in vtkXOpenGLRenderWindow::Initialize() 
(this=0x372fe10)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:929
#5  0x00007f4acb280d41 in vtkOpenGLRenderWindow::SupportsOpenGL() 
(this=0x372e610)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2350
#6  0x00007f4ac2c6ed45 in vtkPVDisplayInformation::SupportsOpenGLLocally() 
()
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108
---Type <return> to continue, or q <return> to quit---
#7  0x00007f4ac2c6edc9 in 
vtkPVDisplayInformation::CopyFromObject(vtkObject*) (this=0x1f6e330)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124
#8  0x00007f4acd16151a in 
vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned 
int) (this=0x1614fc0, information=0x1f6e330, globalid=0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:783
#9  0x00007f4acd1617cf in vtkPVSessionCore::GatherInformation(unsigned 
int, vtkPVInformation*, unsigned int) (this=0x1614fc0, location=4, 
information=0x1f6e330, globalid=0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:821
#10 0x00007f4acd15d458 in vtkPVSessionBase::GatherInformation(unsigned 
int, vtkPVInformation*, unsigned int) (this=
     0x1d197b0, location=4, information=0x1f6e330, globalid=0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:243
#11 0x00007f4acfea426d in 
pqDefaultViewBehavior::onServerCreation(pqServer*) (this=0x1d15b00, 
server=0x20b4ed0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/ApplicationComponents/pqDefaultViewBehavior.cxx:119
#12 0x00007f4acff4cf5c in 
pqDefaultViewBehavior::qt_static_metacall(QObject*, QM---Type <return> to 
continue, or q <return> to quit---
etaObject::Call, int, void**) (_o=0x1d15b00, 
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff452a5390)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/ApplicationComponents/moc_pqDefaultViewBehavior.cpp:81
#13 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int, 
void**) ()
     at /lib64/libQt5Core.so.5
#14 0x00007f4acf49d885 in pqServerManagerModel::serverAdded(pqServer*) 
(this=0x15e5e30, _t1=0x20b4ed0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/moc_pqServerManagerModel.cpp:564
#15 0x00007f4acf4671f8 in pqServerManagerModel::onConnectionCreated(long 
long) (this=0x15e5e30, id=1)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqServerManagerModel.cxx:503
#16 0x00007f4acf49ce83 in 
pqServerManagerModel::qt_static_metacall(QObject*, QMetaObject::Call, int, 
void**) (_o=0x15e5e30, _c=QMetaObject::InvokeMetaMethod, _id=36, 
_a=0x7fff452a55e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/moc_pqServerManagerModel.cpp:268
#17 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int, 
void**) ()
     at /lib64/libQt5Core.so.5
#18 0x00007f4acf49ebf7 in pqServerManagerObserver::connectionCreated(long 
long) (this=0x1823580, _t1=1)
---Type <return> to continue, or q <return> to quit---
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/moc_pqServerManagerObserver.cpp:278
#19 0x00007f4acf46ad11 in 
pqServerManagerObserver::connectionCreated(vtkObject*, unsigned long, 
void*, void*) (this=0x1823580, callData=0x15fe1e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqServerManagerObserver.cxx:110
#20 0x00007f4acf49e604 in 
pqServerManagerObserver::qt_static_metacall(QObject*, QMetaObject::Call, 
int, void**) (_o=0x1823580, _c=QMetaObject::InvokeMetaMethod, _id=10, 
_a=0x7fff452a5830)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/moc_pqServerManagerObserver.cpp:142
#21 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int, 
void**) ()
     at /lib64/libQt5Core.so.5
#22 0x00007f4acc2b5f34 in vtkQtConnection::EmitExecute(vtkObject*, 
unsigned long, void*, void*, vtkCommand*) (this=0x15e7f90, _t1=0x15fe1a0, 
_t2=67, _t3=0x0, _t4=0x15fe1e0, _t5=0x1614ce0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/VTK/GUISupport/Qt/moc_vtkQtConnection.cpp:139
#23 0x00007f4acc2a13a6 in vtkQtConnection::Execute(vtkObject*, unsigned 
long, void*) (this=0x15e7f90, caller=0x15fe1a0, e=67, call_data=0x15fe1e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/GUISupport/Qt/vtkQtConnection.cxx:72
#24 0x00007f4acc2a1346 in vtkQtConnection::DoCallback(vtkObject*, unsigned 
long,---Type <return> to continue, or q <return> to quit---
  void*, void*) (vtk_obj=0x15fe1a0, event=67, client_data=0x15e7f90, 
call_data=0x15fe1e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/GUISupport/Qt/vtkQtConnection.cxx:62
#25 0x00007f4ac5978d21 in vtkCallbackCommand::Execute(vtkObject*, unsigned 
long, void*) (this=0x1614ce0, caller=0x15fe1a0, event=67, 
callData=0x15fe1e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/Core/vtkCallbackCommand.cxx:42
#26 0x00007f4ac5a80264 in vtkSubjectHelper::InvokeEvent(unsigned long, 
void*, vtkObject*) (this=0x156bcb0, event=67, callData=0x15fe1e0, 
self=0x15fe1a0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/Core/vtkObject.cxx:616
#27 0x00007f4ac5a8077f in vtkObject::InvokeEvent(unsigned long, void*) 
(this=0x15fe1a0, event=67, callData=0x15fe1e0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/Core/vtkObject.cxx:785
#28 0x00007f4acc9f4ab3 in vtkProcessModule::RegisterSession(vtkSession*) 
(this=0x15fe1a0, session=0x1d197b0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:378
#29 0x00007f4acd657bf7 in vtkSMSession::ConnectToSelf() ()
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/ServerManager/Core/vtkSMSession.cxx:311
---Type <return> to continue, or q <return> to quit---
#30 0x00007f4acf4235d6 in pqObjectBuilder::createServer(pqServerResource 
const&) (this=0x15e80e0, resource=...)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqObjectBuilder.cxx:656
#31 0x00007f4acfe5cca6 in pqAlwaysConnectedBehavior::serverCheck() (this=
     0x1d16b30)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:81
#32 0x00007f4acfe5cb26 in 
pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) 
(this=0x1d16b30, parentObject=0x1d143c0)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:52
#33 0x00007f4acfeda449 in 
pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) 
(this=0x1d143c0, mainWindow=0x160b200, parentObject=0x160b200)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/ApplicationComponents/pqParaViewBehaviors.cxx:163
#34 0x00000000004113ca in ParaViewMainWindow::ParaViewMainWindow() (this=
     0x160b200)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Applications/ParaView/ParaViewMainWindow.cxx:258
#35 0x000000000040f1c7 in pqparaviewInitializer::Initialize(int, char**) 
(this=0x7fff452a61c0, argc=1, argv=0x7fff452a6338)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Applications/ParaView---Type 
<return> to continue, or q <return> to quit---
/pqparaviewInitializer.cxx:122
#36 0x000000000040eb64 in main(int, char**) (argc=1, argv=0x7fff452a6338)
     at 
/uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Applications/ParaView/paraview_main.cxx:121

Thanks,
MC

-- 
Martin Cuma
Center for High Performance Computing
Department of Geology and Geophysics
University of Utah


From rccm.kyoshimi at gmail.com  Wed Jul 19 20:06:59 2017
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Thu, 20 Jul 2017 09:06:59 +0900
Subject: [Paraview] Extract by ID
In-Reply-To: <7ed0e1fc-a128-90ba-ee74-b2f2452ae422@yahoo.de>
References: <7ed0e1fc-a128-90ba-ee74-b2f2452ae422@yahoo.de>
Message-ID: <CAHDyfPCMOdL2xJ6VDzO04Fzig+8HZBPZnzWMseQzWoTm8RxcrQ@mail.gmail.com>

Hi bastil,

This can be achieved through running a query (Edit > Find Data) on
your data using the criteria "is one of" where you can specify
multiple separated cell ids by a comma(,). After selecting the cells
the Extract Selection filter will extract a set of them.

Thanks,
yoshimi

2017-07-20 3:21 GMT+09:00 bastil2001 via ParaView <paraview at paraview.org>:
> Hello all,
>
> short question: I have an unstructured grid where I want to extract
> cells from. I know the IDs of the cells. Is there an easy way to do and
> script that? Thanks.
>
> _______________________________________________
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: criteria_is_on_of.png
Type: image/png
Size: 16160 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170720/7e6130d3/attachment.png>

From chuck.atkins at kitware.com  Thu Jul 20 01:38:51 2017
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 20 Jul 2017 01:38:51 -0400
Subject: [Paraview] Paraview segfaults on CentOS 7.2
In-Reply-To: <alpine.LRH.2.20.1707191312100.1837@marastik.chpc.utah.edu>
References: <alpine.LRH.2.20.1707131437380.29075@marastik.chpc.utah.edu>
 <20170714140156.GA25876@megas.kitware.com>
 <alpine.LRH.2.20.1707191312100.1837@marastik.chpc.utah.edu>
Message-ID: <CAOXZzG5=NOxSpUoE=EsORsvZQZNtTLz2JPAk3JcV9pfhsruW5g@mail.gmail.com>

Hi Martin,

Do you know which graphics card and OpenGL driver you're using?  Given that
it works with the --mesa option I suspect ParaView is hitting an issue with
your OpenGL stack.  Some versions of the binary AMD/ATI driver on Linux
have known bugs in them that cause ParaView to segfault, for instance.

----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.


On Wed, Jul 19, 2017 at 3:19 PM, Martin Cuma <martin.cuma at utah.edu> wrote:

> Hi Ben,
>
> I finally got all the dependencies in and built Paraview from the source
> with the debug options on our CentOS 7 machine. Paraview still segfaults,
> and, loading the core file in gdb, below is the backtrace. If you see
> anything of interest, I'd be keen to know it.
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x0000000000000000 in ?? ()
> (gdb)
> (gdb) bt
> #0  0x0000000000000000 in  ()
> #1  0x00007f4acb27fcd6 in vtkOpenGLRenderWindow::CreateHardwareOffScreenBuffers(int,
> int, bool) (this=0x372fe10, width=300, height=300, bind=false)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/
> OpenGL2/vtkOpenGLRenderWindow.cxx:2004
> #2  0x00007f4acb27f971 in vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int,
> int) (this=0x372fe10, width=300, height=300)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/
> OpenGL2/vtkOpenGLRenderWindow.cxx:1917
> #3  0x00007f4acb31ae10 in vtkXOpenGLRenderWindow::CreateOffScreenWindow(int,
> int) (this=0x372fe10, width=300, height=300)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/
> OpenGL2/vtkXOpenGLRenderWindow.cxx:814
> #4  0x00007f4acb31b222 in vtkXOpenGLRenderWindow::Initialize()
> (this=0x372fe10)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/
> OpenGL2/vtkXOpenGLRenderWindow.cxx:929
> #5  0x00007f4acb280d41 in vtkOpenGLRenderWindow::SupportsOpenGL()
> (this=0x372e610)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/
> OpenGL2/vtkOpenGLRenderWindow.cxx:2350
> #6  0x00007f4ac2c6ed45 in vtkPVDisplayInformation::SupportsOpenGLLocally()
> ()
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/
> ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108
> ---Type <return> to continue, or q <return> to quit---
> #7  0x00007f4ac2c6edc9 in vtkPVDisplayInformation::CopyFromObject(vtkObject*)
> (this=0x1f6e330)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/
> ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124
> #8  0x00007f4acd16151a in vtkPVSessionCore::GatherInform
> ationInternal(vtkPVInformation*, unsigned int) (this=0x1614fc0,
> information=0x1f6e330, globalid=0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/S
> erverImplementation/Core/vtkPVSessionCore.cxx:783
> #9  0x00007f4acd1617cf in vtkPVSessionCore::GatherInformation(unsigned
> int, vtkPVInformation*, unsigned int) (this=0x1614fc0, location=4,
> information=0x1f6e330, globalid=0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/S
> erverImplementation/Core/vtkPVSessionCore.cxx:821
> #10 0x00007f4acd15d458 in vtkPVSessionBase::GatherInformation(unsigned
> int, vtkPVInformation*, unsigned int) (this=
>     0x1d197b0, location=4, information=0x1f6e330, globalid=0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/S
> erverImplementation/Core/vtkPVSessionBase.cxx:243
> #11 0x00007f4acfea426d in pqDefaultViewBehavior::onServerCreation(pqServer*)
> (this=0x1d15b00, server=0x20b4ed0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Application
> Components/pqDefaultViewBehavior.cxx:119
> #12 0x00007f4acff4cf5c in pqDefaultViewBehavior::qt_static_metacall(QObject*,
> QM---Type <return> to continue, or q <return> to quit---
> etaObject::Call, int, void**) (_o=0x1d15b00, _c=QMetaObject::InvokeMetaMethod,
> _id=0, _a=0x7fff452a5390)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/
> ApplicationComponents/moc_pqDefaultViewBehavior.cpp:81
> #13 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int,
> void**) ()
>     at /lib64/libQt5Core.so.5
> #14 0x00007f4acf49d885 in pqServerManagerModel::serverAdded(pqServer*)
> (this=0x15e5e30, _t1=0x20b4ed0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/
> moc_pqServerManagerModel.cpp:564
> #15 0x00007f4acf4671f8 in pqServerManagerModel::onConnectionCreated(long
> long) (this=0x15e5e30, id=1)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqServ
> erManagerModel.cxx:503
> #16 0x00007f4acf49ce83 in pqServerManagerModel::qt_static_metacall(QObject*,
> QMetaObject::Call, int, void**) (_o=0x15e5e30,
> _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fff452a55e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/
> moc_pqServerManagerModel.cpp:268
> #17 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int,
> void**) ()
>     at /lib64/libQt5Core.so.5
> #18 0x00007f4acf49ebf7 in pqServerManagerObserver::connectionCreated(long
> long) (this=0x1823580, _t1=1)
> ---Type <return> to continue, or q <return> to quit---
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/
> moc_pqServerManagerObserver.cpp:278
> #19 0x00007f4acf46ad11 in pqServerManagerObserver::connectionCreated(vtkObject*,
> unsigned long, void*, void*) (this=0x1823580, callData=0x15fe1e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqServ
> erManagerObserver.cxx:110
> #20 0x00007f4acf49e604 in pqServerManagerObserver::qt_static_metacall(QObject*,
> QMetaObject::Call, int, void**) (_o=0x1823580,
> _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fff452a5830)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Qt/Core/
> moc_pqServerManagerObserver.cpp:142
> #21 0x00007f4ac48f1761 in QMetaObject::activate(QObject*, int, int,
> void**) ()
>     at /lib64/libQt5Core.so.5
> #22 0x00007f4acc2b5f34 in vtkQtConnection::EmitExecute(vtkObject*,
> unsigned long, void*, void*, vtkCommand*) (this=0x15e7f90, _t1=0x15fe1a0,
> _t2=67, _t3=0x0, _t4=0x15fe1e0, _t5=0x1614ce0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/VTK/
> GUISupport/Qt/moc_vtkQtConnection.cpp:139
> #23 0x00007f4acc2a13a6 in vtkQtConnection::Execute(vtkObject*, unsigned
> long, void*) (this=0x15e7f90, caller=0x15fe1a0, e=67, call_data=0x15fe1e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/GUISupport
> /Qt/vtkQtConnection.cxx:72
> #24 0x00007f4acc2a1346 in vtkQtConnection::DoCallback(vtkObject*,
> unsigned long,---Type <return> to continue, or q <return> to quit---
>  void*, void*) (vtk_obj=0x15fe1a0, event=67, client_data=0x15e7f90,
> call_data=0x15fe1e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/GUISupport
> /Qt/vtkQtConnection.cxx:62
> #25 0x00007f4ac5978d21 in vtkCallbackCommand::Execute(vtkObject*,
> unsigned long, void*) (this=0x1614ce0, caller=0x15fe1a0, event=67,
> callData=0x15fe1e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/
> Core/vtkCallbackCommand.cxx:42
> #26 0x00007f4ac5a80264 in vtkSubjectHelper::InvokeEvent(unsigned long,
> void*, vtkObject*) (this=0x156bcb0, event=67, callData=0x15fe1e0,
> self=0x15fe1a0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/
> Core/vtkObject.cxx:616
> #27 0x00007f4ac5a8077f in vtkObject::InvokeEvent(unsigned long, void*)
> (this=0x15fe1a0, event=67, callData=0x15fe1e0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Common/
> Core/vtkObject.cxx:785
> #28 0x00007f4acc9f4ab3 in vtkProcessModule::RegisterSession(vtkSession*)
> (this=0x15fe1a0, session=0x1d197b0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/
> ClientServerCore/Core/vtkProcessModule.cxx:378
> #29 0x00007f4acd657bf7 in vtkSMSession::ConnectToSelf() ()
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/ParaViewCore/
> ServerManager/Core/vtkSMSession.cxx:311
> ---Type <return> to continue, or q <return> to quit---
> #30 0x00007f4acf4235d6 in pqObjectBuilder::createServer(pqServerResource
> const&) (this=0x15e80e0, resource=...)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Core/pqObje
> ctBuilder.cxx:656
> #31 0x00007f4acfe5cca6 in pqAlwaysConnectedBehavior::serverCheck() (this=
>     0x1d16b30)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Application
> Components/pqAlwaysConnectedBehavior.cxx:81
> #32 0x00007f4acfe5cb26 in pqAlwaysConnectedBehavior::pqA
> lwaysConnectedBehavior(QObject*) (this=0x1d16b30, parentObject=0x1d143c0)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Application
> Components/pqAlwaysConnectedBehavior.cxx:52
> #33 0x00007f4acfeda449 in pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*,
> QObject*) (this=0x1d143c0, mainWindow=0x160b200, parentObject=0x160b200)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Qt/Application
> Components/pqParaViewBehaviors.cxx:163
> #34 0x00000000004113ca in ParaViewMainWindow::ParaViewMainWindow() (this=
>     0x160b200)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/Applications/
> ParaView/ParaViewMainWindow.cxx:258
> #35 0x000000000040f1c7 in pqparaviewInitializer::Initialize(int, char**)
> (this=0x7fff452a61c0, argc=1, argv=0x7fff452a6338)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Applicat
> ions/ParaView---Type <return> to continue, or q <return> to quit---
> /pqparaviewInitializer.cxx:122
> #36 0x000000000040eb64 in main(int, char**) (argc=1, argv=0x7fff452a6338)
>     at /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/build/Applicat
> ions/ParaView/paraview_main.cxx:121
>
> Thanks,
> MC
>
> --
> Martin Cuma
> Center for High Performance Computing
> Department of Geology and Geophysics
> University of Utah
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170720/b077b839/attachment.html>

From Amine.Aboufirass at deltares.nl  Thu Jul 20 09:03:12 2017
From: Amine.Aboufirass at deltares.nl (Amine Aboufirass)
Date: Thu, 20 Jul 2017 13:03:12 +0000
Subject: [Paraview] Using python IDLE 3.6 with VTK and paraview.simple
Message-ID: <DEA101B66315B941B487EAE03CFFF44346437FAE@V-EXC-C02.DIRECTORY.INTRA>


Dear all,

I would like to use paraview.simple with python 3.6 and IDLE. Currently when I import the library this is what I get:

>>> import paraview.simple
Error: Could not import vtkCommonComputationalGeometry
Traceback (most recent call last):
  File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\Lib\site-packages\paraview\vtk\vtkCommonCore.py", line 5, in <module>
    from .vtkCommonCorePython import *
ImportError: dynamic module does not define module export function (PyInit_vtkCommonCorePython)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<pyshell#72>", line 1, in <module>
    import paraview.simple
  File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\Lib\site-packages\paraview\simple.py", line 43, in <module>
    from paraview import servermanager
  File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\Lib\site-packages\paraview\servermanager.py", line 53, in <module>
    from paraview import vtk
  File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\Lib\site-packages\paraview\vtk\__init__.py", line 7, in <module>
    from paraview.vtk.vtkCommonCore import *
  File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\Lib\site-packages\paraview\vtk\vtkCommonCore.py", line 9, in <module>
    from vtkCommonCorePython import *
ImportError: dynamic module does not define module export function (PyInit_vtkCommonCorePython)

It appears that the module is defined but it has trouble with some of the VTK submodules. I tried to import VTK on its own but since the modules inside make use of the old print statement (no parentheses) there is not a way to do this free from error. How do I get this stuff to import properly?

Thanks,

Amine Aboufirass
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170720/3cf4465e/attachment.html>

From ben.boeckel at kitware.com  Thu Jul 20 11:00:27 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 20 Jul 2017 11:00:27 -0400
Subject: [Paraview] Using python IDLE 3.6 with VTK and paraview.simple
In-Reply-To: <DEA101B66315B941B487EAE03CFFF44346437FAE@V-EXC-C02.DIRECTORY.INTRA>
References: <DEA101B66315B941B487EAE03CFFF44346437FAE@V-EXC-C02.DIRECTORY.INTRA>
Message-ID: <20170720150027.GA30430@megas.kitware.com>

On Thu, Jul 20, 2017 at 13:03:12 +0000, Amine Aboufirass wrote:
> It appears that the module is defined but it has trouble with some of
> the VTK submodules. I tried to import VTK on its own but since the
> modules inside make use of the old print statement (no parentheses)
> there is not a way to do this free from error. How do I get this stuff
> to import properly?

The ParaView binaries only support Python2. If you want Python3 support,
you'll need to compile ParaView yourself (unfortunately, the superbuild
is not set up to do this yet, so anything in there you need will need to
be managed manually). We do test ParaView with Python3 though, so it
should work once you have a Python3-compatible build.

--Ben

From aashish.chaudhary at kitware.com  Thu Jul 20 13:43:48 2017
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Thu, 20 Jul 2017 17:43:48 +0000
Subject: [Paraview] [Non-DoD Source] Eye separation has been wrong since
 Immersive ParaView 5.2 - here's how to fix it
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91F149F0@UCOLHPUD.easf.csd.disa.mil>
References: <D572E2C6.5E36%Mark.Stock@nrel.gov>
 <10A03274360DCF47A6EE78C9952A31CA91F149F0@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <CAEw35Z9Kj89GOB5ZDERF9Nhb_3Pw5J3ngGGqog9TxmBt=wxiQg@mail.gmail.com>

Generally you want to scale objects appropriately - almost all of the
library I used / wrote do that (except paraview). If the object is too
small you will have very large eye separation and it is too big, very
small.

You want to scale object according to your screen size so that it can fit
there if placed at focal distance from the camera.

We talked about supporting auto-scaling in paraview but ran out of funding.

Let us know how should be proceed and I happy to help.

On Tue, Jul 18, 2017 at 2:59 PM Hennessey, Joseph G CTR USARMY RDECOM ARL
(US) <joseph.g.hennessey2.ctr at mail.mil> wrote:

> Mark,
>
> I have discussed the changes I made with my colleagues.
> We do not want to harm your work with the Cave,
> so we would be okay with backing out our changes.
>
> We can scale our data to be of size greater than 1
> by using the transform data inside of ParaView
> and our data will still work. My changes were only
> necessary when working with data of size less than or
> a lot less than zero.
>
> Please let me know what I can do to assist, my changes
> are found in the ParaView 5.x versions, ParaView 4.4.0
> still has your code in it without my changes for visualizing
> small data in stereo with devices such as the zSpace.
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
> Email:  joseph.g.hennessey2.ctr at mail.mil
>
>
> -----Original Message-----
> From: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> Sent: Monday, June 26, 2017 11:42 AM
> To: 'Stock, Mark' <Mark.Stock at nrel.gov>; Gena Bug via ParaView
> <paraview at paraview.org>
> Subject: RE: [Non-DoD Source] [Paraview] Eye separation has been wrong
> since
> Immersive ParaView 5.2 - here's how to fix it
>
> Hello,
>
> I am the one who requested the changes,
> they were made to correct the stereo separation with working with zSpace
> hardware
> for data that was small in size (floating point values of coordinates, >>
> 1,
> for example data that ranged from 0.0000000 to  0.0000001
> I checked its use with data across 13 orders of magnitude from data of size
> 1,000,000 to data of scale 1/1,000,000.
> I admit my fix is an approximation, but I am attempting to get a reasonable
> agreement of size with  the non stereo operation
>
>   double eyeSeparationCorrectionFactor = 10.0;
>   double shiftDistance = this->EyeSeparation / (2.0 *
> eyeSeparationCorrectionFactor);
>   if(this->Distance < 1.0)
>   {
>     shiftDistance *= this->Distance;
>   }
>
>   // Front (aka near)
>   double F = E[2] - (this->Distance + this->Thickness);//E[2] -
> 10000.0;//this->ClippingRange[1];
>   // Back (aka far)
>   double nearDistanceCorrectionFactor  = 1000.0;
>   double B = E[2] - (this->Distance / nearDistanceCorrectionFactor);//E[2]
> - .1;//this->ClippingRange[0];
>
> Without these changes with small data the stereo separation is incorrect,
> (too large)
> also small data will not even show up in the render window as the clipping
> planes will be wrong.
>
> This change
>
> "  if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) {
> normalVCVSOutput = -1.0*normalVCVSOutput; }"
>
> I did not make and do not know its purpose.
>
> I think we  need a solution that works for both caves and planar display
> hardware,
> and I think the underlying issue is that there is different render code
> being used,
> that is a subset of the full normal rendering solution, which is creating
> these issues.
> I think the correct solution is to remove  the separate render code and use
> the primary
> code for both client and server rendering of mono and stereo. I do not have
> a cave to
> test with, but I do not see why we can not find a solution that works for
> everyone.
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
> Aberdeen Proving Ground, MD 21005
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Stock,
> Mark
> Sent: Friday, June 23, 2017 5:23 PM
> To: Gena Bug via ParaView <paraview at paraview.org>
> Subject: [Non-DoD Source] [Paraview] Eye separation has been wrong since
> Immersive ParaView 5.2 - here's how to fix it
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Hello,
>
> If you're an Immersive ParaView user, you may have noticed that 5.x
> versions
> don't work as well in your CAVE. Specifically, I've noticed the following
> differences when compared with ParaView 4.4.0:
>
> 1) I can place an object in space properly but it seems to move 10x as fast
> when I move my head.
> 2) If I move the object just a little farther away from its initial
> position, it clips out (vanishes).
> 3) When I am viewing a triangle mesh, some triangles seem to flip normals
> (and get dark) when I move the object around.
>
> The first two problems are caused by a change in the VTK source code from
> March 2016 which arbitrarily multiples the eye separation distance by 10,
> and also tightens the near and far clipping planes. The third can be
> corrected by adding a single comment (which will help CAVE and Immersive
> users, but probably nobody else). Both fixes will require you to build
> ParaView from source - which you're probably doing anyway. I can't comment
> on how these changes will affect HMD VR users.
>
>
> The first and second problems are caused by a single commit to the VTK
> repository that began to appear in ParaView with version 5.2.0. The problem
> code is in VTK/Rendering/Core/vtkCamera.cxx starting at line 452 in
> versions
> 5.3 and 5.4. This problem can be fixed by replacing
>
>   double eyeSeparationCorrectionFactor = 10.0;
>   double shiftDistance = this->EyeSeparation / (2.0 *
> eyeSeparationCorrectionFactor);
>   if(this->Distance < 1.0)
>   {
>     shiftDistance *= this->Distance;
>   }
>
>
>
> with simply
>
>   double shiftDistance = this->EyeSeparation;
>
>
> The second problem (clipping planes) is just a few lines down. I fixed it
> by
> replacing
>
>   // Front (aka near)
>   double F = E[2] - (this->Distance + this->Thickness);//E[2] -
> 10000.0;//this->ClippingRange[1];
>   // Back (aka far)
>   double nearDistanceCorrectionFactor  = 1000.0;
>   double B = E[2] - (this->Distance / nearDistanceCorrectionFactor);//E[2]
> - .1;//this->ClippingRange[0];
>
>
>
> with
>
>   // Front (aka near)
>   double F = E[2] - 10000.0;//this->ClippingRange[1];
>   // Back (aka far)
>   double B = E[2] - .1;//this->ClippingRange[0];
>
>
>
> The third problem can be fixed by commenting out this line in
> VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx (around line 1198 in 5.1,
> 1416 in 5.2 to 5.4):
>
> "  if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) {
> normalVCVSOutput = -1.0*normalVCVSOutput; }"
>
>
> I hope these fixes help some of you out there get your CAVE updated to the
> latest ParaView.
>
> Mark
>
> Mark.Stock at nrel.gov
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at: Caution-
> http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170720/adccaa52/attachment.html>

From steytle1 at illinois.edu  Thu Jul 20 17:19:18 2017
From: steytle1 at illinois.edu (Steytler, Louis Louw)
Date: Thu, 20 Jul 2017 21:19:18 +0000
Subject: [Paraview] Reading files in Parallel with ParaView
Message-ID: <2F8BA25CC0B82C4DB6756F8F663E6DB35BF3F4AD@CITESMBX3.ad.uillinois.edu>

Hi All,

What is the best way to read a large dataset? I am performing parallel computations, so the mesh is broken into multiple smaller pieces, but it is also possible to re-assemble these pieces into one large piece in a post-processing step.

The results could also be stored in multiple files corresponding to different time steps, or in one big file containing all the time steps. So it is possible to decompose in space and/or time.

Does ParaView read data in parallel regardless of whether the file is decomposed in space and/or time? Would it be faster to read decomposed files vs. reading one large file?

Any ideas?

Thanks very much,

Louis Steytler
Department of Mechanical Science and Engineering
University of Illinois at Urbana-Champaign
1206 West Green Street
Urbana, Il 61801
steytle1 at illinois.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170720/bd21db87/attachment.html>

From Amine.Aboufirass at deltares.nl  Fri Jul 21 05:07:15 2017
From: Amine.Aboufirass at deltares.nl (Amine Aboufirass)
Date: Fri, 21 Jul 2017 09:07:15 +0000
Subject: [Paraview] issue from 2014 seemingly not resolved?
Message-ID: <DEA101B66315B941B487EAE03CFFF44346438164@V-EXC-C02.DIRECTORY.INTRA>

Dear all,

I would like to bring attention to the following thread (http://public.kitware.com/pipermail/paraview/2014-June/031517.html). I am experiencing the exact same problem. It seems like this error is recurrent whether the dll bin directory is included in PYTHONPATH and system PATH or not:

Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] on win32
Type "copyright", "credits" or "license()" for more information.
>>> import paraview.simple
Error: Could not import vtkCommonComputationalGeometryPython

Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    import paraview.simple
  File "C:\Program Files\ParaView 5.0.1\lib\paraview-5.0\site-packages\paraview\simple.py", line 39, in <module>
    import servermanager
  File "C:\Program Files\ParaView 5.0.1\lib\paraview-5.0\site-packages\paraview\servermanager.py", line 48, in <module>
    import paraview, re, os, os.path, new, sys, atexit, vtk
  File "C:\Program Files\ParaView 5.0.1\lib\paraview-5.0\site-packages\paraview\vtk\__init__.py", line 7, in <module>
    from vtkCommonCorePython import *
ImportError: DLL load failed: The specified module could not be found.
>>>

The link provided shows a work-around which works for me. Namely:

>>> import os
>>> os.chdir(r'C:\Program Files\ParaView 5.0.1\bin')
>>> import paraview.simple

Although this works it would be good to determine the underlying reason why the regular method does not. Again I am including the bin directory in both pythonpath and system environment path as proven by the following:

>>> string = r'C:\Program Files\ParaView 5.0.1\bin'
>>> string in os.environ["PATH"]
True
>>> string in sys.path
True

I also tried to track down the user who was facing a similar problem back in 2014 (livia.barazzetti at istb.unibe.ch) to see if she ended up figuring out the solution. Unfortunately her name is not in the mailing list anymore which to me implies she is either not a user anymore or has become so proficient that she doesn't use the mailing list anymore.

Thanks for your consideration and look forward to hearing from you.

Amine Aboufirass
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170721/2e69e8f2/attachment.html>

From ross.gardiner at ultrahaptics.com  Fri Jul 21 06:14:43 2017
From: ross.gardiner at ultrahaptics.com (Ross Gardiner)
Date: Fri, 21 Jul 2017 10:14:43 +0000
Subject: [Paraview] Opacity transfer function in pvpython
Message-ID: <73C93799-7CF6-4D39-84CD-B0E24B7EDB4B@ultrahaptics.com>

Hi,

I?m currently working on a tool that generates Python scripts which, in turn, save a ParaView state. The state can then be loaded in ParaView.

I am experiencing some issues with setting up the LUT for volume rendering of some data. (I?ve already reported one issue that I?m pretty sure is a bug at https://gitlab.kitware.com/paraview/paraview/issues/17616 )

I am able to set the color transfer function and opacity transfer function, and both appear in the UI. However, while the color transfer function works, the opacity transfer function seems to have no effect on rendering whatsoever. After loading the state in ParaView, I can set the entire opacity transfer function to zero and the renderered volume remains completely opaque.

Here?s an example of the Python code I am using:

soundfield = OpenDataFile('my_data.vti')
representation = Show(soundfield)
representation.ColorArrayName = 'ImageScalars'
representation.Representation = 'Volume'
representation.LookupTable = AssignLookupTable(soundfield.PointData['ImageScalars'], 'Cool to Warm')
representation.LookupTable.ScalarOpacityFunction = CreatePiecewiseFunction(Points=[0.0, 0.0, 0.5, 0.0, 1.0, 1.0, 0.5, 0.0])
SaveState('state.pvsm')

Is there anything special I have to do? I?ve looked over the documentation/mailing lists/ListProperties() and I can?t see anything obvious.

Thanks,
Ross


From Amine.Aboufirass at deltares.nl  Fri Jul 21 07:19:41 2017
From: Amine.Aboufirass at deltares.nl (Amine Aboufirass)
Date: Fri, 21 Jul 2017 11:19:41 +0000
Subject: [Paraview] Trying to get a Paraview API like environment
Message-ID: <DEA101B66315B941B487EAE03CFFF443464381BB@V-EXC-C02.DIRECTORY.INTRA>

Dear all,

I am trying to control Paraview application using an external python IDE (IDLE). The objective is to send commands using Paraview.simple modules from IDLE and see the changes take place in the Paraview GUI. I cannot use the python shell in Paraview because I seek to use other unrelated libraries so would prefer not to be bound to the shell in Paraview.

So far, I have succeeded in importing the Paraview modules (simple, servermanager...etc) from IDLE. I accomplished this thanks to a 2014 thread (http://public.kitware.com/pipermail/paraview/2014-June/031517.html) using the following commands in IDLE:

>>> import os
>>> os.chdir(r'C:\Program Files\ParaView 5.0.1\bin')
>>> import paraview.simple
>>> os.chdir(r'D:\TEMP\Myfolder')

I attempted some of the examples in the Paraview docs online. For instance:

>>> from paraview.simple import *
>>> cone = Cone()
>>> Show()
>>> Render()

Fortunately, this does indeed create a cone and output it to a new window (OpenGL). Unfortunately this is not what I am trying to do. I need to be able to render it in the Paraview program.

Beyond this simple example I will also eventually need to load in vtk legacy timeseries into Paraview, change some of their visualization parameters and then export several animations. It would be great if I could achieve this from a simple IDLE terminal.

Please let me know if this is even possible? If so am I on the right track? What are the options missing for me to be able to do this ?


Amine Aboufirass


DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170721/66c50ad1/attachment.html>

From rakshitdmr at gmail.com  Fri Jul 21 12:17:56 2017
From: rakshitdmr at gmail.com (Rakshit DM)
Date: Fri, 21 Jul 2017 17:17:56 +0100
Subject: [Paraview] time dependent temperature plot ??
Message-ID: <CAPca1TwyaW3JemWwnPWm6VHOcL-wtQ_52B1NGDbe0GFD1sn8=w@mail.gmail.com>

Hi all,

I am analysing heat transfer in solid bodies (walls). I used simscale for
modelling and running the simulation and I am using ParaView for the
post-processing.

I have applied a varying temperature on the surface of the wall and I used
plot over line filter to get the plot but in that, I am getting a plot of
temperature v/s distance, what I was expected was temperature v /s time. I
have tried plot global variable over time and plot selection over time I am
not getting any plots in that. I don?t know where I am going wrong with
ParaView

And if I want to see the node points number/temperature on the geometry and
to extract them where should I go ??

And when I open the ParaView application I am getting an output message
like UNABLE TO DISABLE THE ROTATION, (:0,)

So Can any one please help me with this


I have attached the case.pvd files below


thanks in advance

?
 COMPOSITE WALL 2-TRANSIENT-2-TRANSIENT STATE -R...
<https://drive.google.com/file/d/0B_sJ7o8lm_y1dU5kdWdFQUZfbEE/view?usp=drive_web>
??
 TEST WALL - HEATING INSIDE-Simulation 1-Run 3.zip
<https://drive.google.com/file/d/0B_sJ7o8lm_y1T0ZGeHE2c1FiSkU/view?usp=drive_web>
?


-- 
Thanks & Regards
Rakshit DM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170721/f953d97b/attachment.html>

From sebastien.jourdain at kitware.com  Fri Jul 21 16:34:39 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 21 Jul 2017 14:34:39 -0600
Subject: [Paraview] Fwd: ParaviewWeb OSMesa build
In-Reply-To: <CAABzCAwHZNDofXR2evMk7SsLuoqU=5Ab0ix02hpuuuihjUJiyQ@mail.gmail.com>
References: <59556572.d4931c0a.53696.5630@mx.google.com>
 <CABObKxdx+DKhjbAEp_4xW-t4dM+_Q774djaGfYM6=BhpEgTOAw@mail.gmail.com>
 <CAABzCAyV4_U=Z2QTk6gD+FQBp1qcjEUdG2-PVm0gRf3NxUXZ9g@mail.gmail.com>
 <CAABzCAytxMjadpQ+Ko8fM5Mo7kM9UbO0znv4W6uO6cqy74PDjg@mail.gmail.com>
 <CABObKxf4VpF+jpga-QVwq3TMgdqWua1nYZzNzOdYv93GLQheDA@mail.gmail.com>
 <CAABzCAwHZNDofXR2evMk7SsLuoqU=5Ab0ix02hpuuuihjUJiyQ@mail.gmail.com>
Message-ID: <CABObKxeWt2sxbcLWti+gncStJg5=yPxMf8_-0rgGnM8i=KseqA@mail.gmail.com>

Can you send me a log from a visualizer session?

On Wed, Jul 19, 2017 at 10:23 AM, Hayk Grigoryan <hayk.grigoryan.a at gmail.com
> wrote:

> No, there is not any error logs in log files, just one that I wrote I see
> in the browser console. Please find in attachments the config files.
>
> I'm using http://localhost/visualizer or http://localhost/lightviz. BTW
> lightviz is showing a black page with 2 icons in the top left, and there is
> not errors. The error appears on visualizer.
>
> Thanks,
> Hayk
>
> On Wed, Jul 19, 2017 at 6:28 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Did you get any error or feedback in the various logs? Moreover, which
>> URL did you use to connect and what launcher and apache configuration did
>> you use?
>>
>> On Wed, Jul 19, 2017 at 6:34 AM, Hayk Grigoryan <
>> hayk.grigoryan.a at gmail.com> wrote:
>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Hayk Grigoryan <hayk.grigoryan.a at gmail.com>
>>> Date: Wed, Jul 19, 2017 at 4:33 PM
>>> Subject: Re: [Paraview] ParaviewWeb OSMesa build
>>> To: Sebastien Jourdain <sebastien.jourdain at kitware.com>
>>>
>>>
>>> Dear Sebastien,
>>>
>>> Thanks for you response.
>>>
>>> I'm trying a different ways for configuring paraviewweb as a web service.
>>>
>>> Now I have Ubuntu Desktop 16.04 and followed the tutorial link
>>> https://kitware.github.io/paraviewweb/docs/ubuntu_14_04.html .
>>>
>>> Following the steps I end up with error about WebSockets -> WebSocket
>>> connect to 'ws://localhost/ws' failed.
>>>
>>> I've used Paraview 5.2 and 5.4 versions.
>>>
>>> After long hours research I didn't find any answer for me.
>>>
>>> Could you please help to understand what cause this problem: Ubuntu
>>> version, Paraview version or configurations.
>>>
>>> Thanks in advance,
>>> Hayk
>>>
>>> On Tue, Jul 4, 2017 at 1:45 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Yes, but you will need to build ParaView with either OSMesa or EGL (if
>>>> you have a compatible NVidia GPU).
>>>>
>>>> When you do so, you won't need to build the Qt UI.
>>>>
>>>> Seb
>>>>
>>>> On Thu, Jun 29, 2017 at 2:39 PM, <hayk.grigoryan.a at gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> I'm trying to build ParaViewWeb with OSMesa. I need help with my
>>>>> question.
>>>>>
>>>>>
>>>>>
>>>>> I've ubuntu 14.04 server without desktop and X. Can I install and make
>>>>> ParaViewWeb to work as a web service on my server?
>>>>>
>>>>>
>>>>>
>>>>> Thank in advance,
>>>>>
>>>>> Hayk
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170721/49f9c747/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 21 16:47:30 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 21 Jul 2017 16:47:30 -0400
Subject: [Paraview] time dependent temperature plot ??
In-Reply-To: <CAPca1TwyaW3JemWwnPWm6VHOcL-wtQ_52B1NGDbe0GFD1sn8=w@mail.gmail.com>
References: <CAPca1TwyaW3JemWwnPWm6VHOcL-wtQ_52B1NGDbe0GFD1sn8=w@mail.gmail.com>
Message-ID: <CADHSJjD5Uo5xL-m1mfZX0jHRvnrs1Z3aszJP23SpUszxEhsNXw@mail.gmail.com>

> I am getting a plot of temperature v/s distance, what I was expected was
> temperature v /s time.
>

Just focusing on this question to begin with, when you say you want to plot
temperature over time. Temperature of what? Each of the case.pvd seems to
have multiple blocks of data. Do you want to plot the average temperature
of the whole dataset or a particular block? or max temperature at each
timestep or something else?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170721/ce9b133e/attachment.html>

From rccm.kyoshimi at gmail.com  Sat Jul 22 06:12:36 2017
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Sat, 22 Jul 2017 19:12:36 +0900
Subject: [Paraview] Opacity transfer function in pvpython
In-Reply-To: <73C93799-7CF6-4D39-84CD-B0E24B7EDB4B@ultrahaptics.com>
References: <73C93799-7CF6-4D39-84CD-B0E24B7EDB4B@ultrahaptics.com>
Message-ID: <CAHDyfPDiS-MEwmgjG8Z-HCBqr+8W9ErhMYTrbD6N6R7CfmUgkw@mail.gmail.com>

Hi Ross,

Specifying representation.ScalarOpacityFunction via the same piecewise
function may be also needed:
representation.ScalarOpacityFunction =
CreatePiecewiseFunction(Points=[0.0, 0.0, 0.5, 0.0, 1.0, 1.0, 0.5,
0.0])

Thanks,
yoshimi

2017-07-21 19:14 GMT+09:00 Ross Gardiner <ross.gardiner at ultrahaptics.com>:
> Hi,
>
> I?m currently working on a tool that generates Python scripts which, in turn, save a ParaView state. The state can then be loaded in ParaView.
>
> I am experiencing some issues with setting up the LUT for volume rendering of some data. (I?ve already reported one issue that I?m pretty sure is a bug at https://gitlab.kitware.com/paraview/paraview/issues/17616 )
>
> I am able to set the color transfer function and opacity transfer function, and both appear in the UI. However, while the color transfer function works, the opacity transfer function seems to have no effect on rendering whatsoever. After loading the state in ParaView, I can set the entire opacity transfer function to zero and the renderered volume remains completely opaque.
>
> Here?s an example of the Python code I am using:
>
> soundfield = OpenDataFile('my_data.vti')
> representation = Show(soundfield)
> representation.ColorArrayName = 'ImageScalars'
> representation.Representation = 'Volume'
> representation.LookupTable = AssignLookupTable(soundfield.PointData['ImageScalars'], 'Cool to Warm')
> representation.LookupTable.ScalarOpacityFunction = CreatePiecewiseFunction(Points=[0.0, 0.0, 0.5, 0.0, 1.0, 1.0, 0.5, 0.0])
> SaveState('state.pvsm')
>
> Is there anything special I have to do? I?ve looked over the documentation/mailing lists/ListProperties() and I can?t see anything obvious.
>
> Thanks,
> Ross
>
> _______________________________________________
> 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

From stoltz.c at pg.com  Sat Jul 22 12:53:41 2017
From: stoltz.c at pg.com (Stoltz, Christopher)
Date: Sat, 22 Jul 2017 16:53:41 +0000
Subject: [Paraview] ParaView 5.4.0 Build Error
Message-ID: <6A422BABAB959549A1E860E170B2C499D1C918CA@GADC-EMB002.na.pg.com>

Hi,

I am trying to build ParaView 5.4.0 from source so I can use the Superquadric plugin and am running into a problem that appears to be related to Qt and ffmpeg.  At the end of the log output from 'Make', I see the following:

[100%] Linking CXX executable ../bin/pvrenderserver
/usr/bin/ld: warning: libicui18n.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libicuuc.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libicudata.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libswresample.so.2, needed by ~/ffmpeg_3.3.2/lib/libavcodec.so.57, not found (try using -rpath or -rpath-link)
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_alloc at LIBSWRESAMPLE_2'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_getAlias_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `uenum_next_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `u_strToUpper_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_fromUnicode_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `uenum_close_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_openTimeZoneIDEnumeration_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_getDSTSavings_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_setMillis_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucol_getSortKey_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_get_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_compareNames_56'
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_free at LIBSWRESAMPLE_2'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucol_setAttribute_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_open_56'
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_is_initialized at LIBSWRESAMPLE_2'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_openTimeZones_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_getAvailableName_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_close_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_getDefaultName_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_getDefaultTimeZone_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucol_strcoll_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_close_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_countAvailable_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `u_strToLower_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_getStandardName_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_getTimeZoneDisplayName_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_setSubstChars_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `u_errorName_56'
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_close at LIBSWRESAMPLE_2'
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_init at LIBSWRESAMPLE_2'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucol_close_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucol_open_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_clone_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_open_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_openCountryTimeZones_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_countAliases_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_inDaylightTime_56'
~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to `swr_convert at LIBSWRESAMPLE_2'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_toUnicode_56'
~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucnv_getMaxCharSize_56'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/pvrenderserver] Error 1
make[1]: *** [CommandLineExecutables/CMakeFiles/pvrenderserver.dir/all] Error 2
make: *** [all] Error 2


Both Qt and ffmpeg seemed to have installed correctly, and when I set up the configuration for ParaView, I didn't see any issues related to either one.  Any thoughts on how I resolve this?  Apologies as I am not well-versed at building software in Linux.

Thanks,
Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170722/85e4be39/attachment.html>

From tengli2 at illinois.edu  Sun Jul 23 22:41:03 2017
From: tengli2 at illinois.edu (Li, Teng)
Date: Mon, 24 Jul 2017 02:41:03 +0000
Subject: [Paraview] Point data to 2d plane data
Message-ID: <81A18720EB4BBA489B6552676D14533C67BE25EC@chimbx4.ad.uillinois.edu>

Dear Paraview developers,

I have a question about how to convert point data (vtk file) to 2d plane data. Actually, originally, I was working with vtk file. Then I use the extract selection to select some cells in the original model. In order to process the data of the selected cells, I save the data as the csv file. Then I use Matlab to do some calculation on the data in the csv file. After that, I open the modified csv file by using Paraview directly. And now, I only have spreadsheet view. After searching some online information, I use TabletoPoint to convert the data to point data. However, I still want to view them as the 2d cell. So I use point interpolation to try to convert the points data to 2d plane cell data. However, It doesn't work.

So my question is, how to show the data value in the space between different 2d points data by using point interpolation? Or is there any way that I can process the original data in the 2d cell plane mode without saving it as the csv file?

Best,
Teng Li


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: tengli2 at illinois.edu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/d79e5571/attachment.html>

From ross.gardiner at ultrahaptics.com  Mon Jul 24 07:01:38 2017
From: ross.gardiner at ultrahaptics.com (Ross Gardiner)
Date: Mon, 24 Jul 2017 11:01:38 +0000
Subject: [Paraview] Opacity transfer function in pvpython
In-Reply-To: <CAHDyfPDiS-MEwmgjG8Z-HCBqr+8W9ErhMYTrbD6N6R7CfmUgkw@mail.gmail.com>
References: <73C93799-7CF6-4D39-84CD-B0E24B7EDB4B@ultrahaptics.com>
 <CAHDyfPDiS-MEwmgjG8Z-HCBqr+8W9ErhMYTrbD6N6R7CfmUgkw@mail.gmail.com>
Message-ID: <B63D3DF1-1D8E-4126-AF26-E1C724D66552@ultrahaptics.com>

Hi yoshimi,

Thanks ? your suggestion helped me find a solution:


opacity_map = CreatePiecewiseFunction(Points=[44.0, 0.0, 0.5, 0.0, 132.0, 0.0, 0.5, 0.0, 154.0, 1.0, 0.5, 0.0]) 
representation.LookupTable.ScalarOpacityFunction = opacity_map
representation.ScalarOpacityFunction = opacity_map

I believe what?s going on here is that the LookupTable editor in ParaView gets its data from LookupTable.ScalarOpacityFunction, while the renderer gets it from representation.ScalarOpacityFunction. If they?re both initialised separately, updating the opacity mapping in the colour map editor does not cause the rendering to update. If they both reference the same object, it works as expected.

- Ross

On 22/07/2017, 11:12, "kenichiro yoshimi" <rccm.kyoshimi at gmail.com> wrote:

    c


From chuck.atkins at kitware.com  Mon Jul 24 09:34:40 2017
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Mon, 24 Jul 2017 09:34:40 -0400
Subject: [Paraview] Reading files in Parallel with ParaView
In-Reply-To: <2F8BA25CC0B82C4DB6756F8F663E6DB35BF3F4AD@CITESMBX3.ad.uillinois.edu>
References: <2F8BA25CC0B82C4DB6756F8F663E6DB35BF3F4AD@CITESMBX3.ad.uillinois.edu>
Message-ID: <CAOXZzG5S6Wodu-d-aUA=3ZMZNqWgbVhosCJGJBbjqDjG9+naRg@mail.gmail.com>

Hi Louis,

Does ParaView read data in parallel regardless of whether the file is
> decomposed in space and/or time?
>

Space, yes.  Time, not really, at least not without writing a custom reader.



> Would it be faster to read decomposed files vs. reading one large file?
>

This is something that will be dependent on the file format yuou're using.
It will most certainly be faster to read the data in parallel, spatially
decomposed, and most of the parallel readers support an N -> M IO mapping,
that is, using a different number of readers than there are spatial
partitions.  As to using one big file or not, well, some parallel file
formats support it, some dont.  Just make sure you use a file format that
supports the spatial decomposition, whether thats as one file per
partition-timestep, one file per-timestep with multiple partitions per
file, or everything in one file with multiple partitions adn timesteps per
file.  Your bottlenext in IO will likely be the write time anyways and as
long as the file format your using supports parallel reads then how that's
laid out, whether in a single file or multiple files, will probably not
have a significant impact.


----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/7e2feaed/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul 24 11:30:15 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 24 Jul 2017 11:30:15 -0400
Subject: [Paraview] ParaView 5.4.0 Build Error
In-Reply-To: <6A422BABAB959549A1E860E170B2C499D1C918CA@GADC-EMB002.na.pg.com>
References: <6A422BABAB959549A1E860E170B2C499D1C918CA@GADC-EMB002.na.pg.com>
Message-ID: <CADHSJjA6D2ymazWe3-TdjoCQ8DWKHTStXkLJmjBaQk+cVXhq9w@mail.gmail.com>

What if you try this:

> export
LD_LIBRARY_PATH=~/Qt5.6.2/5.6/gcc_64/lib/:~/ffmpeg_3.3.2/lib/:$LD_LIBRARY_PATH
> make

Does that work?

Utkarsh

On Sat, Jul 22, 2017 at 12:53 PM, Stoltz, Christopher <stoltz.c at pg.com>
wrote:

> Hi,
>
>
>
> I am trying to build ParaView 5.4.0 from source so I can use the
> Superquadric plugin and am running into a problem that appears to be
> related to Qt and ffmpeg.  At the end of the log output from ?Make?, I see
> the following:
>
>
>
> [100%] Linking CXX executable ../bin/pvrenderserver
>
> /usr/bin/ld: warning: libicui18n.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5,
> not found (try using -rpath or -rpath-link)
>
> /usr/bin/ld: warning: libicuuc.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5,
> not found (try using -rpath or -rpath-link)
>
> /usr/bin/ld: warning: libicudata.so.56, needed by ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5,
> not found (try using -rpath or -rpath-link)
>
> /usr/bin/ld: warning: libswresample.so.2, needed by
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57, not found (try using -rpath or
> -rpath-link)
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_alloc at LIBSWRESAMPLE_2'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_getAlias_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `uenum_next_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `u_strToUpper_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_fromUnicode_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `uenum_close_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to `ucal_
> openTimeZoneIDEnumeration_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_getDSTSavings_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_setMillis_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucol_getSortKey_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_get_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_compareNames_56'
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_free at LIBSWRESAMPLE_2'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucol_setAttribute_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_open_56'
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_is_initialized at LIBSWRESAMPLE_2'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_openTimeZones_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_getAvailableName_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_close_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_getDefaultName_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_getDefaultTimeZone_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucol_strcoll_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_close_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_countAvailable_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `u_strToLower_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_getStandardName_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_getTimeZoneDisplayName_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_setSubstChars_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `u_errorName_56'
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_close at LIBSWRESAMPLE_2'
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_init at LIBSWRESAMPLE_2'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucol_close_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucol_open_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_clone_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_open_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_openCountryTimeZones_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_countAliases_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucal_inDaylightTime_56'
>
> ~/ffmpeg_3.3.2/lib/libavcodec.so.57: undefined reference to
> `swr_convert at LIBSWRESAMPLE_2'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_toUnicode_56'
>
> ~/Qt5.6.2/5.6/gcc_64/lib/libQt5Core.so.5: undefined reference to
> `ucnv_getMaxCharSize_56'
>
> collect2: error: ld returned 1 exit status
>
> make[2]: *** [bin/pvrenderserver] Error 1
>
> make[1]: *** [CommandLineExecutables/CMakeFiles/pvrenderserver.dir/all]
> Error 2
>
> make: *** [all] Error 2
>
>
>
>
>
> Both Qt and ffmpeg seemed to have installed correctly, and when I set up
> the configuration for ParaView, I didn?t see any issues related to either
> one.  Any thoughts on how I resolve this?  Apologies as I am not
> well-versed at building software in Linux.
>
>
>
> Thanks,
>
> Chris
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/12f2036d/attachment.html>

From ross.gardiner at ultrahaptics.com  Mon Jul 24 11:48:23 2017
From: ross.gardiner at ultrahaptics.com (Ross Gardiner)
Date: Mon, 24 Jul 2017 15:48:23 +0000
Subject: [Paraview] Opacity transfer function in pvpython
In-Reply-To: <B63D3DF1-1D8E-4126-AF26-E1C724D66552@ultrahaptics.com>
References: <73C93799-7CF6-4D39-84CD-B0E24B7EDB4B@ultrahaptics.com>
 <CAHDyfPDiS-MEwmgjG8Z-HCBqr+8W9ErhMYTrbD6N6R7CfmUgkw@mail.gmail.com>
 <B63D3DF1-1D8E-4126-AF26-E1C724D66552@ultrahaptics.com>
Message-ID: <26016603-DE1D-454B-B7C7-D961CED4DCBA@ultrahaptics.com>

In case anyone finds this useful, I also found a solution to a related problem.

Once I extended the previous code to import multiple VTIs, editing the colour/opacity mapping broke again. I could only get it to affect either one of the imageDatas, or all of them simultaneously.

I eventually discovered that this was due to the default name of the scalar points in imageDatas being hardcoded to ?ImagesScalars? in VTK. ParaView apparently assumes that they should all have the same colour/opacity maps as a result. I just added 

imageData->GetPointData()->GetScalars()->SetName(?ImageScalars? + std::to_string(index)).c_str());

to my export code, which seems to have fixed it.

- Ross

On 24/07/2017, 12:01, "Ross Gardiner" <ross.gardiner at ultrahaptics.com> wrote:

    Hi yoshimi,
    
    Thanks ? your suggestion helped me find a solution:
    
    
    opacity_map = CreatePiecewiseFunction(Points=[44.0, 0.0, 0.5, 0.0, 132.0, 0.0, 0.5, 0.0, 154.0, 1.0, 0.5, 0.0]) 
    representation.LookupTable.ScalarOpacityFunction = opacity_map
    representation.ScalarOpacityFunction = opacity_map
    
    I believe what?s going on here is that the LookupTable editor in ParaView gets its data from LookupTable.ScalarOpacityFunction, while the renderer gets it from representation.ScalarOpacityFunction. If they?re both initialised separately, updating the opacity mapping in the colour map editor does not cause the rendering to update. If they both reference the same object, it works as expected.
    
    - Ross
    
    On 22/07/2017, 11:12, "kenichiro yoshimi" <rccm.kyoshimi at gmail.com> wrote:
    
        c
    
    


From mbahameish at gmail.com  Mon Jul 24 13:27:57 2017
From: mbahameish at gmail.com (Mariam)
Date: Mon, 24 Jul 2017 18:27:57 +0100
Subject: [Paraview] MPI on multiple nodes
Message-ID: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>

Hi, 

I would like to ask about running pvserver in parallel with MPI on multiple hosts. Is that possible?

 

The following commands were tested successfully:

1)       Running MPI on localhost:

mpiexec ?n M localhost pvserver

2)       Running MPI on remotehost:

mpiexec ?host remotehost ?n M pvserver

 

But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver

I run the following to test MPI on multiple hosts and it worked: mpiexec ?hosts 2 localhost 1 remotehost 1 hostname

 

Is there any pre-configuration that should be done to pvserver? I want the clients to connect to the server (master server), and the jobs are distributed across multiple nodes.

 

Regards,

Mariam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/fbf651b2/attachment.html>

From leonardopessanha74 at gmail.com  Mon Jul 24 15:28:34 2017
From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=)
Date: Mon, 24 Jul 2017 16:28:34 -0300
Subject: [Paraview] Running a simple example using ParaviewWeb
Message-ID: <CAE=GJrbQf9PW9Jz8nn3zufLvDj0BCzH2qgC-a3zV52CnHOAheg@mail.gmail.com>

Hi!

I would like to know the steps in order to run simple example like the
following one:

https://kitware.github.io/paraviewweb/examples/Composite/index.html

It doesn't need to be a really elaborated tutorial, but a simple one with
the main things.
I have little to no background in web development.

What I managed to do so far was to create my own project and add
paraviewweb to it like its described in
https://kitware.github.io/paraviewweb/docs/setup.html .

I don't know what to do next but I believe that a great start would be to
know where to put the source code in the example and how to run it.

Thanks in advance,

Leonardo Pessanha
Laboratory of Computational Methods in Engineering
Federal University of Rio de Janeiro - COPPE
Rio de Janeiro, RJ, Brasil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/04729dd5/attachment.html>

From sebastien.jourdain at kitware.com  Mon Jul 24 16:21:22 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 24 Jul 2017 14:21:22 -0600
Subject: [Paraview] Running a simple example using ParaviewWeb
In-Reply-To: <CAE=GJrbQf9PW9Jz8nn3zufLvDj0BCzH2qgC-a3zV52CnHOAheg@mail.gmail.com>
References: <CAE=GJrbQf9PW9Jz8nn3zufLvDj0BCzH2qgC-a3zV52CnHOAheg@mail.gmail.com>
Message-ID: <CABObKxdVyzrp3cgC8oWuGkX2RQqQFMD320F-+gzNRUY6f86DYA@mail.gmail.com>

Based on the path given in the setup guide, you should copy the example you
want to reproduce inside ${ROOT}/src/* where the main example file should
be named index.js.

Then you should be able to build your example using the npm command: "npm
run build".

Maybe the vtk.js explanation might be easier to follow (
https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html),
but the concept is exactly the same.
As it is picking the example available here
https://kitware.github.io/vtk-js/examples/Cone.html |
https://github.com/Kitware/vtk-js/tree/master/Examples/WebGL/Cone
and making a standalone application from it.

Just be aware that vtk.js is using webpack2 which is not the case for
ParaViewWeb.

Hope that helps,

Seb


On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha <leonardopessanha74 at gmail.com>
wrote:

> Hi!
>
> I would like to know the steps in order to run simple example like the
> following one:
>
> https://kitware.github.io/paraviewweb/examples/Composite/index.html
>
> It doesn't need to be a really elaborated tutorial, but a simple one with
> the main things.
> I have little to no background in web development.
>
> What I managed to do so far was to create my own project and add
> paraviewweb to it like its described in https://kitware.github.io/para
> viewweb/docs/setup.html .
>
> I don't know what to do next but I believe that a great start would be to
> know where to put the source code in the example and how to run it.
>
> Thanks in advance,
>
> Leonardo Pessanha
> Laboratory of Computational Methods in Engineering
> Federal University of Rio de Janeiro - COPPE
> Rio de Janeiro, RJ, Brasil
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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
>
>

On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha <leonardopessanha74 at gmail.com>
wrote:

> Hi!
>
> I would like to know the steps in order to run simple example like the
> following one:
>
> https://kitware.github.io/paraviewweb/examples/Composite/index.html
>
> It doesn't need to be a really elaborated tutorial, but a simple one with
> the main things.
> I have little to no background in web development.
>
> What I managed to do so far was to create my own project and add
> paraviewweb to it like its described in https://kitware.github.io/
> paraviewweb/docs/setup.html .
>
> I don't know what to do next but I believe that a great start would be to
> know where to put the source code in the example and how to run it.
>
> Thanks in advance,
>
> Leonardo Pessanha
> Laboratory of Computational Methods in Engineering
> Federal University of Rio de Janeiro - COPPE
> Rio de Janeiro, RJ, Brasil
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/49aeb1f0/attachment.html>

From dennis_conklin at goodyear.com  Mon Jul 24 16:34:11 2017
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Mon, 24 Jul 2017 20:34:11 +0000
Subject: [Paraview] Excel Pivot Table like functionality
Message-ID: <SN2PR0701MB7847F8F480ACAF325FB09799FBB0@SN2PR0701MB784.namprd07.prod.outlook.com>

All,

So, I have a multi-block dataset (Exodus).   Within each block, I have sets of 360 elements which have a common index.   So, in Block 1, elements 0-359 have a cell variable called N_RING, which is 1.    Elements 360-719, have N_RING=2, etc.

What I really want is the ability to operate on these sets.   Imagine I have an element variable called Ying, which is different for each element in the model.  I would like every element with N_RING=1 to have an element variable of Ying_max assigned, which is the maximum value of Ying for any element with N_RING=1.    So, for example,  elements 0-359 would be assigned a value of Ying_max which is the maximum value of Ying in any of elements 0-359.   Elements 360-719 would be assigned a value of Ying_max which is the maximum value for any element with N_RING=2.    I would ideally also like to get min and average.

Is there any way to get max/min/average of a group consisting of a cell variable index?  - and to assign the output as element variables so I can color by?

Thanks for any hints.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/d244c077/attachment.html>

From joseph.g.hennessey2.ctr at mail.mil  Mon Jul 24 17:18:33 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Mon, 24 Jul 2017 21:18:33 +0000
Subject: [Paraview] Monitoring the progress of a paraview filter
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91F2EDF5@UCOLHPUD.easf.csd.disa.mil>

Hello,

I am trying to monitor the progress of a paraview filter (contour)
on rather large data, so that I could  predict when it will finish.
Is there a recommended way to do this? I am running using
42 paraview servers and I cannot find an easy way of estimating
the filter percent of progress or expected completion time.

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170724/6293ff8a/attachment.bin>

From 253295860 at qq.com  Tue Jul 25 07:17:47 2017
From: 253295860 at qq.com (=?ISO-8859-1?B?RGF2aWQ=?=)
Date: Tue, 25 Jul 2017 19:17:47 +0800
Subject: [Paraview] Multi-RenderView in tiled-display
Message-ID: <tencent_5790574211C269880456095E@qq.com>

Hello,everyone.


When I use the tiled-display mode with one RenderView, the image can be correctly displayed.


But if I open another horizontal or vertical RenderView, the result will go wrong.


For instance, one of these tiles will be invisible. And the image's sequence is incorrect,and we can only get two fragmentary images.


Shall we reconfigure our MPI machinefile?


David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/bf6e783a/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 25 09:29:35 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 25 Jul 2017 09:29:35 -0400
Subject: [Paraview] Multi-RenderView in tiled-display
In-Reply-To: <tencent_5790574211C269880456095E@qq.com>
References: <tencent_5790574211C269880456095E@qq.com>
Message-ID: <CADHSJjDY7SHdKWOyEF5vsgj2wZ=FO1=8rwwC=xj=K2sCJeJR2Q@mail.gmail.com>

David,

This is indeed a bug (
https://gitlab.kitware.com/paraview/paraview/issues/17611). I believe the
bug was introduced in 5.0.

Utkarsh

On Tue, Jul 25, 2017 at 7:17 AM, David <253295860 at qq.com> wrote:

> Hello,everyone.
>
> When I use the tiled-display mode with one RenderView, the image can be
> correctly displayed.
>
> But if I open another horizontal or vertical RenderView, the result will
> go wrong.
>
> For instance, one of these tiles will be invisible. And the image's
> sequence is incorrect,and we can only get two fragmentary images.
>
> Shall we reconfigure our MPI machinefile?
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/97f1a1b8/attachment.html>

From jkulesza at umich.edu  Tue Jul 25 12:28:50 2017
From: jkulesza at umich.edu (Joel Kulesza)
Date: Tue, 25 Jul 2017 10:28:50 -0600
Subject: [Paraview] ParaView 5.4.0 Volume Rendering Inquiry
Message-ID: <CAAGOGw9TH--UXetQpbVUoa9eKKoNB6zfiOsdgN0kK7av-YVNkQ@mail.gmail.com>

Colleagues:

Has anyone else had problems rendering with "Volume" representation with
the as-distributed ParaView 5.4.0 (on OS X 10.11.6)?  When I select that
representation and "Yes" to the box regarding possibly taking a while, I
have only a white/blank Render View.  This is the case regardless of
coloring, colormap, or lighting options. Sometimes if I rotate the view,
I'll see a pseudo-surface representation, but when I stop I return to a
fully white render view.

In 5.4.0, I create the Volume by first Tetrahedraliz'ing my data set and
then selecting Volume representation.  Conversely, if I load the same data
in 5.2.0 and select Volume directly, it plots as I would expect.  If I try
to do the same in 5.3.0, it hangs on the render (status bar at the bottom
gets ~80% of the way and doesn't appear to proceed further).

Note that if I plot the same data in VisIt, it shows a Volume as I would
expect and quickly enough that I don't believe impatience to be my issue
(the data set is relatively small).

Any thoughts are appreciated.

Please contact me with any comments, questions, or concerns.

Thank you,
Joel

Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher
 University of Michigan, College of EngineeringNuclear Engineering &
Radiological Sciences Dept.2355 Bonisteel Boulevard
Ann Arbor, MI 48109-2104, USAMobile:  +1 (734) 223-7312Email:
jkulesza at umich.eduHome Page:  http://www.engin.umich.edu/ners/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/91fb289c/attachment.html>

From Patrick.Begou at legi.grenoble-inp.fr  Tue Jul 25 12:45:23 2017
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Tue, 25 Jul 2017 18:45:23 +0200
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
Message-ID: <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>

I think the syntax for mpiexec is:

mpiexec -np 8 --host host_one,host_two pvserver

This would launch 4 occurences of pvserver on host_one and 4 on host_two.

1) first check mpi is running:

mpiexec -np 2 --host host_one,host_two hostname

This should print the name of the 2 hosts.

If it does not works check you can ssh from one host to the other without password.

2) You need the same paraview/pvserver install on the two hosts in the same 
location (not imposed but it is easier to launch)

3) May be use reverse connection from the parallel pvserver to the paraview 
client when you launch pvserver

Patrick


Mariam wrote:
>
> Hi,
>
> I would like to ask about running pvserver in parallel with MPI on multiple 
> hosts. Is that possible?
>
> The following commands were tested successfully:
>
> 1)Running MPI on localhost:
>
> mpiexec ?n M localhost pvserver
>
> 2)Running MPI on remotehost:
>
> mpiexec ?host remotehost ?n M pvserver
>
> But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver
>
> I run the following to test MPI on multiple hosts and it worked: mpiexec 
> ?hosts 2 localhost 1 remotehost 1 hostname
>
> Is there any pre-configuration that should be done to pvserver? I want the 
> clients to connect to the server (master server), and the jobs are distributed 
> across multiple nodes.
>
> Regards,
>
> Mariam
>
>
>
> _______________________________________________
> 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


-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/e9c5f5f7/attachment.html>

From cory.quammen at kitware.com  Tue Jul 25 14:24:22 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 25 Jul 2017 14:24:22 -0400
Subject: [Paraview] ParaView 5.4.0 Volume Rendering Inquiry
In-Reply-To: <CAAGOGw9TH--UXetQpbVUoa9eKKoNB6zfiOsdgN0kK7av-YVNkQ@mail.gmail.com>
References: <CAAGOGw9TH--UXetQpbVUoa9eKKoNB6zfiOsdgN0kK7av-YVNkQ@mail.gmail.com>
Message-ID: <CAB5Fpx6aGuaTV44mDz=AS6Np1W=58n-cbFypKc_ZTOELo5jPUg@mail.gmail.com>

Joel,

This is a known issue that we have not yet resolved:
https://gitlab.kitware.com/paraview/paraview/issues/17303

As a workaround, you can try a different volume rendering algorithm (Select
Mapper property in the Properties panel) such as "Z Sweep", "Bunyk ray
cast", or "Resample to Image".

HTH,
Cory

On Tue, Jul 25, 2017 at 12:28 PM, Joel Kulesza <jkulesza at umich.edu> wrote:

> Colleagues:
>
> Has anyone else had problems rendering with "Volume" representation with
> the as-distributed ParaView 5.4.0 (on OS X 10.11.6)?  When I select that
> representation and "Yes" to the box regarding possibly taking a while, I
> have only a white/blank Render View.  This is the case regardless of
> coloring, colormap, or lighting options. Sometimes if I rotate the view,
> I'll see a pseudo-surface representation, but when I stop I return to a
> fully white render view.
>
> In 5.4.0, I create the Volume by first Tetrahedraliz'ing my data set and
> then selecting Volume representation.  Conversely, if I load the same data
> in 5.2.0 and select Volume directly, it plots as I would expect.  If I try
> to do the same in 5.3.0, it hangs on the render (status bar at the bottom
> gets ~80% of the way and doesn't appear to proceed further).
>
> Note that if I plot the same data in VisIt, it shows a Volume as I would
> expect and quickly enough that I don't believe impatience to be my issue
> (the data set is relatively small).
>
> Any thoughts are appreciated.
>
> Please contact me with any comments, questions, or concerns.
>
> Thank you,
> Joel
>
> Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher
>  University of Michigan, College of EngineeringNuclear Engineering &
> Radiological Sciences Dept.2355 Bonisteel Boulevard
> Ann Arbor, MI 48109-2104, USAMobile:  +1 (734) 223-7312 <(734)%20223-7312>Email:
>  jkulesza at umich.eduHome Page:  http://www.engin.umich.edu/ners/
>
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/7a70290a/attachment.html>

From jkulesza at umich.edu  Tue Jul 25 15:05:47 2017
From: jkulesza at umich.edu (Joel Kulesza)
Date: Tue, 25 Jul 2017 13:05:47 -0600
Subject: [Paraview] ParaView 5.4.0 Volume Rendering Inquiry
In-Reply-To: <CAB5Fpx6aGuaTV44mDz=AS6Np1W=58n-cbFypKc_ZTOELo5jPUg@mail.gmail.com>
References: <CAAGOGw9TH--UXetQpbVUoa9eKKoNB6zfiOsdgN0kK7av-YVNkQ@mail.gmail.com>
 <CAB5Fpx6aGuaTV44mDz=AS6Np1W=58n-cbFypKc_ZTOELo5jPUg@mail.gmail.com>
Message-ID: <CAAGOGw879yyY3grMAwQ_20eewc=u3_ntkY_Rs16AqzYNaBGjkw@mail.gmail.com>

Cory,

Excellent, thanks, the workarounds got me going.  Sorry I didn't think to
search the tickets.

- Joel

On Tue, Jul 25, 2017 at 12:24 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Joel,
>
> This is a known issue that we have not yet resolved: https://gitlab.
> kitware.com/paraview/paraview/issues/17303
>
> As a workaround, you can try a different volume rendering algorithm
> (Select Mapper property in the Properties panel) such as "Z Sweep", "Bunyk
> ray cast", or "Resample to Image".
>
> HTH,
> Cory
>
> On Tue, Jul 25, 2017 at 12:28 PM, Joel Kulesza <jkulesza at umich.edu> wrote:
>
>> Colleagues:
>>
>> Has anyone else had problems rendering with "Volume" representation with
>> the as-distributed ParaView 5.4.0 (on OS X 10.11.6)?  When I select that
>> representation and "Yes" to the box regarding possibly taking a while, I
>> have only a white/blank Render View.  This is the case regardless of
>> coloring, colormap, or lighting options. Sometimes if I rotate the view,
>> I'll see a pseudo-surface representation, but when I stop I return to a
>> fully white render view.
>>
>> In 5.4.0, I create the Volume by first Tetrahedraliz'ing my data set and
>> then selecting Volume representation.  Conversely, if I load the same data
>> in 5.2.0 and select Volume directly, it plots as I would expect.  If I try
>> to do the same in 5.3.0, it hangs on the render (status bar at the bottom
>> gets ~80% of the way and doesn't appear to proceed further).
>>
>> Note that if I plot the same data in VisIt, it shows a Volume as I would
>> expect and quickly enough that I don't believe impatience to be my issue
>> (the data set is relatively small).
>>
>> Any thoughts are appreciated.
>>
>> Please contact me with any comments, questions, or concerns.
>>
>> Thank you,
>> Joel
>>
>> Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher
>>  University of Michigan, College of EngineeringNuclear Engineering &
>> Radiological Sciences Dept.2355 Bonisteel Boulevard
>> Ann Arbor, MI 48109-2104, USAMobile:  +1 (734) 223-7312
>> <(734)%20223-7312>Email:  jkulesza at umich.eduHome Page:
>> http://www.engin.umich.edu/ners/
>>
>>
>> _______________________________________________
>> 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&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/76ff673b/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 25 17:51:31 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 25 Jul 2017 17:51:31 -0400
Subject: [Paraview] Monitoring the progress of a paraview filter
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91F2EDF5@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91F2EDF5@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <CADHSJjAjZ-piOJXt1T4OA+ehnobA-dwdRPMY29DR1Z_7x6xeow@mail.gmail.com>

Joe,

I am afraid there's no easy answer for this. In fact, in ParaView, we don't
collect progress from ranks other than the root.

Utkarsh

On Mon, Jul 24, 2017 at 5:18 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL
(US) <joseph.g.hennessey2.ctr at mail.mil> wrote:

> Hello,
>
> I am trying to monitor the progress of a paraview filter (contour)
> on rather large data, so that I could  predict when it will finish.
> Is there a recommended way to do this? I am running using
> 42 paraview servers and I cannot find an easy way of estimating
> the filter percent of progress or expected completion time.
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
> Aberdeen Proving Ground, MD 21005
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170725/3f579f35/attachment.html>

From tengli2 at illinois.edu  Wed Jul 26 00:22:56 2017
From: tengli2 at illinois.edu (Li, Teng)
Date: Wed, 26 Jul 2017 04:22:56 +0000
Subject: [Paraview] Point data to 2d plane data
Message-ID: <81A18720EB4BBA489B6552676D14533C67BE2E13@chimbx4.ad.uillinois.edu>

Dear Paraview developers,

I have a question about how to convert point data (vtk file) to 2d plane data. Actually, originally, I was working with vtk file. Then I use the extract selection to select some cells in the original model. In order to process the data of the selected cells, I save the data as the csv file. Then I use Matlab to do some calculation on the data in the csv file. After that, I open the modified csv file by using Paraview directly. And now, I can only see this csv file in spreadsheet view. After searching some online information, I use TabletoPoint to convert the data to point data. However, I still want to view them as the 2d cell. So I use point interpolation to try to convert the points data to 2d plane cell data. However, It doesn't work.

So my question is, how to show the data value in the space between different 2d points data by using point interpolation? Or is there any way that I can process the 2d cell plane data without saving it as the csv file?

Best,
Teng Li


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: tengli2 at illinois.edu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/ba250081/attachment.html>

From yzhzhang at ipe.ac.cn  Wed Jul 26 03:57:44 2017
From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=)
Date: Wed, 26 Jul 2017 15:57:44 +0800 (GMT+08:00)
Subject: [Paraview] Can I use paraview to visualize molecule dataset?
Message-ID: <4dc0a8.23046.15d7de6d038.Coremail.yzhzhang@ipe.ac.cn>



Hello,

      I want to know if I can use paraview to visualize molecule dataset, i.e., using ball-and-stick model to represent molecules? Currently I can only using point gaussian to represent the "ball", but I don't know how to visualize the "stick". I know another visualization tool VMD is designed to do works of this kind, but I've not found similar founctions in ParaView.

-Zhang



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/0e937635/attachment.html>

From cory.quammen at kitware.com  Wed Jul 26 07:25:09 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 26 Jul 2017 07:25:09 -0400
Subject: [Paraview] Can I use paraview to visualize molecule dataset?
In-Reply-To: <4dc0a8.23046.15d7de6d038.Coremail.yzhzhang@ipe.ac.cn>
References: <4dc0a8.23046.15d7de6d038.Coremail.yzhzhang@ipe.ac.cn>
Message-ID: <CAB5Fpx6FDifu4gLoWgC7XW1AsguebkV+yttGeEQz6cO2JLKXNQ@mail.gmail.com>

Zhang,

Yes, you can visualize molecules in ball-and-stick representation in
ParaView (see attached). This representation is used whenever you load
a vtkMolecule data type. If you have a PDB file, for example, it will
be read in as a vtkMolecule data type and displayed with
ball-and-stick representation by default. You can also change the
Molecule "Render Mode" property to "Space Filling" or "Liquorice"
representation.

HTH,
Cory



On Wed, Jul 26, 2017 at 3:57 AM, ??? <yzhzhang at ipe.ac.cn> wrote:
>
>
> Hello,
>
>       I want to know if I can use paraview to visualize molecule dataset,
> i.e., using ball-and-stick model to represent molecules? Currently I can
> only using point gaussian to represent the "ball", but I don't know how to
> visualize the "stick". I know another visualization tool VMD is designed to
> do works of this kind, but I've not found similar founctions in ParaView.
>
> -Zhang
>
>
>
>
>
> _______________________________________________
> 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&D Engineer
Kitware, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Molecule.png
Type: image/png
Size: 22539 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/9afbbbab/attachment.png>

From utkarsh.ayachit at kitware.com  Wed Jul 26 08:57:13 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 26 Jul 2017 08:57:13 -0400
Subject: [Paraview] Can I use paraview to visualize molecule dataset?
In-Reply-To: <CAB5Fpx6FDifu4gLoWgC7XW1AsguebkV+yttGeEQz6cO2JLKXNQ@mail.gmail.com>
References: <4dc0a8.23046.15d7de6d038.Coremail.yzhzhang@ipe.ac.cn>
 <CAB5Fpx6FDifu4gLoWgC7XW1AsguebkV+yttGeEQz6cO2JLKXNQ@mail.gmail.com>
Message-ID: <CADHSJjCD4Ya2sGQYS3OPn4iOJZ19b5-A2WVWXyb9F1awAvTscA@mail.gmail.com>

And here's a related blog post:
https://blog.kitware.com/new-features-paraview-chemistry-pettt/

Utkarsh

On Wed, Jul 26, 2017 at 7:25 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Zhang,
>
> Yes, you can visualize molecules in ball-and-stick representation in
> ParaView (see attached). This representation is used whenever you load
> a vtkMolecule data type. If you have a PDB file, for example, it will
> be read in as a vtkMolecule data type and displayed with
> ball-and-stick representation by default. You can also change the
> Molecule "Render Mode" property to "Space Filling" or "Liquorice"
> representation.
>
> HTH,
> Cory
>
>
>
> On Wed, Jul 26, 2017 at 3:57 AM, ??? <yzhzhang at ipe.ac.cn> wrote:
> >
> >
> > Hello,
> >
> >       I want to know if I can use paraview to visualize molecule dataset,
> > i.e., using ball-and-stick model to represent molecules? Currently I can
> > only using point gaussian to represent the "ball", but I don't know how
> to
> > visualize the "stick". I know another visualization tool VMD is designed
> to
> > do works of this kind, but I've not found similar founctions in ParaView.
> >
> > -Zhang
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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&D 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/e5f88e66/attachment.html>

From yzhzhang at ipe.ac.cn  Wed Jul 26 09:11:09 2017
From: yzhzhang at ipe.ac.cn (=?UTF-8?B?5byg6amt5rSy?=)
Date: Wed, 26 Jul 2017 21:11:09 +0800 (GMT+08:00)
Subject: [Paraview] Can I use paraview to visualize molecule dataset?
In-Reply-To: <CAB5Fpx6FDifu4gLoWgC7XW1AsguebkV+yttGeEQz6cO2JLKXNQ@mail.gmail.com>
References: <4dc0a8.23046.15d7de6d038.Coremail.yzhzhang@ipe.ac.cn>
 <CAB5Fpx6FDifu4gLoWgC7XW1AsguebkV+yttGeEQz6cO2JLKXNQ@mail.gmail.com>
Message-ID: <27065d.21fe7.15d7f05bff1.Coremail.yzhzhang@ipe.ac.cn>


Thank you very much! That's exactly what I want.

-Zhang

> -----????-----
> ???: "Cory Quammen" <cory.quammen at kitware.com>
> ????: 2017?7?26? ???
> ???: "???" <yzhzhang at ipe.ac.cn>
> ??: ParaView <paraview at paraview.org>
> ??: Re: [Paraview] Can I use paraview to visualize molecule dataset?
> 
> Zhang,
> 
> Yes, you can visualize molecules in ball-and-stick representation in
> ParaView (see attached). This representation is used whenever you load
> a vtkMolecule data type. If you have a PDB file, for example, it will
> be read in as a vtkMolecule data type and displayed with
> ball-and-stick representation by default. You can also change the
> Molecule "Render Mode" property to "Space Filling" or "Liquorice"
> representation.
> 
> HTH,
> Cory
> 
> 
> 
> On Wed, Jul 26, 2017 at 3:57 AM, ??? <yzhzhang at ipe.ac.cn> wrote:
> >
> >
> > Hello,
> >
> >       I want to know if I can use paraview to visualize molecule dataset,
> > i.e., using ball-and-stick model to represent molecules? Currently I can
> > only using point gaussian to represent the "ball", but I don't know how to
> > visualize the "stick". I know another visualization tool VMD is designed to
> > do works of this kind, but I've not found similar founctions in ParaView.
> >
> > -Zhang
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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&D Engineer
> Kitware, Inc.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/39332e6c/attachment.html>

From kmorel at sandia.gov  Wed Jul 26 09:58:37 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 26 Jul 2017 13:58:37 +0000
Subject: [Paraview] Point data to 2d plane data
In-Reply-To: <81A18720EB4BBA489B6552676D14533C67BE2E13@chimbx4.ad.uillinois.edu>
References: <81A18720EB4BBA489B6552676D14533C67BE2E13@chimbx4.ad.uillinois.edu>
Message-ID: <29338753-4F0A-43BA-868E-ABDFD4BA11B0@sandia.gov>

Teng,

When you saved your data to a csv file, you lost all cell information. If you want to look at cells in your data, you will have to recreate them.

The easiest way to create cells is probably to use the Delaunay 2D filter. Note, however, that the cells created will not be the same as in your original vtk file.

If you want to keep your original cells, you will have to save them in a file that supports cell topology. One way to do that is when you save your csv file, also save a vtk file of the same data. Then, after you have run Matlab, load both the csv file and the vtk file. Do the TableToPoints on the csv data as before. Then use append attributes to copy the csv data to the vtk cell data.

-Ken

Sent from my iPad

On Jul 26, 2017, at 12:41 AM, Li, Teng <tengli2 at illinois.edu<mailto:tengli2 at illinois.edu>> wrote:

Dear Paraview developers,

I have a question about how to convert point data (vtk file) to 2d plane data. Actually, originally, I was working with vtk file. Then I use the extract selection to select some cells in the original model. In order to process the data of the selected cells, I save the data as the csv file. Then I use Matlab to do some calculation on the data in the csv file. After that, I open the modified csv file by using Paraview directly. And now, I can only see this csv file in spreadsheet view. After searching some online information, I use TabletoPoint to convert the data to point data. However, I still want to view them as the 2d cell. So I use point interpolation to try to convert the points data to 2d plane cell data. However, It doesn't work.

So my question is, how to show the data value in the space between different 2d points data by using point interpolation? Or is there any way that I can process the 2d cell plane data without saving it as the csv file?

Best,
Teng Li


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: tengli2 at illinois.edu<mailto:tengli2 at illinois.edu>



_______________________________________________
Powered by www.kitware.com<http://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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/d46f5c8c/attachment.html>

From lukas.kresta at gmail.com  Wed Jul 26 11:20:51 2017
From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=)
Date: Wed, 26 Jul 2017 17:20:51 +0200
Subject: [Paraview] Paraview Catalyst offscreen rendering
In-Reply-To: <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>
References: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
 <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>
Message-ID: <CAN4WRTzv15MiNuvP0P=YbyrSMGT2y-QfhjAbsTaTdUaj0MH74g@mail.gmail.com>

Thank you, but I have ParaView build with OSMesa without X. If I run
program with Catalyst(genereted script from ParaView, with render views) on
cluster with mpi, ussually one render view will show, but on anothers
process it crash with this error: ERROR: In
.../ParaView-v5.4.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line
819
vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I have
the same error with pvserver with or without --use-offscreen-rendering or
without pvserver.

If i run Catalyst with script only for live visualization then the program
go without problem but i dont get pictures which i want. Is there some
posibility how fix the error or how to get pictures(with offscreen
rendering)?

2017-07-14 16:24 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:

> Hi,
>
> If you're not memory constrained I suggest just doing a full ParaView
> build with OSMesa and X11 disabled. There are quite a few discussions on
> the PV mailing list on how to do that.
>
> If you're memory constrained then I would suggest building with all of the
> Catalyst editions enabled and see if that works for you.
>
> Best,
> Andy
>
> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta <lukas.kresta at gmail.com>
> wrote:
>
>> Hi,
>>
>> I would like to ask, which Paraview Catalyst (python) script use(with
>> render view or live visualization). If i want save images with offscreen
>> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>>
>> Thank you for your help.
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/0d7861bc/attachment.html>

From andy.bauer at kitware.com  Wed Jul 26 11:37:12 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 26 Jul 2017 11:37:12 -0400
Subject: [Paraview] Paraview Catalyst offscreen rendering
In-Reply-To: <CAN4WRTzv15MiNuvP0P=YbyrSMGT2y-QfhjAbsTaTdUaj0MH74g@mail.gmail.com>
References: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
 <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>
 <CAN4WRTzv15MiNuvP0P=YbyrSMGT2y-QfhjAbsTaTdUaj0MH74g@mail.gmail.com>
Message-ID: <CAMaOp+HsCwvvkhPd_a9kyRb_dWYCKGwxrvKcHZf5aVKVpn6TKA@mail.gmail.com>

Hi,

It sounds like you didn't properly build with OSMesa. If you share your
CMakeCache.txt from your ParaView build I can see if I can track down the
problem.

Best,
Andy

On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta <lukas.kresta at gmail.com>
wrote:

> Thank you, but I have ParaView build with OSMesa without X. If I run
> program with Catalyst(genereted script from ParaView, with render views) on
> cluster with mpi, ussually one render view will show, but on anothers
> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/
> Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819
> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I have
> the same error with pvserver with or without --use-offscreen-rendering or
> without pvserver.
>
> If i run Catalyst with script only for live visualization then the program
> go without problem but i dont get pictures which i want. Is there some
> posibility how fix the error or how to get pictures(with offscreen
> rendering)?
>
> 2017-07-14 16:24 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:
>
>> Hi,
>>
>> If you're not memory constrained I suggest just doing a full ParaView
>> build with OSMesa and X11 disabled. There are quite a few discussions on
>> the PV mailing list on how to do that.
>>
>> If you're memory constrained then I would suggest building with all of
>> the Catalyst editions enabled and see if that works for you.
>>
>> Best,
>> Andy
>>
>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta <lukas.kresta at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I would like to ask, which Paraview Catalyst (python) script use(with
>>> render view or live visualization). If i want save images with offscreen
>>> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>>>
>>> Thank you for your help.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/b049a212/attachment.html>

From mbahameish at gmail.com  Wed Jul 26 15:29:40 2017
From: mbahameish at gmail.com (Mariam)
Date: Wed, 26 Jul 2017 20:29:40 +0100
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
 <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
Message-ID: <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>

Thanks for your reply.

The correct syntax to run on multiple hosts is: mpiexec ?hosts N localhost M remotehost 1 appName

I tested with hostname and it worked; it printed the expected output.

 

However, by executing the same command with pvserver, it does not work. I ensured the location of paraview/pvserver is the same across both hosts. And I am providing the full path of pvserver.

 

I would like to make sure that I understood the concept correctly:

>From host1, if I executed parallel pvservers with MPI (host1, host2, hostN), the clients should connect to host1. 

 

Can you please confirm?

 

From: Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr>
Date: Tuesday, July 25, 2017 at 5:45 PM
To: Mariam <mbahameish at gmail.com>, <paraview at paraview.org>
Subject: Re: [Paraview] MPI on multiple nodes

 

I think the syntax for mpiexec is:

mpiexec -np 8 --host host_one,host_two pvserver

This would launch 4 occurences of pvserver on host_one and 4 on host_two.

1) first check mpi is running:

mpiexec -np 2 --host host_one,host_two hostname

This should print the name of the 2 hosts.

If it does not works check you can ssh from one host to the other without password.

2) You need the same paraview/pvserver install on the two hosts in the same location (not imposed but it is easier to launch)

3) May be use reverse connection from the parallel pvserver to the paraview client when you launch pvserver 

Patrick


Mariam wrote: 

Hi, 

I would like to ask about running pvserver in parallel with MPI on multiple hosts. Is that possible?

 

The following commands were tested successfully:

1)      Running MPI on localhost:

mpiexec ?n M localhost pvserver

2)      Running MPI on remotehost:

mpiexec ?host remotehost ?n M pvserver

 

But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver

I run the following to test MPI on multiple hosts and it worked: mpiexec ?hosts 2 localhost 1 remotehost 1 hostname

 

Is there any pre-configuration that should be done to pvserver? I want the clients to connect to the server (master server), and the jobs are distributed across multiple nodes.

 

Regards,

Mariam




_______________________________________________
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



-- 
===================================================================
|? Equipe M.O.S.T.???????? |????????????????????????????????????? |
|? Patrick BEGOU?????????? | mailto:Patrick.Begou at grenoble-inp.fr |
|? LEGI??????????????????? |????????????????????????????????????? |
|? BP 53 X???????????????? | Tel 04 76 82 51 35?????????????????? |
|? 38041 GRENOBLE CEDEX??? | Fax 04 76 82 52 71?????????????????? |
===================================================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170726/b8823e98/attachment.html>

From Patrick.Begou at legi.grenoble-inp.fr  Thu Jul 27 03:07:09 2017
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Thu, 27 Jul 2017 09:07:09 +0200
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
 <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
 <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>
Message-ID: <9b728677-d356-ee24-1bca-56ab979e5b08@legi.grenoble-inp.fr>

I'm sorry but the syntax you want to use doesn't work on my servers. So I cannot 
help.
With the one I suggest I'm running 360 pvserver processes this morning to 
visualize a large dataset on a cluster. May be you should try it.

Patrick

Mariam wrote:
>
> Thanks for your reply.
>
> The correct syntax to run on multiple hosts is: mpiexec ?hosts N localhost M 
> remotehost 1 appName
>
> I tested with hostname and it worked; it printed the expected output.
>
> However, by executing the same command with pvserver, it does not work. I 
> ensured the location of paraview/pvserver is the same across both hosts. And I 
> am providing the full path of pvserver.
>
> I would like to make sure that I understood the concept correctly:
>
> From host1, if I executed parallel pvservers with MPI (host1, host2, hostN), 
> the clients should connect to host1.
>
> Can you please confirm?
>
> *From: *Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr>
> *Date: *Tuesday, July 25, 2017 at 5:45 PM
> *To: *Mariam <mbahameish at gmail.com>, <paraview at paraview.org>
> *Subject: *Re: [Paraview] MPI on multiple nodes
>
> I think the syntax for mpiexec is:
>
> mpiexec -np 8 --host host_one,host_two pvserver
>
> This would launch 4 occurences of pvserver on host_one and 4 on host_two.
>
> 1) first check mpi is running:
>
> mpiexec -np 2 --host host_one,host_two hostname
>
> This should print the name of the 2 hosts.
>
> If it does not works check you can ssh from one host to the other without 
> password.
>
> 2) You need the same paraview/pvserver install on the two hosts in the same 
> location (not imposed but it is easier to launch)
>
> 3) May be use reverse connection from the parallel pvserver to the paraview 
> client when you launch pvserver
>
> Patrick
>
>
> Mariam wrote:
>
>     Hi,
>
>     I would like to ask about running pvserver in parallel with MPI on
>     multiple hosts. Is that possible?
>
>     The following commands were tested successfully:
>
>     1)Running MPI on localhost:
>
>     mpiexec ?n M localhost pvserver
>
>     2)Running MPI on remotehost:
>
>     mpiexec ?host remotehost ?n M pvserver
>
>     But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver
>
>     I run the following to test MPI on multiple hosts and it worked: mpiexec
>     ?hosts 2 localhost 1 remotehost 1 hostname
>
>     Is there any pre-configuration that should be done to pvserver? I want the
>     clients to connect to the server (master server), and the jobs are
>     distributed across multiple nodes.
>
>     Regards,
>
>     Mariam
>
>
>
>
>     _______________________________________________
>
>     Powered bywww.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects athttp://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
>
>
>
>
> -- 
> ===================================================================
> |  Equipe M.O.S.T.         |                                      |
> |  Patrick BEGOU           |mailto:Patrick.Begou at grenoble-inp.fr  |
> |  LEGI                    |                                      |
> |  BP 53 X                 | Tel 04 76 82 51 35                   |
> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
> ===================================================================


-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/180e07be/attachment.html>

From mbahameish at gmail.com  Thu Jul 27 03:18:58 2017
From: mbahameish at gmail.com (Mariam Bahameish)
Date: Thu, 27 Jul 2017 08:18:58 +0100
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <9b728677-d356-ee24-1bca-56ab979e5b08@legi.grenoble-inp.fr>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
 <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
 <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>
 <9b728677-d356-ee24-1bca-56ab979e5b08@legi.grenoble-inp.fr>
Message-ID: <BA3B52FE-6327-4A7C-973C-F79D15D77AC4@gmail.com>

Yesterday, I tried the syntax you provided me, but it didn't work.
So I am thinking if there is anything that I should preconfigure.

Are you using it with reverse connection?

Thanks,
Sent from my iPhone

> On Jul 27, 2017, at 8:07 AM, Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr> wrote:
> 
> I'm sorry but the syntax you want to use doesn't work on my servers. So I cannot help.
> With the one I suggest I'm running 360 pvserver processes this morning to visualize a large dataset on a cluster. May be you should try it.
> 
> Patrick
> 
> Mariam wrote:
>> 
>> Thanks for your reply.
>> The correct syntax to run on multiple hosts is: mpiexec ?hosts N localhost M remotehost 1 appName
>> I tested with hostname and it worked; it printed the expected output.
>>  
>> However, by executing the same command with pvserver, it does not work. I ensured the location of paraview/pvserver is the same across both hosts. And I am providing the full path of pvserver.
>>  
>> I would like to make sure that I understood the concept correctly:
>> From host1, if I executed parallel pvservers with MPI (host1, host2, hostN), the clients should connect to host1.
>>  
>> Can you please confirm?
>>  
>> From: Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr>
>> Date: Tuesday, July 25, 2017 at 5:45 PM
>> To: Mariam <mbahameish at gmail.com>, <paraview at paraview.org>
>> Subject: Re: [Paraview] MPI on multiple nodes
>>  
>> I think the syntax for mpiexec is:
>> 
>> mpiexec -np 8 --host host_one,host_two pvserver
>> 
>> This would launch 4 occurences of pvserver on host_one and 4 on host_two.
>> 
>> 1) first check mpi is running:
>> 
>> mpiexec -np 2 --host host_one,host_two hostname
>> 
>> This should print the name of the 2 hosts.
>> 
>> If it does not works check you can ssh from one host to the other without password.
>> 
>> 2) You need the same paraview/pvserver install on the two hosts in the same location (not imposed but it is easier to launch)
>> 
>> 3) May be use reverse connection from the parallel pvserver to the paraview client when you launch pvserver 
>> 
>> Patrick
>> 
>> 
>> Mariam wrote:
>> Hi,
>> I would like to ask about running pvserver in parallel with MPI on multiple hosts. Is that possible?
>>  
>> The following commands were tested successfully:
>> 1)      Running MPI on localhost:
>> mpiexec ?n M localhost pvserver
>> 2)      Running MPI on remotehost:
>> mpiexec ?host remotehost ?n M pvserver
>>  
>> But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver
>> I run the following to test MPI on multiple hosts and it worked: mpiexec ?hosts 2 localhost 1 remotehost 1 hostname
>>  
>> Is there any pre-configuration that should be done to pvserver? I want the clients to connect to the server (master server), and the jobs are distributed across multiple nodes.
>>  
>> Regards,
>> Mariam
>> 
>> 
>> 
>> _______________________________________________
>> 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
>> 
>> 
>> 
>> -- 
>> ===================================================================
>> |  Equipe M.O.S.T.         |                                      |
>> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
>> |  LEGI                    |                                      |
>> |  BP 53 X                 | Tel 04 76 82 51 35                   |
>> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
>> ===================================================================
> 
> 
> -- 
> ===================================================================
> |  Equipe M.O.S.T.         |                                      |
> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
> |  LEGI                    |                                      |
> |  BP 53 X                 | Tel 04 76 82 51 35                   |
> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
> ===================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/630d58b3/attachment.html>

From lukas.kresta at gmail.com  Thu Jul 27 05:48:07 2017
From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=)
Date: Thu, 27 Jul 2017 11:48:07 +0200
Subject: [Paraview] Paraview Catalyst offscreen rendering
In-Reply-To: <CAMaOp+HsCwvvkhPd_a9kyRb_dWYCKGwxrvKcHZf5aVKVpn6TKA@mail.gmail.com>
References: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
 <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>
 <CAN4WRTzv15MiNuvP0P=YbyrSMGT2y-QfhjAbsTaTdUaj0MH74g@mail.gmail.com>
 <CAMaOp+HsCwvvkhPd_a9kyRb_dWYCKGwxrvKcHZf5aVKVpn6TKA@mail.gmail.com>
Message-ID: <CAN4WRTxmDAU=hzhTuYG46ev0COiSs8v5rUC+YRuQZ=kUR4UEJQ@mail.gmail.com>

it was build with easybuild with these parametrs:

cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/

-DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay

-DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz
-fp-speculation=safe -fp-model source -fPIC'

-DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model
source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc'

DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz
-fp-speculation=safe -fp-model source -fPIC'

-DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON
-DVTK_OPENGL_HAS_OSMESA=ON

-DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include
-DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so

-DOSMESA_INCLUDE_DIR=$EBROOTMESA/include
-DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so

-DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so
-DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON
-DBUILD_SHARED_LIBS=ON

-DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON
-DOSPRAY_INSTALL_DIR=$EBROOT
 OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF


I hope, it will help solve my problem. If you need, i can send you complete log.


2017-07-26 17:37 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:

> Hi,
>
> It sounds like you didn't properly build with OSMesa. If you share your
> CMakeCache.txt from your ParaView build I can see if I can track down the
> problem.
>
> Best,
> Andy
>
> On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta <lukas.kresta at gmail.com>
> wrote:
>
>> Thank you, but I have ParaView build with OSMesa without X. If I run
>> program with Catalyst(genereted script from ParaView, with render views) on
>> cluster with mpi, ussually one render view will show, but on anothers
>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render
>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819
>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I have
>> the same error with pvserver with or without --use-offscreen-rendering or
>> without pvserver.
>>
>> If i run Catalyst with script only for live visualization then the
>> program go without problem but i dont get pictures which i want. Is there
>> some posibility how fix the error or how to get pictures(with offscreen
>> rendering)?
>>
>> 2017-07-14 16:24 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:
>>
>>> Hi,
>>>
>>> If you're not memory constrained I suggest just doing a full ParaView
>>> build with OSMesa and X11 disabled. There are quite a few discussions on
>>> the PV mailing list on how to do that.
>>>
>>> If you're memory constrained then I would suggest building with all of
>>> the Catalyst editions enabled and see if that works for you.
>>>
>>> Best,
>>> Andy
>>>
>>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta <lukas.kresta at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I would like to ask, which Paraview Catalyst (python) script use(with
>>>> render view or live visualization). If i want save images with offscreen
>>>> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>>>>
>>>> Thank you for your help.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/ac073609/attachment.html>

From jlopezfisica at ciencias.unam.mx  Thu Jul 27 08:51:51 2017
From: jlopezfisica at ciencias.unam.mx (=?UTF-8?B?Sm9zw6kgTHVpcyBMw7NwZXogTMOzcGV6?=)
Date: Thu, 27 Jul 2017 14:51:51 +0200
Subject: [Paraview] Unable to build paraview in ubuntu
Message-ID: <CABYN2Np_JbVXTbBbQmwOUV+BkcQDyK0ES2uStNbTNRHVtV62Vg@mail.gmail.com>

Hi! Guys,

this error was found before, do you remember how to solve it? I am building
ParaView with CMake and I need to start a trace, but pvpython does not work

collect2: error: ld returned 1 exit status
CommandLineExecutables/CMakeFiles/pvpython.dir/build.make:128: recipe for
target 'bin/pvpython' failed
make[2]: *** [bin/pvpython] Error 1
CMakeFiles/Makefile2:46261: recipe for target
'CommandLineExecutables/CMakeFiles/pvpython.dir/all' failed
make[1]: *** [CommandLineExecutables/CMakeFiles/pvpython.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

thanks Jose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/facf2f38/attachment.html>

From shawn.waldon at kitware.com  Thu Jul 27 08:56:36 2017
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Thu, 27 Jul 2017 08:56:36 -0400
Subject: [Paraview] Unable to build paraview in ubuntu
In-Reply-To: <CABYN2Np_JbVXTbBbQmwOUV+BkcQDyK0ES2uStNbTNRHVtV62Vg@mail.gmail.com>
References: <CABYN2Np_JbVXTbBbQmwOUV+BkcQDyK0ES2uStNbTNRHVtV62Vg@mail.gmail.com>
Message-ID: <CALSpCT1gZnee_serxQ32y5Of-poBDroCAHbV738AvGko6ziT=g@mail.gmail.com>

Hi Jose,

The real error is higher up in your build log, that is just make's output
that something failed.  It looks like the pvpython executable failed to
link, so you need to scroll back and look for the link error.

HTH,
Shawn

On Thu, Jul 27, 2017 at 8:51 AM, Jos? Luis L?pez L?pez <
jlopezfisica at ciencias.unam.mx> wrote:

> Hi! Guys,
>
> this error was found before, do you remember how to solve it? I am
> building ParaView with CMake and I need to start a trace, but pvpython does
> not work
>
> collect2: error: ld returned 1 exit status
> CommandLineExecutables/CMakeFiles/pvpython.dir/build.make:128: recipe for
> target 'bin/pvpython' failed
> make[2]: *** [bin/pvpython] Error 1
> CMakeFiles/Makefile2:46261: recipe for target 'CommandLineExecutables/CMakeFiles/pvpython.dir/all'
> failed
> make[1]: *** [CommandLineExecutables/CMakeFiles/pvpython.dir/all] Error 2
> Makefile:116: recipe for target 'all' failed
> make: *** [all] Error 2
>
> thanks Jose
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/9444c930/attachment.html>

From chuck.atkins at kitware.com  Thu Jul 27 10:46:51 2017
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 27 Jul 2017 10:46:51 -0400
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <BA3B52FE-6327-4A7C-973C-F79D15D77AC4@gmail.com>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
 <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
 <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>
 <9b728677-d356-ee24-1bca-56ab979e5b08@legi.grenoble-inp.fr>
 <BA3B52FE-6327-4A7C-973C-F79D15D77AC4@gmail.com>
Message-ID: <CAOXZzG7fFLwyaGaUAzTqEpvPvyp+dfCc6t6xC+C5f1M9rv0aqA@mail.gmail.com>

Hi Mariam, Patrick,


> Yesterday, I tried the syntax you provided me, but it didn't work.
>

...

> I'm sorry but the syntax you want to use doesn't work on my servers.
>
> ...

> The correct syntax to run on multiple hosts is
>
> ...

> I think the syntax for mpiexec is:
>
>
The syntax for specifying what ranks run on which hosts is implementation
specific and will be specified differently for OpenMPI, MPICH, MVAPICH2,
IntelMPI, etc.  It will also depend on the environment you're running it in
and how it';s configured, i.e. are you running mpiexec inside a job
launched by a scheduler or are you manually configuring MPI, using tcp
everywhere, are you using host or machine files, etc.  All of these things
are going to be implementation specific.  Please consult the documentation
for the system you're using or the specific MPI implementation you're using
for the appropriate syntax to use, as it will be different for different
people, machines, environments, and configurations.


But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1
> pvserver
>
> Can you provide some more context?  What actually happens?  What didn't
work?  Were there any error messages? etc.


Thanks

----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/8a879f15/attachment.html>

From shawn.waldon at kitware.com  Thu Jul 27 11:02:57 2017
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Thu, 27 Jul 2017 11:02:57 -0400
Subject: [Paraview] Unable to build paraview in ubuntu
In-Reply-To: <CABYN2NpQfJCxYXR9_aBpGPJb+UVGAX0hb61v8Fur8Q1stNULdA@mail.gmail.com>
References: <CABYN2Np_JbVXTbBbQmwOUV+BkcQDyK0ES2uStNbTNRHVtV62Vg@mail.gmail.com>
 <CALSpCT1gZnee_serxQ32y5Of-poBDroCAHbV738AvGko6ziT=g@mail.gmail.com>
 <CABYN2NpQfJCxYXR9_aBpGPJb+UVGAX0hb61v8Fur8Q1stNULdA@mail.gmail.com>
Message-ID: <CALSpCT2DVDCu3xE1+8xYDAO8WvQyk=JEnAPbnkh5XbvBWEWUqA@mail.gmail.com>

Hi Jose,

Please keep the list in the conversation so that others can chime in too
(and/or find the solution in the future).  I'm not sure why pvpython is
even linking to Qt.  As far as I know it shouldn't be.  If you want to
re-send your error to the list, someone may be able to help.

HTH,
Shawn

On Thu, Jul 27, 2017 at 9:45 AM, Jos? Luis L?pez L?pez <
jlopezfisica at ciencias.unam.mx> wrote:

> Hi Shawn,
>
> I tried different things but it seems to be a problem with Qt5, I attached
> the error in a file,
> I hope you can help me, ParaView works fine but pvpython does not,
>
> Jose
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/56edf6fe/attachment.html>

From mbahameish at gmail.com  Thu Jul 27 10:59:51 2017
From: mbahameish at gmail.com (Mariam)
Date: Thu, 27 Jul 2017 15:59:51 +0100
Subject: [Paraview] MPI on multiple nodes
In-Reply-To: <CAOXZzG7fFLwyaGaUAzTqEpvPvyp+dfCc6t6xC+C5f1M9rv0aqA@mail.gmail.com>
References: <F343C469-F370-4038-96F1-638B5626E4AF@gmail.com>
 <aec095db-979a-a6de-acf2-59035827ada0@legi.grenoble-inp.fr>
 <61AB1756-E6B9-4E6A-9B8A-4BBC3B5B8E92@gmail.com>
 <9b728677-d356-ee24-1bca-56ab979e5b08@legi.grenoble-inp.fr>
 <BA3B52FE-6327-4A7C-973C-F79D15D77AC4@gmail.com>
 <CAOXZzG7fFLwyaGaUAzTqEpvPvyp+dfCc6t6xC+C5f1M9rv0aqA@mail.gmail.com>
Message-ID: <ACF3F3F1-F515-4181-BB56-CDDA74CA937F@gmail.com>

Thanks for your reply Chuck.

I am using Microsoft MPI which I believe it has MPICH basis.

 

I created a small LAN network for testing, both running Windows 10, and ParaView is installed on the same path, firewall is turned off.

I was running MPIEXEC manually from one of the machines using this command: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver

 

By doing that, no errors where received but it seems the connection has not been established. I should get a message like the following:

Waiting for client...

Connection URL: cs://PC.local:11111

Accepting connection(s): PC.local:11111

 

But nothing has been received, and even no messages on SMPD console. I tried to forcefully connect the ParaView client to the server in this state, but I got a message that the socket is not open.

 

>From the localhost, I tried to run pvserver on the remotehost and this has been successfully executed: mpiexec ?host remotehost ?n M pvserver

 

Apologies,

This is my first time to work with MPI, appreciate your help & support. I could not troubleshoot since there were no messages/ indications to resolve the issue.

 

Thanks again!

 

From: Chuck Atkins <chuck.atkins at kitware.com>
Date: Thursday, July 27, 2017 at 3:46 PM
To: Mariam Bahameish <mbahameish at gmail.com>
Cc: Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr>, "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [Paraview] MPI on multiple nodes

 

Hi Mariam, Patrick,

 

Yesterday, I tried the syntax you provided me, but it didn't work.

 

... 

I'm sorry but the syntax you want to use doesn't work on my servers.

... 

The correct syntax to run on multiple hosts is

... 

I think the syntax for mpiexec is:

 

The syntax for specifying what ranks run on which hosts is implementation specific and will be specified differently for OpenMPI, MPICH, MVAPICH2, IntelMPI, etc.  It will also depend on the environment you're running it in and how it';s configured, i.e. are you running mpiexec inside a job launched by a scheduler or are you manually configuring MPI, using tcp everywhere, are you using host or machine files, etc.  All of these things are going to be implementation specific.  Please consult the documentation for the system you're using or the specific MPI implementation you're using for the appropriate syntax to use, as it will be different for different people, machines, environments, and configurations.

 

But I was not able to run: mpiexec ?hosts 2 localhost 1 remotehost 1 pvserver

Can you provide some more context?  What actually happens?  What didn't work?  Were there any error messages? etc.

 

Thanks

----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/ec5d30b2/attachment.html>

From cory.quammen at kitware.com  Thu Jul 27 12:32:17 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 27 Jul 2017 12:32:17 -0400
Subject: [Paraview] ParaView 5.4.1-RC2 available for download
Message-ID: <CAB5Fpx5+Bf5n132GHS8zVE4-_hmJg++kZJBjjKOkYDyjZMGTRg@mail.gmail.com>

On behalf of the ParaView development team, I am happy to announce
that ParaView 5.4.1-RC2 is available for download. Binaries and source
code are available from

www.paraview.org/download

Note that ParaView 5.4.1-RC1 had a critical bug that was identified
and resolved internally before binaries and source code were made
available for download, so we have skipped straight to RC2.

The 5.4.1-RC2 bug fix release addresses a number of problems, including:

* The black render window observed on some systems when FXAA was
enabled or an object's opacity was less than 1 has been fixed.

* Field output for cells with non-straight edges has been corrected.

* Derivatives for quadratic triangles are now computed correctly.

* A bug that occurred when generating a Catalyst script with no images
output has been fixed.

* A problem with writing animations as AVIs was fixed.

* Logic in the CGNS reader was updated to correctly read all solution
nodes for each centering type when FlowSolutionPointers are missing.

* Fixed crash in CGNS reader when moving forward in time.

* Fixed problem with long-running animations not advancing past a
certain number of time steps.

* Resolved issue where changing one file path in the state file loader
"Choose File Names" dialog also changed the file paths of other files
with the same type.

* Addressed problem with enumerated property dependencies in ParaViewWeb.

* Added ability to change the font size in the ParaView user interface.

* Fixed BoxLib3D file reader.

* State files now properly support files with relative paths.

* Removed inappropriate scalar bar scaling when saving large screen shots.

Please report any problems you find with this release candidate on the
mailing list or on the bug tracker at
https://gitlab.kitware.com/paraview/paraview/issues

- Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.

From utkarsh.ayachit at kitware.com  Thu Jul 27 13:54:34 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 27 Jul 2017 13:54:34 -0400
Subject: [Paraview] time dependent temperature plot ??
In-Reply-To: <CAPca1TwhRhA9uMJRUDCsmM3ahU=zkZ85=+kjqCthLRqLt=f7aw@mail.gmail.com>
References: <CAPca1TwyaW3JemWwnPWm6VHOcL-wtQ_52B1NGDbe0GFD1sn8=w@mail.gmail.com>
 <CADHSJjD5Uo5xL-m1mfZX0jHRvnrs1Z3aszJP23SpUszxEhsNXw@mail.gmail.com>
 <CAPca1TwhRhA9uMJRUDCsmM3ahU=zkZ85=+kjqCthLRqLt=f7aw@mail.gmail.com>
Message-ID: <CADHSJjDsXRFv6AkSrj=TzHfEZgxEnmq+X58bVNThWqOD-sN8qQ@mail.gmail.com>

> a)       Temperature across the wall ( the heat transfer plot across the
> wall for applied varying temperature  with respect to time )

It's still unclear to me what you want when you save "across the wall"
and v/s time. Across in which direction? So attached is state that
generates the plot for max temperature of the data over time. Hope
that gets you started. The state was generated with 5.4.1-RC2. You can
download the binaries from paraview.org.

> I do want an average and min and max plots of temperature w.r.t for each
> time step of that whole block

Change the "Python Calculator" expression to `min` or `mean` instead
of `max` and you'll be plotting that curve.

>  c)   and one more thing Utkarsh, after I open the ParaView application, I
> will get an output message tab like " UNABLE TO DISABLE THE ROTATION (0.,)".
> by closing this tab I can work on that, but my only doubt does it have any
> implication the results ?? I have attached the picture of that

Not sure where that is coming from. Do you still get it with 5.4.1-RC2 binaries?

Utkarsh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max-temperature-vs-time.pvsm
Type: application/octet-stream
Size: 292150 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/d889e934/attachment-0001.obj>

From andy.bauer at kitware.com  Thu Jul 27 14:13:03 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 27 Jul 2017 14:13:03 -0400
Subject: [Paraview] Paraview Catalyst offscreen rendering
In-Reply-To: <CAN4WRTxmDAU=hzhTuYG46ev0COiSs8v5rUC+YRuQZ=kUR4UEJQ@mail.gmail.com>
References: <CAN4WRTyXMvK8_M0CbqPjx=sMTsa5KPFt_sErmO9i=PTF-N5-SQ@mail.gmail.com>
 <CAMaOp+EVD_POv-aqBbQXicaj0qrbKsux6NToJqcY7GPfCVnZLQ@mail.gmail.com>
 <CAN4WRTzv15MiNuvP0P=YbyrSMGT2y-QfhjAbsTaTdUaj0MH74g@mail.gmail.com>
 <CAMaOp+HsCwvvkhPd_a9kyRb_dWYCKGwxrvKcHZf5aVKVpn6TKA@mail.gmail.com>
 <CAN4WRTxmDAU=hzhTuYG46ev0COiSs8v5rUC+YRuQZ=kUR4UEJQ@mail.gmail.com>
Message-ID: <CAMaOp+GGdj1PdeJeybdbsEN7BSsU+Sq-ynqd17aT0vOaQMsJuQ@mail.gmail.com>

I think what you're missing is -DVTK_USE_X=OFF and probably
-DVTK_USE_OFFSCREEN=ON. If that doesn't work, please send your
CMakeCache.txt from your build directory.

On Thu, Jul 27, 2017 at 5:48 AM, Luk?? Kresta <lukas.kresta at gmail.com>
wrote:

> it was build with easybuild with these parametrs:
>
> cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/
>
> -DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay
>
> -DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC'
>
> -DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc'
>
> DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC'
>
> -DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DVTK_OPENGL_HAS_OSMESA=ON
>
> -DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include -DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so
>
> -DOSMESA_INCLUDE_DIR=$EBROOTMESA/include -DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so
>
> -DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so -DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON -DBUILD_SHARED_LIBS=ON
>
> -DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON -DOSPRAY_INSTALL_DIR=$EBROOT
>  OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF
>
>
> I hope, it will help solve my problem. If you need, i can send you complete log.
>
>
> 2017-07-26 17:37 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:
>
>> Hi,
>>
>> It sounds like you didn't properly build with OSMesa. If you share your
>> CMakeCache.txt from your ParaView build I can see if I can track down the
>> problem.
>>
>> Best,
>> Andy
>>
>> On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta <lukas.kresta at gmail.com>
>> wrote:
>>
>>> Thank you, but I have ParaView build with OSMesa without X. If I run
>>> program with Catalyst(genereted script from ParaView, with render views) on
>>> cluster with mpi, ussually one render view will show, but on anothers
>>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render
>>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819
>>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I
>>> have the same error with pvserver with or without --use-offscreen-rendering
>>> or without pvserver.
>>>
>>> If i run Catalyst with script only for live visualization then the
>>> program go without problem but i dont get pictures which i want. Is there
>>> some posibility how fix the error or how to get pictures(with offscreen
>>> rendering)?
>>>
>>> 2017-07-14 16:24 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:
>>>
>>>> Hi,
>>>>
>>>> If you're not memory constrained I suggest just doing a full ParaView
>>>> build with OSMesa and X11 disabled. There are quite a few discussions on
>>>> the PV mailing list on how to do that.
>>>>
>>>> If you're memory constrained then I would suggest building with all of
>>>> the Catalyst editions enabled and see if that works for you.
>>>>
>>>> Best,
>>>> Andy
>>>>
>>>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta <lukas.kresta at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I would like to ask, which Paraview Catalyst (python) script use(with
>>>>> render view or live visualization). If i want save images with offscreen
>>>>> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>>>>>
>>>>> Thank you for your help.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/394d00af/attachment.html>

From steytle1 at illinois.edu  Thu Jul 27 16:44:21 2017
From: steytle1 at illinois.edu (Steytler, Louis Louw)
Date: Thu, 27 Jul 2017 20:44:21 +0000
Subject: [Paraview] Suppress Error Printout
Message-ID: <2F8BA25CC0B82C4DB6756F8F663E6DB35EC803A3@CITESMBX2.ad.uillinois.edu>

Hi All,

Is it possible to suppress the printing of errors when using pvpython?

I am getting this error:

ERROR: In /projects/pvdev/common/pv-source/v4.3.1/VTK/Common/DataModel/vtkTriQuadraticHexahedron.cxx, line 231
vtkTriQuadraticHexahedron (0x294372c0): Newton did not converged, iteration 10 det -0.0262359

many times over every time the time step is incremented and streamlines are re-computed. I am not so much worried that the streamlines are not converging, but the error messages are flooding the output window.

Any advice would be very much appreciated.

Thanks very much,

Louis Steytler
Department of Mechanical Science and Engineering
University of Illinois at Urbana-Champaign
1206 West Green Street
Urbana, Il 61801
steytle1 at illinois.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170727/aa5a7777/attachment.html>

From cory.quammen at kitware.com  Mon Jul 31 10:51:17 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 31 Jul 2017 10:51:17 -0400
Subject: [Paraview] ParaView 5.4.1-RC2 available for download
In-Reply-To: <CAB5Fpx5+Bf5n132GHS8zVE4-_hmJg++kZJBjjKOkYDyjZMGTRg@mail.gmail.com>
References: <CAB5Fpx5+Bf5n132GHS8zVE4-_hmJg++kZJBjjKOkYDyjZMGTRg@mail.gmail.com>
Message-ID: <CAB5Fpx710ROJU-HV-GQAom6UcgbyRoYKn0R3aa5c2x4c2w_ZxQ@mail.gmail.com>

Hi folks,

Signed Mac .dmg and .pkg installers for ParaView 5.4.1-RC2 are now
available on the downloads page at www.paraview.org/download.

Thanks,
Cory

On Thu, Jul 27, 2017 at 12:32 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> On behalf of the ParaView development team, I am happy to announce
> that ParaView 5.4.1-RC2 is available for download. Binaries and source
> code are available from
>
> www.paraview.org/download
>
> Note that ParaView 5.4.1-RC1 had a critical bug that was identified
> and resolved internally before binaries and source code were made
> available for download, so we have skipped straight to RC2.
>
> The 5.4.1-RC2 bug fix release addresses a number of problems, including:
>
> * The black render window observed on some systems when FXAA was
> enabled or an object's opacity was less than 1 has been fixed.
>
> * Field output for cells with non-straight edges has been corrected.
>
> * Derivatives for quadratic triangles are now computed correctly.
>
> * A bug that occurred when generating a Catalyst script with no images
> output has been fixed.
>
> * A problem with writing animations as AVIs was fixed.
>
> * Logic in the CGNS reader was updated to correctly read all solution
> nodes for each centering type when FlowSolutionPointers are missing.
>
> * Fixed crash in CGNS reader when moving forward in time.
>
> * Fixed problem with long-running animations not advancing past a
> certain number of time steps.
>
> * Resolved issue where changing one file path in the state file loader
> "Choose File Names" dialog also changed the file paths of other files
> with the same type.
>
> * Addressed problem with enumerated property dependencies in ParaViewWeb.
>
> * Added ability to change the font size in the ParaView user interface.
>
> * Fixed BoxLib3D file reader.
>
> * State files now properly support files with relative paths.
>
> * Removed inappropriate scalar bar scaling when saving large screen shots.
>
> Please report any problems you find with this release candidate on the
> mailing list or on the bug tracker at
> https://gitlab.kitware.com/paraview/paraview/issues
>
> - Cory
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170731/34f5fffb/attachment.html>

From wascott at sandia.gov  Mon Jul 31 12:52:44 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 31 Jul 2017 16:52:44 +0000
Subject: [Paraview] [EXTERNAL]  Excel Pivot Table like functionality
In-Reply-To: <SN2PR0701MB7847F8F480ACAF325FB09799FBB0@SN2PR0701MB784.namprd07.prod.outlook.com>
References: <SN2PR0701MB7847F8F480ACAF325FB09799FBB0@SN2PR0701MB784.namprd07.prod.outlook.com>
Message-ID: <8aa51ddaf34849e2958d92bad7a27015@ES01AMSNLNT.srn.sandia.gov>

Kitware - Ping?

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dennis Conklin
Sent: Monday, July 24, 2017 2:34 PM
To: Paraview (paraview at paraview.org) <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Excel Pivot Table like functionality

All,

So, I have a multi-block dataset (Exodus).   Within each block, I have sets of 360 elements which have a common index.   So, in Block 1, elements 0-359 have a cell variable called N_RING, which is 1.    Elements 360-719, have N_RING=2, etc.

What I really want is the ability to operate on these sets.   Imagine I have an element variable called Ying, which is different for each element in the model.  I would like every element with N_RING=1 to have an element variable of Ying_max assigned, which is the maximum value of Ying for any element with N_RING=1.    So, for example,  elements 0-359 would be assigned a value of Ying_max which is the maximum value of Ying in any of elements 0-359.   Elements 360-719 would be assigned a value of Ying_max which is the maximum value for any element with N_RING=2.    I would ideally also like to get min and average.

Is there any way to get max/min/average of a group consisting of a cell variable index?  - and to assign the output as element variables so I can color by?

Thanks for any hints.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170731/d8928426/attachment.html>