User Tools

Site Tools


haas:spring2022:unix:projects:upf0

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:spring2022:unix:projects:upf0 [2022/02/28 15:27] – [conditions] wedgehaas:spring2022:unix:projects:upf0 [2022/03/01 19:58] (current) – [upf0steps] wedge
Line 162: Line 162:
 There are one or more statements within the body of the if (to be run in the event the result of the condition tests true), and the structure is terminated with the trailing **fi** (if spelled backwards). There are one or more statements within the body of the if (to be run in the event the result of the condition tests true), and the structure is terminated with the trailing **fi** (if spelled backwards).
  
-We also have the ability to react in the event the **if** condition tests false, and that is with an option **else** statement (which is used 0 or 1 times per if, and must always follow the if):+We also have the ability to react in the event the **if** condition tests false, and that is with an optional **else** statement (which is used 0 or 1 times per if, and must always follow the if):
  
 <code bash> <code bash>
Line 234: Line 234:
   * **-le** - is less than or equal to   * **-le** - is less than or equal to
   * **-gt** - is greater than   * **-gt** - is greater than
-  * **-gt** - is greater than or equal to+  * **-ge** - is greater than or equal to
  
 These of course are binary conditions, meaning we compare TWO variables to see if they possess the indicated relation (which results in a true or false result produced). These of course are binary conditions, meaning we compare TWO variables to see if they possess the indicated relation (which results in a true or false result produced).
Line 268: Line 268:
 You will once again be creating a steps file that can automate your project.  You will once again be creating a steps file that can automate your project. 
  
-As in previous projects, **upf0steps** will contain the steps you took from the point of copying the numbers suite and downloading the pipemath suite up until the submit step (hint: just run the task#.cli scripts within the steps script). +As in previous projects, **upf0steps** will contain the steps you took from the point of downloading the pipemath suite up until the submit step (hint: just run the task#.cli scripts within the steps script). 
-  * To clarify: YES, I want to see steps creating a project directory, copying and downloading files in question, extracting, compiling, installing, and then of course running each individual task#.cli script.+ 
 +  * To clarify: YES, downloading files in question, extracting, compiling, installing, and then of course running each individual task#.cli script.
  
 There are some additional constraints you need to keep in mind: There are some additional constraints you need to keep in mind:
Line 322: Line 323:
 78:upf0:final tally of results (78/78) 78:upf0:final tally of results (78/78)
 *:upf0:upf0steps has valid list of non-interactive instructions [4/4] *:upf0:upf0steps has valid list of non-interactive instructions [4/4]
-*:upf0:upf0steps only copies/alters files if USER matches [4/4]+*:upf0:upf0steps only modifies files if USER matches [4/4]
 *:upf0:upf0steps builds the various task#.cli files it runs [4/4] *:upf0:upf0steps builds the various task#.cli files it runs [4/4]
 *:upf0:upf0steps obtains the latest pipemath release from site [4/4] *:upf0:upf0steps obtains the latest pipemath release from site [4/4]
 *:upf0:upf0steps only displays specified STDOUT output [4/4] *:upf0:upf0steps only displays specified STDOUT output [4/4]
-*:upf0:upf0steps resiliently creates local project directory [4/4] +*:upf0:upf0steps errorlessly creates local project directory [4/4]
-*:upf0:upf0steps copies public dir data with absolute path [4/4]+
 *:upf0:upf0steps makes clear, effective use of wildcards [4/4] *:upf0:upf0steps makes clear, effective use of wildcards [4/4]
 *:upf0:upf0steps has descriptive why and how comments [4/4] *:upf0:upf0steps has descriptive why and how comments [4/4]
-*:upf0:upf0steps indentation used to promote scope and clarity [2/2]+*:upf0:upf0steps indentation used to promote scope and clarity [4/4]
 *:upf0:upf0steps defines and uses custom variables [4/4] *:upf0:upf0steps defines and uses custom variables [4/4]
 *:upf0:upf0steps uses command expansions to get information [4/4] *:upf0:upf0steps uses command expansions to get information [4/4]
Line 337: Line 337:
 *:upf0:all files are organized, clear, and easy to read [4/4] *:upf0:all files are organized, clear, and easy to read [4/4]
 *:upf0:task#.cli files output only correct, specified data [4/4] *:upf0:task#.cli files output only correct, specified data [4/4]
-*:upf0:task#.cli files use specified number tools by quantity [4/4]+*:upf0:task#.cli files use specified number tools by quantity [6/6]
 *:upf0:task#.cli files display no STDERR output [4/4] *:upf0:task#.cli files display no STDERR output [4/4]
 *:upf0:task#.cli files have solution within given constraints [4/4] *:upf0:task#.cli files have solution within given constraints [4/4]
Line 343: Line 343:
 </code> </code>
  
 +Additionally:
 +  * Solutions not abiding by **SPIRIT** of project 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 lacking **ORGANIZATION** and are not easy to read (within 90 char width) are subject to a 25% overall deduction
haas/spring2022/unix/projects/upf0.1646062036.txt.gz · Last modified: 2022/02/28 15:27 by wedge