haas:spring2017:unix:projects
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:spring2017:unix:projects [2017/02/05 22:57] – [Week 3] wedge | haas:spring2017:unix:projects [2017/04/24 15:16] (current) – wedge | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * [[/ | * [[/ | ||
| * [[/ | * [[/ | ||
| + | * [[/ | ||
| + | * pbx2 (bonus; complete by 20170301) | ||
| + | * [[/ | ||
| + | * [[/ | ||
| + | * [[/ | ||
| + | * [[/ | ||
| + | * [[/ | ||
| + | * EoCE (bottom of journal) (due 20170512-141459) | ||
| + | ======Class Stats====== | ||
| + | * [[/ | ||
| + | ======Week 13====== | ||
| + | * For those getting to that point in the EoCE and are having issues operating **dd(1)**, in addition to referencing the manual page, I put together a quick tutorial showing some basic operations: | ||
| + | * [[/ | ||
| + | ======Week 12====== | ||
| + | * As I mentioned last week, the UNIX IPKA is now available. Prior average times are about 1 hour 30 minutes, so be sure to plan accordingly. | ||
| + | * Some good progress is being made on the EoCE by some. Also some good questions and realizations. Keep up the good work. | ||
| - | ======Class Stats====== | + | ======Week 11====== |
| - | * [[/haas/spring2017/unix/projects/status|status]] | + | * Welcome back! I hope everyone had a phenomenal spring break! |
| + | * The EoCE will be unveiled, at which point that will be the main focus from here on out. | ||
| + | * It will be located at the bottom of your journal. | ||
| + | |||
| + | ======Week 10====== | ||
| + | * Week before break; it was a general "work on stuff" time. | ||
| + | |||
| + | ======Week 9====== | ||
| + | * The fun continues! **icp0** will occupy our time in class this week, as you work to automate the drawing of pretty pictures- all from a script run on the command-line! | ||
| + | * Your next project is **gfo0**, which is also a script-heavy project. Because you've been so awesome, this one won't be due until the Wednesday we get back from break (think of the bonus point opportunities!) | ||
| + | * Have we hit and moved beyond the high water mark for the semester? **upf1** showed a tangible decline in overall class performance. The average, median, and mode all took massive hits. Largely due to outright non-submits. At the same time, for many (who submitted), it was among their best work (including being their best work all semester). It appears we have a growing divide between those who are //really// getting it and those who are struggling. | ||
| + | ======Week 8====== | ||
| + | * the project this week dives into a full-blown script; **usf0** has us interacting with binary, octal, decimal, and hexadecimal values | ||
| + | * your .cli files need to contain JUST the command-lines to produce the desired output... the "Task 0 result is" part needs to be in the main steps file, which then executes each .cli file. A few of you rigged up this overly elaborate .cli file chaining. | ||
| + | |||
| + | ======Week 7====== | ||
| + | * **usr0** | ||
| + | * Warning grades are on the horizon; for those with a D or F as of my time of entering warning grades, such will be reported. Most of you have nothing to worry about. | ||
| + | * **upf1** is the next project in the "pipe fun" series of projects. | ||
| + | * With **usr0** now behind us, I have adapted the **urev** tool for general use- for those that wanted to keep up your file permission practice, you may now do so. | ||
| + | |||
| + | ======Week 6====== | ||
| + | * With the evaluation of **pbx1** and **uka1**, we now have enough data points to start generating the class stats page to potentially see useful trends. Check it out. | ||
| + | * Some observed trends: | ||
| + | * So far, someone (at least 1) has always gotten a 100% | ||
| + | * So far, someone (at least 1, but not always the same someone) has always gotten a 0% | ||
| + | * With each passing project, the class average and medians seem to slide down, yet the mode (most frequent score) remains in the 90' | ||
| + | * Reviewing the **uka1** knowledge assessment, some general comments: | ||
| + | * I would have thought that giving something familiar to what you've seen before (past, current, and bonus projects, PLUS a practice knowledge assessment just a week prior), there' | ||
| + | * And a big part of that is just in reading and following directions. | ||
| + | * Topics and activities we encounter ARE and continue to be comprehensive... that means what you learned before is still needed as it gets built upon. We don't just learn these things for show... these are important concepts that allow for new approaches to solving problems. | ||
| + | * The next project, **upf0**, has us exploring pipes in a themed problem solving setting. I had a lot of fun putting it together, so hopefully you'll have just as much fun undertaking it! | ||
| + | * This week, we'll likely continue with some of our shell scripting endeavors, getting to: | ||
| + | * loops | ||
| + | * possibly functions | ||
| + | * ... and maybe working through some scripts together in class to see more examples. | ||
| + | * But remember, none of this will become more familiar if you do not take the time to play with this outside of class. I was dismayed at the number of people who, prior to break, asked me how to access the class homepage/lab46 from outside the room (this was something you were to have established in the FIRST PROJECT, and hearing it then only confirmed that you haven' | ||
| + | |||
| + | ======Break 1====== | ||
| + | * It has been a relatively quiet break... only 12 or so people have commenced on the **usr0** project... remember that with the built-in time limits, waiting until we get back may be a costly decision to have made. | ||
| + | |||
| + | ======Week 5====== | ||
| + | * I've put together the bonus puzzlebox, pbx2. To get it, copy the files from your user directory residing within the **pbx2/** subdirectory of the UNIX Public Directory. There will be a README file with further instructions. | ||
| + | * Your next project is ready: **usr0** | ||
| + | * we're going a little light this week as we have the knowledge assessment on Friday, AND I am giving you a chance to experiment and play. Please take advantage of this opportunity. | ||
| + | * Remarks on the practice knowledge assessment (uka0): | ||
| + | * for something that was supposed to be closed person, there was certainly a heck of a lot of " | ||
| + | * My tendency is to give people the rope to hang themselves with. I may not directly intervene, but I may set score vampires loose on your results, sucking away points as appropriate (so be warned). | ||
| + | * more than 1 person (that' | ||
| + | * file permissions are still plaguing people. At least it has progressed from "I don't know what to do" to "I cannot access the file" | ||
| + | * of course the critical response you need to take is "why can I not access the file?" and to have the knowledge of the **chmod** command not be a mystery (it has been touched on in almost every project, yet I still got some people who were still unable to recall both the command and how to effectively operate it!) | ||
| + | * " | ||
| + | * square brackets in argument specifications denote optionality. You do not include them when specifying that feature. | ||
| + | * reading: I left an important " | ||
| + | * This is different from having trouble understanding what to do with the information. But the number of people trying to process the information vs. those oblivious to it was very much out of proportion. | ||
| + | * observation: | ||
| + | * again, this isn't a class about learning commands. It is a class about solving problems, using tools in strategic ways. | ||
| + | * steps file: more than a few did not include the copy step, nor properly include the steps to establish your project working directory. | ||
| + | * some that included the copy step did not use a full absolute path to copy it. | ||
| + | * now, that isn't to say that progress wasn't made. A number of people took on the challenge, encountered new situations, and adapted to it accordingly. I am most pleased by that (and those individuals likely know who they are). | ||
| ======Week 4====== | ======Week 4====== | ||
| Line 29: | Line 104: | ||
| * and be sure to include the initial file copying step! | * and be sure to include the initial file copying step! | ||
| * making a local data directory to store your project files is a valid step that must be included in the steps file | * making a local data directory to store your project files is a valid step that must be included in the steps file | ||
| + | * putting the nano lines in the script doesn' | ||
| * generally, a lot of problems were due to developed habits of not reading between the lines- assuming things were in place without specifying the precise step(s) the computer would need to accomplish the task from the steps file. | * generally, a lot of problems were due to developed habits of not reading between the lines- assuming things were in place without specifying the precise step(s) the computer would need to accomplish the task from the steps file. | ||
| * Now that you know how to run scripts, you should verify your pbx1steps file executes cleanly and correctly before submission. | * Now that you know how to run scripts, you should verify your pbx1steps file executes cleanly and correctly before submission. | ||
haas/spring2017/unix/projects.1486335465.txt.gz · Last modified: 2017/02/05 22:57 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
