Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » spring2019 » unix » projects » pct0
haas:spring2019:unix:projects:pct0

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:spring2019:unix:projects:pct0 [2019/04/01 16:38] – [puzzle key] wedgehaas:spring2019:unix:projects:pct0 [2019/08/04 13:46] (current) – [Objective] wedge
Line 11: Line 11:
  
 =====Objective===== =====Objective=====
-To continue to cultivate your problem solving, critical thinking, analytical, and observation skills; to apply your skills on the UNIX command-line.+To continue to cultivate your problem solving, critical thinking, analytical, and observation skills.
  
 +The aim here is on observation, analysis, and documentation. You are solving and documenting a problem by hand, thinking your way through to solution, NOT copying something, NOR writing any sort of program.
 =====Background===== =====Background=====
-The true nature of problem solving frequently involves critical thinking, analytical, and observation skills. Where problems are not solved by memorizing some pre-defined set of answers and regurgitating them mindlessly, but it crafting an elaborate solution from subtle cues and tested, experimental realizations.+The true nature of problem solving frequently involves critical thinking, analytical, and observation skills. Where problems are not solved by memorizing some pre-defined set of answers and regurgitating them mindlessly, but in crafting an elaborate solution from subtle cues and tested, experimental realizations.
  
-This project has puts you in contact with such endeavours.+This project puts you in contact with such endeavours.
  
 ====Long Division==== ====Long Division====
Line 520: Line 521:
 =====Getting started===== =====Getting started=====
  
-In the **pct0/** sub-directory of the UNIX Public Directory, under a directory by the name of your username, you will find the following file:+In the **pct0/** sub-directory of the UNIX Public Directory, under a directory by the name of your username, you will find the following files:
  
 +  * **bonus**
 +  * **practice0**
 +  * **practice1**
 +  * **practice2**
 +  * **practice3**
   * **puzzle**   * **puzzle**
  
-Copy this file into your project directory.+Copy these file into your project directory.
  
 There is also a **MANIFEST** file in the parent directory (the **pct0/** sub-directory), which will contain MD5sums of the various puzzle keys, provided to help you in verifying your puzzle key. There is also a **MANIFEST** file in the parent directory (the **pct0/** sub-directory), which will contain MD5sums of the various puzzle keys, provided to help you in verifying your puzzle key.
-=====Process===== 
-In the **TASK** file, you will be given a set of source quantities/units and destination units you need to construct command-lines for to solve, using the tools provided to you in the **unittools** suite. You will also want to make use of pipes and command expansions in your solutions. 
  
-As an example, take the following (formatted is it would appear in your **TASK** file):+For this project, the only puzzle you HAVE to solve in order to be eligible for full credit will be the one contained in the **puzzle** file.
  
-<code> +Should you desire, there's an opportunity to gain some bonus points, which can be earned by successfully solving and documenting your solution to the puzzle contained within the file **bonus** and reporting it to me as appropriate.
-task: 0 +
-precision: 3 +
-input_value: 35 +
-input_unit: cm +
-output_unit: ft +
-chain_delim: " >> " +
-</code>+
  
-With these in mind, we can set about solving this problem, using the tools in combination to arrive at the desired result. +As you gear up to work on the project-required puzzle (or additionally the bonus puzzle), I have provided a sampling of practice puzzles that you can try your hand on in order to get more experience working with these type of puzzles. Doing them will not net you any points, nor will not doing them diminish your totals for this project. I would recommend doing them, though, as the more exposure you have within this domain, the more patterns become identified, further facilitating your chances of success. 
- +=====Process===== 
-A potential solution would be as follows: +Solve and document the puzzle.
- +
-<cli> +
-lab46:~/src/unix/upf1$ echo "35" | cm2in +
-13.78 in +
-lab46:~/src/unix/upf1$ echo "13.78" | in2ft +
-1.15 ft +
-lab46:~/src/unix/upf1$  +
-</cli> +
- +
-But that's not very optimized. We could instead do something better, like: +
- +
-<cli> +
-lab46:~/src/unix/upf1$ echo "35.000 cm" | cm2in OPTIONS | in2ft OPTIONS +
-35.000 cm >> 13.780 in >> 1.148 ft +
-lab46:~/src/unix/upf1$  +
-</cli> +
- +
-Note that with **precision**, you need to instruct the tools to display out to the specified number of decimal places. +
- +
-We'll want to record our command-lines in the appropriate place. Since this is task #0, we'll want to record it in a file called: **task0.cli**, which should basically just contain the command-lines you ran, merely placed in a text file. +
- +
-For final output, we'll want to display the chain of conversions we went through. So, for this above example: +
- +
-<cli> +
-lab46:~/src/unix/upf1$ ./task0.cli +
-35.000cm >> 13.780in >> 1.148ft +
-lab46:~/src/unix/upf1$  +
-</cli>+
  
-Basically, each task#.cli will be its own script. If we were to execute it, the correct result should be produced.+On your own.
  
 +Seek to discover and explore and understand, NOT to just come up with an answer.
 =====Your Solution===== =====Your Solution=====
 As this project focuses more on the critical thinking process than being heavy in unravelling a problem using UNIX commands, your solution will be in 2 parts: As this project focuses more on the critical thinking process than being heavy in unravelling a problem using UNIX commands, your solution will be in 2 parts:
  
-  * your puzzle key, in a textfile called 'key' containing ONLY the capital letters corresponding in order to the 0-9 values (and a trailing newline). +  * your puzzle key, in a textfile called 'puzzle.key' containing ONLY the capital letters corresponding in order to the 0-9 values (and a trailing newline). 
-  * your documentation of your solving and exploration of the puzzle. If you did this on paper, I'll want it digitized and submitted as a file with this project.+  * your documentation of your solving and exploration of the puzzle. If you did this on paper, I'll want it digitized and submitted as a file with this project. The file, if is text form, should be called 'puzzle.solution'; if an image, please append the image format to the end of the filename.
  
 ====puzzle key==== ====puzzle key====
-As indicated, you are to place the determined key to your puzzle in a regular text file called 'key', and will contain ONLY the capital letters, in order from 0-9, of your puzzle (and a trailing newline).+As indicated, you are to place the determined key to your puzzle in a regular text file called 'puzzle.key', and will contain ONLY the capital letters, in order from 0-9, of your puzzle (and a trailing newline).
  
 For example, using the example puzzle above: For example, using the example puzzle above:
Line 600: Line 570:
  
 <cli> <cli>
-lab46:~/src/unix/pct0$ echo "RBVGPMOLJK" > key+lab46:~/src/unix/pct0$ echo "RBVGPMOLJK" > puzzle.key
 lab46:~/src/unix/pct0$  lab46:~/src/unix/pct0$ 
 </cli> </cli>
Line 607: Line 577:
  
 <cli> <cli>
-lab46:~/src/unix/pct0$ cat key+lab46:~/src/unix/pct0$ cat puzzle.key
 RBVGPMOLJK RBVGPMOLJK
 lab46:~/src/unix/pct0$  lab46:~/src/unix/pct0$ 
Line 631: Line 601:
  
 <cli> <cli>
-lab46:~/src/unix/pct0$ md5sum key | cut -d' ' -f1+lab46:~/src/unix/pct0$ md5sum puzzle.key | cut -d' ' -f1
 1395327d0826e3145b4f285a2b936707 1395327d0826e3145b4f285a2b936707
 lab46:~/src/unix/pct0$  lab46:~/src/unix/pct0$ 
Line 637: Line 607:
  
 Obviously, YOUR MD5 sum will be DIFFERENT from this, because this is the MD5 sum of the puzzle key explored at the top of this project page. Obviously, YOUR MD5 sum will be DIFFERENT from this, because this is the MD5 sum of the puzzle key explored at the top of this project page.
 +
 +NOTE: MD5 sums of your bonus and practice puzzles are also present in the MANIFEST file, so you can perform verifications on them in the same manner.
  
 ====Look for matching MD5 sum in MANIFEST==== ====Look for matching MD5 sum in MANIFEST====
Line 642: Line 614:
  
 <cli> <cli>
-lab46:~/src/unix/pct0$ cat ${PROJECTDIR}/MANIFEST | grep $(md5sum key | cut -d' ' -f1) && echo "MATCH FOUND" || echo "NO MATCHES FOUND"+lab46:~/src/unix/pct0$ cat ${PROJECTDIR}/MANIFEST | grep $(md5sum puzzle.key | cut -d' ' -f1) && echo "MATCH FOUND" || echo "NO MATCHES FOUND"
 MATCH FOUND MATCH FOUND
 lab46:~/src/unix/pct0$  lab46:~/src/unix/pct0$ 
Line 649: Line 621:
 If you have a match, congratulations, you unravelled the puzzle correctly. Just remember: evaluation is heavily based on your documentation of the process, not whether or not you can arrive at the correct answer key. If you have a match, congratulations, you unravelled the puzzle correctly. Just remember: evaluation is heavily based on your documentation of the process, not whether or not you can arrive at the correct answer key.
 =====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 **upf1steps** file.+By successfully performing this project, you should be submitting files that satisfy the following requirements: 
 + 
 +  * a 'puzzle.key' file formatted as indicated elsewhere in this project document 
 +  * a 'puzzle.solution' file containing organized and informative detailing of your path to solution 
 + 
 +Additionally, although optional, if you'd like to do similar for the bonus puzzle: 
 +  * a 'bonus.key' file formatted as indicated elsewhere in this project document 
 +  * a 'bonus.solution' file containing organized and informative detailing of your path to solution
  
 To submit this project to me using the **submit** tool, run the following command at your lab46 prompt: To submit this project to me using the **submit** tool, run the following command at your lab46 prompt:
  
 <cli> <cli>
-$ submit unix upf1 upf1steps task*.cli +$ submit unix pct0 puzzle.key puzzle.solution 
-Submitting unix project "upf1": +Submitting unix project "pct0": 
-    -> upf1steps(OK) +    -> puzzle.key(OK) 
-    -> task0.cli(OK) +    -> puzzle.solution(OK)
-    -> task1.cli(OK) +
-    -> task2.cli(OK) +
-    -> task3.cli(OK) +
-       ...+
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
 </cli> </cli>
  
-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.+or, if submitting results for the bonus puzzle as well: 
 + 
 +<cli> 
 +$ submit unix pct0 puzzle.key puzzle.solution bonus.key bonus.solution 
 +Submitting unix project "pct0": 
 +    -> puzzle.key(OK) 
 +    -> puzzle.solution(OK) 
 +    -> bonus.key(OK) 
 +    -> bonus.solution(OK) 
 + 
 +SUCCESSFULLY SUBMITTED 
 +</cli> 
 + 
 +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:
  
 <code> <code>
-78:upf1:final tally of results (78/78) +78:pct0:final tally of results (78/78) 
-*:upf1:upf1steps has valid list of non-interactive instructions [4/4] +*:pct0:puzzle.key file submitted with correct values [7/7] 
-*:upf1:upf1steps only copies/alters files if USER matches [4/4] +*:pct0:puzzle.key file formatted according to project specifications [6/6] 
-*:upf1:upf1steps builds the various task#.cli files it runs [4/4] +*:pct0:puzzle.solution is organized and easy to read [35/35] 
-*:upf1:upf1steps obtains the latest pipemath release from site [4/4] +*:pct0:puzzle.solution adequately documents discovery of each letter [30/30]
-*:upf1:upf1steps only displays specified STDOUT output [4/4] +
-*:upf1:upf1steps resiliently creates local project directory [4/4] +
-*:upf1:upf1steps copies public dir data with absolute path [4/4] +
-*:upf1:upf1steps makes clear, effective use of wildcards [4/4] +
-*:upf1:upf1steps defines and uses custom variables [4/4] +
-*:upf1:upf1steps uses command expansions to get information [4/4] +
-*:upf1:upf1steps uses a loop to drive numbers in final output [4/4] +
-*:upf1:upf1steps automates the task when run [4/4] +
-*:upf1:all files are organized, clear, and easy to read [4/4] +
-*:upf1:task#.cli files output using specified precision [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 in specified format [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 only contain the solution command-line [4/4]+
 </code> </code>
- 
-Additionally: 
-  * 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 
haas/spring2019/unix/projects/pct0.1554136731.txt.gz · Last modified: 2019/04/01 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