Mirror/AI-on-the-edge-device-docs
1
0
Fork 0
mirror of https://github.com/jomjol/AI-on-the-edge-device-docs.git synced 2025-12-08 20:46:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 05c0e80 with MkDocs version: 1.6.1

Browse Source
This commit is contained in:
github-actions[bot]
2025-04-16 19:02:06 +00:00
parent 9996a8e8ad
commit 62b1d549c5
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Correction Algorithm/index.html
View File

@@ -876,7 +876,7 @@
</ol>
<h3 id="terms-and-definitions"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1</span> Terms and definitions</h3>
<h5 id="prevalue"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1.0.1</span> PreValue</h5>
<p>The last correct read value. PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check nagtive rates, high rates (MaxRateValue / MaxRateType) and CCheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
<p>The last correct read value. PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check negative rates, high rates (MaxRateValue / MaxRateType) and CCheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
<h5 id="digits"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1.0.2</span> Digits</h5>
<p>Value that are digitized from a digit number. There are 11 allowed values for this: </p>
<ol>

2
FAQs/index.html
View File

@@ -882,7 +882,7 @@
So please be a bit patient with your meter :-)</li>
</ul>
<h2 id="pre-value"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.7</span> Pre-Value</h2>
<p>PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check nagtive rates, high rates (MaxRateValue / MaxRateType) and CheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
<p>PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check negative rates, high rates (MaxRateValue / MaxRateType) and CheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
<p>If you use post processes, enable the pre-value. The pre-value must be set at first time. Set it to the current raw value. </p>
<p>If the device runs in errors, the pre-value will not be updated, as long as the <code>preValueAgeStartup</code> time between the last valid value (or startup time) and current time is not exceeded. After it the preValue will be set again, if no other error occured. So the device can not run in an endless error, like high rate.</p>
<h2 id="rate-too-high-read"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.8</span> "Rate too high - Read: ..."</h2>

2
search/search_index.json
View File

File diff suppressed because one or more lines are too long