Differences

This shows you the differences between two versions of the page.

--- haas:spring2018:unix:projects:spf0 [2018/03/14 17:22] – [Specifications] wedge
+++ haas:spring2018:unix:projects:spf0 [2018/03/14 18:30] (current) – [Specifications] wedge
@@ Line 247: / Line 247: @@
   * 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, groups of 2 cannot have overall class ranks within 3 ranks of each other (ie ranks 8 and 9, or 8 and 10, or 8 and 11 are not valid combinations for 2-person groups).
+      * furthermore, groups of 2 or 3 cannot have overall class ranks (rankings as of today: 03/14/2018) within 3 ranks of each other (ie ranks 8 and 9, or 8 and 10, or 8 and 11 are not valid combinations for 2-person groups).
+        * 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
@@ Line 307: / 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).
-=====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**, which contains a list of filenames (output0 - outputF) and the **pwn0.sh** script command-line used to generate the output found in those files.
-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, it should offer up some assistance in helping you broaden your view of troubleshooting scenarios.
 =====Submission=====
-By successfully performing this project, you should have a fully functioning script by the name of **pwn0.sh**, which is all you need to submit for project completion (no steps file, as your "steps" file IS the script you wrote).
+By successfully performing this project, you should have a fully functioning set of scripts by the names **pigen** and **pigrep**, which are all you need to submit for project completion (no steps file, as your "steps" file ARE the scripts you wrote).
 To submit this project to me using the **submit** tool, run the following command at your lab46 prompt:
 <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
 </cli>
-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.
+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:
 <code>
-:pwn0:final tally of results (78/78)
+: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 [2/2]
-*:pwn0:pwn0.sh effectively utilizes variables in operations [4/4]
+*:spf0:scripts effectively utilize command-line arguments [2/2]
-*:pwn0:pwn0.sh effectively utilizes command expansions [4/4]
+*:spf0:scripts effectively utilize command expansions [2/2]
-*:pwn0:pwn0.sh effectively utilizes regular expressions [4/4]
+*:spf0:scripts effectively utilize regular expressions [2/2]
-*:pwn0:pwn0.sh effectively utilizes selection statements [4/4]
+*:spf0:scripts effectively utilize selection structures [2/2]
-*:pwn0:pwn0.sh effectively utilizes looping structures [4/4]
+*:spf0:scripts effectively utilize looping structures [2/2]
-*:pwn0:pwn0.sh effectively utilizes functions in script [4/4]
+*:spf0:scripts are proper bash scripts with shabang and exit [2/2]
-*:pwn0:pwn0.sh is a proper bash script with shabang and exit [4/4]
+*:spf0:pigrep displays values in proper orientation [2/2]
-*:pwn0:pwn0.sh parses command-line arguments as appropriate [4/4]
+*:spf0:pigrep accurately displays values as requested [2/2]
-*:pwn0:pwn0.sh accurately displays values in proper alignment [4/4]
+*:spf0:scripts properly manage input violations [2/2]
-*:pwn0:pwn0.sh accurately displays values in requested bases [4/4]
+*:spf0:pigen operates according to specifications [2/2]
-*:pwn0:pwn0.sh accurately displays values in specified range [4/4]
+*:spf0:pigrep operates according to specifications [2/2]
-*:pwn0:pwn0.sh range logic flexibly works forward and reverse [4/4]
+*:spf0:script logic is organized and easy to read [2/2]
-*:pwn0:pwn0.sh iterates as appropriate in given scenarios [4/4]
-*:pwn0:pwn0.sh includes additional bases as requested [4/4]
-*:pwn0:pwn0.sh omits specified bases as requested [4/4]
-*:pwn0:pwn0.sh properly manages input violations [4/4]
-*:pwn0:pwn0.sh operates according to specifications [5/5]
-*:pwn0:pwn0.sh logic is organized and easy to read [5/5]
 </code>
@@ Line 358: / Line 349: @@
   * 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 done in a valid group will be subject to a 25% overall deduction

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools