# Scalar, vector, tensor, texture and norm fields from vtk file

**URL:** https://discourse.paraview.org/t/scalar-vector-tensor-texture-and-norm-fields-from-vtk-file/14895
**Category:** ParaView Support
**Tags:** vtk
**Created:** [June 20, 2024, 5:29pm UTC](https://discourse.paraview.org/t/scalar-vector-tensor-texture-and-norm-fields-from-vtk-file/14895 "2024-06-20T17:29:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jpmorr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jpmorr/32/8745_2.png) [@jpmorr](https://discourse.paraview.org/u/jpmorr)
#### Post date: [June 20, 2024, 5:29pm UTC](https://discourse.paraview.org/t/scalar-vector-tensor-texture-and-norm-fields-from-vtk-file/14895/1 "2024-06-20T17:29:33Z")

</div>

I’m writing results data out to various xml file formats (vti, vtu, vtp) depending on simulation data but regardless of whether it’s point or cell data, I usually have multiple scalars or vectors in the data and occasionally some tensors such as stress/strain.

While `vtk` files support “active” `Scalars`, `Vectors`, etc, I’m not quite sure how `paraview` deals with this information. For example, in the following example file, I have a few different types of `DataArray`s but I can’t see any difference in how `vtk` or `paraview` are differentiating between `Normals` and `Vectors` or even just some result which has 2,3 or 4 components. In my dataset I’m calling these multi-component scalars because they containing things like counters or percentage limits for results such as “failure mode” which may have several different modes (1,2,3,4, etc) but don’t have a magnitude and should be grouped together.

How are `vtk`/`paraview` differentiating? Does it just use the number of components? A single component is always scalar, 2-component is a texture, 3-5 is a vector and 6 or 9 are shown as tensors. I’ve also been experimenting with using some named components to help differentiate some of these multi-component scalars and by grouping them all under `active Scalars` in the vtk file which mean that when the are loaded in paraview the first component is always loaded first in the drop-down but I still see the magnitude option.

And the magnitude option still seems to be enabled for the `Normals` data, which seems somewhat redundant since everything will be 1 anyway. Can this also be disabled or controlled from within the `vtk ` files or is it a paraview setting that needs to be specified?

[test\_uniform\_image\_data\_3.vti](https://discourse.paraview.org/uploads/short-url/5bqC7OT8FJPrAENFbd0hwh6KNhF.vti) (40.8 KB)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 21, 2024, 7:28am UTC](https://discourse.paraview.org/t/scalar-vector-tensor-texture-and-norm-fields-from-vtk-file/14895/2 "2024-06-21T07:28:30Z")

</div>

> [@jpmorr](#):
>
> While `vtk` files support “active” `Scalars`, `Vectors`, etc, I’m not quite sure how `paraview` deals with this information.

Simple, ParaView mostly ignore those fields and let users specify which field they want to visualize and which field filter should apply on.

Do you have any specific issue with that behavior ?
