Progress I unfortunately was not able to work on capstone as much as I would have liked this week, because I was really busy with projects due in my three other classes. The last one of them is due tomorrow, so after that I will be working on the final paper and assisting with the demo as much as I can, since I don’t have the physical tiles with me. Functions are as developed as last week, and my group…
Progress This week I worked on three major things. We had our demo on Wednesday, during which I realized that the interpreter doesn’t throw errors in many cases: for example, when a single “<” symbol was the only tile, or if I had a nonsense statement such as “if print”. My first task of the week was therefore to comb through the interpreter and throw errors wherever possible. Almost all of these were new syntax errors. Then, I worked on…
Progress This week I began to look at function application, and also fix PEMDAS on the interpreter and smoothen everything out for the final demo. My group decided that it would make more sense for me to focus on polishing the interpreter this week so that we are in good shape for the final demo, and work on functions on a different branch. I was a little busy this week with other classes, so function application is a little incomplete,…
Progress This week I continued work on the display/GUI and introduced a top level module so that the translator (reads in input from the master tile, TODO, interpreter and the display can interact). The top level module is very simple for now, but I have yet to add the deserialization code to it. I will see if this deserialization is more suited to a different module (translation) or whether it should happen in the top level itself. As for the…
Progress This week I worked on creating a display/GUI. This will be run as soon as the master tile sends an input stream to the top module (coming soon). The GUI will show a display of the tiles read in, what each tiles is (from the encoding), error tiles highlighted in red, and output of the program on the side. The GUI also allows for “user input”, if we add a corresponding CodeBlox tile. Since I’ve never made a GUI…
Risks Our updated risk mitigation strategy can be found here. Changes Interpreter/GUI code: Aarohi is planning on writing a simple top level program that knows which functions to call. It receives the stream from the master tile (by deserializing), passes it to the translator to translate into CodeBlox code, passes the output to the interpreter, and passes the CodeBlox outline and interpreter output to the GUI. This would make communication between the code components easier. Embedded: As detailed in Melodee’s status…
Progress This week I worked on porting the interpreter from Arduino C to python, and implemented error checking. I first worked on getting individual commands to work first. Handling commands was straightforward since the only command to implement with the remote, laptop version is print. Handling variables was a little more involved, since I needed to work with evaluating an expression. I changed eval_expression completely, so that it now recursively evaluates expressions. I split up eval (helper function for eval_expression…
Progress This week we worked on modifying our project to fit the new COVID-19 remote protocol. Since Eric and Melodee will be at the same location the rest of the semester, our project on a whole does not change as much, but since my laptop does not communicate with the robot, the interpreter (my portion) will be modified. Instead of communicating output and input from the robot, the interpreter will output to a laptop with simple print statements. Additionally, I…
Risks To mitigate the risk in the interpreter, Aarohi will be implementing operations that only take in values at first (no recursion in eval_expression) and only one argument to functions. If these go smoothly, Aarohi will then work on the recursion in eval_expression, and then transition to functions with multiple arguments. Changes An updated system diagram can be found below: Schedule We are behind schedule because of focusing on the design report and midterms and projects in other classes. …
Progress This week we focused mostly on writing the design report. Since we made a few changes regarding functions from the initial design, we had to design a new code diagram. A copy of the diagram is below: The boxes is orange are to be modified/under modification by me, the boxes in red are allowed to modify the global variable containing the error (aka they are allowed to throw errors) and the box in green (eval_expression) performs type checking. I…