Ticket #7875 (closed: fixed)
Add time average to "Sample Logs..." window
Reported by: | Peter Peterson | Owned by: | Peter Peterson |
---|---|---|---|
Priority: | major | Milestone: | Release 3.0 |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Reuter |
Description (last modified by Peter Peterson) (diff)
This has two components:
- Add a timeAverageValue() to TimeSeriesProperty. The start of this method is hiding in averageValueInFilter.
- Expose the new method to python
- Show the result in the window as an additional value. If something is not a TimeSeriesProperty then this field should be blank.
Change History
comment:2 Changed 7 years ago by Peter Peterson
- Status changed from new to inprogress
Re #7875. Adding TimeSeriesProperty::timeAverageValue
Changeset: 8d5afdf258110df511f558dde287c06183b3f276
comment:3 Changed 7 years ago by Peter Peterson
Re #7875. Exposing TimeSeriesProperty::timeAverageValue to python.
Changeset: de163f65e5888d99eb08dfeb22946fa19c5a1b44
comment:4 Changed 7 years ago by Peter Peterson
Re #7875. Added time average value to sample log window.
Changeset: fcf34654f6a8ed381256a2479023cd59ad1bd15c
comment:5 Changed 7 years ago by Peter Peterson
- Status changed from inprogress to verify
- Resolution set to fixed
This is on feature/7875_time_avg_value.
To test: This can be tried with other values, but I found a run and log that shows a difference since that is harder to find.
- Load SEQ_32464_event.nxs
- Right-click the workspace and see "Sample Logs..."
- Plot the log "svpressure" and look at the statistics for it. Since there is the same number of values at the min and max, the average is just halfway between. The time-average is lower because there is more time spent at the minimum value.
comment:6 Changed 7 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
Note: See
TracTickets for help on using
tickets.