Matlab HW help
CS 122L Lab Submission Guidelines
These guidelines explain how lab work should be submitted for CS 122L. Points will be deducted from submissions that do not follow these guidelines.
General Submission Information
· Each student must submit a report and any relevant additional files for each lab on BbLearn. The Deliverables section in each lab description indicates required files.
· The files that you and your partner submit for a lab should be identical.
· Proper spelling and grammar are enforced.
Lab reports should be submitted in .pdf, .doc, .docx, or .rtf format. No other file formats will be accepted for lab reports. Lab reports should adhere to the following naming scheme:
<Last Name 1>_<First Initial 1>_<Last Name 2>_<First Initial 2>_lab<Lab Number>.<File Extension>
Example: washington_g_franklin_b_lab2.docx
All files other than the lab report document should be submitted in the form of a zipped folder file. Ask your lab instructor if you need help zipping the folder of additional files. The name of the zipped folder file should adhere to the following naming scheme:
<Last Name 1>_<First Initial 1>_<Last Name 2>_<First Initial 2>_lab<Lab Number>.zip
Example: washington_g_franklin_b_lab2.zip
Plagiarism and Cheating
Plagiarism and cheating are not permitted. Anyone who plagiarizes or cheats will at least receive a zero for the lab assignment. It is okay to talk with people other than your partner about general lab concepts, but the work you submit should be the work of you and your partner. Be sure to cite any external sources you use to help you with your lab work.
Report Format
Lab reports must follow the layout shown in the lab report template. The top of each report should include each partner’s full name, lab section number, lab number and title, and date on which the lab was first introduced. The main part of the report should include some number of possible sections, which are described below. If the lab has more than one part, use subheadings within each section to differentiate between the parts of the lab.
Report Sections
The outline below describes the possible sections for a lab report and what should go in each section. Some section descriptions include a minimum number of sentences required for the section.
Refer to the rubric in the lab description to see what sections are required for the report of a particular lab. The rubric also shows the point values for each of those required sections. When working from the template, you can delete any sections that are not relevant to the lab report that you are working on.
Task Description
Discuss the tasks required by the lab in your own words.
Minimum sentences: 3
Learning Objectives
Discuss the learning objectives for the lab in your own words.
Minimum sentences: 3
Approach
Discuss your overall approach to accomplish the lab tasks. The discussion should be general and focus on high level aspects of your strategy for completing the lab.
Minimum sentences: 3
Mathematical Concepts
Discuss any relevant mathematical concepts for the lab and identify any key equations. Cite any external resources that you use to help you with the mathematical concepts.
Minimum sentences: 3
Program Inputs
Write out the main program inputs in bullet form.
Program Outputs
Write out the main program outputs in bullet form.
Program Description
Write out the main steps that your program uses to accomplish the tasks for the lab. The steps should be more specific than the overall plan discussed in the approach section.
Minimum sentences: 4
Source Code
Include all relevant source code for the lab.
Code Execution Results
Include any relevant output from running the code. Relevant output may include figures or the content of other files.
Question Responses
Include the answers to any of the lab questions. Be sure to restate each question above its corresponding answer so that it is clear which question you are responding to.
Conclusions
Discuss your conclusions for the lab. These conclusions may include a discussion of:
· key concepts or takeaways
· applications of the code
· issues with implementing the code
Minimum sentences: 4