cse15l-lab-reports's People
cse15l-lab-reports's Issues
Leb Report 4 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
Lab Report 5 Feedback
Here is your feedback for Lab Report 5:
- Provides correct description of how mismatch in outputs was identified
- Correct markdown formatting.
- Lab report is on its own page, not the index page.
Test File 1
- [] Describes which implementation is correct
missing this description - Shows actual output and the expected output
- Provides correct description of the bug
- [] Provides code snippet that needs to be changed
missing code snippet
Test File 2
- [] Describes which implementation is correct
- Shows actual output and the expected output
- Provides correct description of the bug
- [] Provides code snippet that needs to be changed
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
Lab 1 Report Feedback
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
The lab report is on the index page when it should be on a separate page called something like lab-report-1. You should add a link on your index page that links to your lab-report-1 page. - Last example 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:
Make sure to fix the issue regarding putting the lab report on its own page. Also, please change the link in the VSCode section so that it links to a valid url.
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
Lab Report 2 Feedback
Here is your feedback for Lab Report 2:
- Correct screenshot of code diff page
- Correct failure inducing test file - 1
- Correct failure inducing test file - 2
- Correct failure inducing test file - 3
- Screenshot of symptom output that caused the failure for test file - 1
- Screenshot of symptom output that caused the failure for test file - 2
- Screenshot of symptom output that caused the failure for test file - 3
- Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 1
- Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 2
- Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 3
- Correct markdown formatting
- Lab report is on its own page, not the index page
- Text is formatted in a way that was easy for grader to read
Additional comments from your grader:
Good Job :)
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
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.