Giter Club home page Giter Club logo

cse15l-lab-reports's People

Watchers

 avatar

cse15l-lab-reports's Issues

Lab Report 3 Feedback

Here is your feedback for Lab Report 3:

  • Correct markdown formatting.
  • Lab report is on its own page, not the index page.
  • Correct screenshot of .ssh/config file
  • Show the ssh command logging you into your account using just the alias you chose.
  • Show an scp command copying a file to your account using just the alias you chose.
  • Correct description of streamlining ssh configuration.
  • Screenshot of where the public key you made is stored on Github and in your user account.
  • Screenshot of where the private key you made is stored on your user account.
  • Show git commands to commit/push a change while logged into your ieng6 account.
  • Show a link for the resulting commit.
  • Correct description of setting up Github access from ieng6.
  • Show copying your whole markdown-parse directory to your ieng6 account.
  • Show logging into your ieng6 account and compiling/running the tests for your repository.
  • Show combining scp, semicolon, and ssh to copy the whole directory and run the tests in one line.
  • Correct description of copying whole directories.

Additional comments from your grader:
-Please include the git push command as well as the link to the commit
-Include some annotations describing what each screenshot shows in the last task (also it might make the screenshots a bit cleaner to use the -q option tag)
-Show the tests running successfully in one line

Great work!

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. see first comment
  • Lab report is on its own page, not the index page.

Test File 1

  • 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

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:

Ensure that you provide the links to both of the test files that you chose to use. Please read the lab write-up carefully! You should be analyzing the outputs for both test files.

Feel free to comment below with 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 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
    • close! expected output should be the link inside the parentheses and not the text inside the brackets. Also, because you seemed to have used to two different tests for Snippet 1 on your implementation and the other implementation, please include both tests.
  • 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
    • expected output should be the link inside the parentheses and not the text inside the brackets. Also, because you seemed to have used to two different tests for Snippet 2 on your implementation and the other implementation, please include both tests.
  • 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
    • expected output should be the link inside the parentheses and not the text inside the brackets. Also, because you seemed to have used to two different tests for Snippet 3 on your implementation and the other implementation, please include both tests.
  • 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:
Good job!
 
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 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
    • try to explicitly name the bug and symptom in your description.
  • Correct markdown formatting
    • try updating your test file links to be in markdown format
  • 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:
Great job! Keep up the good work:)


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 photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.