Skip to content
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

Closed
quantumsteve opened this issue Jun 1, 2015 · 5 comments · Fixed by #13024
Closed

Migrate to newer ParaView #12719

quantumsteve opened this issue Jun 1, 2015 · 5 comments · Fixed by #13024
Assignees
Labels
Framework Issues and pull requests related to components in the Framework
Milestone

Comments

@quantumsteve
Copy link
Contributor

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

@quantumsteve quantumsteve added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@quantumsteve quantumsteve self-assigned this Jun 3, 2015
@quantumsteve quantumsteve added this to the Release 3.5 milestone Jun 3, 2015
@quantumsteve
Copy link
Contributor Author

There is something strange with Paraview 4.4 and the VSI. It's as though the signal has disappeared! Perhaps this is related to changes in either the signal or the colormap?

Below is the view at z=-3.5 from slice viewer.
viewfromsliceviewer
Below is the same view at z=-3.5 in the VSI

viewfromvsi

@AntonPiccardoSelg
Copy link
Contributor

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:

  • Have you tried another color map?
  • Does this happen for all views?
  • If you play manually with the limits of the color scale, can you create some differentation in the display color?
  • Have you tried to open this in the "old" Mantid build and checked if this happens? It might be independent of PV4.4

@quantumsteve
Copy link
Contributor Author

  • Yes, I tried several colormaps
  • Yes, it appears to be consistent among all of the views.
  • There is some signal on the order of 10^-7, but it doesn't match the pattern above.
  • I opened and viewed the same dataset in mantid nightly without issue.

@quantumsteve
Copy link
Contributor Author

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.

@quantumsteve
Copy link
Contributor Author

I think the next commit fixes the following warning.

[2651/3054] Building CXX object Vates/VatesSimpleGui/ViewWidgets/CMakeFiles/VatesSimpleGuiViewWidgets.dir/src/ViewBase.cpp.o
/Users/svh/Documents/MantidProject/mantid/Code/Mantid/Vates/VatesSimpleGui/ViewWidgets/src/ViewBase.cpp:86:25: warning: 'getWidget' is deprecated [-Wdeprecated-declarations]
  hbox->addWidget(view->getWidget());
                        ^
/Users/svh/Documents/MantidProject/ParaView/Qt/Core/pqView.h:79:23: note: 'getWidget' has been explicitly marked deprecated here
  VTK_LEGACY(QWidget* getWidget());
                      ^
/Users/svh/Documents/MantidProject/ParaView/VTK/Common/Core/vtkSetGet.h:795:30: note: expanded from macro 'VTK_LEGACY'
#  define VTK_LEGACY(method) method __attribute__((deprecated))
                             ^
1 warning generated.

quantumsteve added a commit that referenced this issue Jul 6, 2015
martyngigg added a commit that referenced this issue Jul 7, 2015
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
martyngigg added a commit that referenced this issue Jul 7, 2015
martyngigg added a commit that referenced this issue Jul 7, 2015
martyngigg added a commit that referenced this issue Jul 7, 2015
martyngigg added a commit that referenced this issue Jul 7, 2015
martyngigg added a commit that referenced this issue Jul 8, 2015
The previous version when to a new NonOrthogonalSource subdirectory
on Windows.
Refs #12719
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants