New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to newer ParaView #12719
Comments
The auto scale checkbox is unchecked. What happens when you check the "Auto Scale" checkbox? It seems though that the range is 2e-3 to 2e-2 for both the SliceViewer and the VSI, so auto scaling will probably have no effect. Things to check:
|
|
It was human error and not some bizarre change in PV. I clicked the wrong download link and got v3.4 instead of nightly. Mantid nightly has the same issues auto-selecting the correct normalization. The normalization selection isn't a PV 4.4-specific issue, I created a separate issue #12832. |
I think the next commit fixes the following warning.
|
The solution is far from ideal but there seems to be no generic way of retrieving the location of the RUNTIME library from the ParaView CMake as the plugins do not define importable targets. Refs #12719
The previous version when to a new NonOrthogonalSource subdirectory on Windows. Refs #12719
This issue was originally TRAC 11881
We would like to move VATES from ParaView 4.3.1 to a later snapshot so that we can use the new features from our latest contract and also ease our move to ParaView 5. The SHA1 Utkarsh suggests is
b40280a2f274aa27aac707abf9097317f731dcc1
from May 31, 2015The text was updated successfully, but these errors were encountered: