Event Filtering can leave 0 log entries

[NickDraper]

This issue was originally TRAC 8212

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).

rnum=28511

Load(str(rnum),OutputWorkspace=str(rnum),LoadMonitors='1')

ws=mtd[str(rnum)]
r= ws.getRun()
time_array = r.getLogData("proton_charge").times
value_array = r.getLogData("proton_charge").value

FilterByLogValue(str(rnum),'Theta',0.295,0.305,OutputWorkspace=str(rnum)+"_03deg")
Rebin(str(rnum)+"_03deg","5.0,20.0,100000.0",PreserveEvents=0,OutputWorkspace=str(rnum)+"_03deg_Hist")

[NickDraper]

@NickDraper (2013-11-06T15:16:27):
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.

---

@NickDraper (2014-02-14T11:04:54):
Bulk move to assigned at the introduction of the triage step

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.