# vector field visualisation

**URL:** https://discourse.paraview.org/t/vector-field-visualisation/11904
**Category:** ParaView Support
**Created:** [April 17, 2023, 9:04am UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904 "2023-04-17T09:04:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Rigel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@Rigel](https://discourse.paraview.org/u/Rigel)
#### Post date: [April 17, 2023, 9:04am UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904/1 "2023-04-17T09:04:05Z")

</div>

Hi,

I am having problems to properly visualise a 3D vector (namely, the velocity) field in ParaView. If I select one of the components from the vector, I get the following view:

 ![Captura de tela de 2023-04-17 10-55-55](https://discourse.paraview.org/uploads/default/original/2X/8/88dd6e70aedc3d9d2ce67e7caa8bec152b57b3ff.png)

However, if I create a new array using the Calculator Filter, which is just the same component of the same vector, I get the following view (for the very same time step):

 ![Captura de tela de 2023-04-17 10-56-25](https://discourse.paraview.org/uploads/default/original/2X/e/e1f63bdcbdae1023bc9ab17db84308d26d74cb7c.png)

Am I doing something wrong? Is it a bug in the ParaView filters’ pipelining?

Thanks a lot,

---

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [April 17, 2023, 12:48pm UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904/2 "2023-04-17T12:48:29Z")

</div>

It looks like the data is the same, but the color map scaling is different. If you look at the color scale for your first image (the one showing the `X` component of the `U` vectors), you will see that it goes from -15 to 17.

![Captura de tela de 2023-04-17 10-55-55](https://discourse.paraview.org/uploads/default/original/2X/7/7d83155f463bc61d41c4601b7ea37d264e16c4ef.png)

In comparison, the color scale for the output of the field from the `Calculator` filter goes from -11 to 3.7.

![Captura de tela de 2023-04-17 10-56-25](https://discourse.paraview.org/uploads/default/original/2X/b/b3ae92a2ffc54643594e877a023594d994d740d9.png)

Because the output of the calculator filter is narrower, you are seeing more detail. Try using the `Rescale to Data Range` ![image](https://discourse.paraview.org/uploads/default/original/2X/b/beac3eace6a61572242a181ab5b20da5bfad2c2e.png) or `Rescale to Custom Range` ![image](https://discourse.paraview.org/uploads/default/original/2X/7/7065498780971a02dae08d71870d71c0280ba8ae.png) to get the ranges to match up.

I can’t say for sure why ParaView scaled the two fields differently, but it might have been that you ran an animation showing one but not the other.

---

<div class="post-metadata">

### Author: ![Rigel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@Rigel](https://discourse.paraview.org/u/Rigel)
#### Post date: [April 17, 2023, 3:20pm UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904/3 "2023-04-17T15:20:24Z")

</div>

Thank you very much Kenneth for your reply. Indeed, the color scales are different; but I clicked on `Rescale to Data Range` before producing the pictures above. In fact, this is the “natural” scaling applied by ParaView when selecting the desired data array (none of the pictures come from an animation).

---

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [April 17, 2023, 3:37pm UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904/4 "2023-04-17T15:37:04Z")

</div>

What happens when you click on the `Rescale to Visible Data Range` ![image](https://discourse.paraview.org/uploads/default/original/2X/7/703d9452279c26ee38feed49ac041a1d54b02988.png) on each?

---

<div class="post-metadata">

### Author: ![Rigel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@Rigel](https://discourse.paraview.org/u/Rigel)
#### Post date: [April 18, 2023, 8:08am UTC](https://discourse.paraview.org/t/vector-field-visualisation/11904/5 "2023-04-18T08:08:44Z")

</div>

Same problem. For example, here in another data set (from another simulation in another geometry): component _x_ of vector:

 ![Captura de tela de 2023-04-18 10-02-02](https://discourse.paraview.org/uploads/default/original/2X/4/4274c1161a09a600cb0e79ee43c50efb37f90654.png)

Same component, but extracted with a Calculator Filter:

 ![Captura de tela de 2023-04-18 10-03-00](https://discourse.paraview.org/uploads/default/original/2X/2/2f6bdb4ec6e57e8632c4d70eb6c97646cb23c6b0.png)

I clicked on `Rescale to Visible Data Range` before producing the snapshots.

We can see that in both cases I presented there is the application of Slices. Not sure if it is related to the issue…