<br><br><div class="gmail_quote">On Wed, Apr 2, 2008 at 11:47 AM, Moreland, Kenneth <<a href="mailto:kmorel@sandia.gov">kmorel@sandia.gov</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Levent,<br>
<br>
I think I tracked down the problem. It appears that the Gradient and Gradient Magnitude filters pay no attention to the Select Input Scalars parameter. I'm dumfounded about why no one else has run into this problem. I don't want to get into details about the issues, but you can read about them on the bug tracker.<br>
<br>
<a href="http://www.paraview.org/Bug/view.php?id=6706" target="_blank">http://www.paraview.org/Bug/view.php?id=6706</a><br>
<br>
Right now, the workarounds are kind of crummy. Since the image gradient filters work on the active scalars, you can get around the problem by setting some active scalars in your file. For example, if you wanted to take the gradient of the RT array in iter0.vti, you could achieve this by changing the Scalars parameter of the PointData tag to be RT:<br>
<br>
<PointData Scalars="RT"><br>
<br>
Unfortunately, that means you need to change the file every time you want to change the variable you want to perform the gradient on. You could also create a separate file for each variable, but I don't know if that is more cumbersome for you.</blockquote>
<div><br>Thanks for tracking this down Ken. It is cumbersome as you said but this method works(around). <br><br>Levent<br> </div></div><br>-- <br>Server Levent Yilmaz<br>Mechanical Engineering<br>University of Pittsburgh