You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a maintainers of the platform, we want to have a visible dataset on how many rejected data is there. I want to be able to run analysis on this data. For business purposes it would be great if we can do this. so that I can I can measure the performance and quality of the verification algorithm.
Acceptance Criteria
Given When user enter rejected Reads,
Then this read get persisted somewhere accessible for analytics.
Additional Information
Currently, when users enter MeterReads on the D-REC platform the platform checks on-the-fly where these are valid or not using the implemented validation algorithm.
Ideas:
Persist rejected MeterReads into a different InfluxDB table
The text was updated successfully, but these errors were encountered:
As a maintainers of the platform, we want to have a visible dataset on how many rejected data is there.
I want to be able to run analysis on this data. For business purposes it would be great if we can do this.
so that I can I can measure the performance and quality of the verification algorithm.
Acceptance Criteria
Additional Information
Currently, when users enter MeterReads on the D-REC platform the platform checks on-the-fly where these are valid or not using the implemented validation algorithm.
Ideas:
The text was updated successfully, but these errors were encountered: