• As Spec Snuffy, when I’m transmitting, I want the instructor to be able to see it so that they can evaluate my performance.
• #12

Backend

• It should have GET and POST for the /signals endpoint to add and grab data to/from the db
• It should have GET and POST for the /users endpoint to add and grab data to/from the db
• It should return the response in JSON format
• Update the wiki API page with response body examples
• Update seed to clear the authors table before running.

Frontend

• It should display student signals as a different color than noise and instructor signals so that instructors can see each student's signal
• It could display signal and student data by hovering over a student signal.

• As Mr. Programmer, I want to layout the general structure of the program UI by adding and organizing component files.

• As Mr. Programmer, I want to ^^^ by making a theme component.

We need to add CRUD functions so that the instructor can modify the starting signals for everyone.

Student modifications to their transmitter should be pushed to the database in addition to emitted via websocket (otherwise a page refresh will delete everything)

• As Capt Gruff, in the students window I want to see a list of teams with their rosters so that I know which students are on each team.
• As Capt Gruff, in the students window I want to see a list of students who have not been assigned to a team so I know who is unassigned.
• As Capt Gruff, in the students window I want to be able to click the ‘add’ button next to a team then click students to add them to the team until I click the add button again to stop adding so that I can quickly assign teams or swap team members.
• As Capt Gruff, in the students window I want to see a list of my broadcasts in a row next to each team so that I can see each teams’ progress at a glance.
• As Capt Gruff, in the students window I want the broadcast icons to change color or somehow reflect whether or not they are active, passive, or active and being jammed.
• As Capt Gruff, in the students window I want to see a list of antennas for each team and their current properties so I can quickly tell when and how each team is broadcasting.
• As Capt Gruff, in the students window I want to be able to click on a broadcast icon to toggle it between active and passive.

• As Spec Snuffy, in the receiver window, I want to be able to select the antenna, center frequency (with dropdown for unit), span (with dropdown for unit), and modulation (with dropdown) so I can configure my receiver.
• As Spec Snuffy, in the receiver window, I want to be able to toggle on and off the receiver with a power button and I want a pop-up to warn me when I’m turning it on if I’m transmitting on that antenna because I can’t receive while I’m transmitting.
• As Spec Snuffy, in the receiver window, I want to see a clear video feed when I’ve configured my receiver correctly and the signal is not being jammed so that I know I’ve done things correctly.
• As Spec Snuffy, in the receiver window, I want to see a distorted video when I’ve configured my receiver correctly and the signal is being jammed so that I know I’m jamming the signal.
• As Spec Snuffy, in the receiver window, I want to see a static video when I’ve configured my receiver incorrectly so that I now I’ve messed up.

• As Mr Programmer, I want to be able to deploy to heroku, so that I have a public facing application

Add a new about modal to include BSDI origins and other contributors.

github.io deployment assumes everything is under /iris/ but create-react-app assumes everything is under /. Need to find a way to resolve this without breaking Heroku deployment since any production build will likely be under root.

We need to update the README

As a student/instructor, I want to create a game that is 'independent' of anyone else's game.

Socket.io has the ability to create 'namespaces' that we can use to separate out websockets. That way updates in one game are independent of updates in another game and we don't get 'crosstalk'

• As Spec Snuffy, in the transmitter window I want to be able to add multiple transmitter configurations that show up as tabs so I can prepare potential broadcasts to be accessed on demand.
• As Spec Snuffy, in the transmitter antenna window, for each transmitter configuration, I want to be able to select the antenna using a drop down menu so I don’t input a bad value.
• As Spec Snuffy, in the transmitter signal generator window, for each transmitter configuration, I want to be able to select the frequency (with a drop down for unit), amplitude, symbol rate, mode (with a drop down), modulation (with a drop down), sweep center frequency (with a drop down for unit), sweep hop width (with a drop down for unit), sweep rate (with a drop down for unit), hop rate so I can get the correct signal generated.

• As Spec Snuffy, when I visit the site I want to see a banner at the top with the name of the app so I know I’m in the right place.
• As Spec Snuffy, I want only the header and login dialog box visible when I first visit the site so I can quickly access what I need in that moment.
• As Spec Snuffy, in the header I want a logout button to be easily recognized so I don’t have to search to be able to log out.
• As Spec Snuffy, in the header I want to see my team name once it’s been assigned so I can quickly see who I’m working with.
• As Spec Snuffy, in the header when I click my team name, I want to see the names of my team members so I know who I’m working with.

As an instructor, I need initial seed data to create a server/session/game

AC

• It should have, uh, data? I guess?

When running docker-compose up on a freshly cloned repo, knex does not install causing the build for the backend to fail. Research different ways to resolve this and implement any changes as needed.

• It should be able to run docker-compose up without knex errors on a clean clone

Are Jest tests are woefully lacking.

We assume that everything sent to the db actually gets put in it. Now just make sure that actually happens and then error handle if not.

Add Cypress to the project to enable integration tests.

• It should have Cypress folders created in the UI directory
• It should have Cypress added to the package.json

When the receiver receives an update in box 0, it updates all 4 receivers at the same time. Updating values in any of the other boxes don't update anything, even though the update function is called. Compare to Tx implementation, there may be a mismatch somewhere.

• As Capt Gruff, in the injects window I want to be able to add as many broadcast signals as I want by clicking on a plus-tab icon so that I can easily understand how to add configurations.
• As Capt Gruff, in the injects window I want to see all of my configurations as a list of tabs so that I can quickly choose between them.
• As Capt Gruff, in the injects window I want to be able to type the name, center frequency (with dropdown units), span (with dropdown units), amplitude, modulation (with dropdown), source (with dropdown), and video source (with dropdown) so I can easily set up the configuration.
• As Capt Gruff, in the injects window I want to be able to click save and type a save name into a popup dialog to save all of the current broadcast configurations so that I can quickly rebuild the current environment.
• As Capt Gruff, in the injects window I want to be able to click a load button and select a save file from a dropdown in a popup dialog so I can quickly restore saved configurations.

As Spec Snuffy and or Capt Instructor, I want to see the same data regardless of which browser/UI instance that I am using.

Jeff has recommended https://github.com/socketio/socket.io and potentially a queue service like Rabbit MQ or Redis to synchronize things across all UI instances.

REST requests from the UI can likely all be handled in the files under /ui/src/context. IE, when a user submits a change on their transmitter, it updates their UI's context in txContext.jsx where it can then perform the PATCH request, and upon receiving a 200 response can send an update task to redis/rabbitmq for the rest of the frontends to pull from and update their respective contexts with a GET to the DB.

@thkruz I believe you worked with web sockets on your last project. We will probably need your help implementing this.

• When Spec Snuffy changes a value in the transmitter box and transmits, Capt Instructor and any other student should be able to see the new value on their UI instances.
• Any Patch request from the UI should be met with an update to displayed values across all applications.

websockets should allow the interface to update across the "game" for each team

• transmitter updates
• receiver updates
• the antenna updates

The DB schema has been updated with lots of new tables. Create API endpoints for interaction.

• It should have at least a GET endpoint for each table
• Wiki is updated with new endpoints
• Investigate how to implement "instructor only" endpoints. Session cookies?

Create basic backend and DB design to support frontend development.

• It should be dockerized
• It should deploy with docker-compose up without any issues

DB schema needs to be redesigned to reflect new input from squadron.

• Migrations updated to new schema
• XML updated with changes
• Wiki updated with changes

• As Spec Snuffy, in the antenna window I want to be able to configure my antennas by selecting an antenna, then selecting from a list of targets and enabling an ‘auto-track’ feature so that I can choose which target it is engaging.

Going to https://sew-ui.herokuapp.com/ results in:

Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command

• As Spec Snuffy, I want to be able to click the ‘create an account’ dialog to open a popup that lets me create an account with a user id, password, and student role so I can login.
• As Spec Snuffy, I want to be able to reset my password if I forget it.
• As Spec Snuffy, I want to be able to login to my own account that has my configurations saved for me so that I can quickly pick up where I left off.
• As Spec Snuffy, when I login, I want to be taken to a page with a Spectrum analyzer, antenna configuration, transmitter, and receiver visible so I can see everything at once.
• As Capt Gruff, I want to be able to click the ‘create an account’ dialog to open a popup that lets me create an account with a user id, password, and instructor role so I can login.
• As Capt Gruff, when I login, I want to be taken to a page with a students window and an injects window so that I have everything I need right in front of me.

• As Spec Snuffy, in the transmitter transmitter modem window, for each transmitter configuration, I want to be able to select the frequency (with drop down for unit), power, and modulation (with a drop down) so that I can set up my transmitter easily.
• As Spec Snuffy, in the transmitter transmitter modem window, for each transmitter configuration, I want to be able to turn on and off my rf emissions with a toggle switch and I want to be warned with a pop-up when I try to turn it on so that I don’t accidentally radiate bad transmissions.
• As Spec Snuffy, in the transmitter transmitter modem window, I want to see a power light turn green when I’m transmitting that configuration and red when I’m not.

• As Spec Snuffy, in the Spectrum analyzer window, I want to see a power vs frequency graph
• As Spec Snuffy, in the Spectrum analyzer window, I want the power vs frequency graph to tell me the center frequency and span so that I know what I’m looking at
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click the frequency button, type a number, then select a unit from the menu window so that I can change the center frequency of the graph
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click the span button, type a number, then select a unit from the menu window so that I can change the span of the graph
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able click the mode button so that I can toggle between Spectrum analyzer and apsk graphs.
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click the trace button and select the type of trace I see in the Spectrum analyzer window so that I can better understand the data.
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click the marker button and have a marker appear no the graph.
• As Spec Snuffy, in the Spectrum analyzer window, I want to see the current frequency and amplitude of the marker on the graph so that I can use it as a reference.
• As Spec Snuffy, in the Spectrum analyzer window, I want to click the left and right arrow buttons to move the marker around the graph so that I can get information from multiple points.
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click the reset button to restore the Spectrum analyzer to it’s default values.
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to select an antenna to connect to the Spectrum analyzer so that I can use the carrier-under-carrier function.
• As Spec Snuffy, in the Spectrum analyzer window, I want to be able to click carrier-under-carrier to show what the Spectrum looks like without my broadcast.
• As Mr. Programmer, in the Spectrum analyzer window, I want the logic for drawing the spectrum analyzer results to be class based and standalone