haas:spring2017:unix:projects:upf0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:spring2017:unix:projects:upf0 [2017/02/21 22:07] – [Submission] wedge | haas:spring2017:unix:projects:upf0 [2017/02/27 18:27] (current) – [upf0steps] wedge | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| This week's project has 2 points of origin. | This week's project has 2 points of origin. | ||
| - | First, in the **upf0/** sub-directory of the UNIX Public Directory, | + | First, in the **upf0/** sub-directory of the UNIX Public Directory, |
| - | * **TASK** | ||
| * **numbers.tgz** | * **numbers.tgz** | ||
| - | Copy these into your project directory. | + | Then, under a directory by the name of your username within that same directory, there will be another file: |
| + | |||
| + | * **TASK** | ||
| + | |||
| + | Copy both of these files into your project directory. | ||
| The **TASK** file will contain the particular command-line equations you have to perform, along with their stated constraints. | The **TASK** file will contain the particular command-line equations you have to perform, along with their stated constraints. | ||
| - | The **numbers.tgz** file needs to be extracted, compiled, and installed; there are README | + | The **numbers.tgz** file needs to be extracted, compiled, and installed; there is a README |
| Next, you will want to grab the latest version of the **pipemath** suite from the following URL: | Next, you will want to grab the latest version of the **pipemath** suite from the following URL: | ||
| - | * url to pipemath | + | * https:// |
| + | |||
| + | You will want to use a tool like **wget(1)** or **curl(1)** to non-interactively download it onto your lab46 account, and similarly extract, compile, and install that (check its own README file). | ||
| + | |||
| + | There may be multiple versions of **pipemath** available at the download link. Unless you have specific reason otherwise (for this project, you do not), you want to go for the latest version, which will be reflected by the most recent datestamp encoded in the file's name. | ||
| + | |||
| + | For example, say you have the following: | ||
| + | |||
| + | * pipemath-20160731-10.tar.gz | ||
| + | * pipemath-20161024-14.tar.gz | ||
| + | * pipemath-20170123-13.tar.gz | ||
| + | * pipemath-20170201-09.tar.gz | ||
| - | You will want to use a tool like **wget(1)** or **curl(1)** to non-interactively download | + | You would select the " |
| 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. | ||
| Line 50: | Line 64: | ||
| ====pipemath suite==== | ====pipemath suite==== | ||
| - | The pipemath suite is a collection of command-line tools that perform various basic math operations you may fine useful for this project. The tools include: | + | The pipemath suite is a collection of command-line tools that perform various basic math operations you may find useful for this project. The tools include: |
| * **plus** - addition | * **plus** - addition | ||
| Line 59: | Line 73: | ||
| * **abs** - absolute value | * **abs** - absolute value | ||
| * **negate** - negation | * **negate** - negation | ||
| + | * **negify** - absolute negation | ||
| * **sqrt** - square root | * **sqrt** - square root | ||
| - | With the exception of **abs**, **negate**, and **sqrt**, all the tools require two inputs (known as a binary operator; note, this is **NOT** saying you need to enter binary numbers into them... they expect decimal values). The first input **MUST** come from STDIN. The second input **MUST** come from the first command-line argument. | + | With the exception of **abs**, **negate**, **negify**, and **sqrt**, all the tools require two inputs (known as a binary operator; note, this is **NOT** saying you need to enter binary numbers into them... they expect decimal values). The first input **MUST** come from STDIN. The second input **MUST** come from the first command-line argument. |
| The tool, with the appropriate inputs, will perform the operation and output its result to STDOUT. | The tool, with the appropriate inputs, will perform the operation and output its result to STDOUT. | ||
| - | The **abs**, **negate**, and **sqrt** tools require only one input (known as a unary operator). That input **must** come from STDIN. When given an appropriate input, the operation is performed and will output its result to STDOUT. | + | The **abs**, **negate**, **negify**, and **sqrt** tools require only one input (known as a unary operator). That input **must** come from STDIN. When given an appropriate input, the operation is performed and will output its result to STDOUT. |
| =====Process===== | =====Process===== | ||
| In the **TASK** file, you will be given a set of tasks you need to construct command-lines for to solve, using the tools provided to you in both the **numbers** and **pipemath** suites. You will also want to make use of pipes and command expansions in your solutions. | In the **TASK** file, you will be given a set of tasks you need to construct command-lines for to solve, using the tools provided to you in both the **numbers** and **pipemath** suites. You will also want to make use of pipes and command expansions in your solutions. | ||
| - | There will also be both number, operation, minimum pipes, and maximum pipes constraints listed for each problem, which you will need to abide by in order to receive full credit. A < | + | There will also be result, numbers, operations, minimum pipes, and maximum pipes constraints listed for each problem, which you will need to abide by in order to receive full credit. |
| - | There may be quantity limits on how many times you can use each number or operation. If so, such will be shown in parenthesis following the item in question. | + | The potential constraints are as follows: |
| + | |||
| + | * **ANY:** no restrictions, | ||
| + | * **ONLY:** you are restricted to only those listed | ||
| + | * **WITH_LIMITS: | ||
| + | * **EXCEPT:** you are explicitly not allowed to use the listed; usually restricting an existing **ANY** domain | ||
| + | |||
| + | There may also be quantity limits on how many times you can use each number or operation. If so, such will be shown in parenthesis following the item in question. | ||
| + | |||
| + | Also, no cheating with idle " | ||
| As an example, take the following (formatted is it would appear in your **TASK** file): | As an example, take the following (formatted is it would appear in your **TASK** file): | ||
| Line 79: | Line 103: | ||
| task: 0 | task: 0 | ||
| result: 4 | result: 4 | ||
| - | numbers: three(2), five, seven, nine | + | numbers: |
| - | operations: | + | operations: |
| min_pipes: 2 | min_pipes: 2 | ||
| - | max_pipes: | + | max_pipes: |
| </ | </ | ||
| Line 123: | Line 147: | ||
| 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 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 copying the numbers |
| + | * 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. | ||
| There are some additional constraints you need to keep in mind: | There are some additional constraints you need to keep in mind: | ||
| Line 135: | Line 160: | ||
| * 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. | ||
| + | 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): | ||
| + | |||
| + | <cli> | ||
| + | lab46: | ||
| + | Task 0 result is: 13 | ||
| + | Task 1 result is: 27 | ||
| + | Task 2 result is: 32 | ||
| + | Task 3 result is: 7 | ||
| + | Task 4 result is: -4 | ||
| + | Task 5 result is: 57 | ||
| + | Task 6 result is: 2 | ||
| + | Task 7 result is: 98 | ||
| + | lab46: | ||
| + | </ | ||
| =====Submission===== | =====Submission===== | ||
| By successfully performing this project, you should have a set of task#.cli files (one for each task). You will want to submit these, along with a **upf0steps** file. | By successfully performing this project, you should have a set of task#.cli files (one for each task). You will want to submit these, along with a **upf0steps** file. | ||
| Line 153: | Line 192: | ||
| </ | </ | ||
| - | You should get some sort of confirmation indicating successful submission | + | You should get some sort of confirmation indicating successful submission |
| I'll be looking for the following: | I'll be looking for the following: | ||
| Line 165: | Line 204: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| *: | *: | ||
| *: | *: | ||
| - | *: | + | *: |
| *: | *: | ||
| </ | </ | ||
haas/spring2017/unix/projects/upf0.1487714849.txt.gz · Last modified: 2017/02/21 22:07 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
