haas:spring2018:unix:projects:spf0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:spring2018:unix:projects:spf0 [2018/03/14 17:16] – [Specifications] wedge | haas:spring2018:unix:projects:spf0 [2018/03/14 18:30] (current) – [Specifications] wedge | ||
|---|---|---|---|
| Line 245: | Line 245: | ||
| You'll notice that everything lines up and is positioned similarly: | You'll notice that everything lines up and is positioned similarly: | ||
| - | * groupwork! This project is specifically designed to be performed in groups. I want to see groups ranging from a minimum of 2 people, to a maximum of 4 people. Any less and any more are not allowed. | + | * groupwork! This project is specifically designed to be performed in groups. |
| + | * I want to see groups ranging from a minimum of 2 people, to a maximum of 4 people. Any less and any more are not allowed. | ||
| + | * furthermore, | ||
| + | * ranks 1 and 2 are specifically and uniquely exempt from this restriction (ie they can be part of the same group, if they were to choose to be a group of 2). Otherwise, same rank spacing still applies. | ||
| + | * groups of 4 cannot have rank subsets that span 3 consecutive ranks (ie ranks 6, 7, 8, and 11) | ||
| + | * EVERY group member needs to be identified in your scripts (in a comment listing everyone). | ||
| * EVERY group member needs to be familiar with the end products | * EVERY group member needs to be familiar with the end products | ||
| * EVERY group member needs to submit a copy of the scripts (they should all be identical- I will check) | * EVERY group member needs to submit a copy of the scripts (they should all be identical- I will check) | ||
| Line 304: | Line 309: | ||
| This can be in the form of comments in your script, or even a separate file submitted at time of submission (if a file, be sure to make mention of it in your script so I can be sure to look for it). | This can be in the form of comments in your script, or even a separate file submitted at time of submission (if a file, be sure to make mention of it in your script so I can be sure to look for it). | ||
| - | =====Verification===== | ||
| - | To assist you in verifying output compliance, I have generated a set of sample script outputs and placed them in the public directory for this project. | ||
| - | |||
| - | There you will find a file by the name of **outputlist**, | ||
| - | |||
| - | Using these files, you can check the functionality of your script in a number of operating conditions, to verify that it is indeed working as it should be. While this isn't likely to cover the full spectrum of possibilities, | ||
| =====Submission===== | =====Submission===== | ||
| - | By successfully performing this project, you should have a fully functioning | + | By successfully performing this project, you should have a fully functioning |
| To submit this project to me using the **submit** tool, run the following command at your lab46 prompt: | To submit this project to me using the **submit** tool, run the following command at your lab46 prompt: | ||
| <cli> | <cli> | ||
| - | $ submit unix pwn0 pwn0.sh | + | $ submit unix spf0 pigen pigrep |
| - | Submitting unix project "pwn0": | + | Submitting unix project "spf0": |
| - | -> pwn0.sh(OK) | + | -> pigen(OK) |
| + | -> pigrep(OK) | ||
| SUCCESSFULLY SUBMITTED | SUCCESSFULLY SUBMITTED | ||
| </ | </ | ||
| - | You should get some sort of confirmation indicating successful submission | + | You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. |
| I'll be looking for the following: | I'll be looking for the following: | ||
| < | < | ||
| - | 78:pwn0:final tally of results (78/78) | + | 26:spf0:final tally of results (26/26) |
| - | *:pwn0:pwn0.sh on help displays informative usage and exits [4/4] | + | *:spf0:scripts effectively utilize variables in operations |
| - | *:pwn0:pwn0.sh | + | *:spf0:scripts |
| - | *:pwn0:pwn0.sh | + | *:spf0:scripts |
| - | *:pwn0:pwn0.sh | + | *:spf0:scripts |
| - | *:pwn0:pwn0.sh | + | *:spf0:scripts |
| - | *:pwn0:pwn0.sh | + | *:spf0:scripts |
| - | *:pwn0:pwn0.sh effectively utilizes functions in script [4/4] | + | *:spf0:scripts are proper bash scripts |
| - | *: | + | *:spf0:pigrep |
| - | *:pwn0:pwn0.sh parses command-line arguments as appropriate [4/4] | + | *:spf0:pigrep |
| - | *: | + | *:spf0:scripts properly manage input violations |
| - | *:pwn0:pwn0.sh | + | *:spf0:pigen operates according to specifications |
| - | *: | + | *:spf0:pigrep |
| - | *: | + | *:spf0:script |
| - | *: | + | |
| - | *: | + | |
| - | *:pwn0:pwn0.sh omits specified bases as requested | + | |
| - | *:pwn0:pwn0.sh properly manages input violations | + | |
| - | *:pwn0:pwn0.sh | + | |
| - | *:pwn0:pwn0.sh | + | |
| </ | </ | ||
| Line 355: | Line 349: | ||
| * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | ||
| * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | ||
| + | * Solutions not done in a valid group will be subject to a 25% overall deduction | ||
haas/spring2018/unix/projects/spf0.1521047813.txt.gz · Last modified: 2018/03/14 17:16 by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
