# \[Proposition\] Using an Information Property to optimize ResetScalarRangeToDataOverTime

**URL:** https://discourse.paraview.org/t/proposition-using-an-information-property-to-optimize-resetscalarrangetodataovertime/9614
**Category:** Development
**Created:** [May 11, 2022, 2:01pm UTC](https://discourse.paraview.org/t/proposition-using-an-information-property-to-optimize-resetscalarrangetodataovertime/9614 "2022-05-11T14:01:30Z")
**Posts on this page:** 3
**Page:** 1

<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: [May 11, 2022, 2:01pm UTC](https://discourse.paraview.org/t/proposition-using-an-information-property-to-optimize-resetscalarrangetodataovertime/9614/1 "2022-05-11T14:01:30Z")

</div>

This is a follow up of a previous post on [VTK discourse](https://discourse.vtk.org/t/adding-an-arrays-range-over-time-information-key-in-vtkdataobject/8398)

# Use case

We read some temporal data. For the visualization we choose an array and we want to setup a lookup table with the union of all the data ranges over time, i.e. we use the `Rescale to data range over all timesteps` button.

For now each timestep is read successively and ranges are aggregate to get the union.

In the specific case where the reader knows about this data range over time, we would like to avoid this loop over timesteps to save a lot of time and resources.

# Proposal

The `pqResetScalarRangeReaction::resetScalarToDataRangeOverTime` may look for a “new” `InformationProperty` called `ArraysRangeOverTime` to get this information from the reader and reuse it if present.

_edit_  
as @mwestphal suggests, we can also use an Information Property for (non-temporal) ranges, for consistency.

# Details

This optimization will be available for each source proxy containing the relevant `InformationProperty`, but it is more expected to have it on the reader.  
For further filter in the pipeline, one can look for the property in the panel and do a manual `Reset To Custom Range` if relevant.

Thought ?

---

<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: [May 11, 2022, 2:01pm UTC](https://discourse.paraview.org/t/proposition-using-an-information-property-to-optimize-resetscalarrangetodataovertime/9614/2 "2022-05-11T14:01:44Z")

</div>

@utkarsh.ayachit@mwestphal

---

<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: [May 11, 2022, 2:02pm UTC](https://discourse.paraview.org/t/proposition-using-an-information-property-to-optimize-resetscalarrangetodataovertime/9614/3 "2022-05-11T14:02:46Z")

</div>

I think that providing a ArrayRange information prop could also make sense.
