[Paraview] ParaView 5.4.1-RC3 available for download

[Cory Quammen]

On behalf of the ParaView development team, I am happy to announce
that ParaView 5.4.1-RC3 is available for download. Binaries and source
code are available from

www.paraview.org/download

The 5.4.1-RC3 bug fix release candidate features a couple improvements
over 5.4.1-RC2:

* A bug in the color mapping that in some cases incorrectly mapped
some data values to the above-range color was fixed.

* OSPRay can now be compiled in Cray programming environments and for
the first time has support for Intel Skylake processors.


Additional fixes since the release of ParaView 5.4.0 include:

* 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

Thanks!
Cory

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

[Paraview] Fix PLOT3D reader

[Jie Cheng]

Hi Eric

Thank you for reporting this bug with a nice example! You can find the
cause and fix of this bug in this merge request
.

Thanks
Jie Cheng
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

[Ibanez, Daniel Alejandro]

Ah, that’s the magic flag.
Thanks, Andy!

From: Andy Bauer 
Date: Wednesday, August 2, 2017 at 10:27 AM
To: "Ibanez, Daniel Alejandro" 
Cc: "paraview@paraview.org" 
Subject: Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

Hi Dan,
In order to work with an install directory you need to enable 
PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I 
personally just use my build directory for linking simulations with Catalyst 
though.
Best,
Andy

On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro 
mailto:daib...@sandia.gov>> wrote:
It seems I can point Albany at my build directory of Catalyst, although I 
wonder why these things aren’t available in the install directory.

From: ParaView 
mailto:paraview-boun...@paraview.org>> on behalf 
of "Ibanez, Daniel Alejandro" mailto:daib...@sandia.gov>>
Date: Wednesday, August 2, 2017 at 9:14 AM
To: "paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: [EXTERNAL] [Paraview] Building Catalyst for Albany

Hello,

I’m trying to revive the integration of Catalyst into the Albany application.
I’ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured 
like this:

#!/bin/bash -ex
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh 
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \
-DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \
-DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \
-DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \
2>&1 | tee config_log

But the install directory doesn’t contain any headers or ParaViewConfig.cmake 
files.
In Albany, the following is done:

find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst)
include("${PARAVIEW_USE_FILE}")

target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst)


Where am I going wrong? What is it I should be installing?

Thanks!

Dan Ibanez

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

[Andy Bauer]

Hi Dan,

In order to work with an install directory you need to enable
PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I
personally just use my build directory for linking simulations with
Catalyst though.

Best,
Andy

On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro <
daib...@sandia.gov> wrote:

> It seems I can point Albany at my *build* directory of Catalyst, although
> I wonder why these things aren’t available in the *install* directory.
>
>
>
> *From: *ParaView  on behalf of "Ibanez,
> Daniel Alejandro" 
> *Date: *Wednesday, August 2, 2017 at 9:14 AM
> *To: *"paraview@paraview.org" 
> *Subject: *[EXTERNAL] [Paraview] Building Catalyst for Albany
>
>
>
> Hello,
>
>
>
> I’m trying to revive the integration of Catalyst into the Albany
> application.
>
> I’ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and
> configured like this:
>
>
>
> #!/bin/bash -ex
>
> $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh
> $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \
>
> -DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \
>
> -DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \
>
> -DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \
>
> 2>&1 | tee config_log
>
>
>
> But the install directory doesn’t contain any headers or
> ParaViewConfig.cmake files.
>
> In Albany, the following is done:
>
>
>
> find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst)
>
> include("${PARAVIEW_USE_FILE}")
>
>
>
> target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst)
>
>
>
>
>
> Where am I going wrong? What is it I should be installing?
>
>
>
> Thanks!
>
>
>
> Dan Ibanez
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

[Ibanez, Daniel Alejandro]

It seems I can point Albany at my build directory of Catalyst, although I 
wonder why these things aren’t available in the install directory.

From: ParaView  on behalf of "Ibanez, Daniel 
Alejandro" 
Date: Wednesday, August 2, 2017 at 9:14 AM
To: "paraview@paraview.org" 
Subject: [EXTERNAL] [Paraview] Building Catalyst for Albany

Hello,

I’m trying to revive the integration of Catalyst into the Albany application.
I’ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured 
like this:

#!/bin/bash -ex
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh 
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \
-DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \
-DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \
-DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \
2>&1 | tee config_log

But the install directory doesn’t contain any headers or ParaViewConfig.cmake 
files.
In Albany, the following is done:

find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst)
include("${PARAVIEW_USE_FILE}")

target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst)


Where am I going wrong? What is it I should be installing?

Thanks!

Dan Ibanez
___
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] Building Catalyst for Albany

[Ibanez, Daniel Alejandro]

Hello,

I’m trying to revive the integration of Catalyst into the Albany application.
I’ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured 
like this:

#!/bin/bash -ex
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh 
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \
-DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \
-DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \
-DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \
2>&1 | tee config_log

But the install directory doesn’t contain any headers or ParaViewConfig.cmake 
files.
In Albany, the following is done:

find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst)
include("${PARAVIEW_USE_FILE}")

target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst)


Where am I going wrong? What is it I should be installing?

Thanks!

Dan Ibanez
___
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