hw03 - Name GT Email ...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Name : <your name> % GT Email : <your GT email address> % Homework : HW03 % Course : CS1371 % Instructor : Marsicano, Smith % Lecture Time : MWF <?:??> % TA's Name : <your TA's name (You may not know this yet)> % Section : <your section, (Can be found on Oscar)> % Collaboration: <place here one of the following: % "I worked on the homework assignment alone, using % only course materials." % OR % "I worked on this homework with <give the names of the % people you worked with>, used solutions or partial % solutions provided by <name the people or other % sources>, and referred to <cite any texts, web sites, or % other materials not provided as course materials for CS % 1371.>" % % % Files provided with this homework: % - hw03.m % - ABCs_vectors.m % - ABCs_hw3_pretest.p % - test_script.m % % Files to submit: % - hw03.m % - ABCs_vectors.m % - arrayMix.m % - eliminate.m % - rotCeva.m % - eval_vec.m % - randInt.m % - score_predict.m % % Instructions: % 1) Follow the directions for each problem very carefully or you will % lose points. % 2) Make sure you name functions exactly as described in the problems or % you will not receive credit. % 3) Read the announcements! Any clarifications and/or updates will be % announced on T-Square. Check the T-Square announcements at least once % a day. % 4) You should not use any of the following functions in any file that % you submit to T-Square: % a) clear % b) clc % c) solve % d) input % e) disp % f) close all % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %========================================================================== % COMMENTING %--------------------------------------------------------------------------
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
% % Whenever you program, it is always a good idea to comment your code. % Commenting helps you keep track of what you are attempting to code, and % it helps others in understanding why you wrote various lines of code. % Since the AutoGrader does not give partial credit for attempting a % problem, we have added a commenting system to give some incentive to at % least attempt each problem. From now on, when you write a solution to a % problem, you should comment your code and explain what you were % attempting to code. Some good places to comment would be sections of your % code that directly relate with your algorithm. However, don't comment % every line of code. Instead comment the lines of code that are either % difficult to understand or are important to solving the problem. %
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/26/2010 for the course CS 1371 taught by Professor Stallworth during the Spring '08 term at Georgia Tech.

Page1 / 5

hw03 - Name GT Email ...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online