# Doubts about Historical

**URL:** <https://forum.inductiveautomation.com/t/doubts-about-historical/40577>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [November 12, 2020, 12:03pm UTC](https://forum.inductiveautomation.com/t/doubts-about-historical/40577 "2020-11-12T12:03:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![informatica](https://avatars.discourse-cdn.com/v4/letter/i/3ab097/32.png) [@informatica](https://forum.inductiveautomation.com/u/informatica)\
**Post date:** [November 12, 2020, 12:03pm UTC](https://forum.inductiveautomation.com/t/doubts-about-historical/40577/1 "2020-11-12T12:03:41Z")

</div>

Good Morning.

1. In a **Easy Chart** , in the “_ **Tag History Resolution Mode** _”, which is the different between **Natural** and **Raw** mode. Can you explain it with an example, please?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/5/558933e54a6587443bfac8c334eaac8dc78d39f2.png)

1. If a **Tag Group** (Scan Class) is configured to historize tags with **Direct** mode, then the **History options** are ignored? I understand that the tags will be recorded at the indicated **rate** , regardless of the Min Time and Max Time.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/5/f53a2d0c38624964d1f80e44fc707d48246d6f57.png)

Best regards.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 12, 2020, 4:00pm UTC](https://forum.inductiveautomation.com/t/doubts-about-historical/40577/2 "2020-11-12T16:00:54Z")

</div>

> [@informatica](#):
>
> In a **Easy Chart** , in the “ _ **Tag History Resolution Mode** _ ”, which is the different between **Natural** and **Raw** mode. Can you explain it with an example, please?

Natural means that the results dataset will have a value corresponding to each expected execution of the scan class. Due to the historian's storage optimization, there won't be an _actual_ row of data in the database, but natural mode will essentially 'reverse' the storage optimization and give you a point of data for each expected row per the scan class.

Raw mode will return _only the actual data that is stored in the database_. You can still reverse this into the expected results by reversing the sliding window algorithm yourself, but it's probably easier to do use 'natural' mode if you expect to use this data elsewhere.

> [@informatica](#):
>
> If a **Tag Group** (Scan Class) is configured to historize tags with **Direct** mode, then the **History options** are ignored? I understand that the tags will be recorded at the indicated **rate** , regardless of the Min Time and Max Time.

Not exactly. When driving tag history, the scan class indicates how often the system should decide to store a point - but a rate of 1 second (or 10 seconds, or anything else) does not, by itself, mean that a data point will actually be stored into the database every 1, 10, etc seconds.  
[https://docs.inductiveautomation.com/display/DOC81/Configuring+Tag+History#ConfiguringTagHistory-MaxandMinTimeBetweenSamples](https://docs.inductiveautomation.com/display/DOC81/Configuring+Tag+History#ConfiguringTagHistory-MaxandMinTimeBetweenSamples)  
That manual page goes into more detail. The short version is you can override the sliding window algorithm behavior to force an actual row to be logged by using the min/max time settings.