This week, now that the FPGA has both been setup and connected to the campus wifi network, we could easily complete all parts individually without having to pass the FPGA around.
We architected an alternate approach to multi-client based response that operates with the scheduler on the client side rather than the server side of things:
- When the FPGA receives a query, it sets an “in-use” flag on and starts operating on that query.
- Before the client sends a query to the FPGA, it checks the in-use flag.
- Waits till the in-use flag turns off before actually sending the query.
This system leaves it vulnerable to race conditions, but we have decided to accept that minor flaw.
Andrew worked on running the model on the FPGA.
Anirudh setup a basic answer system and the in-use flag requirement.
Amelia refined the UI script so that it reads the flag and performs the wait before sending the query across.
For the time being, all individual components have been completed and at this stage we are moving on to the integration step. While we have tested everything, this can only be verified during integration. But it looks like we are well ahead of schedule given how easy integration should be.