Ticket #8212 (assigned)

Opened 7 years ago

Last modified 5 years ago

Event Filtering can leave 0 log entries

Reported by: Nick Draper Owned by: Wenduo Zhou
Priority: critical Milestone: Backlog
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester:


Reported by Rob Dlagleish.

This definitely happens with filtering by log, but might happen with time and filterevents as well.

If you filter the data fine enough so that loging on change does not have an entry within the filtered region you get 0 entries in the log while we should be propogating the last valid log value in (for each filtered section).



r= ws.getRun()
time_array = r.getLogData("proton_charge").times
value_array = r.getLogData("proton_charge").value


Change History

comment:1 Changed 7 years ago by Nick Draper

This case is when the logs only log the value on change, and there were no changes in the filtered period. So the fix is to propagate the last valid value into the start of the filtered period.

comment:2 Changed 7 years ago by Nick Draper

  • Owner set to Wenduo Zhou

comment:3 Changed 7 years ago by Wenduo Zhou

  • Milestone changed from Release 3.1 to Backlog

comment:4 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 9057

Note: See TracTickets for help on using tickets.