Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » spring2018 » unix » projects » upf1
haas:spring2018:unix:projects:upf1

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:spring2018:unix:projects:upf1 [2018/03/07 16:38] – [upf1steps] wedgehaas:spring2018:unix:projects:upf1 [2018/03/17 12:59] (current) – [Process] wedge
Line 8: Line 8:
 =====Errata===== =====Errata=====
  
-  * any bugfixes or project updates will be posted here+  * revision: unittools now all list **-I** argument (input delimiter) on help; **hm2Dm** link should also connect correctly (20180308)
  
 =====Objective===== =====Objective=====
Line 73: Line 73:
 The tools by default expect input via STDIN, and will output to STDOUT. The tools by default expect input via STDIN, and will output to STDOUT.
  
-These tools have command-line arguments which can alter their default behavior. You may want to review the options and defaults.+These tools have command-line arguments which can alter their default behavior. You may want to review the options and defaults (try running them with the **-h** argument to see what sort of functionality is available).
  
 =====Process===== =====Process=====
Line 117: Line 117:
 <cli> <cli>
 lab46:~/src/unix/upf1$ ./task0.cli lab46:~/src/unix/upf1$ ./task0.cli
-35.000 cm >> 13.780 in >> 1.148 ft+35.000cm >> 13.780in >> 1.148ft
 lab46:~/src/unix/upf1$  lab46:~/src/unix/upf1$ 
 </cli> </cli>
Line 133: Line 133:
   * your script should not produce ANY STDERR output   * your script should not produce ANY STDERR output
   * your script should ONLY produce STDOUT output in conformance with the below stated requirements. Any other output needs to be silenced.   * your script should ONLY produce STDOUT output in conformance with the below stated requirements. Any other output needs to be silenced.
 +  * You will want one unified command-line producing the end result, not separate one-step transitions. The idea is to utilize pipes.
 +    * semi-colons used to separate commands do not constitute one command-line, but several.
   * For each task, you'll want to display things as follows:   * For each task, you'll want to display things as follows:
     * "Task X conversion chain: CHAIN"     * "Task X conversion chain: CHAIN"
Line 189: Line 191:
 *:upf1:task#.cli files output using specified delimiter [3/3] *:upf1:task#.cli files output using specified delimiter [3/3]
 *:upf1:task#.cli files output only correct value and unit [4/4] *:upf1:task#.cli files output only correct value and unit [4/4]
-*:upf1:task#.cli files use specified number tools by quantity [4/4]+*:upf1:task#.cli files output in specified format [4/4]
 *:upf1:task#.cli files display no STDERR output [4/4] *:upf1:task#.cli files display no STDERR output [4/4]
 *:upf1:task#.cli files have solution within given constraints [4/4] *:upf1:task#.cli files have solution within given constraints [4/4]
-*:upf1:task#.cli files only have the solution command-line [4/4]+*:upf1:task#.cli files only contain the solution command-line [4/4]
 </code> </code>
  
haas/spring2018/unix/projects/upf1.1520440699.txt.gz · Last modified: 2018/03/07 16:38 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