Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » spring2017 » unix » projects » upf0
haas:spring2017: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:spring2017:unix:projects:upf0 [2017/02/25 21:31] – [Process] wedgehaas:spring2017:unix:projects:upf0 [2017/02/27 18:27] (current) – [upf0steps] wedge
Line 64: 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 85: Line 85:
 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 <nowiki>*</nowiki> in any field indicates you are free to use any and all in that category. You may also see values preceded with a <nowiki>-</nowiki> sign, which specifically negates their use (shorter than writing out everything EXCEPT that value). In such cases, if there are only negated values in a field, that implies whatever isn't negated is allowed.+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, any in applicable category can be used 
 +  * **ONLY:** you are restricted to only those listed 
 +  * **WITH_LIMITS:** usually providing specific restrictions within an **ANY** domain 
 +  * **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 "filler" operations, like "plus 0 | plus 0 | plus 0" to rack up needed pipe counts.
  
 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 94: Line 103:
 task: 0 task: 0
 result: 4 result: 4
-numbers: three(2), five, seven, nine +numbers: ONLY(three(2), five, seven, nine) 
-operations: *+operations: ANY
 min_pipes: 2 min_pipes: 2
-max_pipes: *+max_pipes: ANY
 </code> </code>
  
Line 158: Line 167:
 Task 1 result is: 27 Task 1 result is: 27
 Task 2 result is: 32 Task 2 result is: 32
 +Task 3 result is: 7
 Task 4 result is: -4 Task 4 result is: -4
 Task 5 result is: 57 Task 5 result is: 57
Line 182: Line 192:
 </cli> </cli>
  
-You should get some sort of confirmation indicating successful submission (actually, two) 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: I'll be looking for the following:
Line 194: Line 204:
 *:upf0:task0.cli produces correct result [2/2] *:upf0:task0.cli produces correct result [2/2]
 *:upf0:task0.cli uses specified numbers by quantity [2/2] *:upf0:task0.cli uses specified numbers by quantity [2/2]
-*:upf0:task0.cli uses specified operations [2/2]+*:upf0:task0.cli uses specified operations by quantity [2/2]
 *:upf0:task0.cli solution within min_pipes, max_pipes [2/2] *:upf0:task0.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task1.cli produces correct result [2/2] *:upf0:task1.cli produces correct result [2/2]
 *:upf0:task1.cli uses specified numbers by quantity [2/2] *:upf0:task1.cli uses specified numbers by quantity [2/2]
-*:upf0:task1.cli uses specified operations [2/2]+*:upf0:task1.cli uses specified operations by quantity [2/2]
 *:upf0:task1.cli solution within min_pipes, max_pipes [2/2] *:upf0:task1.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task2.cli produces correct result [2/2] *:upf0:task2.cli produces correct result [2/2]
 *:upf0:task2.cli uses specified numbers by quantity [2/2] *:upf0:task2.cli uses specified numbers by quantity [2/2]
-*:upf0:task2.cli uses specified operations [2/2]+*:upf0:task2.cli uses specified operations by quantity [2/2]
 *:upf0:task2.cli solution within min_pipes, max_pipes [2/2] *:upf0:task2.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task3.cli produces correct result [2/2] *:upf0:task3.cli produces correct result [2/2]
 *:upf0:task3.cli uses specified numbers by quantity [2/2] *:upf0:task3.cli uses specified numbers by quantity [2/2]
-*:upf0:task3.cli uses specified operations [2/2]+*:upf0:task3.cli uses specified operations by quantity [2/2]
 *:upf0:task3.cli solution within min_pipes, max_pipes [2/2] *:upf0:task3.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task4.cli produces correct result [2/2] *:upf0:task4.cli produces correct result [2/2]
 *:upf0:task4.cli uses specified numbers by quantity [2/2] *:upf0:task4.cli uses specified numbers by quantity [2/2]
-*:upf0:task4.cli uses specified operations [2/2]+*:upf0:task4.cli uses specified operations by quantity [2/2]
 *:upf0:task4.cli solution within min_pipes, max_pipes [2/2] *:upf0:task4.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task5.cli produces correct result [2/2] *:upf0:task5.cli produces correct result [2/2]
 *:upf0:task5.cli uses specified numbers by quantity [2/2] *:upf0:task5.cli uses specified numbers by quantity [2/2]
-*:upf0:task5.cli uses specified operations [2/2]+*:upf0:task5.cli uses specified operations by quantity [2/2]
 *:upf0:task5.cli solution within min_pipes, max_pipes [2/2] *:upf0:task5.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task6.cli produces correct result [2/2] *:upf0:task6.cli produces correct result [2/2]
 *:upf0:task6.cli uses specified numbers by quantity [2/2] *:upf0:task6.cli uses specified numbers by quantity [2/2]
-*:upf0:task6.cli uses specified operations [2/2]+*:upf0:task6.cli uses specified operations by quantity [2/2]
 *:upf0:task6.cli solution within min_pipes, max_pipes [2/2] *:upf0:task6.cli solution within min_pipes, max_pipes [2/2]
 *:upf0:task7.cli produces correct result [2/2] *:upf0:task7.cli produces correct result [2/2]
 *:upf0:task7.cli uses specified numbers by quantity [2/2] *:upf0:task7.cli uses specified numbers by quantity [2/2]
-*:upf0:task7.cli uses specified operations [2/2]+*:upf0:task7.cli uses specified operations by quantity [2/2]
 *:upf0:task7.cli solution within min_pipes, max_pipes [2/2] *:upf0:task7.cli solution within min_pipes, max_pipes [2/2]
 </code> </code>
haas/spring2017/unix/projects/upf0.1488058277.txt.gz · Last modified: 2017/02/25 21:31 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
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki