Commit d48be47e authored by Mathieu Westphal's avatar Mathieu Westphal Committed by Kitware Robot

Merge topic 'UseSeparateColorMap'

7a11a712 UseSeparateColorMap doc
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Reviewed-by: Cory Quammen's avatarCory Quammen <cory.quammen@kitware.com>
Merge-request: !67
parents e04a35a7 7a11a712
Pipeline #73540 passed with stage
in 0 seconds
......@@ -30,7 +30,8 @@ In \ParaView, you can set up a transfer function for each data array
for both color and opacity separately. \ParaView associates a transfer function
with the data array identified by its name. The same transfer function is used
when coloring with the same array in different 3D views or results from
different stages in the pipeline.
different stages in the pipeline. You can also use \ref{SeparateColorMap}
to have independant color map by array name and representation.
For arrays with more than one component, such as vectors or tensors, you can
specify whether to use the magnitude or a specific component for the
......@@ -46,9 +47,8 @@ opacity and color, but also the component/magnitude selection.
a dataset being shown in one view affects other views as well. Using different
transfer functions for the same variable is discouraged by design in \ParaView,
since it can lead to the misinterpretation of values. If you want to use different
transfer functions, despite this caveat, you can use a filter like the
\ui{Calculator} or \ui{Programmable Filter} to rename the array and then use a
different transfer function for it.
transfer functions, despite this caveat, you can use the Separate Color Map feature
(see \ref{SeparateColorMap}).
\end{commonerrors}
There are separate transfer functions for color and opacity. The opacity
......@@ -150,6 +150,74 @@ default for all arrays. Note that this will not affect transfer
functions already setup. Also this is saved across sessions,
so \ParaView will remember this even after restart.
\subsection{Separate Color Map}\label{SeparateColorMap}
\begin{figure}[htb]
\begin{center}
\includegraphics[width=0.7\linewidth]{Images/ParaView_UsersGuide_SeparateColorMap.png}
\label{fig:separatecolormap}
\caption{The Separate Color Map button}
\end{center}
\end{figure}
In order to force \ParaView to use a separate color map on the current Active Representation,
click on the button shown in Figure~\ref{fig:separatecolormap}. A separate color map
is not shared across representations by name, but is instead uniquely associated with the array
name and the representation.
This can also easily be done in python:
\begin{python}
from paraview.simple import *
Wavelet()
wavelet1Display = Show()
wavelet1Display.SetRepresentationType('Surface')
# set scalar coloring
ColorBy(wavelet1Display, 'RTData')
# set the usage of a Separate Color Map
wavelet1Display.UseSeparateColorMap = True
# or use the ColorBy interface directly
ColorBy(wavelet1Display, 'RTData', separate = True)
# display the same data in another view for comparison with different color map
# get layout
layout1 = GetLayout()
# split cell
layout1.SplitHorizontal(0, 0.5)
renderView1 = GetActiveView()
# Create a new 'Render View'
renderView2 = CreateView('RenderView')
# place view in the layout
layout1.AssignView(2, renderView2)
# set active view
SetActiveView(renderView2)
wavelet2Display = Show()
wavelet2Display.SetRepresentationType('Surface')
# Use the ColorBy interface to create a separated color map
ColorBy(wavelet2Display, 'RTData', separate = True)
# get separate color transfer function/color map for 'RTData'
separate_wavelet2Display_RTDataLUT = GetColorTransferFunction('RTData', wavelet2Display, separate=True)
# Apply a preset using its name.
separate_wavelet2Display_RTDataLUT.ApplyPreset('Cold and Hot', True)
ResetCamera(renderView1)
ResetCamera(renderView2)
RenderAllViews()
\end{python}
\subsection{Mapping data}
\label{sec:ColorMapping:MappingData}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment