This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2019:unix:projects:pct0 [2019/04/05 20:27] – [Submission] wedge | haas: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, | ||
=====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 | + | 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 | + | In the **pct0/** sub-directory of the UNIX Public Directory, under a directory by the name of your username, you will find the following |
+ | * **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), | There is also a **MANIFEST** file in the parent directory (the **pct0/** sub-directory), | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Should you desire, there' | ||
+ | |||
+ | 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===== | =====Process===== | ||
Solve and document the puzzle. | Solve and document the puzzle. | ||
Line 536: | Line 548: | ||
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 ' | + | * 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 key==== | ====puzzle key==== | ||
- | As indicated, you are to place the determined key to your puzzle in a regular text file called ' | + | 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 558: | Line 570: | ||
<cli> | <cli> | ||
- | lab46: | + | lab46: |
lab46: | lab46: | ||
</ | </ | ||
Line 565: | Line 577: | ||
<cli> | <cli> | ||
- | lab46: | + | lab46: |
RBVGPMOLJK | RBVGPMOLJK | ||
lab46: | lab46: | ||
Line 589: | Line 601: | ||
<cli> | <cli> | ||
- | lab46: | + | lab46: |
1395327d0826e3145b4f285a2b936707 | 1395327d0826e3145b4f285a2b936707 | ||
lab46: | lab46: | ||
Line 595: | 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 600: | Line 614: | ||
<cli> | <cli> | ||
- | lab46: | + | lab46: |
MATCH FOUND | MATCH FOUND | ||
lab46: | lab46: |