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.

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

Version 0.2 checklist #8

Open
18 of 24 tasks
sthenic opened this issue Apr 4, 2023 · 0 comments
Open
18 of 24 tasks

Version 0.2 checklist #8

sthenic opened this issue Apr 4, 2023 · 0 comments

Comments

@sthenic
Copy link
Owner

sthenic commented Apr 4, 2023

  • Time domain marker frequency conversion (1 / dT)
  • Limit data rate (trigger blocking)?
  • Max hold (maximum for each bin in the FFT)
  • Implement the waveform memory all the way (make global like the markers)
  • Save sensor data to file
  • Propagate const ProcessedRecord from the processing thread.
  • Add valid bit to metrics (don't show bad frequency metrics).
  • Record frames
    • One selected record index within the frame
    • Plot all records on top of each other (persistence-ish)
    • Only update the plot when all information is available (lower perceived trigger rate).
  • Add firmware name to configuration filename
  • Allow clock system actions in acquisition state
  • FWPD integration
    • Use dynamic length in transfer interface
    • Implement nof_acquisition_channels/nof_transfer_channels
    • Figure out how to visualize the attribute data. In metric view I guess? Need more sophisticated masking.
  • Make the screenshot path more discoverable/configurable somehow.
  • Don't clear the FFT processing on Start/Stop (ever?)
  • Rework the Python embedding (message thread + reinitialize the interpreter between scripts)
  • Synchronize parameter files after calling Python
    • Special return value or always?
  • Statistics for time domain metrics (mean, min, max etc.) cleared manually?
  • Still some issue w/ harmonic analysis on max-hold buffer?
  • Tooltips for solo and mute buttons.
  • Validate pyadq compatibility
@sthenic sthenic mentioned this issue Apr 4, 2023
64 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant