Skip to content

Latest commit

 

History

History
122 lines (72 loc) · 3.89 KB

TODO.md

File metadata and controls

122 lines (72 loc) · 3.89 KB

C2DataViewer TODO list

TODO

  • Remove hard code EPICS7 PV field names [Done]

Currently there are some hard coded field names, which are inherited from old code, for example "ArrayId".

  • User selectable/configurable EPICS field name [Done]

Provide a mechanism to allow user to configure X axes. If it is not provided, it will use data count for the plotting.

It could be from command line, or selectable from drop down menu.

  • Use time diff as X axes [Done]

    • Allow user to select time axis

  • Image initial resize and auto gain control [Done]

  • Separate UI from data source for image [Done]

  • Bug fix when changing frame rate and/or camera [Done]

  • Show statistics data for Scope [Done]

  • Add histogram support [Done]

  • Add Binning support [Done]

  • Support different plotting

    • FFT [Done]
    • PSD [Done]
    • Diff [Done]
    • X vs Y

  • Filtering function [Done]

Filter out data which is out of user specified range (max & min)

  • Keep latest plot when stopping plotting [Done]

  • BUG: buffer size from configuration is not initialized properly. [Done]

  • ENH: Improve model handling: merge pvAccess layer for different application into one class. [Done]

  • ENH: Handling channel connection time out in a more proper way instead of crashing [Done]

  • ENH: Handling empty image channel with no data inside in a more proper way instead of crashing [Done]

  • Handle PV disconnection in a more proper way [Done]

When a PV disconnected in the middle, data source (scope_data.py) throws out a RuntimeError, which is proper. Currently the UI does not catch that exception, which causes the UI crash. This behavior shall be improved to make the application more robust. A popup window shall be used instead of crashing the application.

  • ENH: move exception handling to controller [Done]

  • Add trigger support [Done]

Support an external PV which behaviors like a trigger. It currently takes an EPICS3 binary-like PV. The trigger function will be enable when a trigger PV name is given, and trigger mode is enabled. When the value of given trigger PV changed from 0 to 1, it triggers the Scope to capture data to until the 2nd half of buffer filled up. Once the buffer is captured, it stops data capturing, and displays data for scope. The event from trigger PV is ignored in the following cases:

  1. trigger changes from 1 to 0;
  2. trigger stays at value 1.

When Scope goes from data capturing mode to data off capturing mode, the UI shall uncheck the start checkbox.

The external trigger support is for scope application currently, and does not work for image yet.

Advanced function to be implemented later:

  1. Time period requirements to hold trigger after valid trigger event;
  2. Customized time for taking data after valid trigger event.

  • Support trigger pv from command line [Done]

  • User adjustable DC offset for all channels [Done]

  • Add trigger position in plotting [Done]

  • Utilize time stamp to determine trigger position [Done]

  • Handle trigger with ai/ao, and select trigger level [Done]

  • Handle trigger for the same rising edge Once the trigger event is processed, the current implementation will generate another trigger even the trigger signal is on the sme rising edge.

  • User selectable trigger edge (rising, falling, or both)

  • Support post trigger

Need to clarify the requirements

  • Support hold trigger

Need to clarify the requirements, how this work together with different EPICS record types.

  • Use trigger (different) field embedded within same EPICS7 record

  • APSU LLRF FFT requirement support

  • Support waveform plotting driven by IOC

  • Strip plotting

  • INtegration with PyDM

  • Bug to fix updating rate drop caused by CPU spark during resizing for image

  • Plot against multiple vertical axes

    • Discussed, and decided to gather more requirements first before coding.

  • Unit test suite

  • CI testing integration

  • Logging for error and warning message