Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed minimum/maximum calculate in Meta Data Point script #2770

Closed
Limraj opened this issue Nov 16, 2023 · 0 comments
Closed

Fixed minimum/maximum calculate in Meta Data Point script #2770

Limraj opened this issue Nov 16, 2023 · 0 comments
Assignees
@Limraj
Labels
bug high priority
Milestone
2.7.7

Comments

@Limraj
Copy link
Collaborator

Limraj commented Nov 16, 2023 •
edited
Loading

Description
Fixed minimum/maximum calculate in Meta Data Point script.

To Reproduce
Steps to reproduce the behavior:

  1. Login as admin;
  2. Created Virtual Data Source as virtual_ds_1 (enabled, update: 1s) and Virtual Data Point as virtual_dp_1 (enabled, numeric, change type: increment (min: 0 - max: 10 - change: 1, checked roll, start: 0))
  3. Created Meta Data as meta_ds_1 (enabled) and Meta Data Point meta_dp_1 (enabled, numeric) with:
    a) Script context add: 'virtual_ds_1 - virtual_dp_1 ' as p1;
    b) Script: return p1.prev(SECOND,11).minimum;
    c) Event Update: Update Context;
  4. Created WatchLists as wl_1 with points: 'meta_ds_1 - meta_dp_1', 'virtual_ds_1 - virtual_dp_1';
  5. Then 'meta_ds_1 - meta_dp_1' value is 0 -> ok;
  6. Change 'virtual_ds_1 - virtual_dp_1' -> set 5 in increment.min;
  7. Go back to wl_1 and wait 10s then 'meta_ds_1 - meta_dp_1' value is 0 -> error;

Spec:

  • Scada-LTS Version 2.6.18
@Limraj Limraj added the bug label Nov 16, 2023
@Limraj Limraj added this to the 2.7.7 milestone Nov 16, 2023
@Limraj Limraj self-assigned this Nov 16, 2023
Limraj added a commit that referenced this issue Nov 16, 2023
@Limraj
#2770 Fixed minimum/maximum calculate in Meta Data Point script - 'de…
9a53c7a 
…sc' was added to the PointValueDAO.POINT_VALUE_FILTER_BEFORE_TIME_STAMP_BASE_ON_DATA_POINT_ID query at the end, now the start value used to calculate statistics should be correct and should not result in incorrect statistics calculation;
Limraj added a commit that referenced this issue Nov 17, 2023
@Limraj
Merge pull request #2771 from SCADA-LTS/fix/#2770_Fixed_minimum/maxim…
11407ae 
…um_calculate_in_Meta_Data_Point_script

#2770 Fixed minimum/maximum calculate in Meta Data Point script - 'de…
@Limraj Limraj closed this as completed Nov 17, 2023
Limraj added a commit that referenced this issue Jan 8, 2024
@Limraj
#2770 Fixed minimum/maximum calculate in Meta Data Point script - cor…
ea322c5 
…rected performance
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Limraj Limraj

Labels
bug high priority
Projects
None yet
Milestone
2.7.7
Development

No branches or pull requests
1 participant
@Limraj