pandrew99 / cse15l-lab-reports Goto Github PK

Here is your feedback for Lab Report 1:

• All relevant URLs written as markdown links
• All relevant code examples written with backticks (```)
• All screenshots correspond to the described steps
• All titles of sections are formatted as headers or similar
• Lab report is on its own page, not the index page
• Last example counts keystrokes and shows how to run remotely saving time
• Text is formatted in a way that was easy for grader to read

Additional comments from your grader:
I think for the last example, 'Optimizing Remote Running' you could've included either more examples, code, or tried and/or talked about the different tricks the writeup mentioned. Other than that, great job! Everything was neat and easy to read.

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Here is your feedback for Lab Report 3 - Copy whole directories with scp -r:

• Show copying your whole markdown-parse directory to your ieng6 account
• Show logging into your ieng6 account after doing this and compiling and running the tests for your repository
• Show (like in the last step of the first lab) combining scp, ;, and ssh to copy the whole directory and run the tests in one line.

Additional comments from your grader:

Good job persevering! Debugging can be so exhausting but super proud of you for figuring it out :))

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Here is your feedback for Lab Report 5:

• Explains how tests with different results were found (diff, manual search, etc)

Test 1:

• Describes which, if any, implementation is correct by showing both actual outputs and indicating what the expected output is
• Describes bug in code for one of the incorrect implementation and shows the code that should be fixed.

Test 2:

• Describes which, if any, implementation is correct by showing both actual outputs and indicating what the expected output is
• Describes bug in code for one of the incorrect implementation and shows the code that should be fixed.

Additional comments from your grader:
Good job!

Feel free to comment below any questions about the rubric/feedback

Here is your feedback for Lab Report 4:

• Provides link to their markdown-parse repository
• Provides link to the markdown-parse repository they reviewed

Snippet 1

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Snippet 2

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Snippet 3

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Additional comments from your grader:

Feel free to comment below any questions about the rubric/feedback

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Bug/Input 1

• Commit screenshot for bug/input 1
• Link to test file for bug/input 1
• Symptom shown as command + output for bug/input 1
• Description of relationship between bug, symptom, and input for bug/input 1

Bug/Input 2

• Commit screenshot for bug/input 2
• Link to test file for bug/input 2
• Symptom shown as command + output for bug/input 2
• Description of relationship between bug, symptom, and input for bug/input 2

Bug/Input 3

• Commit screenshot for bug/input 3
• Link to test file for bug/input 3
• Symptom shown as command + output for bug/input 3
• Description of relationship between bug, symptom, and input for bug/input 3

Additional comments from your grader:
Nice job on this report and great analysis of your bugs/symptoms! I liked your "Final Thoughts" section. I gave you full credit.

Feel free to comment below if you have any questions about the rubric/feedback.

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page