Programming HW #$0$

First$-$time Directions:

In addition to completing the tasks given below, all programming assignments should include the following elements. These

will not be repeated on future assignments, unless changes are necessary.

$$ Every program you submit for grading must include a header section that includes your full name, course and section

number, last date you edited the program, and a brief description of the intent of the program. $($It may be easiest to

copy from $000-$ README $-$ Header and path template for students.sas and make the necessary updates.$)$

$$ Your program must include clear and concise comments to explain the intent of your code. Keep in mind that comments

are not just for you $-$ they are also for your colleagues and clients $($and TA$).$ There are typically multiple ways to achieve

the same result, so use brief comments to explain your reasoning.

$$ The only file you need to submit for grading is your SAS code. The file must be saved as a $.$SAS file in the format

HWXXLastNameFirstInitial.sas. For example, my submissions would be named HW$00$DugginsJ.sas for the first assignment. No other submission types will be graded $($i$.$e$.,$ you will get a zero on the assignment.$)$ Points will be deducted

for submissions that are not named using this style.

$$ The TA can run your code to see your output and log$.$ For this reason it is important that you use any specified names

given to you by the assignment.

$$ When you submit your file to Gradescope, ensure that it is viewable $$ by that I mean make sure you don$$t get a

message stating that your submission cannot be read by Gradescope. The only reason I$$ve ever seen this happen is

when students copy and paste information from rich text sources into their code. As such, I strongly advise you to

never copy and paste into your code from a rich text source. Regardless of the reason, points will be deducted for

submissions that are not viewable.

$$ Files you produce should also include your name. If I produce a report called HW$6$ Duggins Superfund Report.pdf

then a student named Tony Stark should be producing a file called HW$6$ Stark Superfund Report.pdf $-$ this makes

comparing our results very simple because you cannot confuse when you are looking at my work or yours!

$$ Assignments are graded based on two components: $(1)$ general process and $(2)$ homework specifications.

$$ The rubric provided on the Moodle page covers all the elements of the general process. Please read through the

rubric and make sure you understand it$.$ Because the same rubric is used for every assignment you will always

know what is expected of each program for this component.

$$ Your adherence to the homework specifications are evaluated by comparing your code to the specifications to

determine what, if any, elements you got wrong. Because the specifications are also provided in advance, you also

know exactly what is required of you for this component.

$$ Finally, while I can$$t require you to do the following $-$ I strongly suggest that:

$$ Before submitting your code, delete any data sets you were using, close SAS, reopen SAS, and then run your entire

program. Doing so ensures that no forgotten options or data sets are affecting your output. This should create a

scenario in which you and the TA are looking at the same output.

$$ Even after submission $($or before, if you prefer$)$ you should take time to experiment with the code. Each assignment

will be asking you for a specific task, but that does not mean it requires mastery of every programming technique

we$$ve seen so far. Try changing variables, or formats, or programming the same output a different way and see

how it affects your results. Then figure out why! As an example, I won$$t ask you about the IB and PDV contents

or the location of pointers on every assignment, but you should always know what is going on behind the scenes!

Programming HW #$0$

$$ You are allowed at most zero DATA steps and five PROC steps to complete this assignment.

Specifications:

$$ Create a library that points to the provided data sets and name this library InputDS. Be sure any LIBNAME statements

only use relative paths and, further, that LIBNAME statements referring to the S drive have no folder names included.

You are not creating any SAS files in this assignment, so you do not need to create a library for your work but you do

need to make sure than any non$-$SAS output $($like a PDF$!)$ goes to the location of your choice!

$$ I$$ve created a report called HW$0$ Duggins Partial Weather Listing.pdf and your task is to create an identical report.

$($Remember$,$ from above that means your file name should be HW$0$ your$-$last$-$name Partial Weather Listing.pdf $)$

There are a few elements you$$ll need that cannot be inferred from the provided report, or which I want you to pay

special attention to but could be easily missed $$ for those I$$ve provided these pointers!

$$ The PDF uses the Festival style. Otherwise, all fonts, font sizes, colors