Differences

This shows you the differences between two versions of the page.

--- blog:spring2016:mpotapen:journal [2016/05/11 02:52] – mpotapen
+++ blog:spring2016:mpotapen:journal [2016/05/11 15:51] (current) – mpotapen
@@ Line 188: / Line 188: @@
   * What concepts are you dealing with that may not make perfect sense?
   * What challenges are you facing with respect to the course?
-======EoCE======
-=====Rules=====
-Presented within will be various questions evaluating your knowledge and experience gained this semester. In places where you are able, the more you write and explain topics the better the chance you will have of receiving full credit (and alternatively, the more credit you will receive should something defer correctness).
-The questions on this experience are open resource with the exception of other individuals. In that respect, it is **CLOSED PERSON**. This means you are not to communicate with other people (either in the class or otherwise), in real life or electronically. Use your own knowledge, use your own skills, and use your own ability to access the allowed resources to aid you in coming up with your well thought out responses to each question.
-You are allowed, and expected, to seek clarification on any question by asking me. But the aim here is to evaluate what you have learned, so do not expect any handholding, handouts, or tutoring. You may find I will be more responsive to finer, more fluent questions; just asking "I don't know, what do I do?" is neither inspiring nor encouraging.
-You are to do **all** items. Submission is to be as follows:
-  * an organized and easy to read presentation of information on your EoCE wiki page.
-  * if applicable, a submitted archive using the **submit** tool (likely via Makefile)
-The EoCE will be worth 24% of your overall grade, and will be broken down as follows:
-  * If there is an In-Person Knowledge Assessment, the EoCE breakdown will be as follows:
-    * 1/3 will count toward the project component of your grade (constituting 8% of the project component total).
-      * this will include any programs/scripts created and their correctness to stated specifications
-    * 1/3 will count toward the journal component of your grade (constituting 8% of the journal component total).
-      * this will involve documenting your responses to various questions on this EoCE document, along with the consideration of correctness to stated specifications (where applicable)
-    * 1/3 will count toward the participation component of your grade (constituting 8% of the project component total).
-      * this involves completing the in-person knowledge assessment, with consideration of correctness to stated specifications
-  * If there is no In-Person Knowledge Assessment, the EoCE breakdown is as such:
-    * 1/2 will count toward the project component of your grade (constituting 12% of the project component total).
-      * this will include any programs/scripts created and their correctness to stated specifications
-    * 1/2 will count toward the journal component of your grade (constituting 12% of the journal component total).
-      * this will involve documenting your responses to various questions on this EoCE document, along with the consideration of correctness to stated specifications (where applicable)
-**DEADLINE FOR SUBMISSION:** You have until 02:14:59pm (that's 14:14:59 in 24-hour time) Thursday, May 12th, 2016 to complete your EoCE(s). This is the ultimate deadline for any and all coursework. There is no "late", only "too late". Don't be that person, not with this.
-While some classes are allocated a specific meeting time during finals week, I make all such times available should you be free and have questions. Available times (all in **R108**) are:
-  * Monday,    May 09th, 2016 from 10:00am - 02:00pm
-  * Tuesday,   May 10th, 2016 from 08:00am - 02:00pm
-  * Wednesday, May 11th, 2016 from 10:00am - 02:15pm
-  * Thursday,  May 12th, 2016 from 10:00am - 02:15pm
-Good luck!
-=====UNIX=====
-====0x0: Script Analysis====
-Analyze the following script and respond to the questions that follow:
-<code bash 1>
-#!/bin/bash
-#
-# Run this script as follows:
-#   ./script 44.1 33 22 3 11 12 23 0 34 2 45 5 1 3.14159 4
-#
-function process() {
-    sleep   "$1"
-    echo -n "$1 "
-}
-for data in $*; do
-    process "$data" &
-done
-wait
-echo
-exit 0
-</code>
-**ASSUMPTIONS:** To make your task easier, you may work with the following assumptions:
-  * no value provided on the command-line will be greater than 60 (ie all values will range from 0-59)
-  * no need to do command-line argument error checking: assume only correct values will be provided
-===Questions to answer===
-  * What does the **<nowiki>$*</nowiki>** variable do?
-  * What does the **&** symbol do?
-  * What is this script doing? (think general operation/end product)
-  * How is it doing this?
-  * Adjust the script to output each value on a line by itself, include it below
-  * Comment the script and include your updated code below (first code block)
-  * If you wanted to reverse the order of processing, how would you do it (second code block)
-Please respond to all questions either directly after, under, or in an otherwise clearly identified manner.
-===Commented Script===
-Place your code to the updated scripts here:
-<code bash>
-# Your commented, one value per line script
-</code>
-===Reverse Order Script===
-<code bash>
-# Your script that reverses order of processing
-</code>
-====0x1: super puzzlebox 2 turbo====
-In **/var/public/spring2016/unix/eoce/** is a file called **swe7tfa.mp4**, which is your EoCE puzzlebox. Unravel its mysteries, and post any command-lines used and end results obtained here.
-<cli>
-lab46:~/src/unix/eoce/0x1$
-</cli>
-Feel free to create any many stanzas of **cli** tags as needed (just make sure for every opening tag there's a corresponding closing tag).
-====0x2: emordnilaP as a Palindrome====
-Write two scripts, each one implementing palindrome checking functionality.
-Each script must validate whether or not input is a palindrome (or not), and output a message appropriately.
-Each script must perform its palindrome processing in an entirely different way from the other.
-The intent here is to come up with fundamentally different ways of solving a problem.
-===Your Code===
-Put your code for your first iteration here:
-<code bash>
-# Your code
-</code>
-===Your Code===
-Put your code for your second iteration here:
-<code bash>
-# Your code
-</code>
-====0x3: By the pale moonlight====
-As a mid-level UNIX support specialist, and fledgling scripting deity, you find a commonly given explanation for why something broke that seemingly started working on its own has been that it "must be the phase of the moon".
-Bored one afternoon with debugging misguided user configurations that set ls colors of directories to red foreground on red background (what were they thinking?), you decided to hone your moon phase skills and offer up a bit of variety to support clients.
-The **pom**(**1**) tool reports the current phase of the moon. It can also be given an argument of a particular date, and it will report the moon phase.
-Your task is to write a script that:
-  * if given no command-line arguments, will report the next day and approximate starting time (from the current date) that "The Moon will be Full".
-  * if given a command-line (a specific year), display that year's full moons (From Jan 1st - Dec 31st), identifying the date and approximate start time of each occurrence.
-===Your script here===
-<code bash>
-</code>
-====0x4: Scripting the count====
-Understanding should not come from exclusively memorization; in fact, it is far more important to know where to look than to know every possible aspect of a thing. The frequently-used aspects will flow, the lesser-used should be a good or reference away.
-In computing, the ability to deal with binary, octal, and hexadecimal values in a quick and effective fashion involves having more immediate recall on a subset of important knowledge; specifically, how these different number bases correspond up to a common value (we'll go for 15, or 0xF in hex).
-I've drawn the following table on the board in various classes; it is a good thing to be able to produce on your own, and to memorize its contents (especially how they relate to one another).
-Your task is to write a script that calculates and outputs the following:
-<cli>
-lab46:~/src/unix/eoce/0x4$ ./0x4
-+===============================================+
-|  binary  |  octal   |  decimal  | hexadecimal |
-| (base 2) | (base 8) | (base 10) |  (base 16)  |
-+===============================================+
-|   0000   |   000    |     0     |     0x0     |
-|   0001   |   001    |     1     |     0x1     |
-|   0010   |   002    |     2     |     0x2     |
-|   0011   |   003    |     3     |     0x3     |
-|   0100   |   004    |     4     |     0x4     |
-|   0101   |   005    |     5     |     0x5     |
-|   0110   |   006    |     6     |     0x6     |
-|   0111   |   007    |     7     |     0x7     |
-|   1000   |   010    |     8     |     0x8     |
-|   1001   |   011    |     9     |     0x9     |
-|   1010   |   012    |    10     |     0xA     |
-|   1011   |   013    |    11     |     0xB     |
-|   1100   |   014    |    12     |     0xC     |
-|   1101   |   015    |    13     |     0xD     |
-|   1110   |   016    |    14     |     0xE     |
-|   1111   |   017    |    15     |     0xF     |
-+===============================================+
-lab46:~/src/unix/eoce/0x4$
-</cli>
-By "calculates and outputs", I mean:
-  * you are not just to have fixed literal lines that you are displaying.
-  * you must calculate each value, and you must do so using variables, if statements, and loops.
-  * you can use pipelines to commands, but I do not want any calculators used (sorry, no bc).
-    * you may use simple iteration, as provided via the bash **let** keyword
-  * You are managing the progression of numbers on your own!
-Your script should produce the table, resembling mine as closely as possible.
-===Your script===
-Provide your script here:
-<code bash>
-</code>
-====0x5: In-person Knowledge Assessment====
-During some standard time between now and 02:14:59pm (that's 14:14:59 in 24-hour time) Thursday, May 12th, 2016, you are to approach me to perform an in-person knowledge assessment. This is to help ensure consistency and validity of the other work you are performing on the EoCE (which of course you are following the rules and doing it all yourself with no outside help).
-Valid times include any remaining class or office/lab hours **with no structured/scheduled activities**, or any of the finals week availabilities.
-Note that you only have a single opportunity to take this (no make sure you allocate yourself an adequate amount of time).
-__Pro tip__: Don't wander in 30 minutes (or similarly time deficient) before a deadline and expect an extension/more time to work on it.
-When ready, please proceed: [[/ipka/spring2016/unix/mpotapen|UNIX IPKA]]
-====0x6: Reflection====
-Answer me the following:
-  * Of all the work you've done this semester in this course, identify something that was meaningful to you. What is it?
-  * Why does it stick out in your mind? Explain.
-  * How did you feel about the course?
-  * Was it useful/interesting to you?
-  * What was your least favorite aspect, and why?
-  * Any comments, suggestions?
-====0x7: Personal Assessment====
-After an exciting and intellectually challenging run, we're arriving at the end of this semester's journey. Some will be moving on, others sticking around for more. I make it a practice to listen to your thoughts and suggestions. The course, as we all experienced it, unfolds in a manner pertaining, in part, to how you respond to concepts and topics (do we need more time, can I crank it up a couple notches, etc.) so each semester and each class is entirely different from any other- because of each of you, and all of us, working together and learning together.
-So, searching deep down within your soul- balancing reason with emotion, and considering attendance and timeliness; what grade do you feel you deserve for this course, and why? Justify your answer based on your own perceived performance to course ideals and content, not on need or desire.
-=====Submission=====
-====Journal====
-All responses to questions, unless specifically indicated otherwise, should be addressed on this document (or the intended wiki document).
-Please edit the appropriate section and provide the necessary information.
-====File Submission====
-For any other deliverables, if using a project directory tree you can obtain a copy of, when ready, submit it using the **Makefile**, as follows:
-<cli>
-lab46:~/src/CLASS/eoce$ make submit
-...
-</cli>
-If no formal project, you can submit requested files (preferably in an archive of their own), using the **submit** tool. A project called **eoce** has been likely set up for this purpose.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools