haas:spring2018:unix:projects:upf0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:spring2018:unix:projects:upf0 [2018/01/28 16:32] – wedge | haas:spring2018:unix:projects:upf0 [2018/02/28 20:26] (current) – [numbers suite] wedge | ||
|---|---|---|---|
| Line 50: | Line 50: | ||
| * pipemath-20170201-09.tar.gz | * pipemath-20170201-09.tar.gz | ||
| - | You would select the " | + | From visual inspection, you would select the " |
| + | |||
| + | Note, however, that visual inspection alone is not good enough for your steps file. New versions may be released, and your steps file needs to obtain the most recent version available. To facilitate this task, the latest and greatest version of pipemath will be listed in a file called LATEST (which you should see near the top of the directory index listing). You can make use of this file to assist you in automating the process of determining and downloading the latest version of the pipemath tools. | ||
| Once those two steps are complete, you can begin on the tasks listed in your **TASK** file. | Once those two steps are complete, you can begin on the tasks listed in your **TASK** file. | ||
| ====numbers suite==== | ====numbers suite==== | ||
| - | The numbers suite is basically a collection of command-line tools whose purpose is to display a single digit number, in accordance with the tools name. | + | The numbers suite is basically a collection of command-line tools whose purpose is to display a single digit number, in accordance with the tool' |
| For example, when you run the **zero** tool, a **0** is displayed to STDOUT. For **one**, a **1** is displayed to STDOUT. And so on up through **nine**. | For example, when you run the **zero** tool, a **0** is displayed to STDOUT. For **one**, a **1** is displayed to STDOUT. And so on up through **nine**. | ||
| Line 157: | Line 159: | ||
| * where # is the calculated output matching the TASK file result requested (ie, you must run your task#.cli script to produce this output). | * where # is the calculated output matching the TASK file result requested (ie, you must run your task#.cli script to produce this output). | ||
| * note that the task#.cli output appears on the SAME line as the "Task X result is:" text, and there is a single space separating it from the colon. | * note that the task#.cli output appears on the SAME line as the "Task X result is:" text, and there is a single space separating it from the colon. | ||
| + | * additionally, | ||
| + | * you will be making use of a loop to drive the execution of your results (the "Task # result is: ..."). | ||
| For example, a sample output of your **upf0steps** script should appear like follows (but your # values will of course be different based on your individual **TASK** file): | For example, a sample output of your **upf0steps** script should appear like follows (but your # values will of course be different based on your individual **TASK** file): | ||
| Line 196: | Line 200: | ||
| < | < | ||
| 78: | 78: | ||
| - | *: | + | *: |
| - | *: | + | *: |
| - | *: | + | *: |
| - | *: | + | *: |
| - | *:upf0:task0.cli produces correct result | + | *:upf0:upf0steps only displays specified STDOUT output |
| - | *:upf0:task0.cli uses specified numbers by quantity | + | *:upf0:upf0steps resiliently creates local project directory |
| - | *:upf0:task0.cli uses specified operations by quantity | + | *:upf0:upf0steps copies public dir data with absolute path [4/4] |
| - | *:upf0:task0.cli solution within min_pipes, max_pipes | + | *:upf0:upf0steps makes clear, effective use of wildcards |
| - | *:upf0:task1.cli produces correct result | + | *:upf0:upf0steps has descriptive why and how comments |
| - | *:upf0:task1.cli uses specified numbers by quantity | + | *:upf0:upf0steps indentation used to promote scope and clarity |
| - | *:upf0:task1.cli | + | *:upf0:upf0steps defines and uses custom variables |
| - | *:upf0:task1.cli solution within min_pipes, max_pipes [2/2] | + | *:upf0:upf0steps |
| - | *: | + | *:upf0:upf0steps |
| - | *: | + | *:upf0:upf0steps automates the task when run [4/4] |
| - | *:upf0:task2.cli | + | *:upf0:all files are organized, clear, and easy to read [4/4] |
| - | *: | + | *:upf0:task#.cli files output only correct, specified |
| - | *: | + | *:upf0:task#.cli files use specified |
| - | *: | + | *:upf0:task#.cli files display no STDERR output |
| - | *:upf0:task3.cli uses specified operations by quantity | + | *:upf0:task#.cli files have solution within |
| - | *:upf0:task3.cli solution within min_pipes, max_pipes | + | *:upf0:task#.cli files only have the solution |
| - | *:upf0:task4.cli produces | + | |
| - | *: | + | |
| - | *: | + | |
| - | *: | + | |
| - | *: | + | |
| - | *: | + | |
| - | *:upf0:task5.cli uses specified | + | |
| - | *:upf0:task5.cli solution within min_pipes, max_pipes | + | |
| - | *:upf0:task6.cli produces correct result [2/2] | + | |
| - | *: | + | |
| - | *: | + | |
| - | *: | + | |
| - | *:upf0:task7.cli produces correct result [2/2] | + | |
| - | *: | + | |
| - | *: | + | |
| - | *: | + | |
| </ | </ | ||
haas/spring2018/unix/projects/upf0.1517157125.txt.gz · Last modified: 2018/01/28 16:32 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
