From cf0c3df81fa0772c00c0b423395f6b6ea56e1a98 Mon Sep 17 00:00:00 2001 From: fhb Date: Sun, 16 Apr 2023 11:45:05 +0200 Subject: [PATCH 1/5] Update NUMBER.MaxRateValue.md The decimal separator used is actually a comma not a point. The code handles an input using a point as the separator and changes the separator to a comma: e.g. 0.05 input to 0,05. I also updated the description of the influence of MaxRateType and included a use case example in the last paragraph. --- .../parameter-pages/PostProcessing/NUMBER.MaxRateValue.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md index 1e8350f..2936cff 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md @@ -1,5 +1,6 @@ # Parameter `.MaxRateValue` -Default Value: `0.05` +Default Value: `0,05` -Maximum change of a reading. -Depending on the settings of `.MaxRateType` it is either treated as `absolute` or `relative`! +Maximum allowed change of a reading, if exceeded the reading will be rejected. Depending on the settings of `.MaxRateType` it is either treated as the difference between the two measurements (AbsoluteChange) not taking the set time interval into account or as the difference per minute (RateChange). + +If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at 600,00 and it's read incorrctly as 610,00, all measurements will be skipped until the counter reaches 610,00. Setting the MaxRateValue to 0,05 leads to a rejection of all readings with a difference > 0,05, in this case 610,00. The rejection also applies to correct readings with a difference > 0,05! From a47b88244f411d91d8f918a492797e066ef4ed90 Mon Sep 17 00:00:00 2001 From: fhb Date: Sun, 16 Apr 2023 11:52:31 +0200 Subject: [PATCH 2/5] Update NUMBER.MaxRateType.md Tried to explain MaxRateType more clearly --- .../parameter-pages/PostProcessing/NUMBER.MaxRateType.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateType.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateType.md index 45da6ad..aab9d29 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateType.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateType.md @@ -1,5 +1,5 @@ # Parameter `.MaxRateType` Default Value: `AbsoluteChange` -Defines if the **Change Rate** compared to the previous value is calculated as absolute change (`AbsoluteChange`) or -as rate normalized to the interval (`RateChange` = change/minute). +Defines if the **Change Rate** is calculated as the difference between the last two readings (`AbsoluteChange` = difference) or +as the difference normalized to the interval (`RateChange` = difference per minute). From 4b5c87e48f4a877c91e93d994ede4fdd9dbf7364 Mon Sep 17 00:00:00 2001 From: fhb Date: Sun, 16 Apr 2023 11:56:04 +0200 Subject: [PATCH 3/5] Update NUMBER.MaxRateValue.md updated the MaxRateType description. --- .../parameter-pages/PostProcessing/NUMBER.MaxRateValue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md index 2936cff..ef48000 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md @@ -1,6 +1,6 @@ # Parameter `.MaxRateValue` Default Value: `0,05` -Maximum allowed change of a reading, if exceeded the reading will be rejected. Depending on the settings of `.MaxRateType` it is either treated as the difference between the two measurements (AbsoluteChange) not taking the set time interval into account or as the difference per minute (RateChange). +Maximum allowed change between two readings, if exceeded the last reading will be rejected. Depending on the settings of `.MaxRateType` the `MaxRateValue` is either treated as the difference between the two measurements (`AbsoluteChange` = difference) not taking the set time interval into account or as the difference normalized to the interval (`RateChange` = difference per minute). If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at 600,00 and it's read incorrctly as 610,00, all measurements will be skipped until the counter reaches 610,00. Setting the MaxRateValue to 0,05 leads to a rejection of all readings with a difference > 0,05, in this case 610,00. The rejection also applies to correct readings with a difference > 0,05! From a22b756bd1fc9b6fe080feec63ee7d8e3e3bb170 Mon Sep 17 00:00:00 2001 From: CaCO3 Date: Sun, 16 Apr 2023 15:46:48 +0200 Subject: [PATCH 4/5] Update param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md --- .../parameter-pages/PostProcessing/NUMBER.MaxRateValue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md index ef48000..c4597de 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md @@ -3,4 +3,4 @@ Default Value: `0,05` Maximum allowed change between two readings, if exceeded the last reading will be rejected. Depending on the settings of `.MaxRateType` the `MaxRateValue` is either treated as the difference between the two measurements (`AbsoluteChange` = difference) not taking the set time interval into account or as the difference normalized to the interval (`RateChange` = difference per minute). -If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at 600,00 and it's read incorrctly as 610,00, all measurements will be skipped until the counter reaches 610,00. Setting the MaxRateValue to 0,05 leads to a rejection of all readings with a difference > 0,05, in this case 610,00. The rejection also applies to correct readings with a difference > 0,05! +If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at `600,00` and it's read incorrctly as` 610,00`, all measurements will be skipped until the counter reaches `610,00`. Setting the MaxRateValue to `0,05` leads to a rejection of all readings with a difference `> 0,05`, in this case `610,00`. The rejection also applies to correct readings with a difference `> 0,05`! From aa9c2232daadcfec82c75f690355d19953cab716 Mon Sep 17 00:00:00 2001 From: fhb Date: Sun, 16 Apr 2023 17:23:40 +0200 Subject: [PATCH 5/5] Update NUMBER.MaxRateValue.md Typo --- .../parameter-pages/PostProcessing/NUMBER.MaxRateValue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md index c4597de..98bb0af 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md @@ -3,4 +3,4 @@ Default Value: `0,05` Maximum allowed change between two readings, if exceeded the last reading will be rejected. Depending on the settings of `.MaxRateType` the `MaxRateValue` is either treated as the difference between the two measurements (`AbsoluteChange` = difference) not taking the set time interval into account or as the difference normalized to the interval (`RateChange` = difference per minute). -If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at `600,00` and it's read incorrctly as` 610,00`, all measurements will be skipped until the counter reaches `610,00`. Setting the MaxRateValue to `0,05` leads to a rejection of all readings with a difference `> 0,05`, in this case `610,00`. The rejection also applies to correct readings with a difference `> 0,05`! +If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at `600,00` and it's read incorrectly as` 610,00`, all measurements will be skipped until the counter reaches `610,00`. Setting the MaxRateValue to `0,05` leads to a rejection of all readings with a difference `> 0,05`, in this case `610,00`. The rejection also applies to correct readings with a difference `> 0,05`!