Skip to content
This repository has been archived by the owner on Feb 19, 2022. It is now read-only.

TODO #4

Open
8 of 26 tasks
jvanstraten opened this issue Oct 23, 2019 · 0 comments
Open
8 of 26 tasks

TODO #4

jvanstraten opened this issue Oct 23, 2019 · 0 comments

Comments

@jvanstraten
Copy link
Collaborator

jvanstraten commented Oct 23, 2019

List of things to do (also includes nice-to-haves)

Web interface

  • add links to wikipedia articles
  • cache images retrieved from wikipedia's API locally for increased speed
  • allow running both software and hardware implementations automatically
  • bar plot for hardware vs software
    • rudimentary implementation
    • tick marks (probably requires some kind of plotting device)
    • don't rely on javascript setInterval() accuracy for animation (chromium seems to be accurate, waterfox is not)
    • implement websocket-based push notifications to allow the web app to delay starting the bar graph timer until the run actually starts
  • locking the server to allow multiple client connections
    • a proper queue?
  • language switching
  • status display
    • rudimentary server status display using polling
    • handle and indicate errors when the server goes offline, and automatically restart polling or show a button to do so
    • use websocket-based push notifications for the status display
    • add CPU utilization meter (this is easier if there is just some thread running that generates the push notifications, because of the required averaging window)
    • make a nice plot instead of just having bars
  • proper error handling (right now, the client tries to interpret a failure message as JSON, so the script crashes)
  • demo-mode that automatically requests things every so often
  • architecture/information page(s)

FPGA implementation

  • allow pattern matching (wildcards etc)
  • actually fill up the FPGA to get more performance
    • figure out why memory is bottlenecking at around 50% theoretical (burst size, probably)
    • four instead of three subkernels, or do a simpler kind of duplication

Clean up

  • make sure readme is up-to-date
  • move to abs-tudelft, open repository
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant