# Change display format of decimals in Statistics Inspector

**URL:** https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044
**Category:** ParaView Support
**Tags:** vtk
**Created:** [July 12, 2024, 10:26am UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044 "2024-07-12T10:26:09Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![mmros](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/m/8baadc/32.png) [@mmros](https://discourse.paraview.org/u/mmros)
#### Post date: [July 12, 2024, 10:26am UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044/1 "2024-07-12T10:26:10Z")

</div>

Good day. I’m displaying in Paraview 5.11.1 some .vtk files that comes from cellSets of a openfoam mesh. I use Sources \> Statistics Inspector to read the bounding box of each .vtk and manually compute the center point of the cellSet. Happens that sometimes, coordinates are in the order of 1000 in value and the format of displaying is 1 position + 10³ values on this column and does not show enough detail to make a precise calculation of middle value.  
Is there a way I can change the # of decimals to be displayed in ‘Spatial Bounds’ ?

 ![Screenshot from 2024-07-12 12-20-36](https://discourse.paraview.org/uploads/default/original/2X/3/358869104b47566ce8eb6ad2f5fbc7478ec0f9b5.png)

---

<div class="post-metadata">

### Author: ![nicolas.vuaille](https://discourse.paraview.org/user_avatar/discourse.paraview.org/nicolas.vuaille/32/5873_2.png) [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [July 12, 2024, 1:48pm UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044/2 "2024-07-12T13:48:31Z")

</div>

It looks like the Statistic Insptector does not honor the `Real number Display Notation / Precision` settings. (I reproduced with last version of ParaView).

You may want to open an issue here : [https://gitlab.kitware.com/paraview/paraview/-/issues/new](https://gitlab.kitware.com/paraview/paraview/-/issues/new)

Thanks for reporting!

---

<div class="post-metadata">

### Author: ![mmros](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/m/8baadc/32.png) [@mmros](https://discourse.paraview.org/u/mmros)
#### Post date: [July 12, 2024, 2:03pm UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044/3 "2024-07-12T14:03:05Z")

</div>

Hi Nicolas, thanks for sharing the link.  
By the way, do you know if there is a way to gather via Paraview using Python (without GIU) the ‘spatial bounds’ of an object? I always do this manually, opening GIU and taking notes of the values displayed, I have not found yet how this task can be automized, any recommendations are welcome.

---

<div class="post-metadata">

### Author: ![nicolas.vuaille](https://discourse.paraview.org/user_avatar/discourse.paraview.org/nicolas.vuaille/32/5873_2.png) [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [July 12, 2024, 3:05pm UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044/4 "2024-07-12T15:05:08Z")

</div>

Yes it is possible!

Please have a look at the `DataInformation` mechanism [3. Understanding Data — ParaView Documentation 5.12.0 documentation](https://docs.paraview.org/en/latest/UsersGuide/understandingData.html#getting-data-information-in-pvpython)

---

<div class="post-metadata">

### Author: ![nicolas.vuaille](https://discourse.paraview.org/user_avatar/discourse.paraview.org/nicolas.vuaille/32/5873_2.png) [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [July 15, 2024, 11:40am UTC](https://discourse.paraview.org/t/change-display-format-of-decimals-in-statistics-inspector/15044/5 "2024-07-15T11:40:51Z")

</div>

For future ref, the corresponding issue is here: [https://gitlab.kitware.com/paraview/paraview/-/issues/22697](https://gitlab.kitware.com/paraview/paraview/-/issues/22697)